Framework for L2TP Message Extensions
draft-ietf-pppext-l2tpmsgext-00
| Document | Type |
Expired Internet-Draft
(pppext WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard Shea | ||
| Last updated | 1998-11-17 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | 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 Layer Two Tunneling Protocol (L2TP) defines mechanisms for extensibility. The mechanisms provided are for Attribute-Value Pair (AVP) fields received in control messages to be set as Mandatory or not. This document specifies a mechanism whereby an L2TP implementation can signal its support of the set of L2TP extensions that it supports. This then allows the L2TP implementations to use extensions such as L2TP message types not defined in [1], the presence of existing AVPs in messages they are not currently defined to be in, and the definition of new AVPs that can be marked as Mandatory, beyond those defined in [1].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)