[ipv6-wg@ripe.net] Re: [dns-wg] IPv6 in .ie
"Daniel" == Daniel Karrenberg <daniel.karrenberg@ripe.net> writes:
Daniel> If I was IANA I would advise .ie strongly to rationalise Daniel> the names in their glue to save space. Yeah. Somebody needs to write up a draft on this as a BCP: using efficient label compression to avoid truncated responses.
On 08 Sep, Jim Reid wrote: | >>>>> "Daniel" == Daniel Karrenberg <daniel.karrenberg@ripe.net> writes: | | Daniel> If I was IANA I would advise .ie strongly to rationalise | Daniel> the names in their glue to save space. | | Yeah. Somebody needs to write up a draft on this as a BCP: using | efficient label compression to avoid truncated responses. ==> In order not to reinvent the wheel, I believe, this humble contribution might be a good start for whom wants to write such a draft. http://w6.nic.fr/dnsv6/resp-size.html#compress-tld-ans Mohsen.
At 9:54 AM +0100 2004-09-08, Jim Reid wrote:
Yeah. Somebody needs to write up a draft on this as a BCP: using efficient label compression to avoid truncated responses.
That's a good idea. Should this be a RIPE BCP, or under IETF? I'll be glad to contribute some of my own personal experiences, if anyone wants to write such a beast. I'd be very interested to see how much supporting evidence could be gathered to explain why this is an important topic. -- Brad Knowles, <brad@stop.mail-abuse.org> "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See <http://www.sage.org/> for more info.
On Wed, Sep 08, 2004 at 09:54:02AM +0100, Jim Reid wrote:
"Daniel" == Daniel Karrenberg <daniel.karrenberg@ripe.net> writes:
Daniel> If I was IANA I would advise .ie strongly to rationalise Daniel> the names in their glue to save space.
Yeah. Somebody needs to write up a draft on this as a BCP: using efficient label compression to avoid truncated responses.
you mean the resp-size draft that is already out there is not good enough? --bill
"Bill" == bmanning <bmanning@vacation.karoshi.com> writes:
Daniel> the names in their glue to save space. >> Yeah. Somebody needs to write up a draft on this as a BCP: >> using efficient label compression to avoid truncated responses. Bill> you mean the resp-size draft that is already out there Bill> is not good enough? I thought that had died.....
On Wed, 08 Sep 2004 17:38:20 +0100 Jim Reid <jim@rfc1035.com> wrote:
"Bill" == bmanning <bmanning@vacation.karoshi.com> writes:
Daniel> the names in their glue to save space. >> Yeah. Somebody needs to write up a draft on this as a BCP: >> using efficient label compression to avoid truncated responses.
Bill> you mean the resp-size draft that is already out there Bill> is not good enough?
I thought that had died.....
For your information and reference: resp-size is at: http://www.ietf.org/internet-drafts/draft-ietf-dnsop-respsize-01.txt A common parent name is recommended in the resp-size draft: 4.1. The current practice of giving all nameserver names a common parent (such as GTLD-SERVERS.NET or ROOT-SERVERS.NET) saves space in DNS responses and allows for more nameservers to be enumerated than would otherwise be possible. (Note that in this case it is wise to serve the common parent domain's zone from the same servers that are named within it, in order to limit external dependencies when all your eggs are in a single basket.) The document is not dead, it came up in the DNSOP meeting at IETF60 in San Diego. http://darkwing.uoregon.edu/~llynch/dnsop/msg03041.html Rob Austein: Paul, want to say anything about respsize doc? Paul Vixie: I know that one person actually read this and found clownish commentary I put in draft. Nobody flamed me. There is a very controversial comment in this draft. Peter Koch: Have one question or remark. We had funny discussion about what is allowed length for domain name. 255, 256, 253. It'. a bit late now to discuss this because this is very basic DNS stuff. Nothing to do with your draft, but obviously some basic questions yet unresolved. Anything we can do in this or another WG to resolve this? (Peters question sidetracked the discussion somewhat ... I skip that here... ) Paul Vixie: In terms of process, I do not think this draft is ready to progress, because no-one complained. So until I have some feeling that someone other than me has seen this text, I will say it's not ready to go forward. Rob Austein: So given that we had a number of people claiming this was important work, suggests that there is some work to be done in terms of reading doc that hasn't happened yet. You're all slackers. Go read the document! -- ---------------------------------| Olaf M. Kolkman ---------------------------------| RIPE NCC
participants (5)
-
bmanning＠vacation.karoshi.com -
Brad Knowles -
Jim Reid -
Mohsen Souissi -
Olaf M. Kolkman