Juergen, On Wed, Mar 11, 2015 at 3:24 AM, Juergen Schoenwaelder < [email protected]> wrote:
> On Fri, Mar 06, 2015 at 06:06:44PM -0500, Alia Atlas wrote: > > Given the excellent progress that the WG has been making - due to your > work > > and interest, I have been working on a simple rechartering with Sue and > > Here is the diff related to topology: > > - o The ability to extract information about topology from the network. > - Injection and creation of topology will not be considered as an > initial work item. > + o The ability to extract information about topology from the network. > + These models will be based on a generic topology model to support > + multiple uses. Injection and creation of topology will not be > considered > + as a work item. > > The first and third sentences are both about 'reading topology'. Does > this imply that the generic model will also be limited to 'reading > topology'? Or will the generic model also allow create topology? It's an interesting question. What use-cases do you see where writing the topology is appropriate? If one thinks of reading the topology as reading operational state, aren't read-write config and read-only operational recommended to be separated in YANG models (at least for now)? Alia > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
