- NZNOG - lists.nznog.org

RE: limiting smtp message size
by Olof Olsson 25 Feb '99

25 Feb '99

> > As Joe says we have a 10Mb limit - we also have a 15Mb limit on the > > mailbox size. > > What do you do when the mailbox exceeds this size, fail all new > messages, or defer them? > > We bounce them, with the bounce-message saying that the customer's mailbox is full. --Olof -- Olof Olsson <oolsson(a)clear.co.nz>, System Architect, CLEAR Net CLEAR Communications Ltd, Private Bag 92143, Auckland, New Zealand --------- 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: limiting smtp message size
by Bob Baal 25 Feb '99

25 Feb '99

At 13:34 26/02/99 +1300, Chris Wedgwood wrote: >On Tue, Feb 23, 1999 at 08:34:55PM +1300, 2Day Chief Enthusiast wrote: > >> Does anybody here limit size of smtp e-mail messages accepted by >> mail exchange and if so, what max size (including attachments)? > >> I have a customer who thinks that we were being unreasonable for >> rejecting a 20Mb email :-) > >20MB isn't unreasonable IMO... most people have limits far below this >(as others have replied) > Since Peter asked the question I have been snooping around and found that quite a few US ISP's operate with 3-5 Meg Limitations. I am feeling very generous now. Bob CLEAR Net =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bob Baal CLEAR Net Email: rbaal(a)clear.net.nz =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- --------- 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: limiting smtp message size
by Joe Abley 25 Feb '99

25 Feb '99

As Joe says we have a 10Mb limit - we also have a 15Mb limit on the mailbox size. I had a complaint about being unable to pass a 50Mb file a couple of days ago! Bob CLEAR Net Ops. On Tue, Feb 23, 1999 at 08:34:55PM +1300, 2Day Chief Enthusiast wrote: > Does anybody here limit size of smtp e-mail messages accepted by mail > exchange and if so, what max size (including attachments)? > > I have a customer who thinks that we were being unreasonable for rejecting a > 20Mb email :-) !We have a 10Mbyte limit for customer mail (and a 5Mbyte limit for mail !to clear.co.nz). !Tell your customer "man split" :) Joe --------- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

limiting smtp message size
by 2Day Chief Enthusiast 25 Feb '99

25 Feb '99

Does anybody here limit size of smtp e-mail messages accepted by mail exchange and if so, what max size (including attachments)? I have a customer who thinks that we were being unreasonable for rejecting a 20Mb email :-) regards Peter Mott Chief Enthusiast 2Day Internet Limited http://www.2day.net.nz -/- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

FW: INET'99 Network Training Workshop
by Barry Raveendran Greene 23 Feb '99

23 Feb '99

[FYI - Please pass along to those individuals, institutions, and ISPs would could use the this specialized training.] -----Original Message----- From: Carla Rosenfeld [mailto:carla(a)isoc.org] Sent: Tuesday, February 23, 1999 9:34 AM To: ALAN(a)VM1.MCGILL.CA Cc: carla(a)isoc.org Subject: INET'99 Network Training Workshop Dear Friends- Please forgive the delay in sending a copy of the 1999 Network Training Workshop announcement and application. There are only two more weeks until the deadline. We would appreciate it if you could distribute this to the appropriate individuals as soon as possible. Thank you for your help and support of this valuable program for countries in the early stages of internetworking. Regards, Carla Rosenfeld Manager of Conferences Internet Society ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ INTERNET SOCIETY 1999 Network Training Workshop For Countries in the Early Stages of Internetworking ~ 13-20 June 1999 ~ NOTE: To help ensure the largest possible pool of qualified applicants, recipients of this e-mail message are encouraged to re-distribute, wherever appropriate, this announcement and application, in its entirety, among developing country professionals and those working with development issues in developing countries. For a copy of this announcement, including the application, send e-mail to Workshop-Apply(a)ISOC.ORG. Professionals from around the world will be taught the design, operation, maintenance and management of Internetworks when they attend the Internet Society's (ISOC) 7th Network Training Workshop for Countries in the Early Stages of Internetworking, 13-20 June 1999. More than 1100 previous graduates have performed a vital role in setting up the Internet connections and networks in virtually every country that has connected to the Internet during the past six years. A new cadre of networking professionals will again be taught the technical and operational aspects of establishing and managing their national network infrastructure. The focus of the workshop is to assist countries that are either not yet connected to the Internet or are in the process of developing and enhancing an initial national Internet. For all participants, attendance at the workshop includes attendance at INET'99. Workshop participants will be able to attend the K-12 Workshop or the Developing Countries Networking Symposium, scheduled 21-22 June 1999, at no charge if they pre-register. The workshops are an outgrowth of and build upon the experiences of six similar workshops held during 1993-1998 at Stanford University, U.S.A., Czech Technical University in Prague, Czech Republic, University of Hawaii, U.S.A., McGill University, Montreal, Canada, Petronas Training Center, Kuala Lumpur, Malaysia and Cité Universitaire, Geneva, Switzerland. GOALS The goals of the workshops are: 1.To train a critical mass of trainer/professionals in network infrastructure, transport, services, and management to be able to support an extension of meaningful Internet-related activities within the countries represented. 2.To identify and share individual and institutional contacts as well as information sources that will assist the process of national development, using international Internet connections. 3.To build robust professional linkages between all participants in the programs so that the mentor-student and colleague-colleague relationships formed during the workshop and conferences will remain strong and of continuing usefulness well beyond the workshop and conference. 4.To increase the level of cooperation among existing projects and activities for establishing public data networks in developing countries. 5.To train people and groups of people who will return to their country and region and who will teach others what they have learned at the workshop. PROGRAM An intensive program of instruction is planned for the workshop, composed of four instructional tracks. Participants attend only one of the four tracks, since the tracks run concurrently. All participants (except those in the National Network Management track) will engage in extensive hands-on training, either setting up a prototype network or using actual Internet resources or both, as appropriate, using the Workshop facilities . The course descriptions below include for each instructional track: 1. Who should attend the workshop. 2. What you need to know to enter the workshop and benefit from it (Prerequisites). 3. What you will learn in the workshop. 4. What you should be able to do after completing the workshop (Goals). TRACK 1: Host-based Internetworking Technology ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ WHO SHOULD ATTEND: Technical staff who are operating or installing a TCP/IP based network and providing TCP/IP based services (such as mail, file, web) to end-users. Those are involved in the establishment and/or operation of an Internet presence, possibly initiating the deployment of a basic national network infrastructure in the country. PREREQUISITES: UNIX use and preferably some UNIX system administration. Some knowledge of, and experience with, computer networks. WHAT YOU WILL LEARN: Techniques for design, set up and operation of a TCP/IP network. Knowledge of routing, network troubleshooting, interior routing protocols, domain name system, providing dial-up connectivity, and TCP/IP application servers such as mail and web. GOALS: To be able to design, set up, and operate a TCP/IP network with a permanent connection to the international Internet, and to provide TCP/IP services to end-users, using primarily PC hardware and Unix. TRACK 2: Backbone Internetworking Technology ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ WHO SHOULD ATTEND: Technical staff who are now or soon will be building or operating a wide area TCP/IP backbone network, likely with international and/or multi-provider connectivity. PREREQUISITES: UNIX use and preferably some system administration. Some knowledge of, and experience with, computer networks, preferably TCP/IP-based. WHAT YOU WILL LEARN: Techniques for design, setup, and operation of a metropolitan, regional, or national TCP/IP dedicated backbone network. Detailed knowledge of routing, network troubleshooting, backbone engineering, interior and exterior routing protocols, domain name system, NIC name and address coordination. The emphasis will be on use of dedicated routing hardware. GOALS: To be able to design, set up, and operate a metropolitan, regional, or national TCP/IP dedicated backbone network, with a permanent connection to the international Internet. TRACK 3: Internet Information Services ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ WHO SHOULD ATTEND: would-be providers of Internet-based information services; also those supporting and training potential information providers on the non-commercial Internet. PREREQUISITES: A good user-level knowledge of the various Internet services such as e-mail and the World Wide Web is highly desirable. No programming skills are required. WHAT YOU WILL LEARN: How to set up and design quality Internet Information services with emphasis on the World Wide Web. Since an important reason for your attendance will be to enable you to pass on your knowledge to others, there will be sessions on how to support and train users and providers of information. Note that this is NOT a programming course. The main topics covered will include: ~ A brief introduction to the Internet and Internet tools ~ Setting up and maintaining quality information services ~ World Wide Web servers ~ World Wide Web clients ~ Search services ~ Caching strategies ~ HTML authoring ~ How to support and train users and providers of information The following will be discussed: ~ Security issues ~ Legal and ethical issues ~ National infrastructure issues An awareness of topics such as the following will be given ~ CGI scripts ~ JAVA ~ Javascript The course is a mixture of presentations and demonstrations with emphasis on hands-on practical experience. You will work in small teams to design and set up web services during the workshop. GOALS: Ability to set up and design quality Internet Information services; ability to support and train users and providers of information. TRACK 4: National Network Management ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ WHO SHOULD ATTEND: Individuals who will have the responsibility for management of a network. The topic of "management" covers technical, operational and business management of national Internet services. PREREQUISITES: Rudimentary familiarity with the Internet, and familiarity with management of information technology at a technical level. WHAT YOU WILL LEARN: Exposure to the aspects of management of a public Internet network on a national scale, including areas of operational and policy management commonly found with Internet development. No technical or hands-on component is included, although the managerial aspects of various technical topics is covered. GOALS: Capability to manage the development of a national public Internet, guiding its development into the role of a cost effective and useful communications resource. Location The workshop activities will be held at San Jose State University in San Jose, California, U.S.A. Participants will be housed at the training facilities during the Workshop and the INET'99 Conference. Working Language The working language of the workshop will be English, good comprehension of spoken and written English will be required of each participant. Some members of the instructional staff will have some degree of proficiency in languages other than English. Dates Participants should plan to arrive at their workshop location on or before 1800 hours on Saturday 12 June, and leave San Jose after 1300 hours on Friday 25 June . Exact arrival requirements may depend on the Track selected. We will notify you of your travel requirements when you are accepted. INET'99 begins at 1800 hours, Tuesday 22 June and ends at 1230 hours on Friday 25 June. ELIGIBILITY The workshop is specifically directed toward the needs of people from developing countries who are playing or will play an important part in introducing and extending public internetworking in their countries and regions. Attendees should be involved in planning to establish or in establishing the Internet's presence in their countries and regions, in institutionalizing its operation, and/or in assisting the country's schools and universities, governmental agencies, local firms, and residents in learning about and exploiting the range of services available through the net. Staff members of international and bilateral technical co-operation agencies, as well as professionals having substantial involvement in international technical assistance activities, are also eligible for admission as space allows. Participants who have attended one or more previous Internet Technology Network Workshops (formerly Developing Countries Workshop) will be considered eligible to attend the 1999 workshop; however, these former participants must apply for a course of study other than subjects studied previously. Their request must be consistent with their responsibilities in a national and/or regional context, and a convincing argument for repeated attendance must accompany the application. This should include a statement of the activities carried out as a result of the previous workshop. Less financial aid will be available for repeat attendees than for first-time applicants. APPLICATION FOR ADMISSION PLEASE SUBMIT YOUR COMPLETED APPLICATION VIA THE WEB IF POSSIBLE. You might want to use a word processor and then cut and past the text into the web form. The web form is located at <http://www.isoc.org/inet99/ntw_info.shtml#form>. If you are unable to submit via the web, PLEASE SUBMIT BY ELECTRONIC MAIL IF POSSIBLE, using plain text, no attachments. Further submission instructions, fax and postal addresses are at the end of the application. Applicants will be notified of their acceptance to the program and the amount of financial aid, if any, available to them at the end of April. Please note that in this context, the workshop activity includes attendance at the INET'99 Conference. If you are admitted to the workshop, you should NOT register separately for the Conference; that will be done automatically for you. NOTE: Applicants are required to submit some form of *reliable* electronic address (Please make an effort to give an electronic mail address if possible; a reliable FAX number should also be included on your application, and can be used for correspondence if e-mail communication is not possible.) in order to expedite notification of their acceptance as well as any further correspondence. Please be sure that all of the contact information you submit is legible and accurate, or we will not be able to contact you. Visas Every visitor to the United States must have a valid passport in order to obtain the necessary visa from the U.S.A. If you apply to attend the workshop, be prepared to obtain a passport immediately upon receiving an invitation to attend, or sooner if practical, since visa procedures may be lengthy. It is the responsibility of participants to ascertain the visa requirements that apply to them and to obtain any appropriate visas (including transit visas) needed to attend the workshop and the related conference. The Internet Society will assist applicants in this matter by providing visa application information as well as information regarding the Workshop, the Society and its professional goals and activities. Costs The cost of attending the workshop and associated events is U.S. $3,500. Your acceptance may depend on your ability to provide some or all of the funding for the workshop and air transportation. This fee includes: - All tuition and fees for the workshop. - All lodging charges from Saturday, 12 June through Friday, 25 June. - All meal charges for the period starting with dinner on Saturday evening, 12 June through breakfast on Friday morning, 25 June. - Registration at the INET'99 Conference (22-25 June), including those meals and social events included in conference registration. Participants should bring the equivalent of U.S. $50 for airport transfers and departure tax. They may wish to budget approximately U.S.$50-250 for optional travel and other needs and activities (laundry, etc.) from Sunday 20 June through the morning of Friday, 25 June. For some candidates, the Internet Society will provide financial assistance to cover a part or all of each participant's overall expenditures. If you request financial aid for the workshop, please be certain to provide the financial information that will be requested in the application for admission. Financial aid will take the form of either pre-paid airline tickets for travel to and from your workshop location and the INET'99 conference, partial or total coverage of the workshop fee, or both. The overall amount of aid available will be limited. Please make all possible efforts to secure whatever funding is possible from sources known to you. If you are requesting financial aid, please tell us why it is necessary, how you expect to fund part of your expenses, and what efforts you have made and are making to obtain additional aid. Aid from ISOC may depend upon your ability to obtain partial financial support from other sources. Additional Information Specific questions regarding the workshop may be directed to Carla Rosenfeld, Manager of Conferences, by sending e-mail to Workshop-Info(a)ISOC.ORG or sent by postal mail to 1999 Workshop Info, Internet Society, 12020 Sunrise Valley Drive, Suite 210, Reston, VA, 20191, USA. APPLICATION FOR ADMISSION A. Personal Data ------------------------ FULL NAME: FAMILY NAME (LAST NAME, SURNAME) ONLY: Employer/Organization: Position/Title: Business Address: (not to exceed 40 characters per line) Business Telephone: Fax (if any): Email address (if any): Home Address: (not to exceed 40 characters per line) Home Telephone: At which address would you like to receive your mail? _____ Business _____ Home Which phone number do you prefer we call? _____ Business _____ Home Date of birth (day/month/year): Nationality: Name as it appears on passport or other travel document: Passport number: Country issuing passport: Are you an ISOC member? ----- yes ----- no Your ISOC member number if you know it: Knowledge of English: Please rate your knowledge in these categories: Listening/ Comprehension None Fair Good Excellent Reading None Fair Good Excellent Speaking None Fair Good Excellent Writing None Fair Good Excellent B. Course of Instruction ------------------------ Instructional track applied for (Select only one track; the tracks will run concurrently): [ ] Track 1 Host-based Internetworking Technology [ ] Track 2 Backbone Internetworking Technology [ ] Track 3 Internet Information Services [ ] Track 4 National Network Management Please indicate any specific interests within the area (track) you have chosen: C1. Technical Skills (This section to be completed only for applicants attending Tracks 1 or 2) ------------------------------------------------------------------ 1. Are you a UNIX user? How much have you used it? 2. Have you been a UNIX system administrator? Describe your experience (length of time, versions, etc.). 3 Have you used/administered TCP/IP networks? Describe. 4. Have you used or run a BBS? Describe. 5. Have you set up UUCP? How many times? Describe. 6. Have you set up modem initialization strings? In what circumstances? How many times? 7. What other operating systems are you familiar with (e.g. MacOS, Appletalk, MS-DOS, Novell Netware, Banyan Vines, VMS, DECNET, etc.), and for how long have you been a user or administrator of each? 8. Have you configured and operated a Domain Name System server? How many zones? 9. Have you configured routing on either dedicated router hardware or a UNIX host? If yes, please list manufacturer/model/software version(s) and protocols routed. C2. Internet Experience (This section to be completed only for applicants attending Track 3) ------------------------------------------------------------------ 1. Do you have experience in using the following Internet services? (Please qualify your experience using 0 to 5, 0 means no experience and 5 a lot of expertise) [ ] Email [ ] Listserver [ ] News [ ] FTP [ ] Web [ ] Other (specify): 2. Do you have experience running Internet services? (Please qualify your experience using 0 to 5, 0 means no experience and 5 a lot of expertise) [ ] Listserver [ ] News server [ ] FTP server [ ] Web server [ ] Searching/Indexing services [ ] Caching Server [ ] Other (specify): D. Description of Role in National Networking Activities -------------------------------------------------------- Your answers to the questions below will be used to determine whether to admit you to the workshop. Please be sure that your information is sufficiently clear, well organized and adequate for this purpose. 1. A summary of your educational and professional background. 2. A description of your current employer, your position, your duties and responsibilities, and how they relate to current and future data networking activities in your country. 3. A brief description of your computing and networking environment (operating systems, networking software, modems, etc.), including the connectivity of your organization to the Internet and your country's connectivity to the international Internet. 3a. Scope of your institution (check all categories that apply): [ ] Academic [ ] General Research [ ] Government [ ] NGO [ ] International organizations (UNESCO, UNDP, World Bank, etc.) [ ] Commercial [ ] Internet Provider [ ] National Network Support [ ] Special Interest Group Specify________ [ ] Other Specify________ 3b. Approximate number of full time staff at your institution: 4. How your training and current work prepare and qualify you for the track you wish to attend. 5. How you expect to use the knowledge you gain at the workshop and the INET'99 conference after you return to your country. 6. Have you have previously attended Internet Society Workshops for Developing Countries? _____ Yes _____ No If yes, 1. Year and track you attended: 2. A precise description of how you have used the training you have received in the past: 3. The significant advances in networking which have occurred in your country specifically because of your knowledge and effort: E. Financial Information ------------------------ You MUST fill out the following financial information. The cost of the workshop is $3500 1. Are you are requesting any financial aid from the Internet Society (ISOC) for attending the workshop and conference? [ ] No [ ] Yes 2. Will you provide your own airfare? [ ] Yes [ ] No 3. If you are requesting financial aid, please indicate source below: Amount provided by your institution, government, international organizations or personal contribution U.S.$__________ Amount you are requesting from ISOC U.S.$__________ TOTAL Income Required $3,500.00 PLEASE SUBMIT YOUR COMPLETED APPLICATION VIA THE WEB IF POSSIBLE. You might want to use a word processor and then cut and past the text into the web form. The web form is located at <http://www.isoc.org/inet99/ntw_info.shtml#form>. If you are unable to submit via the web, PLEASE SUBMIT BY ELECTRONIC MAIL IF POSSIBLE, using plain text, no attachments. The "Subject" line of the message should contain your surname or family name in the following format: Subject: NTW'99 Application: <family-name> Applications submitted electronically should be sent to: Workshop-Application(a)ISOC.ORG If you are not able to send your application by electronic mail, please return this application by fax or air mail to: Internet Society Network Technology Workshop Internet Society 12020 Sunrise Valley Drive, Suite 210 Reston, VA 20191-3429 U.S.A. Voice: +1.703-648-9888 Facsimile: +1.703-648-9887 For a copy of this announcement, including a blank application, send e-mail to: Workshop-Apply(a)ISOC.ORG --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

