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

Peter Dunkley <peter.dunkley@crocodilertc.net> Sun, 19 January 2014 13:53 UTC

Return-Path: <peter.dunkley@crocodilertc.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40761ACCEB for <dispatch@ietfa.amsl.com>; Sun, 19 Jan 2014 05:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 XbFYmcalVOF6 for <dispatch@ietfa.amsl.com>; Sun, 19 Jan 2014 05:53:11 -0800 (PST)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 761BC1AC421 for <dispatch@ietf.org>; Sun, 19 Jan 2014 05:53:11 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id tq11so5483696ieb.28 for <dispatch@ietf.org>; Sun, 19 Jan 2014 05:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crocodilertc.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BWL11cdD/JDijz9Xi7t7jJFcmjXPbxz+IDhoe3bXRRE=; b=gqmyjCTp+m+MEFlXCtll2koFSJY03tBP1jQCJTOgLelx0TM98sso1v7JBg+Prg4Htz LqZhsKJmPGfx4O635IdHCgoFWLjSgyuLZnLEI9NHlwK11o7GOTUxiFioBcmnRp0ZIcm9 GRwJejqkP99HbKJGsGtudiGvo6u5tDk/0Qrkg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=BWL11cdD/JDijz9Xi7t7jJFcmjXPbxz+IDhoe3bXRRE=; b=ERKxMWWdGVzcbtVuXA2EgrY7XbBWnZagtNXBHDRxnNem5y8Xh0nF5UedvAOX6kASCw JiWNKJxZVMEYhV43GCQrksCc6gZ+Ga3jd30kbypOx/gbB+E6wzp5hxsrxwLVMCP4E4P5 YeV2JNlgsLlVpUptrS1JHupFKeNbjfNywZUSdtfdjB0XKDXTQpgfnXzjFxK53bcjn9bS 9bji2DH3Hv9KZakEVQx9aMgYcN6wGGstP/LtPKoFNP6LiWgR+BAglWHa28O/lxtfS3xf 4Yfgq9W5MvfPausgMaafE3uxw+At3M0LyiOSM7pWv7er5mk54Mb8MFGMcXqp/1RFv+Vl 4fFw==
X-Gm-Message-State: ALoCoQlU+qC94in/+JniD68jnf74t1jmwm1j2IUcih9K1EPPnNS5GqQmmNSo2NA9Yb6XOQKhvXuW
MIME-Version: 1.0
X-Received: by 10.50.50.70 with SMTP id a6mr7726893igo.1.1390139578055; Sun, 19 Jan 2014 05:52:58 -0800 (PST)
Received: by 10.64.229.13 with HTTP; Sun, 19 Jan 2014 05:52:57 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D104D91@ESESSMB209.ericsson.se>
References: <20131213005747.777.34301.idtracker@ietfa.amsl.com> <CAHBDyN4tSRO_nYy7_-V4xfmDbF0ZeLJ24_fEOQ1p9Z2BvJyinQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D104D91@ESESSMB209.ericsson.se>
Date: Sun, 19 Jan 2014 13:52:57 +0000
Message-ID: <CAEqTk6QcSU+u2nrp3oyoyr6p4diGD2s4-4PhBQW-UP2VdZmsqw@mail.gmail.com>
From: Peter Dunkley <peter.dunkley@crocodilertc.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=089e010d9d40bd187304f053175b
Cc: DISPATCH <dispatch@ietf.org>, Ben Campbell <ben@estacado.net>, "draft-pd-dispatch-msrp-websocket@tools.ietf.org" <draft-pd-dispatch-msrp-websocket@tools.ietf.org>
Subject: Re: [dispatch] I-D Action: draft-pd-dispatch-msrp-websocket-03.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jan 2014 13:53:14 -0000

Hello,

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.


Regards,

Peter


On 18 January 2014 08:52, Christer Holmberg
<christer.holmberg@ericsson.com>wrote;wrote:

>  Hi,
>
>
>
> 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.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
>
> *Lähettäjä:* dispatch [mailto:dispatch-bounces@ietf.org] *Puolesta *Mary
> Barnes
> *Lähetetty:* 11. tammikuuta 2014 0:59
> *Vastaanottaja:* DISPATCH
> *Kopio:* Ben Campbell; draft-pd-dispatch-msrp-websocket@tools.ietf.org
> *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.
>
>
>
> Regards,
>
> Mary.
>
>
>
> 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.,:
>
> OLD:
>
>   registry of WebSocket sub-protocols
>
> NEW:
>
>   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, <internet-drafts@ietf.org> 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
>
> Abstract:
>    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
>    4976.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-pd-dispatch-msrp-websocket
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-pd-dispatch-msrp-websocket-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-pd-dispatch-msrp-websocket-03
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft<https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>directoriestories:
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>



-- 
Peter Dunkley
Technical Director
Crocodile RCS Ltd