Supporting Notes for the Provider Aggregatable (PA) Assignment Request Form Contents * Introduction * Supporting Notes for the Request Form Templates * Example * References Introduction This document contains instructions for completing the 'Provider Aggregatable (PA) Assignment Request Form'. It is a tool for gathering the information necessary to evaluate the request and to ensure that the same guidelines are applied to each request. Where necessary, the RIPE NCC will ask for additional information. The "Provider Aggregatable (PA) Assignment Request Form" can be found at: http://www.ripe.net/ripe/docs/iprequestform.html A separate form must be completed on behalf of each customer's network or for the infrastructure of the Local Internet Registry (LIR). Do not include requests for more than one customer in one form. The policies and procedures to follow in making IP address space assignment decisions are described in "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region" found at: http://www.ripe.net/ripe/docs/ipv4-policies.html Supporting Notes for the Request Form Templates #[GENERAL INFORMATION]# request-type: pa-ipv4 form-version: 1.3 Please do not alter the value of the 'request-type' and 'form-version' fields. x-ncc-regid: The Registry Identifier (RegID) must be included in every message sent to . It is used to identify the Local Internet Registry (LIR). It has the following format: . Warning: Requests sent to the RIPE NCC that lack a proper RegID (x-ncc-regid) will bounce back to the sender. #[ ADDRESS SPACE USER ]# % % Who will use the address space being requested? organisation-name: organisation-location: website-if-available: If you are making a request in order to make an assignment to a customer or an End User other than the LIR, enter their details here. If the request is for the LIR's infrastructure enter your own details here. In the 'organisation-name' field please enter the complete name of the organisation that will use this assignment of PA address space. In the 'organisation-location' field please enter the location of the main office of the company. In the "website-if-available" field please enter the URL of the organisation"s website if available. % % Does the organisation already have address space that % can meet the needs for this request? Enter "Yes" or "No". space-available: You should only send a request for address space that will be needed in the foreseeable future and for which the End User does not currently have enough space available to cover. If the organisation requesting an assignment does currently have address space that is not in use and could be used for this new assignment, please reply with "Yes" and give an explanation of why more address space is needed. #[CURRENT ADDRESS SPACE USAGE]# In this section, please show how the organisation is using all address space that has been assigned to it in the past, and what its future plans are for that space. Do not include information here for address space they are requesting nor about private address space. Include an entry for each physically separate subnet in the network. Subnets are considered to be physically separate if there is an IP router between them. % % Subnet Immediate Intermediate Entire Purpose % size (/nn) Requirement Requirement Period subnet: totals: Complete the fields as it follows in the next section. #[ADDRESSING PLAN]# number-of-subnets: address-space-returned: In the "number-of-subnets" field please enter the total number of subnets listed in the plan below. Please complete the "address-space-returned" field if the user will be returning address space to another LIR. Please enter the prefixes that will be returned, to which LIR, and when. Include a separate field (address-space-returned:) per prefix. Note that the expected time for renumbering is three months. Use the following syntax for this field: to by % % Subnet Immediate Intermediate Entire Purpose % size (/nn) Requirement Requirement Period subnet: totals: This table represents each subnet and a usage description of the requested address space. Please repeat the "subnet:" field for all subnets requested. Only include information about public address space. Private address space does not need to be described. Please specify the number of IP addresses needed using the CIDR (slash) notation. In the "Subnet size" column please enter the CIDR (slash) notation corresponding to the total number of IP addresses needed for that subnet. (Only specify one subnet size, i.e. if the subnet needs a total of six IP addresses indicate this as /29 NOT /30, /31.) In the "Immediate Requirement", "Intermediate Requirement", and "Entire period" columns please enter in CIDR (slash) notation the number of IP addresses needed immediately and the estimated usage for the next two years. Include interfaces used for hosts, routers, gateways, terminal concentrators, and any other machines requiring one or more network interfaces. (Multiple slash notations may be used, i.e. /30, /31.) In the "Purpose" column please enter a short description of how the subnet being requested will be used. In the "totals" field please enter the total for each column. The amount in the "Subnet size" column total should be the total amount of address space required for this request. % % Which netname will be used when registering this network in % the RIPE Database? netname: Enter the netname that will be used for the inetnum object in the RIPE Database. The netname should be a concise, descriptive name for the network and should reflect the name of the address space user. Valid characters are letters, numbers and dash. Note that the netname that we approve for this assignment must be the netname that is used in the database object. If a different netname is used the object will be classed as "invalid" to the RIPE NCC. If you want to change the netname after approval contact with the same ticket number in the subject line. #[DATABASE INFORMATION]# Network Template This is the information that will be entered in the RIPE database about the organisation requesting the address space. To obtain practical information on using the RIPE database, try: whois -h whois.ripe.net help Network Template Fields --------------------------------------------------------- inetnum: Specifies the IP address range that will be assigned to the enterprise. It will be filled out by the Local IR (or the RIPE NCC in exceptional cases) after the request is approved. It is needed when sending the object to the database. The field can be left blank in the form. netname: A concise, descriptive name for the net- 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 in the person template (see below). country: The ISO 3166 two letter country code which is most appropriate for the organisation; For networks that will cross international boundaries, choose the country in which the administrative contact is based. If you don't know the appropriate country code, use the full name of the country. **admin-c: The NIC handle of the person who is the administrative contact for the network; The administrative contact must be someone who is physically located at the site of the network. More than one contact can be specified by adding more "admin-c" fields. **tech-c: The NIC handle of the technical contact person; The technical contact person does not have to be physically located at the site of the network. There can be more than one name specified in multiple fields for this template. status: Specifies whether the request is provider 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. changed: The e-mail address of the person complet- ing this form, followed by the date; Spec- ify the date in the format as shown in the example. source: The source of the information. This field will always be RIPE and should already be filled in. **NOTE: Each person or role object in the database 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 OR nic-hdl: AUTO-1YourInitials in the "nic-hdl:" field of the object to be added to the database. If "YourInitials" are specified (no less than 2, and no more than 4 letters), the database will use them in constructing a NIC handle. Otherwise, it will determine the letters itself. In 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: AUTO-2) so that you can add more objects in one E- mail message. Person Template: If contact information for the network administra- tion persons entered in the Network Template is already in the RIPE database, then the person han- dling the request should check to see if it is up to date. For each person specified in the network tem- plate for which there is no entry in the RIPE database, one should now be created by using the following template. Person Template Fields -------------------------------------------------------- person: The full name of the person; No official titles and no dots between the names or initials should be used. address: The full postal address, written as it would be for an ordinary postal mail with one line for each part of the address. phone: The work telephone number of the person mentioned above; + . If there is more than one phone number, put each on a sepa- rate line, starting with the most appropri- ate number for the person. fax-no: The fax number of the person specified above, this field is optional. e-mail: The e-mail address of the person specified above. nic-hdl: The person's NIC handle mnt-by: This optional field references a registered maintainer object, which spefifies authori- sation checks on changes to the person 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. changed: The e-mail address of the person submitting the form, followed by the date; Use the format for the date as shown in the example. source: This field will be RIPE and should already be filled in. #[EQUIPMENT DESCRIPTION]# % % Please describe the equipment that will be used in the % network. Indicate the function of the equipment and provide % information regarding the way it uses IP address space. equipment-name: manufacturer-name: model-number: other-data: In the "equipment-name" field please enter the type of equipment requiring public IP addresses (Router, Switch, ATM, Workstation, etc.) for this request. In the "manufacturer-name" field please enter the vendor name for the equipment listed in "equipment-name". In the "model-number" field please enter the model number for the equipment listed in "equipment-name". In the "other-data" field please enter any additional information that would clarify how this equipment or model uses IP address space. For example, the number of cards, ports, or network interfaces that the equipment has. If the software being used by the equipment requires multiple IP addresses, you should also describe this here. Repeat this template (i.e. all four fields) as many times as necessary to describe the equipment relating to the IP address space being requested in the Addressing Plan template. Please leave a blank line between each template. #[NETWORK DESCRIPTION]# % % If your description does not allow the Hostmaster to % understand the request you may be asked additional % questions. Please add any additional information that you % think may facilitate the evaluation of this request below. This is free-text space where you can include additional information that you think will be helpful to the RIPE NCC and the Hostmaster evaluating your request. If the Hostmaster requires additional information in order to understand the request, you may be asked more specific questions. #[NETWORK DIAGRAM]# % % Please enter "Yes" or "No" if you have attached a network % diagram in JPEG or PostScript format to this e-mail % request. diagram-attached: The diagram can be sent as a MIME attachment with your e-mail to . A network diagram (topology map) can be helpful in clarifying the set up of the network and illustrating why the IP addresses being requested are needed. #[END OF REQUEST]# --------------------------------------------------------------------------- Examples #[GENERAL INFORMATION]# request-type: pa-ipv4 form-version: 1.0 x-ncc-regid: nn.santa #[ADDRESS SPACE USER]# % % Who will use the address space being requested" organisation-name: 1st National Bank organisation-location: Polar City, Northern Nowhere website-if-available: Not % % Does the organisation already have address space that % can meet the needs for this request" Enter "Yes" or "No". space-available: No #[CURRENT ADDRESS SPACE USAGE]# Addresses Used Prefix Subnet Mask Size Current 1-yr 2-yr Description 193.1.193.0 255.255.255.192 64 28 34 60 Candy Cane Dept. 193.1.193.64 255.255.255.224 32 10 21 28 Toy Design 193.1.193.96 255.255.255.224 32 8 13 27 Toy Manufacture 193.1.193.128 128 Unused 193.1.194.0 255.255.254 512 317 429 480 Reindeer Training 193.1.196.0 255.255.255 256 132 200 230 Naughty or Nice 1024 495 697 825 Totals #[ADDRESSING PLAN]# number-of-subnets: 3 address-space-returned: None % % Size % in CIDR Immediate 1yr 2yr Purpose subnet: /24 /26,/27 /25,/27 /25,/26 Workstations & printers subnet: /25 /26 /25 /25 Servers, routers & switches subnet: /25 /25 /25 /25 Staff dial-in access totals: /23 /24,/27 /24,/25,/27 /24,/25,/26 % % Which netname will be used when registering this network in % the RIPE Database" netname: NN-1st-National-Bank #[NETWORK TEMPLATE]# inetnum: 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@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[PERSON TEMPLATE]# 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@xmas.nn nic-hdl: SC12-RIPE notify: jbgood@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[PERSON TEMPLATE]# 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@xmas.nn notify: jbgood@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[EQUIPMENT DESCRIPTION]# % % Please describe the equipment that will be used in the % network. Indicate the function of the equipment and provide % information regarding the way it uses IP address space. equipment-name: Workstations manufacturer-name: Dell model-number: Optiplex GX150 other-data: 230 units equipment-name: Printers manufacturer-name: HP model-number: Laserjet VII other-data: 15 units equipment-name: Switches manufacturer-name: Cisco model-number: Catalyst 5500 other-data: equipment-name: Routers manufacturer-name: Cisco model-number: 7300 other-data: equipment-name: Servers manufacturer-name: Sun model-number: Fire v1280 other-data: 20 " 25 units #[NETWORK DESCRIPTION]# % % If your description does not allow the Hostmaster to % understand the request you may be asked additional % questions. Please add any additional information that you % think may facilitate the evaluation of this request below. We will have 4 ISDN30 coming in to the dial-up server to serve approximately 100 staff members. #[NETWORK DIAGRAM]# % % Please enter "Yes" or "No" if you have attached a network % diagram in JPEG or PostScript format to this e-mail % request. diagram-attached: No #[END of REQUEST]# Best Regards, Santa Claus Network Administrator Santa's Workshop Inc. --------------------------------------------------------------------------------- #[GENERAL INFORMATION]# request-type: pa-ipv4 form-version: 1.0 x-ncc-regid: nn.santa #[ADDRESS SPACE USER]# % % Who will use the address space being requested? organisation-name: Snowflake Cybercafe organisation-location: Polarcity, Northern Nowhere website-if-available: www.snowflake.nn % % Does the organisation already have address space that % can meet the needs for this request? Enter "Yes" or "No". space-available: No #[ADDRESSING PLAN]# number-of-subnets: 3 address-space-returned: 192.168.28.0 - 192.168.29.255 to nn.teleco on 20030531 % % Size % in CIDR Immediate 1yr 2yr Purpose subnet: /24 /25 /25,/26 /24 Customer cyberstations subnet: /25 /26 /25 /25 Game servers subnet: /25 /26,/27 /25 /25 Routers, switches, printers totals: /23 /24,/27 /24,/25,/26 /23 % % Which netname will be used when registering this network in % the RIPE Database? netname: SNOWFLAKE-LAN #[NETWORK TEMPLATE]# inetnum: 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@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[PERSON TEMPLATE]# 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@xmas.nn nic-hdl: SC12-RIPE notify: jbgood@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[PERSON TEMPLATE]# 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@xmas.nn notify: jbgood@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[EQUIPMENT DESCRIPTION]# % % Please describe the equipment that will be used in the % network. Indicate the function of the equipment and provide % information regarding the way it uses IP address space. equipment-name: Router manufacturer-name: Cisco model-number: 6712 other-data: equipment-name: Servers manufacturer-name: Intel model-number: Pentium 4 Entry Level IDE Server other-data: 50 " 60 units equipment-name: Cyberstations / PCs manufacturer-name: Dell model-number: Optiplex GX150 other-data: 230 units #[NETWORK DESCRIPTION]# % % If your description does not allow the Hostmaster to % understand the request you may be asked additional % questions. Please add any additional information that you % think may facilitate the evaluation of this request below. This request is a one to one renumbering. #[NETWORK DIAGRAM]# % % Please enter "Yes" or "No" if you have attached a network % diagram in JPEG or PostScript format to this e-mail % request. diagram-attached: No #[END of REQUEST]# Best Regards, Santa Claus Network Administrator Santa's Workshop Inc. #[GENERAL INFORMATION]# request-type: pa-ipv4 form-version: 1.0 x-ncc-regid: nn.santa #[ADDRESS SPACE USER]# % % Who will use the address space being requested" organisation-name: Santa's Workshop Inc. organisation-location: Polar City, Northern Nowhere website-if-available: www.santasworkshop.nn % % Does the organisation already have address space that % can meet the needs for this request" Enter "Yes" or "No". space-available: No #[ADDRESSING PLAN]# number-of-subnets: 14 address-space-returned: No % % Size % in CIDR Immediate 1yr 2yr Purpose subnet: /23 /24 /23 /23 Dynamic Dial-up Lagos subnet: /23 /24 /23 /23 Dynamic Dial-up Kiev subnet: /23 /24 /23 /23 Dynamic Dial-up Bagdad subnet: /23 /24 /23 /23 Dynamic Dial-up Bucarest subnet: /23 /24 /23 /23 Dynamic Dial-up Cairo subnet: /23 /24 /23 /23 Dynamic Dial-up Budapest subnet: /23 /24 /23 /23 Dynamic Dial-up Warsaw subnet: /23 /24 /23 /23 Dynamic Dial-up Prague subnet: /23 /24 /23 /23 Dynamic Dial-up Lisbon subnet: /23 /24 /23 /23 Dynamic Dial-up Madrid subnet: /22 /24 /23,/24 /22 Dynamic Dial-up London subnet: /22 /24 /23,/24 /22 Dynamic Dial-up Berlin subnet: /23 /24 /23 /23 Dynamic Dial-up Paris subnet: /23 /24 /23 /23 Dynamic Dial-up Rome totals: /19 /21,/22,/23 /20,/21,/22,/23 /19 % % Which netname will be used when registering this network in % the RIPE Database? netname: SANTA-OPS-DIALUP #[NETWORK TEMPLATE]# inetnum: 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@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[PERSON TEMPLATE]# 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@xmas.nn nic-hdl: SC12-RIPE notify: jbgood@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[PERSON TEMPLATE]# 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@xmas.nn notify: jbgood@antarctic.nn mnt-by: SANTA-SECURITY-MNT changed: jbgood@antarctic.nn 19960412 source: RIPE #[EQUIPMENT DESCRIPTION]# % % Please describe the equipment that will be used in the % network. Indicate the function of the equipment and provide % information regarding the way it uses IP address space. equipment-name: Access Server manufacturer-name: Cisco model-number: 5300 other-data: one for each of the local operations #[NETWORK DESCRIPTION]# % % If your description does not allow the Hostmaster to % understand the request you may be asked additional % questions. Please add any additional information that you % think may facilitate the evaluation of this request below. All locations will have dynamic dial-up deployed for our local operatives to keep in touch with central offices. User modem ratio = 10:1. The access servers can provide up to 240 concurrent connections each, they will backhaul traffic via multiple E1s to our satellite set-up. #[NETWORK DIAGRAM]# % % Please enter "Yes" or "No" if you have attached a network % diagram in JPEG or PostScript format to this e-mail % request. diagram-attached: Yes #[END of REQUEST]# Best Regards, Santa Claus Network Administrator Santa's Workshop Inc References IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region http://www.ripe.net/ripe/docs/ipv4-policies.html RIPE Database User Manual: Getting Started http://www.ripe.net/ripe/docs/db-start.html