Guidelines for Writing an IANA Considerations Section in RFCs

Narten, Thomas; Alvestrand, Harald

doi:10.17487/rfc5226

Cited by 309 publications

(152 citation statements)

References 9 publications

Supporting

Mentioning

152

Contrasting

Order By: Relevance

“…It has been created and is now maintained at <http://www.iana.org/assignments/http-warn-codes>. Values to be added to this namespace require IETF Review (see [RFC5226], Section 4.1).…”

Section: Warn Code Registrymentioning

confidence: 99%

Hypertext Transfer Protocol (HTTP/1.1): Caching

2014

View full text Add to dashboard Cite

show abstract

“…It has been created and is now maintained at <http://www.iana.org/assignments/http-warn-codes>. Values to be added to this namespace require IETF Review (see [RFC5226], Section 4.1).…”

Section: Warn Code Registrymentioning

confidence: 99%

Hypertext Transfer Protocol (HTTP/1.1): Caching

2014

View full text Add to dashboard Cite

show abstract

“…The "TLS Certificate Status Types" registry has been created under the "Transport Layer Security (TLS) Extensions" registry. CertificateStatusType values are to be assigned via IETF Review as defined in [RFC5226]. The initial registry corresponds to the definition of "CertificateStatusType" in Section 2.2.…”

Section: Iana Considerationsmentioning

confidence: 99%

The Transport Layer Security (TLS) Multiple Certificate Status Request Extension

Pettersen¹

2013

View full text Add to dashboard Cite

“…Use of this naming convention is not mandated by the Internet Standards Process [BCP9] or IANA registration rules [BCP26]. Rather, it is an individual choice by each specification that references the convention or each administrative process that chooses to use it.…”

Section: Appendix a Backgroundmentioning

confidence: 99%