Use of ARP and Flood Routing Technique for LSP setup in ECPN
draft-jaihyung-ccamp-arpsignal-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jaihyung Cho | ||
| Last updated | 2005-02-01 | ||
| 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
In this memo, we first discuss some weaknesses of proposals employing RSVP in local network, such as RFC2814, 2815, 2816, and propose extension of ARP (Address Resolution Protocol) and [LSE] technique for solution to provide QoS in Ethernet based Customer Premise Network (ECPN). Framework architecture of LSE (Label Switched Ethernet) as a method of GMPLS implementation for Ethernet is described in [LSE]. ARP is proposed for integrated signaling and routing protocol in ECPN. This document describes overview of ARP extension, procedure for label negotiation and method for QoS routing. Major features of this ARP extension are; support for label switching, incorporation of routing function, compatibility with legacy Ethernet and enhanced security.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)