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 09:51 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 684F221F8B1F for <sipcore@ietfa.amsl.com>; Mon, 5 Dec 2011 01:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level:
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.200, 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 DdwzuOaOWEjH for <sipcore@ietfa.amsl.com>; Mon, 5 Dec 2011 01:51:41 -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 B33A421F8B1D for <sipcore@ietf.org>; Mon, 5 Dec 2011 01:51:41 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so1291126vbb.31 for <sipcore@ietf.org>; Mon, 05 Dec 2011 01:51:41 -0800 (PST)
Received: by 10.52.33.239 with SMTP id u15mr4136385vdi.49.1323078701196; Mon, 05 Dec 2011 01:51:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.203.8 with HTTP; Mon, 5 Dec 2011 01:51:19 -0800 (PST)
In-Reply-To: <CA+cEqjctnA4_0Oef-juusN3=LUiao414DYUJhO6od+JYkutkJg@mail.gmail.com>
References: <CALiegfm8Dv8kHE1xrt59vBzLzB29mOvjH6YR2m=vm=p_BtSBTw@mail.gmail.com> <CAGTXFp82jNsCUBM=j=Tq1Xc5cOr7P1Hbp9gv5MQyeVBoOS5=ng@mail.gmail.com> <5470070492D34F4EAC60E4ED91CB3841@gsmlaptop> <CALiegfmdxJQ+fAevUCfOaJjRkja-vW2Sqh-83-J=3_E5Ba1j6A@mail.gmail.com> <CA+cEqjc+2JR8S5i=kcpSz96KC_Mtd9OThafcGgeeAXaFEzZoWQ@mail.gmail.com> <CALiegfnCym7NdEs=TH=UtYjsK6jgqkVfHaeyHo1VU1QMTb-VyA@mail.gmail.com> <CA+cEqjctnA4_0Oef-juusN3=LUiao414DYUJhO6od+JYkutkJg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Dec 2011 10:51:19 +0100
Message-ID: <CALiegf=3HF3TdKof+Pghqzmzs192sDXRvO_GzU7TDODAT+bVwg@mail.gmail.com>
To: Gilad Shaham <gilad@voxisoft.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: José Luis Millán <jmillan@aliax.net>, "SIPCORE (Session Initiation Protocol Core) WG" <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 09:51:42 -0000

2011/12/5 Gilad Shaham <gilad@voxisoft.com>:
>> Yes, using localhost would be another option, but it has a drawback in
>> case the WebSocket SIP UA does not use GRUU: in that case a remote
>> peer would see "localhost" as the target of of WS UA. If it sends a
>> REFER to a third participant containing "Refer-To:
>> <sip:alice@localhost;transport=ws>" then the third participant would
>> try to open a WS connection to itself. Well, as the draft states, GRUU
>> is required for SIP UA's using WebSocket transport, at least in web
>> browsers.
>>
>> So I'm not sure wheter using "localhost" is better than using
>> "anonymous.invalid". Maybe it is better to use "invalid.domain"?
>>
> So, if we were to have normative text that defines this, it would probably
> explain why localhost or any routable domain name is a bad choice as opposed
> to a non-routable domain. Should a UA be free to choose based on a set of
> rules or are we defining one host part for all? Should it generate parts or
> all of this domain dynamically to assist with matching incoming requests? Is
> one free to use an invalid IP (such as the infamous 0.0.0.0)?

Take into account that when a JavaScript code (running in a web
browser) open a WebSocket connection given a WS URI with domain, the
JavaScript code is not aware of the resulting IP nor the IP family
(IPv4 or IPv6). So IMHO using a IP address in Via/Contact is a bad
idea.

Assuming that a domain is used, I think that which one to set should
not be normative, for the following reasons:

1) If Outbound is being used (and it's a MUST for these kind of SIP
endpoints) the host in Via and Contact does not matter (for
registration or dialogs).

2) If GRUU is used, the host in Contact would be a globally routable
URI. If GRUU is not used, then there is no way  at all for SIP REFER
mechanism to work (since a SIP WebSocket client can only be contacted
via the WS connection it has opened with the WS server). So the domain
in Contact does not matter (with GRUU it will always work, without
GRUU it will never work).


> And most importantly, do others believe this requires normative text or not?

I consider that this should be an informative text, maybe by
suggesting the usage of "invalid.domain" or "any non routable domain".


Regards.

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