Re: [Json] [IANA #1147224] Request for Assignment (websocket)

Mark Nottingham <mnot@mnot.net> Thu, 26 September 2019 00:07 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E65E412001A for <json@ietfa.amsl.com>; Wed, 25 Sep 2019 17:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=GD+bIx1F; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KsmmrKaj
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 selFgN1sj8Jd for <json@ietfa.amsl.com>; Wed, 25 Sep 2019 17:07:00 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBC4B12004D for <json@ietf.org>; Wed, 25 Sep 2019 17:06:59 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 2BA5F615; Wed, 25 Sep 2019 20:06:58 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 25 Sep 2019 20:06:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=y 2ikPudxnW+WYBua/+tE1YZemHoWeKblLa8j/vIWV/c=; b=GD+bIx1FGxr2I4cd4 fMviVAyLpUkueafwcZInkKls1TRUxHSyGSrh6CBcX30lLWq1Q/0v3w31k2F09Kn8 IbjRvjsv1JcIyF/pKXpNALrhs806APTwUXIGoygZ5zyCgRtTn8C2Dzpgl1XwJEl2 lKzq8Hrx6k3KiJo5Nrg0Evzi6eU+hOPSsvznMYe1pL8u00hZqU8DXdrraFGH/nps VWdRDS9NJgIQoPOYAmwA1q/PfYszPkaysYLILbwmHAZoOMuUXyssHbBvhw72WNJT krif8cL3XH+IFJWvA/8w7VicxXa1yjTVuu4IWtS52umGFi/AlJ1oNKq93qoLYy9X DstDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=y2ikPudxnW+WYBua/+tE1YZemHoWeKblLa8j/vIWV /c=; b=KsmmrKaj70P6cphgJA2l0Cat5v4j2LcdJXcYYKdh4pjVCXPx0JhdwoFYl M0o0cuIu1WinbEReXUG38gaOnSJ6tW7epGaj+4Bii45oHIojcObmswQRAzBb7fO0 +V0IQGxTFy8n2fYEs5g/Ux8Y761h5w+dy/fXLtqPyMMAR1BJciRSJnBMZB3MZW4P 6HHlGJBbQGqW4I6v5l25c9r4BkOMGiQ7G15qJ1HqIAMe83dBJ42ra+arhEhNrknZ fDxdMPTrScen0xLZ/EmT9qj5/BJ7QIOonZXlI7TzaMMI9jOrZKrW/5KQqyZ9HH5Z SsVrwJnux/ji9O8xa42e8mDzSg52A==
X-ME-Sender: <xms:IAGMXQKoXRUkvNbNG1ysv8yIYoNuroni8JRiz69UhBvtV4gCqFa5IA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrfeefgdeftdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesthhqmh dthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhn ohhtrdhnvghtqeenucffohhmrghinhepvggtmhgrqdhinhhtvghrnhgrthhiohhnrghlrd horhhgpdhivghtfhdrohhrghdpmhhnohhtrdhnvghtpdhirghnrgdrohhrghenucfkphep uddrudegfedrheelrdejnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnoh htrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:IAGMXbwaLG3ebUiAG2qDWYjvGOqjGI_bPL-ZKuWuA9sTDn6LLBHreQ> <xmx:IAGMXS3hw2gWBZfQPZ0XdbKJLweTA1eT_g2qU2ER4jET7MNpFMdeeA> <xmx:IAGMXbyeseItZxAQRxusxptkjJJL9UfWJhr_uhMZYbqSBHEPQns5lQ> <xmx:IQGMXSH1qnM1kqnPdrnYsjJL8UBMuD9uhzFb-ig42WuzfMbPaRddPA>
Received: from [IPv6:2001:8004:1200:70bc:c9af:ecc3:4600:bc56] (unknown [1.143.59.7]) by mail.messagingengine.com (Postfix) with ESMTPA id 9EE318005C; Wed, 25 Sep 2019 20:06:54 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <3530055a-b7db-1a16-24bd-060b31144136@outer-planes.net>
Date: Thu, 26 Sep 2019 10:06:49 +1000
Cc: iana-prot-param-comment@iana.org, json@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AFF8A0C-DB07-406B-B87D-28C8FA756819@mnot.net>
References: <RT-Ticket-1147224@icann.org> <7888644A-1F38-413E-81F8-B43A58BE3972@iana.org> <69996e23-6d23-8ed2-482a-de79ff348b66@gmx.de> <rt-4.4.3-6257-1568696553-1328.1147224-9-0@icann.org> <rt-4.4.3-18233-1569454234-1725.1147224-9-0@icann.org> <3530055a-b7db-1a16-24bd-060b31144136@outer-planes.net>
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Ec3Mrv7ywoHzdxTzXXk4Ef677Jg>
Subject: Re: [Json] [IANA #1147224] Request for Assignment (websocket)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 00:07:05 -0000

+1

> On 26 Sep 2019, at 9:59 am, Matthew A. Miller <linuxwolf+ietf@outer-planes.net> wrote:
> 
> In my opinion, a generic "json" WebSocket subprotocol does not make
> sense.  JSON is too generic a content format for a client and server to
> adequately understand what the WebSocket session would be used for.
> 
> If there were a specification that made it clearer what the intent is,
> my opinion might change.
> 
> 
> - m&m
> 
> Matthew A. Miller
> On 19/09/25 17:30, Amanda Baber via RT wrote:
>> Hi Julian, all,
>> 
>> We received a suggestion from the ADs that we specifically ask about the utility of websocket subprotocol IDs for JSON (and CBOR, the subject of the other request we received). Are there issues there? 
>> 
>> thanks,
>> 
>> Amanda Baber
>> Lead IANA Services Specialist
>> 
>> On Tue Sep 17 05:02:33 2019, julian.reschke@gmx.de wrote:
>>> On 17.09.2019 06:50, Amanda Baber wrote:
>>>> Hi all,
>>>> 
>>>> IANA has received a request to register "json" in the WebSocket
>>>> Subprotocol Name registry at
>>>> 
>>>> https://www.iana.org/assignments/websocket/websocket.xml#subprotocol-
>>>> name
>>>> 
>>>> Barry Leiba and Alexey Melnikov suggested asking this mailing list
>>>> for opinions on this request.
>>>> 
>>>> This is all of the information that was provided:
>>>> 
>>>> ===
>>>> 
>>>> Type of Assignment:
>>>> WebSocket Subprotocol ID: `json`, Common Name: `JavaScript Object
>>>> Notation`
>>>> 
>>>> Description:
>>>> A lightweight messaging protocol for structured data using simple
>>>> data types. Defined in http://www.ecma-
>>>> international.org/publications/files/ECMA-ST/ECMA-404.pdf
>>>> 
>>>> ===
>>>> 
>>>> We currently have only the requester's name as an entry for the
>>>> registry's "Reference" field.
>>>> 
>>>> We're also asking the CBOR mailing list to comment on a request to
>>>> register "cbor."
>>> 
>>> That looks insufficient to me. The definition of a payload format
>>> isn't
>>> a protocol definition, as required by
>>> <https://tools.ietf.org/html/rfc6455#section-11.5>:
>>> 
>>>> Subprotocol Definition
>>>>   A reference to the document in which the subprotocol being used
>>>>   with the WebSocket Protocol is defined.
>>> 
>>> Best regards, Julian
>> 
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json
>> 
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

--
Mark Nottingham   https://www.mnot.net/