Suggested process changes for handling new SIP headers and SIP responses
draft-drage-rai-sip-header-process-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Keith Drage | ||
| Last updated | 2008-07-07 | ||
| 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
RFC 3427 currently defines the process for defining and registering new SIP header fields. This document proposes that prefixs to header field names should be discontinued, and that an additional category of experimental header field should be created. This document also relaxes the requirement that response codes are defined by standards track RFCs, also allowing them to be defined by experimental RFCs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)