Re: [sipcore] RFC5626 and REGISTER with multiple contacts

Iñaki Baz Castillo <ibc@aliax.net> Thu, 03 May 2012 14: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 984B321F848A for <sipcore@ietfa.amsl.com>; Thu, 3 May 2012 07:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.63
X-Spam-Level:
X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[AWL=0.047, 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 dc1RCgWjo2bP for <sipcore@ietfa.amsl.com>; Thu, 3 May 2012 07:52:22 -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 B46E521F85CF for <sipcore@ietf.org>; Thu, 3 May 2012 07:52:21 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1595745vbb.31 for <sipcore@ietf.org>; Thu, 03 May 2012 07:52:21 -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=Sa+rIiKWxx7oQrzL0uxOY+ziyTSxxq9ncb8WR4ry8JE=; b=eJR/yPCzqI0Skx9PFZJ2pxbjXUt7tJFD3hzeuIA0rS3+mRBtjcNdtriCXd62G1J4oi Fnw5V8OFq3+ymxi534TURy3t2/iCEGuwO7+VGTUxF+SkA+pfYTA+AMI9mAAb2i9mNSPE Lhwf04AXK6HjUq2Dtp4bk3WAZP+L+ixHPS8oqeIR3qk9VETPmbSsyE6cg074sLU0ExZz U95kujsI6TBgoucp5hmYPeknfvbVXoYIR4yd0GeNFFXql6zfj54Du6H/y+tizZKac2Xg tn/jfYZYt/s9NcCtDh9sxxjqpC9+fjcOuKB8WSKijC6KwRtBOSRJw+RboYSJM+rFZtja OCdg==
Received: by 10.220.115.130 with SMTP id i2mr1442528vcq.72.1336056741236; Thu, 03 May 2012 07:52:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.107.199 with HTTP; Thu, 3 May 2012 07:52:01 -0700 (PDT)
In-Reply-To: <3A324A65CCACC64289667DFAC0B88E12197E3BBA2F@ESESSCMS0360.eemea.ericsson.se>
References: <3A324A65CCACC64289667DFAC0B88E12197E3BB890@ESESSCMS0360.eemea.ericsson.se> <CALiegfnep=ZKXPpYphZ5ZKPPRUC5AWP6miV76WXHrMa3Qokr8Q@mail.gmail.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBA2F@ESESSCMS0360.eemea.ericsson.se>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 03 May 2012 16:52:01 +0200
Message-ID: <CALiegfmnmYEdUmotcxje+sBsBQF1A2yLC4+9ubBJUuhSQXLsYQ@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: ALoCoQlRsTol20GkP+5yAv+7qaE54xgDQZZv5BvkkfEj6MnTahg/Wd8ph9v912IpiHTppmiWe5WQ
Cc: "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: Thu, 03 May 2012 14:52:22 -0000

2012/5/3 Ivo Sedlacek <ivo.sedlacek@ericsson.com>:
>> This is, if your device registers various bindings for the AoR in the REGISTER's
>> To header, when that AoR is called your device would receive the request with parallel
>> forking for each binding. What is the purpose of that?
>
> Applications have different capabilities, indicated in the associated contacts using the mechanism in RFC 3840.
> The registrar then uses the mechanism in RFC 3841 to choose the correct contact.

Thanks. Then I agree that limiting the number of Contact instances in
the REGISTER is an artificial limitation (in case all of them include
the same instance and reg-id parameters).

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