IETF Logo Mail Archive

Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09

Iñaki Baz Castillo <ibc@aliax.net> Mon, 17 June 2013 18: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 2420421F9CFE for <sipcore@ietfa.amsl.com>; Mon, 17 Jun 2013 11:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.728
X-Spam-Level:
X-Spam-Status: No, score=-1.728 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 I9w6MbjfG4Ce for <sipcore@ietfa.amsl.com>; Mon, 17 Jun 2013 11:51:45 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5669C21F9CEA for <sipcore@ietf.org>; Mon, 17 Jun 2013 11:51:44 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id hu16so1660944qab.8 for <sipcore@ietf.org>; Mon, 17 Jun 2013 11:51:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=0xkv7ThPyNY0UYWsFbvgUxTfspllYNH0ABiKPYrDI54=; b=A0yW6GuHOwLB0Ck8VTL12loOSyHyuAy3FOK/78QohYqbkyvPAkJ5Wv3APII8NKG81Y Bq/sFIl7QochOESm89gU0zHHCS77vvd4/VlkLqqPt/xNmEDdJfHmryWfZ7PU4HQVGMeP MZRfBVc3RJBJOh0Hp/gyvOBUenf7fDjonUy8DWPv4WPXk0MydBEYilNATtdiSpwuA6xN aeW5x+iMxdw/Wx/I6Ub6xkaR59nuMhtTQhEZwuzBGK49CIJe9RlJXDjxT6rzEnSD55yp vT63oK3ob0jQN6QIc57JamlWDv9jEiRk2cNjXiAau79XOHqyVkwmCa66r1oSKvktziLD gDrg==
X-Received: by 10.229.124.68 with SMTP id t4mr6780334qcr.93.1371495104213; Mon, 17 Jun 2013 11:51:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Mon, 17 Jun 2013 11:51:23 -0700 (PDT)
In-Reply-To: <003f01ce6aaf$aabda760$0038f620$@co.in>
References: <CALiegfmtohM8Nnf34o2EqMr-jV-LaQBP7mOB5qq+7OcQO9FkSA@mail.gmail.com> <003f01ce6aaf$aabda760$0038f620$@co.in>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 17 Jun 2013 20:51:23 +0200
Message-ID: <CALiegfn=KrEsOT+HGkCpfkS3C7Tc0Jko6kautCHk3sP8zHrzVw@mail.gmail.com>
To: Parthasarathi R <partha@parthasarathi.co.in>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkXQxljtCeqdY6aku1jfePL8NT1IrkrZqU/bD/4ha+jcMPYqXIqzjqW635At3EXvnAAmpki
Cc: "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>
Subject: Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09
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, 17 Jun 2013 18:51:46 -0000

2013/6/16 Parthasarathi R <partha@parthasarathi.co.in>:
> I could not understand how this update resolve the issue in the following scenario:
>
>  SIP UA1 (WS only)----Proxy-----SIP UA2 (UDP/TCP)
>
> Here, the dialog is established with contact details for SIP UA1 & SIP UA2 as follows:
>
> 1) contact: sip:sipua1@example.com;transport=ws
> 2) contact: sip:sipua2@example.com;transport=tcp
>
> In case SIP UA2 wishes to send RE-INVITE towards SIP UA1, how does it possible now as per the current update in Sec 5.2.4 of draft-ietf-sipcore-sip-websocket-09.


Hi Parthasarathi,

  SIP UA1 (SCTP/UDP/TCP)----Proxy-----SIP UA2 (UDP/TCP)

Here, the dialog is established with contact details for SIP UA1 & SIP
UA2 as follows:

1) contact: sip:sipua1@example.com;transport=sctp
2) contact: sip:sipua2@example.com;transport=tcp

In case SIP UA2 wishes to send RE-INVITE towards SIP UA1, please let
me know in which section of RFC 4168 (SIP STCP) it is stated that the
proxy must use Record-Route for the initial INVITE for this scenario
to work.

Regards.


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

v2.23.0 | Report a Bug | By Email