[6bone] pTLA request by CTN1 - review closes 16 December 2003

[Bob Fink]

6bone Folk,

CTN1 has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this closes 16 December 
2003. Please send your comments to me or the list.

   <http://www.ctn1.com>

This may be the last 6bone pTLA allocation made as the phaseout plan 
specifies no new pTLA allocations after the end of this year. Thus if 
anyone is expecting to request a pTLA, the request must be sent to me no 
later than 5 December to allow enough review and approval time prior to 31 
December.


Thanks,

Bob

===
>From: "Marc GOMEZ" <mg@ctn1.com>
>To: <bob@thefinks.com>
>Cc: <6bone@ctn1.net>
>Subject: 6bone request form
>Date: Mon, 1 Dec 2003 23:06:31 +0100
>
>Dear Bob,
>
>I'd like to request a pTLA for CTN1, please find relevant info below.
>
> >From RFC 2772
>
>
>7. Guidelines for 6Bone pTLA sites
>
>
>    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:
>
>Our IPv6 site is operational since 09 August 2003.
>
>        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.
>
>http://whois.6bone.net/cgi-bin/whois?CTN1
>
>
>       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.
>
>Our ASN is 29402.
>We have an IPv6 native Gigabit connexion to FNIX6.
>NDSoftware (AS25358) provide us IPv6 transit through FNIX6.
>
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>           entries for the Applicant's router(s) and at least one host
>           system.
>
>We have 3 nameservers:
>  - ns1.ctn1.net
>  - ns2.ctn1.net
>
>       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://www.ctn1.com (all services are ready to use with IPv6)
>
>    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.
>
>RP10-6BONE
>MG22-6BONE
>BV3-6BONE
>
>       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.
>
>6bone@ctn1.net
>
>    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.
>
>CTN1 operates an IPv6 Network and provides a lot of IPv6 services to many
>projects.
>We provide: Usenet Provider, Email provider and Hosting Provider with dual
>IPv4 and IPv6.
>All IPv6 services is free of charge.
>We encourage all people to start a web site and Email server with IPv6.
>
>    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.
>
>
>We agree to all current and future rules and policies.
>
>----