Re: (in)Security Analysis and Catastrophically bad Design:
Christopher Chan <[email protected]>
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
>>>> It seems to me that arguing against messaging opacity only makes >>>> sense from a position with desire to monitor passing messages. > >>>> Privacy concerns -- what dns i look up should be between me and my >>>> selected recursive resolver, and not information available to anyone >>>> with access to the intervening wires -- seem absent from the >>>> discussion. > > This is sad and true. > > According to my understanding: > > a) DNS RR are public. > b) However MY Queries and the Answers I receive from either the Content > Server or the Cache Server SHOULD not be public and available to everybody. > c) Google's IETF draft > <http://www.ietf.org/id/draft-vandergaast-edns-client-ip-00.txt> > would even make this situation worse. > > Protecting 'private' DNS communication is legitime and a matter of > "netneutrality" <http://lessig.org/blog/netneutrality/>. All bow before the data mining overlords! Or is it Big Brother?