Re: [i2rs] [Rtg-yang-coord] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
Lou Berger <lberger@labn.net> Wed, 01 July 2015 15:39 UTC
Return-Path: <lberger@labn.net>
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 193061A906F for <i2rs@ietfa.amsl.com>; Wed, 1 Jul 2015 08:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level:
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 pGPvF8ai6BN8 for <i2rs@ietfa.amsl.com>; Wed, 1 Jul 2015 08:39:04 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by ietfa.amsl.com (Postfix) with SMTP id DC2B61A90E1 for <i2rs@ietf.org>; Wed, 1 Jul 2015 08:38:51 -0700 (PDT)
Received: (qmail 4614 invoked by uid 0); 1 Jul 2015 15:38:48 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy2.mail.unifiedlayer.com with SMTP; 1 Jul 2015 15:38:48 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id n9Xp1q00t2SSUrH019XsMN; Wed, 01 Jul 2015 15:31:56 -0600
X-Authority-Analysis: v=2.1 cv=UNFOQkvy c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=AGkejYDSTmIA:10 a=N659UExz7-8A:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=zOBTXjUuO1YA:10 a=48vgC7mUAAAA:8 a=NojvYFcnAAAA:8 a=CPnfetgAX7tcl8b5zoEA:9 a=tkKJxfFjhvdEEwf1:21 a=HAHpWqdVs0F_ZZq2:21 a=pILNOxqGKmIA:10 a=cVpdEv2aUKUA:10 a=9uUzcS5Nrb8A:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=83U9S0MeH/s6NfZXvL1nzxB/Pb1XF5xUfQH8B9T/mo0=; b=FWqLfyU+k8NbSlYAq7wPhNLk1Hv5GWJMtM1RY7m9zPAelPQJWm3+nxsbNPP8zkq7WdQwJB1Pc5+RgXefrQT2lew5b5T4jcV55GVM8u/pknanbeqkGWfJLBNuRIt8AC9w;
Received: from box313.bluehost.com ([69.89.31.113]:47929 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1ZAK5x-0005ty-T1; Wed, 01 Jul 2015 09:38:42 -0600
Message-ID: <5594097C.70607@labn.net>
Date: Wed, 01 Jul 2015 11:38:36 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Susan Hares <shares@ndzh.com>, 'Jeffrey Haas' <jhaas@pfrc.org>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com>
In-Reply-To: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/s360sq8aQ6FKUalfBxGLk9WFuQY>
Cc: Rtg-yang-coord@ietf.org, i2rs@ietf.org, "'BRUNGARD, DEBORAH A'" <db3546@att.com>, Vishnu Pavan Beeram <vbeeram@juniper.net>, "'Alvaro Retana (aretana)'" <aretana@cisco.com>, 'Alia Atlas' <akatlas@gmail.com>
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 15:39:07 -0000
> 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-topology/> > > 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=m4260bee7be61cb17b0008a3c52069d0f > > > > 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.html > > > > Sue Hares > > > > > > > > _______________________________________________ > Rtg-yang-coord mailing list > Rtg-yang-coord@ietf.org > https://www.ietf.org/mailman/listinfo/rtg-yang-coord
- [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