< draft-acee-ospf-geo-location-00.txt		draft-acee-ospf-geo-location-01.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 15, 2016 Cisco Systems		Expires: August 29, 2016 Cisco Systems
	February 12, 2016		February 26, 2016
	OSPF Extensions for Advertising/Signaling Geo Location Information		OSPF Extensions for Advertising/Signaling Geo Location Information
	draft-acee-ospf-geo-location-00.txt		draft-acee-ospf-geo-location-01.txt
	Abstract		Abstract
	This document specifies an OSPF Link-Local-Signaling (LLS) TLV to		This document specifies an OSPF Link-Local-Signaling (LLS) TLV to
	signal the current Geo Coordinates of the OSPF router. For Point-to-		signal the current Geo Coordinates of the OSPF router. For Point-to-
	Point (P2)) and Point-to-Multi-Point (P2MP) networks, the Geo		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 and can be advertised
	in the OSPF Router Information (RI) LSA.		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
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 15, 2016.		This Internet-Draft will expire on August 29, 2016.
	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 17 ¶		skipping to change at page 2, line 17 ¶
	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. OSPF Geo Coordinates Link-Local-Signaling . . . . . . . . . . 4
	4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 4		4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 4
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 4		5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	7.1. Normative References . . . . . . . . . . . . . . . . . . 5		7.1. Normative References . . . . . . . . . . . . . . . . . . 5
	7.2. Informative References . . . . . . . . . . . . . . . . . 5		7.2. Informative References . . . . . . . . . . . . . . . . . 6
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	This document specifies an OSPF Link-Local-Signaling (LLS) TLV to		This document specifies an OSPF Link-Local-Signaling (LLS) TLV to
	signal the current Geo Coordinates of the OSPF router. For Point-to-		signal the current Geo Coordinates of the OSPF router. For Point-to-
	Point (P2)) and Point-to-Multi-Point (P2MP) networks, the Geo		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 and can be advertised
	in the OSPF Router Information (RI) LSA [OSPF-RI].		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 either OSPF Link-
	Local-Signaling [LLS] or the OSPF Router Information LSA [OSPF-RI].		Local-Signaling [LLS] or the OSPF Router Information LSA [OSPF-RI].
	The Geo Coordinates TLV encoding is adapted from the format in		The value of the Geo Coordinates TLV consists of the following
	[LISP-CAF]. The value of the Geo Coordinates TLV consists of the		fields:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length |		|U|N|E|A|M| Reserved | Location Uncertainty |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|N| Latitude Degrees | Minutes | Seconds |		|Latitude Degr. | Latitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|E| Longitude Degrees | Minutes | Seconds |		|Longitude Degr.| Longitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Altitude |		| Altitude |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| .. Optional Sub-TLVs		| .. Optional Sub-TLVs
	+-+-+-+-+-+-+-+-+-....		+-+-+-+-+-+-+-+-+-....
	Type: TBD. 8 bits value, to be assigned by IANA.		Where:
	Length: Variable. 8 bits value. The mandatory part is 12 octets.		U-bit: If the U-bit is set, it indicates that the "Location
			Uncertainty" field is specified. If the U-bit is clear,
			it indicates the "Location Uncertainty" field is
			unspecified.
	N: Bit indicating North (set) or South (clear).		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 Latitude is south of the Equator.
	Latitude Degrees: Valid values range from 0 to 90 degrees above or		E-bit: If the E-bit is set, it indicates the Longitude is east
	below the equator (northern or southern hemisphere,		of the Prime Meridian. If the E-bit is clear, it indicates
	respectively).		the Longitude is west of the Prime Meridian.
	Latitude Minutes: Valid values range from 0 to 59.		A-bit: If the A-bit is set, it indicates the "Altitude" field is
			specified. If the A-bit is clear, it indicates the
			"Altitude" field is unspecified.
	Latitude Seconds: Valid values range from 0 to 59.		M-bit: If the M-bit is set, it indicates the "Altitude" is
			specified in meters. If the M-bit is clear, it indicates
			the "Altitude" is in centimeters.
	E: Bit indicating East (set) or West (clear).		Reserved: These bits are reserved. They SHOULD be set to 0 when
			sending protocol packets and MUST be ignored when
			receiving protocol packets.
	Longitude Degrees: Value values are from 0 to 180 degrees right or		Location Uncertainty: Unsigned 16-bit integer indicating the
	left of the Prime Meridian.		number of centimeters of uncertainty for
			the location.
	Longitude Minutes: Valid values range from 0 to 59.		Latitude Degrees: Unsigned 8-bit integer with a range of 0 - 90
			degrees north or south of the Equator (northern
			or southern hemisphere, respectively).
	Longitude Seconds: Valid values range from 0 to 59.		Latitude Milliseconds: Unsigned 24-bit integer with a range of
			0 - 3,599,999 (i.e., less than 60 minutes).
	Altitude: Height relative to sea level in meters. This is a signed		Longitude Degrees: Unsigned 8-bit integer with a range of 0 - 180
	integer meaning that the altitude could be below sea		degrees east or west of the Prime Meridian.
	level. A value of 0x7fffffff indicates no Altitude value
	is encoded.
	Optional Sub-TLVs: No additional Sub-TLVs are defined in this		Longitude Milliseconds: Unsigned 24-bit integer with a range of
			0 - 3,599,999 (i.e., less than 60 minutes).
			Altitude: Signed 32-bit integer containing the Height relative to
			sea level in centimeters or meters. A negative height
			indicates that the location is below sea level.
			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. OSPF Geo Coordinates Link-Local-Signaling
	The OSPF Geo Coordinates TLV may optionally be included in the Link-		The OSPF Geo Coordinates TLV may optionally be included in the Link-
	Local-Signaling [LLS] data block appended to OSPF hello packets.		Local-Signaling [LLS] data block appended to OSPF hello packets.
	When an OSPF router receives the Geo Coordinates TLV in the LLS		When an OSPF router receives the Geo Coordinates TLV in the LLS
	skipping to change at page 5, line 41 ¶		skipping to change at page 6, line 10 ¶
	[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		7.2. Informative References
	[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-CAF]
	Farinacci, D., Meyers, D., and J. Snijders, "LISP
	Cananical Address Format (LCAF)", draft-ietf-list-lcaf-
	11.txt (work in progress), September 2015.
	[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.
	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.		Document and particularily Dino Farinacci for subsequent discussions.
			Thanks to Yi Yang for review and discussions of the Geo Coordinate
			encoding.
			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
			Chunduri, Xiaohu Xu, Luis M. Contreras, Mohamed Boucadair, and Luay
			Jalil.
	Authors' Addresses		Authors' Addresses
	Acee Lindem (editor)		Acee Lindem (editor)
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		USA
	Email: acee@cisco.com		Email: acee@cisco.com
	skipping to change at page 6, line 31 ¶		skipping to change at page 7, line 4 ¶
	Email: acee@cisco.com		Email: acee@cisco.com
	Naiming Shen		Naiming Shen
	Cisco Systems		Cisco Systems
	821 Alder Drive		821 Alder Drive
	Milpitas, CA 95935		Milpitas, CA 95935
	USA		USA
	Email: naiming@cisco.com		Email: naiming@cisco.com
	Enke Chen		Enke Chen
	Cisco Systems		Cisco Systems
	225 West Tasman Drive		821 Alder Drive
	San Jose, CA 95134		Milpitas, CA 95935
	USA		USA
	Email: enkechen@cisco.com		Email: enkechen@cisco.com
End of changes. 28 change blocks.
	42 lines changed or deleted		63 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/