Notice - intend to vote on websockets draft at Tues April 22 meeting

Steve, Andreas, others:
As to IANA registration requests for ports, Media/Mime types, (sub)Protocol names, etc

--
I needed to let you know that OASIS Staff handles these with IETF/IANA, at least in some important details and data points in the use  of the IANA request forms.
For the past several years, I have had Staff responsibility for this -- so let's please coordinate.
I have been working also the MQTT members as well, since they are planning to register a WebSocket ssubprotocol name ('mqtt'), per one of the latest drafts [1]
Thanks,
- Robin Cover
[1]  Draft MQTT specification
6  Using WebSocket as a network transport
If MQTT is transported over a WebSocket [RFC6455] connection, the following conditions apply:
* MQTT Control Packets MUST be sent in WebSocket binary data frames. If any other type of data frame is received the recipient MUST close the Network Connection [MQTT-6.0.0.1].
* A single WebSocket data frame can contain multiple or partial MQTT Control Packets. The receiver MUST NOT assume that MQTT Control Packets are aligned on WebSocket frame boundaries [MQTT-6.0.0.2].
* The client MUST include "mqtt" in the list of WebSocket Sub Protocols it offers [MQTT-6.0.0.3].
* The WebSocket Sub Protocol name selected and returned by the server MUST be "mqtt" [MQTT-6.0.0.4].
* The WebSocket URI used to connect the client and server has no impact on the MQTT protocol.
6.1 IANA Considerations
This specification requests IANA to register the WebSocket MQTT sub-protocol under the WebSocket Subprotocol Name registry with the following data:
Subprotocol Identifier    mqtt  Subprotocol Common Name   mqtt  Subprotocol definition     http://docs.oasis-open.org/mqtt/mqtt/v4.0/mqtt-v4.0.html
On Tue, Apr 15, 2014 at 12:13 PM, Steve Huston  < 
>  wrote:
Thanks for raising this, Andreas – excellent point.

The WebSockets RFC says:
  These subprotocol names should be registered as per  Section 11.5 .  To
   avoid potential collisions, it is recommended to use names that
   contain the ASCII version of the domain name of the subprotocol's
   originator.  For example, if Example Corporation were to create a
   Chat subprotocol to be implemented by many servers around the Web,
   they could name it " chat.example.com ".  If the Example Organization
   called their competing subprotocol " chat.example.org ", then the two
   subprotocols could be implemented by servers simultaneously, with the
   server dynamically selecting which subprotocol to use based on the
   value sent by the client.

   Subprotocols can be versioned in backward-incompatible ways by
   changing the subprotocol name, e.g., going from
   " bookings.example.net " to " v2.bookings.example.net ".  These
  subprotocols would be considered completely separate by WebSocket
   clients.  Backward-compatible versioning can be implemented by
   reusing the same subprotocol string but carefully designing the
   actual subprotocol to support this kind of extensibility.

So, the name should probably say oasis somewhere.

As for timing, I think sooner is better – the name registration is first-come-first-served so to ensure the registration is valid and obtainable before publishing  the doc with the name in it, I believe it is best to apply soon and possible update the spec reference later.

Thoughts?

-Steve
From:
  [mailto:  ]  On Behalf Of

Sent:  Tuesday, April 15, 2014 12:55 PM
To:

Subject:  Re: [amqp-bindmap] Notice - intend to vote on websockets draft at Tues April 22 meeting

Steve, Dave,
When does the IANA registration (“WebSocket Subprotocol Name”) happen - before CSD, after CSD, after CS?
Who triggers it?
Andreas
From:          Steve Huston < 
>
To:          "  " <  >,
Date:          15/04/2014 16:45
Subject:          [amqp-bindmap] Notice - intend to vote on websockets draft at Tues April 22 meeting
Sent by:          < 
>
Hello BINDMAPpers,
The current Advanced Message Queuing Protocol (AMQP)

WebSocket Binding (WSB)

Version 1.0 WD07 (
https://www.oasis-open.org/apps/org/workgroup/amqp-bindmap/download.php/52665/amqp-wsb-v1.0-wd07.doc
)  is ready to move ahead to Committee Specification Draft (CSD). I would like to hold a vote for the same at next Tuesday's meeting. During that meeting, I would like someone (ideally, David Ingham) to make the following motion:
"I move that the TC approve Advanced Message Queuing Protocol (AMQP)

WebSocket Binding (WSB)

Version 1.0 WD07 currently posted at
https://www.oasis-open.org/apps/org/workgroup/amqp-bindmap/download.php/52665/amqp-wsb-v1.0-wd07.doc
as a Committee Specification Draft and designate the MS-Word version of the document as authoritative."
-Steve

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

-------------------------------------------------------------------------

Deutsche Börse AG  Chairman of the Supervisory Board/  Vorsitzender des Aufsichtsrats:  Dr. Joachim Faber  Executive Board/Vorstand:  Dr. Reto Francioni (Chief Executive Officer/Vorsitzender),  Andreas Preuss (Deputy Chief Executive Officer/  stellv. Vorsitzender), Gregor Pottmeyer,  Hauke Stars, Jeffrey Tessler.  Aktiengesellschaft with registered seat in/mit Sitz in  Frankfurt am Main.  Commercial register/Handelsregister: HRB 32232  Local court/Amtsgericht Frankfurt am Main.

-----------------------------------------

Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen.  Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte  sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren  dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen  ist nicht gestattet.
The information contained in this message is confidential or protected by  law. If you are not the intended recipient, please contact the sender and  delete this message. Any unauthorised copying of this message or  unauthorised distribution of the information contained herein is prohibited.
Legally required information for business correspondence/  Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz:
http://deutsche-boerse.com/letterhead

--
Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink
Email:  
Staff bio:  http://www.oasis-open.org/people/staff/robin-cover  Cover Pages:  http://xml.coverpages.org/
Newsletter:  http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783