Re: [sipcore] Draft new: draft-holmberg-sipcore-proxy-feature [was: Feature-tags in the Path header field] Tue, 12 October 2010 15:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5FD823A69E4 for <>; Tue, 12 Oct 2010 08:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -97.771
X-Spam-Status: No, score=-97.771 tagged_above=-999 required=5 tests=[AWL=-1.625, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id C0MCSR8OlCSr for <>; Tue, 12 Oct 2010 08:45:50 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CC1B33A69D6 for <>; Tue, 12 Oct 2010 08:45:47 -0700 (PDT)
Received: from [] by with surfront esmtp id 35101727820181; Tue, 12 Oct 2010 23:45:43 +0800 (CST)
Received: from [] by [] with StormMail ESMTP id 38058.5143419512; Tue, 12 Oct 2010 23:44:22 +0800 (CST)
Received: from ([]) by with ESMTP id o9CFlGwv034157; Tue, 12 Oct 2010 23:47:16 +0800 (CST) (envelope-from
In-Reply-To: <>
To: Paul Kyzivat <>, Christer Holmberg <>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <>
Date: Tue, 12 Oct 2010 23:44:50 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-10-12 23:46:56, Serialize complete at 2010-10-12 23:46:56
Content-Type: multipart/alternative; boundary="=_alternative 0056AFA4482577BA_="
X-MAIL: o9CFlGwv034157
Cc: "" <>
Subject: Re: [sipcore] Draft new: draft-holmberg-sipcore-proxy-feature [was: Feature-tags in the Path header field]
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Oct 2010 15:45:53 -0000

Hi Paul and Christer,

We now use this draft in our IMS(3GPP's SRVCC), currently in standard 

So, we support this one.



 Zip    : 210012
 Tel    : 87211
 Tel2   :(+86)-025-52877211
 e_mail :

Paul Kyzivat <> 
2010-09-27 22:46

Christer Holmberg <>
"" <>
Re: [sipcore] Draft new: draft-holmberg-sipcore-proxy-feature [was: 
Feature-tags in the Path header field]

[as chair]

To all sipcore participants:

Christer has been looking for a way to accomplish a particular function 
that 3gpp wants. This proposal seems a plausible way to do that. But it 
is of necessity defining a more general mechanism.

I'd really appreciate comments from others (including people in no way 
involved with 3gpp) regarding this mechanism. For instance, do you 
consider the semantics to be well defined? Do you see need for more 
about security implications?

How many would find this useful to have?


On 9/24/2010 7:04 AM, Christer Holmberg wrote:
> Hi,
> I've submitted a draft, which extends the rr-param rule, allowing 
proxies to indicate supported features using feature tags in Path, 
Record-Route etc.
> The draft can also be found at:

> As I indicated earlier on the list, and as you can read in the draft, 
there is a 3GPP use-case where we believe the mechanism could be used. 
But, there is nothing 3GPP specific about the mechanism as such.
> Regards,
> Christer
sipcore mailing list

ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.