March 1st, 2019 by miki

Because it is nice-to-know™ what people and systems around you are talking about standards are a better-than-complete-chaos-and-mayhem way to align thoughts, terms and procedures.

Request for Comments (Internet Standards)

Internet Standards are the happy children of which the internet is made up. These transition through phases from infant babies called Internet-Drafts (I-Ds) through scrambling toddlers called Request for Comments (RFCs) until getting all mature and on their own feets as a youngster STDs. Many, however, do never really grow up or do so very slowly or even refuse to leave the playful child state and end up roaming around as toddler RFCs.

The complete on-boarding list can be found at the editor kindergarten and listed below are direct references to the most attended ones in a Mikini context.

The Teacher

Transport Class

  • STD 7/RFC 793 Transmission Control Protocol (aka. TCP)
  • STD 37/RFC 826 Ethernet Address Resolution Protocol (aka. ARP)
  • RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
  • RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
  • RFC 7232 Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
  • RFC 7233 Hypertext Transfer Protocol (HTTP/1.1): Range Requests
  • RFC 7234 Hypertext Transfer Protocol (HTTP/1.1): Caching
  • RFC 7235 Hypertext Transfer Protocol (HTTP/1.1): Authentication
  • RFC 2616 Hypertext Transfer Protocol — HTTP/1.1 (obsolete single page edition)
  • RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3 (ANN:, tracker:
  • RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
  • RFC 6455 The WebSocket Protocol
  • RFC 7296 Internet Key Exchange Protocol Version 2 (IKEv2)
  • RFC 7252 The Constrained Application Protocol (CoAP)

Shell Class (SSH2/secsh)

  • RFC 4251 The Secure Shell (SSH) Protocol Architecture
  • RFC 4252 The Secure Shell (SSH) Authentication Protocol
  • RFC 4253 The Secure Shell (SSH) Transport Layer Protocol
  • RFC 4254 The Secure Shell (SSH) Connection Protocol
  • RFC 4255 Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
  • RFC 4716 The Secure Shell (SSH) Public Key File Format
  • I-D draft-ietf-secsh-filexfer-13 SSH File Transfer Protocol

Authentication Class

  • RFC 5849 The OAuth 1.0 Protocol
  • RFC 7617 The ‘Basic’ HTTP Authentication Scheme

Referencing Class

Signalling Class


  • RFC 7208 Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
  • RFC 7489 Domain-based Message Authentication, Reporting, and Conformance (DMARC)
  • RFC 6376 DomainKeys Identified Mail (DKIM) Signatures
  • RFC 7672 SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) (generic DANE on wikipedia)


  • RFC 4918 HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
  • RFC 5545 Internet Calendaring and Scheduling Core Object Specification – (iCalendar)
  • RFC 4791 Calendaring Extensions to WebDAV (CalDAV)
  • RFC 6352 CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)


  • RFC 3261 SIP: Session Initiation Protocol
  • RFC 6189 ZRTP: Media Path Key Agreement for Unicast Secure RTP



Special Class

  • STD 63/RFC 3629 UTF-8, a transformation format of ISO 10646
  • RFC 3339 Date and Time on the Internet: Timestamps (subset/profile of ISO 8601)
  • RFC 6238 TOTP: Time-Based One-Time Password Algorithm
  • RFC 4226 HOTP: An HMAC-Based One-Time Password Algorthm
  • RFC 4287 The Atom Syndication Format
  • RFC 4180 Common Format and MIME Type for Comma-Separated Values (CSV) Files
  • STD 68/RFC 5234 Augmented BNF for Syntax Specifications: ABNF



Comments are closed

»  Substance:WordPress   »  Style:Ahren Ahimsa
© 2023 Mikkel Kirkgaard Nielsen, contents CC BY-SA 4.0