IETF Logo Mail Archive

Re: [Cbor] [IANA #1147225] WebSocket Subprotocol Name registration

Carsten Bormann <cabo@tzi.org> Tue, 17 September 2019 05:32 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B6A1200B4 for <cbor@ietfa.amsl.com>; Mon, 16 Sep 2019 22:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.195
X-Spam-Level:
X-Spam-Status: No, score=-4.195 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 kjb_bJv9zK-v for <cbor@ietfa.amsl.com>; Mon, 16 Sep 2019 22:32:15 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 73DA21200A4 for <cbor@ietf.org>; Mon, 16 Sep 2019 22:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x8H5Vh1Z003600; Tue, 17 Sep 2019 07:31:48 +0200 (CEST)
Received: from [100.64.60.36] (ip-109-40-130-132.web.vodafone.de [109.40.130.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 46XWv26lj9z1Bp8; Tue, 17 Sep 2019 07:31:42 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-FA7D4DFC-03C8-4A4D-A725-A34AD8569362"
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <F64AC482-0342-4A2A-9082-5FCB17A157DE@iana.org>
Date: Tue, 17 Sep 2019 08:31:41 +0300
Cc: "cbor@ietf.org" <cbor@ietf.org>, "rt-comment@icann.org" <rt-comment@icann.org>
Content-Transfer-Encoding: 7bit
Message-Id: <ADFF7D45-0840-4AF5-991B-A3899682465E@tzi.org>
References: <F64AC482-0342-4A2A-9082-5FCB17A157DE@iana.org>
To: Amanda Baber <amanda.baber@iana.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/l8HPdS9Ikhl-tLN7u9zmNkcUv0c>
Subject: Re: [Cbor] [IANA #1147225] WebSocket Subprotocol Name registration
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 05:32:18 -0000

To me it seems such a protocol would be about cbor sequences, not single cbor data items. The fact that I have to guess this, demonstrates the registration request is underspecified. 

Sent from mobile, sorry for terse

> On 17. Sep 2019, at 07:49, Amanda Baber <amanda.baber@iana.org> wrote:
> 
> Hi all,
> 
> IANA has received a request to register "cbor" 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: `cbor`, Common Name: `Concise Binary Object Representation`
> 
> Description:
> A concise binary object format for representing structured data. Defined in https://tools.ietf.org/html/rfc7049
> 
> ===
> 
> We understand that if this registration can be made, the RFC should not be listed on its own in the Subprotocol Definition field. In addition, we currently have only the requester's name to list in the registry's "Reference" field. 
> 
> We're also asking the JSON mailing list to comment on a request to register "json."
> 
> thanks,
> Amanda
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

v2.23.0 | Report a Bug | By Email