[6bone] pTLA request ENTERZONE - review closes 7 August 2002

[Bob Fink]

6bone Folk,

ENTERZONE has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this will close 7 August 
2002. Please send your comments to me or the list.

<http://whois.6bone.net/cgi-bin/whois?ENTERZONE>

<http://ipv6.enterzone.net/>

Also note that ENTERZONE already has an ARIN issued sTLA prefix allocated 
(2001:04F0::/35) for their customers willing to pay for IPv6 service. They 
want to provide free experimental 6bone services to anyone who wants to
experiment as well as providing production IPv6 services.


Thanks,

Bob

===
>Date: Wed, 17 Jul 2002 20:51:29 -0400 (EDT)
>From: John.Fraizer@ENTERZONE.NET
>To: fink@es.net
>Subject: pTLA prefix request - updated
>
>
>    The following rules apply to qualify for a 6Bone pTLA allocation. It
>    should be recognized that holders of 6Bone pTLA allocations are
>    expected to provide production quality backbone network services for
>    the 6Bone.
>
>    1. The pTLA Applicant must have a minimum of three (3) months
>       qualifying experience as a 6Bone end-site or pNLA transit.   During
>       the entire qualifying period the Applicant must be operationally
>       providing the following:
>
>       a. Fully maintained, up to date, 6Bone Registry entries for their
>          ipv6-site inet6num, mntner, and person objects, including each
>          tunnel that the Applicant has.
>
>  EnterZone has been a pNLA since March 1999 and has since March 30,
>1999 maintained our ipv6-site, inet6num, mntner and person objects,
>including each tunnel that we have active.
>
>
>       b. Fully maintained, and reliable, BGP4+ peering and connectivity
>          between the Applicant's boundary router and the appropriate
>          connection point into the 6Bone. This router must be IPv6
>          pingable. This criteria is judged by members of the 6Bone
>          Operations Group at the time of the Applicant's pTLA request.
>
>  EnterZone has during this time period experienced one outage with
>respect to 6bone connectivity that was caused by catastrophic failure of
>our (single at the time) 6bone router.  Our IPv6 network now consists of
>redundant border (border1.enterzone.net and border2.enterzone.net) and
>core (core1.enterzone.net and core2.enterzone.net) routers to prevent
>this single point of failure situation from occuring again.  Note: Core1
>is currently being upgraded and is not at this time ipv6 accessable.
>
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>  EnterZone has maintained DNS forward and reverse records for
>nitrous.ipv6.enterzone.net (v4 or v6 looking-glass) and ipv6.enterzone.net
>(v6 only accessable website) in our nameservers since some time in
>1999.  In addition, all tunnel endpoint addresses have appropriate
>ip6.int entries.
>
>       d. A fully maintained, and reliable, IPv6-accessible system
>          providing, at a mimimum, one or more web pages, describing the
>          Applicant's IPv6 services.  This server must be IPv6 pingable.
>
>  http://ipv6.enterzone.net/ while not pretty, includes up-to-date
>information about EnterZones IPv6 site and services.
>
>  http://nitrous.ipv6.enterzone.net/ is our IPv6 looking-glass running the
>MRLG code that I wrote.
>
>    2. The pTLA Applicant MUST have the ability and intent to provide
>       "production-quality" 6Bone backbone service. Applicants must
>       provide a statement and information in support of this claim.
>       This MUST include the following:
>
>       a. A support staff of two persons minimum, three preferable, with
>          person attributes registered for each in the ipv6-site object
>          for the pTLA applicant.
>
>  EnterZone maintains a 24x7 network operations center and has multiple
>contacts associated with our ipv6-site object with appropriate person
>objects registered in the 6bone registry.
>
>       b. A common mailbox for support contact purposes that all support
>          staff have acess to, pointed to with a notify attribute in the
>          ipv6-site object for the pTLA Applicant.
>
>  EnterZone maintains the ipv6@enterzone.net mail alias that goes to all
>network operations staff which is indicated in the notify attribute of our
>ipv6-site object.
>
>    3. The pTLA Applicant MUST have a potential "user community" that
>       would be served by its becoming a pTLA, e.g., the Applicant is a
>       major provider of Internet service in a region, country, or focus
>       of interest. Applicant must provide a statement and information in
>       support this claim.
>
>  EnterZone is a regional NSP providing in High-Security Datacenter
>services, dedicated connectivity services and colocation services.  We
>count 4 dialup providers among our customers and are working with these
>providers in hopes to facilitate native IPv6 access services for their
>dialup customers in the future.  In addition, EnterZone owns and operates
>the CMH-IX NAP [http://www.cmh-ix.net] and plans on implementing IPv6
>route servers at the exchange and encouraging native IPv6 peering
>among its participants.
>
>    4. The pTLA Applicant MUST commit to abide by the current 6Bone
>       operational rules and policies as they exist at time of its
>       application, and agree to abide by future 6Bone backbone
>       operational rules and policies as they evolve by consensus of the
>       6Bone backbone and user community.
>
>  EnterZone has strived to abide by the 6bone operational rules since
>the time of our connection to the 6bone in March of 1999.  In recent
>weeks, as a matter of necessity, we have been forced to announce our
>specific 3ffe:1ced::/32 and request that our BGP peers accept and
>redistribute this de-aggregated prefix to maintain connectivity for our
>downstream IPv6 clients.  This was necessary because the pTLA from which
>we have our pNLA allocation has been unresponsive in modifying a tunnel
>configuration.  This modification was necessary because of events beyond
>our control.  Had our pTLA been responsive, we would never have announced
>the more specific prefix however.  Since March of 1999, this is the ONLY
>instance in which we have not abided by the 6bone operational
>rules.  Please understand that we only announced our specific pNLA to
>maintain connectivity because our pTLA was, and remains unresponsive.  I
>tried multiple emails, telephone calls, and ultimately a broadcast email
>to the 6bone list to no avail.
>
>
>Thank you for your consideration.
>
>
>
>---
>John Fraizer              | High-Security Datacenter Services |
>EnterZone, Inc            | Dedicated circuits 64k - 155M OC3 |
>http://www.enterzone.net/ | Virtual, Dedicated, Colocation    |