10/01  NJEDge.Net IP Request Template
 
********************** PLEASE DO NOT REMOVE Version Number ********************
                                              Network Version Number: 2.0
*************************** Please see attached detailed instructions ********************
 
1a.  Institution Name ............………………………………….:
1b.  Approximate date of NJEDge connection.....................:
 
Technical Point of Contact
 
2a.  Name (Last, First).............:
2b.  Title..........................:
2c.  Postal address.................:
2d.  Phone Number...................:
2e.  E-Mailbox......................:
 
3.   Previously assigned addresses..:
 
     Explain how addresses have been utilized, to include:
 
               3a.  Number of hosts................:
               3b.  Number of subnets..............:
               3c.  Subnet mask....................:
 
Justification 
 
Host Information
4a.  Initially.......................:
4b.  Within 1 year...................:
 
Subnet Information
4c.  Initially.......................:
4d.  Within one year.................:
 
Number of Addresses Requested and Additional Supporting Documentation.
 
5a.  Number of addresses requested...:
5b.  Additional supporting justification...................:
 
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.0
 
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
 
 
 
 
a network diagram should also be included with your request.
 
6. Will you be dual-homed with another Internet Service Provider (Y/N).:
 
=========================================================================
INSTRUCTIONS FOR REQUESTING INTERNET PROTOCOL (IP) NUMBERS FROM NJEDge.Net
 
Completion of the Network Version Number: 2.0 template above is required to obtain 
NJEDge.Net Internet protocol (IP) Network Numbers.
 
Each line in the blank template must be copied EXACTLY AS IT APPEARS. 
Take care not to alter the established field names or spacing when you fill in the information. 
Any change to the template may cause an error that inhibits the processing of your template
and delays the input of your request.
 
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: http://www.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.  Identifying Information
 
1a.  Please supply the name of the requesting Educational institutional member.
1b.  Approximate date of NJEDge connection.
       Please supply information on the approximate date of your connection to the NJEDge.Net.
 
Section 2.  Technical Point of Contact (POC).
 
The technical 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.   Name. 
               Place the last name and the first name of the POC on the same line, 
               separated by a comma as shown:  Last name, First name
     
               EXAMPLES:
                Smith, Mary
                Netman, John 
 
               2b.  Title.
               List the POC's title, if known. 
 
               2c.  Postal Address.
Provide the physical address of the POC at the organization requesting IP address Space. 
 
When completing question 2d, place the city, state, and zip code on separate lines.  
Use a comma to separate the city and state.  Do not insert a period following the state abbreviation. 
       
               EXAMPLES:
               111 Main Street
               Town Center, VA 22070
                         
               2d.  Phone Number.
               You must the list the complete telephone number of the POC, including area
               code and/or international telephone codes.  
 
               2e.  E-mailbox.
You must provide the E-mail address of the POC at the organization requesting IP address space.
 
Section 3.  Previously Assigned Addresses.
 
Please list all IP addresses previously assigned to your entire organization.
Please repond to items 3a through 3c with a specific description regarding the utilization of those addresses.
 
               3a.  Number of hosts.
               3b.  Number of subnets.
               3c.  Subnet mask.
 
Section 4.   Justification.
               4a./4b.  Host Information.  
               4a.  Initially.  
               Please include here your estimates for the initial size of the network.
               
               4b.  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 printer,that will be assigned an address from the host portion
               of the network number.  
               4c./4d.  Subnet Information.  
 
               4c.  Initially. Include the number of subnets that will be supported by the network initially.
 
4d.  Within 1 year. Include the number of subnets projected to be supported by the network one year from now. 
 
Section 5.  Number of Addresses Requested and Additional Supporting Documentation.
 
               5a.  Number of Addresses Requested.
                    Please state exactly how many addresses you are requesting.
 
               5b.  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.0           255.255.255.128       128   102    116    Network Operations
               1.1           255.255.255.192       64    44      48      Engineering
               1.2           255.255.255.240       16    12      13      Business
               1.3           255.255.255.240       16    11      14      Chemistry
               1.4           255.255.255.240       16    10      15      Biology
               1.5           255.255.255.240       16     0       0       Spare
               -------------------------------------------------------------------------------------------------------
               Totals                                    256   179   206
               -------------------------------------------------------------------------------------------------------
 
NOTE:   This represents one /24 (Class C) using Variable Length Subnet Masking (VLSM).
 
Section 6.   Dual-homed.
               Please indicate if you are planning to be dual-homed with NJEDge.Net (yes/no)
 
For further information contact NJEDge.Net Offices 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.arin.net/rfc/rfc2050.txt
 
Rekhter, Y., Moskowitz. B., Karrenberg, D., de Groot, G.
Address Allocation for Private Internets, IBM Corp., Chrysler Corp.,
RIPE NCC.  February 1996. RFC 1918. 9 p.
http://www.arin.net/rfc/rfc1918.txt
 
 
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.arin.net/rfc/rfc1009.txt
 
  
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.arin.net/rfc/rfc1122.txt
 
 
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.arin.net/rfc/rfc1123.txt 
 
Internet Activities Board. Internet Official Protocol Standards.
1994 March; RFC 1600. 34p. 
http://www.arin.net/rfc/rfc1600.txt      
 
 
Postel, J.B.  Internet Standard Subnetting Procedure. 
Stanford, CA: Stanford University. March 1995. RFC 1780. Obsoletes
RFC1720.
http://www.arin.net/rfc/rfc1720.txt 
 
 
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.arin.net/rfc/rfc792.txt 
 
 
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.arin.net/rfc/rfc793.txt 
 
 
 
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.arin.net/rfc/rfc768.txt 
 
 
 
Postel, J.B.  Internet Protocol. Marina del Rey, CA: University of 
Southern California, Information Sciences Institute.  September 1981. 
RFC 791. 45 p. 
http://www.arin.net/rfc/rfc791.txt 
 
 
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.arin.net/rfc/rfc1700.txt