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

["Leis, Peter (NSN - DE/Munich)" <[e-mail]>]

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.