Re: [Casm] Possible charter goals and milestones

"Liushucheng (Will Liu)" <liushucheng@huawei.com> Wed, 01 March 2017 09:04 UTC

Return-Path: <liushucheng@huawei.com>
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 4C9A21296BC for <casm@ietfa.amsl.com>; Wed, 1 Mar 2017 01:04:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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, 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 1UOtQ4CDQAQ7 for <casm@ietfa.amsl.com>; Wed, 1 Mar 2017 01:04:31 -0800 (PST)
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 C7D2612967E for <CASM@ietf.org>; Wed, 1 Mar 2017 01:04:21 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DBX41513; Wed, 01 Mar 2017 09:04:19 +0000 (GMT)
Received: from SZXEMA415-HUB.china.huawei.com (10.82.72.33) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 1 Mar 2017 09:02:37 +0000
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.147]) by SZXEMA415-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0235.001; Wed, 1 Mar 2017 17:02:34 +0800
From: "Liushucheng (Will Liu)" <liushucheng@huawei.com>
To: Benoit Claise <bclaise@cisco.com>, "CASM@ietf.org" <CASM@ietf.org>, "Xie Chongfeng" <xiechf.bri@chinatelecom.cn>, Rakesh Kumar <rkkumar@juniper.net>
Thread-Topic: [Casm] Possible charter goals and milestones
Thread-Index: AQHShukHT/ahGRtvKkWC8ytb2VweDaFpUmRwgAA3f4CAAi2NcIASvhkAgAFPofA=
Date: Wed, 1 Mar 2017 09:02:34 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB898CF4FD@SZXEMA509-MBS.china.huawei.com>
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>
In-Reply-To: <47128f6c-2dc8-400b-4521-a36dec4eb4e8@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.79.101]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB898CF4FDSZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.58B68E94.019B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.147, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: be4cfbcfd4603cba961a59c352e411f3
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/UpRDvP8sKBnl_EBff5j0AV9ZqgE>
Cc: "joelja@bogus.com" <joelja@bogus.com>, Marc Blanchet <marc.blanchet@viagenie.ca>, 'Ying Cheng' <chengying10@chinaunicom.cn>, "warren@kumari.net" <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 09:04:35 -0000

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. ☺
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<mailto:CASM@ietf.org>
Cc: 'Ying Cheng'; 'Xie Chongfeng'; 'Rakesh Kumar'; joelja@bogus.com<mailto:joelja@bogus.com>; Marc Blanchet; warren@kumari.net<mailto: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)