IETF Logo Mail Archive

Re: [sipcore] RFC5626 and REGISTER with multiple contacts

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 08 May 2012 13:44 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 8D2EC21F84DF for <sipcore@ietfa.amsl.com>; Tue, 8 May 2012 06:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level:
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599]
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 df+xLnoNhR2M for <sipcore@ietfa.amsl.com>; Tue, 8 May 2012 06:44:21 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by ietfa.amsl.com (Postfix) with ESMTP id 7791821F84DD for <sipcore@ietf.org>; Tue, 8 May 2012 06:44:21 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta01.westchester.pa.mail.comcast.net with comcast id 7Ny51j0061wpRvQ51RkKsz; Tue, 08 May 2012 13:44:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta18.westchester.pa.mail.comcast.net with comcast id 7RkJ1j01C07duvL3eRkJze; Tue, 08 May 2012 13:44:18 +0000
Message-ID: <4FA92331.5010001@alum.mit.edu>
Date: Tue, 08 May 2012 09:44:17 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
References: <3A324A65CCACC64289667DFAC0B88E12197E3BB890@ESESSCMS0360.eemea.ericsson.se> <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> <CALiegfkjp=V8ZHZRuD7atXN5eqNbrXnO8tVxc9-U8k=637Ok9Q@mail.gmail.com> <3A324A65CCACC64289667DFAC0B88E12197E438EF2@ESESSCMS0360.eemea.ericsson.se> <CALiegfkBge3QWUVdk01bAOtqLA9UGN2meoR4Aoc_LJjfUGyMvg@mail.gmail.com> <3A324A65CCACC64289667DFAC0B88E12197E438F2D@ESESSCMS0360.eemea.ericsson.se>
In-Reply-To: <3A324A65CCACC64289667DFAC0B88E12197E438F2D@ESESSCMS0360.eemea.ericsson.se>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: Iñaki Baz Castillo <ibc@aliax.net>, "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 13:44:22 -0000

I understand Ivo's point here - AFAIK there is no better way to indicate 
mutually exclusive capabilities.

	Thanks,
	Paul

On 5/8/12 8:22 AM, Ivo Sedlacek wrote:
> 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: 8. května 2012 14:05
>> To: Ivo Sedlacek
>> Cc: Paul Kyzivat; sipcore@ietf.org
>> Subject: Re: [sipcore] RFC5626 and REGISTER with multiple contacts
>>
>> 2012/5/8 Ivo Sedlacek<ivo.sedlacek@ericsson.com>:
>>>>> Contact:
>>>>> <sip:address:port>;+sip.instance="x";+sip.duplex="full";+sip.audio
>>>>> Contact:
>>>>> <sip:address:port>;+sip.instance="x";+sip.duplex="receive-only";+si
>>>>> p.a
>>>>> udio;+sip.video
>>>>
>>>> IMHO those two Contacts are expressing different capabilities for the
>>>> same *UA* (same
>>>> sip-instance) so they make no sense.
>>>
>>> The Contacts represent different combinations of supported capabilities in the
>> UA. Scope of support of a capability can be dependent on what other capabilities
>> are supported.
>>
>> Honestly I don't understand it. I try to see it simple, and for me the above two
>> Contact are expressing contradictory capabilities for the same UA (sip.instance)
>> since the first one announces
>> +sip.duplex="full" while the second one announces
>> +sip.duplex="receive-only", and both Contact announce capabilities for
>> the same UA.
>
> The UA is reachable using two contacts, each having different capabilities.
> At the first contact, the UA has capability to handle full duplex audio. E.g. normal voice call.
> At the second contact, the UA has capability to receive-only audio and video. E.g. TV broadcast.
>
> Please note that neither of the contacts of the UA support full duplex audio and video.
>
>
>>
>>
>> --
>> Iñaki Baz Castillo
>> <ibc@aliax.net>

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