pTLA request for GLOBAL - review closes 11 February 2002

[Bob Fink]

6bone Folk,

GLOBAL has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this will close 11 
February 2002 (an extended time as I will be on travel 24 Jan - 10 Feb). 
Please send your comments to me or the list.

Note that this new pTLA will replace the existing pTLA IPF 
(3FFE:3400::/24), that is stopping operation. Their technical principal 
Jan-Ahrent Czmok has moved to Global Access where he is setting up new IPv6 
services and thus wants a new pTLA based on his experience at IPF. I have 
asked that they reapply for a pTLA, and that the existing /24 will be 
de-allocated.

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

<http://www.ipv6.gatel.net>


Thanks,

Bob

===
>Date: Sat, 19 Jan 2002 18:13:35 +0100
>From: Jan-Ahrent Czmok <czmok@gatel.net>
>To: Bob Fink <fink@es.net>
>Cc: kocovski@gatel.net, Alain.Durand@sun.com, tonyhain@microsoft.com
>Subject: Re: Request for 6bone pTLA
>Organization: Global Access Telecommunications Inc.
>
>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.
>
>Answer--> All objects are fully maintained, please see:
>           inet6num:     3FFE:3400:1000::/48
>           ipv6-site:    GLOBAL
>
>Current tunnels-->
>
>IPV6 in IPv4 ipv6-gw.de.gatel.net -> cisco.ipv6.ipf.net IPF BGP4+
>IPv6 in IPv4 ipv6-gw.de.gatel.net -> swiPV6.switch.ch SWITCH BGP4+
>IPv6 in IPv4 ipv6-gw.de.gatel.net -> 6bone.uni-muenster.de JOIN BGP4+
>IPv6 in IPv4 ipv6-gw.de.gatel.net -> home.czmok.de CZMOK-NET STATIC
>
>         -> our Nameserver(s) are dns1.us.gatel.net and dns1.de.gatel.net
>
>    Also i would like to add that i used to work for IPF before; 
> its    followup Gigabell AG is also a founding member of the ipv6-forum.
>    We also used to have a long history in the 6bone.
>
>    I changed jobs at January 2002, so i would like to transfer my knowledge
>    and experience to Global Access.
>
>    I will implement further project work and involvement in the ipv6-wg 
> at ripe in our Company.
>
>    The IPF ipv6-site will cease soon.
>
>  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.
>
>Answer--> We will upgrade our router to the latest cisco ios image
>           to have up-to-date features. We will also expand our ipv6
>           network as soon as the current ios ipv6 implementation is
>           proven to be stable to the ocmplete backbone and will natively
>           do ipv6 peerings at decix + inxs.
>
>  c. Fully maintained DNS forward (AAAA) and reverse
>(ip6.int) entries for the Applicant's router(s) and at least one host
>  system.
>
>We will also upgrade one of our nameservers to the latest bind 
>implementation supporting AAAA and A6 records.
>
>ipv6-gw.de.gatel.net and www.ipv6.gatel.net should be ipv6 pingable.
>
>  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 server www.ipv6.gatel.net is descibing the services on ipv6.
>Also it will hold the tunnel broker implementation (from cselt)
>
>  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.
>
>Answer-> We are intending and able to provide ipv6 6bone backbone service.
>
>We are a european-based ISP offering dialup and leased line services
>    besides hosting. We are working in cooperation with other parties
>    to sponsor and broaden IPv6 around europe. My involvement in the IPv6
>    working Group (ripe) and IPV6-FORUM is widely known.
>
>
>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.
>
>Please see: JC9-6BONE, JK8-6BONE and UK1-6BONE and ipv6-site object GLOBAL
>
>
>  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.
>
>in object GLOBAL :
>
>remarks:      Will configure tunnels to interested parties! Please contact 
>support@gatel.net
>notify:       czmok@gatel.net
>
>common email-adress is czmok@gatel.net or support@gatel.net for queries
>
>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.
>
>Global Access is a business provider and has a substantial user community
>which are interested in ipv6 services.
>
>please see a inverse query to the ipv4 tree of GAT-MNT.
>
>
>  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 commit to abide the rules and future rules.
>
>  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>.
>
>Answer ->> We are subscribed to the list.
>
>
>If anymore questions arise, please feel free to contact me.
>
>Jan
>
>
>--
>      Jan Ahrent Czmok - Senior Network Engineer - Access Networks
>Global Access Telecommunications, Inc. - Stephanstr. 3 - 60313 Frankfurt
>voice: +49 69 299896-35 - fax: +49 69 299896-66 - email: czmok@gatel.de