- NZNOG - lists.nznog.org

Connections to APE (plus changes)
by Richard Naylor 01 Nov '99

01 Nov '99

In the next week or so the 2 switches at APE will be replaced with a more capable Cisco switch, through the generosity of Cisco NZ. While this is taking place there will be a smal outage on the APE switch. Users will notice an outage of less than 1 minute while the new switch learns mac addresses etc. At the same time, cablers will be on site and available to connect up any parties interested in joining the exchange. Prospective users whose external connectivity has yet to arrive, can still be connected while the cabling is taking place - its easier for the installers to pull a bundle at one time. If you are interested in having cable put in place for a future connection, please contact me in the next week. thanks - rich richard.naylor(a)citylink.co.nz This mail message contains information that is confidential and which may be subject to legal privilege. If you are not the intended recipient, you must not use, distribute or copy this message. If you have received this message in error, please notify the sender immediately and erase this mail. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

web page with APE stuff on it
by Joe Abley 01 Nov '99

01 Nov '99

I thought it might be good to have some info about APE on a web page somewhere. So I threw this together: http://www.patho.gen.nz/ape/ It almost certainly contains at least _some_ lies; please let me know what they are (or, if you don't care, I'll just carry on spreading them :) Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 4

WHOIS/Zone Transfer Policy
by John Vorstermans 26 Oct '99

26 Oct '99

Hi. The revised draft of the WHOIS and Zone Transfer policies are now available at: http://www.isocnz.org.nz/whoisdraft231099.html http://www.isocnz.org.nz/zfdraft231099.html Any comment or feedback are welcome. The earlier drafts are still available at: http://www.isocnz.org.nz/zfdraft1099.html http://www.isocnz.org.nz/whoisdraft1099.html Regards John Vorstermans Technical Committee ISOCNZ -- John Vorstermans || We are what we repeatedly do. Technical Manager || - Aristotle Actrix Networks --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

rata.vuw.ac.nz outage
by Richard Stevenson 23 Oct '99

23 Oct '99

Hi all I figured that you may all want to know that rata.vuw.ac.nz, one of the secondary nameservers for the nz ccTLD, will be out of service for an undetermined period of time tomorrow evening (Saturday 23 October 1999). As part of our Y2K preparations, management here has decided that all of our core systems should be shut down, powered off, left to cool, and then restarted, to see what breaks. This will all happen tomorrow night. The shutdown and startup procedures will be carried out by unqualified staff (i.e. not even Unix-literate) as an experiment in system documentation standards. I hope to see you all on the other side. Regards Richard ------------------------------------------------------------------------------ Richard Stevenson Systems Engineer, Information Technology Services Victoria University of Wellington Phone: +64 4 4635051 Fax: +64 4 4635552 Being a Unix system administrator is like being a tech in a biological warfare laboratory, except that none of the substances are labeled consistently, any of the compounds are just as likely to kill you by themselves as they are when mixed with one another, and it is never clear what distinction is made between a catastrophic failure in the lab and a successful test in the field. (--M. Tiemann) ------------------------------------------------------------------------------ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

Re: rata.vuw.ac.nz outage
by Mark Davies 21 Oct '99

21 Oct '99

From: Joe Abley <jabley(a)patho.gen.nz> Date: Fri, 22 Oct 1999 16:41:35 +1300 > Nice to have some warning on this. However, 24 hours is a little > slim for an event that will take out 1/6 of all recursive lookups > on nz names "for an undetermined period", isn't it? Well I would have given you more warning but when I first heard they were going to do this and queried it I misread the answer they gave me to say that rata wouldn't be included so Richards message was a little surprise to me as well. Rata is intended to be the last machine down and the first up so hopefully the disruption should be quite short. mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: [ISOCNZ-L] Re: zdraft1099.html (DRAFT ISOCNZ Zone Transfer P
by Mark Harris 18 Oct '99

18 Oct '99

Joe, Not to steal his thunder, but John V. has indicated to the Council that he had received some good feedback from the lists and email which is going to require a redraft of both policies to include some of the suggestions and rewordings. He also said that the Technical Committee is meeting later this week to consider these changes and he hopes to have something final after that. We don't want this to go on forever, so I imagine RSN :-) Cheers Mark > -----Original Message----- > From: Joe Abley [SMTP:jabley(a)patho.gen.nz] > Sent: Tuesday, October 19, 1999 9:44 AM > To: nznog(a)list.waikato.ac.nz; isocnz-l(a)isocnz.org.nz > Subject: Re: [ISOCNZ-L] Re: zdraft1099.html (DRAFT ISOCNZ Zone > Transfer P > > It seems that a reasonable amount of feedback has been provided now... > When can we expect revised draft policies to be made available? > > > Joe > > - > To subscribe/unsubscribe to the isocnz-l mailing list send a message > to majordomo(a)isocnz.org.nz with the keyword subscribe or unsubscribe > as the message plus the list name i.e. unsubscribe isocnz-l --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

zdraft1099.html (DRAFT ISOCNZ Zone Transfer Policy)
by Joe Abley 18 Oct '99

18 Oct '99

John, Some feedback for you. Background A primary name server is a name server that gets the data for its zones from local files. Changes to a zone, such as adding domains or hosts, are done at the Primary Name Server. A secondary name server gets the data for its zones from another name server across the network which is authoritative for that zone. The processes of obtaining this zone information (that is the database file) across the network is referred to as a zone transfer. Since bind 8 I believe the nomenclature that has been widely adopted is a "master" nameserver (corresponding to a master zone configured on that host) and multiple "slave" nameservers which keep their copies of the zone up-to-date using zone transfers. Probably makes sense to make use of the current terminology. Zone Transfers will be allowed provided: [...] I think that there are numerous reasons to perform a zone transfer which are not covered here, which would be consistent with the privacy act provision in point 2. It seems to me that the list is unnecessarily restrictive in presuming to know all the reasons an operator might have for performing a zone transfer. I also think that there is nothing wrong with statistics gathering. Understanding trends makes the network a safer place. I do not understand your earlier point that data for statistical analysis would be available on the web, but not by zone transfer... Perhaps I misunderstood it. I would rephrase point (3) to be something like: that it is not for the purpose of allowing, enabling or otherwise supporting the transmission of mass unsolicitited, commercial advertising or solicitatious e-mail. I would also make point (4) a little more general, and allow zone transfers to facilitate "operational network engineering". Is it reasonable for a request not to contain a detailed description of the reason for wanting to perform a zone transfer? What is a reasonable request? Is the idea of this policy to be prepared in the event that a flagrant misuse of the zone data occurs? If so, I think it's a good idea. If the idea is to implement an immediate set of restrictions on zone transfers, and to administer zone transfer access control (including all associated adds, moves and changes) for all secondary nameservers, then I remain slightly dubious :) Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 12

Draft WHOIS and Zone Transfer Policies
by John Vorstermans 16 Oct '99

16 Oct '99

Greetings. The ISOCNZ Technical Committee has prepared two draft policies. 1. Directing Domainz to implement a WHOIS server. http://www.isocnz.org.nz/whoisdraft1099.html 2. A policy on Zone Transfers. http://www.isocnz.org.nz/zfdraft1099.html I hope to be able to ask the council to vote on these next week. Any comments or submissions to these draft proposals would of course be most welcome. If you wish to make a submission please email to john(a)actrix.co.nz These drafts have also been sent to the ISOCNZ members mailing list for comment. Regards John -- John Vorstermans || We are what we repeatedly do. Technical Manager || - Aristotle Actrix Networks --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

10 21

Re: whoisdraft1099.html (DRAFT WHOIS SERVER POLICY)
by Joe Abley 15 Oct '99

15 Oct '99

John, More feedback, different draft. An WHOIS server is the Internet Standard way of access details from, in our case, the .nz database. "a" whois server, surely :) * It is a separate service. Separate from what? * It is currently provided by all major Name Service organisations, e.g. Ripe and APNIC etc. RIPE and APNIC aren't actually name service organisations; they're regional registries for ASN and IP number allocations. You might use CRSNIC, NSI, Nominet, etc if you're looking for examples of registries' and registrars' use of whois. WHOIS Policy * That NZIRL be required to put in place a standard WHOIS server on the .nz database. What needs to be carefully specified is the formatting of queries and responses to the whois service. There are a number of different "standard" query definitions and response formats currently in use amongst different registries. It would make sense for Domainz/ISOCNZ to approach the heavier users of their existing services and consult as to the query and response formats that are required. The Data in ISOCNZ WHOIS database is provided by NZIRL for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. NZIRL does not guarantee its accuracy. NIRL should guarantee that the response returned to a query is consistent with the data stored by Domainz at the time of the query. (2) enable high volume, automated, electronic processes that apply to NZIRL (or its systems). I'm not sure what this means. What does it mean? ISOCNZ reserves the right to modify these terms at any time. I would imagine that you should qualify this by specifying how changes to the policy will be notified to users of the whois service. You might also refer to RFC812, which specifies nicname/whois. It's a little old (it refers to NCP/TCP!) but the core protocol is described there, such as it is. Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: [ISOCNZ-Members] Draft WHOIS Policy
by David Harpham 15 Oct '99

15 Oct '99

ISOCNZ technical committee, Thanks very much for the opportunity to comment (and hopefully influence) the Zone transfer and Whois policies, *before having the council vote on them.* DRAFT ZONE TRANSFER POLICY (http://www.isocnz.org.nz/zfdraft1099.html) ========================================================== Great to see that "No reasonable request shall be refused." A/ In item 3. it explicitly lists "simply for the gathering of statistical analysis" as being undesirable. Surely we can remove this phrase. The no spam bit I endorse but no statistics is a bit closed shop isn't it.? B/ In item 3 it provides for 'private name' servers. What is the objection to (shadow) public but non authoritative name servers. Surely these are OK in an open environment.? An ISP may want to improve response times for it's customers and help unload the official authoritative name servers, this would help robustness with perhaps a greater diversity of machines and operators. If it is OK for Auckland University then why not an ISP? DRAFT WHOIS POLICY (http://www.isocnz.org.nz/whoisdraft1099.html) ==================================================== Starts off well pointing out the expectation that "It is used generally by system administrators." A/ Surely to be useful for an ISP administrator, the ISP needs to be able to be sure that it is the current authoritative contents of the official database but instead we have "NZIRL does not guarantee its accuracy". Also I do not believe that ISOCNZ policy should include a disclaimer on behalf of NZIRL, I think people need to be clear which hat is being worn when they write this. B/ Surely to be useful to ISP administrators, one of the major differences in using a Whois instead of a web page is that it *CAN* be used for efficient automated definitive lookups etc. Why specifically ""under no circumstances will you use this Data to ...enable high volume, automated, electronic processes ", I thought that was largely what the objective was. OVERALL ========= If we make the above changes (open statistics gathering, open shadow name servers, accuracy of whois with efficient automation) we might allow for ISP's wanting to provide equivalent or alternative services to the registry in an efficient manor, without them it looks very centralist. Cheers David Harpham david(a)harpham.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1