Re: [tor-dev] Prop279 and DNS

[Jeremy Rand <jeremyrand@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hugo Landau:
> After giving it some thought, I think Tor should use a
> Tor-specific protocol to interface with name plugins, not DNS.
> 
> My reasoning is as follows: the Tor daemon knows what it wants and
> is designed to source specific data from a name plugin. Where Tor
> specifies a custom protocol for this, this will match perfectly the
> type of queries and type of responses which Tor needs to ultimately
> obtain and convert to some corresponding internal in-memory
> representation.
> 
> As such, forcing this made-for-Tor format to be marshalled into a 
> pre-existing format, namely that of DNS queries and responses, can
> only ever reduce the power and flexibility of the plugin interface.
> It only creates the potential for impedence discontinuities, and
> also creates a substantial nuisance and implementation barrier for
> plugins which are intended only for use with the Tor daemon. These
> plugins would need to source a DNS packet marshalling/unmarshalling
> library, which creates an unnecessary barrier to implementation,
> and both sides of the interface would be marshalling into a format
> which isn't especially aligned with the internal representations
> they'd ideally like to be speaking. As such, using DNS here feels
> rather pointless.
> 
> Looking at the Prop279 proposal as it stands, it would be trivial
> for a plugin that wants to work with DNS packets to convert a query
> to a DNS packet. As such, I see very little utility to adopting the
> DNS format for this.

Thanks Hugo.  Yeah, I think you're probably right.  In Namecoin's
case, it *may* make sense to have a Prop279 provider implementation
that uses DNS to talk to Namecoin software, but the difficulty of
doing stream isolation properly with DNS and the rather large set of
DNS features that have no relevance to many Prop279 providers suggest
that it's unwise to force that coupling.

Cheers,
- -- 
- -Jeremy Rand
Lead Application Engineer at Namecoin
Mobile email: jeremyrandmobile@xxxxxxxxxx
Mobile OpenPGP: 2158 0643 C13B B40F B0FD 5854 B007 A32D AB44 3D9C
Send non-security-critical things to my Mobile with OpenPGP.
Please don't send me unencrypted messages.
My business email jeremy@xxxxxxxxxxx is having technical issues at the
moment.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJZBDotAAoJELPy0WV4bWVwyCgQAIinmd5pBqf86vq4ae2N9KwX
/IFstwBZFuD7QSzBeFyQI1n+tP76OHM7dSpPPvZZfz8ksuTLwjdYJBkSDMGoiWzS
KjAFcFK4VBCmPhkq6nd97nqSYXiqlyoZMKCAwE6Yxg4YV6a0mLnfkNYdIpRwXgXa
EkL75FxsYFFWPztLBa63vZlJcuxfJ4lBtZDdhiRunnQh+KXwHmA2fukc8yqxs5lF
tnE2Mzb06bI3KYmcjmpi+Zb0u2QYNtnY5jPTN5LNu4XeOcpvKieHpqEDHTBVzArR
3zXpmvmvWlPcT6KzWp4kaNM+f76Q/uXbetVfyPPPUlxR3fKbRGjJ9owpGpcR/Nhb
YnpG0jSZXKu5j+zN9mXM+SB+lBVqOGwwF5ae2oIRe6H0gG53il7jv3gQCSh/EZO7
9harqftv9LqfKtPZpRjzIWGv2DSriy2wPJsKwsL1o3c/DrEbnbbh/cEIs+RMlijF
fjP2daO9DVKnAClB8YcZw0cgWc4xZ5EcZnF0FPsV4ZWREgG1UIzUm+fV04HPruYB
k5OX5T4HdNSU0lJJY7H4P6VHbpr3i73PnDBJsUvOM2cFQattxGCMxGzF5pDp+wIC
R2dFLASWtiQOL4alyqUxP9aoR7DJcvYm7jThe1aNjyyN880wbYCJnUYEoQa0k10t
DBAecAT+HDKuZt7WklMm
=84wv
-----END PGP SIGNATURE-----
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev