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-boun...@ietf.org] On Behalf Of
Mahesh Jethanandani
Sent: Tuesday, June 30, 2015 3:44 PM
To: Susan Hares
Cc: rtg-yang-co...@ietf.org; i...@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 sha...@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 (
https://datatracker.ietf.org/doc/draft-ietf-i2rs-architecture/
draft-ietf-i2rs-architecture-09) 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) https://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/
draft-ietf-i2rs-ephemeral-state-00
2)
https://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/
draft-ietf-i2rs-pub-sub-requirements-02
3) https://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/
draft-ietf-i2rs-traceability-03
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:
- https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/
draft-ietf-i2rs-rib-data-model-00
- 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:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo/
draft-ietf-i2rs-yang-network-topo-01
o L3 topology model:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/
draft-ietf-i2rs-yang-l3-topology-00
o L2 topology model:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/
draft-ietf-i2rs-yang-l2-network-topology-00
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
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:
