Network Working Group A. Lindem, Ed. Internet-Draft N. Shen Intended status: Standards Track E. Chen Expires: August15,29, 2016 Cisco Systems February12,26, 2016 OSPF Extensions for Advertising/Signaling Geo Location Informationdraft-acee-ospf-geo-location-00.txtdraft-acee-ospf-geo-location-01.txt Abstract This document specifies an OSPF Link-Local-Signaling (LLS) TLV to signal the current Geo Coordinates of the OSPF router. For Point-to- Point(P2))(P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo Coordinates can be used to dynamically computing the cost to neighbors. This is useful both from the standpoint of auto- configuration and situations where the OSPF routers are moving. The Geo Coordinates are also useful for other applications such as Traffic Engineering (TE) and network management and can be advertised in the OSPF Router Information (RI) LSA. 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 August15,29, 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2 2. OSPF Geo Coordinates TLV . . . . . . . . . . . . . . . . . . 2 3. OSPF Geo Coordinates Link-Local-Signaling . . . . . . . . . . 4 4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . .45 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . .56 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction This document specifies an OSPF Link-Local-Signaling (LLS) TLV to signal the current Geo Coordinates of the OSPF router. For Point-to- Point(P2))(P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo Coordinates can be used to dynamically computing the cost to neighbors. This is useful both from the standpoint of auto- configuration and situations where the OSPF routers are moving. The Geo Coordinates are also useful for other applications such as Traffic Engineering (TE) and network management and can be advertised in the OSPF Router Information (RI) LSA [OSPF-RI]. 1.1. Requirements Notation 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-KEYWORDS]. 2. OSPF Geo Coordinates TLV The Geo Coordinates TLV can be used to advertise the current location of an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] router using either OSPF Link- Local-Signaling [LLS] or the OSPF Router Information LSA [OSPF-RI]. TheGeo Coordinates TLV encoding is adapted from the format in [LISP-CAF]. Thevalue of the Geo Coordinates TLV consists of the following fields: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |U|N|E|A|M| Reserved |Type | LengthLocation Uncertainty | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+|N| Latitude Degrees | Minutes|Latitude Degr. |SecondsLatitude Milliseconds | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+|E||Longitude Degr.| LongitudeDegrees | Minutes | SecondsMilliseconds | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Altitude | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | .. Optional Sub-TLVs +-+-+-+-+-+-+-+-+-....Type: TBD. 8Where: 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. 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 bitsvalue,are reserved. They SHOULD be set to 0 when sending protocol packets and MUST beassigned by IANA. Length: Variable. 8 bits value. The mandatory part is 12 octets. N: Bitignored when receiving protocol packets. Location Uncertainty: Unsigned 16-bit integer indicatingNorth (set) or South (clear).the number of centimeters of uncertainty for the location. Latitude Degrees:Valid valuesUnsigned 8-bit integer with a rangefromof 0to- 90 degreesabovenorth orbelowsouth of theequatorEquator (northern or southern hemisphere, respectively). LatitudeMinutes: Valid values range from 0 to 59. Latitude Seconds: Valid valuesMilliseconds: Unsigned 24-bit integer with a rangefromof 0to 59. E: Bit indicating East (set) or West (clear).- 3,599,999 (i.e., less than 60 minutes). Longitude Degrees:Value values are fromUnsigned 8-bit integer with a range of 0to- 180 degreesrighteast orleftwest of the Prime Meridian. LongitudeMinutes: Valid values range from 0 to 59. Longitude Seconds: Valid valuesMilliseconds: Unsigned 24-bit integer with a rangefromof 0to 59.- 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.This is a signed integer meaningA negative height indicates that thealtitude could belocation is below sea level.A value of 0x7fffffff indicates no Altitude value is encoded.Optional Sub-TLVs: No additional Sub-TLVs are defined in this document. OSPF Geo Coordinates TLV 3. OSPF Geo Coordinates Link-Local-Signaling The OSPF Geo Coordinates TLV may optionally be included in the Link- Local-Signaling [LLS] data block appended to OSPF hello packets. When an OSPF router receives the Geo Coordinates TLV in the LLS extension from an adjacent neighbor, it can be used to calculate the physical distance to neighbor. For P2P and P2MP networks, this 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 local matter and is not specified in this document. Computation of cost based on physical distance can be useful both for autoconfiguration of these networks types and dynamic cost computation when the routers are moving. The Geo location information can be statically provisioned or dynamically acquired from a GPS capable device on the OSPF Router. 4. OSPFv2 Router Information (RI) Opaque LSA The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF Router Information (RI) LSA [OSPF-RI]. It then may be used for applications such as traffic engineering (TE) and network management (e.g., the Find-My-Router application). The details of such applications are beyond the scope of this document. 5. Security Considerations Since the Geo Location coordinates provide the exact location of the OSPF router, disclosure will make the OSPF router more susceptible to physical attacks. In situations where this is a concern (e.g., military applications), confidentiality should be provided either through a secure tunnel (e.g., [IP-ESP]) or protocol encryption [OSPFV3-AUTH]. Additionally, in some situations, the topology of the network is considered proprietary information. With the Geo Location coordinates, the physical topology, as well as the IP topology, can be discerned from the OSPF Router Information (RI) LSA. In these situations, confidentiality should be assured. Security considerations for the base OSPF protocol are covered in [OSPF] and [OSPFV3]. 6. IANA Considerations The document will require two IANA actions: 1. An LLS Type TLV for the Geo Location TLV will be allocated from the OSPF Link Local Signaling TLV Identifiers (LLS Types) registry. 2. A Router Information TLV type for the Geo Location TLV will be allocated from the OSPF Router Information (RI) TLVs registry. 7. References 7.1. Normative References [LLS] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. Young, "OSPF Link-local Signaling", RFC 5613, August 2009. [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. Shaffer, "Extensions to OSPF for Advertising Optional Router Capabilities", RFC 7770, January 2016. [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, July 2008. [RFC-KEYWORDS] Bradner, S., "Key words for use in RFC's to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 7.2. Informative References [IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC 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] Gupta, M. and S. Melam, "Authentication/Confidentiality for OSPFv3", RFC 4552, June 2006. Appendix A. Acknowledgments The RFC text was produced using Marshall Rose's xml2rfc tool. 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 thatDocument.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 Acee Lindem (editor) Cisco Systems 301 Midenhall Way Cary, NC 27513 USA Email: acee@cisco.com Naiming Shen Cisco Systems 821 Alder Drive Milpitas, CA 95935 USA Email: naiming@cisco.com Enke Chen Cisco Systems225 West Tasman821 Alder DriveSan Jose,Milpitas, CA9513495935 USA Email: enkechen@cisco.com