Re: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt

Christer Holmberg <> Mon, 20 January 2014 03:28 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 744281A0023 for <>; Sun, 19 Jan 2014 19:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EhpvAQVyK3fO for <>; Sun, 19 Jan 2014 19:28:56 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D83361A001F for <>; Sun, 19 Jan 2014 19:28:55 -0800 (PST)
X-AuditID: c1b4fb30-b7f228e000003e6c-48-52dc97f43fbc
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 83.AD.15980.4F79CD25; Mon, 20 Jan 2014 04:28:52 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Mon, 20 Jan 2014 04:28:51 +0100
From: Christer Holmberg <>
To: Peter Dunkley <>
Thread-Topic: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt
Thread-Index: AQHPDleQGzr1Sxm0FkKTa2Dy1OUwAJqKNznggAHW2ICAAPS5Pw==
Date: Mon, 20 Jan 2014 03:28:50 +0000
Message-ID: <>
References: <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_t8ggf2ti82dib0706kka9dx11390188532252emailandroidcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyM+Jvje6X6XeCDI7t07RofviLzWLppAWs Fpe3fGa3+Lx/P7PF+e3bmBxYPR71hHo8/jqL1WPnrLvsHkuW/GTy+HL5M1sAaxSXTUpqTmZZ apG+XQJXxs3eJWwF91cwVjRfVWpgXNTP2MXIwSEhYCJx5KJPFyMnkCkmceHeejYQW0jgEKPE yj/cXYxcQPYSRomd33vYQOrZBCwkuv9pg9SICBhJrFiwkhWkhlngGqPEp+vzmUASwgLeEmev /WSDKPKRuLn9ABOE7SRxuPkjK4jNIqAq8ejPaWYQm1fATeL+b5B7QBb3M0mceKEJYnMKBEpM PXoVrIYR6Ljvp9aAzWEWEJe49QRil4SAgMSSPeeZIWxRiZeP/7FC1ORIfF87mQ1ivqDEyZlP WCYwisxC0j4LSdksJGUQcQOJ9+fmM0PY2hLLFr6GsvUlNn45y4gsvoCRfRUje25iZk56ufkm RmDUHdzy22AH46b7YocYpTlYlMR5P7x1DhISSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAGNtU zuf79VGzruvzhRHlPkvu7C5TPy/w+O/8BOEN7pyxs09N0Dxu8vsyi+D/pdv5esRLU5beZtf7 dMzv1X2WWQW6m0NTr2yoPCDQl5D66OGd/3u/zVDYMt9rtqkNi4bS1guRKzdPPDlFvz7oWQv/ i89rKp6LRes3vXy7LKZI3O18ZXpJQEuSrBJLcUaioRZzUXEiAKv2hySIAgAA
Cc: DISPATCH <>, Ben Campbell <>, "" <>
Subject: Re: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 20 Jan 2014 03:28:59 -0000


I see no reason why it should be a separate document, as it should not have any affect on the websocket specific procedures, which is the main scope of the document.



Sent from my Sony Ericsson Xperia arc S

Peter Dunkley <> wrote:


Perhaps the document title should be corrected. MSRP-CEMA is outside of the scope of this document as this document is intended to describe connecting to a WebSocket server that is an MSRP relay.

I can see no reason why MSRP-CEMA can't be used over WebSockets, but if anyone has an interest in this I think that they should put it in a document of its own.



On 18 January 2014 08:52, Christer Holmberg <<>> wrote:

I have not followed the work on this draft, so I appologize if the following has been discussed.

While I do understand that a WS Client has to establish the WebSocket with the Web Server, I don’t understand why we need to mandate the WS Server to be an MSRP Relay. That would e.g. prevent the usage of MSRP-CEMA.



Lähettäjä: dispatch [<>] Puolesta Mary Barnes
Lähetetty: 11. tammikuuta 2014 0:59
Vastaanottaja: DISPATCH
Kopio: Ben Campbell;<>
Aihe: Re: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt

I have agreed to shepherd this document.  I've reviewed the document in anticipation of doing the PROTO write-up and have the following comments and questions.  Ben Campbell has agreed to do the required expert review and that should be posted within the next week or so.    This is also a good time for anyone in the WG that hasn't previously reviewed this document to review and provide any final comments.  Note, that this document was agreed to be AD sponsored around the IETF-86 timeframe.


Review Summary: Almost ready. Comments & questions below.

1)  Section 2 & General.  I'm not sure the documented approach for separating normative text from non-normative is quite so helpful.  In general, we expect that in the case of standards track document use RFC 2119 language to indicate normative behaviors.  I think the first sentence is good, but that's not a terminology thing.   I just don't see a lot of value in writing the document this way.  For example, the definitions aren't stated to be non-normative, but I don't see anything normative about the definitions.  I think you could easily title Section 3 as "WebSocket Protocol overview" and that would clearly imply non-normative behavior.  There are also several places in the document in sections that I believe are intended to provide normative behavior, but there is certainly non-normative text in those sections (e.g., section 5.2.2, second paragraph).  I would suggest this document follow the typical (and accepted) style of identifying normative behavior with 2119 language (consistently using upper case for normative behavior and avoiding using 2119 language in cases where alternative words can be substituted).

2) Section 5.2.2, 2nd paragraph.  Related to my point above, it's not clear to me this is normative behavior.  I don't think it is since it's referring to existing 4975 behavior. However, I didn't see that the reference given in 4975 relates to the second part of that sentence stating that implementations "should" already be allowing unrecognized transports.  It would be quite useful to have the exact reference here as I was trying to double check this point and I couldn't find it.

3) Section 6.  I'm really puzzled as to why the Connection Keep-alive would be non-normative.  In particular given that 2119 language is clearly being used.

4) Section 7.  Again, I'm puzzled as to why Authentication is considered non-normative. AGain, you have 2119 language in this section.

5) Section 10.1. Since securing the connection is just RECOMMENDED, what are the implications and risks if the MSRP traffic isn't transported over a secure connection?

6) Section 11.  You should change the name of the registry to be the exact name of the IANA registry to avoid any confusion.- i.e.,:
  registry of WebSocket sub-protocols
  WebSocket Subprotocol Name Registry

7) Section 11. There is also a Reference field in that IANA registry. I would suggest you use the same information as the pointer to the Subprotocol Definition (i.e., this RFC).

8) It's typical for documents that are updating existing RFCs to have a section that summarizes the updates to the existing RFCs that are made by this document.

On Thu, Dec 12, 2013 at 6:57 PM, <<>> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.

        Title           : The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
        Author(s)       : Peter Dunkley
                          Gavin Llewellyn
                          Victor Pascual
                          Anton Roman
                          Gonzalo Salgueiro
        Filename        : draft-pd-dispatch-msrp-websocket-03.txt
        Pages           : 21
        Date            : 2013-12-12

   The WebSocket protocol enables two-way real-time communication
   between clients and servers.  This document specifies a new WebSocket
   sub-protocol as a reliable transport mechanism between MSRP (Message
   Session Relay Protocol) clients and relays to enable usage of MSRP in
   new scenarios.  This document normatively updates RFC 4975 and RFC

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at<>.

Internet-Drafts are also available by anonymous FTP at:

I-D-Announce mailing list<>
Internet-Draft<> directories:

Peter Dunkley
Technical Director
Crocodile RCS Ltd