[Ibnemo] 答复: [Supa] SUPA call: 7:30-8:30am, Monday, July 13, San Francisco time

Xiayinben <xiayinben@huawei.com> Thu, 16 July 2015 01:39 UTC

Return-Path: <xiayinben@huawei.com>
X-Original-To: ibnemo@ietfa.amsl.com
Delivered-To: ibnemo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFBB1B2CD2; Wed, 15 Jul 2015 18:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.31
X-Spam-Level:
X-Spam-Status: No, score=-3.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rkQieitoVP8p; Wed, 15 Jul 2015 18:39:00 -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 086861B2CCE; Wed, 15 Jul 2015 18:38:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BYV07528; Thu, 16 Jul 2015 01:38:57 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 16 Jul 2015 02:38:54 +0100
Received: from NKGEML507-MBS.china.huawei.com ([169.254.6.64]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Thu, 16 Jul 2015 09:38:41 +0800
From: Xiayinben <xiayinben@huawei.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "Scott O. Bradner" <sob@sobco.com>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Supa] SUPA call: 7:30-8:30am, Monday, July 13, San Francisco time
Thread-Index: AQHQuu8q+K2aOynku0yFD3N2gimUkZ3bp54AgAFs4UA=
Date: Thu, 16 Jul 2015 01:38:40 +0000
Message-ID: <5FD31D8EDBF4EC468B36D86F04FDB2E8780A102F@nkgeml507-mbs.china.huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A818C258DF@szxeml557-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A818C45663@szxeml557-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A818C71DF4@szxeml557-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A818C71DF4@szxeml557-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.53.87]
Content-Type: multipart/alternative; boundary="_000_5FD31D8EDBF4EC468B36D86F04FDB2E8780A102Fnkgeml507mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/0tFdKlaEaMmdfdiHcJZ7IXrwkDU>
Cc: "ibnemo@ietf.org" <ibnemo@ietf.org>, "supa@ietf.org" <supa@ietf.org>
Subject: [Ibnemo] 答复: [Supa] SUPA call: 7:30-8:30am, Monday, July 13, San Francisco time
X-BeenThere: ibnemo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of Nemo, an intent-based North Bound \(NB\) interface consisting of an application protocol running over HTTP \(RESTful interfaces\) to exchange intent-based primitives between applications and meta-controllers controlling virtual network resources \(networks, storage, CPU\)." <ibnemo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ibnemo>, <mailto:ibnemo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ibnemo/>
List-Help: <mailto:ibnemo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ibnemo>, <mailto:ibnemo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2015 01:39:03 -0000

Hi Tina and all,

I do not agree with your word about NEMO/ibnemo in page 8.

Your sentence: “NEMO uses a flatter, simpler object model with fewer objects to represent targets of policy. NEMO does not define a policy model, and does not support ECA policies. NEMO uses a condition-action paradigm to execute its policy commands.”
The truth is that NEMO define an object model and an operation model to represent network abstraction for intent NBI, because NEMO’s target is a simplified network interface(Intent NBI) for application even for ender-user.  policy is only a type of operation in Intent NBI. NEMO doesn’t NEED to define a new policy model, because industry already has well defined policy model(such as RFC 3460). We will not rebuild a wheel.

Your sentence: “IBNemo – 'intent' means I express a desired topology and its properties.”
The truth  is that Ibnemo –‘Intent’ means user simply and intuitively  express demands of network resource and/or network behavior. Topology and its properties are typical type of network resource, so they are part of network intent, but not all.

Best regards,
Yinben
发件人: Supa [mailto:supa-bounces@ietf.org] 代表 Tina TSOU
发送时间: 2015年7月15日 15:42
收件人: Scott O. Bradner; Susan Hares
抄送: supa@ietf.org<mailto:supa@ietf.org>
主题: Re: [Supa] SUPA call: 7:30-8:30am, Monday, July 13, San Francisco time

Dear all,

Enclosed pls find the updated slides based on Monday July 13 call discussion, only page 8 added.


Thank you,
Tina

From: Supa [mailto:supa-bounces@ietf.org] On Behalf Of Tina TSOU
Sent: Friday, July 10, 2015 4:31 PM
To: Scott O. Bradner; Susan Hares
Cc: supa@ietf.org<mailto:supa@ietf.org>
Subject: Re: [Supa] SUPA call: 7:30-8:30am, Monday, July 13, San Francisco time

Dear Scott and Sue,

Regarding “2.2. Relationship to other WGs (Scott/Sue et al, 5 minutes)” (Times are the ones in the call next week – not the BOF), attached is a quick update based on Jun’s presentation in last BoF, according to the discussion after Dallas.

Feel free to use or update the slides.


Thank you,
Tina

From: Supa [mailto:supa-bounces@ietf.org] On Behalf Of Tina TSOU
Sent: Tuesday, July 07, 2015 7:05 AM
To: supa@ietf.org<mailto:supa@ietf.org>
Subject: [Supa] SUPA call: 7:30-8:30am, Monday, July 13, San Francisco time


Dear all,



Below is the draft agenda and logistics for next call during 7:30-8:30am, Monday, July 13, San Francisco time.



Look forward to talking to many of you at the meeting.



----------

1. Note Well, logistics, agenda bashing (chairs, 5 min)



2. Slides Preparation for the BoF (Times are the ones in the call next week – not the BOF)



2.1. Goals, Framework, Examples (Max, Oscar (Luis) et al, 10 minutes)

2.2. Relationship to other WGs (Scott/Sue et al, 5 minutes)

2.3. Information Model Overview (John et al, 5 minutes)

2.4. Data Model Overview (Andy et al, 5 minutes)

2.5. Charter presentation (Dan/Juergen et al, 10 minutes)

2.6. Discussion on whether the progress assessment implies going forward changes to the charter (all, 15 minutes)

2.7. Questions to the audience (chairs, 10 minutes)



-----------





Join WebEx meeting<https://ietf.webex.com/ietf/j.php?MTID=m23e113c8822a0970e0e779383ab09322>

Meeting number: 646 022 302

Meeting password:       2015





Join by phone

1-877-668-4493 Call-in toll free number (US/Canada)

1-650-479-3208 Call-in toll number (US/Canada)

Access code: 646 022 302

Toll-free calling restrictions<http://www.webex.com/pdf/tollfree_restrictions.pdf>







Can't join the meeting? Contact support.<https://ietf.webex.com/ietf/mc>



IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.





Thank you,

Dan & Tina