Considerations on the Extensibility of IETF protocols
draft-iesg-vendor-extensions-02

Document Type Expired Internet-Draft - resurrect requested by Alex Zinin
Last updated 2007-01-15 (latest revision 2004-06-07)
Stream IETF
Intended RFC status Best Current Practice
Formats
Expired & archived
plain text pdf html
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Telechat date
Responsible AD Brian Carpenter
IESG note Replaced by draft-carpenter-protocol-extensions published as RFC 4775.
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-iesg-vendor-extensions-02.txt

Abstract

This document discusses 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 need to be reviewed by the larger IETF community. The document also recommends that major extensions to IETF protocols only take place through normal IETF processes or in coordination with the IETF.

Authors

Scott Bradner (sob@harvard.edu)
Thomas Narten (narten@us.ibm.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)