pTLA request for TIAI - closes 19Mar01

[Bob Fink]

6bone Folk,

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


Thanks,

Bob

======================================

>Date: Mon, 5 Mar 2001 15:17:29 -0500 (EST)
>From: Jason <jslagle@toledolink.com>
>To: fink@es.net
>Subject: TIAI pTLA Application
>
>
>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.
>
>We have been on the 6bone since November 1999.  Since that time we have
>kept our site records, along with our netblock records up to date.  Out
>maintainer block never accepted, but this has since been remedied.
>
>          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 currently have a tunnel to Merit and are acting as a transit pLNA.  We
>have downstream tunnels for over 10 sites currently and are always willing
>to bring up more tunnels on request.  We have been running BGP4+ with
>Merit since early 2000, first with a private ASN, and more recently with
>our assigned ASN.  The gateway router on site is ipv6.toledolink.com which
>should be ipv6 and ipv4 pingable.
>
>          c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>             entries for the Applicant's router(s) and at least one host
>             system.
>
>Our forward and reverse zones have been set up and functioning properly
>since early 2000.  Mainstream ipv6 services are being rolled out and all
>new machines have both ipv4 and 6 connectivity.  DNS is being updated as
>this happens.
>
>          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.
>
>The machine raistlin.ipv6.toledolink.com has had ipv6 aware apache running
>on it for some time.  I have updated our ipv6 services page and added it
>to our site entry.  I have also pointed www.ipv6.toledolink.com to it.
>
>In addition, we have several ipv6 aware maileservers on site, with at
>least one (mail.ipv6.tacorp.net) receiving mail via the 6bone.
>
>       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 2 people on site with person entries and famaliar with it.  We
>have several more who are learning it and will create person objects as
>they are brought up to speed.
>
>          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.
>
>We have the common ipv6@toledolink.com mailbox to address this.  Once the
>process of converting the toledolink.com mailserver to an ipv6 aware OS is
>complete (It is in process), this will also accept ipv6 mail.
>
>       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 believe that the internet as a whole is a potential community.  We have
>been providing tunnel services to anyone who asks, and I am involved in
>several projects in which we will be adding ipv6 support.  I believe that
>the need is there for someone to provide tunnels to sites doing
>development of ipv6 services, and it is a niche I wish to fill.
>
>       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.
>
>I have no reason to believe I am breaking any policies.  Let me know if I
>am.
>
>
>       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.
>
>Thanks,
>
>Jason
>
>---
>Jason Slagle - CCNA - CCDA
>Network Administrator - Toledo Internet Access - Toledo Ohio
>- raistlin@tacorp.net - jslagle@toledolink.com - WHOIS JS10172
>/"\ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>\ /   ASCII Ribbon Campaign  .
>  X  - NO HTML/RTF in e-mail  .
>/ \ - NO Word docs in e-mail .