November 1998 - NZNOG - lists.nznog.org

list.waikato.ac.nz Has Moved
by Donald Neal 11 Dec '24

11 Dec '24

NZNOG-People, I have just finished migrating all of the mailing lists held at The University of Waikato from one server to another. I don't have any reason to believe that anything's gone wrong, but please bear with me for today if it turns out that something has. - Donald Neal -- Donald Neal | Q: How many Aucklanders does it take to change Systems Programmer/Analyst | a light bulb? The University of Waikato | A: Pass me that candle and I'll tell you. Hamilton, New Zealand | --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

Re: legal issues, courts etc
by craig＠laptop.iprolink.co.nz 30 Nov '98

30 Nov '98

Hi. Can someone post some details on the outcome of Friday's meeting for those who could not attend or had to leave early. Thanks, -Craig --------- 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: legal issues, courts etc
by 2Day Chief Enthusiast 30 Nov '98

30 Nov '98

>Can someone post some details on the outcome of Friday's meeting for >those who could not attend or had to leave early. The lunch provided by CISCO was absolutely *fantastic* !! Roger was seen taking orders for lots of kit as a result :-) 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

1 0

Re: legal issues, courts etc
by Chris Wedgwood 26 Nov '98

26 Nov '98

On Thu, Nov 19, 1998 at 02:20:54PM +1300, Don Stokes wrote: > apnic-011 already says that, at least for addresses allocated in > the NZGate timeframe. I haven't found any other APNIC document > (expired or not) that states APNIC policy toward address ownership. Assuming we all follow this then -- do we have allow people or users with small (eg. /26) networks to take them with them should they decide to move? Allowing this _without_ any constraints would make fragmentation horrific. > Do you have a clause in your service contracts that states > explicitly what the position is regarding IP numbers you assign to > clients? Most ISPs do (and all should). No idea... I speak only for myself, not for any company. I don't look at the legal bits where possible, thats what marketroids and legal people are for. > Does it matter? Yes. If someone is allocated address space for which they are not specifically told whether or not it should be considered portable or not, and therefore they wish to take the network with them when they move providers, we could get considerable fragmentation when many people with small networks do this. > It does if anyone is allocating address space in new blocks without > explicitly stating the "ownership" of addresses, but for the old > addresses it just means that at worst the routing table space taken > up by old addresses doesn't get any smaller. I don't follow; surely we have a situation where providers in the past have carved up a say /20 for clients -- and when a client moves this /20 might then need to become sixeteen /24 routes (or a /21, a /22, a /23 and two /24 or whatever). > It also matters if an ISP wants to move a bunch old /24 prefixes > over to an upstream provider that refuses to deal with them -- so > far the ones that have made noises about refusing small netblocks > this have backed away from that position. Eventfully as enough /24 are freed up, we will be able to coalesce adjacent ones into large networks. > What can be done as a technical group is to develop a consensus on > how to retire old /24 prefixes and aggregate them into larger > blocks, either through the APNIC's return policy (apnic-072), or > through some local arrangement, without grossly impacting on either > ISP or customer operations. This seems like a good idea. > I think the first step in this is to get the "ownership" issues > aired (I don't think it will be "solved") at the ISOCNZ conference > tomorrow; at least then hopefully we'll have some idea of what > various positions are. I don't think the ex-NZGate issue can be > really proceeded on without that. Can someone who attends this meeting then please provide some feedback? -cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 9

Re: Anyone got a crowbar?
by 2Day Chief Enthusiast 25 Nov '98

25 Nov '98

>> A rhetorical question: why does cisco rack mount equipment need a >> crowbar to install? I recall a similar problem years ago when in broadcast engineering environment. Except in those days the gear worked perfectly on the floor, but when bolted into that precision peice of engineering known as a rack, it started to play up. If you ever did your job really well and tied back the cables neatly so others could tell you were a professional, it was sure to stop. Just be thankful that even after your crowbar adjustment, your router still goes! 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

1 0

Anyone got a crowbar?
by Michael Newbery 25 Nov '98

25 Nov '98

A rhetorical question: why does cisco rack mount equipment need a crowbar to install? Would it really be SO difficult to make the cases 2mm narrower so that when the mounting brackets are fitted they slide into the rack rather than having to be forced? Mild steel is a wonderful engineering material characterised by its ability to gracefully deform under stress, but that doesn't mean I have to enjoy watching it do so. Mumble. -- Michael Newbery Technology Manager Saturn Communications Tel: +64-4-939 5102 Mobile:021-642 957 Fax:+64-4-939 5100 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

FW: Let's look into ICANN Participation from Asia and Pacific Region
by Barry Raveendran Greene 25 Nov '98

25 Nov '98

[Sorry for the duplicates.] FYI - for those not on one of the AP* Groups mailing list (APNIC, APIA, APNG, APPLe, APTLD). -----Original Message----- From: owner-apia-board(a)apia.org [mailto:owner-apia-board(a)apia.org] On Behalf Of Kilnam Chon Sent: Thursday, November 26, 1998 8:47 AM To: apstar(a)apng.org Subject: [APIA-BOARD] Let's look into icann participation from ap region ICANN "made" the agreement with NTIA to be recognized.(See NTIA homepage) ICANN is looking for participation of Membership Advisory Committee, which is being newly created.(will attach the announcement) DNSO(and possibly other SOs; ASO, PSO) will look for participation of various stakeholders(associations, organizations, individuals,...).(will attach memos) Hope to see appropriate participation to various ICANN committees from AP regions. my idea is as follows; 1. ICANN Membership Advisory Committee each relevant AP organizations to volunteer at least one person: apng, apia, apple, apricot,...(more) 2. DNSO APIA for ISP/Telco Constituency APNG(?) and others for General Business(for- and non-profit) APNG(?), APRICOT, APPLe,.. for At Large chon ____________________________________________________________________________ __ >From iana-announce-owner(a)ISI.EDU Thu Nov 26 04:15:01 1998 Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by cosmos.kaist.ac.kr (8.9.1a/8.9.1) with ESMTP id EAA23586 for <chon(a)cosmos.kaist.ac.kr>; Thu, 26 Nov 1998 04:14:58 +0900 (KST) Received: (from majordom(a)localhost) by zephyr.isi.edu (8.8.7/8.8.6) id KAA28440 for iana-announce-outgoing; Wed, 25 Nov 1998 10:08:12 -0800 (PST) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id KAA28435 for <iana-announce(a)zephyr.isi.edu>; Wed, 25 Nov 1998 10:08:11 -0800 (PST) Received: from ode.isi.edu (ode-e.isi.edu [128.9.160.68]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA03177; Wed, 25 Nov 1998 10:08:10 -0800 (PST) From: Internet Assigned Numbers Authority <iana(a)ISI.EDU> Received: (from iana(a)localhost) by ode.isi.edu (8.8.7/8.8.6) id KAA29487; Wed, 25 Nov 1998 10:08:09 -0800 (PST) Date: Wed, 25 Nov 1998 10:08:09 -0800 (PST) Message-Id: <199811251808.KAA29487(a)ode.isi.edu> To: iana-announce(a)ISI.EDU Subject: ICANN Membership Advisory Committee Cc: iana(a)ISI.EDU X-Sun-Charset: US-ASCII Sender: owner-iana-announce(a)ISI.EDU Precedence: discussion Status: RO Content-Length: 3512 Lines: 75 ICANN Membership Advisory Committee- Expressions of Interest Sought by 5 December, 1998 The ICANN Bylaws call for a membership structure to be established to elect At Large directors. (See Bylaws Article V, Section 9(c)) The Initial Board is establishing an advisory committee (see Bylaws Article VII, Section 3(c)) to advise it on the appropriate membership structure to satisfy the need for world wide representation on the board, and in particular how to create a diverse and open membership without subjecting the corporation to undue risk of capture by any particular interest group. The advisory committee will consist of up to ten members, and will include Initial Board members George Conrades as Chairman, and Greg Crew. The Berkman Center for Internet and Society at Harvard Law School has agreed to provide assistance to the committee, including an independent study of membership issues. Expressions of interest are invited from individuals willing to serve on this committee, which will address specific issues including but not limited to: a) membership structures and arrangements that will provide a world wide representative body to nominate and elect the 9 At Large ICANN board directors (with the goal of recommending three to five options to the ICANN Board). b) appropriate rights and obligations of members, including membership application and registration requirements, membership fee structures, liability limitation of members, and voting rights and procedures. c) requirements and procedures for various forms of membership, including individual, corporate and association. d) efficient procedures for members to nominate and participate in the election of At Large directors, and to participate in general meetings of the corporation. The work of the advisory committee will be open and inclusive of all members of the Internet community. Draft and final recommendations will be posted on the ICANN web site, and suggestions and comments via the Internet will be invited from interested parties. Recommendations from the committee will be subject to the notice and comment procedures set forth in the Bylaws, Article III, Section 3. The ICANN Board will select the committee with the goal of assembling a diverse and broadly representative group. Expressions of interest to participate are to be directed to msvh(a)icann.org, by midnight, 5 December, 1998, US west coast time. Applicants are requested to state what contribution they would expect to make towards the work of this committee; such statements need not be more than 100 words. The committee will commence work in December, 1998. Most of the work of the committee will be conducted via phone or the Internet. A final meeting is planned to be held in Singapore on 1 March, 1999, to prepare a report to the ICANN board by the end of March. Committee members will be expected to devote sufficient time to the work of the committee to achieve this very tight schedule. Pending the identification of an ICANN funding mechanism and the actual receipt of funds, ICANN's resources to support meeting and travel expenses of its committees is very limited. We ask that committee members assist us by assuming personal responsibility for their travel expenses, if possible. We will facilitate phone participation in face-to-face meetings as necessary. Contact: Molly Shaffer Van Houweling Senior Advisor to the President and CEO Staff to the Advisory Committee on Membership ICANN msvh(a)icann.org ____________________________________________________________________________ ___ 1998.11.24 Summary report of Monterey DNSO Meeting --------------------------------------- The second DNSO formulation consultation meeting was held in Monterey, Mexico in 1998.11.15-17. This is the informal summary report of the meeting. See www.dnso.org for the meeting minutes. 1. Around 40 people participated the meeting, similar to the first meeting in Bercelona in October 1998. Participation from Asia-Pacific was very small. Some trademark organizations such as INTA and CASIE participated, but not ICC nor WIPO. gTLD registries such as NSI/InterNIC did not participate this time either even though NSI participated the ad hoc meeting in Boston in the previous week. 2. We had (rough) consensus on structure, representation and funding this time, and decided to proceed to submit the application to ICANN by the end of this year as recommendated by ICANN. Others may be applying, too. 3. DNSO structure and each constituency's representation to Names Council are as follows; Names Council as the executive committee of DNSO 5 Constituencies 21 Registry 3+3 Registrar 3 Infrastructure and Connectivity Providers(ISP, Telco,..) 3 General Business(for- and non-profit) 3 Trademark 3 At Large(Other organizations and individuals) 3 Fair Hearing Panel(Option) 4. We set up the following teams to carry on the future work for DNSO formulation. Transition Team Articulation, Liaison, Outreach Drafting Team Minutes and Application Document We agreed to particularly emphasize on the outreach to include as many stakeholders as possible to DNSO. [hope many AP* organizations to participate in various constituencies of DNSO.] Remark: The next ICANN Meetings will be held in March 1999 in Singapore along APRICOT, and 3 Supporting Organizations(Domain Name, Address, and Protocol) are expected to be official approved then. The detail will be announced shortly.(www.icann.org) We need to agree with other major stakeholders such as NSI and ICC prior to submission of the DNSO application to ICANN, or we will be forced to coordinate after the application submission. ____________________________________________________________________________ ___ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Additional
by Joe Abley 25 Nov '98

25 Nov '98

Why do I always do that? Document is attached, this time.

1 0

revised draft for NZGATE addresses
by Joe Abley 25 Nov '98

25 Nov '98

I have made some fairly rough and ready changes to my initial draft (now over a month old) based on feedback received through this list. This is still just "one possible solution". No flames please. I have not been able to spend as much time as I would like polishing this and thinking about the issues, since I've been working on this at nice -20 with frequent context switching :) Consider this very drafty but a possible starting point for the meeting tomorrow in Auckland. Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: Anyone got a crowbar?
by Michael Newbery 25 Nov '98

25 Nov '98

My racks don't have skins---no need since they are in a nice secure blockhouse---and I like the all-around access, but if I used racks I'd have to seismically brace the units (i.e. tie them to the shelves). Besides, it offends me that they do quite a nifty job with the rack mount kits---one size fits all: front/centre/rear/wall mount @19" or 23"---and then I need a jemmy to install the box. At least the PCMCIA slot on recent units is accessible (unlike on the 25xx series, oops). --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0