> On 4/28/11 8:11 PM, Thomson, Martin wrote:
> > This is the right idea, but I don't think that a request parameter
> > is
> going to help. It would be unlikely that a server is able to support
> a new policy URI scheme because a client asks for that scheme.
> Instead, we can simply suggest that the server provide a policy URI
> for every scheme that it supports. The client can then pick the one
> that suits it best.
>
> After thinking about this a bit, there is a possibility that the
> server is having to allocate specific resources on a per-protocol
> basis, in which case you'd want the ability for the client to hint at
> a preferred protocol (so as to avoid unnecessary allocation of
> resources for unwanted protocols).
I'm inclined to classify this as an optimization. So three reasons not to add the parameter:
1. laziness
2. it's probably not too much extra load to create a resource for most types of resources, especially if you optimize for the case where the resource isn't accessed
3. DHCP won't have any hinting
If another editor manages to overcome #1, then I'm OK with having the hint.
--Martin
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