APRICOT
by Robert Gray 22 Feb '99

22 Feb '99

Me. Just until Wednesday night. -----Original Message----- From: Joe Abley [mailto:jabley(a)clear.co.nz] Sent: Tuesday, 23 February 1999 20:43 To: 2Day Chief Enthusiast Cc: nznog(a)list.waikato.ac.nz; jabley(a)clear.co.nz Subject: Re: limiting smtp message size On Tue, Feb 23, 1999 at 08:34:55PM +1300, 2Day Chief Enthusiast wrote: > Does anybody here limit size of smtp e-mail messages accepted by mail > exchange and if so, what max size (including attachments)? > > I have a customer who thinks that we were being unreasonable for rejecting a > 20Mb email :-) We have a 10Mbyte limit for customer mail (and a 5Mbyte limit for mail to clear.co.nz). Tell your customer "man split" :) Changing subjects completely, is anybody on this list going to Apricot next week in Singapore? Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Last Change for APRICOT's Early Bird Discounts!
by Barry Raveendran Greene 16 Feb '99

16 Feb '99

---------------------------------------------------------------------------- ---- Tomorrow - Friday Feb 19th - is the last chance for the APRICOT'99 Early Bird Discounts Register today at http://www.apng.org/apricot99 ---------------------------------------------------------------------------- ---- Specialized and Unique Tutorials! Sign up now for these unique tutorials. Space is limited! "ISP System Administration" by Barbara L. Dijker & Evi Nemeth "Sendmail Configuration and Operation" (Updated for Sendmail 8.9) by Eric Allman "Internet QoS and Traffic Management" by Geoff Huston "Internet Exchanges: The State of the Art" by Bill Manning "Designing Scaleable IP Networks" by Justin W. Newton "Optical Internetworking" by Marty Schulman "VoIP Standards Efforts and Impacts" by Scott Bradner "Routing Policy Specification Language and Analysis Tools" by David Kessens and Cengiz Alaettinoglu "Deploying VPN's and Secure Extranets" by Bruce Perlmutter "Managing Acceptable Use" by Barbara L. Dijker "Promoting Routability" by Philip Smith "Voice and Telephony Over IP" by Drew Freyman "IPv6: The New Version of the Internet Protocol" by Steve Deering "Tools Used at Digex and Verio to Manage Their Networks" by Randy Bush & Ed Kern "Security in All Seven Layers" by Gene Deutsch "Safeguarding The Business Process: E-Commerce Security" by Dr. Kelly Jones "Broadband Wireless Local Loop" by Dewyane Hendricks "Cable Modem Protocols and Technology" by Mark Laubach "APNIC Member Training: Address Policy & Administration" by Anne Lord & Paul Wilson ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ APRICOT (Asia & Pacific Rim Internet Conference on Operational Technologies) Singapore March 1 - 5, 1999 -- The Annual ISP Operations and Business Summit in Asia and Pacific -- http://www.apricot.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

PGP Keysigning Party - APRICOT 99, Singapore, March 1-5 1999
by Barry Raveendran Greene 16 Feb '99

16 Feb '99

