draft-ietf-lisp-vendor-lcaf-05.txt   draft-ietf-lisp-vendor-lcaf-06.txt 
LISP Working Group A. Rodriguez-Natal LISP Working Group A. Rodriguez-Natal
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Experimental V. Ermagan Intended status: Experimental V. Ermagan
Expires: April 1, 2020 Google Expires: October 4, 2020 Google
A. Smirnov A. Smirnov
V. Ashtaputre V. Ashtaputre
Cisco Systems Cisco Systems
D. Farinacci D. Farinacci
lispers.net lispers.net
September 29, 2019 April 2, 2020
Vendor Specific LISP Canonical Address Format (LCAF) Vendor Specific LISP Canonical Address Format (LCAF)
draft-ietf-lisp-vendor-lcaf-05 draft-ietf-lisp-vendor-lcaf-06
Abstract Abstract
This document describes a new LISP Canonical Address Format (LCAF), This document describes a new LISP Canonical Address Format (LCAF),
the Vendor Specific LCAF. This LCAF enables organizations to have the Vendor Specific LCAF. This LCAF enables organizations to have
internal encodings for LCAF addresses. internal encodings for LCAF addresses.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 1, 2020. This Internet-Draft will expire on October 4, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 16 skipping to change at page 4, line 16
The authors would like to thank Joel Halpern and Luigi Iannone for The authors would like to thank Joel Halpern and Luigi Iannone for
their suggestions and guidance regarding this document. their suggestions and guidance regarding this document.
6. IANA Considerations 6. IANA Considerations
Following the guidelines of [RFC8126], this document requests IANA to Following the guidelines of [RFC8126], this document requests IANA to
update the "LISP Canonical Address Format (LCAF) Types" Registry update the "LISP Canonical Address Format (LCAF) Types" Registry
defined in [RFC8060] to allocate the following assignment: defined in [RFC8060] to allocate the following assignment:
+---------+---------------------+------------+ +---------+---------------------+-------------------------------+
| Value # | LISP LCAF Type Name | Reference | | Value # | LISP LCAF Type Name | Reference |
+---------+---------------------+------------+ +---------+---------------------+-------------------------------+
| 255 | Vendor Specific | Section 3 | | 255 | Vendor Specific | Section 3 |
+---------+---------------------+------------+ +---------+---------------------+-------------------------------+
Table 1: Vendor Specific LCAF assignment Table 1: Vendor Specific LCAF assignment
7. Normative References 7. Normative References
[I-D.ietf-lisp-rfc6830bis] [I-D.ietf-lisp-rfc6830bis]
Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
Cabellos-Aparicio, "The Locator/ID Separation Protocol Cabellos-Aparicio, "The Locator/ID Separation Protocol
(LISP)", draft-ietf-lisp-rfc6830bis-27 (work in progress), (LISP)", draft-ietf-lisp-rfc6830bis-32 (work in progress),
June 2019. March 2020.
[I-D.ietf-lisp-rfc6833bis] [I-D.ietf-lisp-rfc6833bis]
Farinacci, D., Maino, F., Fuller, V., and A. Cabellos- Farinacci, D., Maino, F., Fuller, V., and A. Cabellos-
Aparicio, "Locator/ID Separation Protocol (LISP) Control- Aparicio, "Locator/ID Separation Protocol (LISP) Control-
Plane", draft-ietf-lisp-rfc6833bis-25 (work in progress), Plane", draft-ietf-lisp-rfc6833bis-27 (work in progress),
June 2019. January 2020.
[IEEE.802_2001] [IEEE.802_2001]
IEEE, "IEEE Standard for Local and Metropolitan Area IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE 802-2001, Networks: Overview and Architecture", IEEE 802-2001,
DOI 10.1109/ieeestd.2002.93395, July 2002, DOI 10.1109/ieeestd.2002.93395, July 2002,
<http://ieeexplore.ieee.org/servlet/opac?punumber=7732>. <http://ieeexplore.ieee.org/servlet/opac?punumber=7732>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
 End of changes. 8 change blocks. 
14 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/