- ripe-list - mailman.ripe.net

New Document available: RIPE-220
by RIPE NCC Document Announcement Service 04 May '01

04 May '01

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE Document Store. Short content description ------------------------- Supporting Notes for the European IP Address Space Request Form. This document obseletes RIPE-142. 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-220.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-220.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-220 is not available from the WWW at this moment, but will be soon, at the following URL: http://www.ripe.net/ripe/docs/ripe-220.html

2 1

New Document available: RIPE-221
by RIPE NCC Document Announcement Service 04 May '01

04 May '01

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Short content description ------------------------- A new version of the Standard RIPE NCC Service Agreement has been published. This version is an updated version of the RIPE-191 that it refers to all the current documents from 2001 which were already available. 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-221.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-221.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-221 is not available from the WWW at this moment, but will be soon, at the following URL: http://www.ripe.net/docs/ripe-221.html

1 0

Re: RIPE Documents Modified
by RIPE NCC Staff 04 May '01

04 May '01

Dear Colleagues, The RIPE NCC is aware that the changes made to the RIPE documents ripe-141, ripe-142 and ripe-191 were not in keeping with the practices for updating RIPE documents as agreed by the RIPE community. The original versions of the documents in question have been replaced in the RIPE doc. store and new versions of these documents will be published and announced. Again, I apologise for this. Regards, Paul Rendek Communications Manager RIPE NCC

2 1

Re: RIPE Documents Modified
by Nigel Titley 03 May '01

03 May '01

> Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been > modified recently on the RIPE NCC ftp server rather than having new documents > issued with new numbers? It's also interesting to note that the Postscript > versions of these documents seem unchanged. > > And, yes, I realise that there is a requirement to bring database objects > described in the documents in line with the new database implementation but > shouldn't this have been done by issuing new documents? Is it helpful to have > (potentially) different versions of the same document lying around with the > same name? If this has, indeed, happened then I for one would be very disturbed. The only way to modify a RIPE document should to be up-issue it. I recall Rob getting very heated about this at the Budapest RIPE meeting. Nigel

6 5

Re: RIPE Documents Modified
by Nigel Titley 02 May '01

02 May '01

Paul, > Thank you for pointing out the minor changes made to ripe-141, > ripe-142, ripe-191. Apologies are extended and we realise that this > is not the agreed procedure for updating RIPE documents. We assure you > that these changes will not set a precedent for future modifications > made to RIPE documents. A couple of points: 1. It was James who spotted the changes, not Marc 2. Although the changes involved are pretty sensible, one or two at least are not minor. I'm thinking particularly of the change of mnt-by from optional to mandatory. However, apology accepted (by me at any rate), and no doubt Rob will be visiting to make sure that this doesn't happen again :-) Nigel > Regards, > > Paul Rendek > RIPE NCC > > > > Marc Roger <marc(a)belnet.be> writes: > * This message is in MIME format. The first part should be readable text, > * while the remaining parts are likely unreadable without MIME-aware tools. > * Send mail to mime(a)docserver.cac.washington.edu for more info. > * > * ---559023410-341603450-988799134=:8747 > * Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > * Content-ID: <Pine.GSO.4.33.0105021226201.8747@dagesh> > * > * Nigel, > * > * James is right, these documents have changed. I attach the differences > * found for ripe-141, 142 and 191, for info. > * > * On Wed, 2 May 2001, Nigel Titley wrote: > * > * > > Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been > * > > modified recently on the RIPE NCC ftp server rather than having new documents > * > > issued with new numbers? It's also interesting to note that the Postscript > * > > versions of these documents seem unchanged. > * > > > * > > And, yes, I realise that there is a requirement to bring database objects > * > > described in the documents in line with the new database implementation but > * > > shouldn't this have been done by issuing new documents? Is it helpful to have > * > > (potentially) different versions of the same document lying around with the > * > > same name? > * > > * > If this has, indeed, happened then I for one would be very disturbed. > * > The only way to modify a RIPE document should to be up-issue it. I > * > recall Rob getting very heated about this at the Budapest RIPE meeting. > * > * -- > * Marc.Roger(a)belnet.be, BELNET

1 0

Re: RIPE Documents Modified
by Nigel Titley 02 May '01

02 May '01

And the amusing thing is that your diffs show the line "Each revised document will receive a new document number" in RIPE-191 Nigel

1 0

Re: RIPE Documents Modified
by James Aldridge 02 May '01

02 May '01

