draft-ietf-lisp-lcaf-12.txt   draft-ietf-lisp-lcaf-13.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft lispers.net Internet-Draft lispers.net
Intended status: Experimental D. Meyer Intended status: Experimental D. Meyer
Expires: September 15, 2016 Brocade Expires: November 4, 2016 Brocade
J. Snijders J. Snijders
NTT Communications NTT Communications
March 14, 2016 May 3, 2016
LISP Canonical Address Format (LCAF) LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-12 draft-ietf-lisp-lcaf-13
Abstract Abstract
This draft defines a canonical address format encoding used in LISP This draft defines a canonical address format encoding used in LISP
control messages and in the encoding of lookup keys for the LISP control messages and in the encoding of lookup keys for the LISP
Mapping Database System. Mapping Database System.
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 35 skipping to change at page 1, line 35
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 September 15, 2016. This Internet-Draft will expire on November 4, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 30 5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 30
5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 31 5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 31
5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 32 5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 32
6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1. Normative References . . . . . . . . . . . . . . . . . . 35 8.1. Normative References . . . . . . . . . . . . . . . . . . 35
8.2. Informative References . . . . . . . . . . . . . . . . . 36 8.2. Informative References . . . . . . . . . . . . . . . . . 36
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 38 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 38
B.1. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 38 B.1. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 38
B.2. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 38 B.2. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 38
B.3. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 38 B.3. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 38
B.4. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 38 B.4. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 38
B.5. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 39 B.5. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 39
B.6. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 39 B.6. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 39
B.7. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 39 B.7. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 39
B.8. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 39 B.8. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 39
B.9. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 39 B.9. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 39
B.10. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 39 B.10. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 39
B.11. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 40 B.11. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 40
B.12. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 40 B.12. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 40
B.13. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 40 B.13. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 40
B.14. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which are intended to replace most use of IP addresses on the (RLOCs) which are intended to replace most use of IP addresses on the
Internet. To provide flexibility for current and future Internet. To provide flexibility for current and future
applications, these values can be encoded in LISP control messages applications, these values can be encoded in LISP control messages
using a general syntax that includes Address Family Identifier (AFI), using a general syntax that includes Address Family Identifier (AFI),
skipping to change at page 7, line 42 skipping to change at page 7, line 42
IID mask-len: if the AFI is set to 0, then this format is not IID mask-len: if the AFI is set to 0, then this format is not
encoding an extended EID-prefix but rather an instance-ID range encoding an extended EID-prefix but rather an instance-ID range
where the 'IID mask-len' indicates the number of high-order bits where the 'IID mask-len' indicates the number of high-order bits
used in the Instance ID field for the range. used in the Instance ID field for the range.
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
Instance ID field including the AFI field itself. Instance ID field including the AFI field itself.
Instance ID: the low-order 24-bits that can go into a LISP data Instance ID: the low-order 24-bits that can go into a LISP data
header when the I-bit is set. See [RFC6830] for details. header when the I-bit is set. See [RFC6830] for details. The
reason for the length difference is so the maximum number of
instances supported per mapping system is 2^32 while conserving
space in the LISP data header. This comes at the expense of
limiting the maximum number of instances per xTR to 2^24. If an
xTR is configured with multiple instance-IDs where the value in
the high-order 8 bits are the same, then the low-order 24 bits
MUST be unique.
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
This LISP Canonical Address Type can be used to encode either EID or This LISP Canonical Address Type can be used to encode either EID or
RLOC addresses. RLOC addresses.
Usage: When used as a lookup key, the EID is regarded as a extended- Usage: When used as a lookup key, the EID is regarded as a extended-
EID in the mapping system. And this encoding is used in EID records EID in the mapping system. And this encoding is used in EID records
in Map-Requests, Map-Replies, Map-Registers, and Map-Notify messages. in Map-Requests, Map-Replies, Map-Registers, and Map-Notify messages.
When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, When LISP-DDT [LISP-DDT] is used as the mapping system mechanism,
extended EIDs are used in Map-Referral messages. extended EIDs are used in Map-Referral messages.
4.2. Carrying AS Numbers in the Mapping Database 4.2. Carrying AS Numbers in the Mapping Database
When an AS number is stored in the LISP Mapping Database System for When an AS number is stored in the LISP Mapping Database System for
either policy or documentation reasons, it can be encoded in a LISP either policy or documentation reasons, it can be encoded in a LISP
Canonical Address. Canonical Address.
AS Number LISP Canonical Address Format: AS Number LISP Canonical Address Format:
skipping to change at page 38, line 17 skipping to change at page 38, line 17
List Entry LCAF type. List Entry LCAF type.
Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for
suggesting new LCAF types. suggesting new LCAF types.
Thanks also goes to Terry Manderson for assistance obtaining a LISP Thanks also goes to Terry Manderson for assistance obtaining a LISP
AFI value from IANA. AFI value from IANA.
Appendix B. Document Change Log Appendix B. Document Change Log
B.1. Changes to draft-ietf-lisp-lcaf-12.txt B.1. Changes to draft-ietf-lisp-lcaf-13.txt
o Submitted May 2016.
o Explain the Instance-ID LCAF Type is 32-bits in length and the
Instance-ID field in the LISP encapsulation header is 24-bits.
B.2. Changes to draft-ietf-lisp-lcaf-12.txt
o Submitted March 2016. o Submitted March 2016.
o Updated references and document timer. o Updated references and document timer.
o Removed the R, J, and L bits from the Multicast Info Type LCAF o Removed the R, J, and L bits from the Multicast Info Type LCAF
since working group decided to not go forward with draft- since working group decided to not go forward with draft-
farinacci-lisp-mr-signaling-03.txt in favor of draft- ietf-lisp- farinacci-lisp-mr-signaling-03.txt in favor of draft- ietf-lisp-
signal-free-00.txt. signal-free-00.txt.
B.2. Changes to draft-ietf-lisp-lcaf-11.txt B.3. Changes to draft-ietf-lisp-lcaf-11.txt
o Submitted September 2015. o Submitted September 2015.
o Reflecting comments from Prague LISP working group. o Reflecting comments from Prague LISP working group.
o Readying document for a LISP LCAF registry, RFC publication, and o Readying document for a LISP LCAF registry, RFC publication, and
for new use-cases that will be defined in the new charter. for new use-cases that will be defined in the new charter.
B.3. Changes to draft-ietf-lisp-lcaf-10.txt B.4. Changes to draft-ietf-lisp-lcaf-10.txt
o Submitted June 2015. o Submitted June 2015.
o Fix coauthor Job's contact information. o Fix coauthor Job's contact information.
B.4. Changes to draft-ietf-lisp-lcaf-09.txt B.5. Changes to draft-ietf-lisp-lcaf-09.txt
o Submitted June 2015. o Submitted June 2015.
o Fix IANA Considerations section to request a registry to allocate o Fix IANA Considerations section to request a registry to allocate
and track LCAF Type values. and track LCAF Type values.
B.5. Changes to draft-ietf-lisp-lcaf-08.txt B.6. Changes to draft-ietf-lisp-lcaf-08.txt
o Submitted April 2015. o Submitted April 2015.
o Comment from Florin. The Application Data Type length field has a o Comment from Florin. The Application Data Type length field has a
typo. The field should be labeled "12 + n" and not "8 + n". typo. The field should be labeled "12 + n" and not "8 + n".
o Fix length fields in the sections titled "Using Recursive LISP o Fix length fields in the sections titled "Using Recursive LISP
Canonical Address Encodings", "Generic Database Mapping Lookups", Canonical Address Encodings", "Generic Database Mapping Lookups",
and "Data Model Encoding". and "Data Model Encoding".
B.6. Changes to draft-ietf-lisp-lcaf-07.txt B.7. Changes to draft-ietf-lisp-lcaf-07.txt
o Submitted December 2014. o Submitted December 2014.
o Add a new LCAF Type called "Encapsulation Format" so decapsulating o Add a new LCAF Type called "Encapsulation Format" so decapsulating
xTRs can inform encapsulating xTRs what data-plane encapsulations xTRs can inform encapsulating xTRs what data-plane encapsulations
they support. they support.
B.7. Changes to draft-ietf-lisp-lcaf-06.txt B.8. Changes to draft-ietf-lisp-lcaf-06.txt
o Submitted October 2014. o Submitted October 2014.
o Make it clear how sorted RLOC records are done when LCAFs are used o Make it clear how sorted RLOC records are done when LCAFs are used
as the RLOC record. as the RLOC record.
B.8. Changes to draft-ietf-lisp-lcaf-05.txt B.9. Changes to draft-ietf-lisp-lcaf-05.txt
o Submitted May 2014. o Submitted May 2014.
o Add a length field of the JSON payload that can be used for either o Add a length field of the JSON payload that can be used for either
binary or text encoding of JSON data. binary or text encoding of JSON data.
B.9. Changes to draft-ietf-lisp-lcaf-04.txt B.10. Changes to draft-ietf-lisp-lcaf-04.txt
o Submitted January 2014. o Submitted January 2014.
o Agreement among ELP implementors to have the AFI 16-bit field o Agreement among ELP implementors to have the AFI 16-bit field
adjacent to the address. This will make the encoding consistent adjacent to the address. This will make the encoding consistent
with all other LCAF type address encodings. with all other LCAF type address encodings.
B.10. Changes to draft-ietf-lisp-lcaf-03.txt B.11. Changes to draft-ietf-lisp-lcaf-03.txt
o Submitted September 2013. o Submitted September 2013.
o Updated references and author's affilations. o Updated references and author's affilations.
o Added Instance-ID to the Multicast Info Type so there is relative o Added Instance-ID to the Multicast Info Type so there is relative
ease in parsing (S,G) entries within a VPN. ease in parsing (S,G) entries within a VPN.
o Add port range encodings to the Application Data LCAF Type. o Add port range encodings to the Application Data LCAF Type.
o Add a new JSON LCAF Type. o Add a new JSON LCAF Type.
o Add Address Key/Value LCAF Type to allow attributes to be attached o Add Address Key/Value LCAF Type to allow attributes to be attached
to an address. to an address.
B.11. Changes to draft-ietf-lisp-lcaf-02.txt B.12. Changes to draft-ietf-lisp-lcaf-02.txt
o Submitted March 2013. o Submitted March 2013.
o Added new LCAF Type "Replication List Entry" to support LISP o Added new LCAF Type "Replication List Entry" to support LISP
replication engineering use-cases. replication engineering use-cases.
o Changed references to new LISP RFCs. o Changed references to new LISP RFCs.
B.12. Changes to draft-ietf-lisp-lcaf-01.txt B.13. Changes to draft-ietf-lisp-lcaf-01.txt
o Submitted January 2013. o Submitted January 2013.
o Change longitude range from 0-90 to 0-180 in section 4.4. o Change longitude range from 0-90 to 0-180 in section 4.4.
o Added reference to WGS-84 in section 4.4. o Added reference to WGS-84 in section 4.4.
B.13. Changes to draft-ietf-lisp-lcaf-00.txt B.14. Changes to draft-ietf-lisp-lcaf-00.txt
o Posted first working group draft August 2012. o Posted first working group draft August 2012.
o This draft was renamed from draft-farinacci-lisp-lcaf-10.txt. o This draft was renamed from draft-farinacci-lisp-lcaf-10.txt.
Authors' Addresses Authors' Addresses
Dino Farinacci Dino Farinacci
lispers.net lispers.net
San Jose, CA San Jose, CA
 End of changes. 20 change blocks. 
32 lines changed or deleted 46 lines changed or added

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