Re: [Netconf] [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 30 June 2015 22:13 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E861B3317; Tue, 30 Jun 2015 15:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 ulGayuEvAWcB; Tue, 30 Jun 2015 15:13:45 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25E9B1B3313; Tue, 30 Jun 2015 15:13:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=61472; q=dns/txt; s=iport; t=1435702425; x=1436912025; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tjhHoEQRxgW3RYGGcDYhd1sTUgeHWTSMXCa73+bIz7M=; b=kjKFZLfSzzDGGAzeqkl+V2xpq7M7IIVO2Goh/iV8UGa+T1zs2f8rQ4qI XTqg13Lo6W95nYuJE5uH1+2ckzVUvZPptW0AlVmwNSUW64Gx7ytDvgMA9 DHXYmul0vi4FRDuG3S7iyTIIeZeyCW3wMyT2ydMap2sH9sbRCE5xW5DO3 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A0BQByFJNV/5JdJa1BEQmCRUxUXwaDGLoAKgmBSBkBC4UsSgIcgTo4FAEBAQEBAQGBCoQiAQEBBAEBASAKQQsQAgEIDgMBAwEBCxYBAgQDAgICHwYLFAMGCAIEAQkEBQgBEod/AxINOrImkQcNhXMBAQEBAQEBAQEBAQEBAQEBAQEBAQEXi0qCTYFdKy0EBgGCaC+BFAWRKYJeAYRZhRqBZIE5RINOi1eHGhEVggwcFYE9bwGBRYECAQEB
X-IronPort-AV: E=Sophos;i="5.15,380,1432598400"; d="scan'208,217";a="164434195"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Jun 2015 22:13:29 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t5UMDSCg026310 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 30 Jun 2015 22:13:28 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.147]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Tue, 30 Jun 2015 17:13:21 -0500
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Susan Hares <shares@ndzh.com>, 'Mahesh Jethanandani' <mjethanandani@gmail.com>
Thread-Topic: [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
Thread-Index: AQISFdXuYb8FEw5zRd6nzKGMwfXW3QKbN0DLnS3sq9CAAAbrEA==
Date: Tue, 30 Jun 2015 22:13:21 +0000
Message-ID: <EF64FF31F4C4384DBCE5D513A791C2B121B00EE1@xmb-aln-x11.cisco.com>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com> <D8FF75B2-4BB4-4A98-989B-10A2E480EBEF@gmail.com> <007501d0b37a$02d6fbd0$0884f370$@ndzh.com>
In-Reply-To: <007501d0b37a$02d6fbd0$0884f370$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.118.56.228]
Content-Type: multipart/alternative; boundary="_000_EF64FF31F4C4384DBCE5D513A791C2B121B00EE1xmbalnx11ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/netconf/SEzJNOl_5QZKOl9G2D9aZfaypew>
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>, 'NETMOD Working Group' <netmod@ietf.org>, "'BRUNGARD, DEBORAH A'" <db3546@att.com>, 'Netconf' <netconf@ietf.org>
Subject: Re: [Netconf] [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2015 22:13:48 -0000

I presented PubSub ‘-01’ requirements in NETCONF at IETF 92.    Changes in ‘-02’ are likely not enough for a speaking slot.

What might be interesting for a NETCONF speaking slot is an analysis of what requirements from “draft-ietf-i2rs-pub-sub-requirements” are met by “draft-clemm-netconf-yang-push”.   (During IETF 92, NETCONF reviewed draft-clemm. There was a strawman poll (12 yes, 0 no) where the WG indicated interest.)

Would NETCONF want Alex or I to speak on a requirements-to-technology comparison in Prague?

Eric

From: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, June 30, 2015 5:16 PM
To: 'Mahesh Jethanandani'
Cc: Rtg-yang-coord@ietf.org; i2rs@ietf.org; 'NETMOD Working Group'; 'Netconf'; 'BRUNGARD, DEBORAH A'
Subject: Re: [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)

Mahesh:

Ok.  I thought you were going to review the requirement documents and give I2RS an initial guess.  We have present these at 3 I2RS interims, and the slides are online.  I will send the minutes to the netconf working group for their review.

The presentation of the requirements will need the following time:


1)      10 top requirements – 5-10 minutes [Sue Hares]

2)      Ephemeral state – 15 minutes [Jeff Haas]

3)      Pub/sub requirements – 10-15 minutes [Eric Voit]

4)      Traceability [ 10-15 minutes]

5)      Security [10 minutes] [Sue Hares and Joel Halpern]

6)      Review of I2RS models [5 minutes]

7)
If you have heard pub/sub and traceability requirements, you may delete this from timeline.

Sue Hares

From: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] On Behalf Of Mahesh Jethanandani
Sent: Tuesday, June 30, 2015 3:44 PM
To: Susan Hares
Cc: Rtg-yang-coord@ietf.org<mailto:Rtg-yang-coord@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>; BRUNGARD, DEBORAH A; Netconf; NETMOD Working Group
Subject: Re: [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)

Susan,

The NETCONF WG acknowledges the receipt of the requirements.

These requirements need to be discussed in front of the NETCONF WG. Would suggest that i2rs WG present these requirements in front of the NETCONF WG during IETF 93 in Prague to kick start discussion within the WG. Please let us know how much time you (or someone from i2rs) would need to present the requirements.

Thanks.

On Jun 23, 2015, at 11:19 AM, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> 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


_______________________________________________
netmod mailing list
netmod@ietf.org<mailto:netmod@ietf.org>
https://www.ietf.org/mailman/listinfo/netmod

Mahesh Jethanandani
mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>