APRICOT 99, Singapore, March 1-5 1999 PGP Keysigning Party As at most IETF meeting and other regular networking events with sufficient participants, we will be holding a PGP keysigning party during this March's APRICOT/ICANN/APNG/APNIC Meetings & Singapore Linux Conference in Singapore. Quick Facts: ============ Key Submission: Deadline: All keys must be received in the submission email box by Wednesday, 3 March 1999, 18:00 (Singapore Time !) Submission pgp(a)apricot.net email address: Subject: APRICOT PGP KEY Format: Please send your key as normal ASCII text. The keys should NOT be sent as attachments or in any proprietary format (like eg MS Word etc). PGP Formats PGP 2.6 (RSA) and PGP5 (RSA and D/H) Supported Note: Keys sent to any other address or sent with a different subject may not be included in the official Apricot 99 PGP keyring! Event details: Date: Thursday, 4 March 1999 Time: 18:00 - 19:30 Venue: Suntec City Convention City Room MR203 (Level 2) Status: BOF (Birds of a Feather ...) (ie *all* are welcome, as long as your key has been received on time. No APRICOT/SLC etc registration required !) Please check the APRICOT Notice board for any changes in Room and Time ! Instructions for Participants: ============================== 1. Who should attend 1. All people who have a PGP key The PGP Keysigning Party will enable you to obtain additional signatures (among others by noted net- personalities) for your PGP key. 2. All people who have just started to use PGP If you just started using PGP, It is unlikely that your key has been signed by (m)any other PGP users so far. To ensure that your key is trusted by the majority of the PGP users all over the world, you will be interested to have well- known net-personalities (and other people) sign your key. 3. Those who do not have a PGP key yet You will need to: 1. read up on PGP itself 2. create your own PGP key to attend the keysigning party 4. Organizations Many organizations use PGP to sign official announcements etc. Usually these organizations publish their PGP key on the web. As additional security, you may want your key to be signed by other trusted 2. Preparation - extract your public key using one of the following commands (depending on your PGP version): -UNIX PGP 2.6* $ pgp -kxa <your PGP userid> -UNIX PGP 5.* $ pgpk -xa <your PGP userid> -Win95 or other GUI Use the export function to export your implementation key to a text file For more details on the PGP commands refer to the PGP manual - send in your PGP public key. (the PUBLIC KEY!!! Never give out your PRIVATE key to anyone!!) to the submission email address listed above. Please do NOT send the key as an attachment or in any other format but ASCII ARMORED TEXT! You could cut and paste the ascii armored PGP key into the email body if necessary! - write down (print out) your own public key's fingerprint and the Key ID. Under UNIX, you can obtain the key ID and fingerprint using these commands: -UNIX PGP 2.6* $pgp -kvc <your PGP userid> -UNIX PGP 5.* $ pgpk -ll <your PGP userid> -Win95 or other GUI Check the Key Properties (in implementation PGPkeys) Here is an example of a PGP key ID and fingerprint extracted under UNIX (PGP 5.0i): Note: This also lists the signatures on this key, but we need only the first few lines (marked with **): $ pgpk -ll mathias Type Bits KeyID Created Expires Algorithm Use ** sec+ 768 0x25E082BD 1995-11-15 ---------- RSA Sign & Encrypt ** f16 Fingerprint16 = 1A 8B FC D4 93 F1 9A FC BD 98 A3 1A 0E 73 01 65 uid Mathias Koerber <mathias(a)koerber.org> SIG 0x25E082BD 1996-08-22 Mathias Koerber <mathias(a)koerber.org> uid Mathias Koerber <mathias(a)staff.singnet.com.sg> sig 0x101E3A11 1998-02-23 Alfonso B. Carandang <abc(a)epic.net> SIG 0x25E082BD 1996-06-09 Mathias Koerber <mathias(a)koerber.org> uid mathias(a)singapura.singnet.com.sg SIG 0x25E082BD 1995-11-17 Mathias Koerber <mathias(a)koerber.org> uid Mathias Koerber <Mathias_Koerber(a)pobox.org.sg> SIG 0x25E082BD 1995-11-16 Mathias Koerber <mathias(a)koerber.org> uid Mathias Koerber <mathias(a)singnet.com.sg> sig 0x3022C951 1995-12-18 William Allen Simpson <Bill.Simpson(a)um.cc.umich.edu> sig? 0x0DBF906D 1996-03-09 (Unknown signator, can't be checked) sig? 0x579532CD 1995-12-08 (Unknown signator, can't be checked) sig? 0x7B7AE5E1 1995-12-18 (Unknown signator, can't be checked) sig 0x76875905 1995-12-10 Angelos D. Keromytis <kermit(a)forthnet.gr> sig 0x466B4289 1995-12-07 Theodore Ts'o [SIGNATURE] <tytso(a)mit.edu> SIG 0x25E082BD 1995-11-15 Mathias Koerber <mathias(a)koerber.org> uid Mathias Koerber <mathias(a)singnet.com.sg> <Mathias_Koerber(a)pobox.org.sg> SIG 0x25E082BD 1995-11-15 Mathias Koerber <mathias(a)koerber.org> 3. At APRICOT, before the PGP keysigning Party - periodically check the noticeboard, where the list of keys submitted for the PGP keysigning party will be posted. Your key must be submitted by the deadline to be called during the keysigning party and included in the official APRICOT PGP keyring. If you submitted your key, and it does not appear on the list, please submit it again before the deadline! 4. At the PGP Keysigning Party itself - Bring along proper PHOTO identification For other participants to sign your PGP key (which is the whole aim of this event), they must be able to verify that the key belongs to you and that you really are who you claim to be. - if you submitted a PGP key for your organization, please bring along identification which proves that you are indeed representing that organization · letter by the president/management etc on their stationery · namecard · company pass etc - obtain the list of submitted keys (this will be provided as a printout at the beginning of the party). - check that YOUR OWN public key is listed on the printout, and check its PGP KEY FINGERPRINT. Check it carefully. The fingerprint must match in *every* character Procedure ========= - During the party, we will one by one read out aloud each PGP key submitted including the KeyID, the attached userIDs (names) and the Key Fingerprint. During this the owner of the key will stand up to be recognized by the crowd. (We may need each key-owner to read their own Key fingerprint etc, unless we manage to rustle up a suitable Voice program to automatically read the keys) - During this, each participant should 1. check that the userid, name, keyid and fingerprint match what is printed on your printout 2. ensure that the person standing up acknowledges the key as his own 3. note which keys checked out ok and which ones haven't - After all keys have been read, you are encouraged to 1. verify the owners' identities by checking their supporting documents (Photo ID) 2. especially carefully verify the credentials for those who want an organization's key signed. 5. After the PGP Keysigning Party - obtain the official APRICOT 99 keyring from http://www.koerber.org/apricot99/ This will be available sometime after the keysigning party. A more detailed announement will be posted on the APRICOT Notice Board. There will be 2 keyfiles, one with only PGP2.6 keys, the other containg all (PGP2.6 and PGP5) keys - decide whose keys you would want to sign (using your notes made during the keysigning party) You should only sign keys if you have *very carefully* verified the key's integrity and the owner's supporting documents (passport etc). If there is any doubt as to a person's identity or ownership of a key, do NOT sign that person's key !! - sign these people's keys with your own PGP PRIVATE KEY, using your PGP software - export/save the signed keys into ASCII files (see the PGP manual) - either send the signed public keys to the keys owner (recommended) or to one of the public PGP keyservers. It is recommended that you send the key to the owner, so that they can decide themselves which signatures to send to the keyservers. - If you had presented your own key, you may want to check the public pgp keyservers periodically to see whether other participants have sent in new signatures for your own key. If so, you may want to obtain you own public key from the server and add it (actually only the additional signatures) to your own keyring. If another participant has sent you your key with a new signature, you will want to add the new signature to your own keyring, and then send the key to the public PGP keyservers. ========== Background ========== What is PGP? PGP (Pretty Good Privacy) is a standard (and a program implementing that standard) providing strong authentication and encryption for email (and other networking applications such as internet phone) using a public key system. Why is PGP important? From the PGP FAQ (http://www.at.pgp.net/pgpnet/pgp-faq/) You should encrypt your e-mail for the same reason that you don't write all of your correspondence on the back of a post card. E-mail is actually far less secure than the postal system. With the post office, you at least put your letter inside an envelope to hide it from casual snooping. Take a look at the header area of any e-mail message that you receive and you will see that it has passed through a number of nodes on its way to you. Every one of these nodes presents the opportunity for snooping. Encryption in no way should imply illegal activity. It is simply intended to keep personal thoughts personal. Xenon <an48138(a)anon.penet.fi> puts it like this: Crime? If you are not a politician, research scientist, investor, CEO, lawyer, celebrity, libertarian in a repressive society, investor, or person having too much fun, and you do not send e-mail about your private sex life, financial/political/legal/scientific plans, or gossip then maybe you don't need PGP, but at least realize that privacy has nothing to do with crime and is in fact what keeps the world from falling apart. Besides, PGP is FUN. You never had a secret decoder ring? Boo! -Xenon (Copyright 1993, Xenon) What is keysigning, and why is it important? Again, see the FAQ: http://www.at.pgp.net/pgpnet/pgp-faq/faq-06.html What is a PGP Keysigning party? A PGP keysigning party is not a party in the sense of celebration. It is unlikely that alcohol will flow or hors d'oevres be passed out. As PGP uses a public key system, it usually is easy to obtain some person's public PGP key (which is required to securely converse with that person or to verify that person's authorship or identity). The usual method for this is to either ask the person directly for their PGP key. Another method is to request it from a public PGP keyserver, which is like a worldwide replicated directory of PGP public keys. More info? You can find more information on PGP at these webpages: PGP Inc.: http://www.pgp.com PGP.net: http://www.pgp.net International PGP Homepage: http://www.ifi.uio.no/pgp/ There is a PGP discussion newsgroup named comp.security.pgp and its FAQ: http://www.at.pgp.net/pgpnet/pgp-faq/ There is a book on PGP published by O'Reilly & Associates: Simson Garfinkel: PGP: Pretty Good Privacy 1st Edition December 1994 1-56592-098-8, Order Number: 0988 430 pages, $29.95 see: http://www.oreilly.com/catalog/pgp/noframes.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ APRICOT (Asia & Pacific Rim Internet Conference on Operational Technologies) Singapore March 1 - 5, 1999 -- The Annual ISP Operations and Business Summit in Asia and Pacific -- http://www.apricot.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ --------- 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: NZNOG BOG at Uniforum '99
by Donald Neal 14 Feb '99

14 Feb '99

Joe, I'm due to be there. Must write paper soon, too. - Donald Neal --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NZNOG BOG at Uniforum '99
by Joe Abley 14 Feb '99

14 Feb '99

Hi all, Last year a few of us got together at Uniforum to drink beer^H^H^H^H^H^H^H discuss serious issues, resulting in (amongst other things) this list being a bit more widely used. It was also kind of nice to put faces to e-mail addresses. Just a quick straw-poll - who's thinking about going to Uniforum '99 in Rotorua? Enough to organise a BOF at the bar? Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

Re: NZNOG BOG at Uniforum '99
by Mark Davies 13 Feb '99

13 Feb '99

From: Joe Abley <jabley(a)patho.gen.nz> Date: Sun, 14 Feb 1999 13:35:25 +1300 > Oh good lord, damn my typing. That's "BOF", not "BOG". And I thought you were implying something :-) Well I am thinking of going to some of it, unfortunately it clashes with another very important event. cheers 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

Surplus Equipment
by Robert Gray 07 Feb '99

07 Feb '99

I know this is not the place to discuss selling/buying surplus network equipment, but (in common with others?) we have collected quite a bit gear which is somewhat specialist in nature and surplus to requirements. In other words Trade and Exchange is not an appropriate outlet. Anyone found a good place to trade such gear? Robert Gray Clearview Communications, Auckland New Zealand bobg(a)clearview.co.nz http://www.clearview.co.nz/ Phone DDI +64 9 529 5704, Fax +64 9 529 5702, Mob +64 25 971 860 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

Christchurch Recycler details herewith
by Les Chapman 07 Feb '99

07 Feb '99

G'day all Electronic details for Christchurch PC Recycling company are Molten Metal Christchurch bj(a)molten.org.nz (Brett Hayward) This message is sent via Outlook 2000, if any issues please contact me TTFN Les Chapman mostly a gopher at Swichtec/odtaa/ThincNZ asker of at least half-remarkable questions proudly resident in Canterbury on the Brains Plain elsie(a)stmartins.school.nz bosandals(a)stmartins.school. trouble(a)stmartins.school.nz bufonidae(a)stmartins.school.nz les(a)stmartins.school.nz (pick 'n' mix emailing <G) Phone: +64-3-343-3314(friendly answerperson) Fax: +64-3-343-5100 Dungeon: +64-3-332-9143(moi occasionally) Voicemail: +64-3-332-4998(always) http://www.swichtec.co.nz http://www.intergy.co.nz http://www.electroflash.org.nz http://www.stmartins.school.nz "aibohphobia - fear of palindromes?" "Be Alert - for we need more of them!" "wisdom - is knowing a deja-vu when you stumble across one" "if at first you don't succeed - trier drier grain" "The mind is like a parachute - its useless unless its open" "if something goes without saying - let it! "Schools need curriculum, not technology!" "A woman who tries to emulate men lacks vision" "I wish this BETA guy would stop testing our software!" --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

APNIC "Policies for Address Space Management in the Asia Pacific Region"
by Joe Abley 07 Feb '99

07 Feb '99

http://www.apnic.net/policydraft.html --------- 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: Surplus Equipment
by Frank March 07 Feb '99

07 Feb '99

Schools may be interested in good quality equipment which is replaced because of upgrading (ie is still perfectly serviceable or readily repaired). A national consortium of computer recyclers has been set up to channel good quality equipment at minimal cost into schools and not-for-profit organisations (schools are the main emphasis). I am copying this to their mailing list. Briefly AFAIK at present there are just three recyclers: Bob Lye (The Ark) in Auckland; Richard Darton (PCRC) on Wellington and another group in Christchurch (apologies to the folk down there, I dont know who you are). These people are attempting to live from these activities but margins are low so they really appreciate DONATIONS of gear ;) Computer (and other IT equipment) recycling is endorsed as part of the series of initiatives from the Ministry of Education for IT in schools. Another very good contact group is NetDay99.. contacts and information at the web site http://www.netday.net.nz/ NetDay is also backed by the Ministry of Education and many other fine institutions. Netday provides very basic networks for schools (a basic 8 or 16 port hub and Cat 5 cabling) but routers, servers etc etc are badly needed. Frank March Specialist Advisor IT Policy Group, Ministry of Commerce, PO Box 1473, Wellington, New Zealand Telephone: +64 4 474 2908; Fax: +64 4 471 2658 (Please note new Fax number) > -----Original Message----- > From: Robert Gray [SMTP:bobg(a)clearview.co.nz] > Sent: Monday, February 08, 1999 8:30 AM > To: nznog(a)list.waikato.ac.nz > Subject: Surplus Equipment > > I know this is not the place to discuss selling/buying surplus network > equipment, but (in common with others?) we have collected quite a bit gear > which is somewhat specialist in nature and surplus to requirements. In > other > words Trade and Exchange is not an appropriate outlet. > > Anyone found a good place to trade such gear? > > Robert Gray > Clearview Communications, Auckland New Zealand > bobg(a)clearview.co.nz http://www.clearview.co.nz/ > Phone DDI +64 9 529 5704, Fax +64 9 529 5702, Mob +64 25 971 860 > --------- 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: BGP at NZIX. Mmm.
by Warwick GLENDENNING 07 Feb '99

07 Feb '99

>WebFarm blames Ihug for its network becoming inaccessible, because of action Ihug took >following a network attack. But Ihug director Nick Wood doesn't believe the 16-hour outage was >its fault. He says Ihug was being attacked by someone he claims was on the WebFarm network. "We >blocked their network on our router and Waikato's router, for some reason, at NZIX learned the >route." IHUG doesn't directly connect to NZIX. They are behind Telecom's router. -----Original Message----- From: Joe Abley [mailto:jabley(a)patho.gen.nz] Sent: Monday, 8 February 1999 01:15 To: nznog(a)list.waikato.ac.nz Subject: BGP at NZIX. Mmm. http://www.idg.co.nz/nzweb/ca6a.html Looks like another good reason to use a routing protocol that can be filtered at NZIX :) Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

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

07 Feb '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 66 subscribers.) 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 arrange meetings 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

Re: BGP at NZIX. Mmm.
by craig＠laptop.iprolink.co.nz 06 Feb '99

06 Feb '99

> Looks like another good reason to use a routing protocol that can be filtered > at NZIX :) But the article said it had only one in a million chance of happening. Apparently the latest version of IOS supports the following: redistribute static odds 1:1000000 ignore-filters -Craig --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

BGP at NZIX. Mmm.
by Joe Abley 06 Feb '99

06 Feb '99

http://www.idg.co.nz/nzweb/ca6a.html Looks like another good reason to use a routing protocol that can be filtered at NZIX :) 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

NZ Promiscuous Mail Relay Survey
by Joe Abley 06 Feb '99

06 Feb '99

Hi again, Further to my message on this subject the other day, I decided to send an informational note to postmaster addresses at hosts that I had found to be relays. Some readers of this list will have received copies. Although I have received quite a bit of positive feedback from the notes I sent out, it seems that I have inadvertantly upset some people. If you are one of them, then sorry - I didn't mean to intrude. I have put some information about the survey (and a list of the frequently- asked questions so far) at: http://www.patho.gen.nz/~jabley/survey.html 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

NZ promiscuous relay survey
by Joe Abley 05 Feb '99

05 Feb '99

Last night I performed a crude survey in an attempt to find out something about the proportion of SMTP mail relays which permit promiscuous relaying in NZ. The methodology is by no means flawless, but it might give an idea of the scope of the problem. If anything, the proportion of mail relays which are open is understated, due to: + an incomplete list of mail relays in NZ to check; + a rather nasty SMTP implementation hacked together for this purpose that isn't very flexible and makes various poor assumptions; + mail relays which were broken at the time of the test; + mail relays which _will_ relay my mail back to be counted, but which haven't yet. Anyway, here are the results -- comments welcome! Out of 3751 MX hosts that we tried to use as a relay: + 269 (7%) accepted our message, but later bounced it + 1208 (32%) relayed our message OF the messages that were relayed: + 929 (76%) were from hosts named under co.nz + 33 (2%) were from hosts named under net.nz + 72 (5%) were from hosts named under govt.nz + 15 (1%) were from hosts named under ac.nz + 22 (1%) were from hosts named under school.nz + 0 (0%) were from hosts named under iwi.nz + 8 (0%) were from hosts named under gen.nz + 38 (3%) were from hosts named under org.nz + 1 (0%) were from hosts named under mil.nz I will not publish the list of MX hosts that did or did not permit relaying in this experiment. If you'd like to enquire about whether an MX host that you maintain relayed our message, please contact me directly. Methodology: 1. Zone transfers were performed for the NZ second-level domains co.nz, ac.nz, mil.nz, gen.nz, org.nz, school.nz, iwi.nz, and net.nz. 2. For every key in each of these zonefiles with an NS record, the key was extracted. A unique list of keys with NS records was generated. 3. MX records for each key were harvested from the DNS and a unique list of mail exchangers to be tested was produced. 4. A message with envelope sender jabley(a)patho.gen.nz and envelope recipient relayed(a)patho.gen.nz was sent by connecting to each relay and talking SMTP. Each message contained a random key which was stored in a local database. 5. Every time a message was received with a matching key in the body text and addressed to relayed(a)patho.gen.nz, the local database was updated indicating that the MX host in question permitted the relay. 6. All SMTP connections were made from tardis.patho.gen.nz (203.97.2.226) between 0500, Feb 5 1999 and 1400, Feb 6 1999. 7. MX hosts which specifically (intentionally) permit mail relaying from tardis.patho.gen.nz were excluded from summary reports. --------- 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: Traceroutes
by craig＠laptop.iprolink.co.nz 04 Feb '99

04 Feb '99

Hi. > I suspect many of you know of the DIGEX site which allows you to > traceroute (and other things) from a web page [...] My favorite "Address" to use with DIGEX (select "bgp"): regex _MYASNUMBER_ Obtaining a full BGP table dump is left as an exercise for the reader :-) -Craig --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

The APRICOT Week at a Glance ( Version 1.1 ) - The Asia Pacific Internet Festival of 1999
by Barry Raveendran Greene 01 Feb '99

01 Feb '99

