Hi, Christian, On Sep 3, 2015 01:14, "Christian Grothoff" <groth...@gnunet.org> wrote: > > On 09/03/2015 04:54 AM, Spencer Dawkins wrote: > > I thought .onion was tied closely to the TOR protocol, so I have no idea > > why the second sentence in this paragraph is here, or what it means, and > > neither the string "TOR" nor the string "onion" appear in RFC 7230, so > > chasing that reference didn't help. > > > > Like Top-Level Domain Names, .onion addresses can have an arbitrary > > number of subdomain components. This information is not meaningful > > to the Tor protocol, but can be used in application protocols like > > HTTP [RFC7230]. > > > > Am I just being dense the night before a telechat, and everyone else > > understands what this means and why it needs to be included in this > > document? > > > > If this isn't clear to other people, could you either say more about what > > it means, or delete the second sentence? > > > > I'm not confused about the first sentence, only the second ... > > Spencer, let me explain in 2 sentences ;-).
Thank you for the speedy clarification! > The Tor (router) ignores > 'foo' in foo.KEYHASH.onion for the name lookup. However, the Tor > browser sends 'foo.KEYHASH.onion' to the HTTP server as part of the > "Host:" header, so the server may act differently for > 'foo.KEYHASH.onion' than for 'bar.KEYHASH.onion'. (This feature is > typically used for "virtual" HTTP hosts where multiple servers share one > IPv4 address.) Those are two pretty great sentences! Could that thought make it into the document? It helped a lot ... Spencer
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
