idnits 2.17.1 draft-randriamasy-alto-cellular-adresses-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 5, 2018) is 2243 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ALTO S. Randriamasy 3 Internet-Draft Nokia-Bell-labs 4 Intended status: Experimental March 5, 2018 5 Expires: September 6, 2018 7 ALTO cellular addresses 8 draft-randriamasy-alto-cellular-adresses-02 10 Abstract 12 This draft proposes to use the cellular address format composed of 13 elements as specified by 3GPP and called ECGI. ECGI stands for 14 E-UTRAN Cell Global Identifier and is used in Public Land Mobile 15 Networks based on E-UTRAN. 17 Requirements Language 19 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 21 document are to be interpreted as described in RFC 2119 [RFC2119]. 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 https://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 September 6, 2018. 40 Copyright Notice 42 Copyright (c) 2018 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 (https://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 2. Relevant ALTO services and documents . . . . . . . . . . . . 3 59 3. Cell addresses, ALTO Address types and ALTO Entity Domain 60 names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. ALTO Address Type for cellular networks . . . . . . . . . 4 62 3.2. ALTO Entity Domain for cellular networks . . . . . . . . 4 63 3.3. Consistency between ALTO Entity Domain and ALTO Address 64 Type . . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 4. Proposed format for ALTO cell identifiers . . . . . . . . . . 5 66 4.1. Endpoint address canonical string format . . . . . . . . 5 67 4.2. ALTO Cell Id formats . . . . . . . . . . . . . . . . . . 5 68 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 71 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 72 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 73 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 74 9.2. Informative References . . . . . . . . . . . . . . . . . 7 75 Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 8 76 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 78 1. Introduction 80 Cellular networks are present in a number of use cases investigated 81 in the ALTO WG and it is useful to specify a format for Cellular 82 addresses. In these cases, Endpoints, PIDs and entities may be 83 cells. In order to specify services such as Network Maps, Cost Maps, 84 Endpoint property or Property Maps, it is necessary to order to 85 specify an ALTO format for Cell addresses. 87 For the sake of efficiency, a preferred option is to use the cell 88 identifier format as specified by 3GPP [TS 36.300] and called ECGI, 89 as already proposed in [draft-rauschenbach-alto-wireless-access-00] 90 and in other discussions. ECGI stands for E-UTRAN Cell Global 91 Identifier and is used in Public Land Mobile Networks based on 92 E-UTRAN, see [TS 36.331]. 94 The purpose of this document is to be completed by the ALTO WG and in 95 particular: 97 - Amend and finalize the specification for the ALTO Cell identifier 98 format proposed in the present version, 100 - define a placeholder for this specification, identify related ALTO 101 features and ALTO WG documents. 103 2. Relevant ALTO services and documents 105 Particular services and drafts where an ALTO address type for 106 cellular networks is needed include: 108 o - Endpoint property service: extended to allow endpoints to be 109 cells on which properties can be requested, 111 o - (Filtered) Cost Map Service: where PIDs can be cells within and 112 among which cost values can be requested, see also[draft- 113 randriamasy-alto-cost-context-01], 115 o - "Mobility Network Models in ALTO" defined in [draft-bertz-alto- 116 mobilitynets] propose to identify network points of attachment 117 (PoA) such as cells to PIDs. 119 o - "ALTO Performance Cost Metrics": being defined in [draft-ietf- 120 alto-performance-metrics-01], they will be extended to performance 121 costs in cellular networks, 123 o - "Extensible Property Maps for the ALTO Protocol", being defined 124 in [draft-ietf-alto-unified-props-new] are applicable to entities 125 that may be cells which are identified by their addresses. In 126 this document a domain identifier for cells will need to be 127 accordingly defined, and the entity domain identifier "ecgi" is 128 proposed. 130 3. Cell addresses, ALTO Address types and ALTO Entity Domain names 132 This section reflects ALTO WG discussions. The ALTO Address Type 133 Registry is detailed in Section 14.4 of RFC7285 specifying the base 134 ALTO protocol. It currently lists ALTO address types "ipv4" and 135 "ipv6". These ALTO address types can be used in the Endpoint 136 Property Service and the Endpoint Cost Service. They can also be 137 used to list the endpoints covered by a PID. The ALTO base protocol 138 however does not preclude other address types, See RFC7285, section 139 2.2 Endpoint Address. 141 The draft [draft-ietf-alto-unified-props-new] introduces and 142 specifies two new information services called Property Map and 143 Filtered Property Maps. They specify two media types, called "alto- 144 propmap+json" and "alto-propmapparams+json". A Property Map exposes 145 values of properties that are defined on Entities, where an Entity is 146 an object that extends the scope of an Endpoint having an individual 147 IP address to groups of Endpoints, PIDs, network elements abstracted 148 from one or more network elements of arbitrary nature. An Entity has 149 a unique address or name and is defined as belonging to a Domain that 150 has a unique identifier. To this end, 151 [draft-ietf-alto-unified-props-new] specifies an Entity Domain 152 Registry. An entity can thus potentially be a cell. 154 Example entities are Endpoints with addresses in the ipv4 or ipv6 155 domain, or PIDs with a name in the "pid" domain. 157 The draft points out that that "Entity domains and property names are 158 extensible. New domains can be defined without revising the messages 159 defined in this document, in the same way that new cost metrics and 160 new endpoint properties can be defined without revising the messages 161 defined by the ALTO protocol." 163 As a consequence, RFC7285 and draft 164 [draft-ietf-alto-unified-props-new] provide the background to allow 165 Endpoints and Entities to be cells with well-specified addresses. 167 3.1. ALTO Address Type for cellular networks 169 Registering cellular addresses in the ALTO Address Type Registry 170 allows conveying Endpoint Costs and Properties and (Filtered) Cost 171 Maps with PIDs and Endpoints being cells. 173 RFC7285 specifies endpoint address formats for ipv4 and ipv6 and the 174 purpose of this draft is to agree on a format for cellular endpoints. 175 When a cell is mapped to a PID, say "MyCell3" the ALTO Cell Id will 176 be used to specify the endpoints within this PID. 178 Whereas IP addresses are associated to domains ipv4 and ipv6, a Cell 179 Id will be associated to the domain "ecgi". 181 The domain name "ecgi" stems from the term ECGI -- E-UTRAN Cell 182 Global Identifier, defined in 3GPP. 184 3.2. ALTO Entity Domain for cellular networks 186 Applications may want to query (Filtered) Property Maps on Cellular 187 Networks or on networks comprising cells. In which case cells would 188 have to be identified as Entities with an entity address specific to 189 a domain registered in ALTO Entity Domain specified in 190 [draft-ietf-alto-unified-props-new]. 192 The domain "ecgi" is suitable for Entities as well. 194 3.3. Consistency between ALTO Entity Domain and ALTO Address Type 196 Actually, the cell address format proposed in section Section 4 is 197 suitable for both Endpoints and Entities. Likewise, ipv4 and ipv6 198 addresses. Whereas cellular and IP Endpoint addresses can also be 199 Entity addresses, an Entity is not necessarily an Endpoint. This is 200 the case for instance for entities like PIDs or ANEs. Therefore 201 there is a consistency issue to be solved, and this is done in the 202 ALTO Entity Domain specification of the draft 203 [draft-ietf-alto-unified-props-new]. 205 4. Proposed format for ALTO cell identifiers 207 4.1. Endpoint address canonical string format 209 'ecgi:' MCC '.' MNC ':' ECI 211 Where: 213 o MCC: Mobile Country Code, as assigned by ITU. A 3 digits decimal 214 number without leading zeros. 216 o MNC: Mobile Network Code, as assigned by National Authority. A 217 2-3 digits decimal number without leading zeros. 219 o ECI: E-UTRAN Cell Identifier. A 7 digits lower-case hexadecimal 220 number. 222 Example: 224 o ecgi:940.978:1234abc 226 * MCC value 940 stands for country or geographical area 227 "Wonderland" 229 * MNC value 978 stands for Network N1 in Wonderland and other 230 networks in other countries 232 * A same MNC value, say 020 may be associated with several MCCs. 234 * Some MCCs have MNCs encoded with 2 digits and MNCs encoded with 235 3 digits. 237 4.2. ALTO Cell Id formats 239 Three formats are proposed: 241 o 'ecgi:' MCC 242 o 'ecgi': MCC '.' MNC 244 o 'ecgi:' MCC '.' MNC ':' ECI-MASK '/' MASK-LEN 246 where: 247 MASK-LEN is a decimal number. 248 ECI-MASK is a string of lower-case hex digits, of which 249 all but the first MASK-LEN bits are zero. 251 Prefix ecgi:P-MCC.P-MNC:P-ECI/N matches ecgi:MCC.MNC:ECI iff 252 MCC == P-MCC, and 253 MNC == P-MNC, and 254 ECI has the same number of hex digits as P-ECI, and 255 the first N bits of ECI match those of P-ECI. 257 5. Examples 259 o ecgi:940 261 * Matches every cell address with MCC 940. 263 o ecgi:940.978 265 * Matches every cell address with MCC 940 and MNC 978. 267 o ecgi:940.978:1234800/18 269 * Matches every cell address with MCC 940, MNC 978, and a 7-digit 270 ECI that starts with the 18 bits 0x12348. Thus it matches 271 ecgi:940.978:1234abc and ecgi:940.978:1234800, but does not 272 match ecgi:940.978:1234d00. 274 6. IANA Considerations 276 This document extends: the ALTO Address Type Registry defined in 277 section 14.4 of RFC7285 and the ALTO Domain Entity Registry defined 278 in [draft-ietf-alto-unified-props-new]. If the latter is considered 279 a superset of the former, it seems consistent to register only a new 280 Entity Domain named "ecgi". This requires that implementations not 281 willing to use the (Filtered) Property Map Service and related 282 Entities should still be cognizant of the ALTO Domain Entity 283 Registry. Potential extensions are as as follows: 285 o The ALTO Address Type Registry defined in section 14.4 has an 286 additional item with the following properties: 288 * Identifier : ecgi 289 * Address encoding: see section Section 4 291 * Prefix encoding: TBC 293 * Mapping to/from IPv4/v6: none 295 o The ALTO Domain Entity Registry has an additional element with the 296 following properties: 298 * Identifier : ecgi 300 * Entity Address encoding: see section Section 4 302 * Field to be updated as [draft-ietf-alto-unified-props-new] 303 progresses: indicating that this entity domain can also be used 304 as an ALTO Address Type 306 * Hierarchy and inheritance: TBC 308 7. Security Considerations 310 TBC 312 8. Acknowledgements 314 Great thanks to Wendy Roome who initiated this document and Qin Wu 315 for discussions. 317 9. References 319 9.1. Normative References 321 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 322 Requirement Levels", BCP 14, RFC 2119, 323 DOI 10.17487/RFC2119, March 1997, 324 . 326 9.2. Informative References 328 [draft-ietf-alto-unified-props-new] 329 Roome, W., Chen, S., Randriamasy, S., Yang, Y., and J. 330 Zhang, "Extensible Property Maps for the ALTO Protocol", 331 March 2018. 333 [draft-roome-alto-unified-props-new-00] 334 Roome, W. and Y. Yang, "Extensible Property Maps for the 335 ALTO Protocol", March 2017. 337 Appendix A. An Appendix 339 Author's Address 341 Sabine Randriamasy 342 Nokia-Bell-labs 343 Route de Villejust 344 Nozay 91460 345 FRANCE 347 Email: Sabine.Randriamasy@nokia-bell-labs.com