idnits 2.17.1 draft-randriamasy-alto-cellular-adresses-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (December 15, 2017) is 2324 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 December 15, 2017 5 Expires: June 18, 2018 7 ALTO cellular addresses 8 draft-randriamasy-alto-cellular-adresses-01 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 June 18, 2018. 40 Copyright Notice 42 Copyright (c) 2017 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. Proposed format for ALTO cell identifiers . . . . . . . . . . 3 60 3.1. Relation of ALTO Cell Id format to endpoint address 61 format . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3.2. ALTO address type for cellular networks . . . . . . . . . 3 63 3.3. Endpoint address canonical string format . . . . . . . . 4 64 3.4. ALTO Cell Id formats . . . . . . . . . . . . . . . . . . 4 65 3.5. Examples . . . . . . . . . . . . . . . . . . . . . . . . 5 66 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 67 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 71 7.2. Informative References . . . . . . . . . . . . . . . . . 6 72 Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 6 73 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 75 1. Introduction 77 Cellular networks are present in a number of use cases investigated 78 in the ALTO WG and it is useful to specify a format for Cellular 79 addresses. In these cases, Endpoints, PIDs and entities may be 80 cells. In order to specify services such as Network Maps, Cost Maps, 81 Endpoint property or Property Maps, it is necessary to order to 82 specify an ALTO format for Cell addresses. 84 For the sake of efficiency, a preferred option is to use the cell 85 identifier format as specified by 3GPP [TS 36.300] and called ECGI, 86 as already proposed in [draft-rauschenbach-alto-wireless-access-00] 87 and in other discussions. ECGI stands for E-UTRAN Cell Global 88 Identifier and is used in Public Land Mobile Networks based on 89 E-UTRAN, see [TS 36.331]. 91 The purpose of this document is to be completed by the ALTO WG and in 92 particular: 94 - Amend and finalize the specification for the ALTO Cell identifier 95 format proposed in the present version, 96 - define a placeholder for this specification and identify impacted 97 documents. 99 2. Relevant ALTO services and documents 101 Particular services and drafts where an ALTO address type for 102 cellular networks is needed include: 104 o - Endpoint property service: extended to allow endpoints to be 105 cells on which properties can be requested, 107 o - (Filtered) Cost Map Service: where PIDs can be cells within and 108 among which cost values can be requested, see also[draft- 109 randriamasy-alto-cost-context-01], 111 o - "Mobility Network Models in ALTO" defined in [draft-bertz-alto- 112 mobilitynets] propose to identify network points of attachment 113 (PoA) such as cells to PIDs. 115 o - "ALTO Performance Cost Metrics": being defined in [draft-ietf- 116 alto-performance-metrics-01], they will be extended to performance 117 costs in cellular networks, 119 o - "Extensible Property Maps for the ALTO Protocol", being defined 120 in [draft-ietf-alto-unified-props-new] will cover entities that 121 may be cells which are identified by their addresses. In this 122 document a domain identifier for cells will need to be accordingly 123 defined, and the entity domain identifier "ecgi" is proposed. 125 3. Proposed format for ALTO cell identifiers 127 3.1. Relation of ALTO Cell Id format to endpoint address format 129 RFC7285 specifies endpoint address formats for ipv4 and ipv6 and the 130 purpose of this draft is to agree on a format for cellular endpoints. 131 When a cell is mapped to a PID, say "MyCell3" the ALTO Cell Id will 132 be used to specify the endpoints within this PID. 134 Whereas IP addresses are associated to domains ipv4 and ipv6, a Cell 135 Id will be associated to the domain "ecgi". 137 3.2. ALTO address type for cellular networks 139 ECGI -- E-UTRAN Cell Global Identifier 141 3.3. Endpoint address canonical string format 143 'ecgi:' MCC '.' MNC ':' ECI 145 Where: 147 o MCC: Mobile Country Code, as assigned by ITU. A 3 digits decimal 148 number without leading zeros. 150 o MNC: Mobile Network Code, as assigned by National Authority. A 151 2-3 digits decimal number with or without leading zeros. 153 o ECI: E-UTRAN Cell Identifier. A 7 digits lower-case hexadecimal 154 number. 156 Example: 158 o ecgi:940.978:1234abc 160 * MCC value 940 stands for country or geographical area 161 "CountryC" 163 * MNC value 978 stands for Network N1 in CountryC and other 164 networks in other countries 166 * A same MNC value, say 020 may be associated with several MCCs. 168 * Some MCCs have MNCs encoded with 2 digits and MNCs encoded with 169 3 digits. 171 3.4. ALTO Cell Id formats 173 Three formats are proposed: 175 o 'ecgi:' MCC 177 o 'ecgi': MCC '.' MNC 179 o 'ecgi:' MCC '.' MNC ':' ECI-MASK '/' MASK-LEN 180 where: 181 MASK-LEN is a decimal number. 182 ECI-MASK is a string of lower-case hex digits, of which 183 all but the first MASK-LEN bits are zero. 185 Prefix ecgi:P-MCC.P-MNC:P-ECI/N matches ecgi:MCC.MNC:ECI iff 186 MCC == P-MCC, and 187 MNC == P-MNC, and 188 ECI has the same number of hex digits as P-ECI, and 189 the first N bits of ECI match those of P-ECI. 191 3.5. Examples 193 o ecgi:940 195 * Matches every cell address with MCC 940. 197 o ecgi:940.978 199 * Matches every cell address with MCC 940 and MNC 978. 201 o ecgi:940.978:1234800/18 203 * Matches every cell address with MCC 940, MNC 978, and a 7-digit 204 ECI that starts with the 18 bits 0x12348. Thus it matches 205 ecgi:940.978:1234abc but does not match ecgi:940.978:1234dbc. 207 4. IANA Considerations 209 This document currently makes no request of IANA. 211 Note to RFC Editor: this section may be removed on publication as an 212 RFC. 214 5. Security Considerations 216 TBC 218 6. Acknowledgements 220 Great thanks to Wendy Roome who initiated this document, Qin Wu, Li 221 Geng and Yichen Qian for discussions. 223 7. References 224 7.1. Normative References 226 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 227 Requirement Levels", BCP 14, RFC 2119, 228 DOI 10.17487/RFC2119, March 1997, 229 . 231 7.2. Informative References 233 [draft-ietf-alto-unified-props-new] 234 Roome, W. and Y. Yang, "Extensible Property Maps for the 235 ALTO Protocol (in progress)", July 2017. 237 Appendix A. An Appendix 239 Author's Address 241 Sabine Randriamasy 242 Nokia-Bell-labs 243 Route de Villejust 244 Nozay 91460 245 FRANCE 247 Email: Sabine.Randriamasy@nokia-bell-labs.com