ARP Mediation for IP interworking of Layer 2 VPN
draft-shah-ppvpn-arp-mediation-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Himanshu C. Shah | ||
| Last updated | 2003-07-01 | ||
| Replaced by | draft-shah-l2vpn-arp-mediation | ||
| 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-shah-l2vpn-arp-mediation | |
| 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 VPWS service [L2VPN Framework] provides point-to-point connections between pairs of Customer Edge (CE) devices. It does so by binding two Attachment Circuits (each connecting a CE device with a Provider Edge, PE, device) to a Pseudowire (connecting the two PEs). In general, the Attachment Circuits must be of the same technology (e.g., both ethernet, both ATM), and the Pseudowire must carry the frames of that technology. However, if it is known that the frames' payload consists solely of IP datagrams, it is possible to provide a point-to-point connection in which the Pseudowire connects Attachment Circuits of different technologies. This requires the PEs to perform a function known as 'ARP Mediation'. This document specifies the ARP Mediation function, and specifies draft-shah-l2vpn-arp-mediation-03.txt the encapsulation used to carry the IP datagrams on the Pseudowires when ARP mediation is used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)