Nigel Titley wrote: > If this has, indeed, happened then I for one would be very disturbed. The > only way to modify a RIPE document should to be up-issue it. I recall Rob > getting very heated about this at the Budapest RIPE meeting. I notice that the RIPE NCC have now "tidied up" ftp.ripe.net but my mirror on ftp.mcvax.org shows: -r--r--r-- 1 root ftp 66229 Jan 18 1999 ripe-141.ps -r--r--r-- 1 root ftp 5939 May 1 10:17 ripe-141.txt -r--r--r-- 1 root ftp 5973 Sep 19 1997 ripe-141.txt~ -r--r--r-- 1 root ftp 244618 Sep 19 1997 ripe-142.ps -r--r--r-- 1 root ftp 40467 May 1 10:34 ripe-142.txt -r--r--r-- 1 root ftp 40666 Sep 19 1997 ripe-142.txt~ -r--r--r-- 1 root ftp 52071 Oct 9 2000 ripe-191.ps -r--r--r-- 1 root ftp 11488 May 1 10:22 ripe-191.txt -r--r--r-- 1 root ftp 11284 Feb 4 1999 ripe-191.txt~ I too would very much prefer that ripe documents (like RFCs) remained completely unchanged once assigned a number and published. In this case the changes were minor but this MUST NOT set a precedent for future modifications. James

1 0

RIPE Documents Modified
by James Aldridge 02 May '01

02 May '01

Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been modified recently on the RIPE NCC ftp server rather than having new documents issued with new numbers? It's also interesting to note that the Postscript versions of these documents seem unchanged. And, yes, I realise that there is a requirement to bring database objects described in the documents in line with the new database implementation but shouldn't this have been done by issuing new documents? Is it helpful to have (potentially) different versions of the same document lying around with the same name? James -- James Aldridge, Senior Network Engineer (IP Architecture) KPNQwest, Singel 540, 1017 AZ Amsterdam, NL GSM: +31 653 708 707

1 0

"IP tutorial" during the RIPE 39 meeting
by RIPE NCC Staff 26 Apr '01

26 Apr '01

Dear colleagues, During the RIPE 39 Meeting in Bologna, an "IP Requests Tutorial" will be held on Friday, 4th May, 14-17 PM. The "IP Requests Tutorial" contains selected sections of the LIR Training course that RIPE NCC provides to its members: - How to Request Address Space - Completing the Request Form - Evaluation of Address Space Requests - Registering Address Space in the RIPE Database - How to Request New Allocation Registration for this tutorial is not necessary. All RIPE meeting participants are more than welcome to attend this tutorial. The slides from the Tutorial will be shortly available at: http://www.ripe.net/ripe/meetings/archive/ripe-39/presentations/ip-tutorial/ Kind regards, Vesna Manojlovic RIPE NCC Trainer

1 0

Announcement DISI BOF
by Henk Uijterwaal (RIPE-NCC) 25 Apr '01

25 Apr '01

Dear Colleagues, (sorry for duplicate copies). This mail is to inform you about the DISI BOF that will be organized next week during the RIPE39 meeting, on Wednesday 2/5, 9:00-12:30. The purpose of the BOF is to discuss the plans for the DISI project at the RIPE NCC as well as related projects. A draft agenda for the BOF as well as some background material, can be found at the bottom of this mail If you have any additional topics for the BoF, comments or questions, please send me an email. Depending on the outcome of the BoF a mailing list will be set up. I hope to see you in Bologna, Henk Uijterwaal Proposed agenda for the DISI BOF -------------------------------- Wednesday, 9.00-12.30. A. Introduction. - What is this BoF about? B. Administrative Matters - Appointment of a scribe - List of participants - Agenda bashing C. DISI and the deployment of DNSSEC on the reverse DNS tree. - Plans, deadlines and milestones. Olaf Kolkman (RIPE NCC) A draft document describing the plans for the DISI project exists. The abstract of this document can be found below, the current draft of the full document is available at: http://www.ripe.net/ripencc/pub-services/np/Notes/DISI-project-note.ps D. CSIRT coordination for Europe and Extended Incident Handling - standardisation - Overview of TERENA's TF-CSIRT activity Yuri Demchenko (Terena) E. .... F. Discussion G. The Future - Is there sufficient interest in this topic and if so, how should we proceed from here? Z. AOB DISI and the deployment of DNSSEC on the reverse DNS tree. ---------------------------------------------------------- Abstract The Deployment of Internet Security Infrastructure (DISI) project is a new effort at the RIPE NCC. Within the context of DISI we will study, raise awareness and support the use of protocols and techniques that can make the Internet more secure and that need mutual effort of ISPs to be successful. Within the DISI project context we will concentrate on suitable technologies and will try to get these technologies accepted and implemented by ISPs. We will do so by raising awareness, providing documentation, giving courses and, most important, giving and receiving feedback on implementation experience at the RIPE NCC and at the ISPs. The first technology we are concentrating on is the deployment of DNS Security on the reverse tree. We will describe what DNSSEC can do, why DNSSEC is a mutual ISP effort and what DISI's deliverables are. ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(a)ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.5354414 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ As long as you don't tell your friends how I played the hand, then I won't tell my friends how you defended it. (Anonymous)

1 0