L2TP Session Update Mechanism
draft-naveen-l2tpext-sessupdate-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Naveen Gowda , Elwin Stelzer , Umesh Sirsiwal | ||
| Last updated | 2001-06-11 | ||
| 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
Once a L2TP session is established, the current standard [RFC 2661] has no explicit mechanism to update the session characteristics, during the life of the session, between the L2TP tunnel endpoints. One such requirement for this mechanism is, LNS informing LAC about the PPP-user's service characteristics, so that user-specific service actions can be applied at LAC. Eg: DSCP marking. There is a need for additional messages that will address similar requirements. Two additional messages are defined in this draft for this.
Authors
Naveen Gowda
Elwin Stelzer
Umesh Sirsiwal
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)