Re: [Netconf] Reminder: Action by Dec 20th 2013 PLEASE: Draft charter after consensus call
"ietfdbh" <ietfdbh@comcast.net> Wed, 18 December 2013 17:41 UTC
Return-Path: <ietfdbh@comcast.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E7EB1AE021 for <netconf@ietfa.amsl.com>; Wed, 18 Dec 2013 09:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level:
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k9QiJpEMq4-e for <netconf@ietfa.amsl.com>; Wed, 18 Dec 2013 09:41:33 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA541AC448 for <netconf@ietf.org>; Wed, 18 Dec 2013 09:41:33 -0800 (PST)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta13.westchester.pa.mail.comcast.net with comcast id 30lB1n0041wpRvQ5D5hXeK; Wed, 18 Dec 2013 17:41:31 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta18.westchester.pa.mail.comcast.net with comcast id 35hX1n0022yZEBF3e5hXg9; Wed, 18 Dec 2013 17:41:31 +0000
From: ietfdbh <ietfdbh@comcast.net>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, 'Netconf' <netconf@ietf.org>
References: <E4DE949E6CE3E34993A2FF8AE79131F8227417@DEMUMBX005.nsn-intra.net> <52B17B74.1050200@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA129F44E8@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA129F44E8@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 18 Dec 2013 12:41:26 -0500
Message-ID: <02e501cefc18$60dddb10$22999130$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEmI7IVCFtaF9PUijB0b9MDthTEjwJk+F3/AeK431qbiarHgA==
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1387388491; bh=QLCm39EsehXElSJLmRmNuILEO/W6cyXAyFvulyfwUgo=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=IBmSjhGzkxXlAgA7JNtEYlamjzvnSbOae5Hlt62Uw98Buaq4qzEt9/011i4VZfuB1 vClHRnmRZ5Fes0Jl5i4s4C39xQM6l6OyboQ9Tf+Ma44KgSH5IIWRUOwX7uWBlOIXgS EE2rbkLEZqPkVttMX8S8ijKhO9j1oqVNIPg8YHG6umDpBGDLMdpy3wlcUutOuZS9a5 4w9sjQRUo+pRW4QjaK0NpvsID9zzzYgdp/VEDu7zbL7o1JnIlunKFMDJIFyCPZHd3h eTfqinXs/RD0f+kpBaLiUybNvhaYy6D3HqI0i5E5a0eFMyY8BatsdIzr5EbUUkQK2/ 01Abx2qXBSoxA==
Subject: Re: [Netconf] Reminder: Action by Dec 20th 2013 PLEASE: Draft charter after consensus call
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Dec 2013 17:41:35 -0000
Hi, I agree with Dan that starting a RESTCONF effort in the same WG could be destabilizing. I think it might be better to do this work in a separate WG that works closely with NETCONF. David Harrington ietfdbh@comcast.net +1-603-828-1401 > -----Original Message----- > From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Romascanu, > Dan (Dan) > Sent: Wednesday, December 18, 2013 9:18 AM > To: Bert Wijnen (IETF); Netconf > Subject: Re: [Netconf] Reminder: Action by Dec 20th 2013 PLEASE: Draft > charter after consensus call > > Hi, > > I raised questions in Vancouver about the wisdom of doing RESTCONF in the > same WG as NETCONF. I still think that RESTCONF is a different protocol, and > that doing two protocols - the continuation of the development of NETCONF > and a new protocol RESTCONF - in the same WG called NETCONF may be > confusing for people who are not part of this community, and create doubts > about the status and stability of NETCONF. I acknowledge that I am on the > rough part of the consensus. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Bert > Wijnen > > (IETF) > > Sent: Wednesday, December 18, 2013 12:40 PM > > To: Netconf > > Subject: [Netconf] Reminder: Action by Dec 20th 2013 PLEASE: Draft > > charter after consensus call > > > > We've had many emails on our WG mailing list, so maybe this one did > > escape your attention. Please let us (WG hcairs) know if you have any > > issues with this draft new WG charter. If we do not hear any by Dec > > 20th, we will pss it to our AD for approval by th IESG. > > > > It is always nice to hear that WG participants do agree too! > > > > Bert and Mehmet > > > > On 12/11/13 2:56 PM, Ersue, Mehmet (NSN - DE/Munich) wrote: > > > Dear NETCONF WG, > > > we had two consensus calls ended on December 4, 2013. > > > > > > * Verifing session consensus with the maillist on RFC5539bis new > > port and YANG module separation > > > _http://www.ietf.org/mail- > > archive/web/netconf/current/msg08445.html_ > > > * Verifing session consensus on RESTCONF as WG item with the > > maillist > > > > > > _http://www.ietf.org/mail- > archive/web/netconf/current/msg08444.html_ > > > > > > The co-chairs think that there was support for the action points and > > no objections to the consensus from the Vancouver NETCONF session. > > > We think we can go one step further.The co-chairs agreed to have > > Reverse SSH as a separate document for the time being. > > > Below is the relevant part of the draft charter. Please comment by > > December 20, 2013 EOB PT. > > > We will then pass it on to our AD for approval by IESG. > > > Bert & Mehmet > > > --------------- > > > In the current phase of NETCONF's incremental development the > > workgroup > > > will focus on following items: > > > 1. Develop the call home mechanism for the mandatory SSH binding > > (Reverse > > > SSH) providing a server-initiated session establishment. > > > 2. Advance NETCONF over TLS to be in-line with NETCONF 1.1 (i.e., > > update > > > RFC 5539) and add the call home mechanism to provide a server- > > initiated > > > session establishment. > > > 3. Combine the server configuration data models from Reverse SSH > > and > > > RFC5539bis drafts in a separate YANG module. > > > 4. Develop a RESTful protocol (RESTCONF) that provides a > > programmatic > > > interface for accessing data defined in YANG, using the datastores > > > defined in NETCONF. The two parts concerning RESTCONF protocol over > > > HTTP and the YANG patch operation will be prepared in separate > > drafts. > > > Goals and Milestones: > > > Jan 2014 - Submit initial WG drafts for RESTCONF as WG item > > > Apr 2014 - WGLC for RFC5539bis > > > Apr 2014 - WGLC for Reverse SSH > > > Apr 2014 - WGLC for NETCONF server configuration data model > > > May 2014 - Submit Reverse SSH to AD/IESG for consideration as > > Proposed Standard > > > May 2014 - Submit RFC5539bis to AD/IESG for consideration as > > Proposed Standard > > > Jun 2014 - WGLC for RESTCONF > > > Aug 2014 - Submit RESTCONF to AD/IESG for consideration as Proposed > > > Standard > > > > > > > > > _______________________________________________ > > > 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 > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf
- [Netconf] Draft charter after consensus call Ersue, Mehmet (NSN - DE/Munich)
- [Netconf] Reminder: Action by Dec 20th 2013 PLEAS… Bert Wijnen (IETF)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Romascanu, Dan (Dan)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… ietfdbh
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Reinaldo Penno (repenno)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Ladislav Lhotka
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Romascanu, Dan (Dan)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Ladislav Lhotka
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Andy Bierman
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Ersue, Mehmet (NSN - DE/Munich)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Reinaldo Penno (repenno)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Juergen Schoenwaelder
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Alexander Clemm (alex)
- Re: [Netconf] Reminder: Action by Dec 20th 2013 P… Lisa Huang (yihuan)