Re: [alto] New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt

Qin Wu <bill.wu@huawei.com> Fri, 30 June 2017 02:19 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE21129B74 for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 19:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ogbzwx0gecLe for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 19:19:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F824129A9C for <alto@ietf.org>; Thu, 29 Jun 2017 19:19:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJL10656; Fri, 30 Jun 2017 02:19:40 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 30 Jun 2017 03:19:39 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.25]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Fri, 30 Jun 2017 10:19:34 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
Thread-Index: AQHS8Sz1sFndM7XE2EmChLiGoGq2lKI8d8XAgAAwBtA=
Date: Fri, 30 Jun 2017 02:19:33 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A98E559@nkgeml513-mbx.china.huawei.com>
References: <149877783604.4674.4124420883476203809.idtracker@ietfa.amsl.com> <DB6PR0701MB2454676034308E11DF8C2E4B95D20@DB6PR0701MB2454.eurprd07.prod.outlook.com>
In-Reply-To: <DB6PR0701MB2454676034308E11DF8C2E4B95D20@DB6PR0701MB2454.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.78.218]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.5955B53D.007C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 61c23bddc333d01cab9d820a8e1d191f
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Wci3OOg0aD38EIuQ_6WflQvm68I>
Subject: Re: [alto] New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 02:19:45 -0000

Hi, Sabine:
Thank for writing this short draft. It is a good start.
I have a few comments:
1. Section 3.2
MNC is defined as 2-3 digital decimal number without leading zeros?
But in the example following MNC definition, you give an example MNC value 020,
I am not sure if the first digital number "0" is leading zero?
2.Section 3.2
For Endpoint address format, 
MCC and MNC is defined as digital decimal number,
ECI is defined as digital hex number,
I am wondering why not specify MCC, MNC, ECI in the same format?
3. Section 3.2 Example:
Would it be great to make the text consistent with the example "ecgi:211:481:1234abc"?
For example, what do we mean by 311? What do we mean by 481?
4. How ALTO Cell Id format is related to endpoint address format?
5. section 3.4
s/7-digita ECI that starts with the 18 bits 0x12348/7-digital ECI Hex number that starts with 18 bits 0x12348
6. Section 3.4
I think 'ecgi:311.481:1234800/18' doesn't matches 'ecgi:311.481:1234abc'.
Maybe 'ecgi:311.481:1234abc' should be replaced with 'ecgi:311.481:1234cba'

-Qin
-----邮件原件-----
发件人: alto [mailto:alto-bounces@ietf.org] 代表 Randriamasy, Sabine (Nokia - FR/Nozay)
发送时间: 2017年6月30日 7:13
收件人: alto@ietf.org
主题: [alto] FW: New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt

Hello,

There have been several discussions and drafts on ALTO use cases involving cellular networks and it appears as necessary to agree upon an ALTO format for Cell Identifiers.

This relates to several drafts (performance, unified properties, mobility models...). So I have posted this short one just to provide a discussion support. There are actually only 2.5 pages to read. 

For short, 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.   

Looking forward to having your feedback and proposals. 
Thanks,
Sabine

>>-----Original Message-----
>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>Sent: 30 June 2017 01:11
>>To: Randriamasy, Sabine (Nokia - FR/Nozay) <sabine.randriamasy@nokia- 
>>bell-labs.com>
>>Subject: New Version Notification for draft-randriamasy-alto-cellular- 
>>adresses-00.txt
>>
>>
>>A new version of I-D, draft-randriamasy-alto-cellular-adresses-00.txt
>>has been successfully submitted by Sabine Randriamasy and posted to 
>>the IETF repository.
>>
>>Name:		draft-randriamasy-alto-cellular-adresses
>>Revision:	00
>>Title:		ALTO cellular addresses
>>Document date:	2017-06-30
>>Group:		Individual Submission
>>Pages:		5
>>URL:            https://www.ietf.org/internet-drafts/draft-randriamasy-alto-
>>cellular-adresses-00.txt
>>Status:         https://datatracker.ietf.org/doc/draft-randriamasy-alto-cellular-
>>adresses/
>>Htmlized:       https://tools.ietf.org/html/draft-randriamasy-alto-cellular-
>>adresses-00
>>Htmlized:       https://datatracker.ietf.org/doc/html/draft-randriamasy-alto-
>>cellular-adresses-00
>>
>>
>>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.
>>
>>
>>
>>
>>
>>Please note that it may take a couple of minutes from the time of 
>>submission until the htmlized version and diff are available at tools.ietf.org.
>>
>>The IETF Secretariat

_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto