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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Thu, 13 February 2014 16:07 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
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 05E6C1A0327 for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 08:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 K0ovdMIBwCZ6 for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 08:07:27 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id DD4541A030E for <dispatch@ietf.org>; Thu, 13 Feb 2014 08:07:26 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id vb8so12540450obc.32 for <dispatch@ietf.org>; Thu, 13 Feb 2014 08:07:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rDg9seb6KRarESb+61vwuPJBDMqTZr884PMQWdgGpuY=; b=CfogtcRJKqaeiBuU3gPp6ZgE1dW+6VdSdvmdNpod9VmhMkNHlXGumTJ6+zRQB8MFYl pPqlXIN8197lXemcSiBKIihbwAu+FUUHxcBi9mg3nJZL4yaHrMjFOr/yOjG+z/PdDQJd I5tDbAqlWXmDbzNN+u2UdIgVWF0vxnoXxgZRZ2xRaucvqxiqM0RkZXeTlB489hqyIVe9 If0F84kEh67eQ5QTRvqPkXyA737mC6gqu5W+CxA3y1haAy3oXYnZe39XS5PkVinR7BgZ p6lzJA8WMo5TesMEgykaiikBTmo2gaXSaodu8h6DqSLRu8v5tF43zdFNp6cE5dDJiJBY DrTA==
MIME-Version: 1.0
X-Received: by 10.60.246.139 with SMTP id xw11mr1942616oec.36.1392307645573; Thu, 13 Feb 2014 08:07:25 -0800 (PST)
Received: by 10.182.12.99 with HTTP; Thu, 13 Feb 2014 08:07:25 -0800 (PST)
Received: by 10.182.12.99 with HTTP; Thu, 13 Feb 2014 08:07:25 -0800 (PST)
In-Reply-To: <CAHBDyN7hySvbiJYnvRXDQ2ZS_FYFDMaODXBDRarE6DhRwC=fHQ@mail.gmail.com>
References: <20131213005747.777.34301.idtracker@ietfa.amsl.com> <CAHBDyN4tSRO_nYy7_-V4xfmDbF0ZeLJ24_fEOQ1p9Z2BvJyinQ@mail.gmail.com> <97B47463-42D2-4BA9-AC2F-DF8C67702DDC@cisco.com> <52FCE70C.1030608@gmail.com> <CAHBDyN7hySvbiJYnvRXDQ2ZS_FYFDMaODXBDRarE6DhRwC=fHQ@mail.gmail.com>
Date: Thu, 13 Feb 2014 17:07:25 +0100
Message-ID: <CA+ag07bPBHzODTWGKFrKE00nO_wiMgRv2GEwUpGCiH25-Xf2Cw@mail.gmail.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: multipart/alternative; boundary=001a113696c0a1f0d104f24be20b
Cc: DISPATCH <dispatch@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: Thu, 13 Feb 2014 16:07:30 -0000

What I mean is that I expect quite a lot of "over websocekts" drafts and we
should try to use the same solution for advertising it in the SDP, and not
have each one have their own way of handling it.

Best regards
Sergio
El 13/02/2014 16:49, "Mary Barnes" <mary.ietf.barnes@gmail.com> escribió:

> Sergio,
>
> The draft you mention is being discussed in the BFCPBIS WG and any
> comments that others might have on that document should go to that list.
>
> It's not clear to me whether your suggestion is that changes are needed to
> this MSRP document or whether you are just proposing to make the BFCPBIS
> consistent with this MSRP document?
>
> Mary.
>
>
> On Thu, Feb 13, 2014 at 9:38 AM, Sergio Garcia Murillo <
> sergio.garcia.murillo@gmail.com> wrote:
>
>> Hi,
>>
>> We also have recently published a different draft for BFCP over
>> websockets:
>> http://tools.ietf.org/html/draft-pascual-bfcpbis-bfcp-websocket-00
>>
>> I beleive that we should harmonize who the WS transport is signaled and
>> how to signal the WS version if also the "normal" TCP version is supported.
>>
>> In your case you seem to be using the same transport line TCP/MSRP and
>> use the path to signal the ws part, in our case, we choose to signal it in
>> the transport TCP/WS/BFCP and include a new attribute ws-uri to signal the
>> full url (I could not reuse the path attribute as it is restricted to msrp
>> urls only).
>>
>> Best regards
>> Sergio
>> El 13/02/2014 16:17, Gonzalo Salgueiro (gsalguei) escribió:
>>
>>> Hi Mary -
>>>
>>> Thanks for taking the time to review the document.  We have published an
>>> -05 that (hopefully) addresses all your feedback.
>>>
>>> Inline, trimming to only the points requiring responses...
>>>
>>>
>>> On Jan 10, 2014, at 5:58 PM, Mary Barnes <mary.ietf.barnes@gmail.com>
>>> wrote:
>>>
>>>  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.
>>>>
>>> <snip/>
>>>
>>>  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?
>>>>
>>> Other review comments indicated that it was problematic to downgrade the
>>> 4976 MUST requirement for TLS between a client and a server. Thus, the
>>> document has been updated so that MSRP traffic transported over WebSockets
>>> MUST be protected by using a secure WebSocket connection (i.e., using TLS).
>>>  I believe this renders this point moot.
>>>
>>> <snip/>
>>>
>>>  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.
>>>>
>>> This was the intent of Sections 5.2 and 5.3.  Is this sufficient? Or did
>>> you have something else in mind?
>>>
>>> Regards,
>>>
>>> Gonzalo
>>>
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>>
>
>