Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.
Please enable Javascript for full functionality.
Design Considerations for Protocol Extensions
draft-carpenter-extension-recs-04
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|---|---|---|
| Authors | Dr. Bernard D. Aboba , Brian E. Carpenter | |
| Last updated | 2008年10月27日 | |
| RFC stream | (None) | |
| Intended RFC status | (None) | |
| Formats | ||
| Stream | Stream state | (No stream defined) |
| Consensus boilerplate | Unknown | |
| RFC Editor Note | (None) | |
| IESG | IESG state | Expired |
| Telechat date | (None) | |
| Responsible AD | (None) | |
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses issues related to the extensibility of Internet protocols, with a focus on the architectural design considerations involved. Concrete case study examples are included. It is intended to assist designers of both base protocols and extensions.
Authors
Dr. Bernard D. Aboba
Brian E. Carpenter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)