draft-ietf-lisp-lcaf-09.txt   draft-ietf-lisp-lcaf-10.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: December 14, 2015 Brocade Expires: December 14, 2015 Brocade
J. Snijders J. Snijders
NTT NTT Communications
June 12, 2015 June 12, 2015
LISP Canonical Address Format (LCAF) LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-09 draft-ietf-lisp-lcaf-10
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 2, line 41 skipping to change at page 2, line 41
4.16.3. ASCII Names in the Mapping Database . . . . . . . . 28 4.16.3. ASCII Names in the Mapping Database . . . . . . . . 28
4.16.4. Using Recursive LISP Canonical Address Encodings . . 29 4.16.4. Using Recursive LISP Canonical Address Encodings . . 29
4.16.5. Compatibility Mode Use Case . . . . . . . . . . . . 30 4.16.5. Compatibility Mode Use Case . . . . . . . . . . . . 30
5. Security Considerations . . . . . . . . . . . . . . . . . . . 31 5. Security Considerations . . . . . . . . . . . . . . . . . . . 31
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1. Normative References . . . . . . . . . . . . . . . . . . 32 7.1. Normative References . . . . . . . . . . . . . . . . . . 32
7.2. Informative References . . . . . . . . . . . . . . . . . 33 7.2. Informative References . . . . . . . . . . . . . . . . . 33
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 34 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 34
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 35 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 35
B.1. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 35 B.1. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 35
B.2. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 35 B.2. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 35
B.3. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 35 B.3. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 35
B.4. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 36 B.4. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 36
B.5. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 36 B.5. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 36
B.6. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 36 B.6. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 36
B.7. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 36 B.7. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 36
B.8. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 36 B.8. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 36
B.9. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 37 B.9. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 37
B.10. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 37 B.10. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 37
B.11. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37
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 35, line 25 skipping to change at page 35, line 25
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-09.txt B.1. Changes to draft-ietf-lisp-lcaf-10.txt
o Submitted June 2015.
o Fix coauthor Job's contact information.
B.2. 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.2. Changes to draft-ietf-lisp-lcaf-08.txt B.3. 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.3. Changes to draft-ietf-lisp-lcaf-07.txt B.4. 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.4. Changes to draft-ietf-lisp-lcaf-06.txt B.5. 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.5. Changes to draft-ietf-lisp-lcaf-05.txt B.6. 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.6. Changes to draft-ietf-lisp-lcaf-04.txt B.7. 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.7. Changes to draft-ietf-lisp-lcaf-03.txt B.8. 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.8. Changes to draft-ietf-lisp-lcaf-02.txt B.9. 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.9. Changes to draft-ietf-lisp-lcaf-01.txt B.10. 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.10. Changes to draft-ietf-lisp-lcaf-00.txt B.11. 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
skipping to change at page 37, line 36 skipping to change at page 37, line 45
Email: farinacci@gmail.com Email: farinacci@gmail.com
Dave Meyer Dave Meyer
Brocade Brocade
San Jose, CA San Jose, CA
USA USA
Email: dmm@1-4-5.net Email: dmm@1-4-5.net
Job Snijders Job Snijders
NTT NTT Communications
Tupolevlaan 103a Theodorus Majofskistraat 100
Schiphol-Rijk 1119 PA Amsterdam 1065 SZ
NL NL
Email: job@ntt.net Email: job@ntt.net
 End of changes. 14 change blocks. 
25 lines changed or deleted 33 lines changed or added

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