From Anne.Lord at ripe.net Fri Oct 1 15:24:55 1993 From: Anne.Lord at ripe.net (Anne Lord) Date: Fri, 01 Oct 1993 15:24:55 +0100 Subject: Document announcement Message-ID: <9310011424.AA10377@ncc.ripe.net> New/Revised RIPE Document Announcement -------------------------------------- A revised document below European Internet Network Number Application Form is available from the RIPE document store. Ref: ripe-095 Title: European Internet Network Number Application Form Title: and Supporting Notes Author: Anne Lord, Daniel Karrenberg Date: 1st October, 1993 Format: PS=63045 TXT=26784 bytes Obsoletes: ripe-088.txt Obsoleted by: ripe-095{ps,txt} Updates: Updated by: Old: Short content description ------------------------- Updated version of the European IP network number request form. The new version contains some new text on "Requesting Additional address space". -------------- next part -------------- FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get ". For example "get ripe-095.txt". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server at ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. -------------- next part -------------- SEND ripe/docs/ripe-docs/ripe-095.txt From woeber at cc.univie.ac.at Fri Oct 1 15:44:24 1993 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 01 Oct 1993 15:44:24 +0100 Subject: Document announcement Message-ID: <009735FA.4D94C2C0.5035@cc.univie.ac.at> >A revised document below European Internet Network Number Application Form >is available from the RIPE document store. > > >Ref: ripe-095 >Title: European Internet Network Number Application Form >Title: and Supporting Notes > Is there a major change in the contents, format or function of this document? I'm a bit worried, about the name change from ripe-088 to ripe-095, because right now our users/customers get comfortable with the idea to just "pick up ripe-88 from the ftp server" whenever they apply for a new Class C address. Also we would have to update all local text to refer to the new document. So I see 3 possible approaches: - keep the ripe-document number the same unless there is a major change in content, maybe appending some version or date information [preferred] - agree on a fixed document name both for the RIPE document store and local versions [acceptable] - we have to store the document (and/or it's local version) with a fixed name (different from the RIPE document id) on our system [not desirable but workable] Anybody else with strong feelings? Wilfried. From Piet.Beertema at EU.net Fri Oct 1 16:09:43 1993 From: Piet.Beertema at EU.net (Piet.Beertema at EU.net) Date: Fri, 01 Oct 1993 16:09:43 +0100 Subject: Document announcement In-Reply-To: Your message of Fri, 01 Oct 1993 15:44:24 +0100 . <009735FA.4D94C2C0.5035@cc.univie.ac.at> Message-ID: <9310011509.AA13786@mcsun.EU.net> I'm a bit worried, about the name change from ripe-088 to ripe-095, because right now our users/customers get comfortable with the idea to just "pick up ripe-88 from the ftp server" whenever they apply for a new Class C address. Apparently the ripe-xxx numbers are just that: numbers, not related to a date or whatever. Then how about introducing version numbers? Then ripe-088 would become ripe-088.0, ripe-095 would become ripe-088.1, ripe-088 could point to the current version, and people would be happy again. Piet From Daniel.Karrenberg at ripe.net Fri Oct 1 16:16:00 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Fri, 01 Oct 1993 16:16:00 +0100 Subject: Document announcement In-Reply-To: Your message of Fri, 01 Oct 1993 15:44:24 MET. <009735FA.4D94C2C0.5035@cc.univie.ac.at> Message-ID: <9310011516.AA10533@ncc.ripe.net> > "Wilfried Woeber, UniVie/ACOnet" writes: > >A revised document below European Internet Network Number Application Fo > rm > >is available from the RIPE document store. > > > > > >Ref: ripe-095 > >Title: European Internet Network Number Application Form > >Title: and Supporting Notes > > > > Is there a major change in the contents, format or function of this documen > t? The contents has changed: - different encoding of "no email" - additional hints to document present address space usage > I'm a bit worried, about the name change from ripe-088 to ripe-095, because > right now our users/customers get comfortable with the idea to just "pick u > p > ripe-88 from the ftp server" whenever they apply for a new Class C address. > Also we would have to update all local text to refer to the new document. We had a long sicussion about this nternally and at some ripe meeting. The coclusion was to change the number whenever the document content changes. I'd hate to change that -again-. > So I see 3 possible approaches: > > - keep the ripe-document number the same unless there is a major change in > content, maybe appending some version or date information > [preferred] Not preferred here. > - agree on a fixed document name both for the RIPE document store and local > versions > [acceptable] That was the plan and to link it to the current one. We should do this. > - we have to store the document (and/or it's local version) with a fixed na > me > (different from the RIPE document id) on our system > [not desirable but workable] not at all desirable I agree. > Anybody else with strong feelings? I bet. From cliff at demon.co.uk Sat Oct 2 15:38:59 1993 From: cliff at demon.co.uk (Cliff Stanford) Date: Sat, 2 Oct 1993 15:38:59 +0100 (BST) Subject: Document announcement In-Reply-To: <9310011509.AA13786@mcsun.EU.net> from "Piet.Beertema@eu.net" at Oct 1, 93 04:09:43 pm Message-ID: <9310021538.aa22721@demon.demon.co.uk> Piet.Beertema at eu.net writes: > Apparently the ripe-xxx numbers are just that: numbers, not > related to a date or whatever. Then how about introducing > version numbers? Then ripe-088 would become ripe-088.0, > ripe-095 would become ripe-088.1, ripe-088 could point to > the current version, and people would be happy again. Totally agree. Cliff. -- Cliff Stanford (PGP Key Available) Demon Systems Limited DEMON INTERNET 42 Hendon Lane *********************** London N3 1TT England THE INTERNET FOR A TENNER-A-MONTH 081 349 0063 From Daniel.Karrenberg at ripe.net Fri Oct 15 12:17:08 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Fri, 15 Oct 1993 12:17:08 +0100 Subject: Current RIPE Forms and Procedures Available in Fixed Place Message-ID: <9310151117.AA21827@ncc.ripe.net> The files with the current RIPE forms and procedures can from now on always be found in a fixed place in the RIPE dcoument store. This makes it possible to refer to the current version of these documents in other documentation. There are two subdirectories in the document store called "forms" and "procedures" respectively. forms: This directory contains the current RIPE NCC application forms. All of these are links to the current RIPE documents also available in ~ftp/ripe/docs/ripe-docs. as-appl - Application for an Autonomous System Number netmum-appl - Application for an IP network number (IP address space) procedures: This directory contains descriptions of RIPE NCC procedures. All of these are links to the current RIPE documents also available in ~ftp/ripe/docs/ripe-docs. inaddr-delegation Delegation of subdomains of 193.in-addr.arpa and 194.in-addr.arpa ncc-funding Fnding of NCC core activities. netnum-assignment Assignment of IP netowrk numbers by European Internet Registries routing-registry Description of the RIPE Routing Registry From Daniel.Karrenberg at ripe.net Fri Oct 15 15:34:00 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Fri, 15 Oct 1993 15:34:00 +0100 Subject: Document announcement In-Reply-To: Your message of Fri, 01 Oct 1993 15:44:24 MET. <009735FA.4D94C2C0.5035@cc.univie.ac.at> Message-ID: <9310151434.AA22465@ncc.ripe.net> > "Wilfried Woeber, UniVie/ACOnet" writes: > I'm a bit worried, about the name change from ripe-088 to ripe-095, because > right now our users/customers get comfortable with the idea to just "pick u > p > ripe-88 from the ftp server" whenever they apply for a new Class C address. > Also we would have to update all local text to refer to the new document. > > So I see 3 possible approaches: > > - keep the ripe-document number the same unless there is a major change in > content, maybe appending some version or date information > [preferred] We had some deliberations both before and after getting this message. We had decided earlier that changes in semantic content would always generate a new number. Implementing this option would make it harder to speak about a specific document and also create unnecessary confusion. They way we store RIPE documents is now well defined and a history of all documents is available. > - agree on a fixed document name both for the RIPE document store and local > versions > [acceptable] We have implemented fixed aliases. This had been the plan form the beginning but implementation was lacking. It is done now and I hope it is acceptable to you and the other local IRs. Daniel From Daniel.Karrenberg at ripe.net Fri Oct 15 15:34:00 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Fri, 15 Oct 1993 15:34:00 +0100 Subject: Document announcement In-Reply-To: Your message of Fri, 01 Oct 1993 15:44:24 MET. <009735FA.4D94C2C0.5035@cc.univie.ac.at> Message-ID: <9310151434.AA22465@ncc.ripe.net> > "Wilfried Woeber, UniVie/ACOnet" writes: > I'm a bit worried, about the name change from ripe-088 to ripe-095, because > right now our users/customers get comfortable with the idea to just "pick u > p > ripe-88 from the ftp server" whenever they apply for a new Class C address. > Also we would have to update all local text to refer to the new document. > > So I see 3 possible approaches: > > - keep the ripe-document number the same unless there is a major change in > content, maybe appending some version or date information > [preferred] We had some deliberations both before and after getting this message. We had decided earlier that changes in semantic content would always generate a new number. Implementing this option would make it harder to speak about a specific document and also create unnecessary confusion. They way we store RIPE documents is now well defined and a history of all documents is available. > - agree on a fixed document name both for the RIPE document store and local > versions > [acceptable] We have implemented fixed aliases. This had been the plan form the beginning but implementation was lacking. It is done now and I hope it is acceptable to you and the other local IRs. Daniel From woeber at cc.univie.ac.at Fri Oct 15 16:27:33 1993 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 15 Oct 1993 16:27:33 +0100 Subject: Document announcement Message-ID: <00974100.A6E770A0.6981@cc.univie.ac.at> Daniel, | | > - agree on a fixed document name both for the RIPE document store and local | > versions | > [acceptable] | |We have implemented fixed aliases. This had been the plan form the beginning |but implementation was lacking. It is done now and I hope it is |acceptable to you and the other local IRs. I think this is pefectly ok. Now I (again) have a "fixed" name that I can put into the heads of our users, attach to the ACOnet version of this document on our FTP-Server and put into local documentation. And I prefer the new "useful" names for these documents over ripe-xxx. Thanks a lot, Wilfried. From bonito at nis.garr.it Mon Oct 18 12:46:43 1993 From: bonito at nis.garr.it (Antonio_Blasco Bonito) Date: Mon, 18 Oct 93 12:46:43 MET Subject: Document announcement In-Reply-To: <00974100.A6E770A0.6981@cc.univie.ac.at>; from "Wilfried Woeber, UniVie/ACOnet" at Oct 15, 93 4:27 pm Message-ID: <9310181146.AA01918@jolly.nis.garr.it> > > Daniel, > > | > | > - agree on a fixed document name both for the RIPE document store and local > | > versions > | > [acceptable] > | > |We have implemented fixed aliases. This had been the plan form the beginning > |but implementation was lacking. It is done now and I hope it is > |acceptable to you and the other local IRs. > > I think this is pefectly ok. Now I (again) have a "fixed" name that I can put > into the heads of our users, attach to the ACOnet version of this document on > our FTP-Server and put into local documentation. And I prefer the new "useful" > names for these documents over ripe-xxx. > > Thanks a lot, > Wilfried. > Let me add my thanks. Very well done! ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito at nis.garr.it GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito c/o CNUCE - Istituto del CNR Tel: +39 (50) 593246 Via S. Maria, 36 Telex: 500371 CNUCE I 56126 PISA Italy Fax: +39 (50) 904052 ---------- ----------