-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 05/12/2015 04:18 AM, Alec Muffett wrote:
>> On May 12, 2015, at 7:44 AM, hellekin <helle...@gnu.org> wrote:
>>
>> *** So in my understanding of the scope boundaries of RFC6761 IANA
>> considerations, which seems to be the main difference between our
>> drafts and our respective positions, the former is "an application",
>> while the latter bundles "an application" and "a name resolution API
>> or library".
>
> Being a SOCKS-based service, of course, any SOCKS-enabled client can
> talk to Onion-space; including SSH, for instance.
>
*** I'm sorry Alec, but I don't understand the meaning of your response.
On the one hand you seem to agree ("of course"), but on the other hand
you seem to talk about something different.
Let's see. "Naked firefox" is one case. The TBB is another. SSH is
yet another. All three match the "application" case. But only the TBB
comes with a built-in Tor resolver (and matches the "name resolution API
or library" case.) Do you agree with that interpretation?
==
hk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQJ8BAEBCgBmBQJVUezHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0
ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9RcIQAJhwbgNCL9WFcMb7IohlMy07
1dWrMkFjYFBVpCU05LslPVaqY7+XhKcAp1F8tJmNE9QJSyC1+ngozN5n1U1NZ79d
L3Nq/ocKFpVjtaHUq4WbxyuUlJ7u0mSou2HWtFqCchDb5Ps8GuUpiqTwLe4Q2H5L
5ss5vveeB2fTF8J+ErbmbGrgBxWlDfZrGxH2uD69Q/cWjfbdCg3hRJCaS2yWb/Xn
9eDd6C7odt30xNEMfHtr7kzqxAQL8g73fBO2U3Cq1kEZb8brTabByv+soc9MbS10
jlfQlrl1UH7dxbbai7OQYRFqIyl9gAB7LHTy1WB4mk5LG1xbuvqfOzrtlNDk+kmr
WeVz48F8Gliyuf7cOwG1BarnYkk/heAIDLETqN6eMqhLqJ5c5DTfA5Z/TgULncWf
AIa1Mt1k66mz/Gxfqxzcv9GG6IxmnCHmIJeCpoXCp0cvqOjNzdySWbtnABkCKBSK
HptGysbY4l6PWPkIFCGAJZ15lcwO40E4pFfX5iefWitiUZLY0HwJ+2yVCWvzgNC9
JDYnVSsDf0d5EV7bvMG/UwMqZ92O83krYrCUJLfQUbBB6foZialTKV8b2LgLqd7B
DLkfhPZ/CYlvbUZLR2M3nUxx/JQVXscUF88hk+9txQh2kHpm0EMiydM2jP+I84hu
y7pO9+YLniBiYAqnwpwv
=gPmw
-----END PGP SIGNATURE-----
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
