Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
Vishnu Pavan Beeram <vishnupavan@gmail.com> Thu, 02 July 2015 00:42 UTC
Return-Path: <vishnupavan@gmail.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EABD1B2C7E; Wed, 1 Jul 2015 17:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 ajmcqUQGwohW; Wed, 1 Jul 2015 17:41:54 -0700 (PDT)
Received: from mail-vn0-x22c.google.com (mail-vn0-x22c.google.com [IPv6:2607:f8b0:400c:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BA171B2C9F; Wed, 1 Jul 2015 17:41:52 -0700 (PDT)
Received: by vnbf129 with SMTP id f129so9060090vnb.4; Wed, 01 Jul 2015 17:41:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mMjiODT0NSInRQwJr/B++gfoVh+9A5gkb/Qbcss4jM4=; b=dsPfBWaF6XVqR3Gg1xPY8q1jtQuxFd1Rs035VerH0dOxecQtfRpGxFYv5VWiESlO0n Gz+P+I6sQkomdoChDjGVvSKkomGsxGh0FSRGeAAlepsxBxnQ8rhtKbpOhaXdjPMvEK2A 9COfTQmR+EDb8tcYOJJ1ciddCBpCkOtZkVRJKeynWBeOqgBiGZVmlPacGpcBBdf9mw1m YNRBGqovuI5KKETe66XB1dCW1KMoKgYGJSklScA3tyKHk9X/0uGN9DqHvPnIhD6HcswU OZmYn1acDXyfk52YcLJ1YSuw4/o2ff/ifXjAEYKCKQB5mP7j9oZSk5ldjOsF6AV3BTyJ C3zg==
MIME-Version: 1.0
X-Received: by 10.52.32.34 with SMTP id f2mr28501254vdi.11.1435797711282; Wed, 01 Jul 2015 17:41:51 -0700 (PDT)
Received: by 10.31.96.80 with HTTP; Wed, 1 Jul 2015 17:41:51 -0700 (PDT)
In-Reply-To: <00d801d0b450$250e4560$6f2ad020$@ndzh.com>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com> <5594097C.70607@labn.net> <00d801d0b450$250e4560$6f2ad020$@ndzh.com>
Date: Wed, 01 Jul 2015 20:41:51 -0400
Message-ID: <CA+YzgTsJOptCtNqqccsFxGR6y+-kua2dW6NBsPru4fZY4PxnOg@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="bcaec51d2b808ce8250519d9b42d"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/5xSN1eSnJ4WieBv0g-vC7pI2U3k>
X-Mailman-Approved-At: Mon, 06 Jul 2015 08:27:27 -0700
Cc: Rtg-yang-coord@ietf.org, i2rs@ietf.org, "BRUNGARD, DEBORAH A" <db3546@att.com>, alex@cisco.com, Vishnu Pavan Beeram <vbeeram@juniper.net>, Alia Atlas <akatlas@gmail.com>, draft-ietf-teas-yang-te-topo@tools.ietf.com, Jeffrey Haas <jhaas@pfrc.org>, "Alvaro Retana (aretana)" <aretana@cisco.com>, Lou Berger <lberger@labn.net>
Subject: Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2015 00:42:05 -0000
+ Alex + <te-topo-model> authors Sue, Jeff, The authors of the <te-topo-model> draft had a meeting today with one of the authors (Alex) of the <network-topo-model> draft and discussed ways to align the topo models. The consensus so far is that the <te-topo-model> WILL augment the <network-topo-model>. There are some issues that need to be worked out (mapping identifiers, termination-points), but those should get resolved in due course of time. I'll sync up with you (Sue) and coordinate a meeting between the authors of the <te-topo-model> and the authors of the I2RS topo model(s) at the IETF --- hopefully early in the week. Regards, -Pavan On Wed, Jul 1, 2015 at 6:49 PM, Susan Hares <shares@ndzh.com> wrote: > Lou and Jeffrey: > > On 7/22, I talked with the TEAS TE authors team. They had concerns about > how the I2RS was going to integrate the TEAS work. I realized there are > two > different approaches to the models - and I expressed my hope that we could > have aligned/merged models. I chatted with the I2RS topology draft > authors, > and I found that the authors had not yet begun to work on the TE models. > The best plan is to try to get the TEAS authors and the I2RS Topology > authors together at IETF 93 and get a plan together for migrating these > teams together. > > I will send a few times out to teams this evening. It would really help > I2RS if the TEAS group would meet early in the week (or if the folks are at > the hack-athon like I am we may meet Saturday night). We could then try to > give NETCONF our best insight on the TE additions. > > In order to prepare for this TE/Non-TE merge, I2RS WG need to finalize the > non-TE models in the topology. Today's interim was target to firm up the > Service and T1 topology models, but the T1 topology model will not be ready > until IETF 93. My message in June hoped that we would be to the TE models > by IETF so that NETCONF would have our entire scope, but we will not be > there by the beginning of IETF. I2RS will be following up in August and > September with Interims that focus on the TE models in I2RS Topology model. > > Do you have any other suggestions? > > Sue > > > -----Original Message----- > From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Lou Berger > Sent: Wednesday, July 01, 2015 11:39 AM > To: Susan Hares; 'Jeffrey Haas' > Cc: Rtg-yang-coord@ietf.org; i2rs@ietf.org; 'BRUNGARD, DEBORAH A'; Vishnu > Pavan Beeram; 'Alvaro Retana (aretana)'; 'Alia Atlas' > Subject: Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS protocol and > I2RS > interim (6/24/2015 at 10:00 - 11:30am ET) > > > At this time, none of the Topology models utilize Traffic > engineering. It is anticipated that these models will support traffic > engineering. > > Sue, Jeff, > Given some recent messages on the list, I thought it best to confirm > we're all still on the same page. > > Based on our past discussions, it's my understanding that the work being > done in TEAS (see draft-ietf-teas-yang-te-topo) will serve as the > foundation > for TE support in the I2RS models. I complete agree that there are details > on how the different topology models will integrate/mesh still needs to be > worked out, and I assumed that this is what you/Sue were referring to > above. > -- But we will not have two sets of TE topology models. > > I believe that the authors of the respective drafts are already are working > this. (Pavan, my co-chair as well as coauthor of the TEAS yang model, can > comment on this.) > > Please let me know if I missed/miss-understood something. > > Thanks, > Lou > (as TEAS WG co-chair) > On 6/23/2015 2:19 PM, Susan Hares wrote: > > > > Netconf Working Group: > > > > > > > > The I2RS WG would like to pass you a set of requirements for the I2RS > > protocol, and asks that you provide an analysis by IETF 93 on whether > > NETCONF or RESTCONF can meet these requirements. We expect that > > these requirements may require changes to the either NETCONF or > > RESTCONF. > > > > > > > > The I2RS architecture document (draft-ietf-i2rs-architecture-09 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-architecture/>) > > provides a high-level overview of the I2RS protocol. The I2RS has > > compiled the following documents to provide the additional details on > > the requirements for the protocols. > > > > > > > > 1) draft-ietf-i2rs-ephemeral-state-00 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/> > > > > 2) draft-ietf-i2rs-pub-sub-requirements-02 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements > > /> > > > > 3) draft-ietf-i2rs-traceability-03 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/> > > > > > > > > The draft-ietf-i2rs-ephemeral-state-00 contains the results of the > > discussion from the 6/10 interim and the top 10 requirements for I2RS. > > In addition, the draft-ietf-i2rs-ephemeral-state-00 contains an set of > > detailed requirements on how the I2RS WG sees the I2RS protocol > > operating. These detailed requirements are to be seen as suggestions > > on what type of solution the I2RS WG would like to see, but I2RS WG is > > asking the NETCONF WG to provide its best designed protocol. Please > > note as part of these detailed requirement the > > draft-ietf-i2rs-ephemeral-states-00 contains the idea of using > > metadata to record secondary identity. > > > > > > > > The I2RS protocol is driven by data-models. The approved data models > > for protocol independent services are: > > > > - draft-ietf-i2rs-rib-data-model-00 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/> > > > > - Filter-Based RIBS: draft-kini-i2rs-fb-rib-data-model.00 > > (released later this week) > > > > - Topology model which is a composite of: > > > > o Generic topology model: draft-ietf-i2rs-yang-network-topo-01 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo/> > > > > o L3 topology model: draft-ietf-i2rs-yang-l3-topology-00 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/> > > > > o L2 topology model: draft-ietf-i2rs-yang-l2-network-topology-00 > > <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topo > > logy/> > > > > o L1 Topology model: draft-zhang-i2rs-l1-topo-yang-model-01 (-02 > > released later this week). > > > > o Service topology model: > > draft-hares-i2rs-service-topo-yang-model-00 (released on Wednesday) > > > > > > > > At this time, none of the Topology models utilize Traffic engineering. > > It is anticipated that these models will support traffic engineering. > > Estimated rates of transfer and timing requirements for these modules > > are at: http://trac.tools.ietf.org/wg/i2rs/trac/wiki - under the > > protocol requirements table. > > > > > > > > We hope that NETCONF WG can provide some initial feedback on these > > requirements by IETF 93 at the Tuesday I2RS session. I2RS will use > > the 6/24 interim at 10:00-11:30am ET to provide a time for any > > participate in the I2RS, netconf, or netmod group to ask additional > > questions on these requirements. > > > > > > > > Sue Hares > > > > > > > > Interim time: 10:00-11:30am ET > > > > Date 6/24/2015 > > > > Webex: > > > > https://ietf.webex.com/ietf/j.php?MTID=m4260bee7be61cb17b0008a3c52069d > > 0f > > > > > > > > agenda: > > > > > > > > 10:00 - 10:05 - Bash Agenda > > > > 10:05 - 10:20- - review of requirements from > > > > draft-ietf-i2rs-ephemeral-state-00 > > > > draft-ietf-i2rs-pub-sub-requirements-02 > > > > draft-ietf-i2rs-traceability-03 > > > > Timing requirements > > > > > > > > 10:20 - 10:30 Review of requirements for mutual authentication, > > > > and transaction in draft-hares-auth-trans-01 requirements > > > > > > > > 10:30- 11:30 Open discussion for I2RS Requirements > > > > > > > > Proceedings and slides can be found at: > > > > http://www.ietf.org/proceedings/interim/2015/06/24/i2rs/proceedings.ht > > ml > > > > > > > > Sue Hares > > > > > > > > > > > > > > > > _______________________________________________ > > Rtg-yang-coord mailing list > > Rtg-yang-coord@ietf.org > > https://www.ietf.org/mailman/listinfo/rtg-yang-coord > > > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs > > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs >
- [Rtg-yang-coord] Requirements for I2RS protocol a… Susan Hares
- Re: [Rtg-yang-coord] [netmod] Requirements for I2… Mahesh Jethanandani
- Re: [Rtg-yang-coord] [netmod] Requirements for I2… Susan Hares
- Re: [Rtg-yang-coord] [netmod] Requirements for I2… Eric Voit (evoit)
- Re: [Rtg-yang-coord] [netmod] Requirements for I2… BELOTTI, SERGIO (SERGIO)
- Re: [Rtg-yang-coord] Requirements for I2RS protoc… Lou Berger
- Re: [Rtg-yang-coord] Requirements for I2RS protoc… Jeffrey Haas
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Lou Berger
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Susan Hares
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Lou Berger
- Re: [Rtg-yang-coord] [netmod] Requirements for I2… Mahesh Jethanandani
- Re: [Rtg-yang-coord] [i2rs] [netmod] Requirements… Susan Hares
- Re: [Rtg-yang-coord] [netmod] Requirements for I2… Susan Hares
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Vishnu Pavan Beeram
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Alexander Clemm (alex)
- Re: [Rtg-yang-coord] [i2rs] [netmod] Requirements… Susan Hares
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Zhangxian (Xian)
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Susan Hares
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Lou Berger
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Susan Hares
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Tom Taylor
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Susan Hares
- Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS… Susan Hares