Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
"Susan Hares" <shares@ndzh.com> Wed, 01 July 2015 22:49 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2E51B2C0F; Wed, 1 Jul 2015 15:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.055
X-Spam-Level:
X-Spam-Status: No, score=-99.055 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 YMrH7Gt7-Dk5; Wed, 1 Jul 2015 15:49:15 -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 467681B2BD2; Wed, 1 Jul 2015 15:49:15 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.185.134;
From: Susan Hares <shares@ndzh.com>
To: 'Lou Berger' <lberger@labn.net>, 'Jeffrey Haas' <jhaas@pfrc.org>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com> <5594097C.70607@labn.net>
In-Reply-To: <5594097C.70607@labn.net>
Date: Wed, 01 Jul 2015 18:49:09 -0400
Message-ID: <00d801d0b450$250e4560$6f2ad020$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQISFdXuYb8FEw5zRd6nzKGMwfXW3QL4Xs+nnSyjtIA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/iXkQLoUF3g4EoAg52k8d9IhH2UY>
Cc: Rtg-yang-coord@ietf.org, i2rs@ietf.org, "'BRUNGARD, DEBORAH A'" <db3546@att.com>, 'Alia Atlas' <akatlas@gmail.com>, "'Alvaro Retana (aretana)'" <aretana@cisco.com>, 'Vishnu Pavan Beeram' <vbeeram@juniper.net>
Subject: Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2015 22:49:17 -0000
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] Requirements for I2RS protocol and I2RS in… Susan Hares
- Re: [i2rs] [netmod] Requirements for I2RS protoco… Mahesh Jethanandani
- Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements… Susan Hares
- Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements… Eric Voit (evoit)
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Lou Berger
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Jeffrey Haas
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Lou Berger
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Susan Hares
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Lou Berger
- Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements… BELOTTI, SERGIO (SERGIO)
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Vishnu Pavan Beeram
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Alexander Clemm (alex)
- Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements… Mahesh Jethanandani
- Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements… Susan Hares
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Zhangxian (Xian)
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Susan Hares
- Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements… Susan Hares
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Lou Berger
- Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS… Susan Hares