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

What, exactly, are you not agreeing with in the following 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.”

Lets take the sentence point by point.

#1 FLATTER, SIMPLER OBJECT MODEL
NEMO defines three objects: node, link, and flow. How many managed objects
do G.805 or G.809, let alone the average MIB, define? It is irrelevant that
you can define subclasses of node - the user has to do all the work, and
this guarantees non-interoperable solutions.

#2 TARGETS OF POLICY.
You just said that you define an object model and an operation model. Both
would be policy targets, by any standard CA or ECA definition.

#3. NEMO DOES NOT DEFINE A POLICY MODEL
You said: "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." Not only did you agree that you aren't defining a
policy model, but you appear to be unaware of why RFC3460 is badly broken.
So yes, you do need to rebuild this.

#4. DOES NOT SUPPORT ECA POLICIES. NEMO USES A CONDITION-ACTION PARADIGM TO
EXECUTE ITS POLICY COMMANDS.
It is inconceivable to me how you could disagree with this. From
draft-xia-sdnrg-nemo-language-02, Section 5.1: "All the policies follow the
same pattern "when <condition>, to execute <action>, with <constraint>",
and can be applied to any entity." This is NOT an ECA policy; any useful
implementation of CA or ECA allows constraints - EXCEPT RFC3460.

John

On Wed, Jul 15, 2015 at 6:38 PM, Xiayinben <xiayinben@huawei.com> wrote:

>  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 <supa-bounces@ietf.org>] *代表 *Tina
> TSOU
> *发送时间:* 2015年7月15日 15:42
> *收件人:* Scott O. Bradner; Susan Hares
> *抄送:* 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 <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
> *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 <supa-bounces@ietf.org>] *On
> Behalf Of *Tina TSOU
> *Sent:* Tuesday, July 07, 2015 7:05 AM
> *To:* 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
>
>
> _______________________________________________
> Supa mailing list
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa
>
>

-- 
regards,
John