IETF Logo Mail Archive

Re: [sipcore] RFC5626 and REGISTER with multiple contacts

Iñaki Baz Castillo <ibc@aliax.net> Tue, 08 May 2012 11:20 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 8F48E21F848F for <sipcore@ietfa.amsl.com>; Tue, 8 May 2012 04:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.309
X-Spam-Level:
X-Spam-Status: No, score=-2.309 tagged_above=-999 required=5 tests=[AWL=-0.232, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 1OecNS+48yHX for <sipcore@ietfa.amsl.com>; Tue, 8 May 2012 04:20:00 -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 AEDDD21F847E for <sipcore@ietf.org>; Tue, 8 May 2012 04:20:00 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1345352vbb.31 for <sipcore@ietf.org>; Tue, 08 May 2012 04:20:00 -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=Eqv+sqBVK2wJAABhKB6msPRZcL9BfL8cQKk89/cYRPg=; b=St/MQ9RqvOcS06AjPei2LFueQs926x7fbMe9ClqHxWmUSZp8Ztjfs4UfMu3ts0nW8G /kIGoel/uQZ31RMRsTY7OPzf11NCw6YRebzPDBruH+S+LB8V2Z5eXtodk/U6AemPofUW 0YPGpidE61EIfQ/3rE57Wh2bgEzW0oJsA/msYHCu6iSNyOZgYXCl0wWXwLFhTUGm6I6L AW+FtdfVh2i8P+moPJMpBXer5HYds42nGO9pP0ELjbupUBtPIAN709HQF9abuCNfrq8Y 8EGO6XACHWMq2T5NrAMQJElZ9Yb0Ouj4MqiQG3AnyLWMC3gkxpE7RUEkpjzfphh8zKjX TezA==
Received: by 10.52.180.232 with SMTP id dr8mr832945vdc.111.1336476000195; Tue, 08 May 2012 04:20:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.107.199 with HTTP; Tue, 8 May 2012 04:19:39 -0700 (PDT)
In-Reply-To: <3A324A65CCACC64289667DFAC0B88E12197E438E96@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> <3A324A65CCACC64289667DFAC0B88E12197E3BBDF5@ESESSCMS0360.eemea.ericsson.se> <CALiegfk5t5p=sw0MVcrzVshYs2Z3kiw0KYmqzLRGmdcPZj3YfA@mail.gmail.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBEA3@ESESSCMS0360.eemea.ericsson.se> <4FA3EFD8.2080903@digium.com> <3A324A65CCACC64289667DFAC0B88E12197E438967@ESESSCMS0360.eemea.ericsson.se> <4FA7D98E.8090100@alum.mit.edu> <3A324A65CCACC64289667DFAC0B88E12197E438E96@ESESSCMS0360.eemea.ericsson.se>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 08 May 2012 13:19:39 +0200
Message-ID: <CALiegfkjp=V8ZHZRuD7atXN5eqNbrXnO8tVxc9-U8k=637Ok9Q@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: ALoCoQnPyDV6ig7OyuJeGAmo13pNYX9f6lrHH9lyF2NKhKmqZAxH0Jo9XsNj1dbRJCr/tvHwzGUC
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: Tue, 08 May 2012 11:20:01 -0000

2012/5/8 Ivo Sedlacek <ivo.sedlacek@ericsson.com>:
> To Inaki's comment:
>> But user agent capabilities mean *UA* capabilities, and a UA is represented by a single and unique sip.instance.
>
> In some cases it is not even possible to express the UA capabilities by single Contact. E.g.
>
> Contact: <sip:address:port>;+sip.instance="x";+sip.duplex="full";+sip.audio
> Contact: <sip:address:port>;+sip.instance="x";+sip.duplex="receive-only";+sip.audio;+sip.video

IMHO those two Contacts are expressing different capabilities for the
same *UA* (same sip-instance) so they make no sense.

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

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