draft-ietf-lisp-lcaf-19.txt   draft-ietf-lisp-lcaf-20.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: April 21, 2017 Brocade Expires: May 2, 2017 Brocade
J. Snijders J. Snijders
NTT Communications NTT Communications
October 18, 2016 October 29, 2016
LISP Canonical Address Format (LCAF) LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-19 draft-ietf-lisp-lcaf-20
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.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 April 21, 2017. This Internet-Draft will expire on May 2, 2017.
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 47 skipping to change at page 2, line 47
5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 31 5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 31
5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 32 5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 32
5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 33 5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 33
6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 6. Security Considerations . . . . . . . . . . . . . . . . . . . 35
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.1. Normative References . . . . . . . . . . . . . . . . . . 36 8.1. Normative References . . . . . . . . . . . . . . . . . . 36
8.2. Informative References . . . . . . . . . . . . . . . . . 38 8.2. Informative References . . . . . . . . . . . . . . . . . 38
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 39 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 39
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 40 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 40
B.1. Changes to draft-ietf-lisp-lcaf-19.txt . . . . . . . . . 40 B.1. Changes to draft-ietf-lisp-lcaf-20.txt . . . . . . . . . 40
B.2. Changes to draft-ietf-lisp-lcaf-18.txt . . . . . . . . . 40 B.2. Changes to draft-ietf-lisp-lcaf-19.txt . . . . . . . . . 40
B.3. Changes to draft-ietf-lisp-lcaf-17.txt . . . . . . . . . 40 B.3. Changes to draft-ietf-lisp-lcaf-18.txt . . . . . . . . . 40
B.4. Changes to draft-ietf-lisp-lcaf-16.txt . . . . . . . . . 40 B.4. Changes to draft-ietf-lisp-lcaf-17.txt . . . . . . . . . 40
B.5. Changes to draft-ietf-lisp-lcaf-15.txt . . . . . . . . . 40 B.5. Changes to draft-ietf-lisp-lcaf-16.txt . . . . . . . . . 41
B.6. Changes to draft-ietf-lisp-lcaf-14.txt . . . . . . . . . 41 B.6. Changes to draft-ietf-lisp-lcaf-15.txt . . . . . . . . . 41
B.7. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 41 B.7. Changes to draft-ietf-lisp-lcaf-14.txt . . . . . . . . . 41
B.8. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 41 B.8. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 41
B.9. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 41 B.9. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 41
B.10. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 41 B.10. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 41
B.11. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 41 B.11. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 42
B.12. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 42 B.12. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 42
B.13. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 42 B.13. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 42
B.14. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 42 B.14. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 42
B.15. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 42 B.15. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 42
B.16. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 42 B.16. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 42
B.17. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 42 B.17. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 43
B.18. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 43 B.18. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 43
B.19. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 43 B.19. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 43
B.20. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 43 B.20. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 B.21. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
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). To provide flexibility for current and future applications, (RLOCs). To provide flexibility for current and future applications,
these values can be encoded in LISP control messages using a general these values can be encoded in LISP control messages using a general
syntax that includes Address Family Identifier (AFI), length, and syntax that includes Address Family Identifier (AFI), length, and
value fields. value fields.
skipping to change at page 24, line 7 skipping to change at page 24, line 7
using LISP over an IPv4 or IPv6 core network to create a layer-2 VPN. using LISP over an IPv4 or IPv6 core network to create a layer-2 VPN.
In this use case, a MAC address is being used as an EID, and the In this use case, a MAC address is being used as an EID, and the
locator-set that this EID maps to can be an IPv4 or IPv6 RLOCs, or locator-set that this EID maps to can be an IPv4 or IPv6 RLOCs, or
even another MAC address being used as an RLOC. See even another MAC address being used as an RLOC. See
[I-D.portoles-lisp-eid-mobility] for how layer-2 VPNs operate when [I-D.portoles-lisp-eid-mobility] for how layer-2 VPNs operate when
doing EID mobility. Refer to the Security Considerations section for doing EID mobility. Refer to the Security Considerations section for
privacy protection. privacy protection.
4.10.3. ASCII Names in the Mapping Database 4.10.3. ASCII Names in the Mapping Database
If DNS names or URIs are stored in the LISP Mapping Database System, If DNS names [RFC1035] or URIs [RFC3986] are stored in the LISP
the AFI List Type can be used to carry an ASCII string. Mapping Database System, the AFI List Type can be used to carry an
ASCII string.
ASCII LISP Canonical Address Format: ASCII LISP Canonical Address Format:
0 1 2 3 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 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 | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length | | Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 37, line 5 skipping to change at page 37, line 5
Table 1: LISP LCAF Type Initial Values Table 1: LISP LCAF Type Initial Values
8. References 8. References
8.1. Normative References 8.1. Normative References
[BCP160] "An Architecture for Location and Location Privacy in [BCP160] "An Architecture for Location and Location Privacy in
Internet Applications", Best Current Practices Internet Applications", Best Current Practices
https://www.rfc-editor.org/bcp/bcp160.txt, July 2011. https://www.rfc-editor.org/bcp/bcp160.txt, July 2011.
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets", and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
<http://www.rfc-editor.org/info/rfc1918>. <http://www.rfc-editor.org/info/rfc1918>.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced [RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced
by an On-line Database", RFC 3232, DOI 10.17487/RFC3232, by an On-line Database", RFC 3232, DOI 10.17487/RFC3232,
January 2002, <http://www.rfc-editor.org/info/rfc3232>. January 2002, <http://www.rfc-editor.org/info/rfc3232>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6280] Barnes, R., Lepinski, M., Cooper, A., Morris, J., [RFC6280] Barnes, R., Lepinski, M., Cooper, A., Morris, J.,
Tschofenig, H., and H. Schulzrinne, "An Architecture for Tschofenig, H., and H. Schulzrinne, "An Architecture for
Location and Location Privacy in Internet Applications", Location and Location Privacy in Internet Applications",
BCP 160, RFC 6280, DOI 10.17487/RFC6280, July 2011, BCP 160, RFC 6280, DOI 10.17487/RFC6280, July 2011,
<http://www.rfc-editor.org/info/rfc6280>. <http://www.rfc-editor.org/info/rfc6280>.
skipping to change at page 40, line 15 skipping to change at page 40, line 23
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
[RFC Editor: Please delete this section on publication as RFC.] [RFC Editor: Please delete this section on publication as RFC.]
B.1. Changes to draft-ietf-lisp-lcaf-19.txt B.1. Changes to draft-ietf-lisp-lcaf-20.txt
o Submitted October 2016.
o Put in references to DNS names and URIs per Alexey's comment.
B.2. Changes to draft-ietf-lisp-lcaf-19.txt
o Submitted October 2016. o Submitted October 2016.
o Make it more clear that any use-case documents that use the Geo- o Make it more clear that any use-case documents that use the Geo-
Coordinates LCAF type should discuss RFC6280 compliance. Coordinates LCAF type should discuss RFC6280 compliance.
B.2. Changes to draft-ietf-lisp-lcaf-18.txt B.3. Changes to draft-ietf-lisp-lcaf-18.txt
o Submitted October 2016 after October 13th telechat. o Submitted October 2016 after October 13th telechat.
o Addressed comments from Ben Campbell, Jari Arrko, Stephen Farrel, o Addressed comments from Ben Campbell, Jari Arrko, Stephen Farrel,
Peter Yee, Dale Worley, Mirja Kuehlewind, and Suresh Krishnan. Peter Yee, Dale Worley, Mirja Kuehlewind, and Suresh Krishnan.
B.3. Changes to draft-ietf-lisp-lcaf-17.txt B.4. Changes to draft-ietf-lisp-lcaf-17.txt
o Submitted October 2016. o Submitted October 2016.
o Addressed comments from Gen-ART reviewer Peter Yee. o Addressed comments from Gen-ART reviewer Peter Yee.
o Addressed IESG last-call comments from Suresh Krishnan. o Addressed IESG last-call comments from Suresh Krishnan.
B.4. Changes to draft-ietf-lisp-lcaf-16.txt B.5. Changes to draft-ietf-lisp-lcaf-16.txt
o Submitted October 2016. o Submitted October 2016.
o Addressed comments from Security Directorate reviewer David o Addressed comments from Security Directorate reviewer David
Mandelberg. Mandelberg.
B.5. Changes to draft-ietf-lisp-lcaf-15.txt B.6. Changes to draft-ietf-lisp-lcaf-15.txt
o Submitted September 2016. o Submitted September 2016.
o Addressed comments from Routing Directorate reviewer Stig Venass. o Addressed comments from Routing Directorate reviewer Stig Venass.
B.6. Changes to draft-ietf-lisp-lcaf-14.txt B.7. Changes to draft-ietf-lisp-lcaf-14.txt
o Submitted July 2016. o Submitted July 2016.
o Fix IDnits errors and comments from Luigi Iannone, document o Fix IDnits errors and comments from Luigi Iannone, document
shepherd. shepherd.
B.7. Changes to draft-ietf-lisp-lcaf-13.txt B.8. Changes to draft-ietf-lisp-lcaf-13.txt
o Submitted May 2016. o Submitted May 2016.
o Explain the Instance-ID LCAF Type is 32-bits in length and the 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. Instance-ID field in the LISP encapsulation header is 24-bits.
B.8. Changes to draft-ietf-lisp-lcaf-12.txt B.9. 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.9. Changes to draft-ietf-lisp-lcaf-11.txt B.10. 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.10. Changes to draft-ietf-lisp-lcaf-10.txt B.11. 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.11. Changes to draft-ietf-lisp-lcaf-09.txt B.12. 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.12. Changes to draft-ietf-lisp-lcaf-08.txt B.13. 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.13. Changes to draft-ietf-lisp-lcaf-07.txt B.14. 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.14. Changes to draft-ietf-lisp-lcaf-06.txt B.15. 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.15. Changes to draft-ietf-lisp-lcaf-05.txt B.16. 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.16. Changes to draft-ietf-lisp-lcaf-04.txt B.17. 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.17. Changes to draft-ietf-lisp-lcaf-03.txt B.18. 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.18. Changes to draft-ietf-lisp-lcaf-02.txt B.19. 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.19. Changes to draft-ietf-lisp-lcaf-01.txt B.20. 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.20. Changes to draft-ietf-lisp-lcaf-00.txt B.21. 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. 28 change blocks. 
47 lines changed or deleted 64 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/