IETF Logo Mail Archive

Re: [sipcore] RFC5626 and REGISTER with multiple contacts

Iñaki Baz Castillo <ibc@aliax.net> Fri, 04 May 2012 10:52 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 254B721F85FF for <sipcore@ietfa.amsl.com>; Fri, 4 May 2012 03:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.031
X-Spam-Level:
X-Spam-Status: No, score=-2.031 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_24=0.6, J_CHICKENPOX_38=0.6, 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 f2STeQZrTgnz for <sipcore@ietfa.amsl.com>; Fri, 4 May 2012 03:52:41 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB2921F85D3 for <sipcore@ietf.org>; Fri, 4 May 2012 03:52:41 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2306099vbb.31 for <sipcore@ietf.org>; Fri, 04 May 2012 03:52:41 -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=snSTz2iaEJ4YKKxEVzKBkeRtBOMJQWBV0e+FF1cd130=; b=lf9BMxMyrJEnj5rk3f7+AZNKxRbCTDY0Pe4kIqthRON2BF/t1YDQFS6LPBs/u14m6i ccsV46dV7+bXs6cGZRgvsXTOa4yWPBThXjua0TwEi5FUfA4hdYMFacacfR5XnWVLrJmG 1OS/y/+UJM/23R8aetNG0rouxz96D1Q2TpeNz0kdV5kLziL4CVkSLVyvVvrrHTvQm9OP RyufwGWnoY7TbsxPJOju3iO3X7HBKjqLqH2UanWejE6KZWeA8TiZdWY9CMh0FqqnDqin CaK5HG9ez4C7ODr+hGchHtNvYXGVuXrcZnQXEIwoHHtVCHvVBsLp1C/mrArzJSHHAQ8c KSLg==
Received: by 10.52.174.199 with SMTP id bu7mr1751786vdc.39.1336121679668; Fri, 04 May 2012 01:54:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.107.199 with HTTP; Fri, 4 May 2012 01:54:19 -0700 (PDT)
In-Reply-To: <3A324A65CCACC64289667DFAC0B88E12197E3BBBC8@ESESSCMS0360.eemea.ericsson.se>
References: <3A324A65CCACC64289667DFAC0B88E12197E3BB890@ESESSCMS0360.eemea.ericsson.se> <CD5674C3CD99574EBA7432465FC13C1B22726A0AA4@DC-US1MBEX4.global.avaya.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBBC8@ESESSCMS0360.eemea.ericsson.se>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 04 May 2012 10:54:19 +0200
Message-ID: <CALiegfmdb5PHiXk0fiveHAiM6zwUTB8Fi5gPhM-WgzYT_J2uUg@mail.gmail.com>
To: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlerzhQwvWU52b4u7ZTOHwiAinL7SEbFoFgMmUpYILv2ayvEJuCdqXYxnvYGu3e6GE+vHnu
Cc: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] RFC5626 and REGISTER with multiple contacts
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: Fri, 04 May 2012 10:52:42 -0000

2012/5/4 Ivo Sedlacek <ivo.sedlacek@ericsson.com>:
> Based on the feedback received so far, there doesn't seem to be a technical reason why multiple contacts (sharing the same IP address and port, the same sip.instance and the same reg-id) in a single REGISTER would not work with outbound.

I agree, however take into account that if two contacts don't share
the same sip.instance and reg-id (or one of the contacts does not
include those parameters) then the registrar should reject the
request, right? If so, maybe RFC 5626 tries to simplify it by avoiding
such tedious parameters comparison in server side.

Also take into account that the contact IP:port is just "ignored" when
using Outbound (the registrar just matches the contact using the
sip.instance and reg-id params).



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

v2.27.6 | Report a Bug | By Email | System Status