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

"Amanda Baber via RT" <iana-prot-param-comment@iana.org> Wed, 25 September 2019 23:30 UTC

Return-Path: <iana-shared@icann.org>
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 0E4F11201E0 for <json@ietfa.amsl.com>; Wed, 25 Sep 2019 16:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.178
X-Spam-Level:
X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 0KwQ62zp5Dtl for <json@ietfa.amsl.com>; Wed, 25 Sep 2019 16:30:35 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2927F1201C6 for <json@ietf.org>; Wed, 25 Sep 2019 16:30:35 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id 03466E0B8A for <json@ietf.org>; Wed, 25 Sep 2019 23:30:35 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id 0147520374; Wed, 25 Sep 2019 23:30:35 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-prot-param-comment@iana.org>
Reply-To: iana-prot-param-comment@iana.org
In-Reply-To: <rt-4.4.3-6257-1568696553-1328.1147224-9-0@icann.org>
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>
Message-ID: <rt-4.4.3-18233-1569454234-1725.1147224-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1147224
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: json@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 25 Sep 2019 23:30:34 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/2M2CkjYH0HIWBNS7eQHaUxbtCCc>
Subject: [Json] [IANA #1147224] Request for Assignment (websocket)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 25 Sep 2019 23:30:37 -0000

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