-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/22/2015 04:21 PM, Tim Wicinski wrote:
>
> While I understand why you feel 2.6 should contain information about
> user's privacy, it currently seems to meet the requirements for
> [RFC6761].
>
*** I consider important that readers keep the prim
On 6/21/15 8:22 AM, hellekin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/20/2015 03:12 PM, internet-dra...@ietf.org wrote:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-onion-tld/
*** 2.3 has a repeat "either".
That's a good catch. I'll get the authors to fix up.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/20/2015 03:12 PM, internet-dra...@ietf.org wrote:
>
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-onion-tld/
>
*** 2.3 has a repeat "either".
2.6 reads correctly, but the more important reason IMO is the risk of
privacy leak for the use
