ZAMA 6bone pTLA request

[Bob Fink]

ZAMA networks has requested a 6bone pTLA. Please send comments to me or the 
list by 17 November (I am out of town the previous week so wouldn't process 
it before then anyway).


Thanks,

Bob

>From: "Kerry Hu" <khu@zama.net>
>To: <fink@es.net>
>Subject: application for pTLA
>Date: Fri, 27 Oct 2000 12:13:12 +1000
>
>Hi Bob,
>Here is the application for a pTLA of Zama Networks. Please review!
>Thanks,
>
>Kerry.
>
>
>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: Zama have joined 6bone since Aug 5th, 2000
>
>       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.
>
>A: records are fully maintained and updated.
>ipv6-site:    ZAMA
>origin:       AS9940
>descr:        Zama Networks
>               Seattle
>prefix:       3FFE:C00:801B::/48
>tunnel:       IPv6 in IPv4 ipv6.zama.net -> ipv6-router.cisco.com CISCO
>BGP4+
>contact:      KH2-6BONE
>notify:       ipv6@zama6.net
>changed:      khu@zama.net 20000805
>source:       6BONE
>
>
>       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.
>
>A: Zama is connected to 6bone via Cisco running BGP4+.
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>A: We have two name servers running Bind 9 with full forward and reverse
>records.
>    Name servers are: corvette.zama6.net and catera.zama6.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.
>
>A: www.zama6.net is the web server and can be accessed by both v4 and v6.
>
>    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: Zama is committed to build an IPv6 backbone network with statement
>mentioned in www.zama.net web pages.
>
>       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.
>
>A: Kerry Hu: kh2-6bone, Brian Skeen: BS2-6BONE, Grant Furness: GF2-6BONE
>Brad Mcnamara: BWM1-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.
>
>A: an email box ipv6@zama6.net up and running.
>
>    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.
>
>A: www.zama.net pages state that we are committed to provide IPv6 backbone
>services.
>
>    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.
>
>A: we agree the rules and policies.
>
>    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.