I was talking about a reference to a document in a version repository (a github repository). The comment had nothing to do with the corporation "github". The issue is that the content of the reference is not stable. As Tor evolves, the content of that document changes. For many purposes, that is a good thing. For informative references, this is also fine. For normative references, that is references which must be understood to fully understand the document, they must reference stable content. (URIs are allowed if there is reasonable expectation that the content is stable.)
Which means that the real question is whether the references need to be understood to understand the registration. This judgment belongs to the IESG, not to me. I reviewed based on my understanding. If the assignment to Tor of .onion is for any use that Tor chooses, then indeed the references are informative. If the assignment is for use for some specific problem and behavior, then the references are normative. The wording of the draft led me to believe it was the latter. In either case, the draft should be clear about what it is doing. Yours, Joel -----Original Message----- From: Alec Muffett [mailto:al...@fb.com] Sent: Thursday, September 03, 2015 11:32 AM To: Joe Abley Cc: hellekin; tjw.i...@gmail.com; Brian Haberman; dnsop-cha...@ietf.org; draft-ietf-dnsop-onion-...@ietf.org; dnsop@ietf.org; draft-ietf-dnsop-onion-tld...@ietf.org; draft-ietf-dnsop-onion-tld.sheph...@ietf.org; Jari Arkko; The IESG; Joel Halpern Subject: Re: [DNSOP] Jari Arkko's No Record on draft-ietf-dnsop-onion-tld-00: (with COMMENT) Hi Joe! > On Sep 3, 2015, at 4:02 PM, Joe Abley <jab...@hopcount.ca> wrote: > Pretty sure Joel was just referring to where the current documentation is > stored, not poking sticks at corporations. Just in order to fight potential confusion at any point where it might flare up, lest other folk jump into this discussion and try running with it: * The Tor specifications and code are on a Git repository owned by the Tor project, not at Github. A simple DNS lookup will confirm this: $ dig gitweb.torproject.org ; <<>> DiG 9.8.3-P1 <<>> gitweb.torproject.org […] ;; ANSWER SECTION: gitweb.torproject.org. 3600 IN CNAME vineale.torproject.org. vineale.torproject.org. 3600 IN A 154.35.132.68 - so, any arguments which involve Github (Incorporated) are poorly grounded. Continuing: > There's nothing in 6761 section 5 that demands a reference to a stable > specification. The fact that there's any reference at all is a courtesy. Per my previous e-mail, I would be happy to pluck out specifications, especially if they are blocking progress, because I see their inclusion as irrelevant to the matter of registering the special use domain name. -a — Alec Muffett Security Infrastructure Facebook Engineering London _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
