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 <[email protected]> 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/
> <http://datatracker.ietf.org/doc/draft-dong-i2rs-l2-network-topology/>
> <http://datatracker.ietf.org/doc/draft-clemm-i2rs-yang-l3-topo/>
>
> Sue Hares and Jeff Haas
>
> _______________________________________________
> i2rs mailing list
> [email protected] <mailto:[email protected]>
> https://www.ietf.org/mailman/listinfo/i2rs
> <https://www.ietf.org/mailman/listinfo/i2rs>
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
