idnits 2.17.1 draft-acee-ospf-geo-location-00.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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 12, 2016) is 2996 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 information found for draft-ietf-list-lcaf - is the name correct? Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). 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 15, 2016 Cisco Systems 6 February 12, 2016 8 OSPF Extensions for Advertising/Signaling Geo Location Information 9 draft-acee-ospf-geo-location-00.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 (P2)) 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 15, 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 . . . . . . . . . . . . . . . . . . . 4 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 66 7.2. Informative References . . . . . . . . . . . . . . . . . 5 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 (P2)) 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 Geo Coordinates TLV encoding is adapted from the format in 94 [LISP-CAF]. The value of the Geo Coordinates TLV consists of the 95 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 | Type | Length | 101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 |N| Latitude Degrees | Minutes | Seconds | 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 |E| Longitude Degrees | Minutes | Seconds | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | Altitude | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | .. Optional Sub-TLVs 109 +-+-+-+-+-+-+-+-+-.... 111 Type: TBD. 8 bits value, to be assigned by IANA. 113 Length: Variable. 8 bits value. The mandatory part is 12 octets. 115 N: Bit indicating North (set) or South (clear). 117 Latitude Degrees: Valid values range from 0 to 90 degrees above or 118 below the equator (northern or southern hemisphere, 119 respectively). 121 Latitude Minutes: Valid values range from 0 to 59. 123 Latitude Seconds: Valid values range from 0 to 59. 125 E: Bit indicating East (set) or West (clear). 127 Longitude Degrees: Value values are from 0 to 180 degrees right or 128 left of the Prime Meridian. 130 Longitude Minutes: Valid values range from 0 to 59. 132 Longitude Seconds: Valid values range from 0 to 59. 134 Altitude: Height relative to sea level in meters. This is a signed 135 integer meaning that the altitude could be below sea 136 level. A value of 0x7fffffff indicates no Altitude value 137 is encoded. 139 Optional Sub-TLVs: No additional Sub-TLVs are defined in this 140 document. 142 OSPF Geo Coordinates TLV 144 3. OSPF Geo Coordinates Link-Local-Signaling 146 The OSPF Geo Coordinates TLV may optionally be included in the Link- 147 Local-Signaling [LLS] data block appended to OSPF hello packets. 149 When an OSPF router receives the Geo Coordinates TLV in the LLS 150 extension from an adjacent neighbor, it can be used to calculate the 151 physical distance to neighbor. For P2P and P2MP networks, this 152 distance can be used to dynamically compute the cost of the link to 153 that neighbor. The mapping of the distance to advertised cost is a 154 local matter and is not specified in this document. Computation of 155 cost based on physical distance can be useful both for 156 autoconfiguration of these networks types and dynamic cost 157 computation when the routers are moving. 159 The Geo location information can be statically provisioned or 160 dynamically acquired from a GPS capable device on the OSPF Router. 162 4. OSPFv2 Router Information (RI) Opaque LSA 164 The OSPF Geo Coordinates TLV may optionally be advertised in the OSPF 165 Router Information (RI) LSA [OSPF-RI]. It then may be used for 166 applications such as traffic engineering (TE) and network management 167 (e.g., the Find-My-Router application). The details of such 168 applications are beyond the scope of this document. 170 5. Security Considerations 172 Since the Geo Location coordinates provide the exact location of the 173 OSPF router, disclosure will make the OSPF router more susceptible to 174 physical attacks. In situations where this is a concern (e.g., 175 military applications), confidentiality should be provided either 176 through a secure tunnel (e.g., [IP-ESP]) or protocol encryption 177 [OSPFV3-AUTH]. 179 Additionally, in some situations, the topology of the network is 180 considered proprietary information. With the Geo Location 181 coordinates, the physical topology, as well as the IP topology, can 182 be discerned from the OSPF Router Information (RI) LSA. In these 183 situations, confidentiality should be assured. 185 Security considerations for the base OSPF protocol are covered in 186 [OSPF] and [OSPFV3]. 188 6. IANA Considerations 190 The document will require two IANA actions: 192 1. An LLS Type TLV for the Geo Location TLV will be allocated from 193 the OSPF Link Local Signaling TLV Identifiers (LLS Types) 194 registry. 196 2. A Router Information TLV type for the Geo Location TLV will be 197 allocated from the OSPF Router Information (RI) TLVs registry. 199 7. References 201 7.1. Normative References 203 [LLS] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. 204 Young, "OSPF Link-local Signaling", RFC 5613, August 2009. 206 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 208 [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 209 Shaffer, "Extensions to OSPF for Advertising Optional 210 Router Capabilities", RFC 7770, January 2016. 212 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 213 for IPv6", RFC 5340, July 2008. 215 [RFC-KEYWORDS] 216 Bradner, S., "Key words for use in RFC's to Indicate 217 Requirement Levels", BCP 14, RFC 2119, March 1997. 219 7.2. Informative References 221 [IP-ESP] Kent, S., "IP Encapsulation Security Payload (ESP)", RFC 222 4303, December 2005. 224 [LISP-CAF] 225 Farinacci, D., Meyers, D., and J. Snijders, "LISP 226 Cananical Address Format (LCAF)", draft-ietf-list-lcaf- 227 11.txt (work in progress), September 2015. 229 [OSPFV3-AUTH] 230 Gupta, M. and S. Melam, "Authentication/Confidentiality 231 for OSPFv3", RFC 4552, June 2006. 233 Appendix A. Acknowledgments 235 The RFC text was produced using Marshall Rose's xml2rfc tool. 237 The encoding of the Geo location is adapted from the "Geo Coordinate 238 LISP Canonical Address Format" specified in the "LISP Canonical 239 Address Format (LCAF)". We would like to thank the authors of that 240 Document. 242 Authors' Addresses 244 Acee Lindem (editor) 245 Cisco Systems 246 301 Midenhall Way 247 Cary, NC 27513 248 USA 250 Email: acee@cisco.com 252 Naiming Shen 253 Cisco Systems 254 821 Alder Drive 255 Milpitas, CA 95935 256 USA 258 Email: naiming@cisco.com 260 Enke Chen 261 Cisco Systems 262 225 West Tasman Drive 263 San Jose, CA 95134 264 USA 266 Email: enkechen@cisco.com