IPv6 End User Form

Form Guide

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.

IPv6 End User Form

Org Id

SDL-163

Prefix Length Requested

/44

Network Name

SINN-DEVELOPMENT-LTD

Origin AS

TBD

Public Comments

Proposed IPv6 Address Utilization Numbering Topology

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.