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

Hi John and Paul,

>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.

You raise a good point.

In my opinion multiple support indications should be covered by the feature specification, because I don't think it is possible to define a genral behavior.

I can add text about that in the draft.

>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?

I am pretty sure there will be more text added, if we decide to initiate the work on this.

Regards,

Christer

> 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
>