You're viewing an archived page. It is no longer being updated.
RIPE Meeting: |
31 |
Working Group: |
Routing |
Status: |
FINAL |
Revision Number: |
1 |
Please mail comments/suggestions on:
Chair: |
Joachim Schmitz (JS395-RIPE) |
Scribe: |
Mirjam Kühne (MK16-RIPE), Julia Edwards (JE316-RIPE) |
Attenders: |
99 |
RPSL is in the stage of deployment phase 2 with the final transition phase from RIPE-181 in sight. Part of the transition is education to make it easier for users to apply RPSL. After some tutorials in the US we had the first RPSL tutorial in Europe just prior to this RIPE meeting. There were approximately 90 participants.
The training materials are available electronically at http://www.isi.edu/ra/rps/training. Future tutorials will be held at the next RIPE meeting, and plans to offer them as part of the LIR tutorials are currently considered.
Joachim Schmitz then thanked the trainers Cengiz Allaetinoglu, David Kessens, and the RIPE NCC, for preparing and performing this tutorial.
In addition, PGP authentication will also become available in approximately two weeks for production after this RIPE meeting. This method is supplied in parallel to "none", "e-mail address", "UNIX style password" but offers significantly better security. This method may currently be tested at
queries: |
beta-whois.ripe.net |
submissions: |
Phase II of the transition has been completed, meaning that a mirror of the production database is installed and running. The mirror according to definition of transition phases is one-way only (RIPE-181 -> RPSL). The phase II database is accessible at
The database is running using ISI's code written by David Kessens. The usage is still low (which is no wonder because the server just became available).
In the future, as part of the database reimplementation, the RPSL capable database will support the full set of RPSL features, and also support the RAToolSet.
There are three phases proposed in the transition from RIPE-181 to RPSL:
phase 1: |
software development |
done |
|
phase 2: |
tool development, testing, training |
real time mirror of IRR in RPSL format |
|
special RPSL update path for "autnum" objects |
|
status of today |
|
phase 3: |
switch over |
incoming RIPE-181 objects are automatically converted to RPSL |
|
expected during 1999 |
RIPE, ANS, and Merit are currently in phase 2. MCI and CANET are testing RPSL software. Telstra moved to RPSL, and Connect (AU) is already configuring their routers using the alpha RAToolSet for RPSL. A set of others is known to evaluate.
Regarding training and education the following tutorials were held so far
To make use of RPSL, the following software is available:
Merit offers a public RPSL server
Then the current situation regarding IPv6 was described, and the expected development of IPv6 "Inter6net" with its interaction towards IPv4 listed.
Looking at the benefits the IPv4 IRR offers, it seemed obvious that they are also applicable to an IPv6 routing registry. Consequently, the conclusion was drawn that a need for an IPv6 routing registry exists, which may even add more value by easing the coexistence of IPv4 and IPv6, and may help in transition to IPv6. The time to raise the topic is not too early because during the 1st quarter of 1999 IPv6 address allocation is likely to begin.
The presentation was finished with a call for participation to explore the idea and to define the requirements.
The IRR AUP will definitely acknowledge other efforts. Others are currently defining relevant policy rules or have already done so
In the following part of the presentation, a starting framework for an AUP was shown:
- Routing Working Group Meeting -
Agenda for RIPE 31, September 1998, Edinburgh
Mirjam Kühne, Julia Edwards, Joachim Schmitz
21 January 1999