pTLA request for AOL (wwwv6.aolv6.aol.com) - review closes 8 November 2001

[Bob Fink]

6bone Folk,

AOL (wwwv6.aolv6.aol.com) has requested a pTLA allocation. The open review 
period for this will close 8 November 2001. Please send your comments to me 
or the list.


Thanks,

Bob

===
>From: "Cleve Mickles" <micklesc@aol.net>
>To: <fink@es.net>
>Subject: pTLA Request for AOL
>Date: Tue, 23 Oct 2001 13:06:14 -0400
>
>Hi Bob,
>
>We would like to apply for a pTLA allocation
>from the 6Bone.  Please let me know if there are
>any further requirements.
>
>Thanks,
>
>Cleve...
>
> > 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.
>
>Our 6bone registry entries include:
>
>ipv6-site: AOL
>
>We are sub-TLA of VBNS and Sprint with inet6num: entries
>for both address blocks
>
>mntner: MNT-AOL-V6
>person objects: CM1-6BONE & TS6-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.
>
>We are connected to about 8 BGP peers using tunneled connections.
>The external peers are spread over two Cisco 7500 routers and all
>tunnels are recorded in the ipv6-site registry object.
>
> >
> >      c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> >         entries for the Applicant's router(s) and at least one host
> >         system.
> >
>
>We maintain forward (AAAA) records for aolv6.aol.com
>and the reverse zone 3.0.8.2.e.f.f.3.ip6.int in the
>ns.aolv6.aol.com name server for network 3ffe:2803/32.
>
>AAAA DNS records for one of our router interfaces and our
>DNS server are noted below. The domain is aolv6.aol.com
>
>ptn-6bone1-nose-fe200           IN      AAAA    3FFE:2803:FFFE::1
>ns  IN      AAAA    3FFE:2803:FFFE::3
>
>
> >      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.
>
>wwwv6.aolv6.aol.com provides some basic information along
>with a link to our 6bone pinger page.
>
> >
> >   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.
>
>Thom Stehnach tsten@aol.com
>Cleve Mickles micklesc@aol.net
>Please see person objects: CM1-6BONE & TS6-6BONE for other
>details.
>
> >
> >      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.
>
>ipv6-support@listserv.sup.aol.com is used for support issues.
>The notify attribute in our registry objects points to our
>routepolicy@aol.net mail list which incorporates the people
>on ipv6-support list.
>
> >
> >   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.
>
>We have a backbone network, a large user community and a large array
>of content.  We would plan to offer some services via IPv6.
>
> >
> >   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 will abide by the current 6bone operation rules and policies
>and the consensus rules going forward.
>
> >
> >   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>.
> >
> >
> >
> >
>
>
>Cleve Mickles
>Office Phone: 703-265-5618
>Network Architect
>America Online, Network Operations
-end