   |
Заявка для получения статуса Локальной Регистратуры в RIPE NCC |
|
Заявка состоит из формы, заполняемой для регистрации обьекта *regid*
в базе данных RIPE NCC по Локальным регистратурам и дополнительных вопросов. Не забудьте привести данные по контактным персонам в случае, если они отсутствуют в базе данных RIPE. Пеpед отсылкой удалите, пожалуйста, все вспомогательные тексты. Примечания:
Guidelines for Setting up a Local Internet Registry at
the RIPE NCC
Jeroen Bet
Document ID: ripe-212
Obsoletes: ripe-160
Date: August 10, 2000
------------------------------------------------------
Appendix A
-------------------------------------------- cut here
-----------------------------------------------
regid:
org:
type:
Community Served:
address:
country:
admin-c:
tech-c:
phone:
fax-no:
e-mail:
remark:
lst-localir:
lst-contrib:
bill-addr:
bill-mail:
bill-ref:
bill-vatno:
bill-proto:
bill-categ:
bill-scheme:
bill-remark:
reg-ack:
services:
Questions:
1. Does the organisation already operate a Local Internet
Registry in the RIPE NCC region or is the organisation
a member of ARIN or APNIC?
If yes, please give us a short explanation why an additional
LIR in the RIPE NCC region has to be opened?
2. Does the organisation already use address space from
an upstream provider or from a PI block of addresses?
Please list it here. Please only list address space being
used for the organisation's own internal network, and
not address space being used for customers (other than
dial-up or web servers). Please include address space
for the entire organisation, not just this subsidiary.
Please explain whether the address space will be returned
after the new LIR is set up.
3. What type of organisation is this and what services
or products do they provide?
Please list the kind of services you offer (like ADSL,
Dial-up, Web hosting, VOIP etc.)
4. What are the main reasons for becoming an LIR, rather
than requesting address space from the upstream provider?
5. Please tell us who your transit providers / peers will
be?
6. How much address space does the organisation expect
to need in the next year or so?
We would like to know how much address space your LIR
will be needing in the next 2 years. We would like to
have a deployment plan on how you will be using the
address space allocation. The plan should include a list
of events that will lead to the use of the allocated
addresses, along with the dates that the events will
occur. Please try to give us an estimate in a 2 year time
frame, not just the next couple of months. The deployment
plan does not have to be in the same format as the table
above but it has to provide the same information. This
information will be handled in strict confidence and may
also be of aid to your first address space request.
--------------------------------------------- cut here
--------------------------------------------
If possible, please send completed forms by e-mail!
Sending in handwritten forms will delay processing
considerably!
The RIPE NCC publishes the fields marked "Published in
LIR List" on
http://www.ripe.net/ripencc/mem-services/general/indices/data/
for reference of those trying to contact a particular
registry.
Any questions about this form should be directed to
<new-lir@ripe.net>
Description of all the individual fields:
Registry Identifier (regid)
regid: This string uniquely identifies an LIR. The format
is <cc>.<name> where <cc> is the ISO
3166 country code where the LIR is located and <name>
is a somewhat descriptive identifier unique within the
country. If an LIR services several countries, please
choose the country where the LIR has its main office.
Please note that this is only an administrative identifier
and is not necessarily associated with your business.
The RIPE NCC may change the regid if it resembles another
regid closely.
If you want to change the regid after the LIR has been
set up, the RIPE NCC will charge an extra set up fee for
any administrative overhead.
Mandatory, Single Line Only, Single Attribute per Object,
not Published in the LIR List.
Organisation Name
org: A short descriptive name of the organisation running
the LIR. It is used in lists and wherever a short
description is appropriate.
Mandatory, Single Line Only, Single Attribute per Object,
Published in the LIR List.
LIR Type
type: The type field specifies whether this is a PROVIDER
LIR that will be assigning addresses to customers of
theirs, or if this is an ENTERPRISE that will only be
assigning addresses within its organisation. Please fill
in either "ENTERPRISE" or "PROVIDER" in this field.
Mandatory, Single Line Only, Single Attribute per Object,
Published in the LIR List.
Community Served
community: A short and concise description of the community
served by this LIR. For service providers something like
"The LIR will serve customers of <foo> organisation, an
Internet service provider in countries NN AA BB and CC
serving mainly <bar> type customers." is sufficient.
Please also indicate whether you are prepared to serve
those not buying any other service from you. Use multiple
lines for longer text.
Mandatory, Multi-Line Attribute, Published in the LIR
List.
Postal Address
address: The full postal address of the LIR. This should
be exactly what is needed to deliver postal mail, including
the name of the organisation and the country. Multiple
lines are represented by multiple `address' attributes.
Mandatory, Multi-Line Attribute, Published in the LIR
List.
Countries Served
country: The countries to which this LIR assigns addresses,
or provides services. Please use two-letter ISO 3166
codes. Note that there can be multiple country codes in
this field.
Mandatory, Single Line Only, Published in the LIR List.
Administrative Contact
admin-c: A reference to the RIPE database object of the
person(s) administratively responsible for the LIR. The
preferred form is the full name, followed by the NIC
handle* (in brackets). An e-mail address is not sufficient
here. Please check if the person you are entering as an
admin-c or tech-c is registered in the RIPE database. If
not, then register the contacts in the RIPE database
first before you submit the application.
* Please see below for more information.
Mandatory, Published in the LIR List.
Technical Contact
tech-c: A reference to the RIPE database object of the
person(s) executing the LIR work. The preferred form is
the full name, followed by the NIC handle (in brackets).
* Please see below for more information.
Mandatory, Published in the LIR List.
* PLEASE NOTE: We need the administrative and technical
contact persons (admin-c and tech-c) mentioned in the
LIR form registered in the RIPE database. We would
appreciate it if you send in templates for these persons
to the database first. (See RIPE NCC Database Documentation
on creating a new database object.) The RIPE NCC may
ask you to clean up old or duplicate person objects that
have become invalid.
Telephone Number
phone: The general phone number to be called on LIR
matters. If more than one is listed the preferred ones
should be listed first.
Format is +<country code> <number> [ext <extension>].
Extensions should only be mentioned explicitly if they
cannot be dialed directly.
Mandatory, Published in the LIR List.
Telefax Number
fax-no: The general FAX number to be used for LIR matters.
If more than one is listed the preferred ones should be
listed first.
Format is +<country code> <number> [ext <extension>].
Extensions should only be mentioned explicitly if they
cannot be dialed directly.
Optional, Published in the LIR List.
Electronic Mail Address
e-mail: The general electronic mail address to be used
for LIR matters. This has to be in RFC 822 format. When
using a temporary e-mail address, please update it by
sending us the new address as soon as it is operational.
Mandatory, Published in the LIR List.
Remarks
remark: Any useful remarks in free form text.
Optional, Multi-Line Attribute, Published in LIR List.
Local Registries Mailing List
lst-localir: The e-mail addresses to be added to the
mailing list of all "Local Internet Registries". This
list is used to make general announcements. Relevant
discussions about LIR issues are held on the lir-wg
mailing list (Local IR working group). At least one
address is required to be subscribed to the LIR mailing
list. It is recommended that LIRs follow the lir-wg as
well, since normally policies are discussed in this forum.
We will therefore subscribe the address supplied here to
both mailing lists. To change the mailbox subscribed to
the localir mailing list, please write to
<hostmaster@ripe.net>
To change the mailbox subscribed to the lir-wg or to
unsubscribe from this list, please mail
<majordomo@ripe.net>
Mandatory, Not Published.
General Assembly Mailing List
lst-contrib: The addresses to be added to the mailing
list of the "RIPE NCC General Assembly". This Assembly
consists of all organisations contributing to RIPE NCC
funding and discusses formal aspects of RIPE NCC operation
such as the budget and charging.
Mandatory, Not Published.
Billing Address
bill-addr: This is the full postal address to send
billing-related information. It should contain the name
of the responsible person. If no person is mentioned in
the billing address, the admin-c of the LIR will be listed
as a billing contact.
Mandatory, Multi-Line Attribute, Not Published.
Electronic Billing Address
bill-mail: This is the e-mail address to send billing-related
information.
Mandatory, Not Published.
Billing Reference
bill-ref: This is some text that will be included in any
bill for reference by the customer, e.g. purchase order
numbers.
Optional, Single Line Only, Single Attribute per Object,
Not Published.
VAT Number
bill-vatno: This is the VAT number that is required for
billing LIRs inside the European Union without Value
Added Tax. If we do not have this number, Dutch VAT will
be billed. If your LIR has no billing address in the EU,
please write outside EU.
Optional, Single Line Only, Single Attribute per Object,
Not Published.
Billing Preference
bill-proto: The RIPE NCC sends all invoices out by MAIL
and E-MAIL. If you state E-MAIL ASCII in this field, the
RIPE NCC will additionally e-mail the invoice to the
bill-mail address in ASCII format.
Optional, Single Line Only, Single Attribute per Object,
Not Published.
Billing Category
bill-categ: This is the current billing category. All
new Local Internet Registries will have the initial
billing category set to `SMALL'. Please state `ENTERPRISE'
if this is an enterprise LIR making assignments only
within its own organisation.
Mandatory, Single Line Only, Single Attribute per Object,
Published in LIR List.
Billing Scheme
bill-scheme: This is the applicable billing scheme. YEARLY
is the normal billing scheme. HALF YEARLY and QUARTERLY
are possible by special prior arrangements, but an extra
fee is charged. The string LATE after the scheme indicates
that we agreed that invoices due in December can be paid
in January. See the billing procedure document RIPE NCC
Billing Procedure and Fee Schedule for details of applicable
charges, etc.
Mandatory, Single Line Only, Single Attribute per Object,
Not Published.
Billing Remark
bill-remark: Any useful remarks concerning billing.
Optional, Multi-Line Attribute, Not Published.
LIR Acknowledgments
reg-ack: This controls the verbosity of acknowledgments
of address space requests sent to the LIR.
The acknowledgments contain information about your address
space requests such as the assigned ticket number and
the processing priority. You can choose to receive a
`LONG' acknowledgment, with more detailed explanation if
you state `LONG' in this field. If you opt for a shorter
acknowledgment, which will contain only the necessary
information, you may write `SHORT'.
Optional, Single Line Only, Single Attribute per Object,
Not Published.
Services
services: This field will show our hostmasters what kind
of services your organisation offers (like VOIP, ADSL,
xDSL, GPRS, Leased Lines, and Dial-up etc.).
Optional, Multi Line Attribute, Not Published
Sample Form
regid: nn.example
org: E.X.Ample Net
type: PROVIDER
community: The LIR will serve customers of E.X. Ample
community: Networking Ltd., an internet
community: service provider in NN
community: AB serving mainly x-type customers.
community: We will also serve
community: those not buying other services from us.
address: E.X. Ample Networking Ltd.
address: LIR Sq.
address: NN-1822 Internet City
address: Northern Nowhere
country: NN AB
admin-c : Ad Ministrator (AM999-RIPE)
tech-c : Joe Technical (JT1234)
phone: +12 345 6789
fax-no: +12 345 9876
e-mail: LIR@anet.nn
remark:
lst-localir: LIR@anet.nn
lst-contrib: ad.ministrator@anet.nn
bill-addr: E.X. Ample Networking Ltd.
bill-addr: Ad Ministrator
bill-addr: LIR Sq.
bill-addr: NN-1822 Internet City
bill-addr: Northern Nowhere
bill-mail: ad.ministrator@anet.nn
bill-ref: PO4711
bill-vatno: NN-9876 5432 1 00
bill-proto: E-MAIL ASCII
bill-categ: SMALL
bill-scheme: YEARLY
bill-remark:
reg-ack: LONG
services: ADSL, Webhosting, Dial-up
Questions:
1. Does the organisation already operate a Local Internet
Registry in the RIPE NCC region or is the organisation
a member of ARIN or APNIC? If yes, please give us a
short explanation why an additional LIR in the RIPE NCC
region has to be opened?
No.
2. Does the organisation already use address space from
an upstream provider or from a PI block of addresses?
Please list it here. Please list only address space
being used for the organisation's own internal network,
and not address space being used for customers (other
than dial-up or web servers). Include address space for
the entire organisation, not just this subsidiary. State
whether the address space will be returned after the
new LIR is set up.
193.0.0/19 allocated to sn.ample, out of this 193.0.10/23
is being used for the Northern Nowhere network, which
will be returned when the new LIR receives its own
allocation.
3. What type of organisation is this and what services
or products do they provide? Please list the kind of
services you offer (like ADSL, Dial-up, Webhhosting,
VOIP etc.).
We are a new service provider in xx. We offer Dial-up,
webhosting and leased line connectivity to mainly business
customers.
4. What are the main reasons for becoming an LIR, rather
than requesting address space from the upstream provider?
We want to use BGP and connect to 2 upstream providers.
5. Please tell us who your transit providers / peers
will be?
Nl.bluelight (ASxxx) and zz.example (ASyyy)
6. How much address space does the organisation expect
to need in the next year or so?
We would like to know how much address space your LIR
will be needing in the next 2 years. We would like to
have a deployment plan on how you will be using the
address space allocation. The plan should include a list
of events that will lead to the use of the allocated
addresses, along with the dates that the events will
occur. Please try to give us an estimate in a 2-year
time frame, not just the next couple of months.
Below is an example of a deployment plan:
---------------------------------------------------------------
Planned Date Equipment Type of Equipment Number Location
Operational Ordered of
Date Hosts
---------------------------------------------------------------
08/2000 06/2000 Backbone routers 254 Paris
12/2000 07/2000 modems for POP 768 London
03/2001 09/2000 modems for POP 512 Berlin
10/2001 07/2001 Cable modems 254 Madrid
02/2002 11/2001 Routers and Modems 1024 Lisbon
for leased lines
05/2002 02/2002 modems for POP 512 Rome
---------------------------------------------------------------
The deployment plan does not have to be in the same
format as the table above but it has to provide the
same information. This information will be handled in
strict confidence and may also be of aid to your first
address space request.
|
