- NZNOG - lists.nznog.org

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

Petition for .nz registry WHOIS server
by 2Day Operations 11 Oct '99

11 Oct '99

Thanks to those folk who took the time to complete a petition and send it on to us. I have today couriered them to the secretary of ISOCNZ. Lets see if we can get a WHOIS server in place before their new Internet foundation gets all the millions in profit from DOMAINZ. Peter Mott Chief Enthusiast 2DAY INTERNET LIMITED -/- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Looking for Web servers to ping - network research
by Joerg Micheel 07 Oct '99

07 Oct '99

Dear NZnoggers, there are currently some research projects going on which try to measure the health and state of the Internet on a global and local scale. University of Waikato Computer Science is hosting a skitter server for CAIDA, the UCSD-based Internet Research Corporation. The skitter project involves pinging (ICMP traffic) a larger number of "interesting" hosts on the Internet and drawing some conclusions about reachability, network load, performance etc. These people are expanding their scope and would like to find new destinations they could ping on a regular basis. Web servers are of high interest. If you are a network administrator, web administrator etc, who is willing to support such research (and potentially receive valuable information from active network measurements), please get back to me as soon as possible. Thank you for your time. Joerg Micheel ----- Forwarded message from Tracie Monk <tmonk(a)caida.org> ----- We might add that for these measurements, web server are preferred targets. Please do not include any routers or workstations in your lists of additions to the destination lists. We will add everyone's additions next week, then distribute a new dataset soon after. Thanks for your help. Tracie Dear Skitter-Asia Collaborators, We have now collected sufficient data using our initial Skitter destination list that we can now entertain making additions to the list. If you have a suggestions please provide us with the destination host name and IP address. We would prefer candidates with diverse characteristics. For example, we prefer to have examples from commercial, education, non-profit, network, and government sectors. Also destinations from different geographical locations are of interest. Typically we monitor only one host per domain name (i.e. caida.org, san.rr.com,) but exceptions are made for interesting destinations. Please send your suggestions to me along with any additional information you can provide. Peace, Edouard -------------------- Edouard Lagache, PhD elagache(a)caida.org phone (858) 534-5045 fax (858) 822-0861 ----- End forwarded message ----- -- Joerg B. Micheel Email: <joerg(a)cs.waikato.ac.nz> Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, SCMS Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

The New Zealand Network Operators' Group
by Donald Neal 07 Oct '99

07 Oct '99

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has neither a king, a president nor a formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. (At last count the list had a little over one hundred subscribers, with the count growing slightly each month.) The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by an employee of Telecom NZ Ltd. Neither of these organisations (nor the administrator) is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/archives/nznog/ To search the archive, see http://list.waikato.ac.nz/archives/search.html (and remember to select nznog). Subscribing to the List To subscribe to the NZNOG list, send email to majordomo(a)list.waikato.ac.nz, where the body of the message reads subscribe nznog There are at present no restrictions on who may subscribe to the list, or even on who may post to the list. Digest Mailing List If you don't wish to receive postings as they are sent, you can instead subscribe to the nznog-digest mailiing list, on which all postings are sent out in a single "digest" every couple of days. Other Activities NZNOG does not at present have other regular activities than this mailing list, though some Auckland subscribers have been known to meet over beer. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

singlemode/multimode media converters
by Joe Abley 06 Oct '99

06 Oct '99

Noggers, Anybody have any good ideas where I can get my hands on two singlemode/ multimode converters, suitable for clocking at 155M with ATM? SDH framing, if that makes a difference. Needed in Auckland pretty urgently... Any pointers appreciated. Preferred SC connectors on the multimode side, ST on the singlemode. 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

SunOS 4.1.3
by Chris Wedgwood 04 Oct '99

04 Oct '99

Can anyone tell me where the localtime/zoneinfo file for the current timezone should reside on a SunOS 4.1.3 box? I have one that is so horrible crippled right now, I can't think of any good way to find out... -cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

whois.patho.gen.nz now working again
by Joe Abley 02 Oct '99

02 Oct '99

Hi, Just in case anybody missed it :) whois.patho.gen.nz is now reporting correctly again, pulling registration info from http://domainz.waikato.ac.nz/cgi-bin/DNZ-REGISTER. The extended breakage wasn't due to any re-formatting of the data returned by that script at waikato, incidentally; it was entirely due to the fact that the little awk script which drives whois.patho.gen.nz was using character class extensions which are specified in POSIX 1003.2, and implemented in gawk, but sadly misinterpreted by whatever awk OpenBSD installs in /usr/bin. Well, actually the extended-ness of the breakage was more to do with the fact that I wasn't bored enough to look at it until now. nz.whois-servers.net is a CNAME for tardis.patho.gen.nz, which is nice of them. Note that this is a highly non-production system, and is most definitely not what Peter needs to run his business :) 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