Extensions to Layer 2 Relay Agent
draft-ietf-dhc-l2ra-extensions-01
| Document | Type |
Expired Internet-Draft
(dhc WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bharat Joshi , Stefaan De Cnodder , Mukund Kamath , Pavan Kurapati | ||
| Last updated | 2009-02-25 | ||
| Replaces | draft-kurapati-dhc-l2ra-extensions | ||
| 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
As per industry trends, Access Networks have been migrating from traditional ATM based networks to Ethernet networks. In Ethernet based access networks, Access Concentrators are typically configured to act as a transparent bridge in Layer 2 mode. These Access Concentrators also act as Layer 2 relay agents. Layer 2 Relay Agent functionality does not provide means to avoid flooding of DHCP messages and also needs to be extended to support DHCP LeaseQuery This draft discusses these issues and provides solutions for the same.
Authors
Bharat Joshi
Stefaan De Cnodder
Mukund Kamath
Pavan Kurapati
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)