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

Christer Holmberg <> Tue, 21 January 2014 09:43 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 61C6B1A0087 for <>; Tue, 21 Jan 2014 01:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 IAMgu8ewW-lP for <>; Tue, 21 Jan 2014 01:43:19 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 9016A1A00A2 for <>; Tue, 21 Jan 2014 01:43:18 -0800 (PST)
X-AuditID: c1b4fb30-b7faa8e000007034-00-52de4135ea2e
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 22.1D.28724.5314ED25; Tue, 21 Jan 2014 10:43:17 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Tue, 21 Jan 2014 10:43:14 +0100
From: Christer Holmberg <>
To: Victor Pascual <>
Thread-Topic: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt
Thread-Index: AQHPDleQGzr1Sxm0FkKTa2Dy1OUwAJqKNznggAHW2ICAAPS5P4AAWE2AgAAStzCAAX6poP///cyAgAATWxA=
Date: Tue, 21 Jan 2014 09:43:14 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: fi-FI
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D11142FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZGfG3RtfU8V6Qwe9XihbND3+xWSydtIDV 4vKWz+wW57dvY7LYue4wqwOrx6OeUI/HX2exeixZ8pPJ40TvCyaPL5c/swWwRnHZpKTmZJal FunbJXBlnF3az1bQd5epYtPpXUwNjJe2MnUxcnJICJhI3HhxlBXCFpO4cG89WxcjF4eQwCFG ifOPG5ghnCWMEjeungZyODjYBCwkuv9pgzSICOhJtM99C9bALHCHUeLiuQOMIAlhAW+JKcvf MkMU+Ujc3H6ACcJOkjh+cikbiM0ioCrR8XAJWJxXwFfiQdNTqGVPWCQ+vFoFVsQpECjxZu06 dhCbEei876fWgDUwC4hLfDh4nRnibAGJJXvOQ9miEi8f/4N6R0li0e3PUPX5Eu8m7YFaJihx cuYTlgmMorOQjJqFpGwWkjKIuJ7EjalT2CBsbYllC19D1etKzPh3iAVZfAEj+ypG9tzEzJz0 cvNNjMCoPLjlt8EOxk33xQ4xSnOwKInzfnjrHCQkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qB sXFl+yHmV+s/N094Y8SxouPenKpS5o0nlydK2hhJXn/NrC98Jr9zUvzWy4GzWm7IbApSkIyK 5Lt2ZqreJI9/9wVufDvAdHuGV4fxh/K5ARrlHzMlXDdr7mk24rsvk5pYvXdl4PvcsLv94iyy FjtKD9g25szgjV0eGvrp5qEWv3vpnGWJt8tOK7EUZyQaajEXFScCAMX97JeYAgAA
Cc: Ben Campbell <>, DISPATCH <>, "" <>
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: Tue, 21 Jan 2014 09:43:24 -0000


>I believe current approach for 3GPP (WebRTC access to IMS) is datachannel transport for both MSRP and BFCP being open to other mechanisms like websocket.




2014/1/21 Christer Holmberg <<>>

I made a false statement earlier, regarding 3GPP.

3GPP does not have requirement to transport MSRP over WebSocket.

Sorry for the confusion.



Lähettäjä: dispatch [<>] Puolesta Christer Holmberg
Lähetetty: 20. tammikuuta 2014 11:55
Vastaanottaja: Peter Dunkley
Kopio: DISPATCH; Ben Campbell;<>

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

Hi Peter,

I am willing to help, and contribute text.

But, I request that we don't move the document forward before I've had a chance to do that :)

(3GPP also has a requirement to specify the usage of MSRP over WebSocket.)



Lähettäjä: Peter Dunkley []
Lähetetty: 20. tammikuuta 2014 11:45
Vastaanottaja: Christer Holmberg
Kopio: Mary Barnes; DISPATCH; Ben Campbell;<>
Aihe: Re: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt

Hi Christer,

There is working code for the document as-is and plans for more implementations. I think that if someone has a need for MSRP-CEMA in this scenario then they should join with the current authors to contribute the text and working code for this.



On 20 January 2014 03:28, Christer Holmberg <<>> wrote:


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

Peter Dunkley
Technical Director
Crocodile RCS Ltd