All, I have together with Olaf Kolkman suggested a new RR type that I call URI that work similarly to what is described in this draft (regarding the owner of the RRSET), but a URI in the RDATA. It has been posted to the namedroppers list a few times...but maybe that has been wrong. Maybe Apps Area should have been notified about the work a bit more... Cyrus has asked a few questions about it, and maybe it is me that have not reached out to the Caldav people enough? I have tried to push it through via the DNS people in the IETF, but there have not been enough traction. Anyway... I can do that via an individual submission if there is interest. I think the draft is ready for publication. See http://tools.ietf.org/html/draft-faltstrom-uri-04 (i.e. the draft has expired a few months ago). 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Priority | Weight | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / / / Target / / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ In this case (to take an example from the draft in question), it would be for example: Instead of: _caldav._tcp SRV 0 1 80 calendar.example.com. Followed by doing PROPFIND for http://calendar.example.com/.well-known/caldav ...etc... With a potential redirect etc... It could with the URI resource record for example be: _caldav._caldav IN URI 10 1 "http://www.example.com/example/whatever/uri/caldav/"; or _carddav._caldav IN URI 10 1 "http://www.example.com/foo/some/other/uri/carddav/"; And the URI is used directly for the PROPFIND. Patrik On 21 jun 2010, at 20.10, Cullen Jennings 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
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf