< draft-acee-ospf-geo-location-02.txt		draft-acee-ospf-geo-location-03.txt >
	Network Working Group A. Lindem, Ed.		Network Working Group A. Lindem, Ed.
	Internet-Draft N. Shen		Internet-Draft N. Shen
	Intended status: Standards Track E. Chen		Intended status: Standards Track E. Chen
	Expires: April 24, 2017 Cisco Systems		Expires: May 1, 2017 Cisco Systems
	October 21, 2016		October 28, 2016
	OSPF Extensions for Advertising/Signaling Geo Location Information		OSPF Extensions for Advertising/Signaling Geo Location Information
	draft-acee-ospf-geo-location-02.txt		draft-acee-ospf-geo-location-03.txt
	Abstract		Abstract
	This document specifies an OSPF Router Information (RI) TLV to		This document specifies an OSPF Router Information (RI) TLV to
	advertise the current Geo Coordinates of the OSPF router. For Point-		advertise the current Geo Coordinates of the OSPF router. For Point-
	to-Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo		to-Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo
	Coordinates can be used to dynamically computing the cost to		Coordinates can be used to dynamically computing the cost to
	neighbors. This is useful both from the standpoint of auto-		neighbors. This is useful both from the standpoint of auto-
	configuration and situations where the OSPF routers are moving. The		configuration and situations where the OSPF routers are moving. The
	Geo Coordinates are also useful for other applications such as		Geo Coordinates are also useful for other applications such as
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 24, 2017.		This Internet-Draft will expire on May 1, 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 15 ¶		skipping to change at page 2, line 15 ¶
	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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2		1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2
	2. OSPF Geo Coordinates TLV . . . . . . . . . . . . . . . . . . 2		2. OSPF Geo Coordinates TLV . . . . . . . . . . . . . . . . . . 2
	3. Link Advertisement of the OSPF Geo-Coordinates . . . . . . . 4		3. Link Advertisement of the OSPF Geo-Coordinates . . . . . . . 4
	4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 4		4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 5
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 5		5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5		6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
	8.1. Normative References . . . . . . . . . . . . . . . . . . 6		8.1. Normative References . . . . . . . . . . . . . . . . . . 6
	8.2. Informative References . . . . . . . . . . . . . . . . . 6		8.2. Informative References . . . . . . . . . . . . . . . . . 6
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 7		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
	1. Introduction		1. Introduction
	This document specifies an OSPF Router Information (RI) [OSPF-RI] TLV		This document specifies an OSPF Router Information (RI) [OSPF-RI] TLV
	to advertise the current Geo Coordinates of the OSPF router. For		to advertise the current Geo Coordinates of the OSPF router. For
	Point-to-Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the		Point-to-Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the
	skipping to change at page 2, line 48 ¶		skipping to change at page 2, line 48 ¶
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC-KEYWORDS].		document are to be interpreted as described in [RFC-KEYWORDS].
	2. OSPF Geo Coordinates TLV		2. OSPF Geo Coordinates TLV
	The Geo Coordinates TLV can be used to advertise the current location		The Geo Coordinates TLV can be used to advertise the current location
	of an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] router using the OSPF Router		of an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] router using the OSPF Router
	Information LSA [OSPF-RI]. The OSPF Router Information LSA can be		Information LSA [OSPF-RI]. The OSPF Router Information LSA can be
	advertised in both link-scoped and area or AS scoped RI LSAs. The		advertised in both link-scoped and area or AS scoped RI LSAs. The
			fields specify the location of the OSPF router using the WGS-84
			(World Geodetic System) reference coordinate system [WGS84]. The
	value of the Geo Coordinates TLV consists of the following fields:		value of the Geo Coordinates TLV consists of the following fields:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|U|N|E|A|M| Reserved | Location Uncertainty |		|U|N|E|A|M|R|K| Reserved | Location Uncertainty |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Latitude Degr. | Latitude Milliseconds |		| Lat Degrees | Latitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Longitude Degr.| Longitude Milliseconds |		| Long Degrees | Longitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Altitude |		| Altitude |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Radius | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| .. Optional Sub-TLVs		| .. Optional Sub-TLVs
	+-+-+-+-+-+-+-+-+-....		+-+-+-+-+-+-+-+-+-....
	Where:		Where:
	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,		Uncertainty" field is specified. If the U-bit is clear,
	it indicates the "Location Uncertainty" field is		it indicates the "Location Uncertainty" field is
	unspecified.		unspecified.
	skipping to change at page 3, line 40 ¶		skipping to change at page 3, line 44 ¶
	the Longitude is west of the Prime Meridian.		the Longitude is west of the Prime Meridian.
	A-bit: If the A-bit is set, it indicates the "Altitude" field is		A-bit: If the A-bit is set, it indicates the "Altitude" field is
	specified. If the A-bit is clear, it indicates the		specified. If the A-bit is clear, it indicates the
	"Altitude" field is unspecified.		"Altitude" field is unspecified.
	M-bit: If the M-bit is set, it indicates the "Altitude" is		M-bit: If the M-bit is set, it indicates the "Altitude" is
	specified in meters. If the M-bit is clear, it indicates		specified in meters. If the M-bit is clear, it indicates
	the "Altitude" is in centimeters.		the "Altitude" is in centimeters.
			R-bit: If the R-bit is set, it indicates the "Radius" field is
			specified and the encoding is for a circular area. If
			the R-bit is clear, it indicates the "Radius" field is
			unspecified and the encoding is for a single point.
			K-bit: If the K-bit is set, it indicates the "Radius" is specified
			in kilometers. If the K-bit is clear, it indicates the
			"Radius" is in meters.
	Reserved: These bits are reserved. They SHOULD be set to 0 when		Reserved: These bits are reserved. They SHOULD be set to 0 when
	sending protocol packets and MUST be ignored when		sending protocol packets and MUST be ignored when
	receiving protocol packets.		receiving protocol packets.
	Location Uncertainty: Unsigned 16-bit integer indicating the		Location Uncertainty: Unsigned 16-bit integer indicating the
	number of centimeters of uncertainty for		number of centimeters of uncertainty for
	the location.		the location.
	Latitude Degrees: Unsigned 8-bit integer with a range of 0 - 90		Latitude Degrees: Unsigned 8-bit integer with a range of 0 - 90
	degrees north or south of the Equator (northern		degrees north or south of the Equator (northern
	skipping to change at page 4, line 16 ¶		skipping to change at page 4, line 30 ¶
	Longitude Degrees: Unsigned 8-bit integer with a range of 0 - 180		Longitude Degrees: Unsigned 8-bit integer with a range of 0 - 180
	degrees east or west of the Prime Meridian.		degrees east or west of the Prime Meridian.
	Longitude Milliseconds: Unsigned 24-bit integer with a range of		Longitude Milliseconds: Unsigned 24-bit integer with a range of
	0 - 3,599,999 (i.e., less than 60 minutes).		0 - 3,599,999 (i.e., less than 60 minutes).
	Altitude: Signed 32-bit integer containing the Height relative to		Altitude: Signed 32-bit integer containing the Height relative to
	sea level in centimeters or meters. A negative height		sea level in centimeters or meters. A negative height
	indicates that the location is below sea level.		indicates that the location is below sea level.
			Radius: Unsigned 16-bit integer containing the radius of a
			circle centered at the specified coordinates. The radius
			is specified in meters unless the K-bit is specified
			indicating specification in kilometers. If the radius is
			specified, the geo-coordinates specify the entire area
			of the circle defined by the radius and center point.
			While the use cases herein do not make use of this field,
			future use cases may.
	Optional Sub-TLVs: No additional Sub-TLVs are defined in this		Optional Sub-TLVs: No additional Sub-TLVs are defined in this
	document.		document.
	OSPF Geo Coordinates TLV		OSPF Geo Coordinates TLV
	3. Link Advertisement of the OSPF Geo-Coordinates		3. Link Advertisement of the OSPF Geo-Coordinates
	When the Geo Coordinates are used for cost computation, the		When the Geo Coordinates are used for cost computation, the
	cooridinates need to be advertised on the link using the encoding		coordinates need to be advertised on the link using the encoding
	specified in Section 2. For this application, a link-scoped OSPF		specified in Section 2. For this application, a link-scoped OSPF
	Router Information (RI) [OSPF-RI] is advertised on each link where		Router Information (RI) [OSPF-RI] is advertised on each link where
	geo-location cost computation is utilized.		geo-location cost computation is utilized.
	When an OSPF router receives the Geo Coordinates TLV in a link-scoped		When an OSPF router receives the Geo Coordinates TLV in a link-scoped
	OSPF RI LSA from an adjacent neighbor, it can be used to calculate		OSPF RI LSA from an adjacent neighbor, it can be used to calculate
	the physical distance to neighbor. For P2P and P2MP networks, this		the physical distance to neighbor. For P2P and P2MP networks, this
	distance can be used to dynamically compute the cost of the link to		distance can be used to dynamically compute the cost of the link to
	that neighbor. The mapping of the distance to advertised cost is not		that neighbor. The mapping of the distance to advertised cost is not
	specified in this document. However, all OSPF routers in the domain		specified in this document. However, all OSPF routers in the domain
	skipping to change at page 6, line 29 ¶		skipping to change at page 6, line 48 ¶
	8.2. Informative References		8.2. Informative References
	[GEO-PIDF-LO]		[GEO-PIDF-LO]
	Thomson, M. and J. Winterbottom, "Representation of		Thomson, M. and J. Winterbottom, "Representation of
	Uncertainty and Confidence in the Presence Information		Uncertainty and Confidence in the Presence Information
	Data Location Object (PIDF-LO)", RFC 7459, February 2015.		Data Location Object (PIDF-LO)", RFC 7459, February 2015.
	[IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC		[IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC
	4303, December 2005.		4303, December 2005.
			[LISP-GEO]
			Farinacci, D., "LISP Geo-Coordinate Use-Cases", farinacci-
			lisp-geo-02 (work in progress), October 2016.
	[OSPFV3-AUTH]		[OSPFV3-AUTH]
	Gupta, M. and S. Melam, "Authentication/Confidentiality		Gupta, M. and S. Melam, "Authentication/Confidentiality
	for OSPFv3", RFC 4552, June 2006.		for OSPFv3", RFC 4552, June 2006.
	[PRIVACY] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,		[PRIVACY] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
	Morris, J., Hansen, M., and R. Smith, "Privacy		Morris, J., Hansen, M., and R. Smith, "Privacy
	Considerations", RFC 6973, July 2013.		Considerations", RFC 6973, July 2013.
			[WGS84] National Imagery and Mapping Agency, "Department of
			Defense World Geodetic System 1984, Third Edition", NIMA
			TR83500.2, January 2000.
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
	The RFC text was produced using Marshall Rose's xml2rfc tool.		The RFC text was produced using Marshall Rose's xml2rfc tool.
	The encoding of the Geo location is adapted from the "Geo Coordinate		The encoding of the Geo location is adapted from "LISP Geo-
	LISP Canonical Address Format" specified in the "LISP Canonical		Coordinates Use-Cases" [LISP-GEO]. We would like to thank the
	Address Format (LCAF)". We would like to thank the authors of that		author, Dino Farinacci, for subsequent discussions.
	Document and particularily Dino Farinacci for subsequent discussions.
	Thanks to Yi Yang for review and discussions of the Geo Coordinate		Thanks to Yi Yang for review and discussions of the Geo Coordinate
	encoding.		encoding.
	The use-case for using OSPF to advertise the geo-location in OSPF was		The use-case for using OSPF to advertise the geo-location in OSPF was
	first mentioned in an OSPF operator-defined TLV draft by Uma		first mentioned in an OSPF operator-defined TLV draft by Uma
	Chunduri, Xiaohu Xu, Luis M. Contreras, Mohamed Boucadair, and Luay		Chunduri, Xiaohu Xu, Luis M. Contreras, Mohamed Boucadair, and Luay
	Jalil.		Jalil.
	Authors' Addresses		Authors' Addresses
End of changes. 17 change blocks.
	17 lines changed or deleted		45 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/