IETF Logo Mail Archive

Re: [sipcore] Outbound clarification

Iñaki Baz Castillo <ibc@aliax.net> Wed, 03 July 2013 00:27 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 C166321F99CF for <sipcore@ietfa.amsl.com>; Tue, 2 Jul 2013 17:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level:
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=0.050, 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 QYXequEmOxBi for <sipcore@ietfa.amsl.com>; Tue, 2 Jul 2013 17:27:15 -0700 (PDT)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id F2C9621F99CD for <sipcore@ietf.org>; Tue, 2 Jul 2013 17:27:14 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id i13so3247816qae.6 for <sipcore@ietf.org>; Tue, 02 Jul 2013 17:27:13 -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=oq72nNQkxGfI65D5CFg2a9DlZ2bwxSIM6ifmdI7O9dg=; b=VXHwZduVrOQv9boLVRIyWPg9sSvnma/LU0npSBqf9I7brc2lSMIVEWfpXT+dcNkGb5 64+qSVnyjMC0ckxis+L7L2f4BHchgl80rdMTfjjFpsuNkMQP+ZfKU6RU0E8vFIUlzVVD NShxFtyI2Z/XDCDMlsDQFWx5kz5NzQ6a40jrv6bBfqVpdvQritZ8SByfzpsawmsM2F6w gGuDcyiIPrrPbqoJvRU8CVoXmd9ioF8hbQbEC7AUJCSea6om0NMgeWfcUL3j0bddTFjO ZVM7aPD7MxxbVZeTI1UZjwn9l87CIb2KArt9IAx2x0uS1LmuNOE5riCKeiZtVRl0bKKw lv0w==
X-Received: by 10.49.84.164 with SMTP id a4mr8646199qez.4.1372811233087; Tue, 02 Jul 2013 17:27:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Tue, 2 Jul 2013 17:26:53 -0700 (PDT)
In-Reply-To: <201306282034.r5SKYs1E115839@shell01.TheWorld.com>
References: <CABw3bnO9GDT-CyRrfQVN-F9GyhJZBX_ccj1zZ74vVt13noODCg@mail.gmail.com> <CABw3bnP3N=vMa-Jw1V8OaOC4ZU3v462PRjMz26DXTpM_Cd0Lfw@mail.gmail.com> <201306282034.r5SKYs1E115839@shell01.TheWorld.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 03 Jul 2013 02:26:53 +0200
Message-ID: <CALiegfmhiuKUV=m5r6ngngmYT4OeE-H0ikSVd2x30a=c2MdBeA@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlrboXCwvtkD+rXag0DbTPb/ZvgDGMtAoz62WdxNo/oDYiShYZGrsSgV7AP5fBKjQXXOh8X
Cc: "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>, Jose Luis Millan <jmillan@aliax.net>
Subject: Re: [sipcore] Outbound clarification
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: Wed, 03 Jul 2013 00:27:24 -0000

2013/6/28 Dale R. Worley <worley@ariadne.com>:
> Yes, I believe that is what it means.  Every GRUU refers to an
> underlying Contact address, which is where requests to that GRUU will
> be routed to.  That Contact address is what was used in the REGISTER
> request to obtain the GRUU.  The question seems to be, "Does this GRUU
> refer to a Contact address that includes an "ob" parameter?"

The problem is:

alice ---- Proxy+Registrar ---- bob

- alice has a GRUU registration.
- alice calls bob with ;gr in Contact.
- Let's suppose P+R adds Outbound flow token in R-R.
- Call is established.
- Later bob sends BYE.
- Such a BYE arrives to P+R with a Route header containg an outbound
flow token and with a RURI containing ;gr.

How should P+R route the BYE? by using Outbound (looking for the
connection associated to the flow token in the Route header)? or by
performing GRUU (replacing the RURI with the real Contact? In the
former, if the TCP connection of alice was re-established during the
dialog, the BYE could not be sent.



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

v2.23.0 | Report a Bug | By Email