pTLA prefix requests

15 November  2000

Pseudo TLAs (pTLAs) are the IPv6 prefix for the top level of the  IPv6 Testing Address Allocation of the Aggregatable Global Unicast Address hierarchy, and thus define 6bone backbone networks.

The rules for requesting pTLAs are found in RFC 2772, "6Bone Backbone Routing Guidelines" under Section 7. It should be noted that the rules refer to applying to the 6bone Operation Group, documented in Section 8. These two sections are reproduced below for convenience.

The easiest procedure for applying is to simply address each of the points in section 7 below, using the actual text below as a form. Then send this to Bob Fink (fink@es.net) who will let you know if the form and substance of the request is adequate. When the request is ready, Bob will forward the actual request to the 6bone mail list with a two-week review date. In cases where Bob Fink is not available for an extended period (more than a few days), he will let the 6bone list know who is a substitute pre-reviewer. If you are in doubt of whom to request a pTLA from, due to lack of response from Bob or other uncertainty, send email to the IETF ngtrans working group co-chairs (Alain Durand, Bob Fink and Tony Hain). This is approrpiate as the 6bone is considered a part of ngtrans activities.

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:

      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.

      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.

      c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
         entries for the Applicant's router(s) and at least one host
         system.

      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.

   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.

      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.

   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.

   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.

   When an Applicant seeks to receive a pTLA allocation, it will apply
   to the 6Bone Operations Group (see section 8 below) by providing to
   the Group information in support of its claims that it meets the
   criteria above.

8. 6Bone Operations Group

   The 6Bone Operations Group is the group in charge of monitoring and
   policing adherence to the current rules. Membership in the 6Bone
   Operations Group is mandatory for, and restricted to, sites connected
   to the 6Bone.

   The 6Bone Operations Group is currently defined by those members of
   the existing 6Bone mailing list who represent sites participating in
   the 6Bone. Therefore it is incumbent on relevant site contacts to
   join the 6Bone mailing list. Instructions on how to join the list are
   maintained on the 6Bone web site at < http://www.6bone.net>.

[Questions and comments] [Return to 6bone Home Page]