Vendor Specific LISP Canonical Address Format (LCAF)
draft-ietf-lisp-vendor-lcaf-06
LISP Working Group A. Rodriguez-Natal
Internet-Draft Cisco Systems
Intended status: Experimental V. Ermagan
Expires: October 4, 2020 Google
A. Smirnov
V. Ashtaputre
Cisco Systems
D. Farinacci
lispers.net
April 2, 2020
Vendor Specific LISP Canonical Address Format (LCAF)
draft-ietf-lisp-vendor-lcaf-06
Abstract
This document describes a new LISP Canonical Address Format (LCAF),
the Vendor Specific LCAF. This LCAF enables organizations to have
internal encodings for LCAF addresses.
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 October 4, 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
Rodriguez-Natal, et al. Expires October 4, 2020 [Page 1]
Internet-Draft LISP-Vendor-LCAF April 2020
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 2
3. Vendor Specific LCAF . . . . . . . . . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The LISP Canonical Address Format (LCAF) [RFC8060] defines the format
and encoding for different address types that can be used on LISP
[I-D.ietf-lisp-rfc6830bis] [I-D.ietf-lisp-rfc6833bis] deployments.
However, certain deployments require specific format encodings that
may not be applicable outside of the use-case for which they are
defined. The Vendor Specific LCAF allows organizations to create
LCAF addresses to be used only internally on particular LISP
deployments.
2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Vendor Specific LCAF
The Vendor Specific LCAF relies on using the IEEE Organizationally
Unique Identifier (OUI) [IEEE.802_2001] to prevent collisions across
vendors or organizations using the LCAF. The format of the Vendor
Specific LCAF is provided below.
Rodriguez-Natal, et al. Expires October 4, 2020 [Page 2]
Internet-Draft LISP-Vendor-LCAF April 2020
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 255 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Show full document text