IETF Logo Mail Archive

Re: [sipcore] New Version Notification for draft-ibc-sipcore-sip-websocket-00 (previously draft-ibc-rtcweb-sip-websocket-00)

Iñaki Baz Castillo <ibc@aliax.net> Mon, 05 December 2011 08:37 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6738D21F8A91 for <sipcore@ietfa.amsl.com>; Mon, 5 Dec 2011 00:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level:
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZsJnKK27Qf3I for <sipcore@ietfa.amsl.com>; Mon, 5 Dec 2011 00:37:57 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id CB5D921F8A71 for <sipcore@ietf.org>; Mon, 5 Dec 2011 00:37:56 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so1245285vbb.31 for <sipcore@ietf.org>; Mon, 05 Dec 2011 00:37:56 -0800 (PST)
Received: by 10.52.117.65 with SMTP id kc1mr4026868vdb.66.1323074276334; Mon, 05 Dec 2011 00:37:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.203.8 with HTTP; Mon, 5 Dec 2011 00:37:36 -0800 (PST)
In-Reply-To: <4EDA7DDE.1030005@alum.mit.edu>
References: <CALiegfm8Dv8kHE1xrt59vBzLzB29mOvjH6YR2m=vm=p_BtSBTw@mail.gmail.com> <4EDA7DDE.1030005@alum.mit.edu>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Dec 2011 09:37:36 +0100
Message-ID: <CALiegfkch5m-P3OzCMm_6r0nyWUpjcsKR6D_q5C2Pbq=Fhn0rw@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: sipcore@ietf.org
Subject: Re: [sipcore] New Version Notification for draft-ibc-sipcore-sip-websocket-00 (previously draft-ibc-rtcweb-sip-websocket-00)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 08:37:57 -0000

2011/12/3 Paul Kyzivat <pkyzivat@alum.mit.edu>:
> Section 7:
>
> Since you are mostly trying to avoid interactions with sips, why is it that
> you use SIPS+D2W to resolve wss URIs? That seems to imply some relationship
> to sips that is not intended.

Well, we didn't try to discourage the interaction with SIPS, we just
tryed to avoid too much text about SIPS since, IMHO, it adds some
complexity which is not very clear currently.

But as said in other mail, we will add a text under the "Security"
section describing the requirement of using secure WebSocket transport
("wss" schema in the WS URI) when SIPS is used.

Regards.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email