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

[Lou Berger <[e-mail]>]

> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord