< draft-farinacci-lisp-geo-02.txt		draft-farinacci-lisp-geo-03.txt >
	Network Working Group D. Farinacci		Network Working Group D. Farinacci
	Internet-Draft lispers.net		Internet-Draft lispers.net
	Intended status: Experimental October 28, 2016		Intended status: Experimental April 28, 2017
	Expires: May 1, 2017		Expires: October 30, 2017
	LISP Geo-Coordinate Use-Cases		LISP Geo-Coordinate Use-Cases
	draft-farinacci-lisp-geo-02		draft-farinacci-lisp-geo-03
	Abstract		Abstract
	This draft describes how Geo-Coordinates can be used in the LISP		This draft describes how Geo-Coordinates can be used in the LISP
	Architecture and Protocols.		Architecture and Protocols.
	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
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 31 ¶		skipping to change at page 1, line 31 ¶
	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 May 1, 2017.		This Internet-Draft will expire on October 30, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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 19 ¶		skipping to change at page 2, line 19 ¶
	3. Geo-Points in RLOC-records . . . . . . . . . . . . . . . . . 3		3. Geo-Points in RLOC-records . . . . . . . . . . . . . . . . . 3
	4. Geo-Prefixes in EID-records and RLOC-records . . . . . . . . 3		4. Geo-Prefixes in EID-records and RLOC-records . . . . . . . . 3
	5. Geo-Prefix and Geo-Point Encodings . . . . . . . . . . . . . 5		5. Geo-Prefix and Geo-Point Encodings . . . . . . . . . . . . . 5
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 7		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	8.1. Normative References . . . . . . . . . . . . . . . . . . 7		8.1. Normative References . . . . . . . . . . . . . . . . . . 7
	8.2. Informative References . . . . . . . . . . . . . . . . . 8		8.2. Informative References . . . . . . . . . . . . . . . . . 8
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9
	Appendix B. Document Change Log . . . . . . . . . . . . . . . . 9		Appendix B. Document Change Log . . . . . . . . . . . . . . . . 9
	B.1. Changes to draft-farinacci-lisp-geo--02.txt . . . . . . . 9		B.1. Changes to draft-farinacci-lisp-geo-03.txt . . . . . . . 9
	B.2. Changes to draft-farinacci-lisp-geo--01.txt . . . . . . . 9		B.2. Changes to draft-farinacci-lisp-geo-02.txt . . . . . . . 9
	B.3. Changes to draft-farinacci-lisp-geo--00.txt . . . . . . . 10		B.3. Changes to draft-farinacci-lisp-geo-01.txt . . . . . . . 9
			B.4. Changes to draft-farinacci-lisp-geo-00.txt . . . . . . . 10
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
	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)
	[RFC1700].		[RFC1700].
	This specification introduces the use of Geo-Coordinates that can be		This specification introduces the use of Geo-Coordinates that can be
	used in EID-records and RLOC-records of LISP control messages. The		used in EID-records and RLOC-records of LISP control messages. The
	encoding format is specified in [I-D.ietf-lisp-lcaf] as the "Geo-		encoding format is specified in [RFC8060] as the "Geo-Coordinates
	Coordinates LCAF Type".		LCAF Type".
	2. Definition of Terms		2. Definition of Terms
	Geo-Point is a Geo-Coordinate according to [GEO] that defines a		Geo-Point is a Geo-Coordinate according to [GEO] that defines a
	point from parameters Latitude, Longitude, and Altitude.		point from parameters Latitude, Longitude, and Altitude.
	Geo-Prefix forms a circle of a geographic area made up of a Geo-		Geo-Prefix forms a circle of a geographic area made up of a Geo-
	Point and a Radius. A Geo-Point is known to be "more-specific"		Point and a Radius. A Geo-Point is known to be "more-specific"
	than a Geo-Prefix when its physical location is within the		than a Geo-Prefix when its physical location is within the
	geographic circle.		geographic circle.
	skipping to change at page 5, line 32 ¶		skipping to change at page 5, line 32 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Long Degrees | Longitude Milliseconds |		| Long Degrees | Longitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Altitude |		| Altitude |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Radius | Reserved |		| Radius | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| AFI = x | Address ... |		| AFI = x | Address ... |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Rsvd1/Rsvd2/Flags: See [I-D.ietf-lisp-lcaf] for details.		Rsvd1/Rsvd2/Flags: See [RFC8060] for details.
	Length: length in bytes starting and including the byte after this		Length: length in bytes starting and including the byte after this
	Length field.		Length field.
	U-bit: If the U-bit is set, it indicates that the "Location		U-bit: If the U-bit is set, it indicates that the "Location
	Uncertainty" field is specified. If the U-bit is clear, it		Uncertainty" field is specified. If the U-bit is clear, it
	indicates the "Location Uncertainty" field is unspecified.		indicates the "Location Uncertainty" field is unspecified.
	N-bit: If the N-bit is set, it indicates the Latitude is north		N-bit: If the N-bit is set, it indicates the Latitude is north
	relative to the Equator. If the N-bit is clear, it indicates the		relative to the Equator. If the N-bit is clear, it indicates the
	skipping to change at page 6, line 49 ¶		skipping to change at page 6, line 49 ¶
	sea level in centimeters or meters. A negative height indicates		sea level in centimeters or meters. A negative height indicates
	that the location is below sea level.		that the location is below sea level.
	Radius: Unsigned 16-bit integer containing the radius of a circle		Radius: Unsigned 16-bit integer containing the radius of a circle
	(or sphere) centered at the specified coordinates. The radius is		(or sphere) centered at the specified coordinates. The radius is
	specified in meters unless the K-bit is specified indicating		specified in meters unless the K-bit is specified indicating
	radius is in kilometers. When the radius is specified, this LCAF		radius is in kilometers. When the radius is specified, this LCAF
	type encodes a Geo-Prefix where the geo-coordinates define the		type encodes a Geo-Prefix where the geo-coordinates define the
	entire area of the circle defined by the radius and center point.		entire area of the circle defined by the radius and center point.
	AFI = x: x can be any AFI value from [AFI] and [I-D.ietf-lisp-lcaf].		AFI = x: x can be any AFI value from [AFI] and [RFC8060].
	6. Security Considerations		6. Security Considerations
	The use of Geo-Coordinates in any application must be considered		The use of Geo-Coordinates in any application must be considered
	carefully to not violate any privacy concerns about physical		carefully to not violate any privacy concerns about physical
	location. This draft does take into consideration the applicability		location. This draft does take into consideration the applicability
	of BCP160 [RFC6280] for location-based privacy protection.		of BCP160 [RFC6280] for location-based privacy protection.
	In a LISP environment, Geo-Coordinates can be registered to the		In a LISP environment, Geo-Coordinates can be registered to the
	Mapping Database System. When this occurs, an xTR is allowing its		Mapping Database System. When this occurs, an xTR is allowing its
	skipping to change at page 8, line 5 ¶		skipping to change at page 7, line 50 ¶
	At this time there are no specific requests for IANA.		At this time there are no specific requests for IANA.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[GEO] Geodesy and Geophysics Department, DoD., "World Geodetic		[GEO] Geodesy and Geophysics Department, DoD., "World Geodetic
	System 1984", NIMA TR8350.2, January 2000, <http://earth-		System 1984", NIMA TR8350.2, January 2000, <http://earth-
	info.nga.mil/GandG/publications/tr8350.2/wgs84fin.pdf>.		info.nga.mil/GandG/publications/tr8350.2/wgs84fin.pdf>.
	[I-D.ietf-lisp-lcaf]
	Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical
	Address Format (LCAF)", draft-ietf-lisp-lcaf-19 (work in
	progress), October 2016.
	[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700,		[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700,
	DOI 10.17487/RFC1700, October 1994,		DOI 10.17487/RFC1700, October 1994,
	<http://www.rfc-editor.org/info/rfc1700>.		<http://www.rfc-editor.org/info/rfc1700>.
	[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>.
	[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The		[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
	Locator/ID Separation Protocol (LISP)", RFC 6830,		Locator/ID Separation Protocol (LISP)", RFC 6830,
	DOI 10.17487/RFC6830, January 2013,		DOI 10.17487/RFC6830, January 2013,
	<http://www.rfc-editor.org/info/rfc6830>.		<http://www.rfc-editor.org/info/rfc6830>.
			[RFC8060] Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical
			Address Format (LCAF)", RFC 8060, DOI 10.17487/RFC8060,
			February 2017, <http://www.rfc-editor.org/info/rfc8060>.
	8.2. Informative References		8.2. Informative References
	[AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY		[AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY
	NUMBERS http://www.iana.org/assignments/address-family-		NUMBERS http://www.iana.org/assignments/address-family-
	numbers/address-family-numbers.xhtml?, Febuary 2007.		numbers/address-family-numbers.xhtml?, Febuary 2007.
	[I-D.acee-ospf-geo-location]		[I-D.acee-ospf-geo-location]
	Lindem, A., Shen, N., and E. Chen, "OSPF Extensions for		Lindem, A., Shen, N., and E. Chen, "OSPF Extensions for
	Advertising/Signaling Geo Location Information", draft-		Advertising/Signaling Geo Location Information", draft-
	acee-ospf-geo-location-02 (work in progress), October		acee-ospf-geo-location-04 (work in progress), April 2017.
	2016.
	[I-D.chen-idr-geo-coordinates]		[I-D.chen-idr-geo-coordinates]
	Chen, E., Shen, N., and R. Raszuk, "Carrying Geo		Chen, E., Shen, N., and R. Raszuk, "Carrying Geo
	Coordinates in BGP", draft-chen-idr-geo-coordinates-01		Coordinates in BGP", draft-chen-idr-geo-coordinates-02
	(work in progress), March 2016.		(work in progress), October 2016.
	[I-D.farinacci-lisp-name-encoding]		[I-D.farinacci-lisp-name-encoding]
	Farinacci, D., "LISP Distinguished Name Encoding", draft-		Farinacci, D., "LISP Distinguished Name Encoding", draft-
	farinacci-lisp-name-encoding-02 (work in progress),		farinacci-lisp-name-encoding-03 (work in progress), March
	October 2016.		2017.
	[I-D.ietf-lisp-sec]		[I-D.ietf-lisp-sec]
	Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D.		Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D.
	Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-11		Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-12
	(work in progress), October 2016.		(work in progress), November 2016.
	[I-D.jeong-its-v2i-problem-statement]		[I-D.jeong-its-v2i-problem-statement]
	Jeong, J. and T. Oh, "Problem Statement for Vehicle-to-		Jeong, J. and T. Oh, "Problem Statement for Vehicle-to-
	Infrastructure Networking", draft-jeong-its-v2i-problem-		Infrastructure Networking", draft-jeong-its-v2i-problem-
	statement-02 (work in progress), July 2016.		statement-02 (work in progress), July 2016.
	[I-D.shen-isis-geo-coordinates]		[I-D.shen-isis-geo-coordinates]
	Shen, N., Chen, E., and A. Lindem, "Carrying Geo		Shen, N. and E. Chen, "Carrying Geo Coordinates
	Coordinates Information In IS-IS", draft-shen-isis-geo-		Information In IS-IS", draft-shen-isis-geo-coordinates-03
	coordinates-01 (work in progress), March 2016.		(work in progress), April 2017.
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
	The author would like to thank the LISP WG for their review and		The author would like to thank the LISP WG for their review and
	acceptance of this draft.		acceptance of this draft.
	A special thanks goes to Enke Chen, Acee Lindem, and Naiming Shen for		A special thanks goes to Enke Chen, Acee Lindem, and Naiming Shen for
	collaboarting on a consistent geo-location encoding format with OSPF		collaboarting on a consistent geo-location encoding format with OSPF
	[I-D.acee-ospf-geo-location], IS-IS [I-D.shen-isis-geo-coordinates],		[I-D.acee-ospf-geo-location], IS-IS [I-D.shen-isis-geo-coordinates],
	and BGP [I-D.chen-idr-geo-coordinates] protocols.		and BGP [I-D.chen-idr-geo-coordinates] protocols.
	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-farinacci-lisp-geo--02.txt		B.1. Changes to draft-farinacci-lisp-geo-03.txt
			o Posted April 2017.
			o Update document timer.
			B.2. Changes to draft-farinacci-lisp-geo-02.txt
	o Posted October 2016.		o Posted October 2016.
	o Change format of the Geo-Coordinates LCAF Type to be compatible		o Change format of the Geo-Coordinates LCAF Type to be compatible
	with equivalent proposals for OSPF, IS-IS, and BGP.		with equivalent proposals for OSPF, IS-IS, and BGP.
	o Add to the Security Considerations section to BCP160 compliance.		o Add to the Security Considerations section to BCP160 compliance.
	B.2. Changes to draft-farinacci-lisp-geo--01.txt		B.3. Changes to draft-farinacci-lisp-geo-01.txt
	o Posted October 2016.		o Posted October 2016.
	o Clarify that the Geo-Coordinates LCAF type should be encoded		o Clarify that the Geo-Coordinates LCAF type should be encoded
	inside an Instance-ID LCAF type when VPNs are used.		inside an Instance-ID LCAF type when VPNs are used.
	o Indiate what the value of the Altitude field is when not included		o Indiate what the value of the Altitude field is when not included
	in a message. Since this draft shortens the field, a new value is		in a message. Since this draft shortens the field, a new value is
	specified in this draft for not conveying an Altitude value in a		specified in this draft for not conveying an Altitude value in a
	message.		message.
	B.3. Changes to draft-farinacci-lisp-geo--00.txt		B.4. Changes to draft-farinacci-lisp-geo-00.txt
	o Initial draft posted April 2016.		o Initial draft posted April 2016.
	Author's Address		Author's Address
	Dino Farinacci		Dino Farinacci
	lispers.net		lispers.net
	San Jose, CA		San Jose, CA
	USA		USA
End of changes. 18 change blocks.
	31 lines changed or deleted		36 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/