Skip to main content

Procedures for Protocol Extensions and Variations
RFC 4775 also known as BCP 125

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc4775 in bcp125 via sync to the rfc-index
2023-12-12
(System) No history of BCP125 is currently available in the datatracker before this point
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document discusses procedural issues related to the extensibility of IETF protocols, including when it is …
Received changes through RFC Editor sync (changed abstract to 'This document discusses procedural issues related to the extensibility of IETF protocols, including when it is reasonable to extend IETF protocols with little or no review, and when extensions or variations need to be reviewed by the IETF community. Experience has shown that extension of protocols without early IETF review can carry risk. The document also recommends that major extensions to or variations of IETF protocols only take place through normal IETF processes or in coordination with the IETF.

This document is directed principally at other Standards Development Organizations (SDOs) and vendors considering requirements for extensions to IETF protocols. It does not modify formal IETF processes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.')
2015-10-14
(System) Notify list changed from brc@zurich.ibm.com, sob@harvard.edu to (None)
2007-01-02
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2007-01-02
Amy Vezza [Note]: 'RFC 4775
BCP 125' added by Amy Vezza
2006-12-13
(System) RFC published