Perhaps you are right that I2RS never intends to configure topology, this is what RFC 7920 and 7921 talk about. That said, the base topology model clearly supports configured topologies (following the NMDA approach) but then it seems for TEAS this is not workable.
Note that RESTCONF and NETCONF protocol extension proposal I-Ds are in the making and the NETCONF charter is meanwhile in place with a target date for this work in Nov 2017. Sure, we all know that it is difficult to predict WG timing but creating a -state subtree may be something to regret in a year from now. /js On Mon, Jun 26, 2017 at 07:39:47PM +0000, Igor Bryskin wrote: > TE topology model client is a client application that talks netconf/restconf > with the server application implemting one or more TE topologies. > In contrast to I2RS topology server, which only exposes topologies (learnt > for example via IGP) as state information, TE topology model client can > configure TE Topologies with all the implications, such as intended/applied, > etc. > > Igor > From:Juergen Schoenwaelder > To:Igor Bryskin, > Cc:Alexander Clemm,[email protected],[email protected],[email protected], > Date:2017-06-26 15:27:49 > Subject:Re: [i2rs] I-D Action: draft-ietf-i2rs-yang-network-topo-13.txt > > On Mon, Jun 26, 2017 at 07:22:57PM +0000, Igor Bryskin wrote: > > Hi Jorgen, > > The reason is that TE topologies (e.g. anstract TE topologies) could be > > (re-)configured by a client, while I2RS topologies could not. > > Igor > > What is 'client' and what is 'reconfigured' and why does that not > apply to i2rs topologies? > > /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/> -- 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
