Re: [sipcore] Feature-tags in the Path header field

Paul Kyzivat <pkyzivat@cisco.com> Fri, 17 September 2010 13:34 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B509F3A696D for <sipcore@core3.amsl.com>; Fri, 17 Sep 2010 06:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.506
X-Spam-Level:
X-Spam-Status: No, score=-110.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ok-4w-8ak8VU for <sipcore@core3.amsl.com>; Fri, 17 Sep 2010 06:34:40 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id B15393A694D for <sipcore@ietf.org>; Fri, 17 Sep 2010 06:34:24 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOULk0xAZnwN/2dsb2JhbACiInGmDZxUhUAEijOCfg
X-IronPort-AV: E=Sophos;i="4.56,382,1280707200"; d="scan'208";a="160432615"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 17 Sep 2010 13:34:49 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o8HDYntu008902; Fri, 17 Sep 2010 13:34:49 GMT
Message-ID: <4C936E79.3070906@cisco.com>
Date: Fri, 17 Sep 2010 09:34:49 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7F2072F1E0DE894DA4B517B93C6A058501703422@ESESSCMS0356.eemea.ericsson.se> <4C936714.2040808@cisco.com> <7F2072F1E0DE894DA4B517B93C6A058501703523@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058501703523@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] Feature-tags in the Path header field
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Sep 2010 13:34:41 -0000

Comments inline.

	Thanks,
	Paul

On 9/17/2010 9:19 AM, Christer Holmberg wrote:
>
> Hi,
>
>> Didn't somebody else already bring this up a few months ago?
>
> In that case I missed it :)

Maybe I have it mixed up with something else. Had to do with media 
capabilities out at the edge upstream of the UA.

>> IIUC, you are asking if Path can be used with a new parameter
>> without any further standards action. Is that right?
>
> At this point I am asking about the usage of feature tags to indicate proxy features in general.

Oh. I guess I missed the point.
But when feature tags are passed, it is as header parameters.
They have been explicitly defined to be allowed on Contact.
Every header is different in terms of what parameters it permits.

The fact that a parameter is defined for use on one header does not 
automatically usable with any other header. (Unless the two headers 
share some common definition. For instance, if the definition of 
rr-param was extended for Route then I believe Path would automatically 
pick that up as well.)

> Whether it would require some standards actions needs to be checked.
>
>> If I go back to the definition of Path in 3327, I find that
>> it allows multiple parameters of type "rr-param". It doesn't
>> define rr-param, but does say the Path header field values
>> must conform to the syntax of the Path element from 3261,
>> which defines rr-param as generic-param.
>>
>> So *syntactically* you can put whatever parameters you want
>> in there, and sip parsers should not be troubled. But
>> legalistically, new parameters can only be introduced via
>> standards action.
>
> Correct.
>
>> From a pure syntax perspective it is not a problem.
>
> But, for Contact, A-C, R-C and Refer-To we have defined "feature-param",

Yes.

> which in this case would be an explicit usage of "rr-param".

I don't follow your logic. How does definition of feature-param for the 
headers that have it relate in any way to rr-param?

>> I suspect the problem 3gpp is trying to address may be of
>> more general interest. But its hard to decipher from your
>> brief description. Can you provide a more complete
>> description of the problem and the proposed solution? For
>> instance, diagrams of the signaling and media paths before
>> and after the handoff of the call.
>
> Well, I was trying to keep the handover description as short as possible, because the intention was not to discuss it. But, for sure I can provide references if people want to read the details.
>
> The idea was to provide some background information to show that there is a problem, to avoid questions like "You have a solution - where is the problem?" :)

I'm glad to hear that!

> I do, however, agree that the possibility to provide proxy features may be of more general interest, and that is also one reason I raised this issue on the list.
>
> Regards,
>
> Christer
>
>
>
>
>> On 9/17/2010 7:17 AM, Christer Holmberg wrote:
>>> Hi,
>>> Introduction:
>>> -----------------
>>> 3GPP is working on solution which improves the ability to
>> be able to
>>> move an ongoing IMS call from an IP based access network to
>> a legacy
>>> CS based network without dropping the call.
>>> The solution requires a media anchoring proxy (called ATCF) in the
>>> visited network, and a signaling anchoring application
>> server (called
>>> SCC AS) in the users home network.
>>> Problem:
>>> ------------
>>> The SCC AS, when it receives a REGISTER request from a UA, needs to
>>> know whether there is a proxy with ATCF functionaltiy in the
>>> registration path. The reason is that the SCC AS can then choose to
>>> delegate session handover functionality to the ATCF, which provides
>>> advantages related to voice interruption etc.
>>> Possible solution:
>>> -------------------------
>>> During registration the ATCF inserts a Path header field, so a
>>> solution to indicate its support of the ATCF functionlaity
>> would be to
>>> insert a feature tag in the Path header field.
>>> However, eventhough there is no syntax issue, the usage of feature
>>> tags have only been specified for the Contact, Accept-Contact,
>>> Reject-Contact and Refer-To header fields.
>>> So, the question is whether there are any reasons why the
>> proxy could
>>> not use a feature tag in the Path header field for this.
>> Entities that
>>> don't support the feature will simply see it as an unsupported Path
>>> header field parameter, and a registrar doing normal feature tag
>>> matching shouldn't even look at the Path header field. And,
>> based on
>>> the feature tag definitions in RFC3840 and RFC2703, we
>> don't think the
>>> usage is necessarily limited to UAs Regards, Christer
>>>
>>>
>>>
>>> _______________________________________________
>>> sipcore mailing list
>>> sipcore@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sipcore
>>