Differentiated Services on L2TP Sessions
draft-elwin-l2tpext-diffserv-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Elwin Stelzer , Naveen Gowda | ||
| Last updated | 2001-04-09 | ||
| 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
L2TP provides layer-2 tunneling over long distances, and a single L2TP session is likely to carry different type of IP packets. Currently, one L2TP session carries only one payload session; for PPP session (payload) the LCP controls the corresponding L2TP session. Assigning one diffserv code point to a L2TP session, as mentioned in [ref-6] can not provide differentiated services for the different kind of IP packets that are tunneled. For example, VoIP and FTP packets, will have to be treated the same in the backbone, even though the intermediate nodes are diffserv capable.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)