September 2000 - lir-wg - mailman.ripe.net

Re: Modifying references to contact info in the RIPE DB
by Wilfried Woeber, UniVie/ACOnet 24 Jun '01

24 Jun '01

Hi Joao! >If the reference is by name then when I query the DB I will get the list of >persons with that name, right? Right. >Whether the object belongs to the person or not is not going to save this >person from being contacted. From the point of view of the database and the >user querying it, the object belongs to that person. Right >The link is via a name. > >Now we substitute the reference by name with a reference by nic handle >pointing to the same person. >What is the difference? > >ALMOST NONE except that: True, for the case where there is a strict one-to-one mapping, e.g the recursion using the name returns *one* object. What do you suggets to do with the case where the recursion, based on the names, returns a *set* of objects? I can see 2 approaches (at least): - do not perform the handle substitution for that referring object and put it on the list of those requiring human intervention - expand the xxxx-c: list (which? the tech-c:?) to refer to *all* objects, but by ref'ing their handles While human beings are quite clever in selecting the "proper" instance of a person: object (by looking at country, address, email,...) a script might be quite clueless with that respect :-) Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Vienna University : Fax: +43 1 4277 - 9 140 Universitaetsstrasse 7 : RIPE-DB (&NIC) Handle: WW144 A-1010 Vienna, Austria, Europe : PGP public key ID 0xF0ACB369 --------------------------------------------------------------------------

3 3

ANNOUNCEMENT: Public Release of Asused
by Maldwyn Morris 22 Sep '00

22 Sep '00

Hi, The RIPE NCC are pleased to announce the release of a new public version of Asused - this is Version 3.52. Asused is a tool to check and summarise address space registered in the RIPE database. For a given list of allocations the tool prints various information concerning the allocations and the assignments they contain. The software is written in standard Perl 5 and uses several Perl modules. It was written and tested on BSD/OS 3.1, but should work with any modern UNIX-like operating system. All the files needed are stored in this file: ftp://ftp.ripe.net/tools/asused-3.52.tar.gz or alternatively, just: ftp://ftp.ripe.net/tools/asused-latest.tar.gz You will need to use gzip and tar to extract them, then please follow the instructions in the README file. The changes since Version 3.51 are: * No longer designated as beta software. * Fixed problem with huge free address space reports, caused by bug in the Whois DB - "-Tin" returns rev-srv: A.B.C.D fields as well. * Fixed problem with RIPEWhois.pm module, which didn't return anything on some Linux'es. Was reported several times, visible effect was: FATAL ERROR: ERROR: 10.65.0.0/19 No allocation object in DB, inetnum found * Fixed small compatability problem - some systems don't let to use IO::Socket::INET directly, so, turned that into "use IO::Socket". * Put the CPAN IO module IO-1.20.tar.gz into extra/ directory, as some Perl distributions come with outdated modules and CPAN suggests perl5.6.0 as an update :> * Added --free flag to show only free address space list. * Produce a warning if a registry doesn't have mnt-lower attribute on it's allocation. * Fixed the case that --status didn't report assignments with missed status lines and gave incorrect balance. Thanks to the following people for bug reports and suggestions: Elmar K. Bins Jean-Francois Stenuit Dominic Mitchell Daniel N. Rasmussen Johannes Dagemark Timur Bakeyev of RIPE NCC did the programming. We are keen to receive your further feedback on this software - please address your comments and/or suggestions to me. Cheers, Maldwyn Morris maldwyn(a)ripe.net Software Manager RIPE NCC

1 0

LIR-WG Plenary report
by Hans Petter Holen 15 Sep '00

15 Sep '00

Dear workinggroup, As we ran seriously out of time both in the workinggroup itself and in the plenary report, I am posting my slides for you all to view for the full report. It will soon also be up on the RIPE web site. http://home.online.no/~hph/RIPE Sincerely, Hans Petter Holen

1 0

Re: IAB/IESG Recommendations on IPv6 Address Delegation
by Turchanyi Geza 13 Sep '00

13 Sep '00

