From meeting at ripe.net Mon Dec 3 14:16:59 2001 From: meeting at ripe.net (RIPE NCC Meeting Registration) Date: Mon, 03 Dec 2001 14:16:59 +0100 Subject: 1st reminder RIPE 41 registration Message-ID: <200112031316.fB3DGxI12254@birch.ripe.net> Dear Colleagues, Herewith we like to remind you of the registration for the RIPE 41 meeting which has been opened. The meeting will be held from 14th January - 18th January 2002 at hotel Krasnapolsky in Amsterdam, The Netherlands. More information about this meeting and accommodations can be found on this page: http://www.ripe.net/ripe/meetings/current/ripe-41/ Online registration will open on Monday 19th November 2001 and close on Friday 4th January 2002. On-site registration will open on Monday 14th January 2002. Please note the following: To avoid waiting queues at the registration desk on-site we encourage pre-payment by credit card. The registration fee for this meeting is EUR 350.00 (this includes refreshments and lunches) and the dinner fee is EUR 65.00. However, if payment is received before 4 January 2002, the pre-payment cut-off date, you will receive a pre-registration discount of EUR 50.00. Therefore, the fee for attendees paying before the cut-off date is EUR 300.00 for the meeting and 65.00 EUR for the RIPE dinner event. Confirmation of Registration: For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) If you still prefer not to send your credit card number using an encrypted transfer method, we have prepared a fax form. This form is attached to the acknowledgment of your registration. You will receive a second acknowledgment by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. Participants requiring a visa to enter The Netherlands are advised to begin the required procedures as soon as possible. The RIPE Meeting organizers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at . Kind regards, Asha Raghoebarsing RIPE Meeting Co-ordinator From ncc at ripe.net Tue Dec 4 12:35:58 2001 From: ncc at ripe.net (RIPE NCC Document Announcement Service) Date: Tue, 04 Dec 2001 12:35:58 +0100 Subject: New Document available: RIPE-201 Message-ID: <200112041135.fB4BZwG05137@birch.ripe.net> New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-201 Title: Routing Registry Consistency Check Author: Joachim Schmitz, Engin Gunduz, Shane Kerr, Andrei Robachevsky, Joao Luis Silva Damas Date: 4 December 2001 Format: PS=33719 TXT=15425 Obsoletes: Obsoleted by: Updates: Updated by: Short content description ------------------------- "Routing Registry Consistency Check" describes a project to crosscheck European Internet routing against data registered in the RIPE Routing Registry. This project was proposed as a new activity by the RIPE Routing Working Group. The document gives an overview of the project, discusses the implementation, and mentions some points that have to be addressed in future design documents. This document is intended to solicit input from interested parties. Accessing the RIPE document store --------------------------------- The RIPE document store is 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-201.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-201.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-201 is available at the following URL: http://www.ripe.net/docs/rr-consistencycheck.html From stephenb at uk.uu.net Wed Dec 5 11:30:17 2001 From: stephenb at uk.uu.net (Stephen Burley) Date: Wed, 5 Dec 2001 10:30:17 -0000 Subject: Can anyone shed some light on this? Message-ID: <021f01c17d77$d50f1440$2e04bf3e@eu.frd.uu.net> route: 212.249.0.0/16 descr: UUNET CH origin: AS702 mnt-by: AS702-MNT password: ********* changed: jsc at ch.uu.net 20011204 source: RIPE I send the above object to the DB and get the following error: New FAILED: [route] 212.249.0.0/16 route: 212.249.0.0/16 descr: UUNET CH origin: AS702 mnt-by: AS702-MNT changed: stephenb at uk.uu.net 20011204 source: RIPE ***Error: Hierarchical authorisation failed, request forwarded to maintainer. Objects in RIPE-181 format are no longer accepted. Please see http://www.ripe.net/rpsl for more information. RIPE Database Maintenance Department Which is strange as the mainainer is us AS702-mnt. Any help on this matter whould be appreciated as this is not the only one. Regards Stephen Burley UUNET EMEA Hostmaster SB855-RIPE From stephenb at uk.uu.net Wed Dec 5 11:38:31 2001 From: stephenb at uk.uu.net (Stephen Burley) Date: Wed, 5 Dec 2001 10:38:31 -0000 Subject: Can anyone shed some light on this? References: <021f01c17d77$d50f1440$2e04bf3e@eu.frd.uu.net> Message-ID: <02c601c17d78$fbef8350$2e04bf3e@eu.frd.uu.net> Further to this i also get the forwarded message that an atempt was made to change this object - go figure. ----- Original Message ----- From: "Stephen Burley" To: Cc: Sent: Wednesday, December 05, 2001 10:30 AM Subject: Can anyone shed some light on this? > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > password: ********* > changed: jsc at ch.uu.net 20011204 > source: RIPE > > I send the above object to the DB and get the following error: > > New FAILED: [route] 212.249.0.0/16 > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > changed: stephenb at uk.uu.net 20011204 > source: RIPE > ***Error: Hierarchical authorisation failed, request forwarded to > maintainer. > > Objects in RIPE-181 format are no longer accepted. > Please see http://www.ripe.net/rpsl for more information. > > RIPE Database Maintenance Department > > Which is strange as the mainainer is us AS702-mnt. Any help on this matter > whould be appreciated as this is not the only one. > > Regards > Stephen Burley > UUNET EMEA Hostmaster > SB855-RIPE > > > From stephenb at uk.uu.net Wed Dec 5 11:57:55 2001 From: stephenb at uk.uu.net (Stephen Burley) Date: Wed, 5 Dec 2001 10:57:55 -0000 Subject: Can anyone shed some light on this? References: <021f01c17d77$d50f1440$2e04bf3e@eu.frd.uu.net> <02c601c17d78$fbef8350$2e04bf3e@eu.frd.uu.net> Message-ID: <02fc01c17d7b$b19313a0$2e04bf3e@eu.frd.uu.net> Many thanks guys i got the answer to my problem. Regards Stephen Burley UUNET EMEA Hostmaster SB855-RIPE From sabrina at ripe.net Wed Dec 5 12:06:18 2001 From: sabrina at ripe.net (Sabrina Waschke) Date: Wed, 05 Dec 2001 12:06:18 +0100 Subject: mnt-routes in allocation objects Message-ID: <200112051106.fB5B6JG23864@birch.ripe.net> Dear all, This is to inform you that the RIPE NCC Registration Services will update all inetnum objects representing allocations made by the RIPE NCC to Local IRs (status: ALLOCATED PA") adding a mnt-routes attribute. We will use the maintainer specified in the mnt-lower attribute of the particular inetnum object. We will only add a mnt-routes attribute to allocation objects that have exactly one mnt-lower attribute (*). The updates will start on Monday, 10th December 2001. Until the introduction of RPSL there was no mnt-routes attribute. Adding a mnt-routes attribute to the inetnum object representing your allocation will enable you to create route objects matching the exact size of your allocation object. (You might have to pass other authorisations.) For a graphical overview of "Route Object Creation - Getting Authorisation from IP Space" please see: . For more information about route object please read: and . (*) In general: If you want to update an object maintained by the RIPE-NCC-HM-MNT please send a message to including your registry ID and the revised object. Please note that we only accept these requests from official LIR contacts who are registered in our RIPE NCC internal registry files. If you have any further questions please do not hesitate to contact including your registry ID. Kind regards, Sabrina Waschke -- o------------------------------------------o | Sabrina Waschke sabrina at ripe.net | | Registration Services Operations Manager | | | | RIPE NCC tel +31 20 535 4444 | | www.ripe.net fax +31 20 535 4445 | o------------------------------------------o From neil at ednet.co.uk Wed Dec 5 11:33:55 2001 From: neil at ednet.co.uk (Neil Anderson Saunders) Date: Wed, 5 Dec 2001 10:33:55 +0000 (GMT) Subject: Can anyone shed some light on this? In-Reply-To: <021f01c17d77$d50f1440$2e04bf3e@eu.frd.uu.net> Message-ID: Hi Stephen, You need to send the update in RPSL format (http://www.ripe.net/rpsl). Kind regards, Neil -- Neil Anderson Saunders edNET t: +44 131 466 7003 (office) d: +44 131 625 5560 (direct) On Wed, 5 Dec 2001, Stephen Burley wrote: > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > password: ********* > changed: jsc at ch.uu.net 20011204 > source: RIPE > > I send the above object to the DB and get the following error: > > New FAILED: [route] 212.249.0.0/16 > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > changed: stephenb at uk.uu.net 20011204 > source: RIPE > ***Error: Hierarchical authorisation failed, request forwarded to > maintainer. > > Objects in RIPE-181 format are no longer accepted. > Please see http://www.ripe.net/rpsl for more information. > > RIPE Database Maintenance Department > > Which is strange as the mainainer is us AS702-mnt. Any help on this matter > whould be appreciated as this is not the only one. > > Regards > Stephen Burley > UUNET EMEA Hostmaster > SB855-RIPE > > > > -- > Virus scanned by edNET. > Kind regards, Neil -- Neil Anderson Saunders edNET t: +44 131 466 7003 (office) d: +44 131 625 5560 (direct) -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. Any offers or quotation of service are subject to formal specification. Errors and omissions excepted. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of edNET or lightershade ltd. Finally, the recipient should check this email and any attachments for the presence of viruses. edNET and lightershade ltd accepts no liability for any damage caused by any virus transmitted by this email. -- -- Virus scanned by edNET. From tim at colt.net Wed Dec 5 11:35:35 2001 From: tim at colt.net (Tim Franklin) Date: Wed, 5 Dec 2001 10:35:35 -0000 Subject: Can anyone shed some light on this? In-Reply-To: <021f01c17d77$d50f1440$2e04bf3e@eu.frd.uu.net> Message-ID: <001801c17d78$93137d00$dd5f4ad4@TRAVELLINGMACK> > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > password: ********* > changed: jsc at ch.uu.net 20011204 > source: RIPE > > I send the above object to the DB and get the following error: > > New FAILED: [route] 212.249.0.0/16 > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > changed: stephenb at uk.uu.net 20011204 > source: RIPE > ***Error: Hierarchical authorisation failed, request forwarded to > maintainer. > > Objects in RIPE-181 format are no longer accepted. > Please see http://www.ripe.net/rpsl for more information. > > RIPE Database Maintenance Department > > Which is strange as the mainainer is us AS702-mnt. Any help on this matter > whould be appreciated as this is not the only one. You need to pass, as I understand it, authorisation on the inetnum the route is for, the autnum you're originating from, and the existing route object if you're replacing one. 212.249.0.0/16 is mnt-by RIPE-NCC-HM-MNT, so you fail the first check. Ask RIPE nicely to add mnt-lower and mnt-routes as AS702-MNT to the 212.249.0.0/16 inetnum object and you should be away. Regards, Tim. -- Tim Franklin ____________ Project Engineer \C/\O/\L/\T/ EN&S - T: +44 20 7863 5714 V V V V IP Services F: +44 20 7390 7848 From bkrosnov at lirex.bg Wed Dec 5 11:36:37 2001 From: bkrosnov at lirex.bg (Boyan Krosnov) Date: Wed, 5 Dec 2001 12:36:37 +0200 Subject: Can anyone shed some light on this? Message-ID: <3FAEA93E6179FA4FBB329456D0A9054A1E0F65@tquila.lirex.com> http://www.ripe.net/ripe/docs/databaseref-manual.html 3.6.5 Protection of route object space The route object creation must satisfy several authentication criteria. It must match the authentication specified in the aut-num and the authentication specified in either a route object or, if no applicable route object is found, then an inetnum. Finally the creation must be authorised by the maintainer of the route object itself referenced by the "mnt-by:" attribute of the object. When checking for prefix authorisation, an exact route object prefix match is checked for first. If there is no exact match, then a longest prefix match that is less specific than the prefix is searched for. If the route prefix search fails, then a search is performed for an inetnum object that exactly matches the prefix or for the most specific inetnum object that is less specific than the route object submission. The aut-num object used for authentication checks is referenced by the "origin:" attribute of the route object. A route object must pass authorisation from both the referenced aut-num object and the route or inetnum object. Authorisation shall be tested using the maintainer(s) referenced in the "mnt-routes:" attribute(s) first. If that check fails, the "mnt-lower:" attributes are checked. If that check fails, the "mnt-by:" attributes are used for the authorisation check. ---------- aut-num: AS702 as-name: AS702 descr: UUNET - Commercial IP service provider in Europe .... mnt-routes: UUNETDK-MNT mnt-routes: AS1270-MNT mnt-routes: AS1849-MNT mnt-routes: AS1890-MNT mnt-routes: IWAY-NOC mnt-by: UUNET-MNT --------- I bet you didn't pass this authorization check. does this shed a light? :) BR, CCNP Boyan Krosnov Network Administrator Lirex Net phone: +359-2-91815 > -----Original Message----- > From: Stephen Burley [mailto:stephenb at uk.uu.net] > Sent: Wednesday, December 05, 2001 12:30 PM > To: lir-wg at ripe.net > Cc: db-wg at ripe.net > Subject: Can anyone shed some light on this? > > > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > password: ********* > changed: jsc at ch.uu.net 20011204 > source: RIPE > > I send the above object to the DB and get the following error: > > New FAILED: [route] 212.249.0.0/16 > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > changed: stephenb at uk.uu.net 20011204 > source: RIPE > ***Error: Hierarchical authorisation failed, request forwarded to > maintainer. > > Objects in RIPE-181 format are no longer accepted. > Please see http://www.ripe.net/rpsl for more information. > > RIPE Database Maintenance Department > > Which is strange as the mainainer is us AS702-mnt. Any help > on this matter > whould be appreciated as this is not the only one. > > Regards > Stephen Burley > UUNET EMEA Hostmaster > SB855-RIPE > > > > From beri at kpnqwest.net Wed Dec 5 11:38:32 2001 From: beri at kpnqwest.net (Berislav Todorovic) Date: Wed, 5 Dec 2001 11:38:32 +0100 (CET) Subject: Can anyone shed some light on this? In-Reply-To: <021f01c17d77$d50f1440$2e04bf3e@eu.frd.uu.net> Message-ID: I guess that you have to ask RIPE NCC hostmasters to put the newly invented (RPSL) "mnt-routes:" attribute to your inetnum object: inetnum: 212.249.0.0 - 212.249.255.255 netname: CH-UUNET-981023 The RPSL security mechanisms are pretty complex. In order to create a route object the inetnum's "mnt-routes:" and aut-num's "mnt-by:" must point to the maintainer object(s) authorizing you to make changes. On Wed, 5 Dec 2001, Stephen Burley wrote: >> route: 212.249.0.0/16 >> descr: UUNET CH >> origin: AS702 >> mnt-by: AS702-MNT >> password: ********* >> changed: jsc at ch.uu.net 20011204 >> source: RIPE >> >> I send the above object to the DB and get the following error: >> >> New FAILED: [route] 212.249.0.0/16 >> route: 212.249.0.0/16 >> descr: UUNET CH >> origin: AS702 >> mnt-by: AS702-MNT >> changed: stephenb at uk.uu.net 20011204 >> source: RIPE >> ***Error: Hierarchical authorisation failed, request forwarded to >> maintainer. >> >> Objects in RIPE-181 format are no longer accepted. >> Please see http://www.ripe.net/rpsl for more information. >> >> RIPE Database Maintenance Department >> >> Which is strange as the mainainer is us AS702-mnt. Any help on this matter >> whould be appreciated as this is not the only one. >> >> Regards >> Stephen Burley >> UUNET EMEA Hostmaster >> SB855-RIPE >> >> >> >> --------- Berislav Todorovic, Senior NOC Specialist -------- ------- KPNQwest N.V. - IP NOC (formerly EUnet NOC) ------ ---- Wilhelmina van Pruisenweg 78, 2595 AN Den Haag, NL ---- --- Phone: +31-70-379-3990; Mobile: +31-651-333-641 --- -- Email: beri at kpnqwest.net <=> beri at EU.net -- --- _ _ ____ _ .--. ____ ____ __/_ --- ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- From ula at ripn.net Wed Dec 5 11:56:59 2001 From: ula at ripn.net (Larisa A. Yurkina) Date: Wed, 5 Dec 2001 13:56:59 +0300 (MSK) Subject: Can anyone shed some light on this? In-Reply-To: <02c601c17d78$fbef8350$2e04bf3e@eu.frd.uu.net> Message-ID: On Wed, 5 Dec 2001, Stephen Burley wrote: Hi, it looks like a problem we had some time ago. the answer from Database admin was: RPSL requires that both the maintainer of the IP space (i.e. the inetnum object) and the AS number (i.e. the aut-num object) of a route authorize the route creation. This means that the authentication of both maintainers must be included in the e-mail update. The problem is, inetnum object is maintained with RIPE-NCC-HM-MNT but not with your as-mntner. To solve the problem you should ask RIPE NCC hostmaster to add mnt-routes: AS702-MNT to the allocation object. > Further to this i also get the forwarded message that an atempt was made to > change this object - go figure. > > ----- Original Message ----- > From: "Stephen Burley" > To: > Cc: > Sent: Wednesday, December 05, 2001 10:30 AM > Subject: Can anyone shed some light on this? > > > > route: 212.249.0.0/16 > > descr: UUNET CH > > origin: AS702 > > mnt-by: AS702-MNT > > password: ********* > > changed: jsc at ch.uu.net 20011204 > > source: RIPE > > > > I send the above object to the DB and get the following error: > > > > New FAILED: [route] 212.249.0.0/16 > > route: 212.249.0.0/16 > > descr: UUNET CH > > origin: AS702 > > mnt-by: AS702-MNT > > changed: stephenb at uk.uu.net 20011204 > > source: RIPE > > ***Error: Hierarchical authorisation failed, request forwarded to > > maintainer. > > > > Objects in RIPE-181 format are no longer accepted. > > Please see http://www.ripe.net/rpsl for more information. > > > > RIPE Database Maintenance Department > > > > Which is strange as the mainainer is us AS702-mnt. Any help on this matter > > whould be appreciated as this is not the only one. > > > > Regards > > Stephen Burley > > UUNET EMEA Hostmaster > > SB855-RIPE > > > > > > > With respect, Larisa Yurkina --- RIPN Registry center ----- From manuel at ripe.net Thu Dec 6 19:36:46 2001 From: manuel at ripe.net (Manuel Valente) Date: Thu, 6 Dec 2001 19:36:46 +0100 Subject: Problems with RIPE NCC Robots Message-ID: <20011206193646.44447d52.manuel@ripe.net> Dear members, The RIPE NCC request handling system had a few problems today (December 6) which may cause delays in the processing of the wait queue. Some of the requests could not be automatically processed and may have resulted in mail errors being returned to the requester. We are now manually processing the requests which we received. However, if you sent a request today and did not receive an acknoledgement, it is possible that your request was deleted. In that case, please resend your e-mail. Please accept our apologies for this problem - we are working on a fix to prevent the problem from happening again. -- Manuel Valente - Software Manager - RIPE NCC From manuel at ripe.net Thu Dec 6 19:36:46 2001 From: manuel at ripe.net (Manuel Valente) Date: Thu, 6 Dec 2001 19:36:46 +0100 Subject: Problems with RIPE NCC Robots Message-ID: <20011206193646.44447d52.manuel@ripe.net> Dear members, The RIPE NCC request handling system had a few problems today (December 6) which may cause delays in the processing of the wait queue. Some of the requests could not be automatically processed and may have resulted in mail errors being returned to the requester. We are now manually processing the requests which we received. However, if you sent a request today and did not receive an acknoledgement, it is possible that your request was deleted. In that case, please resend your e-mail. Please accept our apologies for this problem - we are working on a fix to prevent the problem from happening again. -- Manuel Valente - Software Manager - RIPE NCC From manuel at ripe.net Thu Dec 6 19:36:46 2001 From: manuel at ripe.net (Manuel Valente) Date: Thu, 6 Dec 2001 19:36:46 +0100 Subject: Problems with RIPE NCC Robots Message-ID: <20011206193646.44447d52.manuel@ripe.net> Dear members, The RIPE NCC request handling system had a few problems today (December 6) which may cause delays in the processing of the wait queue. Some of the requests could not be automatically processed and may have resulted in mail errors being returned to the requester. We are now manually processing the requests which we received. However, if you sent a request today and did not receive an acknoledgement, it is possible that your request was deleted. In that case, please resend your e-mail. Please accept our apologies for this problem - we are working on a fix to prevent the problem from happening again. -- Manuel Valente - Software Manager - RIPE NCC From meeting at ripe.net Mon Dec 10 10:38:32 2001 From: meeting at ripe.net (RIPE NCC Meeting Registration) Date: Mon, 10 Dec 2001 10:38:32 +0100 Subject: 2nd reminder RIPE 41 registration Message-ID: <200112100938.fBA9cWG15822@birch.ripe.net> Dear Colleagues, Herewith we like to remind you of the registration for the RIPE 41 meeting which has been opened. The meeting will be held from 14th January - 18th January 200 2 at hotel Krasnapolsky in Amsterdam, The Netherlands. More information about this meeting and accommodations can be found on this page: http://www.ripe.net/ripe/meetings/current/ripe-41/ Online registration will open on Monday 19th November 2001 and close on Friday 4th January 2002. On-site registration will open on Monday 14th January 2002. Please note the following: To avoid waiting queues at the registration desk on-site we encourage pre-payment by credit card. The registration fee for this meeting is EUR 350.00 (this includes refreshments and lunches) and the dinner fee is EUR 65.00. However, if payment is received before 4 January 2002, the pre-payment cut-off date, you will receive a pre-registration discount of EUR 50.00. Therefore, the fee for attendees paying before the cut-off date is EUR 300.00 for the meeting and 65.00 EUR for the RIPE dinner event. Confirmation of Registration: For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) If you still prefer not to send your credit card number using an encrypted transfer method, we have prepared a fax form. This form is attached to the acknowledgment of your registration. You will receive a second acknowledgment by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. Participants requiring a visa to enter The Netherlands are advised to begin the required procedures as soon as possible. The RIPE Meeting organizers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at . Kind regards, Asha Raghoebarsing RIPE Meeting Co-ordinator ------- End of Forwarded Message From ncc at ripe.net Mon Dec 10 14:26:42 2001 From: ncc at ripe.net (Paul Rendek) Date: Mon, 10 Dec 2001 14:26:42 +0100 Subject: Call for Nominations to ICANN Board of Directors Message-ID: <5.0.0.25.2.20011210141642.00ac4348@mailhost.ripe.net> Dear colleagues, We are pleased to announce a Call for Nominations to the ICANN Board of Directors (see below). In our effort to reach as many interested parties as possible you may receive multiple copies of this message. Please accept our apologies for this. The Call for Nominations for ICANN Board of Directors and current appointments to the Board can be found on the ASO website at: http://www.aso.icann.org/ A publicly archived "expressions of support" form will be made available on the ASO website for those that wish to support nominated candidates. Regards, Paul Rendek RIPE NCC ===== ASO General Assembly 2002 and Call for Nominations for ICANN Board of Directors The Address Council of the Address Supporting Organisation is pleased to announce the 3rd ASO General Assembly meeting, to be held on Tuesday, 5 March 2002 in Bangkok, Thailand. This meeting will be hosted by APNIC alongside APNIC's Open Policy Meeting, and will be open to all parties with an interest in ASO policy matters. A detailed meeting agenda will be published in due course on the ASO web site at: http://www.aso.icann.org. In compliance with the ASO MoU , the Address Council and ICANN hereby call for nominations to the ICANN Board to fill vacant ASO seats on the ICANN Board. The first such seat scheduled to become vacant on 1 October 2002 is currently occupied by Mr. Rob Blokzijl. However, candidates nominated at this time may also be chosen to fill other seats that may become vacant before or after this time. Note that appointments to the ICANN board must satisfy the geographic diversity constraints specified in section 3c. of the ASO MoU. Any individual may be nominated within this process, with the exception of any official of a national government or a multinational entity established by treaty or other agreement between national governments (ICANN Bylaws Art. V., Sec 5). Self-nominations are permitted. Nominations should be sent by email to and should state the following details : A. Nominee details 1. Full name 2. Organisational affiliation 3. Email address 4. Physical address 5. Country of residence 6. Telephone contact 7. Biography B. Details of nominating individual 1. Full name 2. Organisational affiliation 3. Email address 4. Country of residence Nominations must be submitted in English and must be received by the ASO Secretariat before 0900 UTC, 6 February 2002 (30 days prior to the General Assembly meeting). All nominees will be contacted via email to confirm their willingness to serve as an ICANN Director. If the nominee is not contactable via email then the nomination will not be confirmed, a nominee must explicitly confirm the nomination to the ASO Secretariat to be considered as a candidate. All confirmed nominations will be listed on the ASO website (see http://www.aso.icann.org) as soon as they are confirmed. Those wishing to express support for any individuals who have been nominated should use the "ICANN Board - Support of Nomination" Form which will be made available on the ASO website. The list of nominated individuals and the supporting comments will be passed to the Address Council after all nominees are confirmed, and prior to the General Assembly meeting on 5 March 2002. More information regarding the ASO GA and nominations process will be posted on the ASO website in due course. From ncc at ripe.net Mon Dec 10 14:26:42 2001 From: ncc at ripe.net (ncc at ripe.net) Date: Mon, 10 Dec 2001 14:26:42 +0100 Subject: Call for Nominations to ICANN Board of Directors In-Reply-To: <5.0.0.25.2.20011210141642.00ac4348@mailhost.ripe.net> References: <5.0.0.25.2.20011210141642.00ac4348@mailhost.ripe.net> Message-ID: Dear colleagues, We are pleased to announce a Call for Nominations to the ICANN Board of Directors (see below). In our effort to reach as many interested parties as possible you may receive multiple copies of this message. Please accept our apologies for this. The Call for Nominations for ICANN Board of Directors and current appointments to the Board can be found on the ASO website at: http://www.aso.icann.org/ A publicly archived "expressions of support" form will be made available on the ASO website for those that wish to support nominated candidates. Regards, Paul Rendek RIPE NCC ===== ASO General Assembly 2002 and Call for Nominations for ICANN Board of Directors The Address Council of the Address Supporting Organisation is pleased to announce the 3rd ASO General Assembly meeting, to be held on Tuesday, 5 March 2002 in Bangkok, Thailand. This meeting will be hosted by APNIC alongside APNIC's Open Policy Meeting, and will be open to all parties with an interest in ASO policy matters. A detailed meeting agenda will be published in due course on the ASO web site at: http://www.aso.icann.org. In compliance with the ASO MoU , the Address Council and ICANN hereby call for nominations to the ICANN Board to fill vacant ASO seats on the ICANN Board. The first such seat scheduled to become vacant on 1 October 2002 is currently occupied by Mr. Rob Blokzijl. However, candidates nominated at this time may also be chosen to fill other seats that may become vacant before or after this time. Note that appointments to the ICANN board must satisfy the geographic diversity constraints specified in section 3c. of the ASO MoU. Any individual may be nominated within this process, with the exception of any official of a national government or a multinational entity established by treaty or other agreement between national governments (ICANN Bylaws Art. V., Sec 5). Self-nominations are permitted. Nominations should be sent by email to and should state the following details : A. Nominee details 1. Full name 2. Organisational affiliation 3. Email address 4. Physical address 5. Country of residence 6. Telephone contact 7. Biography B. Details of nominating individual 1. Full name 2. Organisational affiliation 3. Email address 4. Country of residence Nominations must be submitted in English and must be received by the ASO Secretariat before 0900 UTC, 6 February 2002 (30 days prior to the General Assembly meeting). All nominees will be contacted via email to confirm their willingness to serve as an ICANN Director. If the nominee is not contactable via email then the nomination will not be confirmed, a nominee must explicitly confirm the nomination to the ASO Secretariat to be considered as a candidate. All confirmed nominations will be listed on the ASO website (see http://www.aso.icann.org) as soon as they are confirmed. Those wishing to express support for any individuals who have been nominated should use the "ICANN Board - Support of Nomination" Form which will be made available on the ASO website. The list of nominated individuals and the supporting comments will be passed to the Address Council after all nominees are confirmed, and prior to the General Assembly meeting on 5 March 2002. More information regarding the ASO GA and nominations process will be posted on the ASO website in due course. From sabrina at ripe.net Mon Dec 10 17:06:02 2001 From: sabrina at ripe.net (Sabrina Waschke) Date: Mon, 10 Dec 2001 17:06:02 +0100 Subject: [apnic-announce] Additional IPv4 address range 220/8 allocated to APNIC Message-ID: <200112101606.fBAG62G16354@birch.ripe.net> Dear Colleagues, Please see the announcement below. Sabrina Waschke RIPE NCC ------- Forwarded Message Date: Fri, 7 Dec 2001 10:25:55 +1000 (EST) From: George Michaelson Sender: owner-apnic-announce at lists.apnic.net To: apnic-announce at whois.staff.apnic.net Subject: [apnic-announce] Date: Fri, 07 Dec 2001 10:25:53 +1000 [Note "reply-to:" field] - ------------------------------------------------- APOLOGIES for multiple copies. Dear colleagues APNIC received the IPv4 address range 220/8 from IANA on 2nd December 2001 and will now begin making allocations from this range. Please configure your routing filters accordingly. For more information on the resources administered by APNIC, see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, see: http://www.apnic.net/db/min-alloc.html Kind regards APNIC Secretariat - ------------------------------------------------- * APNIC-ANNOUNCE: Announcements concerning APNIC * * To unsubscribe, send "unsubscribe" to apnic-announce-request at apnic.net * ------- End of Forwarded Message From BECHA at ripe.net Fri Dec 14 10:57:50 2001 From: BECHA at ripe.net (Vesna Manojlovic) Date: Fri, 14 Dec 2001 10:57:50 +0100 Subject: IP Request Tutorial during the RIPE 41 meeting in Amsterdam Message-ID: <20011214105750.03845187.BECHA@ripe.net> Dear colleagues, During the RIPE 41 Meeting, an "IP Request Tutorial" will be held on Friday, 18 January, from 2 PM till 5.30 PM. The goal of the "IP Request Tutorial" is to explain address space assignment and allocation procedures. It contains selected parts from the LIR course that RIPE NCC provides to its members: How to Interact with the RIPE whois Database How to Request Address Space - Completing the Request Form - Evaluation Assignment Window PI Assignments How to Request New Allocation It is not necessary to register. All RIPE meeting participants are more than welcome to attend this tutorial. More information about the course that RIPE NCC offers to its members is available at http://www.ripe.net/training/ Material is available at the RIPE Meeting web pages: http://www.ripe.net/ripe/meetings/current/ripe-41/tutorials/ip_request.html Regards, Vesna Manojlovic RIPE NCC Trainer From sabrina at ripe.net Fri Dec 14 17:00:05 2001 From: sabrina at ripe.net (Sabrina Waschke) Date: Fri, 14 Dec 2001 17:00:05 +0100 Subject: New Assignment Window Policy implemented Message-ID: <200112141600.fBEG06G00482@birch.ripe.net> [Apologies for duplicate mails] Dear all, At RIPE 40 in Prague (October 2001) the RIPE community changed the Assignment Window (AW) Policy. (see http://www.ripe.net/ripe/meetings/archive/ripe-40/presentations/lir-wg-40/ index.html) The previous AW policy: "The assignment window is the maximum number of addresses that can be assigned by the local IR to an end user without prior approval by the RIPE NCC. This is expressed in /nn notation. Therefore, a local IR with an assignment window of /23 is allowed to assign up to and including 512 addresses to an end user without prior approval of the RIPE NCC. As the Local IR staff gain experience, the window size is increased... ...The assignment window is not only applied to individual assignments, but to multiple assignments to the same end user in a 12 month period If a Local IR makes more than one assignment to an organisation in any 12 month period, the total amount of address space assigned may not exceed the Local IR's assignment window. This also applies to address space used by the Registry for their internal network. Additional address space can only be assigned to that organisation after approval by the RIPE NCC." (see http://www.ripe.net/ripe/docs/ir-policies-procedures.html#toc39) The problem: This AW policy also applied to address space used by the Local Internet Registry (LIR) for their internal network. A registry that mainly assigns addresses to their own network would not be able to make the majority of the assignments to themself using their AW as the AW only applies once every 12 months. The new AW policy: Consensus was reached in the LIR Working Group to change this policy so that the LIR can make multiple assignments to their own infrastructure without contacting the RIPE NCC as long as the individual assignment is within their Assignment Window. The Implementation: Assignments made to the LIR's infrastructure using this new AW policy must have a remarks attribute in the inetnum object with the value INFRA-AW. It is important that a seperate remarks attribute is used for this. No other comment may be included in this line. It is possible to have other remarks attributes in the same object, though. The Audit: The existing audit policy allows the RIPE NCC to review your assignments at any time in order to assure a fair distribution of address space. It was agreed that the RIPE NCC may request proper documentation and an overview of the address space used for the LIR's own infrastructure. "If the LIR fails to show decent documentation the RIPE NCC may lower the LIR's Assignment Window. As this may delay the new allocation of addresses somewhat, the LIRs should be prepared to produce proper documentation upon request." (see http://www.ripe.net/ripe/meetings/archive/ripe-40/presentations/lir-wg-40/sld01 3.html) This new AW policy will be implemented as of Monday, 17th December 2001. If you do not want to use this new facility you are welcome to continue submitting requests to the RIPE NCC. For any questions regarding your AW please contact the RIPE NCC via including your Reg ID. Kind regards, Sabrina Waschke -- o------------------------------------------o | Sabrina Waschke sabrina at ripe.net | | Registration Services Operations Manager | | | | RIPE NCC tel +31 20 535 4444 | | www.ripe.net fax +31 20 535 4445 | o------------------------------------------o From ncc at ripe.net Fri Dec 14 17:00:05 2001 From: ncc at ripe.net (ncc at ripe.net) Date: Fri, 14 Dec 2001 17:00:05 +0100 Subject: New Assignment Window Policy implemented In-Reply-To: <200112141600.fBEG06G00482@birch.ripe.net> References: <200112141600.fBEG06G00482@birch.ripe.net> Message-ID: [Apologies for duplicate mails] Dear all, At RIPE 40 in Prague (October 2001) the RIPE community changed the Assignment Window (AW) Policy. (see http://www.ripe.net/ripe/meetings/archive/ripe-40/presentations/lir-wg-40/ index.html) The previous AW policy: "The assignment window is the maximum number of addresses that can be assigned by the local IR to an end user without prior approval by the RIPE NCC. This is expressed in /nn notation. Therefore, a local IR with an assignment window of /23 is allowed to assign up to and including 512 addresses to an end user without prior approval of the RIPE NCC. As the Local IR staff gain experience, the window size is increased... ...The assignment window is not only applied to individual assignments, but to multiple assignments to the same end user in a 12 month period If a Local IR makes more than one assignment to an organisation in any 12 month period, the total amount of address space assigned may not exceed the Local IR's assignment window. This also applies to address space used by the Registry for their internal network. Additional address space can only be assigned to that organisation after approval by the RIPE NCC." (see http://www.ripe.net/ripe/docs/ir-policies-procedures.html#toc39) The problem: This AW policy also applied to address space used by the Local Internet Registry (LIR) for their internal network. A registry that mainly assigns addresses to their own network would not be able to make the majority of the assignments to themself using their AW as the AW only applies once every 12 months. The new AW policy: Consensus was reached in the LIR Working Group to change this policy so that the LIR can make multiple assignments to their own infrastructure without contacting the RIPE NCC as long as the individual assignment is within their Assignment Window. The Implementation: Assignments made to the LIR's infrastructure using this new AW policy must have a remarks attribute in the inetnum object with the value INFRA-AW. It is important that a seperate remarks attribute is used for this. No other comment may be included in this line. It is possible to have other remarks attributes in the same object, though. The Audit: The existing audit policy allows the RIPE NCC to review your assignments at any time in order to assure a fair distribution of address space. It was agreed that the RIPE NCC may request proper documentation and an overview of the address space used for the LIR's own infrastructure. "If the LIR fails to show decent documentation the RIPE NCC may lower the LIR's Assignment Window. As this may delay the new allocation of addresses somewhat, the LIRs should be prepared to produce proper documentation upon request." (see http://www.ripe.net/ripe/meetings/archive/ripe-40/presentations/lir-wg-40/sld01 3.html) This new AW policy will be implemented as of Monday, 17th December 2001. If you do not want to use this new facility you are welcome to continue submitting requests to the RIPE NCC. For any questions regarding your AW please contact the RIPE NCC via including your Reg ID. Kind regards, Sabrina Waschke -- o------------------------------------------o | Sabrina Waschke sabrina at ripe.net | | Registration Services Operations Manager | | | | RIPE NCC tel +31 20 535 4444 | | www.ripe.net fax +31 20 535 4445 | o------------------------------------------o From ysam at hq.acn.gr Sat Dec 15 00:58:13 2001 From: ysam at hq.acn.gr (Yiannis Samouhos) Date: Sat, 15 Dec 2001 01:58:13 +0200 Subject: New Assignment Window Policy implemented In-Reply-To: <200112141600.fBEG06G00482@birch.ripe.net> References: <200112141600.fBEG06G00482@birch.ripe.net> Message-ID: <200112150158130632.0092EA36@172.31.10.88> X-NCC-Regid: gr.acn Sabrina, Are you sure this is correct?? Is it INFRA-AW or INTRA-AW? Kind Regards, -Yiannis Samouhos Technical Director Altec Communications Network SA. >The Implementation: > >Assignments made to the LIR's infrastructure using this new AW policy must >have a remarks attribute in the inetnum object with the value INFRA-AW. From gert at space.net Sun Dec 16 13:27:11 2001 From: gert at space.net (Gert Doering) Date: Sun, 16 Dec 2001 13:27:11 +0100 Subject: New Assignment Window Policy implemented In-Reply-To: <200112150158130632.0092EA36@172.31.10.88>; from ysam@hq.acn.gr on Sat, Dec 15, 2001 at 01:58:13AM +0200 References: <200112141600.fBEG06G00482@birch.ripe.net> <200112150158130632.0092EA36@172.31.10.88> Message-ID: <20011216132711.Y46150@Space.Net> Hi, On Sat, Dec 15, 2001 at 01:58:13AM +0200, Yiannis Samouhos wrote: > Are you sure this is correct?? > > Is it INFRA-AW or INTRA-AW? I'd guess "INFRA", for "INFRAstructure assignment". Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 72790 (73802) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299 From sabrina at ripe.net Mon Dec 17 11:08:06 2001 From: sabrina at ripe.net (Sabrina Waschke) Date: Mon, 17 Dec 2001 11:08:06 +0100 Subject: New Assignment Window Policy implemented In-Reply-To: Message from Gert Doering of "Sun, 16 Dec 2001 13:27:11 +0100." <20011216132711.Y46150@Space.Net> Message-ID: <200112171008.fBHA87G11835@birch.ripe.net> Gert Doering writes: * Hi, * * On Sat, Dec 15, 2001 at 01:58:13AM +0200, Yiannis Samouhos wrote: * > Are you sure this is correct?? * > * > Is it INFRA-AW or INTRA-AW? * * I'd guess "INFRA", for "INFRAstructure assignment". Correct. Sabrina Waschke RIPE NCC * Gert Doering * -- NetMaster * -- * Total number of prefixes smaller than registry allocations: 72790 (73802) * * SpaceNet AG Mail: netmaster at Space.Net * Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 * 80807 Muenchen Fax : +49-89-32356-299 * From meeting at ripe.net Mon Dec 17 15:53:42 2001 From: meeting at ripe.net (RIPE NCC Meeting Registration) Date: Mon, 17 Dec 2001 15:53:42 +0100 Subject: Reminder RIPE 41 registration Message-ID: <200112171453.fBHErgG15867@birch.ripe.net> Dear Colleagues, Herewith we like to remind you of the registration for the RIPE 41 meeting which has been opened. The meeting will be held from 14th January - 18th January 2002 at hotel Krasnapolsky in Amsterdam, The Netherlands. More information about this meeting and accommodations can be found on this page: http://www.ripe.net/ripe/meetings/current/ripe-41/ The online registration will close on Friday 4th January 2002 (10 workingdays fm now). On-site registration will open on Monday 14th January 2002. Please note the following: To avoid waiting queues at the registration desk on-site we encourage pre-payment by credit card. The registration fee for this meeting is EUR 350.00 (this includes refreshments and lunches) and the dinner fee is EUR 65.00. However, if payment is received before 4 January 2002, the pre-payment cut-off date, you will receive a pre-registration discount of EUR 50.00. Therefore, the fee for attendees paying before the cut-off date is EUR 300.00 for the meeting and 65.00 EUR for the RIPE dinner event. Confirmation of Registration: For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) If you still prefer not to send your credit card number using an encrypted transfer method, we have prepared a fax form. This form is attached to the acknowledgment of your registration. You will receive a second acknowledgment by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. Participants requiring a visa to enter The Netherlands are advised to begin the required procedures as soon as possible. The RIPE Meeting organizers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at . Kind regards, Asha Raghoebarsing RIPE Meeting Co-ordinator From meeting at ripe.net Sun Dec 23 12:43:55 2001 From: meeting at ripe.net (RIPE NCC Meeting Registration) Date: Sun, 23 Dec 2001 12:43:55 +0100 Subject: Important information on RIPE 41 Message-ID: <200112231143.fBNBhtT00320@birch.ripe.net> Dear all, Only two weeks left till the next RIPE meeting. Some of you maybe forgot to register or still has this on the to-do list, please make sure to register now. For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) We would also like to inform you about the accommodation: The Krasnapolsky Hotel has a special rate for all RIPE attendees. The price is EUR 140 for a single room incl. breakfast. Please mention RIPE 41 to the reservations department of the Krasnapolsky Hotel. With kind regards, Asha Raghoebarsing Meeting Coordinator