Come on, GitHub is a corporation, it has NOTHING to do with it.  Git is
a version control system.  An RFC falls to me exactly in the definition
of "the most current version of foo".  When something needs to be
amended, it is: that's what erratas and RFC updates and obsolescence are
for.  Please leave the strawman alone.


Hi Hellekin!

I am pretty sure that what was meant was something like:

As a Git Repository Page Hyperlink Within The Tor Project’s Website, they are 
simply "the most current version of The Onion Specification".

…and as I think that it is pretty obvious that that is what was meant, I 
therefore really fear that your reaction may be perceived as unconstructive.

Let’s fix that. :-)


Being, as I am, an IETF newbie, this does not strike me as a terrible problem, 
but clearly there is an issue here which animates several people, therefore it 
must be something important.

The references to “normative” and “downref” appear to be related to 
https://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry and seems 
related to a desire to “freeze” the reason / address resolution specification 
for which the onion registration is being pursued.

Joel: please correct me if I have misapprehended this?

The thing is, I don’t think that “freezing” the address resolution 
specification for which the onion registration is being pursued, would be 
beneficial in the long term.

The onion names will be compliant with DNS syntax - that will be an invariant.

Their internal structure will evolve over the next few years, and importantly 
so, because security and software change at internet speeds.

The important thing is that:

1) “.onion” exists, and that
2) underneath it, resolution is in the hands of the current Tor software, and 
that
3) none of the above make the DNS barf.


Perhaps the solution is to somehow remove the tor address-resolution 
specification footnotes entirely?

    - alec




> What the onion folks said to me was that they were working on
> creating stable, referenceable documents that explained how
> this should work.  I understand there is a time problem due to the
> certificate.  As a reviewer, I don't see how you can register
> without a stable reference for the meaning of the registration.
>

The referenced Tor documentation does not affect the reservation because
changes in that documentation won't affect the principles set forth in
the relation between Tor and DNS.  These are orthogonal matters.

==
hk


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to