Re: [DNSOP] Problem with CLASS

2015-07-06 Thread Edward Lewis
On 7/6/15, 18:26, "Mark Andrews" wrote: >In message , Edward Lewis writes: >> Content-transfer-encoding: 7bit >> >> (Having quickly scanned through the thread to catch up.) >> >> CLASS has been problematic since the start. The first "mistake" made >>was >> encoding the CLASS field after the OW

Re: [DNSOP] Problem with CLASS

2015-07-06 Thread Mark Andrews
In message , Edward Lewis writes: > Content-transfer-encoding: 7bit > > (Having quickly scanned through the thread to catch up.) > > CLASS has been problematic since the start. The first "mistake" made was > encoding the CLASS field after the OWNER NAME field in a resource record. > This meant

Re: [DNSOP] Problem with CLASS

2015-07-06 Thread manning
agreed. while my buddies and I push rocks around, Ed can make sure the “sleeping[*]” is not wakened. :) * http://www.stuff.co.nz/world/asia/10099510/Dead-guru-just-sleeping-in-a-freezer manning bmann...@karoshi.com PO Box 12317 Marina del Rey, CA 90295 310.322.8102 On 6July2015Monday, at

Re: [DNSOP] Problem with CLASS

2015-07-06 Thread joel jaeggli
On 7/6/15 7:25 AM, manning wrote: > I still need to catch up on the full weekends activity, but I’d like to > suggest that, like the > v4/v6 transition, it may be time to consider revisiting the DNS protocols. > Not that there would > ever be a DNS EMP, wiping our all legacy code, but perhaps a

Re: [DNSOP] Problem with CLASS

2015-07-06 Thread Edward Lewis
Dear Sisyphus[0], +M[1] [0] = https://en.wikipedia.org/wiki/Sisyphus "compelled to roll an immense boulder up a hill, only to watch it roll back down, repeating this action forever" [1] = https://en.wikipedia.org/wiki/Roman_numerals "1000" Yes, the first is Greek, the latter Roman. I can't r

Re: [DNSOP] Problem with CLASS

2015-07-06 Thread manning
I still need to catch up on the full weekends activity, but I’d like to suggest that, like the v4/v6 transition, it may be time to consider revisiting the DNS protocols. Not that there would ever be a DNS EMP, wiping our all legacy code, but perhaps a phased migration to DNSv2 and a shim to en

[DNSOP] Problem with CLASS

2015-07-06 Thread Edward Lewis
(Having quickly scanned through the thread to catch up.) CLASS has been problematic since the start. The first "mistake" made was encoding the CLASS field after the OWNER NAME field in a resource record. This meant that all domain names have to be encoded and treated the same regardless of class,