Re: [Casm] Possible charter goals and milestones

"Xie Chongfeng" <xiechf.bri@chinatelecom.cn> Wed, 01 March 2017 23:28 UTC

Return-Path: <xiechf.bri@chinatelecom.cn>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F360B12940B for <casm@ietfa.amsl.com>; Wed, 1 Mar 2017 15:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.891
X-Spam-Level:
X-Spam-Status: No, score=-1.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 jqe9tCrD7fMY for <casm@ietfa.amsl.com>; Wed, 1 Mar 2017 15:28:32 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id EA81E128DF6 for <casm@ietf.org>; Wed, 1 Mar 2017 15:28:30 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.80:30706.642539364
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-125.33.59.14 (unknown [172.18.0.80]) by chinatelecom.cn (HERMES) with ESMTP id A0FAD280083; Thu, 2 Mar 2017 07:28:13 +0800 (CST)
Received: from ip<125.33.59.14> ([172.18.0.80]) by App0022(MEDUSA 0.0.0.0) with ESMTP id ebf299f6-f699-4562-9a0f-64e916718869 for liushucheng@huawei.com; Thu Mar 2 07:28:25 2017
0/X-Total-Score: 0:
X-FILTER-SCORE: to=<8d8a969489968489868f886189968298868a4f84908e>, score=<1488410905AAAABAAhAAoABhoS8YaxGAPPPPXPP8PP5PX85+KJSF2P>
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.80
X-MEDUSA-Status: 0
Date: Thu, 2 Mar 2017 07:28:13 +0800
From: "Xie Chongfeng" <xiechf.bri@chinatelecom.cn>
To: "'Liushucheng \(Will\)'" <liushucheng@huawei.com>, bclaise <bclaise@cisco.com>, "CASM@ietf.org" <CASM@ietf.org>, "Rakesh Kumar" <rkkumar@juniper.net>
References: <e3e3a854-f452-c176-1757-f0fcb94a5b2a@cisco.com>, <C9B5F12337F6F841B35C404CF0554ACB898C37DB@SZXEMA509-MBS.china.huawei.com>, <6150aca4-83ee-60cf-4b79-b657b8971040@cisco.com>, <C9B5F12337F6F841B35C404CF0554ACB898C4AEA@SZXEMA509-MBS.china.huawei.com>, <47128f6c-2dc8-400b-4521-a36dec4eb4e8@cisco.com>, <C9B5F12337F6F841B35C404CF0554ACB898CF4FD@SZXEMA509-MBS.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 166[cn]
Mime-Version: 1.0
Message-ID: <201703020728125079505@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart202373348553_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/LQTfn08QmZFR7Ql27QyB9LT8CDI>
Cc: joelja <joelja@bogus.com>, "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>, chengying10 <chengying10@chinaunicom.cn>, warren <warren@kumari.net>
Subject: Re: [Casm] Possible charter goals and milestones
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Centralized Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 23:28:37 -0000

I think that the interaction between address management entity and network element needs to be defined, it is a kind of protocol, if my understanding is right.

Chongfeng Xie



xiechf.bri@chinatelecom.cn
 
From: Liushucheng (Will Liu)
Date: 2017-03-01 17:02
To: Benoit Claise; CASM@ietf.org; Xie Chongfeng; Rakesh Kumar
CC: 'Ying Cheng'; joelja@bogus.com; Marc Blanchet; warren@kumari.net
Subject: RE: [Casm] Possible charter goals and milestones
Hi Benoit,
 
Thanks for reply. This is a good question to help the group make the goal clearer. Chongfeng and Rakesh, please correct me if I misunderstood: 
1.      From the discussion on the list, we can see that Chongfeng answered this by referring to the data model draft.  
2.      However, the framework figure in Rakesh’s draft show a more broader scope including APIs. 
3.      Protocol? So far no new protocol or extensions have been raised. Or at least this is my understanding. J
To get aligned we will discuss this topic at the upcoming online meeting. 
 
Regards,
Will (Shucheng LIU)
 
From: Benoit Claise [mailto:bclaise@cisco.com] 
Sent: Wednesday, March 01, 2017 4:54 AM
To: Liushucheng (Will Liu) <liushucheng@huawei.com>om>; CASM@ietf.org
Cc: 'Ying Cheng' <chengying10@chinaunicom.cn>cn>; 'Xie Chongfeng' <xiechf.bri@chinatelecom.cn>cn>; 'Rakesh Kumar' <rkkumar@juniper.net>et>; joelja@bogus.com; Marc Blanchet <marc.blanchet@viagenie.ca>ca>; warren@kumari.net
Subject: Re: [Casm] Possible charter goals and milestones
 
On 2/16/2017 3:45 PM, Liushucheng (Will) wrote:
Hi Benoit,
 
Please see below inline.
 
From: Benoit Claise [mailto:bclaise@cisco.com] 
Sent: Wednesday, February 15, 2017 9:25 PM
To: Liushucheng (Will); CASM@ietf.org
Cc: 'Ying Cheng'; 'Xie Chongfeng'; 'Rakesh Kumar'; joelja@bogus.com; Marc Blanchet; warren@kumari.net
Subject: Re: [Casm] Possible charter goals and milestones
 
Hi Liushucheng,
Hi Benoit and all,
 
Thanks for your guidance. After offline discussions among all the proponents, we changed the BoF to non-WG forming in the wiki.  https://trac.tools.ietf.org/bof/trac/
 
 
We also added the purpose of the BoF in the description:
The purpose of the BoF is to gather a common set of requirements from a larger set of operators and, if needed, possible protocol work milestones and scope.
Protocol work?  Which protocol?  Can you expand on what is needed?
I thought the work was about interfaces.
[Will] Thanks for the comments. As answered by Rakesh and Chongfeng, currently only interfaces are considered.
OK, to make sure we speak the same language, what do you call an interface in this context?
    - A protocol between A and B (with some negotiation, for example)? 
    - A data model?  https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang/ has been mentioned
    - An API?
    - etc.

Regards, Benoit

 
Cheers,
Will (Shucheng LIU)