RE: 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
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.
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
Piet.Beertema@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
"Wilfried Woeber, UniVie/ACOnet" <woeber@cc.univie.ac.at> 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.
"Wilfried Woeber, UniVie/ACOnet" <woeber@cc.univie.ac.at> 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
participants (4)
-
Cliff Stanford -
Daniel Karrenberg -
Piet.Beertemaï¼ EU.net -
Wilfried Woeber, UniVie/ACOnet