Procedures for Protocol Extensions and Variations
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: Internet Architecture Board <firstname.lastname@example.org>, RFC Editor <email@example.com> Subject: Protocol Action: 'Procedures for protocol extensions and variations' to BCP The IESG has approved the following document: - 'Procedures for protocol extensions and variations ' <draft-carpenter-protocol-extensions-05.txt> as a BCP This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Ross Callon. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-carpenter-protocol-extensions-05.txt
Technical Summary 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 larger IETF community. Working Group Summary No dissent reported. Protocol Quality The author is of course chair of the IESG, and Ross Callon has also reviewed this for the IESG. However, due to the fact that this discusses procedural issues that could affect a wide variety of IETF documents, I think that the all IESG members should review this carefully and individually.