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

Andy Bierman <andy@yumaworks.com> Sat, 12 November 2016 21:31 UTC

Return-Path: <andy@yumaworks.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 BF683129552 for <netconf@ietfa.amsl.com>; Sat, 12 Nov 2016 13:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 HRX-WalA9jxC for <netconf@ietfa.amsl.com>; Sat, 12 Nov 2016 13:31:08 -0800 (PST)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (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 2D6EB129589 for <netconf@ietf.org>; Sat, 12 Nov 2016 13:31:07 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id x186so38641747vkd.1 for <netconf@ietf.org>; Sat, 12 Nov 2016 13:31:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kzI9GdrdudmYWKfIbpEYajMpzwu24fC5d1trkqPQg6M=; b=k6iyJq2zpHMaYc1UJPq7Hp8J+B3abW3RQ0O2hN47eZpibOaqOf4vX3rw/2LgL6HOAS HJ9WNS7nC77sVUn0XYGGBmAfDLX4Iru1FCxc7T3xCZvvIH/k/4X72pfQLzWU9O8EOEig ODPoiCpngw/cVIaCBBoKjm73zm9W6FvpP/mH+kIXB+mP7hG0eTVLAxVHJ8iWJ5rarIL8 WsB27OvUICB7fFSmPP6srG5uFKDi9yqCg/pM6yr7liE6De72XizKP12tp4aoFRgU4elb 0xEcEgr4zikb+V4pDL7EgnY/TrEHV703pUILX26uol2JQs57i/cnPg5pt2VCce7HD7vq AZ/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kzI9GdrdudmYWKfIbpEYajMpzwu24fC5d1trkqPQg6M=; b=VYg4r5XIbZAasuV1Yd7APfZBy9AdoG5Weht6HAj+kuINcs/yPT+Cf03XxmKGwIP0OC tEWBqGPl+UKWjSAdyAPnGBUeILceFu3B14edPNdQNAV6KVzeeHNXFWXlIpNlVNEJi5ZR 8gt10AnOjCWkVVlBxPLVxbZWU6wHgwNBZmXyQVBaeMbs5hXMDJECAMToMHLwXkRfysFc Owtu/2hcKak/EKn4HcMac1fIFTqu5pgMJvGapk7v9yLE7QL8vjnquHZSC8BexlfKmxdv 4pZbfRgCJO/T9PftlhDjW9uvX8CeuDlTFqHMnjY3fXoSMVMuO7kibBssxs7260Bc92FB bOCA==
X-Gm-Message-State: ABUngveYzumQWEfonMohyMbP8lCUba5K46aho41dOv9o7jwGUzCJ372i0LdISisU4EvYwlCTgFVX+hJ/wAaO6Q==
X-Received: by 10.31.60.129 with SMTP id j123mr5089329vka.30.1478986266183; Sat, 12 Nov 2016 13:31:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.64.129 with HTTP; Sat, 12 Nov 2016 13:31:05 -0800 (PST)
In-Reply-To: <C3866E7C-A142-4ED6-A60A-EBAE180D681B@fastmail.fm>
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>
From: Andy Bierman <andy@yumaworks.com>
Date: Sat, 12 Nov 2016 13:31:05 -0800
Message-ID: <CABCOCHQCjQmUKLCvwXWcWUH3353Dwkf4WMvA0cQZ7_9nmu55tg@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Type: multipart/alternative; boundary="001a114381fc062083054121532d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/oU6mV60PRZteJ4yoCz4ipklXPFc>
Cc: draft-ietf-netconf-yang-patch@ietf.org, The IESG <iesg@ietf.org>, Netconf <netconf@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: Sat, 12 Nov 2016 21:31:10 -0000

Hi,

Here are some examples of registrations:

cellml+xml

The charset parameter of application/cellml+xml is handled in the
same fashion as for application/xml, as specified in Section 3.2
of [RFC3023]. However, per conformance rule 4 of
[CELLML-UMBRELLA], valid CellML Umbrella documents MUST be in the
UTF-8 character set. If the charset parameter is present, it MUST
take the value "utf-8". CellML processing software SHOULD check
the charset field, and if it is present but not equal to "utf-8",
MAY attempt to recover from the error by processing the document
in the specified character set.


3gpdash-qoe-report+xml

Encoding considerations: 8bit
The utf-8 charset is always used for this type.


several use this text:


Encoding considerations:  Uses XML, which can employ 8-bit
   characters, depending on the character encoding used.  See RFC
   3023 [RFC3023], Section 3.2.


YANG data and YANG patch use UTF-8.
The UTF-16 charset is not used.
Can you suggest a registry entry that we should follow
to properly convey this requirement?


Andy


On Sat, Nov 12, 2016 at 6:03 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
wrote:

> Hi Andy,
>
> On 12 Nov 2016, at 19:13, Andy Bierman <andy@yumaworks.com> wrote:
>
>
> On Fri, Nov 11, 2016 at 5:57 PM, Alexey Melnikov <aamelnikov@fastmail.fm>
> wrote:
>
>> Andy,
>>
>> On 12 Nov 2016, at 02:14, Andy Bierman <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.
>