[Cbor] [IANA #1147225] Request for Assignment (websocket)

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

Return-Path: <iana-shared@icann.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 BCFC3120227 for <cbor@ietfa.amsl.com>; Wed, 25 Sep 2019 16:29:18 -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 uE_nt7lgce4p for <cbor@ietfa.amsl.com>; Wed, 25 Sep 2019 16:29:16 -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 E1A9D1201E0 for <cbor@ietf.org>; Wed, 25 Sep 2019 16:29:16 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id AC4ABE0B8A for <cbor@ietf.org>; Wed, 25 Sep 2019 23:29:16 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id AA83620374; Wed, 25 Sep 2019 23:29:16 +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-9105-1568698350-278.1147225-9-0@icann.org>
References: <RT-Ticket-1147225@icann.org> <F64AC482-0342-4A2A-9082-5FCB17A157DE@iana.org> <ADFF7D45-0840-4AF5-991B-A3899682465E@tzi.org> <rt-4.4.3-9105-1568698350-278.1147225-9-0@icann.org>
Message-ID: <rt-4.4.3-18233-1569454156-62.1147225-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1147225
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: cbor@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 25 Sep 2019 23:29:16 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/-7AN_W3mJ027-WenT9O74-bUNxI>
Subject: [Cbor] [IANA #1147225] Request for Assignment (websocket)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 25 Sep 2019 23:29:19 -0000

HI Carsten, all,

We received a suggestion from the ADs that we specifically ask about the utility of websocket subprotocol IDs for CBOR (and, on that mailing list, JSON). Are there issues there? 

thanks,

Amanda Baber
Lead IANA Services Specialist

On Tue Sep 17 05:32:30 2019, cabo@tzi.org wrote:
> 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