Supporting Notes for the
Provider Aggregatable (PA) Assignment Request Form
T-Com Croatia
Internet network
Croatian Telecom Inc., Zagreb,
Croatia
Based on RIPE
document: ripe-489
General
Information
#[GENERAL INFORMATION]#
%
% Please add your RegID.
request-type: pa-ipv4
form-version: 1.1
x-ncc-regid: [Popunjava T-Com]
Please do not change the value of
any field in this section.
Address
Space User
#[ADDRESS SPACE USER]#
%
% Who will use the requested address space?
legal-organisation-name: Pucka Banka
organisation-location: Puckograd, HR
website-if-available: http://www.pb.hr
% Does this End User already have address space that can be
% used for this assignment? (Yes/No)
space-available: No
Enter the legal name and primary
location of the organisation that will use this
address space in the “legal-organisation-name:”
and “organisation-location:” fields. If this End User has a website,
enter the URL in the “website-if-available:”
field. Otherwise, enter “none” in this field.
If there is any address space
assigned to this End User that is not in use, indicate this in the “space-available:” field. If you answer
“yes”, you can explain why the End User needs another assignment of
address space in the “Network Description”
section at the end of this form.
Addressing
Plan
#[ADDRESSING PLAN]#
% As of 1 January 2010 assignments are for a period of up to 12 months.
% As of 1 July 2010 assignments are for a period of up to 9 months.
% As of 1 January 2011 assignments are for a period of up to 6 months.
% As of 1 July 2011 assignments are for a period of up to 3 months.
%
% How will the End User use this address space?
%
% Subnet Immediate Intermediate Entire Purpose
% size (/nn) Requirement Requirement Period
subnet: /26 32 64 64 Employee VPN Access
subnet: /26 18 34 64 Financial Services
subnet: /26 22 30 60 Workstations
subnet: /27 11 15 28 Public Services
subnet: /27 7 18 30 Operations
subnet: /24 176 192 240 Branch Offices
totals: /23 266 353 486
number-of-subnets: 6
% Will the End User return any address space?
address-space-returned: 85.118.187/24 to nl.bluelight in 3 months
The addressing plan shows how the End User will use the requested address
space. You can repeat the "subnet" row as many times as needed.
Delete any empty "subnet" fields before you send the request. In the
"Subnet size (/nn)" column, enter a slash
notation prefix for each subnet. Each entry should be large enough to contain
the number of addresses needed for that subnet over the next time period.
In order to demonstrate the predicted growth of your network, you must
provide an estimate of the address space you will require over three distinct
periods: Immediate, Intermediate and the Entire period. Your estimates should
include interfaces used for hosts, routers, gateways, terminal concentrators
and any other machines requiring one or more network interfaces. These columns
can either contain numbers (for example, 128) or slash notation prefixes (for
example, /25). Multiple slash notation prefixes must be separated by comma(s)
with no blank spaces (for example, /25,/27).
Starting on 1 January 2010, a gradual reduction in the assignment period
will be applied. As the assignment period changes, so too will the information
required:
Up to 30 June 2010, assignments are for a period of up to twelve months.
Therefore, your request should reflect your immediate requirements, predicted
requirements for the coming six months, and predicted requirements for the
coming twelve months.
As of 1 July 2010, assignments are for a period of up to nine
months. Your request should reflect your immediate requirements, predicted
requirements for the coming six months, and predicted requirements for the
coming nine months.
As of 1 January 2011, assignments are for period of up to six months.
Your request should reflect your immediate requirements, predicted requirements
for the coming three months, and predicted requirements for the coming six
months.
As of 1 July 2011, assignments are for a period of up to three
months. Your request should reflect your immediate requirements, predicted
requirements for the coming two months, and predicted requirements for the
coming three months.
In the “Purpose” column, write a short description of each
subnet. If needed, you can write a more detailed description in the
“Network Description” section at the end of this form.
In the “totals” row, add the total of
each column. The total of the “Subnet size (/nn)” column should be the total amount of
address space you are requesting for this assignment.
In the “number-of-subnets:” field, enter
the total number of subnets listed in the addressing plan.
The “netname:” should be a short, descriptive name for the network
and should reflect the End User’s organisation
name. You should use the same “netname:” when you register this assignment in the RIPE Whois Database.
If there is any address space assigned to the End User that they will
return, list each prefix in separate “address-space-returned:”
fields. The expected time for renumbering is three months. You can use the
following syntax: <x.x.x.x/xx> to <which
LIR/ISP> in <time period> for this field.
Equipment Description
#[EQUIPMENT DESCRIPTION]#
%
% What equipment will be used and how will it use the
% requested address space?
equipment-name: Core switches
manufacturer-name: Cisco
model-number: 25xx
other-data: 3 units
equipment-name: Servers
manufacturer-name: HP
model-number: various
other-data: 40 units
equipment-name: Firewalls
manufacturer-name: Cisco
model-number: PIX 515 E
other-data: 2 units, 8 IP addresses
equipment-name: Workstations
manufacturer-name: Dell
model-number: GX150
other-data: 22 units, 1 IP address each
equipment-name: Routers
manufacturer-name: Cisco
model-number: 3825
other-data: 2 units
equipment-name: Routers
manufacturer-name: Cisco
model-number: AS5300
other-data: 1 unit, 32 ports
The equipment description will
help us (RIPE NCC) to understand the requirements listed in the addressing plan
and can be repeated as many times as needed. Leave an empty line before each
new “equipment-name:” field.
In the “equipment-name:”
field, enter the type of equipment requiring address space from this
assignment.
Enter the vendor name and model
number for the piece of equipment in the “manufacturer-name:”
and “model-number:” fields.
If you have any more information
about how this piece of equipment will use the requested address space, add
this in the “other-data:” field.
Network Description
#[NETWORK DESCRIPTION]#
%
% Please add more information if you think it will help us
% understand this request.
We have 11 branches across Puckograd linked by corporate fibre channels.
We will assign a /28 subnet for each branch.
Each branch will have SMTP, WWW, file server, e-banking and dial-up pool.
Public Internet Services: SMTP (2 IP addresses),
WWW (6 IP addresses, 2 servers), FTP (1 IP address), DNS (2 IP addresses)
Financial Services: 6 servers, 3 IP addresses each.
Operations network: Security, Monitoring, VPN, Proxy, DNS
You can use this space for
additional information that you think will be helpful for us when we evaluate
your request. A clearer understanding of the network and its addressing needs
can help us to evaluate your request more quickly.
Network
Diagram
#[NETWORK DIAGRAM]#
%
% Have you attached a network diagram to this request? (Yes/No)
diagram-attached: Yes
A network diagram (topology map)
can help us to understand the set-up of the network and its addressing needs.
Network Template
#[NETWORK TEMPLATE]#
%
% Please complete all of the fields below.
inetnum: [Popunjava T-Com]
netname: PB-NET
descr: Pucka Banka
country: HR
admin-c: Pero R Peric
tech-c: Zivojin Miric
status: ASSIGNED PA
mnt-by: [Popunjava T-Com]
changed: hostmaster@ripe.net
source: RIPE
Leave the "inetnum:"
field empty as we will choose the address range.
The "netname:" should be a short
and descriptive name for the network and should reflect the organisation
name of the End User.
Enter the End User's organisation name in the "descr:" field.
Use the ISO country code of the
End User's location in the "country:" field.
If the End User is multi-national, repeat the "country:"
field as many times as needed. Alternatively, you can use EU or ZZ if you do
not wish to show the End User's location in the inetnum
object.
The full name in the "admin-c:" field should reflect someone who is
administratively responsible for the network. The admin-c must be physically
located at the site of the network. If there is no entry for the contact person
in the RIPE database, the person object has to be created by completing the
details in the person template.
The full name in the "tech-c:" field should reflect someone who has technical
knowledge of the network. The tech-c does not need to be physically located at
the site of the network. If there is no entry for the contact person in the
RIPE database, the person object has to be created by completing the details in
the person template.
The "status:"
field must be ASSIGNED PA.
The "mnt-by:" field shows which
maintainer authenticates object updates.
The RIPE Database must contain
all of the objects that you use.
The "changed:"
field must be hostmaster@ripe.net.
The "source:"
field must be RIPE.
Person Template
If contact information for the
network administration persons entered in the Network Template is already in
the RIPE database, then the person handling the request should check to see if
it is up to date. For each person specified in the network template for which
there is no entry in the RIPE database, one should now be created by using the
following template.
#[PERSON TEMPLATE]#
person: Pero P Peric
address: Pucka banka
address: Bankarska aleja 12
address: HR-66544 Puckograd
address: Croatia
phone: +385 66 122 1122
phone: +385 66 122 2211 ext. 1221
fax-no: +385 66 122 121
e-mail: pperic@pb.hr
nic-hdl: AUTO-1
notify: netko@nesto.hr
mnt-by: [Popunjava T-Com]
changed: [Popunjava T-Com]
source: RIPE
#[PERSON TEMPLATE]#
person: Zivojin Miric
address: Metal-promet d.o.o.
address: Mrezni pogon
address: Strojarska 121
address: HR-66544 Krnjak
address: Croatia
phone: +385 66 122 1111
fax-no: +385 66 122 2222
nic-hdl: AUTO-1
e-mail: zivko@m-pogon.hr
notify: netko@nesto.hr
mnt-by: [Popunjava T-Com]
changed: [Popunjava T-Com]
source: RIPE
The "person:"
field must be the full name of the person. No official titles and no dots
between the names or initials should be used.
In the "address:"
field enter the full postal address, written as it
would be for an ordinary postal mail with one line for each part of the
address.
The "phone:"
field must be the work telephone number of the person mentioned above;
+<country code> <area code> <telephone number>. If there is
more than one phone number, put each on a separate line, starting with the most
appropriate number for the person.
The "fax-no:"
field should contain the fax number of the person specified above, this field
is optional.
The "e-mail:"
field is the e-mail address of the person specified above.
The "nic-hdl:" field should be
the The person's NIC handle.
If person does not exist in RIPE database, field must be AUTO-1.
The "notify:"
is optional field that specifies an e-mail address to which notifications of
changes to the object should be sent.
The "mnt-by:" optional field
shows which maintainer authenticates object updates.
The "changed:"
is the e-mail address of the person submitting the form, followed by the date.
Use the <yymmdd> format for the date as shown
in the example.
"source:" field will be RIPE
and should already be filled in.
End of Request
#[END of REQUEST]#
Best Regards,
Zelimir Hrmpak
Pucka banka
Please write your full name below
the “#[END
of REQUEST]#” header.