< draft-acee-ospf-geo-location-01.txt		draft-acee-ospf-geo-location-02.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: August 29, 2016 Cisco Systems		Expires: April 24, 2017 Cisco Systems
	February 26, 2016		October 21, 2016
	OSPF Extensions for Advertising/Signaling Geo Location Information		OSPF Extensions for Advertising/Signaling Geo Location Information
	draft-acee-ospf-geo-location-01.txt		draft-acee-ospf-geo-location-02.txt
	Abstract		Abstract
	This document specifies an OSPF Link-Local-Signaling (LLS) TLV to		This document specifies an OSPF Router Information (RI) TLV to
	signal the current Geo Coordinates of the OSPF router. For Point-to-		advertise the current Geo Coordinates of the OSPF router. For Point-
	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
	Traffic Engineering (TE) and network management and can be advertised		Traffic Engineering (TE) and network management.
	in the OSPF Router Information (RI) LSA.
	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.
	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 August 29, 2016.		This Internet-Draft will expire on April 24, 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 14 ¶
	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
	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. OSPF Geo Coordinates Link-Local-Signaling . . . . . . . . . . 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 . . . . . . . . . . 4
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 5		5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	7.1. Normative References . . . . . . . . . . . . . . . . . . 5		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	7.2. Informative References . . . . . . . . . . . . . . . . . 6		8.1. Normative References . . . . . . . . . . . . . . . . . . 6
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6		8.2. Informative References . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 7
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
	1. Introduction		1. Introduction
	This document specifies an OSPF Link-Local-Signaling (LLS) TLV to		This document specifies an OSPF Router Information (RI) [OSPF-RI] TLV
	signal the current Geo Coordinates of the OSPF router. For Point-to-		to advertise the current Geo Coordinates of the OSPF router. For
	Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo		Point-to-Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the
	Coordinates can be used to dynamically computing the cost to		Geo 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
	Traffic Engineering (TE) and network management and can be advertised		Traffic Engineering (TE)and network management.
	in the OSPF Router Information (RI) LSA [OSPF-RI].
	1.1. Requirements Notation		1.1. Requirements Notation
	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 either OSPF Link-		of an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] router using the OSPF Router
	Local-Signaling [LLS] or the OSPF Router Information LSA [OSPF-RI].		Information LSA [OSPF-RI]. The OSPF Router Information LSA can be
	The value of the Geo Coordinates TLV consists of the following		advertised in both link-scoped and area or AS scoped RI LSAs. The
	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| Reserved | Location Uncertainty |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Latitude Degr. | Latitude Milliseconds |		|Latitude Degr. | Latitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Longitude Degr.| Longitude Milliseconds |		|Longitude Degr.| Longitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Altitude |		| Altitude |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| .. Optional Sub-TLVs		| .. Optional Sub-TLVs
	skipping to change at page 4, line 23 ¶		skipping to change at page 4, line 21 ¶
	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.
	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. OSPF Geo Coordinates Link-Local-Signaling		3. Link Advertisement of the OSPF Geo-Coordinates
	The OSPF Geo Coordinates TLV may optionally be included in the Link-		When the Geo Coordinates are used for cost computation, the
	Local-Signaling [LLS] data block appended to OSPF hello packets.		cooridinates need to be advertised on the link using the encoding
			specified in Section 2. For this application, a link-scoped OSPF
			Router Information (RI) [OSPF-RI] is advertised on each link where
			geo-location cost computation is utilized.
	When an OSPF router receives the Geo Coordinates TLV in the LLS		When an OSPF router receives the Geo Coordinates TLV in a link-scoped
	extension from an adjacent neighbor, it can be used to calculate the		OSPF RI LSA from an adjacent neighbor, it can be used to calculate
	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 a		that neighbor. The mapping of the distance to advertised cost is not
	local matter and is not specified in this document. Computation of		specified in this document. However, all OSPF routers in the domain
	cost based on physical distance can be useful both for		SHOULD used the same algorithm. Computation of cost based on
	autoconfiguration of these networks types and dynamic cost		physical distance can be useful both for autoconfiguration of these
	computation when the routers are moving.		networks types and dynamic cost computation when the routers are
			moving.
	The Geo location information can be statically provisioned or		The Geo location information can be statically provisioned or
	dynamically acquired from a GPS capable device on the OSPF Router.		dynamically acquired from a GPS capable device on the OSPF Router.
	4. OSPFv2 Router Information (RI) Opaque LSA		4. OSPFv2 Router Information (RI) Opaque LSA
	The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF		The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF
	Router Information (RI) LSA [OSPF-RI]. It then may be used for		Router Information (RI) LSA [OSPF-RI]. It then may be used for
	applications such as traffic engineering (TE) and network management		applications such as traffic engineering (TE) and network management
	(e.g., the Find-My-Router application). The details of such		(e.g., the Find-My-Router application). The details of such
	skipping to change at page 5, line 23 ¶		skipping to change at page 5, line 23 ¶
	Additionally, in some situations, the topology of the network is		Additionally, in some situations, the topology of the network is
	considered proprietary information. With the Geo Location		considered proprietary information. With the Geo Location
	coordinates, the physical topology, as well as the IP topology, can		coordinates, the physical topology, as well as the IP topology, can
	be discerned from the OSPF Router Information (RI) LSA. In these		be discerned from the OSPF Router Information (RI) LSA. In these
	situations, confidentiality should be assured.		situations, confidentiality should be assured.
	Security considerations for the base OSPF protocol are covered in		Security considerations for the base OSPF protocol are covered in
	[OSPF] and [OSPFV3].		[OSPF] and [OSPFV3].
	6. IANA Considerations		6. Privacy Considerations
	The document will require two IANA actions:		If the location of an OSPF router advertising geo location
			coordinates as described herein can be directly correlated to an
			individual, individuals, or an organization, the location of that
			router should be considered sensitive and OSPF RI LSAs containing
			such geo coordinates should be advertised confidentially as described
			in Section 5. Additionally, OSPF network management facilities may
			require added authorization to view the contents of OSPF RI LSAs
			containing geo-Location TLVs. Refer to [PRIVACY] for more
			information.
	1. An LLS Type TLV for the Geo Location TLV will be allocated from		The Uncertainty and Confidence metrics for geo-location information
	the OSPF Link Local Signaling TLV Identifiers (LLS Types)		as described in [GEO-PIDF-LO] are not included in the Geo Coordinates
	registry.		TLV. In a future document, these may be considered for inclusion
			with additional Geo Location Sub-TLVs dependent on both on
			requirements and adoption of [GEO-PIDF-LO].
	2. A Router Information TLV type for the Geo Location TLV will be		7. IANA Considerations
	allocated from the OSPF Router Information (RI) TLVs registry.
	7. References		The document will require the following IANA actions:
	7.1. Normative References		1. A Router Information TLV type for the Geo Location TLV will be
			allocated from the OSPF Router Information (RI) TLVs registry.
	[LLS] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.		8. References
	Young, "OSPF Link-local Signaling", RFC 5613, August 2009.		8.1. Normative References
	[OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.		[OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
	[OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S.		[OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S.
	Shaffer, "Extensions to OSPF for Advertising Optional		Shaffer, "Extensions to OSPF for Advertising Optional
	Router Capabilities", RFC 7770, January 2016.		Router Capabilities", RFC 7770, January 2016.
	[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF		[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
	for IPv6", RFC 5340, July 2008.		for IPv6", RFC 5340, July 2008.
	[RFC-KEYWORDS]		[RFC-KEYWORDS]
	Bradner, S., "Key words for use in RFC's to Indicate		Bradner, S., "Key words for use in RFC's to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	7.2. Informative References		8.2. Informative References
			[GEO-PIDF-LO]
			Thomson, M. and J. Winterbottom, "Representation of
			Uncertainty and Confidence in the Presence Information
			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.
	[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.,
			Morris, J., Hansen, M., and R. Smith, "Privacy
			Considerations", RFC 6973, July 2013.
	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 the "Geo Coordinate
	LISP Canonical Address Format" specified in the "LISP Canonical		LISP Canonical Address Format" specified in the "LISP Canonical
	Address Format (LCAF)". We would like to thank the authors of that		Address Format (LCAF)". We would like to thank the authors of that
	Document and particularily 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
End of changes. 24 change blocks.
	49 lines changed or deleted		72 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/