IETF Logo Mail Archive

Re: [Netconf] Alexey Melnikov's Yes on draft-ietf-netconf-yang-patch-12: (with COMMENT)

Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 22 November 2016 06:19 UTC

Return-Path: <mjethanandani@gmail.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 D1C3D129562; Mon, 21 Nov 2016 22:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pp91WZqc4z0F; Mon, 21 Nov 2016 22:19:22 -0800 (PST)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74DB0129431; Mon, 21 Nov 2016 22:19:22 -0800 (PST)
Received: by mail-oi0-x242.google.com with SMTP id f201so1191972oib.0; Mon, 21 Nov 2016 22:19:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=ZAtzbUqAna4PCid6oCYOKU/vA3W9vfm+JfxDFPmm9Cs=; b=WzU0o0tj1R+dVU/GUtYoscjeYd5FuN1Bnp/H4XrQhFVi71uvfoHuHiHujRweCQSA4+ RoYO8r15w/ZeiN5d6xypIJopvx+DJuv3T0B1217Wl/1s0AeD2a0ocKOAELc+tRCBdum5 2Yo+n+krNKeW3eYR+M+bJKTabVmZwoS6Pg65KO75VIpU+v5l399E/FxBghM4twgoVrU7 mO7pL4EOKhnjpN5n9WHAu8MkP8LmiA0MIPHPCe+/f74X2N9YWvh7utXjllxJ1l1/YtY9 //5pkQt2aTE3LZS5lZ3SLucYwShbPqk3e88pSVjX/VOIe0YQV/TQw2THmttARrA6dOLv Ebcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=ZAtzbUqAna4PCid6oCYOKU/vA3W9vfm+JfxDFPmm9Cs=; b=KIfXeM3K/LjAhLjx++OATtEVgGdfZPtw613zI2wfazKtgBjKMvs1HXJ7JdfAMsZjdu wA2ILhiWr+tCPs2ib+0wIwa8V3RIgxvBgblr9Jy+VDu4MjcE0OArrGQiaKL7P+Apv7ml aK9V7P/jnQTg+6YI5jG6xyfxu0L9vQGQz1qs8Ir8b0nhv7Ui/9RWnXPQexV6LXV6qFF/ aGxUhZEvqV6lcrYR3gnbHMIRZuvje3U6nEXcyA20BW/FORP7xMG8/ppKK/93GEWjEELj aTyJs1x8HxbxZgzvXAXSeRZwnrxcSFjbTL9IKw39GTls9vtMHywGMwjjyBp/OzKAgUs1 10NQ==
X-Gm-Message-State: AKaTC00H3gTAEfibu3WtHBqeHIQvwk82TS2ft8gVQF5CFnWiRI1Y3zyRJEZI3flSJ+pqvQ==
X-Received: by 10.157.42.21 with SMTP id t21mr11231654ota.1.1479795561788; Mon, 21 Nov 2016 22:19:21 -0800 (PST)
Received: from mahesh-m-m8d1.attlocal.net (108-247-125-249.lightspeed.sntcca.sbcglobal.net. [108.247.125.249]) by smtp.gmail.com with ESMTPSA id o28sm8350484otb.22.2016.11.21.22.19.18 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 21 Nov 2016 22:19:20 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3CCCFDED-0123-40B3-B305-1B589728D0D6"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <CABCOCHSkpHWRx_5BQEcdv2T9-nffpO4hDdDWWaHJBWZFXzvxtg@mail.gmail.com>
Date: Mon, 21 Nov 2016 22:19:14 -0800
Message-Id: <D19C563F-E57B-42E7-A098-37F861AFB7CF@gmail.com>
References: <147777081285.30626.11496029872270655919.idtracker@ietfa.amsl.com> <804071FD-937E-484C-97F3-6D99EAAB699C@gmail.com> <CABCOCHQ2M14JCScs_bVKtfYUBJL3CV0X0+RV-=7KWpp=E7vy=g@mail.gmail.com> <69C29F0B-BC89-44C8-8046-18DCEB53EF17@fastmail.fm> <CABCOCHQFSAKBYfc5XNdTrS5+JNrvTSCSTq6dQocPvsKeqe1ExQ@mail.gmail.com> <F75A7877-138E-4720-926D-7D6F7E73E1FA@fastmail.fm> <CABCOCHTV-FxHyKmO02Z_Xwh0oY2nfHktM-gL6xdd8vmtWExNqA@mail.gmail.com> <C3866E7C-A142-4ED6-A60A-EBAE180D681B@fastmail.fm> <AB60C9A7-CB6B-4488-BAD9-193311918EEF@gmail.com> <CABCOCHSkpHWRx_5BQEcdv2T9-nffpO4hDdDWWaHJBWZFXzvxtg@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/MoYDt5DvVeEULaE4RtiOnv0N7UM>
Cc: Netconf <netconf@ietf.org>, draft-ietf-netconf-yang-patch@ietf.org, NETCONF Working Group <netconf-chairs@ietf.org>
Subject: Re: [Netconf] Alexey Melnikov's Yes on draft-ietf-netconf-yang-patch-12: (with COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 22 Nov 2016 06:19:24 -0000

Alexey, you consider the current media registration to be broken. However, Andy has given two examples of other media registrations which say something similar. Do you still consider the current template to be broken? If so, how would you suggest the entry should be modified? 

Thanks.

> On Nov 21, 2016, at 3:55 PM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> 
> 
> On Mon, Nov 21, 2016 at 3:47 PM, Mahesh Jethanandani <mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>> wrote:
> Alexey,
> 
>> On Nov 12, 2016, at 6:03 AM, Alexey Melnikov <aamelnikov@fastmail.fm <mailto:aamelnikov@fastmail.fm>> wrote:
>> 
>> Hi Andy,
>> 
>> On 12 Nov 2016, at 19:13, Andy Bierman <andy@yumaworks.com <mailto:andy@yumaworks.com>> wrote:
>>> 
>>> On Fri, Nov 11, 2016 at 5:57 PM, Alexey Melnikov <aamelnikov@fastmail.fm <mailto:aamelnikov@fastmail.fm>> wrote:
>>> Andy,
>>> 
>>> On 12 Nov 2016, at 02:14, Andy Bierman <andy@yumaworks.com <mailto:andy@yumaworks.com>> wrote:
>>> 
>>>>> The media type registrations in RESTCONF say 8-bit.
>>>> 
>>>> Then it might be broken too.
>>>> 
>>>> It was approved already, so take it up with th IESG
>>> 
>>> Different people on IESG are experts in different things. What you effectively said is that no bug can be accepted after the fact. It doesn't matter in this case, but I do find your attitude disturbing. 
>>> Best Regards,
>>> 
>>> 
>>> I do not see why RESTCONF and YANG Patch are broken because the
>>> media types say 8-bit.  Please explain what breaks.
>> 
>> I think you misunderstood: I didn't say that RESTCONF and YANG Patch are broken, I just said that the IANA registration template is slightly incorrect.
> 
> Would it help if we said that RESTCONF supports media type of 8-bit by default, and that support for any other encoding can be added later, if need be?
> 
> 
> I do not know how to write that text.
> There is no "by default". There is only utf-8 required.
> The charset parameter is not even supported in RESTCONF.
> We cannot speculate in this version of YANG Patch as to
> what charsets future versions of RESTCONF will require.

> 
>  
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
> 
> 
> 
> 
> Andy
>

v2.23.0 | Report a Bug | By Email