Re: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt

[Dean Willis <[e-mail]>]

On Oct 18, 2005, at 12:32 PM, Paul Kyzivat wrote:
>
> I would say that in the VM case the proxy knows the target is a VM  
> system, and in the other case the proxy knows *nothing* about the  
> characteristics of the target. It might be an application. It might  
> be a user device, or it might be an AOR that could route to either  
> a user device, a VM, some other application, or yet another unknown  
> target.
>

In which case, if we follow the principles of RFC 3087, it becomes  
the responsibility of whoever fills in this URI to include whatever  
parameters are needed by the target. I'm fairly happy with that  
understanding, if that's what Francois is really saying, and if John  
and the other folks agree.

So if that's true, what we're talking about here is really something  
like the netann draft, in that it is informationally defining some  
reusable parameters for specific services that are invoked in a  
manner consistent with RFC 3087. If that's what we want, I think  
that's a manageable scope and something we know how to do.

Like netann and 3087, this doesn't even have to be (although it could  
be, if we have that sort of consensus) a working group document. It  
could proceed as an individual informational. Of course, like netann,  
we'd still want to make sure it actually answers the questions and  
doesn't confuse people excessively.

--
Dean



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP