pTLA request for CALADAN - review closes 30 April 2002
Bob Fink
fink@es.net
Tue, 16 Apr 2002 08:11:26 -0700
6bone Folk,
CALADAN has requested a pTLA allocation and I find their request fully
compliant with RFC2772. The open review period for this will close 30 April
2002. Please send your comments to me or the list.
<http://whois.6bone.net/cgi-bin/whois?CALADAN>
<http://www.ipv6.kewlio.net/>
Thanks,
Bob
===
>Date: Fri, 12 Apr 2002 19:44:06 +0100 (BST)
>From: "Daniel Austin (fxp0)" <fxp0@fxp0.co.uk>
>To: Bob Fink <fink@es.net>
>cc: <ipv6@kewlio.net>
>Subject: Re: 6bone pTLA request
>
>Hi Bob,
>
>Please find attached the new application as requested.
>
>*** 6BONE pTLA REQUEST ***
>
> 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:
>
> >>> We have had our allocation from CALADAN for the past 3 months.
>
> 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 current IPv6 allocation is from CALADAN (3ffe:8270:8::/48) which
> is all upt-o-date in whois.
> >>> Our customer tunnels are also listed.
>
> 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 5 BGP4+ sessions configured via tunnels to
> different providers.
> >>> Our router is router.ipv6.kewlio.net [3ffe:8270:8::1] and should be
> active 24/7.
> >>> We currently handle all ASN details for Global Media Applications
> Limited.
> >>> A seperate e-mail from the Technical Director has been sent to
> fink@es.net allowing
> >>> us full use of AS24765 for 6bone purposes.
> >>> Global Media Applications Limited will be using IPv6 development
> services from our
> >>> allocation(s).
>
> c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> entries for the Applicant's router(s) and at least one host
> system.
>
> >>> Our nameservers currently provide forward and reverse DNS for:
> >>> 8.0.0.0.0.7.2.8.e.f.f.3.ip6.int
> >>> kewlio.net
> >>> These should be able to be queried from anywhere.
>
> 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.
>
> >>> Our (simple) IPv6 services page is http://www.ipv6.kewlio.net/
> >>> This is both IPv4 and IPv6 reachable. This server is
> ping/traceroute-able from the 6bone 24/7.
> >>> You can also reach our 4th nameserver (ns4.kewlio.net) 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:
>
> >>> Although we are a relatively new company, we have every intention to
> provide IPv6 services alongside our existing
> >>> IPv4 services. We have been running as a sole-trader for the past
> year, and business has increased significantly
> >>> during the past few months. There is a lot of interest in the IPv6
> support of our servers and services.
>
> 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.
>
> >>> DJA97-6BONE and TEI122-6BONE - both present in "KEWLIO" ipv6-site in
> whois.
>
> 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@kewlio.net is our support/contact mailbox. our ipv6-site object
> points to this address.
> >>> We also have ipv6-tunnels@kewlio.net for tunnel requests
>
> 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 offer server colocation / rental, also virtual hosting and virtual
> servers. All services are able to use IPv6 if
> >>> the customer requests. We actively inform potential customers of our
> 6bone allocation and their ability to use it.
> >>> We generally supply services to businesses in the Manchester area,
> although we currently have customers from England,
> >>> Germany and the United States. We are open to all customers in all
> regions.
> >>> Our new shell service has had a lot of feedback about IPv6 support,
> and we have our existing CALADAN allocation in
> >>> action on our shell servers.
> >>> All customers are reminded that any 6bone IP's are for development
> purposes and that, at
> >>> some point, we will be joining production-level IPv6 within 6-12
> months time.
> >>> Customers are offerred IPv6 functionality at no extra cost.
>
> 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 have read these and are happy to abide by all policies.
>
>
>
>
>
>Thanks,
>
>Daniel Austin,
>Managing Director,
>kewlio.net Limited.