Considerations on the IEPREP requirements for SIP
draft-peterson-sipping-ieprep-00
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
|
|
|---|---|---|---|
| Author | Jon Peterson | ||
| Last updated | 2003-02-26 | ||
| 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
The IEPREP working group has provided the SIPPING WG with a framework and requirements draft for prioritized communications services in SIP. The considerations raised in that draft are examined here, and some feedback and implementation recommendations based on its requirements are provided.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)