MLEF Without Capacity Admission Does Not Satisfy MLPP Requirements
draft-ietf-tsvwg-mlef-concerns-00
Document | Type |
Expired Internet-Draft
(tsvwg WG)
Expired & archived
|
|
---|---|---|---|
Authors | Fred Baker , James Polk | ||
Last updated | 2023-03-01 (Latest revision 2005-02-09) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Dead WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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 Defense Information Systems Agency of the United States Department of Defense, with its contractors, has proposed a service architecture for military (NATO and related agencies) telephone systems. This is called the Assured Service, and is defined in two documents: "Architecture for Assured Service Capabilities in Voice over IP" and "Requirements for Assured Service Capabilities in Voice over IP". Responding to these are three documents: "Extending the Session Initiation Protocol Reason Header to account for Preemption Events", "Communications Resource Priority for the Session Initiation Protocol", and the "Multi-Level Expedited Forwarding Per Hop Behavior" (MLEF PHB). MLEF, as currently defined, has serious problems, which this draft seeks to discuss.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)