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

One issue that Paul hasn't raised is what happens if there are two or more Path, Service-Route or Record-Route entries declaring a particular feature. Or two or more entries, some but not all of which declare a particular feature. For the application that Christer has in mind, I would imagine it doesn't matter - the most important thing is that at least one entry declares the feature of interest. However, if we try to generalise the mechanism, such issues might become important.

I do not have an opinion on whether this is a good thing to do or not - just trying to understand the implications.

John

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 27 September 2010 15:47
> To: Christer Holmberg
> Cc: sipcore@ietf.org
> Subject: Re: [sipcore] Draft new: 
> draft-holmberg-sipcore-proxy-feature [was: Feature-tags in 
> the Path header field]
> 
> [as chair]
> 
> To all sipcore participants:
> 
> Christer has been looking for a way to accomplish a 
> particular function 
> that 3gpp wants. This proposal seems a plausible way to do 
> that. But it 
> is of necessity defining a more general mechanism.
> 
> I'd really appreciate comments from others (including people 
> in no way 
> involved with 3gpp) regarding this mechanism. For instance, do you 
> consider the semantics to be well defined? Do you see need for more 
> about security implications?
> 
> How many would find this useful to have?
> 
> 	Thanks,
> 	Paul
> 
> On 9/24/2010 7:04 AM, Christer Holmberg wrote:
> >
> > Hi,
> >
> > I've submitted a draft, which extends the rr-param rule, 
> allowing proxies to indicate supported features using feature 
> tags in Path, Record-Route etc.
> >
> > The draft can also be found at: 
> http://users.piuha.net/cholmber/drafts/draft-holmberg-sipcore-
> proxy-feature-00.txt
> >
> > As I indicated earlier on the list, and as you can read in 
> the draft, there is a 3GPP use-case where we believe the 
> mechanism could be used. But, there is nothing 3GPP specific 
> about the mechanism as such.
> >
> > Regards,
> >
> > Christer
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 