[Apologies for the Duplications] !! Early Bird Sign up ends on 12 Feb! !! !! REGISTER NOW by Going to the on-line to !! !! http://www.apng.org/apricot/apricot.html !! !! and save $50 USD on registration cost !! The APRICOT Week at a Glance ( Version 1.1 ) The Asia Pacific Internet Festival of 1999 Venue: SunTec City Convention Centre, downtown Singapore Dates: 28 February 1999 to 7 March 1999 URL: http://www.apng.org/apricot99 (in English, Japanese, Korean, and Chinese) APRICOT'99 will consist of two days of tutorials (1-2 March 1999) and seminars followed by three days of conferences consisting of concurrent Technical, Business, Education, Policy and other tracks. (3-5 March 1999) In addition to other back-to-back meetings of Asia Pacific Internet organizations APNG, APNIC, APIA, APTLD, and their respective working groups, and other Internet conferences such as Internet World Asia @ Singapore 1999 and Singapore LINUX Conference 1999, APRICOT'99 will be hosting within its conference tracks: * ICANN Meeting, the Internet Corporation for Assigned Names and Numbers, the successor organization to IANA. (3 March 1999) * APPLe Policy Track * Women in IT BoF * APNG Education Track * APSIRC WG (Security CERTs and FIRSTs in Asia and Pacific) * Regional Internet eXchange Point (IXP) Update BOF * APIA Business Track In it's tradition of empowering the Internet community, APRICOT'99 will again offer unique tutorials that vital to an ISP's operations. These tutorials are presented by an instructor team that is the top %1 of the ISP Community. Through APRICOT, they are offering the ISP and Telco community knowledge, experience, and information that is not available in any other forum. Some of the material is unique - one time only at APRICOT'99. For example, "Tools Used at DIGEX and Verio to Manage Their Networks" by Randy Bush & Ed Kern, is unique in that the internal network techniques and tools of two US Tier 1 ISPs will be shared with any who come to the tutorial. New and existing ISPs/Telcos can learn from the first hand experience gained from two gurus and apply them to their networks. Here is a list of the APRICOT Tutorials: "ISP System Administration" by Barbara L. Dijker & Evi Nemeth "Sendmail Configuration and Operation" (Updated for Sendmail 8.9) by Eric Allman "Internet QoS and Traffic Management" by Geoff Huston "Internet Exchanges: The State of the Art" by Bill Manning "Designing Scaleable IP Networks" by Justin W. Newton "Optical Internetworking" by Marty Schulman "VoIP Standards Efforts and Impacts" by Scott Bradner "Routing Policy Specification Language and Analysis Tools" by David Kessens and Cengiz Alaettinoglu "Deploying VPN's and Secure Extranets" by Bruce Perlmutter "Managing Acceptable Use" by Barbara L. Dijker "Promoting Routability" by Philip Smith "Voice and Telephony Over IP" by Drew Freyman "IPv6: The New Version of the Internet Protocol" by Steve Deering "Tools Used at Digex and Verio to Manage Their Networks" by Randy Bush & Ed Kern "Security in All Seven Layers" by Gene Deutsch "Safeguarding The Business Process: E-Commerce Security" by Dr. Kelly Jones "Broadband Wireless Local Loop" by Dewyane Hendricks "Cable Modem Protocols and Technology" by Mark Laubach "APNIC Member Training: Address Policy & Administration" by Anne Lord & Paul Wilson ---------------------------------------------------------------------------- Note that all room numbers refer to those at the SunTec City - Singapore International Convention and Exhibition Center (SICEC) Date Time Room Event ---------------------------------------------------------------------------- MR 204 APNG I18n/XDSL WG (APNG WG SLAP Sunday, 28 0800-1230 cancelled) Feb MR 205 vacant 1300-1800 MR 209 APNG Disability SWG ENABLE'99 Symposium ---------------------------------------------------------------------------- 0900-1800 MR 208, 209, 8 APRICOT Tutorials 306, 308-314 MR204 APNG AP-ISOC Meeting (unconfirmed) 0800-1230 MR205 APNG APSIRC WG Meeting Monday, 1 Mar MR307 APNG-APTLD Meeting on Internationalisation of the DNS MR 206 APTLD Workshop on DNS Policy 1330-1800 MR 307 APNG General Meeting APNG Chairman's Commission 1830-2130 MR 307 Critical Infrastructure Protection ---------------------------------------------------------------------------- 0900-1800 MR 208, 209, 8 APRICOT Tutorials 306, 308-314 ICANN Board Committee Meetings Tuesday, 2 0800-1800 MR 204-207 (closed door) Mar 0800-1230 MR 307 APTLD Country Reports Track 1330-1800 MR 307 APTLD Membership General Meeting Evening To be APRICOT Opening Reception determined (unplanned) ---------------------------------------------------------------------------- APRICOT Opening and Plenary 0900-0945: MR 201 Keynote: Professor Dave Farber 0945-1300: MR 201 ICANN Open Track Wednesday, 3 1330-1700 MR 205 ICANN Open Track Mar 1330-1700 MR 202,203 2 APRICOT Technical Tracks 1330-1700 MR 208 APRICOT Business Track APRICOT BOF 1800 - 1930 To be - Peering/Exchanges determined - Y2K ---------------------------------------------------------------------------- APRICOT Plenary Keynote 0900-1000 MR 205 Chris Moore Van Jacobson Thursday, 4 1030-1700 MR 202,203 2 APRICOT Technical Tracks Mar 1030-1700 MR 208 APRICOT APNG Educational Track APRICOT BoFs 1800 - 1930 To be - iDNS determined - PGP signing - Women in IT BOF ---------------------------------------------------------------------------- APRICOT Plenary Keynote Ms Esther Dyson, ICANN 0900-1000 MR 208 Mr Leong Kheng Thai, Director General, Telecommunications Friday, 5 Authority of Singapore Mar 1030-1700 MR 208 APRICOT APPLe Policy Track 1030-1700 MR 202, 203 APRICOT Technical Track 1030-1700 MR 204 APNIC Executive Council Meeting Evening To be APRICOT Social Event(unplanned) determined ---------------------------------------------------------------------------- Saturday, 6 0800-1800 MR 202 APNIC Annual General meeting Mar 0800-1800 MR 201 APIA AGM ---------------------------------------------------------------------------- APRICOT Home Page http://www.apng.org/apricot99/index.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ APRICOT (Asia & Pacific Rim Internet Conference on Operational Technologies) Singapore March 1 - 5, 1999 -- The Annual ISP Operations and Business Summit in Asia and Pacific -- http://www.apricot.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Traceroutes
by Michael Newbery 01 Feb '99

01 Feb '99

I suspect many of you know of the DIGEX site which allows you to traceroute (and other things) from a web page, but I was recently made aware of a whole page of similar sites, allowing traceroutes from almost anywhere in the world. DIGEX has proved most useful in the past in finding oddball misconfigurations, such as routes that go OUT one way and BACK quite another. <http://www.traceroute.org/> <http://nitrous.digex.net> -- Michael Newbery Technology Manager Saturn Communications Tel: +64-4-939 5102 Mobile:021-642 957 Fax:+64-4-939 5100 "There were no survivors sir. We'll have to find another test market." --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic
by Warwick GLENDENNING 27 Jan '99

27 Jan '99

> > On Mon, Jan 25, 1999 at 01:05:11PM +1300, Warwick GLENDENNING wrote: > > We(Waikato) currently still use OSPF on NZIX to collect NZ > routes. And this > > is vital to our traffic metering. A new metering system is > being built to > > use BGP4 to download NZ routes from our traffic provider. > Once this has been > > done, we will be very keen to download NZ routes from major > ISPs on NZIX and > > OSPF can be decommissioned. > > Supposing that a general agreement to move to BGP was made > earlier than > your planned roll-out - presumably as long as Telecom were > able to make > the NZ table available on OSPF to you, your requirements > would be satisifed? > This is true. > There is no particular necessity for us all to speak OSPF, > right? I would > assume that your particular requirements were an issue > between you and your > service provider, and not a general exchange issue. > > Just exploring ideas :) > This is true too. We only provide layer 2 connectivity. ISPs on NZIX don't have to follow some certain routing protocol. It should depend on their interest. But it should be said that Kawaihiko had multiple service providers and NZIX was the place where most of domestic traffic got exchanged. It's why Waikato has used OSPF to collect NZ routes from NZIX. Since Kawaihiko network broke up, we have been trying to build a new way to meter traffic. It will be appreciated very much if Clear can keep OSPF running until we have rolled out the new metering system. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

IOS configuration lint script
by Joe Abley 26 Jan '99

26 Jan '99

[This message has also been posted.] Hi, At various times I have been involved in maintaining routers with lots of (sub)interfaces, and lots of static routes pointing down those subinterfaces. Unfortunately, a simple "show run" on a router produces a listing with all the static routes listed together, and all the subinterfaces listed separately. On a router with a lot of static routes and a lot of connected networks, this becomes a bit of a headache - you end up with static routes hanging around long after the subinterface has been removed, and spring cleaning usually results at least a couple of confused and unhappy users for whom inbound traffic is now spiralling off somewhere else. Even when this kind of configuration is made automatically (from a database which enforces referential integrity), the odd quick-fix static route added at some time might well hang around for years after it has stopped being useful. I have often wished that I could do a "show run" which would group IOS configuration by customer. Now I can! Hooray! Take an IOS configuration file (as tftp'd or rsh'd somewhere, or perhaps retrieved using ciscoconfd) and pass it through this awk script. The configuration will be re-sorted, so that: + most configuration comes first + (sub)interface configuration comes next, with corresponding static routes + all other static routes come next + "end" The static routes corresponding to a connected (sub)interface are hence shown grouped with that subinterface. All static routes that don't point at a connected network are listed separately right at the end, where they can be scruitinised and (if appropriate) removed. Example: The following stripped-down configuration: version 11.1 service timestamps log datetime localtime service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname eg ! clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 enable secret 5 hohoho ! interface ATM5/0 mtu 1500 no ip address no ip route-cache optimum atm ilmi-keepalive 30 atm pvc 999 0 16 ilmi ! interface ATM5/0.2 point-to-point description customer1's network ip address 192.168.24.1 255.255.255.252 atm pvc 502 2 120 aal5snap inarp ! interface ATM5/0.3 point-to-point description customer2's network ip address 192.168.24.5 255.255.255.252 atm pvc 503 2 51 aal5snap inarp ! interface ATM5/0.4 point-to-point description customer3's network ip address 192.168.24.9 255.255.255.252 atm pvc 504 2 52 aal5snap inarp ! interface ATM5/0.5 point-to-point description customer4's network ip address 192.168.24.13 255.255.255.252 atm pvc 505 2 53 aal5snap inarp ! ip name-server 203.97.33.1 ip name-server 203.97.37.1 ip classless ip route 10.1.4.0 255.255.252.0 192.168.24.14 ip route 172.16.0.0 255.255.0.0 192.168.24.6 ip route 172.18.0.0 255.255.0.0 192.168.24.2 ip route 192.168.25.0 255.255.255.0 192.168.24.14 ip route 192.168.27.0 255.255.255.0 192.168.24.42 ! line con 0 exec-timeout 0 0 length 20 line aux 0 line vty 0 4 exec-timeout 0 0 password 7 humhumhum length 25 ! end When run through ios-lint.awk, we get: ! generated by cisco_lint.awk ! version 11.1 service timestamps log datetime localtime service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname eg ! clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 enable secret 5 hohoho ! ip name-server 203.97.33.1 ip name-server 203.97.37.1 ip classless ! line con 0 exec-timeout 0 0 length 20 line aux 0 line vty 0 4 exec-timeout 0 0 password 7 humhumhum length 25 ! interface ATM5/0 mtu 1500 no ip address no ip route-cache optimum atm ilmi-keepalive 30 atm pvc 999 0 16 ilmi ! interface ATM5/0.2 point-to-point description customer1's network ip address 192.168.24.1 255.255.255.252 atm pvc 502 2 120 aal5snap inarp ! ip route 172.18.0.0 255.255.0.0 192.168.24.2 ! interface ATM5/0.3 point-to-point description customer2's network ip address 192.168.24.5 255.255.255.252 atm pvc 503 2 51 aal5snap inarp ! ip route 172.16.0.0 255.255.0.0 192.168.24.6 ! interface ATM5/0.4 point-to-point description customer3's network ip address 192.168.24.9 255.255.255.252 atm pvc 504 2 52 aal5snap inarp ! interface ATM5/0.5 point-to-point description customer4's network ip address 192.168.24.13 255.255.255.252 atm pvc 505 2 53 aal5snap inarp ! ip route 10.1.4.0 255.255.252.0 192.168.24.14 ip route 192.168.25.0 255.255.255.0 192.168.24.14 ! ! ! The following static routes do not point to a connected interface. ! Some of these might be worth looking at more closely :) ! ip route 192.168.27.0 255.255.255.0 192.168.24.42 ! end Much nicer :) Anyway, sorry about all the bandwidth - script is at: http://www.patho.gen.nz/pub/users/jabley/ios-lint.awk Feedback welcome. Share and enjoy. Joe -- Joe Abley <jabley(a)clear.co.nz> I am not speaking for CLEAR. In fact, Network Architect, CLEAR Net I'm not speaking at all. I'm typing. --------- 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: BGP over NZIX
by Warwick GLENDENNING 25 Jan '99

25 Jan '99

Hi Felix Your email implies that you are waiting only for Waikato to implement BGP at NZIX. This does not appear to be a fair call, as no one else on the mailing list that Joe Abley posted to has made any comment on whether they would BGP peer or not at NZIX and especially the largest ISP in NZ Telecom. Regards Warwick -----Original Message----- From: tossan(a)us.ibm.com [mailto:tossan(a)us.ibm.com] Sent: Tuesday, 26 January 1999 08:19 To: WarwickG(a)waikato.ac.nz Cc: abley(a)clear.co.nz; nznog(a)list.waikato.ac.nz; lindsayp(a)agresearch.cri.nz; p.wilson(a)comnet.co.nz; steve(a)webmasters.co.nz; bpearson(a)telstra.co.nz; colinb(a)nz1.ibm.com; skatta(a)nz1.ibm.com; bowden(a)nz1.ibm.com; cholmes(a)telstra.co.nz Subject: BGP over NZIX IBM Global Network position re peering protocol, as explained earlier in teleconf, is we peer exclusively using BGP-4. We see no nationale in using OSPF to collect and distribute interprovider routes. In fact we have started to use BGP Communities within our global Internet BB to direct routes which previously was done by OSPF, thus further reducing OSPF role. Under the NZIX switching network we wish to pursue BGP peerings with all ISPs there who are capable, including Waikato. We await for Waikato to fully implement its BGP capability. Felix Tossan ---------------------- Forwarded by Felix Tossan/White Plains/IBM on 01/25/99 01:59 PM --------------------------- Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> on 01/24/99 07:05:11 PM To: "'Joe Abley'" <jabley(a)clear.co.nz>, Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> cc: nznog(a)list.waikato.ac.nz, "'lindsayp(a)agresearch.cri.nz'" <lindsayp(a)agresearch.cri.nz>, "'p.wilson(a)comnet.co.nz'" <p.wilson(a)comnet.co.nz>, "'steve(a)webmasters.co.nz'" <steve(a)webmasters.co.nz>, Felix Tossan/White Plains/IBM, bpearson(a)telstra.co.nz, colinb(a)nz1.ibm.com, skatta(a)nz1.ibm.com, bowden(a)nz1.ibm.com, cholmes(a)telstra.co.nz Subject: RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

BGP over NZIX
by tossan＠us.ibm.com 25 Jan '99

25 Jan '99

IBM Global Network position re peering protocol, as explained earlier in teleconf, is we peer exclusively using BGP-4. We see no nationale in using OSPF to collect and distribute interprovider routes. In fact we have started to use BGP Communities within our global Internet BB to direct routes which previously was done by OSPF, thus further reducing OSPF role. Under the NZIX switching network we wish to pursue BGP peerings with all ISPs there who are capable, including Waikato. We await for Waikato to fully implement its BGP capability. Felix Tossan ---------------------- Forwarded by Felix Tossan/White Plains/IBM on 01/25/99 01:59 PM --------------------------- Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> on 01/24/99 07:05:11 PM To: "'Joe Abley'" <jabley(a)clear.co.nz>, Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> cc: nznog(a)list.waikato.ac.nz, "'lindsayp(a)agresearch.cri.nz'" <lindsayp(a)agresearch.cri.nz>, "'p.wilson(a)comnet.co.nz'" <p.wilson(a)comnet.co.nz>, "'steve(a)webmasters.co.nz'" <steve(a)webmasters.co.nz>, Felix Tossan/White Plains/IBM, bpearson(a)telstra.co.nz, colinb(a)nz1.ibm.com, skatta(a)nz1.ibm.com, bowden(a)nz1.ibm.com, cholmes(a)telstra.co.nz Subject: RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- 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: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic
by Warwick GLENDENNING 24 Jan '99

24 Jan '99

We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic
by Warwick GLENDENNING 21 Jan '99

21 Jan '99

For our customers we apply community tags to routes so that customers can differentiate between routes learnt from off-shore BGP peers, and those learnt from within NZ - I would imagine that Telecom can do something similar for you. I would keen to hear Telecom NZ view as they seem to have been very quiet on this topic? Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic
by Warwick GLENDENNING 21 Jan '99

21 Jan '99

Waikato has no objection to carriers or ISP's running BGP meshes at the NZIX if it provides a more robust service. However from Waikato's perspective (and possibly for other smaller NZIX users) we would prefer that routers connected to the NZIX also ran OSPF as we use this process to collect NZ routes and differentiate between domestic and international traffic for our campus IP traffic metering.It is possible that other NZIX users do the same. OSPF is also less complex to manage for smaller users with fewer highly skilled network staff. Thanks and best regards Warwick *********************************************************************** Warwick Glendenning NZCE REA Dip.Mgt.St. Network Services Manager Information and Technology Services University of Waikato Private Bag 3105 Hamilton, NZ Tel:07-8384363 Fax:07-8384066 mobile: 025-356121 email:warwickg(a)waikato.ac.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

Re: BGP over NZIX
by Pieren, Jay 20 Jan '99

20 Jan '99

Hi AgResearch is connected to NZIX as well. We provide services for DRC and MIRINZ. Jay Pieren IT Service Manager Phone: ++64-3-489-9080 AgResearch New Zealand Ltd. Fax: ++64-3-489-3739 Invermay Research Centre Mobile: ++64-25-223-4330 Puddle Alley Private Bag 50034 Mosgiel, Otago New Zealand --------- 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: BGP over NZIX
by Dennis Su 19 Jan '99

19 Jan '99

Joe, KC still has a Cisco 3600 connected to NZIX. It could just be used for route collecting but I am not 100% sure. Cheers, Dennis ----------------------------------------------------------------- Dennis Su Msc CNE CCNA Network Engineer, Network Services, ITS, University of Waikato, Hamilton, New Zealand Tel 64 7 838 4183 Fax 64 7 838 4066 Email d.su(a)waikato.ac.nz > -----Original Message----- > From: Tony Wicks [mailto:tonyw(a)iconz.co.nz] > Sent: Wednesday, January 20, 1999 12:11 PM > To: nznog(a)list.waikato.ac.nz > Cc: jabley(a)clear.co.nz > Subject: Re: BGP over NZIX > > > >Did I miss KC? Many apologies if so; do KC have a router at NZIX? > > > No, KC connects to NZIX via us ( ICONZ ). > > Tony Wicks > Network Engineer, ICONZ > > --------- > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog > --------- 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: BGP over NZIX
by Tony Wicks 19 Jan '99

19 Jan '99

>Did I miss KC? Many apologies if so; do KC have a router at NZIX? No, KC connects to NZIX via us ( ICONZ ). Tony Wicks Network Engineer, ICONZ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

BGP over NZIX
by Joe Abley 19 Jan '99

19 Jan '99

Hi people, I would like to gauge interest in the various exchange members at NZIX making a transition from the current OSPF peering mechanism to a BGP4 mesh. The existing OSPF approach is deficient in several areas - I won't list them, as I think there is general agreement that this is the case. OSPF at NZIX seems to be one of those interim measures that, once established, has been difficult to dispense with. Given the relatively small number of networks which connect to the exchange today there is arguably little need to provide a route server or other facilitating infrastructure - a BGP mesh will likely do the job quite nicely. One more more route servers would allow the exchange to scale in future, however, should the BGP mesh become unwieldly. The people who currently connect at the exchange, and to whom this message has direct relevance, are (in no particular order): + Telecom NZ (AS4648) + Telstra NZ (AS4763) + IBM NZ + ICONZ (AS4770) + ComNet + CLEAR (AS4768) + University of Waikato (AS681) + Webmasters (please let me know if I have missed anybody!). I am raising this in the list as it seems to me that the issue has wider interest - for example, any other organisation who is thinking about colocating equipment at Waikato for interconnect/peering. Some points to think about/comment on: + Everybody who wants to peer with more than one network needs a globally-unique autonomous system number (ASN) for BGP. These are available free of charge from APNIC if you are a member. If a transition to BGP is to go ahead, CLEAR (as an APNIC member) is willing to apply for ASNs for any existing exchange members who need them (for the purposes of this transition). We won't be charging anything for this, and you don't need to be a CLEAR customer (although we _will_ want to peer with you). + Everybody who wants to peer needs a router capable of speaking BGP4. Most routers that can talk OSPF can also talk BGP (BGP is way simpler to code!), but the cisco 1600 series are a notable exception. Is this an issue for anybody? + There is a general perception that BGP is a "hard" protocol to configure. I'm not convinced that BGP is any harder to operate than OSPF, but if there is interest/need I'm happy to provide some reference configurations to anybody who needs them. At least 6 of the members on the list above already use BGP elsewhere in their networks. Climbing into a flame-proof suit (better safe than sorry), Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 1

Countdown to APRICOT - the annual ISP Summit for Asia and Pacific (March 1-5 in Singapore)
by Barry Raveendran Greene 16 Jan '99

16 Jan '99

[Apologies for any duplicates. ] ---------------------------------------------------------------------------- APRICOT Registrations open from 4 January 1999 for APRICOT 1-5 March 1999 http://www.apng.org/apricot99/ ---------------------------------------------------------------------------- What is APRICOT? ---------------- The annual Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) is an educational, non-profit, conference run by volunteers to develop and maintain Internet operational stability in Asia Pacific Region. APRICOT's Mission is to develop and advance the skills and understanding necessary to grow a robust Internet infrastructure in the Asia Pacific region. APRICOT is about bringing the world's top Internet experts together with those who can benefit from their knowledge. Since 1996, APRICOT has provided a unique and successful forum for those key Internet builders in the region to learn from their peers and other leaders in the Internet community from around the world. The intense week-long summit consists of seminars, workshops, tutorials, conference sessions, birds-of-a-feather (BOFs), and other forums all with the common goal of : + Spreading and sharing the knowledge required for operational stability and development of the Internet within the Asia Pacific region. + Developing affinity groups that foster mutual support throughout the year. APRICOT's success is due to the excellence of its no-nonsense program focused on the operation of the Internet - technical, business, and policy. Its importance is demonstrated by the fact that it is the only conference in which all of the key Internet operations group in Asia and Pacific meet for the annual and semi-annual meetings. Hence, APRICOT is in reality the critical Internet summit for Asia and Pacific. (see below: APRICOT Week Overview) APRICOT is not an Internet Marketing Conference. APRICOT is about bringing true subject matter experts together with those who can benefit from the information the most. APRICOT provides a unique, vendor neutral forum for frank discussions on the skills and technologies that are either at the heart of today's Internet or very likely to see operational deployment within 12 months. It allows attendees to synchronize with the rapid developments in the wider Internet and an opportunity to dispel market "hype". The people who attend APRICOT are the real people building the Internet in the Asia & Pacific region. Many of best Internet engineers and key decision makers attend APRICOT either to teach, present, or do their own "networking". Where to get more information? ------------------------------ It's all up on the web: http://www.apng.org/apricot99/ or http://www.apricot.net APRICOT Stakeholders -------------------- What makes APRICOT so valuable is the number of groups in the Asia & Pacific Internet Community that come together and co-locate their meetings. Here are a few of the groups co-locating activities for APRICOT99. LINUX User Group - The Singapore LINUX Conference 1999. March 5th - 7th. It will be the first time a conference focussing on Linux is being held in Singapore, let alone Asia. http://www.slc99.linux.com.sg/ Asia Pacific Networking Group (APNG). APNG is an Internet organization dedicated to the advancement of networking infrastructure in this region, and to the research and development of all associated enabling technologies. Its mission is to promote the Internet and the coordination of Network Inter-Connectivity in the Asia Pacific Region. http://www.apng.org APNG will be having it's annual meetings, tutorials, and conference co-located with APRICOT. Asia & Pacific Security Incident Response Coordination WG (APSIRC). APSIRC WG meeting will be held on the evening of 1 March 1999. For more details, please subscribe to the mailing list apsirc(a)apng.org by sending a message "Subscribe" to apsirc-request(a)apng.org or check the web at http://apsirc.singcert.org.sg/ Asia Pacific Network Information Center (APNIC). The NIC project of APNG has led to the formation in 1993 of the Asia Pacific Network Information Center (APNIC). Since the, APNIC has gained independence of APNG and gone from strength to strength to its recent in corporation in 1996. APNIC will be having it's annual general meeting on March 6th. http://www.apnic.net Asia & Pacific Internet Association (APIA). APNG fostered a Commercial Working Group through the mid-1990s. In 1997, this WG spawned off to become the Asia Pacific Internet Association (APIA) of today. APIA membership spans the Internet trade and business communities of the AP region. http://www.apia.org APIA will be having it's annual general meeting on March 6th. Asia & Pacific Top Level Domain Association (APTLD). In view of the urgent need to coordinate and organize the region's country code Top-Level Domain holders. APNG has initiated with other AP organizations to form the APTLD forum which had held its inaugural meeting in July 1998. http://www.aptld.org APPLe - Asia & Pacific Policy and Legal Forum. To promote and facilitate exchange of information and consultations between the Internet industry and governments and regional/international organizations, with the goal of facilitating the balance between industry self-regulation and government regulation. http://www.apng.org/apple/ Internet Corporation for Assigned Names and Numbers (ICANN). The Internet is undergoing some fundamental administrative changes with respect to Internet Domain Names and Internet Protocol Addresses. The Internet Corporation for Assigned Names and Numbers (ICANN) will be having a special meetings and be the #1 topic for the APRICOT Plenary. http://www.icann.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ APRICOT (Asia & Pacific Rim Internet Conference on Operational Technologies) Singapore March 1 - 5, 1999 -- The Annual ISP Operations and Business Summit in Asia and Pacific -- http://www.apricot.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NZNOG - Relevant Events
by Donald Neal 10 Jan '99

10 Jan '99

NZNOG People, If there's enough content for it, I'd like this list ot carry notice of relevant meetings and conferences. Are there any that should be added to these? - Donald Neal January ------- NetWORKS 99: The Third New Zealand ATM and Broadband Workshop Dates: 21-22 January Location: The University of Waikato, Hamilton More: http://byerley.cs.waikato.ac.nz/networks/ April ----- Uniforum NZ '99 Dates: 13-17 April Location: Rydges, Fenton St., Rotorua More: http://www.uniforum.org.nz/ --------- 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 03 Jan '99

03 Jan '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 64 subscribers.) 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 arrange meetings 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

Banned Newsgroups list?
by Simon Lyall 26 Dec '98

26 Dec '98

Just wondering if anyone has the list of newsgroups that Internal Affairs distributed a while back which ISPs are not advised to carry? I think this was done on an unofficial basis and no-one around here seems to have the actual list. I don't carry a large number of the suspect groups but I want to be sure none have been accidentally added. Any pointers welcome. Also wearing one of my other Hats are any sites interested in exchanging newsfeeds for nz.* newsgroups (plus local posts) with usenet.net.nz? . Currently I'm exchanging feeds with a few large ISPs but more is always better. -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Network Admin | Ftpmaster | Home: simon(a)darkmere.gen.nz The Internet Group, Auck. | Asst Doorman | Web: Currently Offline --------- 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: missing router
by Richard Naylor 21 Dec '98

21 Dec '98

At 02:30 pm 21/12/98 +1300, you wrote: >3620 or 40 ? sorry should have mentioned that - a 3640 - the bigger of the two 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

missing router
by Richard Naylor 21 Dec '98

21 Dec '98

Hi folks We have had a Cisco 3600 router removed from our premises in an un-authorised manner - it was nicked. If you get offered a real cheap one with the following config please let me know asap. + no system memory (someone else borrowed it !) + 1x 10/100 ethernet port + 18 Voice ports in a mixed config Unfortunately it was not rack mounted, so was easily removed no crow-bar was required. We also lost a diskless 386 - a DECpc320 configured as a Netramet box, and a Compaq 386 running linux as a secondary DNS server. We are very happy to receive any othe the gear back - no questions asked, rather than see it all go into the harbour. Happy Christmas 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

Workshop on Broadband Networks January
by John G. Cleary 21 Dec '98

21 Dec '98

Hello, I have included below an adverstisment for a workshop on broadband networksthat will be heldat Waikato University on january 21st and 22nd. If you think this would be of interest to anyone within your comapny or any of your customers could you please circulate it. Thank you, John Cleary John G. Cleary Dept. Computer Science, Ph(work): 64(7)838-4378 University of Waikato, Ph(home): 64(7)855-0965 Te Whare Wananga o Waikato, Fax: 64(7)838-4155 Private Bag 3105, e-mail: jcleary(a)cs.waikato.ac.nz Hamilton, New Zealand URL: http://www.cs.waikato.ac.nz/cs/Staff/jgc.html =================================================== Networks-99 sponsored by WAND (Waikato Applied Network Dynamics) Research Group The University of Waikato 21 - 22 January 1999 On the 21st and 22nd January 1999 the third New Zealand ATM and Broadband Workshop will be held at the University of Waikato in Hamilton. The workshop is a forum for the discussion and dissemination of information, ideas and research into broadband issues, including the Internet. Topics at previous workshops have ranged from connecting a doorbell to an ATM network to the statistics of self-similar traffic on the Internet. The first day of the conference comprises two tutorials entitled "Introduction to TCP/IP" and " The Ubiquitous Internet as Seen from Silicon Valley". The second tutorial will be presented by Dr. David Jefferson from the Compaq Network Systems Laboratory at Palo Alto. The second day will contain presentations from Industry in the morning followed by research papers in the afternoon. The cost is $100 for each tutorial and $50 for the conference itself. For further information see "http://byerley.cs.waikato.ac.nz/networks/", email "mailto:NetWorks(a)cs.waikato.ac.nz" or phone +64 7 838 4021. =========================================== John G. Cleary Dept. Computer Science, Ph(work): 64(7)838-4378 University of Waikato, Ph(home): 64(7)855-0965 Te Whare Wananga o Waikato, Fax: 64(7)838-4155 Private Bag 3105, e-mail: jcleary(a)cs.waikato.ac.nz Hamilton, New Zealand URL: http://www.cs.waikato.ac.nz/cs/Staff/jgc.html --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Advance notice for 1q99 walk
by bmanning＠ISI.EDU 20 Dec '98

20 Dec '98

Hi, I appologize for duplicates. Its almost time for the next quarterly walk of the inverse tree of the DNS. For the last few quarters, I've been walking the in-addr tree looking for numbers of delegations, accurate delegations, and types and styles of error conditions. So... this is a heads up that you will be seeing zone transfers being generated by a couple of the collecter machines here. For those of you who utilize BINDs access controls, I'd appreciate your inclusion of the collector machines in allowed transfers. The expectation is that they will be the following IP addresses: 128.9.160.57 and 198.32.4.13 If there are any questions or concerns, I'd be happy to talk about them. Past data has been presented at IEPG, Apricot and RIPE meetings. The expectation is that future data will be presented in the same and similar forums. The expected start date is 01jan99 and it is expected to run through February 1999. The 4q98 and preliminary data for the 1q99 audits will be presented at Apricot99 in Singapore. www.apricot.net for details about this venue. The data will be available via http as well. www.isi.edu/div7/people/bmanning.home/in-addr-audit.html --bill --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Workshop on Broadband Networks January
by John G. Cleary 20 Dec '98

20 Dec '98

Networks-99 sponsored by WAND (Waikato Applied Network Dynamics) Research Group The University of Waikato 21 - 22 January 1999 On the 21st and 22nd January 1999 the third New Zealand ATM and Broadband Workshop will be held at the University of Waikato in Hamilton. The workshop is a forum for the discussion and dissemination of information, ideas and research into broadband issues, including the Internet. Topics at previous workshops have ranged from connecting a doorbell to an ATM network to the statistics of self-similar traffic on the Internet. The first day of the conference comprises two tutorials entitled "Introduction to TCP/IP" and " The Ubiquitous Internet as Seen from Silicon Valley". The second tutorial will be presented by Dr. David Jefferson from the Compaq Network Systems Laboratory at Palo Alto. The second day will contain presentations from Industry in the morning followed by research papers in the afternoon. The cost is $100 for each tutorial and $50 for the conference itself. For further information see "http://byerley.cs.waikato.ac.nz/networks/", email "mailto:NetWorks(a)cs.waikato.ac.nz" or phone +64 7 838 4021. =========================================== John G. Cleary Dept. Computer Science, Ph(work): 64(7)838-4378 University of Waikato, Ph(home): 64(7)855-0965 Te Whare Wananga o Waikato, Fax: 64(7)838-4155 Private Bag 3105, e-mail: jcleary(a)cs.waikato.ac.nz Hamilton, New Zealand URL: http://www.cs.waikato.ac.nz/cs/Staff/jgc.html --------- 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: Appeal to end-users regarding IP address aggregation -Document posting comments -Reply
by Michael Newbery 09 Dec '98

09 Dec '98

> > >>>> Donald Neal <Donald.Neal(a)telecom.co.nz> - 10/12/98 11:57 AM >>> >Craig Anderson at 10/December/1998 10:36am wrote: >[...] >>There are other problems, but i'm not entirely sure of the nature of >>this document, nor it's audience. I suspect Telecom intends to >>distribute this much wider than just to it's clients. The implied >>support from NZNOG for all of the statements contained within bothers >>me. > >I for one hope a document more or less like this is to be widely >distributed. > >In general it's desirable to avoid claiming NZNOG supports things, since >NZNOG isn't an organisation with a process for declaring the >organisation's opinion on something. However, if the meeting minutes >already posted to this list are accurate, many active NZNOG participants >do support the aproach outlined. In that case replacing the existing text >with a reference to "many members of NZNOG" or "acting in consultation >through the New Zealand Network Operators' Group" would make me >happier, but wouldn't make a difference to the average recipient. Which is fine, until it gets reported in the press in a more concise form, as "support from NZNOG" rathrer than the more precise but less snappy "support from many members of NZNOG" or so forth. Not that there is much that can be done about the vagaries of reporters. The problem is surely that NZNOG is a mailing list, no more. We exist to get things done, not to make pronouncements :-) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: Appeal to end-users regarding IP address aggregation - Document posting comments -Reply
by Donald Neal 09 Dec '98

09 Dec '98

Craig Anderson at 10/December/1998 10:36am wrote: [...] >There are other problems, but i'm not entirely sure of the nature of >this document, nor it's audience. I suspect Telecom intends to >distribute this much wider than just to it's clients. The implied >support from NZNOG for all of the statements contained within bothers >me. I for one hope a document more or less like this is to be widely distributed. In general it's desirable to avoid claiming NZNOG supports things, since NZNOG isn't an organisation with a process for declaring the organisation's opinion on something. However, if the meeting minutes already posted to this list are accurate, many active NZNOG participants do support the aproach outlined. In that case replacing the existing text with a reference to "many members of NZNOG" or "acting in consultation through the New Zealand Network Operators' Group" would make me happier, but wouldn't make a difference to the average recipient. - Donald Neal --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Revision to Acceptable Use Policy?
by Donald Neal 09 Dec '98

09 Dec '98

People, The following is a revised version of the posting I send to this list each month, including an acceptable use policy revised as proposed by Joe Abley with some wording changes by me. Are there any objections to the policy in the form in which it appears below? - Donald Neal - - - - - 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 62 subscribers.) 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 arrange meetings 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

2 1

Re: Appeal to end-users regarding IP address aggregation - Document posting comments
by craig＠laptop.iprolink.co.nz 09 Dec '98

09 Dec '98

