Re: [Netconf] WG Last Call (expires Sept 18 2014): express your opinion on RESTCONF modularity

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Thu, 09 October 2014 17:43 UTC

Return-Path: <mehmet.ersue@nsn.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 EB4261AD466 for <netconf@ietfa.amsl.com>; Thu, 9 Oct 2014 10:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 IvVCsEY3bcXB for <netconf@ietfa.amsl.com>; Thu, 9 Oct 2014 10:43:42 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 216401AD467 for <netconf@ietf.org>; Thu, 9 Oct 2014 10:43:41 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.14.3/8.14.3) with ESMTP id s99HhcIw016747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Oct 2014 17:43:39 GMT
Received: from DEMUHTC001.nsn-intra.net ([10.159.42.32]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s99Hhbd1013861 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Oct 2014 19:43:38 +0200
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.176]) by DEMUHTC001.nsn-intra.net ([10.159.42.32]) with mapi id 14.03.0195.001; Thu, 9 Oct 2014 19:43:37 +0200
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext Andy Bierman <andy@yumaworks.com>, Netconf <netconf@ietf.org>
Thread-Topic: [Netconf] WG Last Call (expires Sept 18 2014): express your opinion on RESTCONF modularity
Thread-Index: AQHP4kuCWskhNgGUiUOwBv6Ya3YWfZwoCczQ
Date: Thu, 09 Oct 2014 17:43:36 +0000
Message-ID: <E4DE949E6CE3E34993A2FF8AE79131F81950D70C@DEMUMBX005.nsn-intra.net>
References: <CABCOCHSt3K4O+9w2bDqq0-OvGZP0JcdnfH8_VHMeZ6umv3pJUA@mail.gmail.com> <53FCA5B7.3030105@cisco.com> <CABCOCHRFhK4h_M2NFX16iHRDCcYgj6kXpO11K2k=Zthod8+kUg@mail.gmail.com> <20140826.223423.176169295.mbj@tail-f.com> <CABCOCHSiYmbYY6SN=jCnkz9UFY6FZA_zEegxErX_fP+gmpET+w@mail.gmail.com> <54059AA9.4080902@bwijnen.net> <543394E7.7050902@bwijnen.net> <CABCOCHRGGnZGSibdV6ZaypTH8fPhPZKQB0HAa+JwrO+psRd7Jw@mail.gmail.com>
In-Reply-To: <CABCOCHRGGnZGSibdV6ZaypTH8fPhPZKQB0HAa+JwrO+psRd7Jw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.103]
Content-Type: multipart/alternative; boundary="_000_E4DE949E6CE3E34993A2FF8AE79131F81950D70CDEMUMBX005nsnin_"
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 13388
X-purgate-ID: 151667::1412876619-0000437E-CA79C0C3/0/0
Archived-At: http://mailarchive.ietf.org/arch/msg/netconf/YSEbLd-nnI0dlkeiIeGW-z6JqDg
Subject: Re: [Netconf] WG Last Call (expires Sept 18 2014): express your opinion on RESTCONF modularity
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: Thu, 09 Oct 2014 17:43:46 -0000

Hi Andy, All,

in reality it was 8 for a) and 8 for d) until Mahesh changed his mind in favor of d).
However with the conclusion mail below you may count both co-chair's votes in favor of a).

We indeed think that a) had reasonable support with good technical arguments, which are mainly "less options, less complexity, better understood".
You may count the co-chairs now to "old-school" but we believe that a) improves interoperability.

Mehmet

From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of ext Andy Bierman
Sent: Tuesday, October 07, 2014 6:27 PM
To: Bert Wijnen (IETF)
Cc: Netconf
Subject: Re: [Netconf] WG Last Call (expires Sept 18 2014): express your opinion on RESTCONF modularity

Hi,



On Tue, Oct 7, 2014 at 12:23 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net<mailto:bertietf@bwijnen.net>> wrote:
Dear NETCONF WG participants,

Appologies for being a bit late with trying to draw a conclusion on this
one.

As WG chairs, we believe that option a) had reasonable support with
good technical arguments why the choice was for that option.

On pure numerical count, we believe that option c won, but it was/is also
clear that it just complicates things and has more risk of
interoperability problems.


I think you meant that (d) got the most. And it wasn't "whatever it chooses",
it was "XML or JSON or both".



So we as chairs propose to go with option a).

If anyone still has REAL STRONG objections, pls speak up before
the end of this week. If we hear none by Friday Okt 10th,
we conclude that we have (rough) consensus to go with option a)

Bert and Mehmet.

Andy


On 02/09/14 12:23, Bert Wijnen (IETF) wrote:
On 26/08/14 22:49, Andy Bierman wrote:

Perhaps the co-chairs should decide how to proceed somehow.

Dear NETCONF WG participants, do you have an opinion?

So far I have seen only a few people express their opinion.

Please speak up so that we (WG chairs) have better data to judge if we
do or do not have WG (rough) consensus. Pls do speak up by 18 Sept 2014.

Please speak your mind about these options:

a) XML is mandatory
b) JSON is mandatory
c) XML and JSON are both mandatory
d) Both XML and JSON mandatory on client,
    server can implement whatever it chooses.
    Not clear yet how the client would find out, but that would of course
    be something to be worked out if we choose this option

Bert

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

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