Re: RIPE Documents Modified
-
To: Nigel Titley <>
-
From: Marc Roger <>
-
Date: Wed, 2 May 2001 12:27:19 +0200 (MEST)
-
Cc: James Aldridge <>, <>
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@localhost, BELNET
*** ripe-141.txt.orig Fri Feb 26 14:19:03 1999
--- ripe-141.txt Wed May 2 12:09:40 2001
***************
*** 190,202 ****
inetnum:
netname:
descr:
- descr:
country:
admin-c:
tech-c:
status:
- mnt-by: (optional)
notify: (optional)
changed:
source: RIPE
--- 190,203 ----
inetnum:
netname:
descr:
country:
admin-c:
tech-c:
status:
notify: (optional)
+ mnt-by:
+ mnt-lower: (optional)
+ mnt-routes: (optional)
changed:
source: RIPE
***************
*** 204,211 ****
person:
address:
- address:
- address:
e-mail:
phone:
fax-no: (optional)
--- 205,210 ----
*** ripe-142.txt.orig Wed May 2 12:11:19 2001
--- ripe-142.txt Wed May 2 12:11:49 2001
***************
*** 14,20 ****
Document ID: ripe-142
Obsoletes: ripe-128, ripe-137, ripe-138
! See also: ripe-140, ripe-141
--- 14,20 ----
Document ID: ripe-142
Obsoletes: ripe-128, ripe-137, ripe-138
! See also: ripe-185, ripe-141
***************
*** 28,34 ****
addressing requirements, network infrastructure,
current address space usage and the future plans of
the end user requesting address space. The European
! IP Address Space Request Form (ripe-141) is a tool
for gathering the information necessary to evaluate
the request and to ensure that the same guidelines
are applied to each assignment.
--- 28,34 ----
addressing requirements, network infrastructure,
current address space usage and the future plans of
the end user requesting address space. The European
! IP Address Space Request Form is a tool
for gathering the information necessary to evaluate
the request and to ensure that the same guidelines
are applied to each assignment.
***************
*** 35,52 ****
This document contains instructions for completing
the form consisting of the templates contained in
! ripe-141. An example of a completed form is given in
Section 4. A separate form must be filled out on
! behalf of each separate enterprise. (Do not include
! requests for several customers in one form).
The policies and procedures to be followed in making
IP address space assignment decisions are described
! in ripe-140, "European Internet Registry Policies
and Procedures." Please refer to this document if
you have any questions on policy.
! As stated in ripe-140, address space assignments are
valid as long as the original criteria on which the
assignment was based remain true. If an assignment
is made for a specific purpose and the purpose no
--- 35,54 ----
This document contains instructions for completing
the form consisting of the templates contained in
! it. An example of a completed form is given in
Section 4. A separate form must be filled out on
! behalf of each separate network or customers' network.
! (Do not include requests for several networks in one
! form).
The policies and procedures to be followed in making
IP address space assignment decisions are described
! in the document "European Internet Registry Policies
and Procedures." Please refer to this document if
you have any questions on policy.
! As stated in , European Internet Registry Policies
! and procedures, address space assignments are
valid as long as the original criteria on which the
assignment was based remain true. If an assignment
is made for a specific purpose and the purpose no
***************
*** 394,400 ****
tion for the refusal.
PI-requested: "Yes" if address space requested is
provider independent; "No" other-
! wise. (see ripe-140)
address-space-returned: If the user is returning any
address space, specify the range of
addresses that will be returned, to
--- 396,403 ----
tion for the refusal.
PI-requested: "Yes" if address space requested is
provider independent; "No" other-
! wise. (see European Internet Registry
! policies and Procedures")
address-space-returned: If the user is returning any
address space, specify the range of
addresses that will be returned, to
***************
*** 596,604 ****
work; The "netname" is used for adminis-
trative purposes like Internet Registry
consistency checking. Valid characters are
! capital letters, numbers and dash. Use
! whois to check that the netname is not
! already in use.
descr: A short description of the organisation,
including the location; The full postal
address is not needed as this is provided
--- 599,606 ----
work; The "netname" is used for adminis-
trative purposes like Internet Registry
consistency checking. Valid characters are
! letters, numbers and dash. Use whois to check
! that the netname is not already in use.
descr: A short description of the organisation,
including the location; The full postal
address is not needed as this is provided
***************
*** 637,648 ****
aggregatable or provider independent.
Should be filled in with either "ASSIGNED
PA" or "ASSIGNED PI".
! mnt-by: This optional field references a regis-
tered maintainer object, which spefifies
authorisation checks on changes to the
inetnum object in the database. More
information on the database maintainer
! object can be found in ripe-120.
notify: This optional field specifies an e-mail
address to which notifications of changes
to the object should be sent.
--- 639,650 ----
aggregatable or provider independent.
Should be filled in with either "ASSIGNED
PA" or "ASSIGNED PI".
! mnt-by: This mandatory field references a regis-
tered maintainer object, which spefifies
authorisation checks on changes to the
inetnum object in the database. More
information on the database maintainer
! object can be found in ripe-157.
notify: This optional field specifies an e-mail
address to which notifications of changes
to the object should be sent.
***************
*** 660,669 ****
should contain a NIC handle which allows unambiguous
identification of the appropriate persons as needed
for Internet network administration. A RIPE NIC han-
! dle has the form "MK16-RIPE", but the database will
! also accept NIC handles that have been obtained from
! the InterNIC database (which have the form "DK58").
! To obtain a NIC handle, just put
nic-hdl: AUTO-1
--- 662,669 ----
should contain a NIC handle which allows unambiguous
identification of the appropriate persons as needed
for Internet network administration. A RIPE NIC han-
! dle has the form "MK16-RIPE". To obtain a NIC handle,
! just put
nic-hdl: AUTO-1
***************
*** 679,691 ****
both cases, the NIC handle is guaranteed to be
unique.
! You can reference these (AUTO-1 or
! AUTO-1YourInitials) as temporary NIC handles in the
! same update message in the fields of other objects
! that require a NIC handle (e.g. the inetnum object
! described above). The database software will then
! fill in the freshly assigned NIC handles in the
! objects. Note that you can also use other numbers
____________________________________________________
ripe-142.txt Page 11
--- 679,691 ----
both cases, the NIC handle is guaranteed to be
unique.
! You can reference these (AUTO-1 or AUTO-1YourIni-
! tials) as temporary NIC handles in the same update
! message in the fields of other objects that require
! a NIC handle (e.g. the inetnum object described
! above). The database software will then fill in the
! freshly assigned NIC handles in the objects. Note
! that you can also use other numbers (example:
____________________________________________________
ripe-142.txt Page 11
***************
*** 696,703 ****
____________________________________________________
! (example: AUTO-2) so that you can add more objects
! in one E-mail message.
Person Template:
--- 696,703 ----
____________________________________________________
! AUTO-2) so that you can add more objects in one E-
! mail message.
Person Template:
***************
*** 764,777 ****
inetnum: x.x.x.x/24
netname: XMAS
descr: Santa's Workshop Inc.
! descr: Christmas Toys Manufacturing Facility
! descr: Northern Nowhere
country: NN
admin-c: SC12-RIPE
tech-c: RR212-RIPE
status: ASSIGNED PA
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY
changed: jbgood@localhost 960412
source: RIPE
--- 764,777 ----
inetnum: x.x.x.x/24
netname: XMAS
descr: Santa's Workshop Inc.
! Christmas Toys Manufacturing Facility
! Northern Nowhere
country: NN
admin-c: SC12-RIPE
tech-c: RR212-RIPE
status: ASSIGNED PA
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY-MNT
changed: jbgood@localhost 960412
source: RIPE
***************
*** 779,794 ****
person: Santa Claus
address: Santa's Workshop Inc.
! address: Jingle Bell Lane 12
! address: 1224CH Christmastown
! address: Northern Nowhere
phone: +12 12 122 1122
! phone: +12 12 122 2211 ext. 1221
fax-no: +12 12 122 121
e-mail: Santa@localhost
nic-hdl: SC12-RIPE
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY
changed: jbgood@localhost 960412
source: RIPE
--- 779,794 ----
person: Santa Claus
address: Santa's Workshop Inc.
! Jingle Bell Lane 12
! 1224CH Christmastown
! Northern Nowhere
phone: +12 12 122 1122
! +12 12 122 2211 ext. 1221
fax-no: +12 12 122 121
e-mail: Santa@localhost
nic-hdl: SC12-RIPE
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY-MNT
changed: jbgood@localhost 960412
source: RIPE
***************
*** 796,810 ****
person: Rudolf R N Reindeer
address: Santa's Workshop Inc.
! address: Jingle Bell Lane 21
! address: 1224CH Christmastown
! address: Northern Nowhere
phone: +12 12 122 1111
fax-no: +12 12 122 2222
nic-hdl: RD212-RIPE
e-mail:Rudolf@localhost
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY
changed: jbgood@localhost 960412
source: RIPE
--- 796,810 ----
person: Rudolf R N Reindeer
address: Santa's Workshop Inc.
! Jingle Bell Lane 21
! 1224CH Christmastown
! Northern Nowhere
phone: +12 12 122 1111
fax-no: +12 12 122 2222
nic-hdl: RD212-RIPE
e-mail:Rudolf@localhost
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY-MNT
changed: jbgood@localhost 960412
source: RIPE
***************
*** 1081,1094 ****
inetnum: x.x.x.x/24
netname: XMAS
descr: Santa's Workshop Inc.
! descr: Christmas Toys Manufacturing Facility
! descr: Northern Nowhere
country: NN
admin-c: SC12-RIPE
tech-c: RR212-RIPE
status: ASSIGNED PA
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY
changed: jbgood@localhost 960412
source: RIPE
--- 1081,1094 ----
inetnum: x.x.x.x/24
netname: XMAS
descr: Santa's Workshop Inc.
! Christmas Toys Manufacturing Facility
! Northern Nowhere
country: NN
admin-c: SC12-RIPE
tech-c: RR212-RIPE
status: ASSIGNED PA
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY-MNT
changed: jbgood@localhost 960412
source: RIPE
***************
*** 1095,1111 ****
#[PERSON TEMPLATE]#
person: Santa A Claus
! address: Santa's Workshop Inc.
! address: Jingle Bell Lane 12
! address: 1224CH Christmastown
! address: Northern Nowhere
phone: +12 12 122 1122
! phone: +12 12 122 2211 ext. 1221
fax-no: +12 12 122 121
e-mail: santa@localhost
nic-hdl: SC12-RIPE
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY
changed: jbgood@localhost 960412
source: RIPE
--- 1095,1111 ----
#[PERSON TEMPLATE]#
person: Santa A Claus
! Santa's Workshop Inc.
! Jingle Bell Lane 12
! 1224CH Christmastown
! Northern Nowhere
phone: +12 12 122 1122
! +12 12 122 2211 ext. 1221
fax-no: +12 12 122 121
e-mail: santa@localhost
nic-hdl: SC12-RIPE
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY-MNT
changed: jbgood@localhost 960412
source: RIPE
***************
*** 1113,1127 ****
person: Rudolf R N Reindeer
address: Santa's Workshop Inc.
! address: Jingle Bell Lane 21
! address: 1224CH Christmastown
! address: Northern Nowhere
phone: +12 12 122 1111
fax-no: +12 12 122 2222
e-mail: Rudolf@localhost
nic-hdl: RD212-RIPE
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY
changed: jbgood@localhost 960412
source: RIPE
--- 1113,1127 ----
person: Rudolf R N Reindeer
address: Santa's Workshop Inc.
! Jingle Bell Lane 21
! 1224CH Christmastown
! Northern Nowhere
phone: +12 12 122 1111
fax-no: +12 12 122 2222
e-mail: Rudolf@localhost
nic-hdl: RD212-RIPE
notify: jbgood@localhost
! mnt-by: SANTA-SECURITY-MNT
changed: jbgood@localhost 960412
source: RIPE
***************
*** 1129,1131 ****
--- 1129,1140 ----
____________________________________________________
ripe-142.txt Page 18
+
+
+
+
+
+
+
+
+
*** ripe-191.txt.orig Wed May 2 12:17:03 2001
--- ripe-191.txt Tue May 1 12:22:30 2001
***************
*** 48,56 ****
|with | |
+-------------+---------------------------------------------+
|Registry ID | |
! | | (assigned by RIPE NCC) |
+-------------+---------------------------------------------+
! |Billing | (see 3.4) |
|Category | (SMALL for new contributors) |
+-------------+---------------------------------------------+
--- 48,59 ----
|with | |
+-------------+---------------------------------------------+
|Registry ID | |
! | | |
+-------------+---------------------------------------------+
! |Debtor No. | |
! | | |
! +-------------+---------------------------------------------+
! |Billing | (see secion 3.4) |
|Category | (SMALL for new contributors) |
+-------------+---------------------------------------------+
***************
*** 191,205 ****
and updated from time to time, form an integral part
of and apply fully to this service agreement. Each
revised document will receive a new document number.
! As at January 1st 1999 the documents had the follow-
ing reference numbers:
ripe-173 RIPE NCC General Terms and Conditions
ripe-185 European Internet Registry,
Policies and Procedures
! ripe-186 RIPE NCC Activities & Expenditure
! ripe-187 RIPE NCC Charging Scheme
! ripe-188 RIPE NCC Billing Procedure and Fee Schedule
--- 194,208 ----
and updated from time to time, form an integral part
of and apply fully to this service agreement. Each
revised document will receive a new document number.
! As of January 1st 2001 the documents had the follow-
ing reference numbers:
ripe-173 RIPE NCC General Terms and Conditions
ripe-185 European Internet Registry,
Policies and Procedures
! ripe-213 RIPE NCC Activities, Expenditures and Charging
! Scheme
! ripe-215 RIPE NCC Billing Procedure and Fee Schedule 2001
|
you are here: RIPE -> RIPE Maillists > Archives
