Re: [i2rs] 2 week WG adoption call for draft-dong-i2rs-l2-network-topology-01.txt

Hi Sue

I agree. Recent L2 control planes have leverage common mechanisms such as routing as well as supporting learning. I think it helps to model based on the generic model with common terms at L2 and L3.

Cheers,
Don

From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, April 06, 2015 9:46 AM
To: 'Thomas D. Nadeau'
Cc: i2rs@ietf.org; 'Alia Atlas'; 'Dongjie (Jimmy)'
Subject: Re: [i2rs] 2 week WG adoption call for draft-dong-i2rs-l2-network-topology-01.txt

Tom:

See the charter text from http://datatracker.ietf.org/wg/i2rs/charter/

o The ability to extract information about topology from the network.  Injection and creation of topology will not be considered as a work item. Such topology-related models will be based on a generic  topology model to support multiple uses; the generic topology model should support topology extension for non-I2RS uses.

The L2 draft is a Protocol independent an extension of the generic protocol-independent topology module at layer 2.  Please see draft-clemm-i2rs-yang-network-topo-04<http://datatracker.ietf.org/doc/draft-clemm-i2rs-yang-network-topo/> for details on generic model that points to multiple layers.

The L3 and L2 drafts provide layers of the protocol-independent.  The L1 Topology draft and Service topology drafts need addition work to be aligned with the TEAS WG and other service topology WGs (L3SM, SFC, and SUPA BOF).  Drafts at the L1 layer and Service layer are still within the protocol independent topology.

The WG Adoption calls (L3 topology and L2 topology) are based on this understanding of the I2RS charter

Sue  Hares

From: Thomas D. Nadeau [mailto:tnadeau@lucidvision.com]
Sent: Monday, April 06, 2015 9:28 AM
To: Susan Hares
Cc: i2rs@ietf.org<mailto:i2rs@ietf.org>; Dongjie (Jimmy)
Subject: Re: [i2rs] 2 week WG adoption call for draft-dong-i2rs-l2-network-topology-01.txt

            Is this currently in the charter or does the charter need to be extended
to allow for non-RIB related topology models to be included in i2rs? As I recall,
this is why we didn't do any L1 topology for optical networks, which was
something one particular operator requested at the time but was pushed
back based on that not being in the charter.  At the time, the message was
that we should only focus on l3 topology (i.e.: routing/RIB-related).

o The ability to extract information about topology from the network.
Injection and creation of topology will not be considered as a work
item. Such topology-related models will be based on a generic
topology model to support multiple uses; the generic topology model
should support topology extension for non-I2RS uses.
o Other use cases may be adopted by the working group only through
rechartering.
- Yang Data Models consistent with the use cases. Such documents
should include an information overview. The existing WG draft -
draft-ietf-i2rs-rib-info-model - that is just an informational model
can be completed or extended with the associated YANG data model.

On Apr 6, 2015:9:11 AM, at 9:11 AM, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:

This begins a 2 week adoption call for draft-dong-i2rs-l2-network-topology-01.

Please indicate in your comments “support” or “no support” and discuss how this draft will allow I2RS client-agent pairs to query information about L2 topology.  The draft can be found at:

http://datatracker.ietf.org/doc/draft-dong-i2rs-l2-network-topology/

Sue Hares and Jeff Haas

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