Re: [sipcore] RFC5626 and REGISTER with multiple contacts

Ivo Sedlacek <ivo.sedlacek@ericsson.com> Fri, 04 May 2012 11:10 UTC

Return-Path: <ivo.sedlacek@ericsson.com>
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 29A0221F8717 for <sipcore@ietfa.amsl.com>; Fri, 4 May 2012 04:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.274
X-Spam-Level:
X-Spam-Status: No, score=-5.274 tagged_above=-999 required=5 tests=[AWL=-0.525, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_24=0.6, J_CHICKENPOX_38=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 zKRQQ3xCVPnr for <sipcore@ietfa.amsl.com>; Fri, 4 May 2012 04:10:04 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id CE6B121F86C3 for <sipcore@ietf.org>; Fri, 4 May 2012 04:09:52 -0700 (PDT)
X-AuditID: c1b4fb25-b7b18ae000000dce-2a-4fa3b8ffeacb
Authentication-Results: mailgw2.ericsson.se x-tls.subject="/CN=esessmw0256"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0256", Issuer "esessmw0256" (not verified)) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id E0.7F.03534.FF8B3AF4; Fri, 4 May 2012 13:09:51 +0200 (CEST)
Received: from ESESSCMS0360.eemea.ericsson.se ([169.254.1.5]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Fri, 4 May 2012 13:09:51 +0200
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 04 May 2012 13:09:50 +0200
Thread-Topic: [sipcore] RFC5626 and REGISTER with multiple contacts
Thread-Index: Ac0p04s9XALT8QJeTa2+nFtEQzvS/AAEQtNA
Message-ID: <3A324A65CCACC64289667DFAC0B88E12197E3BBDF5@ESESSCMS0360.eemea.ericsson.se>
References: <3A324A65CCACC64289667DFAC0B88E12197E3BB890@ESESSCMS0360.eemea.ericsson.se> <CD5674C3CD99574EBA7432465FC13C1B22726A0AA4@DC-US1MBEX4.global.avaya.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBBC8@ESESSCMS0360.eemea.ericsson.se> <CALiegfmdb5PHiXk0fiveHAiM6zwUTB8Fi5gPhM-WgzYT_J2uUg@mail.gmail.com>
In-Reply-To: <CALiegfmdb5PHiXk0fiveHAiM6zwUTB8Fi5gPhM-WgzYT_J2uUg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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 11:10:05 -0000

Hello,

please see below

Kind regards

Ivo Sedlacek 

Ericsson
GF Technology, Terminal Standardization
Sweden
Office: +46 10 711 9382
ivo.sedlacek@ericsson.com
www.ericsson.com

This communication is confidential. We only send and receive email on the basis of the term set out at www.ericsson.com/email_disclaimer


-----Original Message-----
> From: Iñaki Baz Castillo [mailto:ibc@aliax.net] 
> Sent: 4. května 2012 10:54 
> To: Ivo Sedlacek 
> Cc: Worley, Dale R (Dale); sipcore@ietf.org 
> Subject: Re: [sipcore] RFC5626 and REGISTER with multiple contacts 
> 
> 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? 

That seems OK - at least we see no need to support cases where all contacts in a REGISTER request don't share the same sip.instance and the same reg-id (and the same IP address and port). 

> 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). 

Exactly, and that is the reason we assume identical IP address and port, because incoming requests are going to be sent to the same IP location no matter which contact is used.


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