pTLA request for NC-REN - review closes 23 November 2001

[Bob Fink]

6bone Folk,

NC-REN has requested a pTLA allocation. The open review period for this 
will close 23 November 2001. Please send your comments to me or the list.


Thanks,

Bob

===
>Date: Wed, 7 Nov 2001 23:51:41 -0500 (EST)
>From: Alan Halachmi <alan@halachmi.net>
>To: <fink@es.net>
>cc: <rdc@netcom.duke.edu>
>Subject: pTLA Request for NC-REN
>
>Bob,
>
>         I'm forwarding you our pTLA request.  We've had a v6 webserver up
>for a while now, but never loaded content.  I'm having the folks at Duke
>take up that piece, and I imagine that'll be done by weeks end.  Otherwise,
>I believe everything's in order.
>
>Best!!
>Alan
>------------------------------------------------------------------------
>
>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:
>
>       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.
>
>         ipv6-site: NC-REN
>
>       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.
>
>         3ffe:1cdd::1
>
>       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 no control over ip6.int, as MERIT is not longer funding
>         IPv6; we do, however, have router setup w/ AAAA records.
>          ipv6-gw-3600.ncni.net is the core router.
>          ipv6.duke.edu is the host.
>
>       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.
>
>         ipv6.duke.edu
>
>    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.
>
>         ipv6-site: NC-REN
>         contact:   AH2-6BONE
>         contact:   RDC-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.
>
>         helpdesk@ncren.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.
>
>       NCREN Internet Services serves as the Internet access provider for 16
>       campus universities, 40 private and community colleges, and a number
>       of other educational and research institutions throughout North
>       Carolina.  http://www.ncren.net/Internet/ for more information.
>
>    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.
>
>       This commitment is hereby made.
...