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

"Leis, Peter (NSN - DE/Munich)" <peter.leis@nsn.com> Thu, 30 September 2010 09:19 UTC

Return-Path: <peter.leis@nsn.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 B63913A6BD4 for <sipcore@core3.amsl.com>; Thu, 30 Sep 2010 02:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 UKjOLwL77FNr for <sipcore@core3.amsl.com>; Thu, 30 Sep 2010 02:19:39 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 9DB203A6C39 for <sipcore@ietf.org>; Thu, 30 Sep 2010 02:19:38 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o8U9KKg7025407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Sep 2010 11:20:20 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o8U9KHe6021942; Thu, 30 Sep 2010 11:20:20 +0200
Received: from DEMUEXC035.nsn-intra.net ([10.150.128.26]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 30 Sep 2010 11:20:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 30 Sep 2010 11:20:17 +0200
Message-ID: <79C4240C13B4C84B910850B96B1B43120188A80A@DEMUEXC035.nsn-intra.net>
In-Reply-To: <4CA0AE61.7060003@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] Draft new: draft-holmberg-sipcore-proxy-feature [was: Feature-tags in the Path header field]
Thread-Index: ActeUuFaw0z49Q1AQGyYWPM9Or9gCwCLBGnw
References: <7F2072F1E0DE894DA4B517B93C6A058501703422@ESESSCMS0356.eemea.ericsson.se> <4C936714.2040808@cisco.com> <7F2072F1E0DE894DA4B517B93C6A058501703523@ESESSCMS0356.eemea.ericsson.se>, <4C936E79.3070906@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585015BCA8B@ESESSCMS0356.eemea.ericsson.se>, <4C938ED5.10507@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585015BCA8E@ESESSCMS0356.eemea.ericsson.se>, <4C93E4DE.9070802@cisco.com><7F2072F1E0DE894DA4B517B93C6A0585015BCA92@ESESSCMS0356.eemea.ericsson.se><7F2072F1E0DE894DA4B517B93C6A058501769F3A@ESESSCMS0356.eemea.ericsson.se> <4CA0AE61.7060003@cisco.com>
From: "Leis, Peter (NSN - DE/Munich)" <peter.leis@nsn.com>
To: "ext Paul Kyzivat" <pkyzivat@cisco.com>, "Christer Holmberg" <christer.holmberg@ericsson.com>
X-OriginalArrivalTime: 30 Sep 2010 09:20:19.0736 (UTC) FILETIME=[B3B69980:01CB6080]
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Draft new: draft-holmberg-sipcore-proxy-feature [was: 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: Thu, 30 Sep 2010 09:19:40 -0000

I do find such a mechanism useful.

regards
Peter

> -----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On
> Behalf Of ext Paul Kyzivat
> Sent: Monday, September 27, 2010 4:47 PM
> To: Christer Holmberg
> Cc: sipcore@ietf.org
> Subject: 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?
> 
> 	Thanks,
> 	Paul
> 
> 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:
> http://users.piuha.net/cholmber/drafts/draft-holmberg-sipcore-proxy-
> feature-00.txt
> >
> > 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
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore