Jeff:
With I2RS datastore (empheral) and I2RS Config there is always a chance that two different actions will change the same data. Take the example config you use in section 2.7 and assume that both I2rs and normal config want to modify this bgp config in the bgp routing process. First - do you think this is possible? If you do then section 2.7's atomic transactions will need to be augmented to indicate the interaction priority between the following different events I2RS (valid), I2RS (invalid/roll-back), config (valid), config (rollback). I define interaction priority as the priority (interrupt or sequencing) when one of these events overlaps with another. Sue -----Original Message----- From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Jeffrey Haas Sent: Friday, September 12, 2014 5:09 PM To: i2rs@ietf.org; net...@ietf.org Subject: [i2rs] I2RS requests to netmod/netconf (was netmod interim and i2rs requirements) With some help from Kent, Dean and Alia, I've put together a rough first draft of requirements I2RS has on netmod/netconf. It should be strongly noted that due to a confluence of a lot of bad timing (travel, vacation, etc.) I didn't have time to more broadly reach out and involve interested parties. As such, please note that this draft is not an I2RS WG draft and does not have current WG consensus. At best, it reflects my attempt to summarize prior discussions and turn them into requirements. This document will most assuredly be wrong and be revised. But it's primary purpose was to provide a start of the discussion of I2RS requirements at the netmod interim meeting next week. My abject apologies to the I2RS and netmod working groups - this was the fastest I could get the text out. Comments are appreciated. Flames are not unexpected. -- Jeff New Internet-Draft is available from the on-line Internet-Drafts directories. Title : I2RS requirements for netmod/netconf Author : Jeffrey Haas Filename : draft-haas-i2rs-netmod-netconf-requirements-00.txt Pages : 10 Date : 2014-09-12 Abstract: This document covers requests to the netmod and netconf Working Groups for functionality to support requirements to implement the I2RS architecture. The IETF datatracker status page for this draft is: <https://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirement s/> https://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirements / There's also a htmlized version available at: <http://tools.ietf.org/html/draft-haas-i2rs-netmod-netconf-requirements-00> http://tools.ietf.org/html/draft-haas-i2rs-netmod-netconf-requirements-00 _______________________________________________ i2rs mailing list <mailto:i2rs@ietf.org> i2rs@ietf.org <https://www.ietf.org/mailman/listinfo/i2rs> https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
