idnits 2.17.1 draft-acee-ospf-geo-location-02.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 21, 2016) is 2744 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: April 24, 2017 Cisco Systems 6 October 21, 2016 8 OSPF Extensions for Advertising/Signaling Geo Location Information 9 draft-acee-ospf-geo-location-02.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 April 24, 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 . . . . . . . . . . 4 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 62 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 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 value of the Geo Coordinates TLV consists of the following fields: 95 0 1 2 3 96 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. Link Advertisement of the OSPF Geo-Coordinates 165 When the Geo Coordinates are used for cost computation, the 166 cooridinates need to be advertised on the link using the encoding 167 specified in Section 2. For this application, a link-scoped OSPF 168 Router Information (RI) [OSPF-RI] is advertised on each link where 169 geo-location cost computation is utilized. 171 When an OSPF router receives the Geo Coordinates TLV in a link-scoped 172 OSPF RI LSA from an adjacent neighbor, it can be used to calculate 173 the physical distance to neighbor. For P2P and P2MP networks, this 174 distance can be used to dynamically compute the cost of the link to 175 that neighbor. The mapping of the distance to advertised cost is not 176 specified in this document. However, all OSPF routers in the domain 177 SHOULD used the same algorithm. Computation of cost based on 178 physical distance can be useful both for autoconfiguration of these 179 networks types and dynamic cost computation when the routers are 180 moving. 182 The Geo location information can be statically provisioned or 183 dynamically acquired from a GPS capable device on the OSPF Router. 185 4. OSPFv2 Router Information (RI) Opaque LSA 187 The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF 188 Router Information (RI) LSA [OSPF-RI]. It then may be used for 189 applications such as traffic engineering (TE) and network management 190 (e.g., the Find-My-Router application). The details of such 191 applications are beyond the scope of this document. 193 5. Security Considerations 195 Since the Geo Location coordinates provide the exact location of the 196 OSPF router, disclosure will make the OSPF router more susceptible to 197 physical attacks. In situations where this is a concern (e.g., 198 military applications), confidentiality should be provided either 199 through a secure tunnel (e.g., [IP-ESP]) or protocol encryption 200 [OSPFV3-AUTH]. 202 Additionally, in some situations, the topology of the network is 203 considered proprietary information. With the Geo Location 204 coordinates, the physical topology, as well as the IP topology, can 205 be discerned from the OSPF Router Information (RI) LSA. In these 206 situations, confidentiality should be assured. 208 Security considerations for the base OSPF protocol are covered in 209 [OSPF] and [OSPFV3]. 211 6. Privacy Considerations 213 If the location of an OSPF router advertising geo location 214 coordinates as described herein can be directly correlated to an 215 individual, individuals, or an organization, the location of that 216 router should be considered sensitive and OSPF RI LSAs containing 217 such geo coordinates should be advertised confidentially as described 218 in Section 5. Additionally, OSPF network management facilities may 219 require added authorization to view the contents of OSPF RI LSAs 220 containing geo-Location TLVs. Refer to [PRIVACY] for more 221 information. 223 The Uncertainty and Confidence metrics for geo-location information 224 as described in [GEO-PIDF-LO] are not included in the Geo Coordinates 225 TLV. In a future document, these may be considered for inclusion 226 with additional Geo Location Sub-TLVs dependent on both on 227 requirements and adoption of [GEO-PIDF-LO]. 229 7. IANA Considerations 231 The document will require the following IANA actions: 233 1. A Router Information TLV type for the Geo Location TLV will be 234 allocated from the OSPF Router Information (RI) TLVs registry. 236 8. References 237 8.1. Normative References 239 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 241 [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 242 Shaffer, "Extensions to OSPF for Advertising Optional 243 Router Capabilities", RFC 7770, January 2016. 245 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 246 for IPv6", RFC 5340, July 2008. 248 [RFC-KEYWORDS] 249 Bradner, S., "Key words for use in RFC's to Indicate 250 Requirement Levels", BCP 14, RFC 2119, March 1997. 252 8.2. Informative References 254 [GEO-PIDF-LO] 255 Thomson, M. and J. Winterbottom, "Representation of 256 Uncertainty and Confidence in the Presence Information 257 Data Location Object (PIDF-LO)", RFC 7459, February 2015. 259 [IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC 260 4303, December 2005. 262 [OSPFV3-AUTH] 263 Gupta, M. and S. Melam, "Authentication/Confidentiality 264 for OSPFv3", RFC 4552, June 2006. 266 [PRIVACY] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 267 Morris, J., Hansen, M., and R. Smith, "Privacy 268 Considerations", RFC 6973, July 2013. 270 Appendix A. Acknowledgments 272 The RFC text was produced using Marshall Rose's xml2rfc tool. 274 The encoding of the Geo location is adapted from the "Geo Coordinate 275 LISP Canonical Address Format" specified in the "LISP Canonical 276 Address Format (LCAF)". We would like to thank the authors of that 277 Document and particularily Dino Farinacci for subsequent discussions. 279 Thanks to Yi Yang for review and discussions of the Geo Coordinate 280 encoding. 282 The use-case for using OSPF to advertise the geo-location in OSPF was 283 first mentioned in an OSPF operator-defined TLV draft by Uma 284 Chunduri, Xiaohu Xu, Luis M. Contreras, Mohamed Boucadair, and Luay 285 Jalil. 287 Authors' Addresses 289 Acee Lindem (editor) 290 Cisco Systems 291 301 Midenhall Way 292 Cary, NC 27513 293 USA 295 Email: acee@cisco.com 297 Naiming Shen 298 Cisco Systems 299 821 Alder Drive 300 Milpitas, CA 95935 301 USA 303 Email: naiming@cisco.com 305 Enke Chen 306 Cisco Systems 307 821 Alder Drive 308 Milpitas, CA 95935 309 USA 311 Email: enkechen@cisco.com