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

[Susan Hares]

Sergio: 

 

Just in case you missed in the rest of the email threads: 

 

Yes – I2RS plans to coordinate the topology model with the TEAS Topology model. 
 The work began with the authors last week, and will continue in a discussion 
of the TEAS And Topology authors next week (7/8)  in a conference call, and at 
IETF on Sunday (7/19 from 6-7pm). 

 

The I2RS WG will provide an update on the merging of these two models.  If you 
are a TEAS author, please let me know.   If you wish to help on an I2RS 
Topology model, the I2RS working group would appreciate your review of any 
model. 

 

I am personally working on the service layer model. 

 

Sue Hares 

From: BELOTTI, SERGIO (SERGIO) [mailto:sergio.belo...@alcatel-lucent.com] 
Sent: Wednesday, July 01, 2015 5:28 AM
To: Susan Hares; 'Mahesh Jethanandani'
Cc: rtg-yang-co...@ietf.org; i...@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)

 

Hello Susan,

-  Topology model which is a composite of:

o   Generic topology model:  
 
draft-ietf-i2rs-yang-network-topo-01 

o   L3 topology model:  
 
draft-ietf-i2rs-yang-l3-topology-00 

o   L2 topology model:  
 
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.   

 

Reading this , my question is whether there is intention for Traffic 
Engineering part of topology model to exploit/coordinate with Teas , and 
particularly with 

 draft-liu-teas-yang-te-topo or to proceed with distinct contributions internal 
to I2RS.

 

Thanks

Sergio

 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

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

[Mahesh Jethanandani]

> On Jun 30, 2015, at 3:13 PM, Eric Voit (evoit)  wrote:
> 
> 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”. 

Susan or somebody from i2rs WG can decide whether the suggested presentation 
would help clarify i2rs requirements to NETCONF. From a personal perspective it 
would certainly help to have examples of how the requirements could be met.

Cheers.

Mahesh Jethanandani
mjethanand...@gmail.com



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

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

[BELOTTI, SERGIO (SERGIO)]

Hello Susan,
-  Topology model which is a composite of:
o   Generic topology model: 
draft-ietf-i2rs-yang-network-topo-01
o   L3 topology model: 
draft-ietf-i2rs-yang-l3-topology-00
o   L2 topology model: 
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.

Reading this , my question is whether there is intention for Traffic 
Engineering part of topology model to exploit/coordinate with Teas , and 
particularly with
 draft-liu-teas-yang-te-topo or to proceed with distinct contributions internal 
to I2RS.

Thanks
Sergio

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

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

[Eric Voit (evoit)]

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-boun...@ietf.org] On Behalf Of 
Susan Hares
Sent: Tuesday, June 30, 2015 5:16 PM
To: 'Mahesh Jethanandani'
Cc: rtg-yang-co...@ietf.org; i...@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-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 
mailto: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 
(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)  
draft-ietf-i2rs-ephemeral-state-00
2)  
draft-ietf-i2rs-pub-sub-requirements-02
3)  
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:
-  
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: 
draft-ietf-i2rs-yang-network-topo-01
o   L3 topology model: 
draft-ietf-i2rs-yang-l3-topology-00
o   L2 topology model: 
draft-ietf-i2rs-yang-l2-network-topology-00
o   L1 Topology model: draft-zhang-i2rs-l1-topo-yang-model-01 (-02 released 
later thi

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

[Susan Hares]

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  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) 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 

2)   
 
draft-ietf-i2rs-pub-sub-requirements-02 

3)    
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:

-    
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:  
 
draft-ietf-i2rs-yang-network-topo-01 

o   L3 topology model:  
 
draft-ietf-i2rs-yang-l3-topology-00 

o   L2 topology model:  
 
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 - 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: