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

Peter Musgrave <peter.musgrave@magorcorp.com> Mon, 27 September 2010 23:14 UTC

Return-Path: <peter.musgrave@magorcorp.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 AFE523A6BC4 for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 16:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.853
X-Spam-Level:
X-Spam-Status: No, score=-101.853 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 ViwEs2X++7uO for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 16:14:17 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id B34DB3A6BE6 for <sipcore@ietf.org>; Mon, 27 Sep 2010 16:14:14 -0700 (PDT)
Received: by qyk2 with SMTP id 2so6695760qyk.10 for <sipcore@ietf.org>; Mon, 27 Sep 2010 16:14:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.37.11 with SMTP id v11mr6066157qad.374.1285629293597; Mon, 27 Sep 2010 16:14:53 -0700 (PDT)
Received: by 10.229.68.39 with HTTP; Mon, 27 Sep 2010 16:14:53 -0700 (PDT)
In-Reply-To: <4CA0AE61.7060003@cisco.com>
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>
Date: Mon, 27 Sep 2010 19:14:53 -0400
Message-ID: <AANLkTinOrkS-_n8jbbLzhqEhPBPYiJs33V2ie3XoO=He@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sipcore@ietf.org" <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: Mon, 27 Sep 2010 23:14:19 -0000

Hi,

I read the draft and I think the semantics are ok (although John's
point about multiple proxies with these tags is a good one).

One use which occurred to me - but which is no doubt controversial  -
is whether a proxy/B2B which is an SBC could provide a feature tag
indicating it is an SBC - so that UAs which register and call through
it could skip adding ICE candidates. (My point is merely that I
suspect other uses for this capability will be found - even if you
think this  particular idea is mis-guided).

Regards,

Peter Musgrave






On Mon, Sep 27, 2010 at 10:46 AM, Paul Kyzivat <pkyzivat@cisco.com> wrote:
> [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
>