IPv6 /44: xxxx:xxxx:xxx::
IPv6 /48: xxxx:xxxx:xxxx::
IPv6 /64: xxxx:xxxx:xxxx:xxxx::
This is the multi-page printable view of this section. Click here to print.
IPv6 /44: xxxx:xxxx:xxx::
IPv6 /48: xxxx:xxxx:xxxx::
IPv6 /64: xxxx:xxxx:xxxx:xxxx::
Briefly describe the products and services your organization offers, or plans to offer.
We provide
List all IP addresses in use in your network, including those registered to you in ARIN’s Whois or in a public RWhois server.
Describe how you plan to use the requested IP addresses. List each logical subnet you plan to create. For each, include a brief description of purpose and number of hosts projected at 30 days and at one year.
If you meet any of the criteria below, you qualify to receive IPv6 address space:
- Have an IPv4 assignment from ARIN or one of its predecessors
- Intend to immediately be IPv6 multi-homed
- Have 13 end sites (offices, data centers, etc.) within one year
- Use 2,000 IPv6 addresses within one year
- Use 200 /64 subnets within one year
IPv6 block size is based on the number of end sites in your network, not on the number of IP addresses you anticipate using. End sites are physical locations such as offices and data centers.
Each end site will generally be assigned one /48 subnet. You can determine the block size you qualify for based on the total number of end sites in your network (refer to the following table). This should include all existing end sites as well as any new end sites that will be deployed within one year.
| Number of End Sites | Block Size |
|---|---|
| 1 site | /48 |
| 2-12 sites | /44 |
| 13-192 sites | /40 |
| 193-3,072 sites | /36 |
| 3,073+ sites | /32 |
SDL-163
/44
SINN-DEVELOPMENT-LTD
TBD
Please provide a subnet mapping of your proposed IPv6 addressing topology. If this is a request for an initial allocation for your organization, please also list your sites within the ARIN service region.
We have two physical sites currently within ARIN’s region. One in Oakville, ON, Canada (Albion), and one in Harmony, ON, Canada, (Harmony) but three logical sites.
Our Harmony site for networking purposes contains two sites. One for general use, and another that is deemed high security - and has zero physical connections to the general site. This is to comply with the guidelines for the Canada Controlled Goods Program. For ARIN’s purposes, this qualifies as three sites.
For the general purpose networks at each of these locations, they’re identical in design. Please see the attached diagram for the network topology. We heavily use VLANs and subnets to segregate traffic and ensure security.
Unfortunately, as part of the Controlled Goods Program, we cannot provide a detailed network diagram for the high-security site. All we can disclose is that there are much more stringent security measures in place, and as a result - we need to segregate each networking area/project into its own uniquely addressed subnet that is tied to that project for the lifetime of the project. This causes a very large number of VLANs to be created, and stay provisioned for the life of the project, which can range for 3-10 years, or more.
We currently have a need for 180 /64 subnets, across all three sites, and we anticipate needing another 200 /64 subnets within the next 12 months. We plan to be using IPv6 as our native IP stack, and only using IPv4 for legacy compatibility.
Site1: xxxx:xxxx:xxx1::/48 Site2: xxxx:xxxx:xxx2::/48 Site3: xxxx:xxxx:xxx3::/48
For further layout/architecture - please see the attached PNGs for the overall layout.
node "Edge Router" as EdgeRouter {
}
node "Site 1 - Harmony" as Site1 {
cloud "Standard Network Design" as Site1Layout
}
node "Site 2 - Albion" as Site2 {
cloud "Standard Network Design" as Site2Layout
}
node "Site 3 - Harmony - High Security" as Site3 {
cloud "Internal Network is Confidential"
}
EdgeRouter -- Site1
EdgeRouter -- Site2
EdgeRouter -- Site3
cloud "Standard Network Design" {
node "Site Network" as SiteNetwork {
component "IP Addressing" as SiteNetworkIP {
card "Private IPv4: /16" as SiteNetwork_IPv4
card "IPv6: /48" as SiteNetwork_IPv6
}
}
node "VLAN 10 - Management" as VLAN10 {
component "IP Addressing" as VLAN10IP {
card "IPv4: /23" as VLAN10_IPv4
card "IPv6: /64" as VLAN10_IPv6
}
}
node "VLAN 20 - Servers" as VLAN20 {
component "IP Addressing" as VLAN20IP {
card "IPv4: /23" as VLAN20_IPv4
card "IPv6: /64" as VLAN20_IPv6
}
}
node "VLAN 30 - Users" as VLAN30 {
component "IP Addressing" as VLAN30IP {
card "IPv4: /23" as VLAN30_IPv4
card "IPv6: /64" as VLAN30_IPv6
}
}
node "VLAN 35 - Users Wireless" as VLAN35 {
component "IP Addressing" as VLAN35IP {
card "IPv4: /23" as VLAN35_IPv4
card "IPv6: /64" as VLAN35_IPv6
}
}
node "VLAN 40 - SCADA" as VLAN40 {
component "IP Addressing" as VLAN40IP {
card "IPv4: /23" as VLAN40_IPv4
card "IPv6: /64" as VLAN40_IPv6
}
}
node "VLAN 50 - CCTV" as VLAN50 {
component "IP Addressing" as VLAN50IP {
card "IPv4: /23" as VLAN50_IPv4
card "IPv6: /64" as VLAN50_IPv6
}
}
node "VLAN 60 - Guest" as VLAN60 {
component "IP Addressing" as VLAN60IP {
card "IPv4: /23" as VLAN60_IPv4
card "IPv6: /64" as VLAN60_IPv6
}
}
node "VLAN 70 - Voice" as VLAN70 {
component "IP Addressing" as VLAN70IP {
card "IPv4: /23" as VLAN70_IPv4
card "IPv6: /64" as VLAN70_IPv6
}
}
node "VLAN 90 - IoT" as VLAN90 {
component "IP Addressing" as VLAN90IP {
card "IPv4: /23" as VLAN90_IPv4
card "IPv6: /64" as VLAN90_IPv6
}
}
node "VLAN 100 - DMZ" as VLAN100 {
component "IP Addressing" as VLAN100IP {
card "IPv4: /23" as VLAN100_IPv4
card "IPv6: /64" as VLAN100_IPv6
}
}
node "VLAN 110 - VPN" as VLAN110 {
component "IP Addressing" as VLAN110IP {
card "IPv4: /23" as VLAN110_IPv4
card "IPv6: /64" as VLAN110_IPv6
}
}
SiteNetwork -- VLAN10
SiteNetwork -- VLAN20
SiteNetwork -- VLAN30
SiteNetwork -- VLAN35
SiteNetwork -- VLAN40
SiteNetwork -- VLAN50
SiteNetwork -- VLAN60
SiteNetwork -- VLAN70
SiteNetwork --> VLAN90
SiteNetwork -- VLAN100
SiteNetwork -- VLAN110
}