MPLS-TP Next-Hop Ethernet Addressing
draft-ietf-mpls-tp-ethernet-addressing-07

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-04-28 (latest revision 2013-04-08)
Replaces draft-fbb-mpls-tp-ethernet-addressing
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Yes
Document shepherd None
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Telechat date
Responsible AD Adrian Farrel
IESG note Loa Andersson (loa@pi.nu) is the document shepherd.
Send notices to mpls-chairs@tools.ietf.org, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
MPLS                                                            D. Frost
Internet-Draft                                                 S. Bryant
Intended status: Standards Track                           Cisco Systems
Expires: October 10, 2013                                       M. Bocci
                                                          Alcatel-Lucent
                                                          April 08, 2013

                  MPLS-TP Next-Hop Ethernet Addressing
               draft-ietf-mpls-tp-ethernet-addressing-07

Abstract

   The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP)
   is the set of MPLS protocol functions applicable to the construction
   and operation of packet-switched transport networks.  This document
   presents considerations for link-layer addressing of Ethernet frames
   carrying MPLS-TP packets.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 10, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Frost, et al.           Expires October 10, 2013                [Page 1]
Internet-Draft        MPLS-TP Ethernet Addressing             April 2013

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of protocol
   functions that meet the requirements [RFC5654] for the application of
   MPLS to the construction and operation of packet-switched transport
   networks.  The MPLS-TP data plane consists of those MPLS-TP functions
   concerned with the encapsulation and forwarding of MPLS-TP packets
   and is described in [RFC5960].

   This document presents considerations for link-layer addressing of
   Ethernet frames carrying MPLS-TP packets.  Since MPLS-TP packets are
   MPLS packets, existing procedures ([RFC3032], [RFC5332]) for the
   encapsulation of MPLS packets over Ethernet apply.  Because IP
   functionality is only optional in an MPLS-TP network, IP-based
   protocols for Media Access Control (MAC) address learning, such as
   the Address Resolution Protocol (ARP) [RFC0826] and IP version 6
   Neighbor Discovery [RFC4861], may not be available.  This document
   specifies the options for the determination and selection of the
   next-hop Ethernet MAC address when MPLS-TP is used between nodes that
   do not have an IP dataplane.

1.1.  Terminology

   Term    Definition
   ------- ---------------------------
   ARP     Address Resolution Protocol
   G-ACh   Generic Associated Channel
   LSP     Label Switched Path
   LSR     Label Switching Router
   MAC     Media Access Control
   MPLS-TP MPLS Transport Profile

   Additional definitions and terminology can be found in [RFC5960] and
   [RFC5654].

1.2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Point-to-Point Link Addressing

Frost, et al.           Expires October 10, 2013                [Page 2]
Internet-Draft        MPLS-TP Ethernet Addressing             April 2013

   When two MPLS-TP nodes are connected by a point-to-point Ethernet
   link, the question arises as to what destination Ethernet Media
   Access Control (MAC) address should be specified in Ethernet frames
   transmitted to the peer node over the link.  The problem of
Show full document text