October 2002 - lir-wg - mailman.ripe.net

[lir-wg]Election of chairs to the lir-wg - call for nominations
by Hans Petter Holen 13 Dec '02

13 Dec '02

Dear wg, As mentioned at the last wg-meeting, one of the co-chairs, James Alderidge, has started working for the RIPE NCC, and as one of the unwritten rules of the LIR-wg is that it should be chaired by non RIPE NCC staff, James is no longer serving as a co-chair of this wg. Last time we had an election the wg deceided that one chair and two co-chairs was suitable. As I find it good practice to hold an open election from time to time I propose that we do an election for all 3 chairs. I would like to propose to the WG that we do a open nomination process on the lir-wg list up until lets say one month before the next RIPE meeting (27 to 31 January 2003) for chair and two co-chairs and that we do the chair election at the next wg meeting in Amsterdam. This should give the wg a good opportunity to discuss potential candidates. Best Regards, Hans Petter Holen lir-wg chair.

3 3

Re: [ipv6-wg@ripe.net] IPv6 TLAs for mobile operators
by leo vegoda 15 Nov '02

15 Nov '02

[Note: <lir-wg(a)ripe.net> cc'd as this relates to policy] Andreas, On Thu, Oct 31, 2002 at 06:31:06PM +0100, Andreas.Schmid1(a)swisscom.com wrote: Re: RE: [ipv6-wg(a)ripe.net] IPv6 TLAs for mobile operators [...] > RFC3314 says on page 14: > "Because multiple IPv6 hosts may attach through a 3GPP handset, the IPv6 > WG recommends that one or more /64 prefixes should be assigned to each > primary PDP context." > > But I really don't want to concentrate on that discussion. I want to > know if RIPE NCC accepts IPv6 TLA requests from mobile operators only > having GPRS/UMTS/WLAN customers - and therefore not providing > connectivity to organisations with a /48. > -> if anybody can clarify this, I would be very happy! The RIPE NCC implements the RIPE community's policy as described in the IPv6 Address Allocation and Assignment Policy. The policy was agreed at the RIPE 42 meeting in May. An LIR submitting a request for an initial IPv6 allocation will need to meet all four requirements specified in the policy. <http://www.ripe.net/ripe/docs/ipv6policy.html#initial_criteria> Kind regards, -- leo vegoda RIPE NCC Registration Services

6 5

New Document available: RIPE-261
by RIPE NCC Document Announcement Service 31 Oct '02

31 Oct '02

[Apologies for duplicate mails] New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Ref: ripe-261 Title: IPv6 Address Space Management Author: Paul Wilson, Raymond Plzak, Axel Pawlik Date: 31 October 2002 Format: PS=27246 TXT=13567 Obsoletes: Obsoleted by: Updates: Updated by: Short content description ------------------------- The "IPv6 Address Space Management" document provides the management process for IPv6 global unicast address space whereby address allocations are made from a single global pool according to a "sparse allocation" algorithm. This allocation process will maximise aggregation of address space, ensuring that most ISPs retain a single prefix as they grow, and avoiding the address space fragmentation which results from the current IPv4 allocation technique. This document also describes the registration process and the administration of the IP6.ARPA domain. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via our website. "IPv6 Address Space Management" is available at the following URL: http://www.ripe.net/ripe/docs/ipv6-sparse.html The RIPE document store is also available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-261.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-261.txt plain text version

1 0

Summary of ERX-TF discussion
by leo vegoda 29 Oct '02

29 Oct '02

Dear Colleagues, As promised, here is a summary of the short discussion had on the <erx-tf(a)ripe.net> mailing list over the last few weeks. There have been about 15 messages in total. On 10 October we published the RIPE NCC's proposed ERX process for IPv4 to the Task Force. There were two technical queries: a request for confirmation that all contacts in both databases be e-mailed. Also, there was a request for confirmation on how reverse delegations would be handled. Substantive issues included a question on how early registrations would be handled from a policy point of view. The RIPE NCC confirmed that in the past, the majority of registrants have agreed to meet the current policy requirements for registration. However, we also noted that previous registrations have tended to be done for organisations who place a value on registration data. It was argued that the policy issues were less important than the accuracy of the registration data transferred/updated. No other issues on the transfer process were raised. It appears that the Task Force is happy with the proposed transfer process. As such, we would like to publish the proposed process in the next few days. Regards, -- leo vegoda RIPE NCC Registration Services

1 0

[lir-wg]Fw: http://www.icann.org/amsterdam/
by Jim Fleming 28 Oct '02

28 Oct '02

----- Original Message ----- From: "Jim Fleming" <JimFleming(a)ameritech.net> To: <richard.hill(a)itu.int>; <Rosa.Delgado(a)SITA.INT>; <jefsey(a)club-internet.fr>; "Barbara Simons" <simons(a)acm.org>; "Milton Mueller" <Mueller(a)syr.edu> Cc: <Amadeu(a)nominalia.com>; <andy(a)ccc.de>; <jcohen(a)shapirocohen.com>; <junsec(a)wide.ad.jp>; <karl(a)cavebear.com>; <lyman(a)acm.org>; <lynn(a)icann.org>; <mouhamet(a)next.sn>; <vinton.g.cerf(a)WCOM.COM>; <apisan(a)servidor.unam.mx>; "Elisabeth Porteneuve" <Elisabeth.Porteneuve(a)cetp.ipsl.fr>; <steinle(a)smartvia.de>; <yjpark(a)myepark.com>; "@quasar Internet Solutions, Inc." <shore(a)quasar.net>; "Bruce Young" <Bruce(a)barelyadequate.info>; <eric(a)hi-tek.com>; <jefsey(a)jefsey.com>; "Joanna Lane" <jo-uk(a)rcn.com>; "Joe Baptista" <baptista(a)dot-god.com>; "Joop Teernstra" <terastra(a)terabytz.co.nz>; "Judith Oppenheimer" <joppenheimer(a)icbtollfree.com>; <k(a)widgital.com>; <love(a)cptech.org>; <ray(a)fassett.org>; "Richard Henderson" <richardhenderson(a)ntlworld.com>; "Richard J. Sexton" <richard(a)vrx.net> Sent: Monday, October 28, 2002 8:04 AM Subject: http://www.icann.org/amsterdam/ > http://www.icann-ncc.org/pipermail/discuss/2002-October/003004.html > J-F C. (Jefsey) Morfin jefsey(a)club-internet.fr > "The same as Shanghai Beijing oriented, I read Amsterdam as the nearest > place from Brussels ICANN could chose to try a last attempt to enroll > Europe, trying to use the still different internal European attitudes, > knowing that within a few months the European position will be quite > united." > ===== > > http://www.icann.org/amsterdam/ > At $168,000,000 per year per /8, I would think that ICANN would want > to visit their customers on a regular basis, and even have an office there. > > http://www.iana.org/assignments/ipv4-address-space > INTERNET PROTOCOL V4 ADDRESS SPACE > (last updated 2002-10-25) > 062/8 Apr 97 RIPE NCC (whois.ripe.net) > 080/8 Apr 01 RIPE NCC (whois.ripe.net) > 081/8 Apr 01 RIPE NCC (whois.ripe.net) > 193/8 May 93 RIPE NCC (whois.ripe.net) > 194/8 May 93 RIPE NCC (whois.ripe.net) > 195/8 May 93 RIPE NCC (whois.ripe.net) > 212/8 Oct 97 RIPE NCC (whois.ripe.net) > 213/8 Mar 99 RIPE NCC (whois.ripe.net) > 217/8 Jun 00 RIPE NCC (whois.ripe.net) > ===================================== > > http://www.ripe.net > http://www.ripe.net/ripencc/about/location.html > Office Location: > RIPE NCC > Singel 258 > 1016 AB Amsterdam > The Netherlands > ============================================= > > How much does SITA pay ICANN each year for this /8 ? > http://www.iana.org/assignments/ipv4-address-space > 057/8 May 95 SITA > ==== > > > Jim Fleming > 128-bit DNS is closer than you think... > http://ipv8.dyndns.tv > http://ipv8.dyns.cx > http://ipv8.no-ip.com > http://ipv8.no-ip.biz > http://ipv8.no-ip.info > http://ipv8.myip.us > http://ipv8.dyn.ee > http://ipv8.community.net.au > >

1 0

[lir-wg]Is there really a shortage of 32-bit Address Space ?
by Jim Fleming 27 Oct '02

27 Oct '02

Is there really a shortage of 32-bit Address Space ? NOTE the changes... http://www.iana.org/assignments/ipv4-address-space Jim Fleming 128-bit DNS is closer than you think... http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee http://ipv8.community.net.au

1 0

[lir-wg]Hostmaster Robot
by Tanja Heimes 26 Oct '02

26 Oct '02

Hello, when sending mails and IP requests to hostmaster(a)ripe.net I am receiving either strange responses from the robot - for instance that totals are missing (but they are not missing), or that the format is not correct. Additionally I am getting a second response that the IP request has not been recognized as an IP request - but it is. When correcting something in the request and resending the mail with the NCC# in the subject I am not receiving a response anymore from the Robot. When checking in the Web for the TT status there is stated that RIPE expects a reply. But RIPE got a reply. And in other cases I even do not get a NCC# Nr. at all. Does somebody have made similar experiences the last two days? Regards, Tanja -- Tanja Heimes E-Mail Tanja.Heimes(a)de.cw.com IP Engineer Comnet: 749 9374 Cable & Wireless Deutschland GmbH TEL. + 49 89 92699-0 Landsberger Strasse 155 Fax. + 49 89 92699-810 D-80687 Munich, Germany web: http://www.cw.com/de

3 2

Re: [lir-wg] ICANN Reform
by Daniel Karrenberg 23 Oct '02

23 Oct '02

[ This message states my personal opinion and *not* the opinion of the RIPE NCC. I realise that NCC staff commenting on controversial"political" issues in a personal capacity can be considered inappropriate. However I feel I have to speak up just *because* I personally invested a lot of energy into the RIR processes and also into the gestation of ICANN, the ASO and its processes. In other words: I think I earned the right and *have the obligation* to speak up.] Hans Petter, I just read your messages analysing the legal prose. While this is good work and highlights quite some symptoms, it does not analyse the disease. A much more clear symptom of the desease is in the latest amendment to the ICANN-USG agreement http://www.ntia.doc.gov/ntiahome/domainname/agreements/amend5_09192002.htm "... ICANN agrees to perform the following activities and provide the following resources ... Work collaboratively on a global and local level to pursue formal legal agreements with the RIRs, and to achieve stable relationships that allow them to continue their technical work, while incorporating their policy-making activities into the ICANN process. ..." This clearly shows that ICANN does not want to work the way the RIRs are successfully working. ICANN has no respect for, and maybe still does not understand our long established, well working, bottom-up, transparent way of making policies. There are more symptoms of this in all areas of ICANN activity. A good example is the current "AXFR conflict" with some ccTLDs. They script for these problems is: - ICANN staff drafts or changes policies for reasons only apparent to ICANN staff and, possibly, the US Government in some cases. - ICANN board ratifies changes without discussion. THIS MEANS THAT THERE IS NO PROCESS OTHER THAN ON PAPER. - ICANN staff applies policy - 'victims' are surprised since they did not hear anything via what they thought of as their part of the "ICANN Process". - ICANN staff says: "This is policy ratified by the board, please use the 'ICANN Process' to change it again. Meanwhile just comply." THIS MEANS THAT THOSE WHO DEPEND ON ICANN FOR SOMETHING ARE SCREWED. In the particular 'AXFR conflictt' I refer to above, ICANN has deliberately jeopradised the stability of the DNS of some pretty large ccTLDs over an extended period of time. I have lost all confidence in ICANN as an organisation, the ICANN process and many of the people involved, both board and staff. I have the strong suspicion that I am not the only one. *This* is the disease: Loss of confidence. It cannot be addressed with adding paper "Core Values" and even more paper process while maintaining the level of substance at a minimum. I personally think the RIRs should *now* walk away from ICANN for better or worse. This means we have to do our home work well: - Create a process for global policy coordination. We have thes substance of it: the ASO. We just need a legal shell outside of ICANN and -maybe- some minor adaptions to the substance. - Create a process for 'process appeal', i.e. where someone can go if the global policy coordination does not follow its own rules. Maybe professional arbitrators can be used. Certainly not another politically loaded body. - Make sure that those who look at ICANN for influcene into the process find their needs sufficiently addressed by the current regional processes plus the "new" global process. I suspect that this is largely a matter of educating people. Hans Petter, imagine you had invested the time it took to analyse the ICANN generated legal prose into drafting this. I think it would have been a much better investment. We should have a very open discussion in this working group on how to proceed with address policy coordination on the global level. If the RIPE NCC, and the other RIRs, should decide to walk away from ICANN they need our full support. The RIPE NCC also needs help with doing the work outlined above together with the other RIRs. Respectfully Daniel

9 26

[lir-wg]Draft Minutes from LIR WG at RIPE 43
by Hans Petter Holen 19 Oct '02

19 Oct '02

Dear WG, The Draft Minutes from LIR WG at RIPE 43 are now available on http://www.ripe.net/ripe/wg/lir/r43-minutes.html Please read trough and submit comments to the list or to me before November 19th. Best Regards, Hans Petter Holen LIR-Wg Chair

1 0

[lir-wg]Ripe ftp server ?
by D'HERTOG Pieterjan 18 Oct '02

18 Oct '02

Is there a problem with the ftp server of ripe ? I get a connection refused... Pieterjan --- Pieterjan d'Hertog, Senior Network Engineer Belgacom Skynet NV/SA, 2 Rue Carli, B-1140 Brussels Phone +3227061311 Fax +3227061150 http://www.skynet.be PGP fingerprint: D9AB CD6A 2A78 73CC 68BF 0AFA 8FB3 5821 E4BB 9D2E

2 1