pTLA request for LavaNet - review closes 14 Feb 01

[Bob Fink]

6bone Folk,

LavaNet has requested a pTLA allocation. The open review period for this 
will close 14 Feb 2001. Please send any comments to me or the list.


Thanks,

Bob

============================================
>Date: Tue, 30 Jan 2001 13:14:40 -1000 (HST)
>From: Antonio Querubin <tony@lava.net>
>To:  <fink@es.net>
>Subject: pTLA request for LavaNet
>
>Bob,
>
>LavaNet is applying for a pTLA.  Here are our responses to the RFC-2772
>section 7 requirements.  Could you review it and let us know what else
>needs to be addressed or whether we need to expand on any points before
>final submission?  Thanks.
>
>Antonio Querubin
>LavaNet System Staff
>
>--
> 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:
>
>LavaNet established it's first 6Bone tunnel in April 2000.  It was
>reestablished in October 2000 and it has been in continuous operation
>since.
>
>       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.
>
>The following objects are currently registered in the 6Bone Registry:
>   LAVANET
>   LAVANET-SYSTEM-STAFF
>   AQ7
>   JC273
>   3FFE:2900:D00A::/48
>
>       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 router is currently a Linux system running zebra.  It's address is
>6bone.lava.net and it peers with Sprint over a tunnel.  Our goal is to
>peer directly with our upstreams on our border cisco routers when IOS 12.2
>reaches maturity.
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>Our IPv6-enabled nameservers are:
>   ns1.ipv6.lava.net
>   ns2.ipv6.lava.net
>
>A query for PTR records in 0.0.0.0.a.0.0.d.0.0.9.2.e.f.f.3.ip6.int at the
>above nameservers will reveal a number of IPv6 hosts.
>
>       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.
>
>This will eventually be www.ipv6.lava.net.  We hope to have some pertinent
>IPv6 pages on it by next week.
>
>    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.
>
>These would be:
>   Antonio Querubin (AQ7)
>   Julian Cowley (JC273)
>   Robert Brewer (?)
>
>       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.
>
>Our system support staff mailbox is system@lava.net (LAVANET-SYSTEM-STAFF).
>
>    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.
>
>LavaNet is the largest locally-owned ISP in the state of Hawaii serving
>approximately 11000 customers throughout the major Hawaiian islands and
>Johnston Island.  We have network connections with Genuity and UUNet (next
>month we'll add Sprint) and are doing full BGP peering with them.  We also
>do regional peering with other Hawaii-based networks at the Hawaii
>Internet Exchange (HIX).
>
>    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 do.
-end