MLEF Without Capacity Admission Does Not Satisfy MLPP Requirements
draft-ietf-tsvwg-mlef-concerns-00
| Document | Type | Expired Internet-Draft (tsvwg WG) | |
|---|---|---|---|
| Last updated | 2005-02-09 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-tsvwg-mlef-concerns-00.txt
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
Fred Baker
(fred.baker@cisco.com)
James Polk
(jmpolk@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)