The process of standards making is to eliminate unnecessary flexibility. In this case the configuration of the caldav Web host is not relevant to the client. Therefore those details should not be exposed to the client. This is a security issue but also an encapsulation issue.
Exposing unnecessary details to clients is an invitation to engage in the equivalent of undocumented API calls. I do not want to expose that information to clients because I do not want them to start relying on it.
Rather, I suggest that we generalize the process and adopt the convention that the URL be formed from the SRV prefix. That is we have one registry for prefixes and apply them to SRV and URI formation.
I would also suggest adding in a version number so that it is possible to run two versions of the protocol using different back ends.
Since we are using SRV we will have two DNS names involved
1) The DNS name of the protocol
2) The DNS name of the host on which the service is provided
The DNS name of the host need not be the only DNS name that the host responds to. Ergo, there is no actual need to use the .wellknown hack in this particular case. We can insist that the DNS name be reserved for forwarding web services.
As for the need for 'redirect' this should not affect the protocol on the wire. Rather the Web server should perform any internal mapping.
On Mon, Jun 21, 2010 at 2:10 PM, Cullen Jennings <fluffy@xxxxxxxxx> wrote:
It seems like using NAPTR might be a better choice than the ./well-known with redirect.
On Jun 18, 2010, at 9:51 AM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
>
> - 'Use of SRV records for locating CalDAV and CardDAV services '
> <draft-daboo-srv-caldav-05.txt> as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@xxxxxxxx mailing lists by 2010-07-16. Exceptionally,
> comments may be sent to iesg@xxxxxxxx instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-daboo-srv-caldav-05.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18589&rfc_flag=0
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@xxxxxxxx
> https://www.ietf.org/mailman/listinfo/ietf-announce
Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
--
Website: http://hallambaker.com/
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf