Networking Working Group N. Shen, Ed. Internet-Draft E. Chen Intended status: Standards Track A. Lindem Expires: September 2, 2016 Cisco Systems March 1, 2016 Carrying Geo Coordinates Information In IS-IS draft-shen-isis-geo-coordinates-01 Abstract This document defines a new IS-IS TLV which carries the Geo Coordinates information of the system. The Geo Coordinates information can be used by IS-IS routing or by any applications. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 2, 2016. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Shen, et al. Expires September 2, 2016 [Page 1] Internet-Draft IS-IS Geo Location March 2016 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Packet Encoding . . . . . . . . . . . . . . . . . . . . . . . 3 3. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 7. Document Change Log . . . . . . . . . . . . . . . . . . . . . 5 7.1. Changes to draft-shen-isis-geo-coordinates-01.txt . . . . 5 7.2. Changes to draft-shen-isis-geo-coordinates-00.txt . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction The IS-IS routing protocol defined by [ISO10589] has been widely deployed in various networks. The Geo Coordinates information can be useful, particularly within the wide area networks for numerous applications. Similar to the Dynamic Hostname defined in [RFC5301], the Geo Coordinates can also be used for network management purposes. In the case of BGP speakers setting the outbound "MED" value in route advertisement to neighbors, a local policy can be defined to evaluate the physical location or physical region of the BGP nexthops. In the case of IGP point-to-multiple operations [I-D.lamparter-isis-p2mp], [RFC6845], the local system configuration can be greatly simplified if the outbound metric to remote neighbors can be generated automatically based on this Geo Location of the IGP neighbors. In the application where IS-IS neighbors are on the same "sub-net" but over the WAN network, this Geo Location information may be used for equal-cost or unequal-cost load sharing on the local system. This enables location based operation on anycast IP prefixes and DMZ gateways across the WAN environment. For the traffic matrix using the Geo Coordinates within the routing domain, instead of a collection of IP nexthops which might be translated into locations, this enables automatic region to region traffic pattern aggregation. This document describes the IS-IS protocol carrying the Geo Coordinates information in a new TLV. This TLV can be distributed Shen, et al. Expires September 2, 2016 [Page 2] Internet-Draft IS-IS Geo Location March 2016 within the node's LSP or inside the IIH PDU. The exact mechanism each application uses this information is outside the scope of this document. 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Packet Encoding This Geo Coordinates extension introduces one TLV for IS-IS LSP PDU and for Hello (IIH) PDU. The code of the TLV is described in the IANA Considerations section of the document. The fields specify the location of the system using WGS-84 (World Geodetic System) reference coordinate system [WGS84]. The value of the Geo Coordinates TLV consists of the following fields: 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Latitude Degr. | Latitude Milliseconds | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Longitude Degr.| Longitude Milliseconds | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Altitude | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | .. Optional Sub-TLVs +-+-+-+-+-+-+-+-+-.... Type: TBD. 8 bits value, to be assigned by IANA. Length: Variable. 8 bits value. The mandatory part is 16 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: 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. 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 Longitude is west of the Prime Meridian. Shen, et al. Expires September 2, 2016 [Page 3] Internet-Draft IS-IS Geo Location March 2016 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. 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. Reserved: These bits are reserved. They SHOULD be set to 0 when sending protocol packets and MUST be ignored when receiving protocol packets. Location Uncertainty: Unsigned 16-bit integer indicating the number of centimeters of uncertainty for the location. Latitude Degrees: Unsigned 8-bit integer with a range of 0 - 90 degrees north or south of the Equator (northern or southern hemisphere, respectively). Latitude Milliseconds: Unsigned 24-bit integer with a range of 0 - 3,599,999 (i.e., less than 60 minutes). Longitude Degrees: Unsigned 8-bit integer with a range of 0 - 180 degrees east or west of the Prime Meridian. 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-TLV: Not defined in this document, for future extension related to the Geo Coordinates information. 3. Operations This IS-IS Geo Coordinates TLV can be optionally included in the node's LSP, and it is recommended to be in the LSP fragment zero. This TLV can also be optionally included in the IIH PDU. This can be useful when the application is setting the outbound p2mp circuit metric based on the neighbor's location. This can also be used in the Spine-Leaf extension [I-D.shen-isis-spine-leaf-ext] where there is no LSP being flooded into the leaf nodes. The Geo location information can be statically provisioned on the system, or it can be dynamically acquired from the GPS capable device on the system. Shen, et al. Expires September 2, 2016 [Page 4] Internet-Draft IS-IS Geo Location March 2016 4. IANA Considerations A new TLV codepoint is defined in this document and needs to be assigned by IANA from the "IS-IS TLV Codepoints" registry. It is referred to as the Geo Coordinates TLV. This TLV is only to be optionally inserted in the LSP PDU and the IIH PDU. This document does not propose any sub-TLV out of this Geo Coordinates TLV. Value Name IIH LSP SNP Purge ----- --------------------- --- --- --- ----- TBD Geo Coordinates y y n n 5. Security Considerations Since the Geo Location coordinates provide the exact location of the routing devices, disclosure may make the IS-IS devices more susceptible to physical attacks. In situations where this is a concern (e.g., in military applications, or the topology of the network is considered proprietary information), the implementation MUST allow the Geo Location extension to be removed from the IS-IS advertisement. Security concerns for the base IS-IS are addressed in [ISO10589], [RFC5304], [RFC5310], and [RFC7602]. 6. Acknowledgments The encoding of the Geo location is adapted from the "Geo Coordinate LISP Canonical Address Format" specified in the "LISP Canonical Address Format (LCAF)". We would like to thank the authors of that Document and particularly Dino Farinacci for subsequent discussions. Thanks to Les Ginsberg, Yi Yang, and Joe Hildebrand for commenting and discussions of Geo Coordinates precision encoding. Thanks to David Ward for commenting on attack vector in relation to this new capability of IS-IS. 7. Document Change Log 7.1. Changes to draft-shen-isis-geo-coordinates-01.txt o The 01 version submitted in February 2016. o Change Geo Location encoding to have better precision and to include uncertainty information. o Added the discussion in security section for the awareness of increased probability in attack vector. Shen, et al. Expires September 2, 2016 [Page 5] Internet-Draft IS-IS Geo Location March 2016 7.2. Changes to draft-shen-isis-geo-coordinates-00.txt o Initial version of the draft is published in February 2016. 8. References 8.1. Normative References [I-D.lamparter-isis-p2mp] Franke, C., Lamparter, D., and C. Hopps, "IS-IS Point-to- Multipoint operation", draft-lamparter-isis-p2mp-01 (work in progress), October 2015. [I-D.shen-isis-spine-leaf-ext] Shen, N. and S. Thyamagundalu, "IS-IS Routing for Spine- Leaf Topology", draft-shen-isis-spine-leaf-ext-00 (work in progress), November 2015. [ISO10589] ISO "International Organization for Standardization", "Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473), ISO/IEC 10589:2002, Second Edition.", Nov 2002. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC5301] McPherson, D. and N. Shen, "Dynamic Hostname Exchange Mechanism for IS-IS", RFC 5301, DOI 10.17487/RFC5301, October 2008, . [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic Authentication", RFC 5304, DOI 10.17487/RFC5304, October 2008, . [RFC5310] Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., and M. Fanto, "IS-IS Generic Cryptographic Authentication", RFC 5310, DOI 10.17487/RFC5310, February 2009, . [RFC6845] Sheth, N., Wang, L., and J. Zhang, "OSPF Hybrid Broadcast and Point-to-Multipoint Interface Type", RFC 6845, DOI 10.17487/RFC6845, January 2013, . Shen, et al. Expires September 2, 2016 [Page 6] Internet-Draft IS-IS Geo Location March 2016 [RFC7602] Chunduri, U., Lu, W., Tian, A., and N. Shen, "IS-IS Extended Sequence Number TLV", RFC 7602, DOI 10.17487/RFC7602, July 2015, . 8.2. Informative References [WGS84] National Imagery and Mapping Agency, "Department of Defense World Geodetic System 1984, Third Edition", NIMA TR8350.2, January 2000. Authors' Addresses Naiming Shen (editor) Cisco Systems 560 McCarthy Blvd. Milpitas, CA 95035 US Email: naiming@cisco.com Enke Chen Cisco Systems 560 McCarthy Blvd. Milpitas, CA 95035 US Email: enkechen@cisco.com Acee Linden Cisco Systems 301 Midenhall Way Cary, NC 27513 US Email: acee@cisco.com Shen, et al. Expires September 2, 2016 [Page 7]