draft-ietf-lisp-lcaf-00.txt   draft-ietf-lisp-lcaf-01.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft D. Meyer Internet-Draft D. Meyer
Intended status: Experimental cisco Systems Intended status: Experimental cisco Systems
Expires: March 3, 2013 J. Snijders Expires: July 11, 2013 J. Snijders
InTouch N.V. InTouch N.V.
August 30, 2012 January 7, 2013
LISP Canonical Address Format (LCAF) LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-00 draft-ietf-lisp-lcaf-01
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 34 skipping to change at page 1, line 34
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 March 3, 2013. This Internet-Draft will expire on July 11, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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
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 2, line 33 skipping to change at page 2, line 33
4.12.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . . 21 4.12.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . . 21
4.12.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 22 4.12.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 22
4.12.3. ASCII Names in the Mapping Database . . . . . . . . . 22 4.12.3. ASCII Names in the Mapping Database . . . . . . . . . 22
4.12.4. Using Recursive LISP Canonical Address Encodings . . 23 4.12.4. Using Recursive LISP Canonical Address Encodings . . 23
4.12.5. Compatibility Mode Use Case . . . . . . . . . . . . . 24 4.12.5. Compatibility Mode Use Case . . . . . . . . . . . . . 24
5. Security Considerations . . . . . . . . . . . . . . . . . . . 25 5. Security Considerations . . . . . . . . . . . . . . . . . . . 25
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1. Normative References . . . . . . . . . . . . . . . . . . . 27 7.1. Normative References . . . . . . . . . . . . . . . . . . . 27
7.2. Informative References . . . . . . . . . . . . . . . . . . 27 7.2. Informative References . . . . . . . . . . . . . . . . . . 27
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 28 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 29
Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 29 Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 30
B.1. Changes to draft-ietf-lisp-00.txt . . . . . . . . . . . . 29 B.1. Changes to draft-ietf-lisp-01.txt . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 B.2. Changes to draft-ietf-lisp-00.txt . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
The LISP architecture and protocols [LISP] introduces two new The LISP architecture and protocols [LISP] 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),
length, and value fields. length, and value fields.
skipping to change at page 10, line 11 skipping to change at page 10, line 11
encoding when an ITR wants a locator-set for a specific application. encoding when an ITR wants a locator-set for a specific application.
When used for an RLOC encoding, the ETR is supplying a locator-set When used for an RLOC encoding, the ETR is supplying a locator-set
for each specific application is has been configured to advertise. for each specific application is has been configured to advertise.
4.4. Assigning Geo Coordinates to Locator Addresses 4.4. Assigning Geo Coordinates to Locator Addresses
If an ETR desires to send a Map-Reply describing the Geo Coordinates If an ETR desires to send a Map-Reply describing the Geo Coordinates
for each locator in its locator-set, it can use the Geo Coordinate for each locator in its locator-set, it can use the Geo Coordinate
Type to convey physical location information. Type to convey physical location information.
Coordinates are specified using the WGS-84 (World Geodetic System)
reference coordinate system [WGS-84].
Geo Coordinate LISP Canonical Address Format: Geo Coordinate 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 = 5 | Rsvd2 | 12 + n | | Type = 5 | Rsvd2 | 12 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds | |N| Latitude Degrees | Minutes | Seconds |
skipping to change at page 10, line 35 skipping to change at page 10, line 38
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
8-byte Longitude and Latitude fields including the AFI field 8-byte Longitude and Latitude fields including the AFI field
itself. itself.
N: When set to 1 means North, otherwise South. N: When set to 1 means North, otherwise South.
Latitude Degrees: Valid values range from 0 to 90. degrees above or Latitude Degrees: Valid values range from 0 to 90 degrees above or
below the equator (northern or southern hemisphere, respectively). below the equator (northern or southern hemisphere, respectively).
Latitude Minutes: Valid values range from 0 to 59. Latitude Minutes: Valid values range from 0 to 59.
Latitude Seconds: Valid values range from 0 to 59. Latitude Seconds: Valid values range from 0 to 59.
E: When set to 1 means East, otherwise West. E: When set to 1 means East, otherwise West.
Longitude Degrees: Value values are from 0 to 90 degrees right or Longitude Degrees: Value values are from 0 to 180 degrees right or
left of the Prime Meridian. left of the Prime Meridian.
Longitude Minutes: Valid values range from 0 to 59. Longitude Minutes: Valid values range from 0 to 59.
Longitude Seconds: Valid values range from 0 to 59. Longitude Seconds: Valid values range from 0 to 59.
Altitude: Height relative to sea level in meters. This is a signed Altitude: Height relative to sea level in meters. This is a signed
integer meaning that the altitude could be below sea level. A integer meaning that the altitude could be below sea level. A
value of 0x7fffffff indicates no Altitude value is encoded. value of 0x7fffffff indicates no Altitude value is encoded.
skipping to change at page 28, line 5 skipping to change at page 27, line 50
[LISP-NATT] [LISP-NATT]
Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino, Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino,
F., and C. White, "NAT traversal for LISP", F., and C. White, "NAT traversal for LISP",
draft-ermagan-lisp-nat-traversal-00.txt (work in draft-ermagan-lisp-nat-traversal-00.txt (work in
progress). progress).
[LISP-TE] Farinacci, D., Lahiri, P., and M. Kowal, "LISP Traffic [LISP-TE] Farinacci, D., Lahiri, P., and M. Kowal, "LISP Traffic
Engineering Use-Cases", draft-farinacci-lisp-te-01.txt Engineering Use-Cases", draft-farinacci-lisp-te-01.txt
(work in progress). (work in progress).
[WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic
System 1984", NIMA TR8350.2, January 2000, <http://
earth-info.nga.mil/GandG/publications/tr8350.2/
wgs84fin.pdf>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The authors would like to thank Vince Fuller, Gregg Schudel, Jesper The authors would like to thank Vince Fuller, Gregg Schudel, Jesper
Skriver, Luigi Iannone, and Isidor Kouvelas for their technical and Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for
editorial commentary. their technical and editorial commentary.
The authors would like to thank Victor Moreno for discussions that The authors would like to thank Victor Moreno for discussions that
lead to the definition of the Multicast Info LCAF type. lead to the definition of the Multicast Info LCAF type.
The authors would like to thank Parantap Lahiri and Michael Kowal for The authors would like to thank Parantap Lahiri and Michael Kowal for
discussions that lead to the definition of the Explicit Locator Path discussions that lead to the definition of the Explicit Locator Path
(ELP) LCAF type. (ELP) LCAF type.
The authors would like to thank Fabio Maino and Vina Ermagan for The authors would like to thank Fabio Maino and Vina Ermagan for
discussions that lead to the definition of the Security Key LCAF discussions that lead to the definition of the Security Key LCAF
type. type.
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-00.txt B.1. Changes to draft-ietf-lisp-01.txt
o Submitted January 2013.
o Change longitude range from 0-90 to 0-180 in section 4.4.
o Added reference to WGS-84 in section 4.4.
B.2. Changes to draft-ietf-lisp-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
cisco Systems cisco Systems
Tasman Drive Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: dino@cisco.com Email: farinacci@gmail.com
Dave Meyer Dave Meyer
cisco Systems cisco Systems
170 Tasman Drive 170 Tasman Drive
San Jose, CA San Jose, CA
USA USA
Email: dmm@cisco.com Email: dmm@cisco.com
Job Snijders Job Snijders
 End of changes. 13 change blocks. 
15 lines changed or deleted 32 lines changed or added

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