Re: [i2rs] WG LC for requirement documents (10/6 to 10/20/2015) -

Carlos: 

Very good question.  You are correct traceability was WG LC 4 months ago (6/12/2015) and pub/sub (10/2/2015).  This fine work paved the way for the rest of the I2RS requirements to be completed. The NETMOD/NETCONF chairs know these drafts have reached WG consensus. 

However, the other components of the I2RS requirements for the I2RS protocol were not complete (I2rs security, I2rs ephemeral state).  This WG LC asks the WG to review all the I2RS requirements as a whole group to see that the whole package of requirements are consistent. This WG LC will not change the results of the pub/sub WG LCs, but other eyes may review and provide you with additional review comments (always good).  

The I2RS WG, NETCONF/NETMOD WG, and the early I2RS protocol design team have spent a great deal of time in July – September working through the other requirements for the I2RS protocol so this WG LC (10/6 to 10/20)  is for the WG to consider all the WG requirements at one time.  

The 10/7/2015 I2RS interim provided some initial work on an I2RS strawman for the I2RS protocol.  The 10/21/2015 I2RS interim will provide addition details on the strawman based on all of these requirements. 

Thank you for asking this question,

Sue Hares 

From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Carlos Pignataro (cpignata)
Sent: Wednesday, October 14, 2015 9:25 PM
To: Susan Hares
Cc: Jeffrey Haas; i2rs@ietf.org; Alia Atlas
Subject: Re: [i2rs] WG LC for requirement documents (10/6 to 10/20/2015) -

Hi, Sue,

Sorry, I am a bit confused — draft-ietf-i2rs-traceability finished WG LC over 4 months ago.

Looking at https://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/history/ you might recall:

2015-06-12      03        Susan Hares    IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call
2015-05-26      02        Susan Hares    WG LC (5/26 to 6/9) for inclusion in requirements
2015-05-26      02        Susan Hares    IETF WG state changed to In WG Last Call from WG Document

And so did draft-ietf-i2rs-pub-sub-requirements BTW.

What is the goal of this new WG LC?

Thanks,

— Carlos.

On Oct 6, 2015, at 8:16 PM, Susan Hares <shares@ndzh.com> wrote:

This begins a 2 week WG LC on the following requirement documents for I2RS: 

draft-ietf-i2rs-ephemeral-state-02.txt  

 <http://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/> http://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/

Note: I2RS ephemeral state has a section on minimal NETCONF Changes.  

This section is blank and this will be discussed at the 10/17/2015 interim.

We will discuss whether this section should be kept or removed.   

draft-ietf-i2rs-protocol-security-requirements-01.txt 

 <http://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/> http://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/

draft-ietf-i2rs-pub-sub-requirements-03.txt 

 <http://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/> http://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/

draft-ietf-i2rs-traceability-03.txt 

 <http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/> http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/

Sue Hares 

_______________________________________________
i2rs mailing list
 <mailto:i2rs@ietf.org> i2rs@ietf.org
 <https://www.ietf.org/mailman/listinfo/i2rs> https://www.ietf.org/mailman/listinfo/i2rs