Fred, I would like to add a few comments and a proposal to your marvellous summary. (Even if it is very difficult to say anything at this stage). Comments: 1, The IPv6 address scheme might be valid for two centuries or even longer, and not only for 50 years. 2, The proposed "sparce allocation for subsribers (sites)", "dence allocation for providers (networks)" should work very well for customers, however, not necessarly for providers. You mentioned already the multihoming issues. There is an other open issue: how to scale effectively the routing. Proposal: I suggest adding a clause to your summary: ADDRESS ALLOCATION POLICY will be reviewed every five years. If different address allocation policy will be set up for any reason, then all subscribers and providers having already address space should adopt themselves to the new policy within TEN years, the latest. If they do not adopt, their not properly allocated address space will be blocked from the global routing. Many thanks for your time, best regards, Geza Turchanyi

2 1

Discussion: Address Council election procedures
by Hans Petter Holen 13 Sep '00

13 Sep '00

On the topic of > Call for Nominations for Representatives to the ASO Address Council - > RIPE NCC Region We have a some desicions to make at the upcoming meeting on - when to do the elections - how to do the elections > 4. Address Council Nominations Process (...) > Nominations should be sent by email to <nominations(a)ripe.net>, by midnight > CET on 30 September 2000. (...) Due to the timeconstraints we unfortunately have ended up with we cannot hold the election at RIPE 37 but will have to do it at a later stage. We can either delay the election to RIPE 38 next year, or we can do some sort of electronic voting between the RIPE meeting and the to ICANN meeting in november (as the ICANN meeting in november would be a convenient place gather the Address Council for a meeting to hand over responsibilities from the 3 members potentialy leaving their seats.) My understanding of the consensus from the previous meetings was that electronic voting was felt to be not yet widely deployable technology. But we may want to reconcider that with experiences from the ICANN at large election and perhaps from ARINs and APNICs plans. > 5. Address Council Selection Process > - ------------------------------------ > > The process for selection of the nominee to serve on the Address Council > will involve an open election. Due to the 90 day lead time needed for a call > for nominations prior to a RIPE NCC region policy meeting, the selection > process will not be held at the RIPE 37 meeting, 12-15 September 2000, in > Amsterdam. > > Two selection processes have been proposed. The first follows the voting > process outlined in the MoU. The selection procedure would take place at the > RIPE 38 meeting in January 2001 in Amsterdam. The second process currently > being discussed involves implementing an electronic voting procedure as it > would allow for more participation in the selection process and could > bring the process forward. This procedure would be discussed prior to > the RIPE 37 meeting and announced in the LIR-WG meeting. > Hans Petter Holen, LIR-WG Chair, > will initiate discussions about this procedure on the lir-wg mailing list. > > Important Dates: > > 30 September 2000 - deadline for Address Council nominations Sincerely, Hans Petter Holen lir-wg chair

3 5

Draft Agenda LIR-WG 37
by Hans Petter Holen 12 Sep '00

12 Sep '00

1. Admin scribe, participant list, charter, mailinglists 2. Agenda 3. Meet the RIPE NCC hostmasters 4. RIPE 35 minutes actions 5. Reports from the Registries RIPE NCC APNIC ARIN ICANN Status of the Latin and AFRI NiCs 6. Report from the address council 7. Presentations of candidates for the AC election 8. Status of the ICANN ad Hoc group 9. Report from the 17th of may Task Force 11. AOB.

1 2

ANNOUNCEMENT: Beta Version of ASinuse Web Page
by Maldwyn Morris 12 Sep '00

12 Sep '00

Hi, The RIPE NCC are please to announce a Beta Version of the ASinuse Web Page, available via the page: http://www.ripe.net/ripencc/pub-services/np/ris-index.html ASinuse lets users look up any AS number in the RIS database to show its observed peers and the time at which they were observed, and to further query those peers. Please let me know if you have any questions about this web page. Cheers, Maldwyn Morris maldwyn(a)ripe.net Software Manager RIPE NCC

1 0

ANNOUNCEMENT: Rttquery Web Page updated
by Maldwyn Morris 12 Sep '00

12 Sep '00

Hi, The RIPE NCC provides information to its members on the processing of their request tickets via the Rttquery Web Page: http://www.ripe.net/cgi-bin/rttquery This is to let you know that we have updated the page to show the given ticket's relative position in the Wait Queue, where it is put before it is given to a Hostmaster. We also now show customer labels in the ticket's messages. Any text in the Subject of a message between the opening delimiter: #{ and the closing delimiter: #} is displayed next to that message. Please let me know if you have any questions about this web page. Cheers, Maldwyn Morris maldwyn(a)ripe.net Software Manager RIPE NCC

1 0

Topics for todays ICANN ASO workshop at 1700
by Hans Petter Holen 12 Sep '00

12 Sep '00

Dear friends of RIPE; I have asked for a timeslot on this RIPE meeting to have a more informal Worksop style of environment were it is possible for those of you with particular interest in the work going on in the ICANN ASO and in the Address Council in particular. We will of course have a report from the AC in the lir-wg (as usual) and maybe even at the RIPE plenary at the RIPE chairs discretion. My thoughts behind this particular format at this particular meeting is to allow for the possibility of even more preparatory discussions in even more details than we usually have time for. Ideally I would have liked the meeting to happen later in the week, but not even the magic of the RIPE NCC meeting staff was enough for that to happen (we simply have to many competing for the same slots). The following rather broad topics lies on the Address Councils table, and will be discussed by the AC, ICANN and the RIRs at a physical AC meeting in Brisbane just after the APNIC meeting in October. This effort is thus an attempt to seek advice from the community before these discussions to satisfy the basic requirements for openness and transparency. 1) What is global policy ? There are several dimensions to this discussion: - replace RFC 2050 with a ICANN Address policy document - what is the distinction between regional and global policy - do we understand and appreciate the differences between the regional policies ? - differences between v4 and v6 with respect to the last item - what's the role/work mode of the AC ? to make the definite address policy, or to work on issues as they show up - were is the border between a service level contract and policy issues. - are there other operating guidelines for the ICANN - IANA than the global addressing policy ? 2) Revising the MOU In the widest sense: are there things in the present MOU that needs more work and needs to be changed ? 3) Addressing the essence of the ad Hoc committee, i.e. discussing how to best address new addressing needs emerging for 4) How to promote ipv6 ? 5) Emerging RIRs How to enable and support the emerging RIRs to establish regional policy processes ? The discussions in just above an hour needs not be limited to these topics. So, if you have a particular interest in influencing your AC members thinking on these or other matters, be there ! Sincerely, Hans Petter Holen Address Council Chair

1 0

Re: Call for Nominations - ASO Address Council
by Hans Petter Holen 12 Sep '00

12 Sep '00

Just a reminder of the ongoing nominations process, and an invitation to nominees and potential nominees: if you want to use this RIPE meeting to present yourselves to the LIR-wg: Please approach me to get on the agenda or if you are not able to make it to the meeting send me, 2-3 slides worth of presentation. Then I, or somebody of your choosing may present to the wg. Depending on the outcome of the election process discussion there will of course also be time to present the nominees to the list before the election. > 4. Address Council Nominations Process > - -------------------------------------- > > The term of Sabine Jaume who has served as an initial AC member for the past > year has expired. One individual from the RIPE NCC Region will be selected to > serve on the Address Council for a term of three years. The selection will be > made through an open election process, from the set of individuals who have > been nominated within this process. > > Any individual may be nominated, with the exception of any staff member of > any Regional Internet Registry. Self-nominations are permitted. > > Nominations should be sent by email to <nominations(a)ripe.net>, by midnight > CET on 30 September 2000. > > The information included with the nomination is to be in English, and > should¨include: > > Name of Nominee: > Country of residence: > Organisation: > Email Address: > Postal Address: > Biographical information: > Motivation for nomination: > > Name of nominating individual: > Organisation: > Email Address: > > All nominees will be contacted via email to confirm their willingness to > serve on the Address Council. If a nominee cannot be contacted via email, > or does not respond, then their nomination will not be confirmed and they > will not be eligible for election to the Address Council. > > All confirmed nominations will be listed on the RIPE NCC web site after they > are confirmed. All nominees will have the opportunity to submit a written > statement in support of their nomination for publication on the web site. > In addition, others may express support for nominated individuals simply by > completing and submitting the nomination form provided above. (...) > Important Dates: > > 30 September 2000 - deadline for Address Council nominations Regards, Hans Petter Holen lir-wg chair.

1 0