IETF Logo Mail Archive

Re: [Netconf] Reminder: Action by Dec 20th 2013 PLEASE: Draft charter after consensus call

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 18 December 2013 19:56 UTC

Return-Path: <dromasca@avaya.com>
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 A56051AE17A for <netconf@ietfa.amsl.com>; Wed, 18 Dec 2013 11:56:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level:
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] 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 fuE3ud9creqd for <netconf@ietfa.amsl.com>; Wed, 18 Dec 2013 11:56:05 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 7822C1ADF70 for <netconf@ietf.org>; Wed, 18 Dec 2013 11:56:05 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFABb9sVKHCzI1/2dsb2JhbABZgmkhOFW4f4EbFnSCJQEBAQECARIoRAsCAQgNCA0UEDIlAgQBEggah1oIAaZfo2AXjmE4gyOBEwSfAosogW2BPoIq
X-IronPort-AV: E=Sophos;i="4.95,508,1384318800"; d="scan'208";a="41637336"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Dec 2013 14:56:03 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 18 Dec 2013 14:45:07 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0158.001; Wed, 18 Dec 2013 20:56:02 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, Netconf <netconf@ietf.org>
Thread-Topic: [Netconf] Reminder: Action by Dec 20th 2013 PLEASE: Draft charter after consensus call
Thread-Index: AQHO+919qCVFIStNh0yva+xw3sPUeJpZ/gQQgACvKAD//7Bx4w==
Date: Wed, 18 Dec 2013 19:56:01 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA129F4DBA@AZ-FFEXMB04.global.avaya.com>
References: <E4DE949E6CE3E34993A2FF8AE79131F8227417@DEMUMBX005.nsn-intra.net> <52B17B74.1050200@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA129F44E8@AZ-FFEXMB04.global.avaya.com>, <m2k3f2dk7t.fsf@nic.cz>
In-Reply-To: <m2k3f2dk7t.fsf@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [198.152.73.21]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 19:56:06 -0000

Hi Lada,

As I said, I do not mind being on the rough side of the consensus. I believe that RESTCONF is important work, and it is more important that it's done than where it's done. 

However, as you used the argument - what does the scope below has with NETCONF? If at all, it has more to do with NETMOD. 

Regards,

Dan
  
________________________________________
From: Ladislav Lhotka [lhotka@nic.cz]


> Also, RESTCONF in fact is not a new protocol, it is, for the most part, an application of existing and well-established stuff: HTTP plus REST principles, plus of course YANG.

Lada

v2.23.0 | Report a Bug | By Email