Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
"Elwell, John" <john.elwell@siemens-enterprise.com> Mon, 24 January 2011 15:30 UTC
Return-Path: <john.elwell@siemens-enterprise.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 534423A68FA for <sipcore@core3.amsl.com>; Mon, 24 Jan 2011 07:30:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level:
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, 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 W8SQzOtgwXas for <sipcore@core3.amsl.com>; Mon, 24 Jan 2011 07:30:43 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 85E6D3A6ADD for <sipcore@ietf.org>; Mon, 24 Jan 2011 07:30:42 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3120817; Mon, 24 Jan 2011 16:33:36 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id DD31D23F0292; Mon, 24 Jan 2011 16:33:36 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 24 Jan 2011 16:33:36 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@cisco.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Mon, 24 Jan 2011 16:33:35 +0100
Thread-Topic: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
Thread-Index: Acu5z9D8UhecMC5qQI6eh5pB0NTuqAARpZOzAHDxB3A=
Message-ID: <A444A0F8084434499206E78C106220CA05FCA0D6FE@MCHP058A.global-ad.net>
References: <7F2072F1E0DE894DA4B517B93C6A058502B84084@ESESSCMS0356.eemea.ericsson.se> <BDBFB6CE314EDF4CB80404CACAEFF5DE07C6C68C@XCH02DFW.rim.net>, <4D3A2C3D.10508@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585194414F717@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A0585194414F717@ESESSCMS0356.eemea.ericsson.se>
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
Subject: Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
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, 24 Jan 2011 15:30:44 -0000
Well, if everyone says they won't perform a feature because somebody else is going to do it, that seems like a recipe for not having the feature performed at all. There would need to be some rules on which entity performs the feature and which entities do not perform the feature. I am not sure this was clear from the draft. John > -----Original Message----- > From: sipcore-bounces@ietf.org > [mailto:sipcore-bounces@ietf.org] On Behalf Of Christer Holmberg > Sent: 22 January 2011 09:32 > To: Paul Kyzivat; sipcore@ietf.org > Subject: Re: [sipcore] Draft new version: > draft-holmberg-sipcore-proxy-feature > > > Hi Paul, > > The idea is that each feature specification defines what > indicating support of a feature means - in the same way it is > done for UAs. > > For example, just because a proxy indicate support of a > feature, it doesn't automatically mean that others will > address requests towards that proxy. It may for example mean > that another entity, when it sees the feature tag, does not > trigger some action. > > I am sure there are things in the draft than can be > clarified, including the 3GPP use-cases, but I think it would > be useful to know (for me personally, and for 3GPP that wants > to use the mechanism) whether the WG is willing to start this > work. Nobody has objected to the work as such (you even say > yourself that it might be useful :), and all questions and > issues that have been raised will of course have to be solved > (like we always do). > > Regards, > > Christer > > > > ________________________________________ > From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On > Behalf Of Paul Kyzivat [pkyzivat@cisco.com] > Sent: Saturday, January 22, 2011 3:00 AM > To: sipcore@ietf.org > Subject: Re: [sipcore] Draft new version: > draft-holmberg-sipcore-proxy-feature > > (speaking as an individual) > > Inline... > > > > On 1/21/2011 5:25 PM, Andrew Allen wrote: > > I have reviewed this draft and basically I am supportive of the > > objective of this work. > > > > I think the current use cases are very specific and the > problem itself > > is even more general. > > > > I think the general requirement is that it is useful for > UAs and other > > intermediaries to be able to detect the presence of an > intermediary on > > the path of a registration or the route of a dialog when that > > intermediary provides some feature or service and be able > to identify > > the URI of that intermediary in order to be able to address > requests to > > it . In addition to the 3GPP specific use cases currently > in the draft I > > think there are others including: > > A major thing that is lacking here is any explanation of what > it *means* > for an intermediary to "offer a feature" - what sorts of > features those > are, and how one might avail oneself of them. > > In the case of callerprefs/callee caps and currently defined, the > intermediary is a proxy that does address translation based on a > registrar. One knows that the way to avail themselves of the > features is > to send a request to an AOR with registrations and use callerprefs to > request routing to a device with those features. > > Or, one might learn about capabilities because they are returned > attached to a contact in a dialog, and then one avails oneself of the > capabilities by sending a subsequent request to that contact. > > Now maybe this draft implies no more - that the capabilities are ones > that I can get access to by sending a request to the address I find in > the Route header. But of course its not normal to send a request with > the R-URI being an address taken from a Route header. > > I think this is the usual thing - there is a framework within > which this > makes sense, but its defined in IMS. And as usual, the > inclination is to > say: please say more than that you want this to use in some > unspecified > way with IMS. > > Thanks, > Paul > > > Dealing with call feature interactions > > > > In a deployment where different intermediaries provide > different call > > features it is sometimes necessary to be able to detect that another > > intermediary has invoked a particular feature as that may > mean that a > > particular feature should not be invoked or should be > invoked in a way > > that takes account of the invocation of the feature by the other > > intermediary in order to prevent conflicts between > different call features. > > So in this case it is not about detecting *capabilities* that might be > used, but rather about detecting behavior that is already > being applied? > > > Detecting the presence of a SIP PBX > > > > SIP PBXs may be present in a network and may provide call > features and > > other services on behalf of the UA. In some cases the UA may need to > > address requests to the PBX to invoke some features or services. > > This is more what I was getting at. But its not clear to me what the > model is for "addressing requests to the PBX to invoke some > features or > services". > > > Although presence of the PBX could be indicated using > configuration this > > isn't really effective when there are mobile UAs moving between > > enterprise networks that have PBXs and public networks that don't. > > > > Detecting the presence of a telephony application server. > > > > In 3GPP IMS Multimedia Telephony Service (MMTel) there is a > Telephony > > Application Server (TAS) that provides call features on > behalf of the > > UA. However not all 3GPP networks will necessarily deploy > MMTel so it is > > necessary that a UA be able to identify that a TAS is > involved in the > > call and be able to send requests such as REFER to the TAS > in order to > > perform functions like call transfer. Having the TAS always act as a > > full B2BUA and overwrite the Contact is not a good solution > as this will > > cause the loss of the GRUUs of the far end UAs. > > This begs some higher level model of the possible components > in a system > and their potential relationships to one another. I realize IMS has > this, that doesn't help in defining this in the ietf context. We are > starting to have such things in the work that was done in BLISS. But I > don't know if that is similar. And of course a bunch of ietf folk > believe that IMS has it all wrong. > > > In addition since the same intermediary may perform > multiple features or > > services it is useful for the URI that is provided to identify the > > related call feature or service so that when the UA > addresses a request > > to the intermediary the intermediary knows what feature or > service the > > request is related to. > > > > Some detailed comments: > > > > Section 6 > > > > NOTE: If a route set is built using Path, Record-Route or Service- > > > > Route header fields, any inserted feature tag will be > copied into the > > > > associated Route header fields, together with other header field > > > > parameters. This specification does not define any specific meaning > > > > of the feature tags present in Route header fields in such cases. > > > > I think the meaning of the feature tag in the Route header > is the same > > it means that the entity whose URI is on the Route supports > the feature > > Yes. Those other headers only exist to form Routes. I would think that > it is presence on the Route that would matter, except in cases where > presence on Record-Route leads something along the way to > block the call. > > > Section 7 > > > > I think the direction issue may need more work. It would I think be > > useful to indicate the directionality. > > > > I believe that SIPCORE should adopt this and work on a solution. > > I hear you. Lets see what others have to say. > > Thanks, > Paul > > > Andrew > > > > *From:*sipcore-bounces@ietf.org > [mailto:sipcore-bounces@ietf.org] *On > > Behalf Of *Christer Holmberg > > *Sent:* Tuesday, December 07, 2010 7:38 AM > > *To:* sipcore@ietf.org > > *Subject:* [sipcore] Draft new version: > draft-holmberg-sipcore-proxy-feature > > > > Hi, > > > > I've submitted a new version of the proxy-feature draft. > > > > It now contains more use-cases, for which the usage of the > draft have > > been discussed in 3GPP. > > > > In the examples there is also some wording about why the > usage of the > > Contact header field is not seen as appropriate. > > > > I have added some text about the "direction" of capabilities. > > > > Regards, > > > > Christer > > > > > --------------------------------------------------------------------- > > This transmission (including any attachments) may contain > confidential > > information, privileged material (including material > protected by the > > solicitor-client or other applicable privileges), or constitute > > non-public information. Any use of this information by > anyone other than > > the intended recipient is prohibited. If you have received this > > transmission in error, please immediately reply to the > sender and delete > > this information from your system. Use, dissemination, > distribution, or > > reproduction of this transmission by unintended recipients is not > > authorized and may be unlawful. > > > > > > > > _______________________________________________ > > sipcore mailing list > > sipcore@ietf.org > > https://www.ietf.org/mailman/listinfo/sipcore > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >
- [sipcore] Draft new version: draft-holmberg-sipco… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Andrew Allen
- 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… R.Jesske
- Re: [sipcore] Draft new version: draft-holmberg-s… Elwell, John
- Re: [sipcore] Draft new version: draft-holmberg-s… Elwell, John
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version:draft-holmberg-si… Andrew Allen
- Re: [sipcore] Draft new version: draft-holmberg-s… Adam Roach
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Adam Roach
- Re: [sipcore] Draft new version: draft-holmberg-s… R.Jesske
- 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… Paul Kyzivat
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… R.Jesske
- Re: [sipcore] Draft new version: draft-holmberg-s… Adam Roach
- Re: [sipcore] Draft new version:draft-holmberg-si… Andrew Allen
- Re: [sipcore] Draft new version: draft-holmberg-s… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Adam Roach
- [sipcore] Proxy-feature use-case: forking capabil… Christer Holmberg
- 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… Adam Roach
- 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… Adam Roach
- 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-si… DOLLY, MARTIN C (ATTSI)
- 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… Paul Kyzivat
- Re: [sipcore] Draft new version:draft-holmberg-si… Paul Kyzivat
- 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… Christer Holmberg
- Re: [sipcore] Draft new version: draft-holmberg-s… Elwell, John
- Re: [sipcore] Draft new version: draft-holmberg-s… Hannes Tschofenig
- 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… Elwell, John
- Re: [sipcore] "emergency" via draft-holmberg-sipc… Paul Kyzivat
- [sipcore] Draft new version: draft-holmberg-sipco… Christer Holmberg