Layer-3 Extensions to DLEP
draft-taylor-manet-l3-dlep-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rick Taylor , John Dowdell | ||
| Last updated | 2015-01-01 (Latest revision 2014-06-30) | ||
| Replaced by | draft-dlep-lid | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-dlep-lid | |
| 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
There exists a class of devices where DLEP functionality is desired but as the devices operate at layer-3, supporting the core DLEP specification with its requirement that modems operate as transparent layer-2 bridges is inappropriate. This document introduces two optional extensions to the core DLEP specification. Each extension may be used in isolation without breaking backwards compatibility. By relaxing the requirement that all DLEP destinations be identified by MAC address, and the addition of a new extension TLV describing available destination routes, the functionality of DLEP can be implemented by layer-3 forwarding devices. Note: o This document is intended as an extension to the core DLEP specification, and readers are expected to be fully conversant with the operation of core DLEP. o The DLEP specification is still in draft, and this document serves a secondary purpose to explore and validate the extension mechanisms detailed in DLEP. This document will therefore require further update as the core DLEP draft progresses towards standards track.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)