|
|
INSTRUCTIONS FOR REQUESTING INTERNET PROTOCOL (IP) NUMBERS FROM NJEDge.Net |
|
Completion of the Network Version Number: 3.0 template above is required to obtain
NJEDge.Net Internet protocol (IP) Network Numbers.
In the Subject field of the E-mail message, use the words: IP REQUEST.
Please submit the template via E-mail to NJEDge.Net at: njedge@njedge.net.
For more information, see: NJEDge.Net
|
**PLEASE READ THE FOLLOWING INFORMATION PRIOR TO REQUESTING AN IP NUMBER**
|
|
NOTE: Your organization will be assigned address space for an immediate to one (1) year requirement.
|
| Section 1. Institution Details |
| 10. |
If you already have an OrgID in ARIN please list it here and go to next section (your existing OrgID must include POC details, if not please fill this section) |
| 1a. |
Please enter the Legal Name of the Educational institution as it is registered with
local, regional or national authorities. |
| 1b. |
Please enter the Street Address for the Educational institution. (If you are
updating the street address of an existing Org ID, you must include
all address lines.) |
| 1c. |
Please enter the Street Address for the Educational institution. (If you are updating the street address of an existing Org ID, you must include
all address lines.) |
| 1d. |
Please enter the City of the Educational institution |
| 1e. |
Please enter two-letter abbreviation of the State/Province of the Educational institution |
| 1f. |
Please enter the zip/postalcode of the Educational institution |
| 1g. |
Please enter the Country code of the Educational institution |
|
| Section 2. Administrative Point of Contact |
| 20. |
The Administrative Point of Contact(POC) is the person responsible for the technical aspects of maintaining an organization's IP address space. This person should be able to answer any utilization questions NJEDge.Net may have. |
| 2a. |
A POC can be either a Person or a Role account. Type P for person
or R for role. The Contact Type cannot be updated. |
| 2b. |
If the POC is a role account, enter the entire role account name.
For example:
Last Name or Role Account: Network Operations Center
If the POC is a person, enter only the last name. For example:
Last Name or Role Account: Smith
|
| 2c. |
If the POC is a person, the first name is required.
If the POC is
a role account, the first name should be left blank. |
| 2d. |
Please enter the street address of the POC. (If you are updating the
street address of an existing POC, you must include all address
lines.) |
| 2e. |
Please enter the street address of the POC. (If you are updating the
street address of an existing POC, you must include all address
lines.) |
| 2f. |
Please enter the city of the POC |
| 2g. |
Please enter the two-letter abbreviation of the state or province of
the POC. |
| 2h. |
Please enter the Zip/Postal code of the POC |
| 2i. |
Please enter the Country code of the POC |
| 2j. |
Please enter the the office telephone number of the POC, including country and
area codes. Only numbers and the characters + - () are valid. Do not
include phone extensions and additional instructions in the phone
number field. |
| 2k. |
Please enter the Email address of the POC |
|
| Section 3. Technical Point of Contact |
| 30. |
The Technical Point of Contact is the person responsible for the technical aspects of maintaining an organization's IP address space. This person should be able to answer any utilization questions NJEDge.Net may have. |
| 3a. |
A POC can be either a Person or a Role account. Type P for person
or R for role. The Contact Type cannot be updated. |
| 3b. |
If the POC is a role account, enter the entire role account name.
For example:
Last Name or Role Account: Network Operations Center
If the POC is a person, enter only the last name. For example:
Last Name or Role Account: Smith
|
| 3c. |
If the POC is a person, the first name is required.
If the POC is
a role account, the first name should be left blank. |
| 3d. |
Please enter the street address of the POC. (If you are updating the
street address of an existing POC, you must include all address
lines.) |
| 3e. |
Please enter the street address of the POC. (If you are updating the
street address of an existing POC, you must include all address
lines.) |
| 3f. |
Please enter the city of the POC |
| 3g. |
Please enter the two-letter abbreviation of the state or province of
the POC. |
| 3h. |
Please enter the Zip/Postal code of the POC |
| 3i. |
Please enter the Country code of the POC |
| 3j. |
Please enter the the office telephone number of the POC, including country and area codes. Only numbers and the characters + - () are valid. Do not
include phone extensions and additional instructions in the phone
number field. |
| 3k. |
Please enter the Email address of the POC |
|
| Section 4. Previously Assigned Addresses from NJEDge.Net. |
| 4a. |
Please list all IP addresses previously assigned to your entire organization.
Please respond to items 4b through 4d with a specific description regarding the utilization of those addresses. |
4b. |
Number of hosts. |
| 4c. |
Number of subnets |
| 4d. |
Subnet mask |
|
| Section 5. Justification. |
| 5a/5b. |
Host Information. |
| 5a. |
Initially.
Please include here your estimates for the initial size of the network. |
| 5b. |
Within 1 year.
Please include here your estimates for the size the network is projected to be one year from now. A "host" is defined as any node or any device,
e.g, PC or typeer,that will be assigned an address from the host portion
of the network number. |
| 5c/5d. |
Subnet Information |
| 5c. |
Initially.
Please include the number of subnets that will be supported by the network initially. |
| 5d. |
Within 1 year
Please Include the number of subnets projected to be supported by the network one year from now. |
|
| Section 6. Number of Addresses Requested and Additional Supporting Documentation. |
| 6a. |
Number of Addresses Requested.
Please state exactly how many addresses you are requesting. |
| 6b. |
Additional justification.
Please state exactly how many addresses you are requesting along with any additional justification necessary. As stated on the template, if you are requesting 8 C's or more, you will need to complete the network topology plan in the format shown on the template. |
| Note: |
All requesters must submit the network topology plan and network diagram.
Your organization is strongly encouraged to subnet where feasible.
Address space is issued based on the utilization of VLSM per RFC 2050.
If requesting 8 C's or more, you are required to submit the network topology plan in the format of the example below: |
|
|
| Subnet# |
Subnet Mask |
Max |
Now |
1yr |
Description |
| 1 |
255.255.255.224 |
30 |
8 |
16 |
Network operations |
| 1.1 |
255.255.255.224 |
30 |
17 |
22 |
Engineering |
| 1.2 |
255.255.255.224 |
30 |
12 |
12 |
Business |
| 1.3 |
255.255.255.224 |
30 |
5 |
9 |
Chemistry |
| 1.4 |
255.255.255.224 |
30 |
10 |
15 |
Biology |
| 1.5 |
255.255.255.224 |
30 |
7 |
8 |
English |
| 1.6 |
255.255.255.224 |
30 |
0 |
0 |
Spare |
| |
Total |
210 |
59 |
82 |
|
|
|
| |
| 6c. |
Will you be dual-homed with another Internet Service Provider (Y/N) |
| 6d. |
Please enter information on the Approximate date of NJEDge connection |
For further information contact NJEDge.Net Office via E-mail at: njedge@njedge.net
Or via Voice at 973-596-5490
|
RECOMMENDED READING
Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., Postel, J. Internet Registry IP Allocation Guidelines; November 1996.
BCP 12 RFC 2050. 13 p.
http://www.faqs.org/rfcs/rfc2050.html
Rekhter, Y., Moskowitz. B., Karrenberg, D., de Groot, G. Address Allocation for Private Internets February 1996. RFC 1918. 9 p.
http://www.faqs.org/rfcs/rfc1918.html
Braden, R.T.; Postel, J.B.
Requirements for Internet Gateways. Marina del Rey, CA: University of
Southern California, Information Sciences Institute. June 1987. RFC 1009. 55 p.
http://www.faqs.org/rfcs/rfc1009.html
Internet Engineering Task Force, Braden, R.T.
Requirements for Internet Hosts -- Communication Layers. Marina del Rey,
CA: University of Southern California, Information Sciences Institute.
October 1989. RFC 1122. 116 p.
http://www.faqs.org/rfcs/rfc1122.html
Internet Engineering Task Force, Braden, R.T.
Requirements for Internet Hosts -- Application and Support.
Marina del Rey, CA: University of Southern California, Information
Sciences Institute. October 1989. RFC 1123. 98 p.
http://www.faqs.org/rfcs/rfc1123.html
Internet Activities Board. Internet Official Protocol Standards.
1994 March; RFC 1600. 34p.
http://www.faqs.org/rfcs/rfc1600.html
Postel, J.B. Internet Standard Subnetting Procedure.
Stanford, CA: Stanford University. March 1995. RFC 1780. Obsoletes
RFC1720.
http://www.faqs.org/rfcs/rfc1720.html
Postel, J.B. Internet Control Message Protocol. Marina del Rey, CA:
University of Southern California, Information Sciences Institute.
September 1981. RFC 792. 21 p.
http://www.faqs.org/rfcs/rfc792.html
Postel, J.B. Transmission Control Protocol. Marina del Rey, CA:
University of Southern California, Information Sciences Institute.
September 1981. RFC 793. 85 p.
http://www.faqs.org/rfcs/rfc793.html
Postel, J.B. User Datagram Protocol. Marina del Rey, CA: University
of Southern California, Information Sciences Institute. August 1980
RFC 768. 3 p.
http://www.faqs.org/rfcs/rfc768.html
Postel, J.B. Internet Protocol. Marina del Rey, CA: University of
Southern California, Information Sciences Institute. September 1981.
RFC 791. 45 p.
http://www.faqs.org/rfcs/rfc791.html
Reynolds, J.K.; Postel, J.B. Assigned Numbers. Marina del Rey, CA:
University of Southern California, Information Sciences Institute.
October 1994. RFC 1700. Obsoletes RFC1340.
http://www.faqs.org/rfcs/rfc1700.html
|
|
|
|
