Re: [i2rs] Ephemeral - Should we use another word - (3/24 to 4/3) Call for opinion

Hi Sue I like maintaining the use of the term ephemeral and defining it as you indicated. By defining the time scope of reboot cycles etc. I think the use is clear. (I think if we used another term at this point we would have to similarly define that term too.) Cheers Don From: i2rs

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-boun...@ietf.org] On Behalf Of Susan Hares Sent:

Re: [i2rs] Draft minutes for December 16, 2014 interim

Hi Jeff My point was the Yang Model for L3 (as presented) seemed to outline L3, Service and Optical and missed L2 totally. (Not saying this is one document but one architecture as presented). Then the L2 Presentation had some L2 but missed several L2 capabilities. (VPLS, EVPN, VXLAN, PBB

Re: [i2rs] Primitive and complex objects in devices

Hi Dean I think the distinction you are making is based on an override capability and ownership. Primitive objects owned by configuration can be overridden by I2RS agents. Complex objects owned by configuration would typically not be overridden by I2RS agents. So there is an implied

Re: [i2rs] Primitive and complex objects in devices

12:30 PM To: Fedyk, Don Cc: i2rs@ietf.org Subject: Re: Primitive and complex objects in devices Don, Yes, you are right On Dec 12, 2014, at 9:29 AM, Fedyk, Don don.fe...@hp.com wrote: Hi Dean I think the distinction you are making is based on an override capability and ownership

Re: [i2rs] Point about writable running

Hi I've been trying to understand the models here. To me what we are describing is a general case of 2 entities trying to configure a switch. Consider one operator or user for short. A user may be able to write to the running config datastore some subset. A user may copy that to the config

Re: [i2rs] topology info model - what makes it a network model vs. a device model

Hi, From an IM standpoint a network wide view is useful to scope the view. Then you could map various views of the device with ever increasing scope: 1) What is contained on the device (local configured) 2) What is contained on the device in the RIB/interfaces etc(local operational state:

Re: [i2rs] topology info model - what makes it a network model vs. a device model

Hi Eric Actually I don't think the 2 are equivalent. My argument is TE as an example is only advertised as a summary (I'm sure there are other examples). So you can get more detail fetching the node by node information. (I'd agree with you if your argument is just limit the information to