Andy and all,
Your reference to RFC 2970 is a recent politically motivated revision of the
original that is not being widely accepted presently and has been hotly
debated on various other forums that I am aware of and participate in,
on a few. John Kliensen along with "Harald(a)alvestrand.no"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sun, 17 Jun 2001, T McC wrote:
Please find attached an Open Letter to all ISPs in New Zealand and all users of NZNOG.
This is in no way to be treated as SPAM. It is in response to the many misconceptions and uninformed comments made by ISPs in New Zealand and users of NZNOG as a result of the email I sent to ISPs in New Zealand asking them to adjust their server settings to accept access to the .z extension.
Please read it and if any one has any comments or requires any further information please contact me.
Trevarr,
Let me commend you for your ability to annoy a very large number of the people you would have needed to convince to get your schemes off the ground:
1) You've told them they don't know how to recognize SPAM - I can see in your case that as it's "Specially Prepared Advertising Material" we should read it and be grateful that you've sent it to us. I and many others on this list get sufficiently large amounts of SPAM that our detectors work extremely well.
Someone else used the "looks like a duck..." metaphor for this. I'd probably favour "looks like it, smells like it, I'm glad we didn't walk in it" metaphor.
2) You posted in a proprietary format - MS Word. You immediately reduced your clue rating. Chris Wedgwood translated otherwise I wouldn't have seen your comments.
3) You chose to imply that some of of us are too stupid to understand, too lazy to investigate, work for organisations that haven't been around for very long compared with ADNS (1993)....
In your response to my comments, you say had I (and several others) bothered to investigate ORSC and ADNS ...
This implies that had I done so I would immediately have been bowled over by the technical arguments presented and would have joined the bandwagon that you are pushing.
The DNS nameservers work by having a rooted tree - if I want my servers to include these other namespaces then I have to change my configuration so that it uses an alternative set of roots that happens to include the existing IETF/ICANN official servers or I have to change the software I run.
If I do that I run a risk, it's as simple as that. You've presented some options to me and I don't think the risk is acceptable. This is is not based on discussions on the nznog list over the last few weeks. This is based on 18 years experience using the Internet and in fact predating the introduction of the DNS in 1987.
RFC 2870 - Root Name Server Operational Requirements, June 2000 (ftp://ftp.isi.edu/in-notes/rfc2870.txt) has this to say:
Abstract
As the internet becomes increasingly critical to the world's social and economic infrastructure, attention has rightly focused on the correct, safe, reliable, and secure operation of the internet infrastructure itself. The root domain name servers are seen as a crucial part of that technical infrastructure. The primary focus of this document is to provide guidelines for operation of the root name servers. Other major zone server operators (gTLDs, ccTLDs, major zones) may also find it useful. These guidelines are intended to meet the perceived societal needs without overly prescribing technical details.
1. Background
The resolution of domain names on the internet is critically dependent on the proper, safe, and secure operation of the root domain name servers. Currently, these dozen or so servers are provided and operated by a very competent and trusted group of volunteers. This document does not propose to change that, but merely to provide formal guidelines so that the community understands how and why this is done.
1.1 The Internet Corporation for Assigned Names and Numbers (ICANN) has become responsible for the operation of the root servers. The ICANN has appointed a Root Server System Advisory Committee (RSSAC) to give technical and operational advice to the ICANN board. The ICANN and the RSSAC look to the IETF to provide engineering standards.
Now when there's an RFC from the IETF saying we should rush off to ADNS and put our DNS requests through them, I'll be happy to make the change but until then I've added your name to my email kill filters.
andy
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: Made with pgp4pine 1.76
iD8DBQE7LU6gkNpmQ2ketuURAhmiAKCG8OUhvl8wMMX3OxZnZ6PY64NAoQCfaz1C ARLsZDJzXUKu0tz1NAXCeJM= =4EjF -----END PGP SIGNATURE-----
--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog
Regards, -- Jeffrey A. Williams Spokesman for INEGroup - (Over 118k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Contact Number: 972-447-1800 x1894 or 214-244-4827 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog