Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature-03 (featuring the Feature-Caps header field)
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 01 November 2011 17:26 UTC
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 398101F0C44 for <sipcore@ietfa.amsl.com>; Tue, 1 Nov 2011 10:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level:
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InCuUnt4lW82 for <sipcore@ietfa.amsl.com>; Tue, 1 Nov 2011 10:26:04 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2702611E8094 for <sipcore@ietf.org>; Tue, 1 Nov 2011 10:26:03 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta05.westchester.pa.mail.comcast.net with comcast id rohc1h0031vXlb855tRmT8; Tue, 01 Nov 2011 17:25:46 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta17.westchester.pa.mail.comcast.net with comcast id rtRl1h01t0tdiYw3dtRlZ2; Tue, 01 Nov 2011 17:25:46 +0000
Message-ID: <4EB02B97.5080008@alum.mit.edu>
Date: Tue, 01 Nov 2011 13:25:43 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <4E8C785D.5080003@alum.mit.edu> <7F2072F1E0DE894DA4B517B93C6A05852233C3B7F8@ESESSCMS0356.eemea.ericsson.se> <D85A6021-FD66-4D06-9A21-74846741C83C@acmepacket.com> <7F2072F1E0DE894DA4B517B93C6A058522341F50A8@ESESSCMS0356.eemea.ericsson.se> <4EA03904.1010704@alum.mit.edu> <7F2072F1E0DE894DA4B517B93C6A05852233D45FEB@ESESSCMS0356.eemea.ericsson.se> <4EA066EB.40701@alum.mit.edu> <8828E4D5-D8C1-4578-A9F4-87B363F0CEE6@acmepacket.com>, <4EA6C3DA.6000605@alum.mit.edu> <7F2072F1E0DE894DA4B517B93C6A05852233C3B811@ESESSCMS0356.eemea.ericsson.se> <4EA75F61.8090409@alum.mit.edu> <7F2072F1E0DE894DA4B517B93C6A0585223428CA5B@ESESSCMS0356.eemea.ericsson.se> <7F2072F1E0DE894DA4B517B93C6A058522342DDA7E@ESESSCMS0356.eemea.ericsson.se> <E9573C46-FD9A-4E3D-BF77-8F25C64F9030@acmepacket.com> <6CB233EE-CBD0-4319-B46F-1483302263E0@cisco.com> <C6014970-2F88-4902-93D6-AECCBDE47872@acmepacket.com>, <4EAEDEDD.30202@alum.mit.edu> <7F2072F1E0DE894DA4B517B93C6A05852235717398@ESESSCMS0356.eemea.erics son.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852235717398@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] Draft new version: draft-holmberg-sipcore-proxy-feature-03 (featuring the Feature-Caps header field)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 01 Nov 2011 17:26:05 -0000
On 10/31/11 2:36 PM, Christer Holmberg wrote: > > Hi, > >>> Since then it has slowly morphed into the type of DWIM vs DWIS mechanism that I thought we agreed we did not to do. Keep in mind any UA can >>> act as an embedded proxy and this looks like the feature scheme that I thought was the roughly the core of the DWIM vs DWIS argument. >>> >>> Anyways, for any mechanisms of this sort, I will be strongly apposed unless the registration mechanism for new tags, features, options or whatever >>> you call them is the same as it is for sip option tags. I have spoken at the mic several times in favor of what Christer was presenting but it always had >>> that property. This does not and I am strongly opposed to it. Given the previous conversation were in the other context, whatever consensus they >>> may or may not have had does not seem to apply here. If the goal is simply to change what is required to register option tags, I'd be happy to have that conversation. >> >> Currently the draft mechanism is indicating RFC-3840-type feature-tags. As such yes new values require RFCs published through IETF Consensus (IESG approval), as >> opposed to standards track RFCs as required for option-tags. I believe as a WG-draft we can choose whether tokens put into a new header are actual feature-tags, >> or some new "capability-tags" with higher RFC approval status required. And of course we can say what semantics such new capability-tags RFCs must define and be >> constrained to. I don't think any of those things prevent us from making it a WG draft do they? I thought being a WG draft just meant the WG accepted the goal as a >> milestone, had enough people willing to work on it, and thought the general direction of the draft's solution was right. >> >> Actually, its possible to define feature tags without any standards >> action. See section 3.1.3 of RFC 2506. (It allows feature tags beginning >> with "u." followed by a URI.) >> >> Its my impression that this is one of the things that 3gpp likes about >> feature tags - they can define new ones without an ietf standards action. > > There are no 3GPP defined feature tags beginning with "u", and as far as I know 3GPP has (or, is in the progress of) registered all their feature tags with IANA. OK, my mistake. There is also a global tree (tags starting with g.) for which new values can be registered by expert review, without publication of an RFC. And 3gpp has registered several of these. > And, as you also indicated, we can specify what information a feature tag specification, and its associated IANA registration, needs to contain. If we use feature tags, unless we require use of the "sip" tree, or define a new tree, I don't think we can specify what the specification includes, since the registration is defined by RFC 2506. > Also, if you look at the use-cases behind this work, I think feature tags are very appropriate. We are talking about feature indications ("I can do this"). And, we are not talking about extensions to the SIP protocol, in > which case I agree option-tags probably would be more suitable. Frankly, IMO the adoption of feature tags for 3840 was a mistake, because the semantics of feature tags for callee caps / callerprefs largely disjoint from the intended original use of feature tags. If the intent is to require a specification with particular properties, then we can do this better by defining a new namespace. Thanks, Paul
- [sipcore] draft-ietf-sipcore-proxy-feature-reqs-01 Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Iñaki Baz Castillo
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Olle E. Johansson
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Iñaki Baz Castillo
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Gilad Shaham
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- [sipcore] Draft new version: draft-ietf-sipcore-p… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Adam Roach
- Re: [sipcore] Draft new version: draft-ietf-sipco… Worley, Dale R (Dale)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] Draft new version: draft-ietf-sipco… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Hadriel Kaplan
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- [sipcore] draft-ietf-sipcore-proxy-feature-reqs-0… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… DRAGE, Keith (Keith)
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-proxy-feature-re… Christer Holmberg
- [sipcore] Draft new version: draft-holmberg-sipco… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Hadriel Kaplan
- Re: [sipcore] Draft new version: draft-holmberg-s… Paul Kyzivat
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Cullen Jennings
- Re: [sipcore] Draft new version: draft-holmberg-s… Hadriel Kaplan
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Paul Kyzivat
- Re: [sipcore] Draft new version: draft-holmberg-s… Paul Kyzivat
- Re: [sipcore] Draft new version: draft-holmberg-s… Paul Kyzivat
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Paul Kyzivat
- Re: [sipcore] Draft new version: draft-holmberg-s… Paul Kyzivat