Hello All, So a couple of days ago I posted draft-appelbaum-dnsop-onion-tld-01:
https://tools.ietf.org/html/draft-appelbaum-dnsop-onion-tld-01 <https://tools.ietf.org/html/draft-appelbaum-dnsop-onion-tld-01> Again, the diffs are minimal from -00: https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-appelbaum-dnsop-onion-tld-01.txt <https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-appelbaum-dnsop-onion-tld-01.txt> …and I am cognizant of (planned, delayed) interim meetings to cover broader RFC6761 discussion points. However I also have an elderly systems administrator’s eye towards extremely hard (and CABForum-sourced) deadlines and process, and I also hereby will admit my complete ignorant newbie-ness towards established procedure for DNSOP and RFC adoption. “Everybody has to be a learner-driver at least once.” :-) So I would like to invite the community, please, to pass comment and consideration on draft-appelbaum-dnsop-onion-tld-01 which (if necessary) can be addressed in one last round of edits-to and review-of the document; and if someone would also kindly point me towards the process for seeking a “call to adoption”, I would be most grateful. I hope to see all of the DNSOP processes - both established and ad-hoc - interlock in a graceful and well-oiled manner. Many thanks and best wishes, - alec — Alec Muffett Security Infrastructure Facebook Engineering London
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
