dunno why it got send to this address but anyway, i presumed it is suppose to go to the list... james ----- Original Message ----- From: "msquared" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, March 23, 2001 9:21 AM Subject: idn list - something broke > As you can see from the headers of the attached email, something broke > between Måns sending, and me receiving. > > Whether it's Måns' mailer, or the idn list software, I don't know, but I > thought I'd let you know. :-) > > 2 > Regards, /|/| > / | >
<[EMAIL PROTECTED]> Subject: Re: [idn] IDN character repertoire, nameprep Sender: [EMAIL PROTECTED] Precedence: bulk Subject: Re: [idn] IDN character repertoire, nameprep Date: Tue, Mar 20, 2001 at 05:46:44PM -0500 Quoting Mark Welter ([EMAIL PROTECTED]): > > This is a great analogy. Marc Blanchet made the point that registrars don't control > (most) third or lower level names. The question then is, do we want to have the > highway patrol handing out speeding tickets for how fast you are driving in your own > back yard? The related question is whether there should be back-yard speed limit. We should advise them in no uncertain terms. Having spent a year with my hands deep in the day-to-day management of a ccTLD Registry, I have a very dystopic view of the general cluon amount present in DNS server admins. Any lax in advised policies (as in 'anything goes') is a sure fire recipy to meltdown. In the 'old days' people took care to follow rules. Now money has come in play, as we all know. The extra effort to do the right thing is overseen. > I think that zone file administrators can police themselves. If they are > "bad actors" we have other, bigger problems. You are an optimist. :-) I'm thinking about cache poisoning and similar leakage. Compare this with the extreme care the operations people use when setting up mere test beds for IPv6 DNS... -- M�ns Nilsson MN1334-RIPE http://vvv.besserwisser.org UH-OH!! We're out of AUTOMOBILE PARTS and RUBBER GOODS!
