Hi, I have not have enough time to work on this draft yet, but here are my initial concerns. I won't comment on the details yet.
1) datastores There is an opstate design team working on everything except ephemeral. We need 1 RPC defining the datastore framework and each specific datastore (known at this time). The I2RS protocol should not be that document. 2) requirements There should not be any duplication of requirements. There should just be normative text defining the protocol, and non-normative examples. 3) YANG validation As stated in BA, I am strongly against protocol documents redefining how YANG works for their spot solution. The YANG designer and operator want the data models to be as protocol-independent as possible. Andy On Thu, May 5, 2016 at 11:13 PM, Susan Hares <[email protected]> wrote: > <WG chair hat off, co-author hat on> > This version of the protocol strawman is the result of all the suggestions > from the I2RS meeting and inputs from other reviews. > Please let us know if you have additional reviews. > > Sue, Amit, and Andy > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Friday, May 06, 2016 2:11 AM > To: Amit Daas; [email protected]; Andy Bierman; Susan Hares > Subject: New Version Notification for > draft-hares-i2rs-protocol-strawman-02.txt > > > A new version of I-D, draft-hares-i2rs-protocol-strawman-02.txt > has been successfully submitted by Susan Hares and posted to the IETF > repository. > > Name: draft-hares-i2rs-protocol-strawman > Revision: 02 > Title: I2RS protocol strawman > Document date: 2016-05-05 > Group: Individual Submission > Pages: 52 > URL: > https://www.ietf.org/internet-drafts/draft-hares-i2rs-protocol-strawman-02.txt > Status: > https://datatracker.ietf.org/doc/draft-hares-i2rs-protocol-strawman/ > Htmlized: > https://tools.ietf.org/html/draft-hares-i2rs-protocol-strawman-02 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-hares-i2rs-protocol-strawman-02 > > Abstract: > This strawman proposal for the I2RS protocol supports I2RS > requirements for ephemeral data store, management data flows, and > protocol security. It proposes additions to the NETCONF, RESTCONF, > and YANG for these requirements. > > > > > Please note that it may take a couple of minutes from the time of > submission until the htmlized version and diff are available at > tools.ietf.org. > > The IETF Secretariat > > > _______________________________________________ > Netconf mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netconf >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
