Re: [Netconf] New WGLC for a proposed new WG Charter - respond BEFORE Sept 1st

Benoit Claise <bclaise@cisco.com> Wed, 05 September 2012 14:38 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C0321F84B2 for <netconf@ietfa.amsl.com>; Wed, 5 Sep 2012 07:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.279
X-Spam-Level:
X-Spam-Status: No, score=-4.279 tagged_above=-999 required=5 tests=[AWL=-1.680, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rX7P1OHfl93k for <netconf@ietfa.amsl.com>; Wed, 5 Sep 2012 07:38:40 -0700 (PDT)
Received: from av-tac-bru.cisco.com (spooky-brew.cisco.com [144.254.15.113]) by ietfa.amsl.com (Postfix) with ESMTP id F390D21F846A for <netconf@ietf.org>; Wed, 5 Sep 2012 07:38:39 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q85Ecaq0029286; Wed, 5 Sep 2012 16:38:36 +0200 (CEST)
Received: from [10.60.67.92] (ams-bclaise-89111.cisco.com [10.60.67.92]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q85EcX2f020137; Wed, 5 Sep 2012 16:38:33 +0200 (CEST)
Message-ID: <504763E9.3040600@cisco.com>
Date: Wed, 05 Sep 2012 16:38:33 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <502D073D.7090200@bwijnen.net> <502D7052.2070302@bwijnen.net> <m28vddyjn1.fsf@nic.cz> <502E0A3B.9010008@bwijnen.net>
In-Reply-To: <502E0A3B.9010008@bwijnen.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: netconf <netconf@ietf.org>
Subject: Re: [Netconf] New WGLC for a proposed new WG Charter - respond BEFORE Sept 1st
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 14:38:41 -0000

+ 1

Regards, Benoit.
> We had agreed in our last f2f meeting that people would submit
> individual I-Ds, and based on that we would potentially
> consider work in this space. So by all means do submit
> such individual drafts and discuss them on the mailing list.
>
> But we do not have a good problem statement or starting I-D
> to base this work on, so cannot put it on the current charter.
>
> Bert Wijnen
>
> On 8/17/12 11:04 AM, Ladislav Lhotka wrote:
>> Hi,
>>
>> I had the impression that there was a reasonable agreement that work 
>> on operational state data is needed. Although this problem lies 
>> somewhere between NETCONF and NETMOD, I think the NETCONF WG is now 
>> in a better position to start this work because apparently NETMOD WG 
>> will have to continue the work on the core data models for some time.
>>
>> So I propose the following fourth item for the charter:
>>
>> 4. The WG will investigate the relationship and interactions between 
>> configurations and
>>     operational state data, propose their appropriate representation 
>> and semantics, and
>>     devise methods for effective data modeling of both configurations 
>> and operational state data.
>>     It is expected that this work will be carried out in a close 
>> sooperation with the NETMOD WG.
>>
>> Lada
>>
>> "Bert Wijnen (IETF)" <bertietf@bwijnen.net> writes:
>>
>>> Based on the comments and feedback and the positions
>>> expressed on the mailing list, it is clear that after all
>>> we did NOT have consensus on the new WG charter.
>>>
>>> Without further ado, this is another proposed WG charter.
>>> It focuses on the things that we do seme to have agreement on.
>>>
>>> Pls comment and/or express your support or objections
>>> no later than August 31, 2012.
>>>
>>> OK, new chapter text (omitting the description of what we have
>>> achieved sofar):
>>>
>>>     In the current phase of the incremental development of NETCONF the
>>>     workgroup will focus on following items:
>>>
>>>     1. Advance NETCONF over TLS to be in-line with NETCONF 1:1.
>>>        This means that RFC5593 needs to be updated.
>>>
>>>     2. Based on the implementation, deployment experience and 
>>> interoperability
>>>        testing, the WG will document the status of NETCONF in a report.
>>>        Based on this, the WG may decide to make some clarifications to
>>>        RFC6241 and RFC6242 (then also fixing any reported errata).
>>>
>>>     3. Since Netconf over BEEP and over SOAP seem not being deployed
>>>        the WG will write a document that makes those 2 protocols
>>>        (RFC4743 and RFC4744) HISTORIC.
>>>
>>> Goals and Milestones:
>>>     done     - Send with-defaults to IESG for consideration as 
>>> Proposed Standard
>>>     done     - WG Last Call on rfc4741bis
>>>     done     - rfc4741bis to IESG for consideration as Proposed 
>>> Standard
>>>     done     - Send rfc4742bis to IESG for consideration as proposed 
>>> Standard.
>>>     done     - first WG draft (rev 00) on NACM posted
>>>     done     - first WG draft (rev 00) on NETCONF specific YANG 
>>> modules posted
>>>     done     - WGLC for NACM document
>>>     done     - WGLC for NETCONF specific notifications document
>>>     done     - submit NACM document to IESG for consideration as 
>>> Proposed Standard
>>>     done     - submit NETCONF specific notifications  document to 
>>> IESG for
>>>                consideration as Proposed Standard
>>>     Aug 2012 - submit initial WG draft for rfc5539bis
>>>     Aug 2012 - submit initial WG draft for making RFC4743 and 
>>> RFC4744 historic.
>>>     Sep 2012 - WGLC for rfc5539bis
>>>     Sep 2012 - WGLC for RFC4743 and 4743 to historic
>>>     Oct 2012 - submit rfc5539bis to AD/IESG for consideration as 
>>> Proposed Standard
>>>     Oct 2012 - submit request to AD/IESG to make RFC4743 and 4744 
>>> historic
>>>     Nov 2012 - Collect Implementation/Deployment reports for RFC6241 
>>> and 6242
>>>     Dec 2012 - Initial I-D for RFC6241/6242 
>>> implementation/deployment experience
>>>     Jan 2013 - WGLC on RFC6241/6242 implementation/deployment 
>>> experience
>>>     Feb 2013 - submit RFC6241/6242 implementation/deployment 
>>> experience doc
>>>                to IESG for publication as Informational RFC.
>>>     Mar 2013 - Evaluate if more work needs to be done by NETCONF WG 
>>> or close WG
>>>
>>> Bert and Mehmet
>>> _______________________________________________
>>> Netconf mailing list
>>> Netconf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netconf
>>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
>