idnits 2.17.1 draft-acee-ospf-geo-location-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 26, 2016) is 2979 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Lindem, Ed. 3 Internet-Draft N. Shen 4 Intended status: Standards Track E. Chen 5 Expires: August 29, 2016 Cisco Systems 6 February 26, 2016 8 OSPF Extensions for Advertising/Signaling Geo Location Information 9 draft-acee-ospf-geo-location-01.txt 11 Abstract 13 This document specifies an OSPF Link-Local-Signaling (LLS) TLV to 14 signal the current Geo Coordinates of the OSPF router. For Point-to- 15 Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo 16 Coordinates can be used to dynamically computing the cost to 17 neighbors. This is useful both from the standpoint of auto- 18 configuration and situations where the OSPF routers are moving. The 19 Geo Coordinates are also useful for other applications such as 20 Traffic Engineering (TE) and network management and can be advertised 21 in the OSPF Router Information (RI) LSA. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on August 29, 2016. 40 Copyright Notice 42 Copyright (c) 2016 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2 59 2. OSPF Geo Coordinates TLV . . . . . . . . . . . . . . . . . . 2 60 3. OSPF Geo Coordinates Link-Local-Signaling . . . . . . . . . . 4 61 4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 4 62 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 66 7.2. Informative References . . . . . . . . . . . . . . . . . 6 67 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 70 1. Introduction 72 This document specifies an OSPF Link-Local-Signaling (LLS) TLV to 73 signal the current Geo Coordinates of the OSPF router. For Point-to- 74 Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the Geo 75 Coordinates can be used to dynamically computing the cost to 76 neighbors. This is useful both from the standpoint of auto- 77 configuration and situations where the OSPF routers are moving. The 78 Geo Coordinates are also useful for other applications such as 79 Traffic Engineering (TE) and network management and can be advertised 80 in the OSPF Router Information (RI) LSA [OSPF-RI]. 82 1.1. Requirements Notation 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in [RFC-KEYWORDS]. 88 2. OSPF Geo Coordinates TLV 90 The Geo Coordinates TLV can be used to advertise the current location 91 of an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] router using either OSPF Link- 92 Local-Signaling [LLS] or the OSPF Router Information LSA [OSPF-RI]. 93 The value of the Geo Coordinates TLV consists of the following 94 fields: 96 0 1 2 3 97 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 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 |U|N|E|A|M| Reserved | Location Uncertainty | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 |Latitude Degr. | Latitude Milliseconds | 102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 103 |Longitude Degr.| Longitude Milliseconds | 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | Altitude | 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | .. Optional Sub-TLVs 108 +-+-+-+-+-+-+-+-+-.... 110 Where: 112 U-bit: If the U-bit is set, it indicates that the "Location 113 Uncertainty" field is specified. If the U-bit is clear, 114 it indicates the "Location Uncertainty" field is 115 unspecified. 117 N-bit: If the N-bit is set, it indicates the Latitude is 118 north relative to the Equator. If the N-bit is clear, 119 it indicates the Latitude is south of the Equator. 121 E-bit: If the E-bit is set, it indicates the Longitude is east 122 of the Prime Meridian. If the E-bit is clear, it indicates 123 the Longitude is west of the Prime Meridian. 125 A-bit: If the A-bit is set, it indicates the "Altitude" field is 126 specified. If the A-bit is clear, it indicates the 127 "Altitude" field is unspecified. 129 M-bit: If the M-bit is set, it indicates the "Altitude" is 130 specified in meters. If the M-bit is clear, it indicates 131 the "Altitude" is in centimeters. 133 Reserved: These bits are reserved. They SHOULD be set to 0 when 134 sending protocol packets and MUST be ignored when 135 receiving protocol packets. 137 Location Uncertainty: Unsigned 16-bit integer indicating the 138 number of centimeters of uncertainty for 139 the location. 141 Latitude Degrees: Unsigned 8-bit integer with a range of 0 - 90 142 degrees north or south of the Equator (northern 143 or southern hemisphere, respectively). 145 Latitude Milliseconds: Unsigned 24-bit integer with a range of 146 0 - 3,599,999 (i.e., less than 60 minutes). 148 Longitude Degrees: Unsigned 8-bit integer with a range of 0 - 180 149 degrees east or west of the Prime Meridian. 151 Longitude Milliseconds: Unsigned 24-bit integer with a range of 152 0 - 3,599,999 (i.e., less than 60 minutes). 154 Altitude: Signed 32-bit integer containing the Height relative to 155 sea level in centimeters or meters. A negative height 156 indicates that the location is below sea level. 158 Optional Sub-TLVs: No additional Sub-TLVs are defined in this 159 document. 161 OSPF Geo Coordinates TLV 163 3. OSPF Geo Coordinates Link-Local-Signaling 165 The OSPF Geo Coordinates TLV may optionally be included in the Link- 166 Local-Signaling [LLS] data block appended to OSPF hello packets. 168 When an OSPF router receives the Geo Coordinates TLV in the LLS 169 extension from an adjacent neighbor, it can be used to calculate the 170 physical distance to neighbor. For P2P and P2MP networks, this 171 distance can be used to dynamically compute the cost of the link to 172 that neighbor. The mapping of the distance to advertised cost is a 173 local matter and is not specified in this document. Computation of 174 cost based on physical distance can be useful both for 175 autoconfiguration of these networks types and dynamic cost 176 computation when the routers are moving. 178 The Geo location information can be statically provisioned or 179 dynamically acquired from a GPS capable device on the OSPF Router. 181 4. OSPFv2 Router Information (RI) Opaque LSA 183 The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF 184 Router Information (RI) LSA [OSPF-RI]. It then may be used for 185 applications such as traffic engineering (TE) and network management 186 (e.g., the Find-My-Router application). The details of such 187 applications are beyond the scope of this document. 189 5. Security Considerations 191 Since the Geo Location coordinates provide the exact location of the 192 OSPF router, disclosure will make the OSPF router more susceptible to 193 physical attacks. In situations where this is a concern (e.g., 194 military applications), confidentiality should be provided either 195 through a secure tunnel (e.g., [IP-ESP]) or protocol encryption 196 [OSPFV3-AUTH]. 198 Additionally, in some situations, the topology of the network is 199 considered proprietary information. With the Geo Location 200 coordinates, the physical topology, as well as the IP topology, can 201 be discerned from the OSPF Router Information (RI) LSA. In these 202 situations, confidentiality should be assured. 204 Security considerations for the base OSPF protocol are covered in 205 [OSPF] and [OSPFV3]. 207 6. IANA Considerations 209 The document will require two IANA actions: 211 1. An LLS Type TLV for the Geo Location TLV will be allocated from 212 the OSPF Link Local Signaling TLV Identifiers (LLS Types) 213 registry. 215 2. A Router Information TLV type for the Geo Location TLV will be 216 allocated from the OSPF Router Information (RI) TLVs registry. 218 7. References 220 7.1. Normative References 222 [LLS] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. 223 Young, "OSPF Link-local Signaling", RFC 5613, August 2009. 225 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 227 [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 228 Shaffer, "Extensions to OSPF for Advertising Optional 229 Router Capabilities", RFC 7770, January 2016. 231 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 232 for IPv6", RFC 5340, July 2008. 234 [RFC-KEYWORDS] 235 Bradner, S., "Key words for use in RFC's to Indicate 236 Requirement Levels", BCP 14, RFC 2119, March 1997. 238 7.2. Informative References 240 [IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC 241 4303, December 2005. 243 [OSPFV3-AUTH] 244 Gupta, M. and S. Melam, "Authentication/Confidentiality 245 for OSPFv3", RFC 4552, June 2006. 247 Appendix A. Acknowledgments 249 The RFC text was produced using Marshall Rose's xml2rfc tool. 251 The encoding of the Geo location is adapted from the "Geo Coordinate 252 LISP Canonical Address Format" specified in the "LISP Canonical 253 Address Format (LCAF)". We would like to thank the authors of that 254 Document and particularily Dino Farinacci for subsequent discussions. 256 Thanks to Yi Yang for review and discussions of the Geo Coordinate 257 encoding. 259 The use-case for using OSPF to advertise the geo-location in OSPF was 260 first mentioned in an OSPF operator-defined TLV draft by Uma 261 Chunduri, Xiaohu Xu, Luis M. Contreras, Mohamed Boucadair, and Luay 262 Jalil. 264 Authors' Addresses 266 Acee Lindem (editor) 267 Cisco Systems 268 301 Midenhall Way 269 Cary, NC 27513 270 USA 272 Email: acee@cisco.com 274 Naiming Shen 275 Cisco Systems 276 821 Alder Drive 277 Milpitas, CA 95935 278 USA 280 Email: naiming@cisco.com 281 Enke Chen 282 Cisco Systems 283 821 Alder Drive 284 Milpitas, CA 95935 285 USA 287 Email: enkechen@cisco.com