pTLA qualifications
Joseph E Eggleston
Joe.Eggleston" <Joe_Eggleston-CJE136@email.mot.com
Wed, 31 Jan 2001 16:08:05 -0600
Hi all,
I am trying to set up our site to meet all the requirements for
requesting a pTLA. I think I have everything configured, but I was
wondering if someone could try hitting our site to see if everything
looks good externally as well.
My IPv6 domain is ipv6.motlabs.com. The router that is handling the
tunnel is i2router.ipv6.motlabs.com. There's a web server at
www.ipv6.motlabs.com and DNS is at dns1.ipv6.motlabs.com. Our 6bone
database entries are under MOTOROLA-LABS.
thanks!
Joe
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.
see MOTOROLA-LABS
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.
We're using BGP4+ and our router is at i2router.ipv6.motlabs.com
c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
entries for the Applicant's router(s) and at least one host
system.
I think DNS forward and reverse is working.
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.
www.ipv6.motlabs.com
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.
We have an OC-3c link to the Chicago NAP.
support staff: JEE1-6BONE, JTE1-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@labs.mot.com
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.
User community is mainly Motorola.
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>.