Label Distribution Using ARP
draft-kompella-mpls-larp-07
|
| Document |
Type |
|
Active Internet-Draft (mpls WG)
|
|
Last updated |
|
2020-03-07
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
Candidate for WG Adoption
|
|
Document shepherd |
|
Loa Andersson
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
MPLS Working Group K. Kompella
Internet-Draft R. Balaji
Intended status: Standards Track R. Thomas
Expires: September 8, 2020 Juniper Networks
March 07, 2020
Label Distribution Using ARP
draft-kompella-mpls-larp-07
Abstract
This document describes extensions to the Address Resolution Protocol
to distribute MPLS labels for IPv4 and IPv6 host addresses.
Distribution of labels via ARP enables simple plug-and-play operation
of MPLS, which is key to deploying MPLS in data centers and
enterprises.
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 https://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 September 8, 2020.
Copyright Notice
Copyright (c) 2020 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
(https://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
Kompella, et al. Expires September 8, 2020 [Page 1]
Internet-Draft L-ARP March 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
1.2. Approach . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview of Ethernet ARP . . . . . . . . . . . . . . . . . . 3
3. L-ARP Protocol Operation . . . . . . . . . . . . . . . . . . 4
3.1. Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Egress Operation . . . . . . . . . . . . . . . . . . . . 5
3.3. Ingress Operation . . . . . . . . . . . . . . . . . . . . 5
3.4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . 6
4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. L-ARP Message Format . . . . . . . . . . . . . . . . . . . . 7
5.1. Hardware Address Format . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document describes extensions to the Address Resolution Protocol
(ARP) [RFC0826] to advertise label bindings for IP host addresses.
While there are well-established protocols, such as LDP, RSVP and
BGP, that provide robust mechanisms for label distribution, these
protocols tend to be relatively complex, and often require detailed
configuration for proper operation. There are situations where a
simpler protocol may be more suitable from an operational standpoint.
An example is the case where an MPLS Fabric is the underlay
technology in a Data Center; here, MPLS tunnels originate from host
machines. The host thus needs a mechanism to acquire label bindings
to participate in the MPLS Fabric, but in a simple, plug-and-play
manner. Existing signaling/routing protocols do not always meet this
need. Labeled ARP (L-ARP) is a proposal to fill that gap.
1.1. 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].
Kompella, et al. Expires September 8, 2020 [Page 2]
Internet-Draft L-ARP March 2020
Show full document text