pTLA request for DOLPHINS-CH - review closes 30 April 2002

[Bob Fink]

6bone Folk,

DOLPHINS-CH has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this will close 1 May 
2002. Please send your comments to me or the list.

<http://whois.6bone.net/cgi-bin/whois?DOLPHINS-CH>

<www.ipv6.as8758.net>


Thanks,

Bob

===
>Date: Wed, 17 Apr 2002 18:16:18 +0200
>From: Matthias Cramer <cramer@dolphins.ch>
>To: fink@es.net
>Cc: ipv6@as8758.net
>Subject: pTLA Request for DOLPHINS-CH
>
>Hi Bob
>
>DOLPHINS-CH likes to get a pTLA allocation for the 6Bone. Following the 
>RFC 2772
>Sections in question, with our statments.
>
>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:
>
>We are on the 6Bone since 9.July 2001
>
>       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.
>
>They reflect allways the current state.
>
>       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.
>
>BGP4+ is stable and working well to SOLNET-CH, and is pingable with the name
>rt.ipv6.freestone.net (3FFE:8150:2001:0:0:0:0:1).
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>All IPv6 our Hosts have forward and reverse entries.
>
>       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 servers name is www.ipv6.as8758.net, and it is pingable, it has
>A and AAAA entries.
>
>    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 two qualified support persons, they are registerd in the ipv6-site 
>entry.
>
>       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 are reachable under ipv6@as8758.net.
>
>    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 allready interested parties. Our whole backbone will be native
>IPv6 in about 4 Weeks.
>
>For Your information on our services. We offer Virtual Webhousing, Server 
>Hosting,
>Leased Lines, DialUP and all other classic ISP services. And we like to offer
>all these Services on IPv6. For that our Cusomers and espessialy we, like 
>to get
>expirience with that matter on the 6Bone.
>
>    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 fully agree to that.
>
>    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.
>
>We fully agree to that.
>
>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>.
>
>We fully agree to that.
>
>
>Best regards
>
>    Matthias Cramer
>
>--
>      _;\_    Matthias Cramer                System & Network Manager
>     /_.  \   Dolphins Network Systems AG    Phone +41-1-847'45'45
>    |/ -\ .)  Libernstrasse 24               Fax   +41-1-847'45'49
>  -'^`-   \;  CH-8112 Otelfingen             http://www.dolphins.ch/
>GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E  3959 B62F DF1C 2D20 8250
>
>