Skip to main content

4.8. IETF Review

4.8. IETF Review​

(Formerly called "IETF Consensus" in the first edition of this document.) With the IETF Review policy, new values are assigned only through RFCs in the IETF Stream -- those that have been shepherded through the IESG as AD-Sponsored or IETF working group documents [RFC2026] [RFC5378], have gone through IETF Last Call, and have been approved by the IESG as having IETF consensus.

The intent is that the document and proposed assignment will be reviewed by the IETF community (including appropriate IETF working groups, directorates, and other experts) and by the IESG, to ensure that the proposed assignment will not negatively affect interoperability or otherwise extend IETF protocols in an inappropriate or damaging manner.

Unless otherwise specified, any type of RFC is sufficient (currently Standards Track, BCP, Informational, Experimental, or Historic).

Examples:

  • IPSECKEY Algorithm Types [RFC4025]
  • TLS Extension Types [RFC5246]
Last updated on