< draft-chen-idr-geo-coordinates-01.txt		draft-chen-idr-geo-coordinates-02.txt >
	Network Working Group E. Chen		Network Working Group E. Chen
	Internet Draft N. Shen		Internet Draft N. Shen
	Intended Status: Standards Track Cisco Systems		Intended Status: Standards Track Cisco Systems
	Expiration Date: September 2, 2016 R. Raszuk		Expiration Date: April 29, 2017 R. Raszuk
	Bloomberg LP		Bloomberg LP
	March 1, 2016		October 28, 2016
	Carrying Geo Coordinates in BGP		Carrying Geo Coordinates in BGP
	draft-chen-idr-geo-coordinates-01.txt		draft-chen-idr-geo-coordinates-02.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/1id-abstracts.html		http://www.ietf.org/1id-abstracts.html
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	This Internet-Draft will expire on September 2, 2016.		This Internet-Draft will expire on April 29, 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 3, line 10 ¶		skipping to change at page 3, line 10 ¶
	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 [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. The Geo Coordinate Capability		2. The Geo Coordinate Capability
	The Geo Coordinate Capability is a new BGP capability [RFC5492]. The		The Geo Coordinate Capability is a new BGP capability [RFC5492]. The
	Capability Code for this capability is specified in the "IANA		Capability Code for this capability is specified in the "IANA
	Considerations" section of this document. The Capability Length is		Considerations" section of this document. The Capability Length is
	16 octets. The Capability Value consists of the following fields		20 octets. The Capability Value consists of the following fields
	that specify the location of the speaker using the WGS-84 (World		that specify the location of the speaker using the WGS-84 (World
	Geodetic System) reference coordinate system [WGS-84]:		Geodetic System) reference coordinate system [WGS-84]:
	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-1 | Location Uncertainty |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Latitude Degr. | Latitude Milliseconds |		| Lat Degrees | Latitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Longitude Degr.| Longitude Milliseconds |		| Long Degrees | Longitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Altitude |		| Altitude |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Radius | Reserved-2 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	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, 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		relative to the Equator. If the N-bit is clear, it
	the Latitude is south of the Equator.		indicates the Latitude is south of the Equator.
	E-bit: If the E-bit is set, it indicates the Longitude is east of		E-bit: If the E-bit is set, it indicates the Longitude is east of
	the Prime Meridian. If the E-bit is clear, it indicates the		the Prime Meridian. If the E-bit is clear, it indicates the
	Longitude is West of the Prime Meridian.		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 "Altitude"		specified. If the A-bit is clear, it indicates the
	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 the		specified in meters. If the M-bit is clear, it indicates
	"Altitude" is in centimeters.		the "Altitude" is in centimeters.
	Reserved: These bits are reserved. They SHOULD be set to zero by		R-bit: If the R-bit is set, it indicates the "Radius" field is
	the sender and MUST be ignored by the receiver.		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-1: These bits are reserved. They SHOULD be set to zero by
			the sender and MUST be ignored by the receiver.
	Location Uncertainty: Unsigned 16-bit integer indicating the number		Location Uncertainty: Unsigned 16-bit integer indicating the number
	of centimeters of uncertainty for the location.		of centimeters of uncertainty for 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 the Equator (northern or southern		degrees north or south of the Equator (northern or southern
	hemisphere, respectively).		hemisphere, respectively).
	Latitude Milliseconds: Unsigned 24-bit integer with a range of		Latitude Milliseconds: Unsigned 24-bit integer with a range of 0 -
	0 - 3,599,999 (i.e., less than 60 minutes).		3,599,999 (i.e., less than 60 minutes).
	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 -
	0 - 3,599,999 (i.e., less than 60 minutes).		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
	the 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.
			Reserved-2: The 16-bit field is reserved. It SHOULD be set to zero
			by the sender and MUST be ignored by the receiver.
	3. The Geo Coordinate Attribute		3. The Geo Coordinate Attribute
	The Geo Coordinate Attribute is an optional, transitive BGP attribute		The Geo Coordinate Attribute is an optional, transitive BGP attribute
	[RFC4271]. The type of the attribute is described in the IANA		[RFC4271]. The type of the attribute is described in the IANA
	Considerations section, and the value of the attribute consists of		Considerations section, and the value of the attribute consists of
	one or more of the tuple encoded as shown below:		one or more of the tuple encoded as shown below:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| AS Number |		| AS Number |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BGP Identifier |		| BGP Identifier |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|U|N|E|A|M| Reserved | Location Uncertainty |		|U|N|E|A|M|R|K| Reserved-1 | Location Uncertainty |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Latitude Degr. | Latitude Milliseconds |		| Lat Degrees | Latitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Longitude Degr.| Longitude Milliseconds |		| Long Degrees | Longitude Milliseconds |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Altitude |		| Altitude |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Radius | Reserved-2 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	where the "AS number" and the "BGP Identifier" fields contain the AS		where the "AS number" and the "BGP Identifier" fields contain the AS
	number and the BGP Identifier [RFC4271, RFC6286] of the BGP speaker		number and the BGP Identifier [RFC4271, RFC6286] of the BGP speaker
	that sources or advertises the route, and the remaining fields		that sources or advertises the route, and the remaining fields
	specify the location of the speaker using the WGS-84 (World Geodetic		specify the location of the speaker using the WGS-84 (World Geodetic
	System) reference coordinate system [WGS-84]. These location related		System) reference coordinate system [WGS-84]. These location related
	fields are hereby given the same description as the ones in the "Geo		fields are hereby given the same description as the ones in the "Geo
	Coordinate Capability" section.		Coordinate Capability" section.
	skipping to change at page 5, line 38 ¶		skipping to change at page 6, line 23 ¶
	UPDATE message from a neighbor, it is up to the speaker and the local		UPDATE message from a neighbor, it is up to the speaker and the local
	policy to decide how this attribute would be handled and used.		policy to decide how this attribute would be handled and used.
	The Geo Coordinate Capability in an OPEN message does not have any		The Geo Coordinate Capability in an OPEN message does not have any
	impact on how the Geo Coordinate Attribute in an UPDATE message		impact on how the Geo Coordinate Attribute in an UPDATE message
	(carried over the same session) would be handled.		(carried over the same session) would be handled.
	5. Error Handling		5. Error Handling
	The Geo Coordinate Attribute in an UPDATE message is considered		The Geo Coordinate Attribute in an UPDATE message is considered
	malformed if the attribute length is not a non-zero multiple of 24.		malformed if the attribute length is not a non-zero multiple of 28.
	An UPDATE message with a malformed Geo Coordinate Attribute SHALL be		An UPDATE message with a malformed Geo Coordinate Attribute SHALL be
	handled using the approach of "attribute discard" [RFC7606].		handled using the approach of "attribute discard" [RFC7606].
	6. IANA Considerations		6. IANA Considerations
	This documents specifies a BGP capability, the Geo Coordinate		This documents specifies a BGP capability, the Geo Coordinate
	Capability. The capability type needs to be allocated by IANA.		Capability. The capability type needs to be allocated by IANA.
	This documents specifies a BGP attribute, the Geo Coordinate		This documents specifies a BGP attribute, the Geo Coordinate
	skipping to change at page 6, line 25 ¶		skipping to change at page 7, line 5 ¶
	The underlying security issues for BGP are discussed in [RFC4271].		The underlying security issues for BGP are discussed in [RFC4271].
	Since the Geo coordinates provide the exact location of the routing		Since the Geo coordinates provide the exact location of the routing
	devices, disclosure may make the routing devices more susceptible to		devices, disclosure may make the routing devices more susceptible to
	physical attacks. In situations where this is a concern (e.g., in		physical attacks. In situations where this is a concern (e.g., in
	military applications, or the topology of the network is considered		military applications, or the topology of the network is considered
	proprietary information), the implementation MUST allow the Geo		proprietary information), the implementation MUST allow the Geo
	Location extension to be removed from the BGP's OPEN and UPDATE		Location extension to be removed from the BGP's OPEN and UPDATE
	messages.		messages.
	8. Acknowledgments		8. Privacy Considerations
			TBD.
			9. Acknowledgments
	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 particularly Dino Farinacci for subsequent discussions.		Document and particularly Dino Farinacci for subsequent discussions.
	Thanks to Yi Yang for review and discussions of the Geo Coordinate		Thanks to Yi Yang and Acee Lindem for review and discussions of the
	encoding.		Geo Coordinate encoding.
	9. References		10. References
	9.1. Normative References		10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A		[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
	Border Gateway Protocol 4 (BGP-4)", RFC 4271,		Border Gateway Protocol 4 (BGP-4)", RFC 4271,
	DOI 10.17487/RFC4271, January 2006,		DOI 10.17487/RFC4271, January 2006,
	<http://www.rfc-editor.org/info/rfc4271>.		<http://www.rfc-editor.org/info/rfc4271>.
	skipping to change at page 7, line 20 ¶		skipping to change at page 8, line 5 ¶
	[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.		[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
	Patel, "Revised Error Handling for BGP UPDATE Messages",		Patel, "Revised Error Handling for BGP UPDATE Messages",
	RFC 7606, DOI 10.17487/RFC7606, August 2015,		RFC 7606, DOI 10.17487/RFC7606, August 2015,
	<http://www.rfc-editor.org/info/rfc7606>.		<http://www.rfc-editor.org/info/rfc7606>.
	[WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic		[WGS-84] 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>.
	9.2. Informative References		10.2. Informative References
	[I-D.ietf-idr-tunnel-encaps]		[I-D.ietf-idr-tunnel-encaps]
	Rosen, E., Patel, K., and G. Velde, "The BGP Tunnel		Rosen, E., Patel, K., and G. Velde, "The BGP Tunnel
	Encapsulation Attribute", draft-ietf-idr-tunnel-encaps-01		Encapsulation Attribute", draft-ietf-idr-tunnel-encaps-01
	(work in progress), December 2015.		(work in progress), December 2015.
			[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
			Morris, J., Hansen, M., and R. Smith, "Privacy
			Considerations for Internet Protocols", RFC 6973,
			DOI 10.17487/RFC6973, July 2013,
			<http://www.rfc-editor.org/info/rfc6973>.
			[RFC7459] Thomson, M. and J. Winterbottom, "Representation of
			Uncertainty and Confidence in the Presence Information
			Data Format Location Object (PIDF-LO)", RFC 7459,
			DOI 10.17487/RFC7459, February 2015,
			<http://www.rfc-editor.org/info/rfc7459>.
	[RFC7665] Halpern, J., Ed., and C. Pignataro, Ed., "Service Function		[RFC7665] Halpern, J., Ed., and C. Pignataro, Ed., "Service Function
	Chaining (SFC) Architecture", RFC 7665,		Chaining (SFC) Architecture", RFC 7665,
	DOI 10.17487/RFC7665, October 2015,		DOI 10.17487/RFC7665, October 2015,
	<http://www.rfc-editor.org/info/rfc7665>.		<http://www.rfc-editor.org/info/rfc7665>.
	10. Authors' Addresses		11. Authors' Addresses
	Enke Chen		Enke Chen
	Cisco Systems		Cisco Systems
	170 W. Tasman Drive		170 W. Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	USA		USA
	Email: enkechen@cisco.com		Email: enkechen@cisco.com
	Naiming Shen		Naiming Shen
End of changes. 33 change blocks.
	43 lines changed or deleted		83 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/