[OCCAID] PLEASE READ: IPv6 Renumbering Plan

[James]

2001:4830::/32 has been allocated to AS30071 for OCCAID Project. Please follow
the renumbering schedule below.

To request your new /48 allocation, please read and follow the procedures
below.

Step 1: Find out the OCCAID POP your tunnel or native ethernet is connected to
        for upstream internet6 connection.

  Each OCCAID POP utilizes International Airport Location Code to identify
  itself. To find out which POP you are homed to, simply run traceroute6 to
  any IPv6 sites out there, for example www.6bone.net

  The first router hop that you see with "occaid.net" postfix represents the
  OCCAID POP you are homed to. OCCAID uses the following router naming
  convention:

  xxx.gr-x-x-x.cr1.loc1.us.occaid.net

  The "loc1" is the airport code that identifies the POP. The "us" is the
  country code. The information you need to identify your OCCAID POP is
  the "loc1" part. Remember this information.

Step 2: Match your OCCAID POP airport code with the Regional Routing Grid ID.

  Find your OCCAID POP's airport code you've found in Step 1 from one of the
  regional routing ID's below. Once you've found the Regional Routing ID that
  covers your OCCAID POP airport code, remember that information.

  Regional Routing Grid ID               Covered POP airport codes
  --------------------------------------------------------------------------
  ZOA (OAKLAND CENTER)                   SFO2, SFO1, SJC1, PAO1
  ZBW (BOSTON CENTER)                    BOS1, BOS2, BOS3
  ZNY (NEW YORK CENTER)                  EWR2, PHL1, JFK2, JFK3, JFK4, JFK5,
                                         RIC1(ROC)
  ZMA (MIAMI CENTER)                     TPA1
  ZFW (FORTWORTH CENTER)                 DFW1
  ZAU (CHICAGO CENTER)                   ORD1
  ZDC (WASHINGTON CENTER)                IAD1, IAD2, DCA1, RDU1
  ZTL (ATLANTA CENTER)                   ATL1
  ZJX (JACKSONVILLE CENTER)              PFN1, JAX1
  ZKC (KANSAS CITY CENTER)               MCI1
  ZLX (LOS ANGELES CENTER)               LAX1, LAX2
  ESE (EUROPE SWEDEN)                    STO1


Step 3: Locate the production TLA deployment date for your POP Routing Grid.

 The dates below specify the time when OCCAID Joint Tech. Coordination
 operators will be rolling out the new production IPv6 TLA prefix for each
 specific regional Routing Grid. Due to the fairly large size of our network,
 the rollout schedule for the new IPv6 prefix is divided in region by region
 using the grid ID's.

  Once you've found the rollout date that matches your OCCAID POP's routing
  grid, please WAIT until that date. On or after that date, send an email
  to <renumber at cnacs.occaid.org> with the following information:

   o The current 3ffe 6BONE address your tunnel is using (the /64 subnet).
   o List of your current /48 NLA allocation(s).
   o List the DNS servers that will be providing reverse mapping for your
     new production TLA prefix. ONLY ENTER HOSTNAMES, DO NOT USE NUMERIC
     IP ADDRESS HERE.

  Please note that the deadline for submitting request to above email
  address is August 30, 2005. You must send email by 8/30/05 to receive
  your new production NLA so that you can replace the 3ffe 6BONE block.

  Scheduled sTLA Roll-out Date               Routing Grid
  --------------------------------------------------------
  January 8 2005                             ZBW
  January 9 2005                             ZNY
  January 14 2005                            ZOA
  January 15 2005                            ZDC, ZLX
  January 16 2005                            ZFW, ZJX
  January 21 2005                            ZTL
  January 22 2005                            ZAU
  January 23 2005                            ESE
  January 28 2005                            ZMA, ZKC


Step 4: Receive your new production (2001 space) NLA and renumber :)

  After submitting your renumbering request on or after the rollout date for
  your POP, within FIVE BUSINESS DAYS, you will be given your new production
  NLA prefix. The /64 handoff address of your tunnel must be renumbered
  immediately. However your old 6BONE 3ffe /48 NLA assignment does NOT have
  to be returned immediately.

  Until November 1 2005, both of your production 2001 NLA and 6BONE 3ffe NLA
  can coexist in their use. So, if you submit your renumbering request right
  after the roll-out date for your POP, you should have PLENTY OF TIME this
  year to renumber out of your 3ffe block.

  You have until November 1, 2005  to completely renumber all services and
  downstream users and network components off of 6BONE 3ffe space and into
  your new production 2001 prefix. 

  After November 1 2005, OCCAID will remove 3ffe static routes and addresses
  that are still resident in router configurations. OCCAID will also go through
  all peering list and ensure that nobody is utilizing 3ffe:401d::/32 space.

  Preferably by mid November or December of this year, OCCAID will cease
  routing of 3ffe:401d::/32 6BONE prefix. All BGP announcements of
  3ffe:401d::/32 should be shutdown by that point, as new production 2001
  space should be taking over the daily operations.

  We plan to make announcement to 6BONE mailing list no later than January
  of 2006, to officially return the 3ffe:401d::/32 back to the 6BONE pool.

  FYI, 6BONE phaseout planning calls for return of all 3ffe blocks by
  June 6 2006. On 6/6/6, OCCAID will begin filtering 3ffe based 6bone prefixes
  on its BGP routing table, as recommended by the phaseout planning.

-- 
James Jun                                            TowardEX Technologies, Inc.
Technical Lead                      Boston IPv4/IPv6 Web Hosting, Colocation and
james at towardex.com            Network design/consulting & configuration services
cell: 1(978)-394-2867           web: http://www.towardex.com , noc: www.twdx.net