Hi. I include the document in a reasonable format below. I'm concerned about several things in this document. One being, this idea of International and National ISPs and the naming of a set of ISPs as this seems to be included only for commercial reasons and is seriously misleading. >From the document: > It is estimated that the frequency and impact of dampening and > filtering by overseas suppliers will increase over the next few years > to the point where un-aggregated address space cannot be guaranteed to > have reliable connectivity or be routed internationally. This is, at best, misleading. At worst it's simply untrue. There is no reasonable basis on which to make such an estimation. There are other problems, but i'm not entirely sure of the nature of this document, nor it's audience. I suspect Telecom intends to distribute this much wider than just to it's clients. The implied support from NZNOG for all of the statements contained within bothers me. -Craig ---------- Date XXX XXX Customer Company Private Bag YYY City Dear XXX An Appeal to Internet Users in NZ - IP Address Aggregation International ISP's in New Zealand are working closely with APNIC as well as many other ISPs, to consolidate existing IP addresses into internationally aggregated, routable blocks. This initiative is recognised by the New Zealand Network Operators' Group (NZNOG), International Internet numbering authorities such as APNIC and IANA, and ISP's world-wide, as being necessary for the good of the Internet as a whole, and will help ensure reliable connectivity for all New Zealand Internet users. This is an appeal for end-user organisations to get behind the drive to tidy up New Zealand allocated Internet address space. Internet address space is a globally managed resource, administered by the Internet registry system for and on behalf of the Internet community as a whole. The Asia Pacific Network Information Centre (APNIC) is the regional body that allocates IP addresses for the South Pacific area, including New Zealand. APNIC is one of 3 Regional Internet Registries, which operate under the auspices of the Internet Assigned Numbers Authority (IANA), providing allocation and registration services that support the operation of the Internet globally. APNIC provide addresses to International ISP's such as Telecom, Telstra, IBM, The Internet Group and Clearnet, for sub-allocation to ISPs or customers around the country. Each downstream ISP can then assign the addresses to their end-user customers. APNIC also allocate directly to multi-homed ISPs or companies requiring large amounts of IP address space, such as /19 (32 Class C's) or larger. Address space is allocated to meet documented requirements and when the address space is no longer required, the address space should be returned to the allocating organisation. As such, historical and current Internet registry policy does not recognise the concept of address "ownership" or the buying and selling of address space. All IP address allocations are registered with APNIC and the end-user details on the APNIC database must be updated regularly. There is a responsibility on the International ISP's to ensure this occurs, as it is an important part of the procedure to maintain efficiency in allocations and to obtain additional address space. On behalf of the Internet community within New Zealand, we are asking for your help to allow us to aggregate overseas Internet advertisements as much as possible. If you have addresses from a previous supplier, and now use a different International ISP, it is in your own interest as well as best Internet practises, to return those addresses to the previous supplier. These addresses will be re-distributed to other customers, whilst your current International ISP will provide new IP addresses for your network. It must be stated that this is entirely voluntary, and if individual companies choose not to renumber at this time, for any particular reason, it is entirely their choice. However, it should also be stated that it is estimated that connectivity may be less reliable in the future and extended outages may become more frequent unless your company's addresses are being advertised in aggregatable or large blocks. Reasons for this forecast are detailed in the following Q&A section below. This letter is intended to start an education process on the issues surrounding IP address advertisement on the Internet. It is in every user's "best interest" to keep routing tables as simple as possible by advertising international routes efficiently. To do this, every administrator of registered IP address space has the responsibility to act in the best interests of Internet users, and respect the global issues of route advertisements and portability of IP addresses. I have attached some questions and answers that may help you to understand the background and necessity for the changes. If you have any further questions you should contact your ISP or upstream provider. Additional supporting information can be found at http://www.your-website.yyy.nz Yours sincerely YYY Title Organisation Contact phone number Questions Question: What are the issues? IP addresses, allocated by APNIC to each International ISP, need to be advertised from that particular supplier's gateway, allowing large blocks of addresses to be advertised to the Internet with maximum routing efficiency. This process is called supernetting or route aggregation using Classless Inter-Domain Routing (CIDR). Documentation on the need for route aggregation can be found at: http://search.ietf.org/internet-drafts/draft-ietf-idr-aggregation-tuto rial-01.txt. International Internet routing can be very complex, leading to large routing tables and router limitations being stretched. Many customers are trying to move the addresses they are using to different gateways, breaking down the maximum block size and causing routing tables to increase in size. The problem is Global in scope and is not just in New Zealand. One way to provide "Internet friendly" advertisements is for provider dependent IP addressing. This means non-portable IP addresses between International ISP's, and is the current APNIC policy for address assignments within NZ. Problems are foreseen due to memory limitations and CPU performance on current backbone routers that are stretched because of the sheer number of routes required to advertise the large number of networks. If customer XXX moves from International ISP A to International ISP B, and continues to use the same IP address range, Int.ISP A must now advertise two smaller blocks, as well as advertising the larger block (supernet), increasing the table size. The route table of Int.ISP B also increases with the advertisement of the new range. Overseas supplier's routers then need to handle both increases (increased advertisements from A and B) on their route table. As additional customers move to and from suppliers, the effect increases, until memory limits on individual routers are reached. When limits are reached on individual routers, filtering can be implemented to ensure the more specific, longer prefix, (or smaller) routes can be dropped to enable the router to carry on operating. Also, when networks have connectivity problems, the overseas supplier can configure dampening to occur. This shuts off access for that network for extended periods, and is typically much longer for small networks than for larger networks. Documentation on route-flap dampening parameters can be found at: http://www.ripe.net/docs/ripe-178.html It is estimated that the frequency and impact of dampening and filtering by overseas suppliers will increase over the next few years to the point where un-aggregated address space cannot be guaranteed to have reliable connectivity or be routed internationally. Question: If nothing is done, what is likely to happen? If present trends continue we may not be able to obtain more IP address space for distribution within New Zealand, and we may be unable to route non-contiguous Class C networks internationally. This will negatively impact service for all customers using Provider Independent (PI) address space which are small and not aggregatable. Documentation on the comparison between Provider Independent (PI) and Provider Aggregatable (PA) address space can be found at: http://www.ripe.net/docs/ripe-127.html Question: What can we do about it? The only way to minimise New Zealand routes negatively impacting on the Internet in the future is to advertise New Zealand routes in contiguous blocks (supernets). The larger the blocks the better. Because routes emanating from New Zealand are currently fragmented between International ISP's, the routes must be consolidated (aggregated) into contiguous blocks. To achieve this, we need to work together to convert current network address schemes into PA address space. Each IP address allocation and assignment must be provided as non-portable, and existing IP address assignments should be renumbered into the aggregated blocks. The Internet is a self regulated organism and as such is driven entirely by it's end-users. To ensure reliable connectivity in the future for all users, some changes may have to take place from time to time as the Internet develops and matures. Some of these changes may be harder for certain user's than for others to implement, but we would ask for your support in doing what will benefit the vast majority of users. Question: Does this affect me? This appeal may affect you if your network uses IP address space supplied by someone other than your current International ISP, and will affect all New Zealand organisations by the ongoing allocation of IP addresses. We would request that all IP addresses from previous International ISP's should be returned to that supplier, or directly to APNIC. Your current supplier will work with you to supply you with the equivalent address space (in a contiguous block). Your company may have to look at renumbering their network. Renumbering has no effect on Domain Names or Email addresses other than behind the scenes configuration, so business cards and stationery should not be affected. Documentation covering the need to renumber can be found at: http://sunsite.hr/cgi-bin/rfc/rfc1900.txt and http://sunsite.hr/cgi-bin/rfc/rfc2008.txt Question: What are my options if my company has to renumber? There are many options available, but some may not be viable for your companies requirements. We hope you will spend some time researching the pro's and con's of each option, and act in the best interests of New Zealand Internet users, and in the spirit of global Internet best practises. The various options include: 1. Implement a firewall for your company. This means you can keep the numbering scheme you are using and not have to renumber. All access to the network can be through a firewall, for enhanced security, and you will only need a handful (at the most) of new registered IP addresses. The old registered IP addresses will be able to be returned to the original supplier. The network will effectively be on a private numbering scheme, interfacing with the Internet registered addressing scheme by means of a network address translation (NAT) mechanism. The benefit of this method is independence from supplier's numbers (apart from the external firewall addresses) which means swapping suppliers in the future will not impact you nearly as much. NAT technology is improving all the time and allowing more flexibility than in earlier versions. 2. Apply NAT functionality or Web-proxy functionality without a firewall. This gives you Internet access without having to renumber your existing network. You may want to review your network security. 3. If you use dynamic IP allocation techniques such as DHCP for your network, the amount of work required to renumber is greatly reduced. Reconfiguring your DHCP server and rebooting network devices will renumber your devices automatically. You may still require several new static IP addresses for devices which support DHCP technology i.e. for devices such as nameservers on production networks you may still require several new static IP addresses. 4. Unfortunately, if you have static IP addressing throughout your network, and your network does not easily support either NAT or DHCP reconfiguration, you may have to manually renumber your network. 5. If your company is using large amounts of IP address space, such as /19 (32 Class Cs) or larger, you can approach APNIC directly, requesting your own provider independent IP address block. Question: Who is driving the changes? * International Internet numbering authorities such as IANA, APNIC, RIPE and ARIN recommend "Best Internet Practises" be maintained by all suppliers of Internet services. * Within New Zealand, International ISP's such as Telecom, Telstra, Clear, The Internet Group, and IBM are supporting the initiative, along with national ISP's, all of whom sub-allocate IP addresses under APNIC policy. * Internet user's world-wide benefit by New Zealand successfully implementing these changes. There does need to be a combined and rational approach to the problem, so International ISP's, national ISP's and end-users will need to work closely and communicate effectively to co-ordinate the changes as they take place. Question: Whom can I contact to get more information? Your ISP or upstream Internet Service Provider should be able to help with any questions regarding renumbering. Your International ISP will also be able to help you by supplying new contiguous IP address blocks. Additional supporting information can be found at http://www.netgate.net.nz, which has references to the latest APNIC RFC's and policy documentation regarding IP address allocations (such as RFC 2050). Contact can also be made directly with APNIC at http://www.apnic.net for IP address allocation request forms and further information. --------- 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: Appeal to end-users regarding IP address aggregation - Docume nt posting comments
by Warwick GLENDENNING 09 Dec '98

09 Dec '98

Hi As a user of this list I am getting tired of these remarks about the posting of documents in certain formats. If you have a problem with a message that has been posted please direct it to the person concerned, NOT the list so the author can fix it instead of lambasting the author on this list, otherwise your comments serve no useful purpose. Thanks Warwick Glendenning Network Manager - University of Waikato -----Original Message----- From: Andy Linton [mailto:asjl(a)netlink.net.nz] Sent: Wednesday, 9 December 1998 04:29 To: Brett Telfer Cc: nznog(a)list.waikato.ac.nz Subject: Re: Appeal to end-users regarding IP address aggregation Brett Telfer wrote: > > Hi all, > > Following on from the meeting at Cisco on the 27th Nov, I have attached > an updated letter which includes suggested input from APNIC. > > This document (or at least the information it contains) can hopefully be > distributed around all end-users as the start of an educational > programme aimed at raising peoples awareness of current IP addressing > issues. > > I have tried to make it as "neutral" as possible, but there may be pieces of > "Telecom centric nature" that slipped past, so if anyone has issues with > these please delete, cut and paste, bastardise etc as necessary. > Apologies also for any inaccuracies that may be present. > Brett, It looks like stuff of a 'Microsoft centric nature' has slipped past. Please can we have this is a non proprietary format? andy -- Mailto:Andy.Linton(a)netlink.net.nz Tel: +64 4 494 6162 Post: Netlink, PO Box 5358, Lambton Quay, Wellington, New Zealand -- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 5

RE: Appeal to end-users regarding IP address aggregation - Docume nt posting comments
by Warwick GLENDENNING 09 Dec '98

09 Dec '98

I will second that Warwick -----Original Message----- From: Joe Abley [mailto:jabley(a)clear.co.nz] Sent: Thursday, 10 December 1998 09:48 To: Dean Pemberton; Andy Linton; nznog(a)list.waikato.ac.nz Cc: jabley(a)clear.co.nz Subject: Re: Appeal to end-users regarding IP address aggregation - Document posting comments On Thu, Dec 10, 1998 at 07:29:14AM +1100, Dean Pemberton wrote: > On Wed, Dec 09, 1998 at 07:13:56AM +0000, Andy Linton wrote: > > I'm happy to leave this alone IFF we all agree that we desist from > > posting Word etc docs. > > I move that we make this an addition (suitable worded) to the charter of the > NZNOG list. How about: + Postings to the list should be in ASCII or MIME encoded as text/plain. No attachments of any kind should be sent to the list. If it is required to present a document, a suitable URL for the document may be referred to. For documents that are of general interest, proprietary file formats are discouraged. and also + Breaches in list etiquette (e.g. including attachments) should be dealt with privately with the offending list user, and should not involve complaints being sent to the list. > Anyone second that? Me too :) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0