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

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 28 September 2010 14:29 UTC

Return-Path: <HKaplan@acmepacket.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 9719C3A6B38 for <sipcore@core3.amsl.com>; Tue, 28 Sep 2010 07:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level:
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128, 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 C2NGSWLB-v3q for <sipcore@core3.amsl.com>; Tue, 28 Sep 2010 07:29:22 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 770273A6C34 for <sipcore@ietf.org>; Tue, 28 Sep 2010 07:29:22 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 28 Sep 2010 10:30:03 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 28 Sep 2010 10:29:41 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
Date: Tue, 28 Sep 2010 10:29:28 -0400
Thread-Topic: [sipcore] Draft new: draft-holmberg-sipcore-proxy-feature [was: Feature-tags in the Path header field]
Thread-Index: ActfGZHyq0CAqF9USIuruRF+AoMFeA==
Message-ID: <FB2F77FC-79D9-45CB-8635-0F5A09D3B0E4@acmepacket.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> <AANLkTinOrkS-_n8jbbLzhqEhPBPYiJs33V2ie3XoO=He@mail.gmail.com>
In-Reply-To: <AANLkTinOrkS-_n8jbbLzhqEhPBPYiJs33V2ie3XoO=He@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 28 Sep 2010 14:29:23 -0000

On Sep 27, 2010, at 7:14 PM, Peter Musgrave wrote:

> 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).
> 

Right, that particular idea is mis-guided. :)

What you'd really do for that is indicate whether or not the b2bua supports ICE (since some SBC's do, and some don't, indicating you're an SBC doesn't help).  

There already is a feature tag for ICE ("sip.ice"), but such a thing would break immediately - since ICE is a new thing, legacy SBC's wouldn't know to say they don't do it, and there is no "!(feature-tag)" anyway; and the UA doesn't know whether it's talking through SBC's or plain proxies to begin with, and if they're plain proxies they wouldn't say anything about ice ever... so the UA can never guess this right.  If it gets back "sip.ice" then it knows for that one hop that said so it's ok, but it knows nothing about the rest.  

-hadriel