[Ibnemo] IB-Nemo on MOnday
"Susan Hares" <shares@ndzh.com> Wed, 22 July 2015 12:22 UTC
Return-Path: <shares@ndzh.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 0DD9C1B3146 for <ibnemo@ietfa.amsl.com>; Wed, 22 Jul 2015 05:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.454
X-Spam-Level:
X-Spam-Status: No, score=-98.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, USER_IN_WHITELIST=-100] autolearn=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 aj8AywaNWJ26 for <ibnemo@ietfa.amsl.com>; Wed, 22 Jul 2015 05:21:58 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC281B312B for <ibnemo@ietf.org>; Wed, 22 Jul 2015 05:21:49 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=31.133.178.184;
From: Susan Hares <shares@ndzh.com>
To: ibnemo@ietf.org
Date: Wed, 22 Jul 2015 08:20:00 -0400
Message-ID: <00ff01d0c478$bca47b00$35ed7100$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0100_01D0C457.359461A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdDEd+d4qaamtbM5SayKsJG1Im6mrQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/kzTNTW-mnmNc6g1jzx_3l2tK6K4>
Cc: 'joel jaeggli' <joelja@bogus.com>, 'Alia Atlas' <akatlas@juniper.net>, 'Alvaro Retana' <aretana@cisco.com>
Subject: [Ibnemo] IB-Nemo on MOnday
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: Wed, 22 Jul 2015 12:22:02 -0000
Hi all: We had a lively discussion from the participants below. We will be meeting at 8pm (20:00) Budapest meeting on mezzanine level We received lots of good input including the following suggestion for improvement to our slides: 1) Need to emphasize what is the value of Declarative. The point that the "Connection" is the single command that the application does to connect after context is loaded. We should show the command to turn the connection off. It is a question whether we should show the expanded theory We could expand the idea in theory to include storage with a command "store" or the calculation - Compute. 2) Need to explain how the "context" is pass between application and the network management slides. We pass the exact topology in node and host statements. Could we load this context from the network for hosts? Do we allow all hosts within a network to connect? Bert was surprised that if Network 1 could talk to Network 2, and Network 2 could talk to network 3 - that network 1 and network 3 could not talk. We need to make it clear that the flows are specifically defined in the model. Alexander Clemm asked why this was better than the learning from the network. This is a question we need to consider. Can we learn the context from the network? How does the user signal to load the network? How do we make this easy? [Sue's comment]: we need to chat via email or in person about whether we can signal the network management system to learn the context from its local area. Rather than specify all of the hosts within a network subnet - can we say "allow all". 3) Start Demo at the user level Need provide a simple node example from Pedro's slide, and then go to a demo with the same names. 4) For the second demo, we can show how the infrastructure provider can allow choices at the infrastructure level. We can then expand one of the network boxes to include various specific hosts. 5) Scott Bradner was concerned that we not work against other network-wide yang models. We need to emphasize that we will utilize network-wide yang models and provide feedback to those network-wide models. 6) Scott Bradner commented that there may not be enough network-wide yang models in IETF to test until 2016. This comment underlines that the November IETF is the right timing for the BOF. By that time, the L3SM and other network-wide yang models may be created by other WGs. This point is important to underscore for slides. I will send slides for the IB-Nemo meeting tonight. I would appreciate any feedback on the changes on Thursday so tune the slides further. I will send the slide to the list tonight. Or if you'd like to join an in-person review Pedro and Tianran and I will walk through the slides a half hour before the meeting on Thursday. Attendees for the IB-Nemo meeting were: Bert Wijnens - Huawei consultant Diego Lopez - Telefonica Pedro Aranda - Telefonica Susan Hares - Huawei Consultant Scott Bradner - Harvard U Alexander Clemm - Cisco Michael Schwan - ALU Deng Hui - China Mobile Peng Fan - China Mobile David Dolson - Sandvine Ignaus Bagdonas RS Ltd. One person from Cable Labs. 13 people
- [Ibnemo] IB-Nemo on MOnday Susan Hares