datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs
draft-ietf-l2vpn-arp-mediation-19

RFC
Document Stream: IETF
Last updated: 2012-01-12
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (l2vpn)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6575
IANA Action State: RFC-Ed-Ack 
Responsible AD: Stewart Bryant
IESG Note: Document Shepherd: Nabil Bitar, nabil.n.bitar@verizon.com
Send notices to: l2vpn-chairs@tools.ietf.org, draft-ietf-l2vpn-arp-mediation@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-l2vpn-arp-mediation.

Abstract:
The Virtual Private Wire Service (VPWS), detailed in RFC 4664, 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 or 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 "Address Resolution Protocol (ARP) Mediation". ARP Mediation refers to the process of resolving Layer 2 addresses when different resolution protocols are used on either Attachment Circuit. The methods described in this document are applicable even when the CEs run a routing protocol between them, as long as the routing protocol runs over IP. [STANDARDS-TRACK]

Authors:
Himanshu Shah <hshah@ciena.com>
Giles Heron <giheron@cisco.com>
Vach Kompella <vach.kompella@alcatel-lucent.com>
Eric Rosen <erosen@cisco.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)