You know Nicholas, if you've got time to respond to the next best thing [DNSOP] and [DNSEXT] have to a troll, we still need a replacement mechanism for registering EDNS0 types. :)
For you curmudgeons like me, remember to "Meta-x auto-fill-mode" before you read this note. o.b.DNS: If I use both SPF and DKIM, do I get SPDIF for better DNS surround sound? -Alex (Note: I don't know, and I don't care, if 'taka does it intentionally. Just a trend I've noticed. This is all just my completely subjective opinion, and should be disregarded as such.) -----Original Message----- From: dnsop-boun...@ietf.org [mailto:dnsop-boun...@ietf.org] On Behalf Of Nicholas Weaver Sent: Thursday, September 29, 2011 1:13 PM To: Masataka Ohta Cc: Paul Vixie; dnsop@ietf.org; Nicholas Weaver Subject: Re: [DNSOP] A new appoarch for identifying anycast name server instance Note: The following is manually formatted because you are incapable of using a modern mail reader OR have deliberately misconfigured your modern mail reader OR are reading the message using a buggy archive: On Sep 29, 2011, at 9:34 AM, Masataka Ohta wrote: > Nicholas Weaver wrote: > >> I think you're missing something subtle here, both in this comment and in >> the "Do it in IP layer" comment. > > I'm afraid it's you. > >> This proposal allows debuging information about the "recursive > resolver TO anycast authority" path, a path which the user AND anycast > operator do not otherwise have direct access to. > > As for subtlety, what if, the information is cached and stale? Good point, but there are easy solutions: a: Do you honestly expect these queries to be common enough to be cached? b: These should have a TTL of 0 seconds and/or support a prepended, cache-busting wildcard. > OTOH, identification by ICMP is up to date save RTT. How can one generate an ICMP on the path from the resolver's outbound interface to to the authority, and receive the response, without access to the resolver? Please tell me how to do so, in a way that is expected to work, so I can use this in automating some significant problem solving. > I skipped to read rest of your mail, because you have not learned > to wrap lines properly. Your inability to use a modern mail client is NOT MY PROBLEM! Let me reiterate, manually formatted to please you: That your mail reader can't word wrap properly on received messages is not my problem. Word wrapping MUST be done on the recipient side, not on the sender side, unless you want to maintain ridiculous conventions like "text lines are at most 72 characters, monospaced" which were obsolete two decades ago. And in this case particular case, blame Microsoft. Apple on their mailer for the longest time implemented a standard method, format=flowed, intended to please BOTH mail readers that can word-wrap and mail readers that can't. But they dropped this way back in 10.6.2, because Microsoft never recognized it right. Given the choice between pleasing a few recipients who cling to an obsolete convention with obsolete tools and pleasing the very large population of recipients with a tool unwilling to accept a standard which could please both, Apple went with the natural choice: it is the mail reader's responsibility to word wrap to the reader's own display parameters. As an addition, your headers suggest you are using Thunderbird. I checked Thunderbird 6 on OS-X this morning, it word wraps unstructured text flawlessly. Please ensure that you haven't mistakenly turned on a mis-formatting "feature". If you are complaining because a particular web mail archive you are using are not formatting properly, it is a bug in the archive generation tool's HTML formatting, and should be reported as such. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
