NOC/ IP-addresses/ Recommendations on how to prepare applications for IP-addresses (for Lucky.net customers).

Brief recommendations on how to prepare applications for IP-addresses.

1. It is mandatory that you send the application (phone requests and personal letters cannot serve as the sufficient ground for allocating a network).

2. The application should be sent to registry@lucky.net

3. Application form:
   ripe-141 (European IP Address Space Request Form)
   ftp://ftp.ripe.net/ripe/docs/ripe-141.txthttp://www.ripe.net/ripe/docs/ripe-141.html
    
   Detailed recommendations on how to fill out the application:
   ripe-185 (European Internet Registry Policies and Procedures)
   ftp://ftp.ripe.net/ripe/docs/ripe-185.txt
    
   Brief "manual":
   ripe-142 (Supporting Notes for the European IP Address Space Request Form)
   ftp://ftp.ripe.net/ripe/docs/ripe-142.txt
   http://www.ripe.net/ripe/docs/ripe-142.html
    
   Syntax checking (of filling out of application):
   The RIPE 141 syntax checking web page http://www.ripe.net/cgi-bin/web141/web141.pl.cgi

4. Save delimiters of templates (like: [# ORGANIZATION OVERVIEW TEMPLATE #],
   and preferably the order too. (see. ripe-141)
   Names of fields - as specified in the form. Mandatory fields must be filled out,
   non-mandatory can be left blank (but name of field should be kept).

5. #[REQUESTER TEMPLATE]#
   Leave blank.

6. #[USER TEMPLATE]#
   Here you must specify name of your organization and other data about you.

7. ORGANIZATION OVERVIEW - the most important and most complicated field.
   Here you must provide persuasive description of why do you need the block of addresses. How the organizational structure and planned dynamics of development of your organization will impact the structure of network (subnetting). It is also very important that you provide all possible reasons to illustrate that your request is in fact very modest one if taken in the context of your company ‘s plans. You must also make it implicit that your request is only the basic one that will help you get by for some time (everyone has their own basic reqs.)

   From the OVERVIEW you should make logic transition to subnetting planning and to the general structure of the network. Key phrases:
   • ORGANIZATION is the large/middle sized/small provider (corporation, enterprise) with big plans, which has certain number of relatively independent structural sub-divisions (departments) and/or technical platforms (points of presence), and each of these sub-divisions has its own LAN and is connected to the rest of the world and other sub-divisions via the point-to-point channels;
   • number of dial-up users is such and such, hence there is a need for ??? dynamic IP-numbers;
   • moreover, you have ??? corporate customers, and each one of them needs 8/16/32/64 addresses for their publicly accessible servers (WWW, FTP, etc.), and all the real structure of their enormous networks will be hidden and no one will have to worry about it;
   • ORGANZIATION has future developments plans. The planned growth of the number of jobs in the company's networks is ??? per year. There are plans to get connected ??? corporate customers. During the initial three years the specified number of addresses should be enough, though you’ll have to use some crafty tricks to survive.
   • ORGANIZATION uses networks of other providers. In the request form you should also specify what networks do you use, as well as what networks and when you will return. Names of the networks to be returned should be specified in address-space-returned field located in REQUEST OVERVIEW section; you should also specify their current usage in CURRENT ADDRESS SPACE USAGE section;
   
    

8. #[CURRENT ADDRESS SPACE USAGE TEMPLATE]#
   Describe what you have.
   For example:

   Relative	Addresses Used
   Prefix	Subnet Mask	Size	Current	1-yr	2-yr	Description
   193.XXX.XX.0 193.XXX.XX.XX	255.255.255.192 255.255.255.192	64 64	62 62	62 62	62 62	Roga & Kopita, Ltd. Office net

   
    

9. REQUEST OVERVIEW TEMPLATE
   Например:

   request-size: x.x.x.x/24
   addresses-immediate: 256
   addresses-year-1: 256
   addresses-year-2: 256
   subnets-immediate: 4
   subnets-year-1: 4
   subnets-year-2: 4
   inet-connect: Connected via Lucky Net
   country-net: UA
   private-considered: Yes
   request-refused: No
   PI-requested: NO
   address-space-returned: XXX.XXX.XX to RELCOM
   request-size: 256
   addresses-immediate: 86
   addresses-year-1: 210
   addresses-year-2: 235
   

10. ADDRESSING PLAN TEMPLATE
    For example:

    Relative	Addresses Used
    Prefix#	Subnet Mask	Size	Immediate	1-yr	2-yr	Description
    0.0.0.0 0.0.0.64 0.0.0.128 0.0.0.192	255.255.255.192 255.255.255.192 255.255.255.192 255.255.255.192	64 64 64 64	62 62 62 62	62 62 62 62	62 62 62 62	Customer 1 Office net Customer 2 Dynamic block

    (in the subnet with 64 addresses we can in fact use 64-2=62). Same also true about any other broadcast network (like Ethernet) -- in reality we can use two addresses less than we have in a mask.

11. NETWORK TEMPLATE
     
    admin-c и tech-c
    Preferably specify handle.
    If person had already been entered into RIPE-db, you can skip PERSON TEMPLATE.

    If not entered into db and there's no handle the object "person" is MANDATORY. It is preferable that you specify different persons as technical and administrative contacts.

    Top of the page