ALTO S. Randriamasy Internet-Draft Nokia-Bell-labs Intended status: Experimental December 15, 2017 Expires: June 18, 2018 ALTO cellular addresses draft-randriamasy-alto-cellular-adresses-01 Abstract This draft proposes to use the cellular address format composed of elements as specified by 3GPP and called ECGI. ECGI stands for E-UTRAN Cell Global Identifier and is used in Public Land Mobile Networks based on E-UTRAN. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on June 18, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents Randriamasy Expires June 18, 2018 [Page 1] Internet-Draft Abbreviated-Title December 2017 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Relevant ALTO services and documents . . . . . . . . . . . . 3 3. Proposed format for ALTO cell identifiers . . . . . . . . . . 3 3.1. Relation of ALTO Cell Id format to endpoint address format . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. ALTO address type for cellular networks . . . . . . . . . 3 3.3. Endpoint address canonical string format . . . . . . . . 4 3.4. ALTO Cell Id formats . . . . . . . . . . . . . . . . . . 4 3.5. Examples . . . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . 6 Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction Cellular networks are present in a number of use cases investigated in the ALTO WG and it is useful to specify a format for Cellular addresses. In these cases, Endpoints, PIDs and entities may be cells. In order to specify services such as Network Maps, Cost Maps, Endpoint property or Property Maps, it is necessary to order to specify an ALTO format for Cell addresses. For the sake of efficiency, a preferred option is to use the cell identifier format as specified by 3GPP [TS 36.300] and called ECGI, as already proposed in [draft-rauschenbach-alto-wireless-access-00] and in other discussions. ECGI stands for E-UTRAN Cell Global Identifier and is used in Public Land Mobile Networks based on E-UTRAN, see [TS 36.331]. The purpose of this document is to be completed by the ALTO WG and in particular: - Amend and finalize the specification for the ALTO Cell identifier format proposed in the present version, Randriamasy Expires June 18, 2018 [Page 2] Internet-Draft Abbreviated-Title December 2017 - define a placeholder for this specification and identify impacted documents. 2. Relevant ALTO services and documents Particular services and drafts where an ALTO address type for cellular networks is needed include: o - Endpoint property service: extended to allow endpoints to be cells on which properties can be requested, o - (Filtered) Cost Map Service: where PIDs can be cells within and among which cost values can be requested, see also[draft- randriamasy-alto-cost-context-01], o - "Mobility Network Models in ALTO" defined in [draft-bertz-alto- mobilitynets] propose to identify network points of attachment (PoA) such as cells to PIDs. o - "ALTO Performance Cost Metrics": being defined in [draft-ietf- alto-performance-metrics-01], they will be extended to performance costs in cellular networks, o - "Extensible Property Maps for the ALTO Protocol", being defined in [draft-ietf-alto-unified-props-new] will cover entities that may be cells which are identified by their addresses. In this document a domain identifier for cells will need to be accordingly defined, and the entity domain identifier "ecgi" is proposed. 3. Proposed format for ALTO cell identifiers 3.1. Relation of ALTO Cell Id format to endpoint address format RFC7285 specifies endpoint address formats for ipv4 and ipv6 and the purpose of this draft is to agree on a format for cellular endpoints. When a cell is mapped to a PID, say "MyCell3" the ALTO Cell Id will be used to specify the endpoints within this PID. Whereas IP addresses are associated to domains ipv4 and ipv6, a Cell Id will be associated to the domain "ecgi". 3.2. ALTO address type for cellular networks ECGI -- E-UTRAN Cell Global Identifier Randriamasy Expires June 18, 2018 [Page 3] Internet-Draft Abbreviated-Title December 2017 3.3. Endpoint address canonical string format 'ecgi:' MCC '.' MNC ':' ECI Where: o MCC: Mobile Country Code, as assigned by ITU. A 3 digits decimal number without leading zeros. o MNC: Mobile Network Code, as assigned by National Authority. A 2-3 digits decimal number with or without leading zeros. o ECI: E-UTRAN Cell Identifier. A 7 digits lower-case hexadecimal number. Example: o ecgi:940.978:1234abc * MCC value 940 stands for country or geographical area "CountryC" * MNC value 978 stands for Network N1 in CountryC and other networks in other countries * A same MNC value, say 020 may be associated with several MCCs. * Some MCCs have MNCs encoded with 2 digits and MNCs encoded with 3 digits. 3.4. ALTO Cell Id formats Three formats are proposed: o 'ecgi:' MCC o 'ecgi': MCC '.' MNC o 'ecgi:' MCC '.' MNC ':' ECI-MASK '/' MASK-LEN Randriamasy Expires June 18, 2018 [Page 4] Internet-Draft Abbreviated-Title December 2017 where: MASK-LEN is a decimal number. ECI-MASK is a string of lower-case hex digits, of which all but the first MASK-LEN bits are zero. Prefix ecgi:P-MCC.P-MNC:P-ECI/N matches ecgi:MCC.MNC:ECI iff MCC == P-MCC, and MNC == P-MNC, and ECI has the same number of hex digits as P-ECI, and the first N bits of ECI match those of P-ECI. 3.5. Examples o ecgi:940 * Matches every cell address with MCC 940. o ecgi:940.978 * Matches every cell address with MCC 940 and MNC 978. o ecgi:940.978:1234800/18 * Matches every cell address with MCC 940, MNC 978, and a 7-digit ECI that starts with the 18 bits 0x12348. Thus it matches ecgi:940.978:1234abc but does not match ecgi:940.978:1234dbc. 4. IANA Considerations This document currently makes no request of IANA. Note to RFC Editor: this section may be removed on publication as an RFC. 5. Security Considerations TBC 6. Acknowledgements Great thanks to Wendy Roome who initiated this document, Qin Wu, Li Geng and Yichen Qian for discussions. 7. References Randriamasy Expires June 18, 2018 [Page 5] Internet-Draft Abbreviated-Title December 2017 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . 7.2. Informative References [draft-ietf-alto-unified-props-new] Roome, W. and Y. Yang, "Extensible Property Maps for the ALTO Protocol (in progress)", July 2017. Appendix A. An Appendix Author's Address Sabine Randriamasy Nokia-Bell-labs Route de Villejust Nozay 91460 FRANCE Email: Sabine.Randriamasy@nokia-bell-labs.com Randriamasy Expires June 18, 2018 [Page 6]