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> Wed, 29 September 2010 07:46 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 833BE3A6D25 for <sipcore@core3.amsl.com>; Wed, 29 Sep 2010 00:46:44 -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 5vmIyRkb-7F3 for <sipcore@core3.amsl.com>; Wed, 29 Sep 2010 00:46:43 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 594073A6C7C for <sipcore@ietf.org>; Wed, 29 Sep 2010 00:32:51 -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 o8T7XRHj019673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Sep 2010 09:33:27 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o8T7XRbC011659; Wed, 29 Sep 2010 09:33:27 +0200
Received: from DEMUEXC035.nsn-intra.net ([10.150.128.26]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 29 Sep 2010 09:33:27 +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: Wed, 29 Sep 2010 09:33:25 +0200
Message-ID: <79C4240C13B4C84B910850B96B1B431201889EB1@DEMUEXC035.nsn-intra.net>
In-Reply-To: <BEEFBEB0-ABF9-4E4C-B12F-32C3078FD7BF@acmepacket.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: ActfMko7GgIhjib/QcOI+UgTLz20ZwAcaSgA
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>, <45CE8B00-05A8-4DF3-9140-6D4C51D81CF1@acmepacket.com><7F2072F1E0DE894DA4B517B93C6A058502C71700@ESESSCMS0356.eemea.ericsson.se> <BEEFBEB0-ABF9-4E4C-B12F-32C3078FD7BF@acmepacket.com>
From: "Leis, Peter (NSN - DE/Munich)" <peter.leis@nsn.com>
To: "ext Hadriel Kaplan" <HKaplan@acmepacket.com>, "Christer Holmberg" <christer.holmberg@ericsson.com>
X-OriginalArrivalTime: 29 Sep 2010 07:33:27.0010 (UTC) FILETIME=[9B048420:01CB5FA8]
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: Wed, 29 Sep 2010 07:46:44 -0000

See below

> > Also note that ATCF adding a feature tag into the Contact header
> field in REGISTER request would also cause reg event package
> > NOTIFY to contain the added feature tag. The UE receiving the reg
> event package NOTIFY would be quite confused as its contact
> > address would have additional feature tags. Parsing and modifying
the
> XML is not desired.
> >>
> >>
> 
> Don't bother keeping it that way then.  This is already a private
> network thing to begin with, so specify that the S-CSCF treats that
> 3gpp.svcc thing of a REGISTER as the network-inserted indication that
> it is, rather than as opaque UE capabilities (ie, so it won't show up
> in XML stuff, because it won't be stored in the UE's normal Registered
> feature tags set in the databases).  Or are you worried about a case
of
> the REGISTER going to another domain (like through a Visited to a Home
> domain)?

Yes, the entity (ATCF) indicating its capabilites may reside in the
visited network, while S-CSCF is in the home. So you may end up in a
situation where the S-CSCF does not understand the semantics of
"3gpp.svcc" appended to the Contact. So the tag would end up in the
"normal" registered feature tags of the UE.