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

Amanda Baber <amanda.baber@iana.org> Tue, 17 September 2019 04:49 UTC

Return-Path: <amanda.baber@iana.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 54B6C1200FB for <cbor@ietfa.amsl.com>; Mon, 16 Sep 2019 21:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 5lIoiwSBliAL for <cbor@ietfa.amsl.com>; Mon, 16 Sep 2019 21:49:30 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (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 A56231200F6 for <cbor@ietf.org>; Mon, 16 Sep 2019 21:49:30 -0700 (PDT)
Received: from PFE112-CA-1.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) by ppa5.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id x8H4nSEA001805 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <cbor@ietf.org>; Tue, 17 Sep 2019 04:49:29 GMT
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 16 Sep 2019 21:49:26 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1473.005; Mon, 16 Sep 2019 21:49:26 -0700
From: Amanda Baber <amanda.baber@iana.org>
To: "cbor@ietf.org" <cbor@ietf.org>
CC: "rt-comment@icann.org" <rt-comment@icann.org>
Thread-Topic: [IANA #1147225] WebSocket Subprotocol Name registration
Thread-Index: AQHVbRNItkuaAzsl2kexDII97MhXKw==
Date: Tue, 17 Sep 2019 04:49:26 +0000
Message-ID: <F64AC482-0342-4A2A-9082-5FCB17A157DE@iana.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3651515366_158942120"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-17_02:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Np4Bg4vP-HykV-GPeuEc-P23_iY>
Subject: [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 04:49:32 -0000

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