Mapping to ATM classes of service for Differentiated Services Architecture
draft-ayandeh-diffserv-atm-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Andrew G. Malis , Siamack Ayandeh , Anand Krishnamurthy | ||
Last updated | 1999-10-19 | ||
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 guidelines for PHB specifications contained in the Differentiated Services (DS) Architecture [1] require descriptions of: 1. How a PHB would map to different link layers 2. How a PHB would inter-work with non-DS compliant nodes and networks This draft includes the mapping to ATM classes of service for EF [2] and AF PHBs [3].
Authors
Andrew G. Malis
Siamack Ayandeh
Anand Krishnamurthy
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)