idnits 2.17.1 draft-acee-ospf-geo-location-03.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 (October 28, 2016) is 2736 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: May 1, 2017 Cisco Systems 6 October 28, 2016 8 OSPF Extensions for Advertising/Signaling Geo Location Information 9 draft-acee-ospf-geo-location-03.txt 11 Abstract 13 This document specifies an OSPF Router Information (RI) TLV to 14 advertise the current Geo Coordinates of the OSPF router. For Point- 15 to-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. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on May 1, 2017. 39 Copyright Notice 41 Copyright (c) 2016 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2 58 2. OSPF Geo Coordinates TLV . . . . . . . . . . . . . . . . . . 2 59 3. Link Advertisement of the OSPF Geo-Coordinates . . . . . . . 4 60 4. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . . . 5 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 62 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 66 8.2. Informative References . . . . . . . . . . . . . . . . . 6 67 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 7 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 70 1. Introduction 72 This document specifies an OSPF Router Information (RI) [OSPF-RI] TLV 73 to advertise the current Geo Coordinates of the OSPF router. For 74 Point-to-Point (P2P)) and Point-to-Multi-Point (P2MP) networks, the 75 Geo 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. 81 1.1. Requirements Notation 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 85 document are to be interpreted as described in [RFC-KEYWORDS]. 87 2. OSPF Geo Coordinates TLV 89 The Geo Coordinates TLV can be used to advertise the current location 90 of an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] router using the OSPF Router 91 Information LSA [OSPF-RI]. The OSPF Router Information LSA can be 92 advertised in both link-scoped and area or AS scoped RI LSAs. The 93 fields specify the location of the OSPF router using the WGS-84 94 (World Geodetic System) reference coordinate system [WGS84]. The 95 value of the Geo Coordinates TLV consists of the following fields: 97 0 1 2 3 98 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 99 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 100 |U|N|E|A|M|R|K| Reserved | Location Uncertainty | 101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 | Lat Degrees | Latitude Milliseconds | 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | Long Degrees | Longitude Milliseconds | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | Altitude | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | Radius | Reserved | 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | .. Optional Sub-TLVs 111 +-+-+-+-+-+-+-+-+-.... 113 Where: 115 U-bit: If the U-bit is set, it indicates that the "Location 116 Uncertainty" field is specified. If the U-bit is clear, 117 it indicates the "Location Uncertainty" field is 118 unspecified. 120 N-bit: If the N-bit is set, it indicates the Latitude is 121 north relative to the Equator. If the N-bit is clear, 122 it indicates the Latitude is south of the Equator. 124 E-bit: If the E-bit is set, it indicates the Longitude is east 125 of the Prime Meridian. If the E-bit is clear, it indicates 126 the Longitude is west of the Prime Meridian. 128 A-bit: If the A-bit is set, it indicates the "Altitude" field is 129 specified. If the A-bit is clear, it indicates the 130 "Altitude" field is unspecified. 132 M-bit: If the M-bit is set, it indicates the "Altitude" is 133 specified in meters. If the M-bit is clear, it indicates 134 the "Altitude" is in centimeters. 136 R-bit: If the R-bit is set, it indicates the "Radius" field is 137 specified and the encoding is for a circular area. If 138 the R-bit is clear, it indicates the "Radius" field is 139 unspecified and the encoding is for a single point. 141 K-bit: If the K-bit is set, it indicates the "Radius" is specified 142 in kilometers. If the K-bit is clear, it indicates the 143 "Radius" is in meters. 145 Reserved: These bits are reserved. They SHOULD be set to 0 when 146 sending protocol packets and MUST be ignored when 147 receiving protocol packets. 149 Location Uncertainty: Unsigned 16-bit integer indicating the 150 number of centimeters of uncertainty for 151 the location. 153 Latitude Degrees: Unsigned 8-bit integer with a range of 0 - 90 154 degrees north or south of the Equator (northern 155 or southern hemisphere, respectively). 157 Latitude Milliseconds: Unsigned 24-bit integer with a range of 158 0 - 3,599,999 (i.e., less than 60 minutes). 160 Longitude Degrees: Unsigned 8-bit integer with a range of 0 - 180 161 degrees east or west of the Prime Meridian. 163 Longitude Milliseconds: Unsigned 24-bit integer with a range of 164 0 - 3,599,999 (i.e., less than 60 minutes). 166 Altitude: Signed 32-bit integer containing the Height relative to 167 sea level in centimeters or meters. A negative height 168 indicates that the location is below sea level. 170 Radius: Unsigned 16-bit integer containing the radius of a 171 circle centered at the specified coordinates. The radius 172 is specified in meters unless the K-bit is specified 173 indicating specification in kilometers. If the radius is 174 specified, the geo-coordinates specify the entire area 175 of the circle defined by the radius and center point. 176 While the use cases herein do not make use of this field, 177 future use cases may. 179 Optional Sub-TLVs: No additional Sub-TLVs are defined in this 180 document. 182 OSPF Geo Coordinates TLV 184 3. Link Advertisement of the OSPF Geo-Coordinates 186 When the Geo Coordinates are used for cost computation, the 187 coordinates need to be advertised on the link using the encoding 188 specified in Section 2. For this application, a link-scoped OSPF 189 Router Information (RI) [OSPF-RI] is advertised on each link where 190 geo-location cost computation is utilized. 192 When an OSPF router receives the Geo Coordinates TLV in a link-scoped 193 OSPF RI LSA from an adjacent neighbor, it can be used to calculate 194 the physical distance to neighbor. For P2P and P2MP networks, this 195 distance can be used to dynamically compute the cost of the link to 196 that neighbor. The mapping of the distance to advertised cost is not 197 specified in this document. However, all OSPF routers in the domain 198 SHOULD used the same algorithm. Computation of cost based on 199 physical distance can be useful both for autoconfiguration of these 200 networks types and dynamic cost computation when the routers are 201 moving. 203 The Geo location information can be statically provisioned or 204 dynamically acquired from a GPS capable device on the OSPF Router. 206 4. OSPFv2 Router Information (RI) Opaque LSA 208 The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF 209 Router Information (RI) LSA [OSPF-RI]. It then may be used for 210 applications such as traffic engineering (TE) and network management 211 (e.g., the Find-My-Router application). The details of such 212 applications are beyond the scope of this document. 214 5. Security Considerations 216 Since the Geo Location coordinates provide the exact location of the 217 OSPF router, disclosure will make the OSPF router more susceptible to 218 physical attacks. In situations where this is a concern (e.g., 219 military applications), confidentiality should be provided either 220 through a secure tunnel (e.g., [IP-ESP]) or protocol encryption 221 [OSPFV3-AUTH]. 223 Additionally, in some situations, the topology of the network is 224 considered proprietary information. With the Geo Location 225 coordinates, the physical topology, as well as the IP topology, can 226 be discerned from the OSPF Router Information (RI) LSA. In these 227 situations, confidentiality should be assured. 229 Security considerations for the base OSPF protocol are covered in 230 [OSPF] and [OSPFV3]. 232 6. Privacy Considerations 234 If the location of an OSPF router advertising geo location 235 coordinates as described herein can be directly correlated to an 236 individual, individuals, or an organization, the location of that 237 router should be considered sensitive and OSPF RI LSAs containing 238 such geo coordinates should be advertised confidentially as described 239 in Section 5. Additionally, OSPF network management facilities may 240 require added authorization to view the contents of OSPF RI LSAs 241 containing geo-Location TLVs. Refer to [PRIVACY] for more 242 information. 244 The Uncertainty and Confidence metrics for geo-location information 245 as described in [GEO-PIDF-LO] are not included in the Geo Coordinates 246 TLV. In a future document, these may be considered for inclusion 247 with additional Geo Location Sub-TLVs dependent on both on 248 requirements and adoption of [GEO-PIDF-LO]. 250 7. IANA Considerations 252 The document will require the following IANA actions: 254 1. A Router Information TLV type for the Geo Location TLV will be 255 allocated from the OSPF Router Information (RI) TLVs registry. 257 8. References 259 8.1. Normative References 261 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 263 [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 264 Shaffer, "Extensions to OSPF for Advertising Optional 265 Router Capabilities", RFC 7770, January 2016. 267 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 268 for IPv6", RFC 5340, July 2008. 270 [RFC-KEYWORDS] 271 Bradner, S., "Key words for use in RFC's to Indicate 272 Requirement Levels", BCP 14, RFC 2119, March 1997. 274 8.2. Informative References 276 [GEO-PIDF-LO] 277 Thomson, M. and J. Winterbottom, "Representation of 278 Uncertainty and Confidence in the Presence Information 279 Data Location Object (PIDF-LO)", RFC 7459, February 2015. 281 [IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC 282 4303, December 2005. 284 [LISP-GEO] 285 Farinacci, D., "LISP Geo-Coordinate Use-Cases", farinacci- 286 lisp-geo-02 (work in progress), October 2016. 288 [OSPFV3-AUTH] 289 Gupta, M. and S. Melam, "Authentication/Confidentiality 290 for OSPFv3", RFC 4552, June 2006. 292 [PRIVACY] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 293 Morris, J., Hansen, M., and R. Smith, "Privacy 294 Considerations", RFC 6973, July 2013. 296 [WGS84] National Imagery and Mapping Agency, "Department of 297 Defense World Geodetic System 1984, Third Edition", NIMA 298 TR83500.2, January 2000. 300 Appendix A. Acknowledgments 302 The RFC text was produced using Marshall Rose's xml2rfc tool. 304 The encoding of the Geo location is adapted from "LISP Geo- 305 Coordinates Use-Cases" [LISP-GEO]. We would like to thank the 306 author, Dino Farinacci, for subsequent discussions. 308 Thanks to Yi Yang for review and discussions of the Geo Coordinate 309 encoding. 311 The use-case for using OSPF to advertise the geo-location in OSPF was 312 first mentioned in an OSPF operator-defined TLV draft by Uma 313 Chunduri, Xiaohu Xu, Luis M. Contreras, Mohamed Boucadair, and Luay 314 Jalil. 316 Authors' Addresses 318 Acee Lindem (editor) 319 Cisco Systems 320 301 Midenhall Way 321 Cary, NC 27513 322 USA 324 Email: acee@cisco.com 326 Naiming Shen 327 Cisco Systems 328 821 Alder Drive 329 Milpitas, CA 95935 330 USA 332 Email: naiming@cisco.com 333 Enke Chen 334 Cisco Systems 335 821 Alder Drive 336 Milpitas, CA 95935 337 USA 339 Email: enkechen@cisco.com