[6bone] pTLA request by T-Net - review closes 23 November 2003

Bob Fink bob@thefinks.com
Sun, 09 Nov 2003 22:17:48 -0800


6bone Folk,

T-NET has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this will close closes 
23 November 2003. Please send your comments to me or the list.

   <http://www.t-net.hu/>


This may be the last 6bone pTLA allocation made as the phaseout plan 
specifies no new pTLA allocations after the end of this year. Thus if 
anyone is expecting to request a pTLA, the request must be sent to me no 
later than 5 December to allow enough review and approval time prior to 31 
December.


Thanks,

Bob

===
>Date: Thu, 6 Nov 2003 10:39:39 +0100 (CET)
>From: Karolyi Reka <mithos@t-net.hu>
>To: bob@thefinks.com
>cc: vagok@t-net.hu, smithis@t-net.hu
>
>Hi Bob,
>
>I'd like to request a pTLA for T-NET, please find relevant info below.
>
>Sincerely,
>
>Reka Karolyi
>
>-------------------------------------------------------------------------
>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:
>
>T-NET is in 6bone since March of 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.
>
>
>ipv6-site:    T-NET
>origin:       AS29657
>descr:        T-NET IPv6 Network
>               Budapest, Hungary
>country:      HU
>prefix:       3FFE:2C03::/32
>application:  ping 6bone-gw-1.t-net.hu
>application:  ping 6bone-gw-2.t-net.hu
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 6bone.uni-muenster.de 
>JOIN BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> cern-atm7.cern.ch CERN BGP4+
>tunnel:       IPv6 in IPv6 6bone-gw-1.t-net.hu -> 6bone-gw1.edisontel.it 
>EDISONTEL BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> rap.viagenie.qc.ca 
>VIAGENIE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> 6bone-gw3.cselt.it CSELT 
>BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> rtr1.ipv6.he.net 
>HURRICANE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 6bone-gw.pantel.t-net.hu 
>T-NET BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> puffi.pszfb.hu PSZFB-NET 
>STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 
>nl-ams-re-02.ipv6.chello.net CHELLO BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> nofear.wbteam.com RIEB 
>STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 6bone-gw-1.6b0ne.hu 
>6B0NE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 6bone-gw-2.6b0ne.hu 
>6B0NE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> bitchx.wigner.bme.hu 
>TEMA BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> nexcom.asterix.hu NEXCOM 
>RIPng
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> hubud-08-00.pop.xs26.net 
>XS26 BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> ircnet.hu GTNET BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> homnyp.hu KV1-6BONE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> arrakis.dune.hu DUNE STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 
>lon2a.core.rtr.caladan.net.uk CALADAN BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> router-2.ipv6.kewlio.net 
>KEWLIO BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 
>linux.obgyn.szote.u-szeged.hu GTNET2 STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 6gw.bnet.hu BNET BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 
>sl-bb1v6-bru.sprintlink.net SPRINT BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> 6bone-gw-1.6b0ne.hu 
>6B0NE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> 6bone-gw-2.6b0ne.hu 
>6B0NE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> ircnet.hu GTNET BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> bitchx.wigner.bme.hu 
>TEMA BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> homnyp KV1-6BONE BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> goodman.hu GOODMAN BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> 
>no-osl-re-01-fe-0-0.ipv6.aorta.net CHELLO BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> 
>catv-c3b8b0df.szolcatv.broadband.hu PR STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> gyurc.movinet.hu GHNET 
>STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> gateway.pmmf.hu PMMF RIPng
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> perverz.hu VUDUNET BGP4+
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> janos.szivarvanynet.hu 
>QTGAME STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> 
>pa8.sulechow.sdi.tpnet.pl CRASHER STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-1.t-net.hu -> tom.tdc.hu AS STATIC
>tunnel:       IPv6 in IPv4 6bone-gw-2.t-net.hu -> 6gw.bnet.hu BNET BGP4+
>contact:      TNET1-6BONE
>contact:      VAGO1-6BONE
>contact:      SS9-6BONE
>contact:      RK5-6BONE
>remarks:      FreeBSD router running Zebra routing daemon
>remarks:      ipv6-site is operational
>mnt-by:       MNT-TNET
>changed:      vagok@t-net.hu 20021021
>changed:      hostmaster@t-net.hu 20030122
>changed:      hostmaster@t-net.hu 20030404
>changed:      hostmaster@t-net.hu 20031104
>source:       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 have BGP connection with UK6X JOIN TILAB HURRICANE KEWLIO EDISONTEL 
>VIAGENIE ...
>
>Our routers (6bone-gw-1.t-net.hu and 6bone-gw-2.t-net.hu) are IPv6 pingable.
>
>        c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>           entries for the Applicant's router(s) and at least one host
>           system.
>
>
>host -t aaaa 6bone-gw-1.t-net.hu
>  6bone-gw-1.t-net.hu IPv6 address 3ffe:2c03:10:0:280:c8ff:fe58:2b0c
>
>host -t aaaa 6bone-gw-2.t-net.hu
>  6bone-gw-2.t-net.hu IPv6 address 3ffe:2c03:20:0:a00:36ff:fe64:6903
>
>primary DNS server ns1.t-net.hu (zeus.mad.hu)
>secondary DNS server ns2.t-net.hu (kiralyco.enternet.hu)
>
>        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.
>
>We have IPv6 www (www.t-net.hu) ftp, telnet, and pop3 services.
>
>     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.
>
>         contact:   RK5-6BONE
>          contact:   VAGO1-6BONE
>         contact:   SS9-6BONE
>
>        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.
>
>
>person:       T-NET IPv6 Project Operative Team
>address:      Kunigunda u. 35.
>address:      H-1037 Budapest
>address:      Hungary
>phone:        +36 20 5569359
>phone:        +36 20 3140665
>phone:        +36 30 2035789
>fax-no:       +36 20 5574899
>e-mail:       ipv6-noc@t-net.hu
>nic-hdl:      TNET1-6BONE
>mnt-by:       MNT-TNET
>changed:      hostmaster@t-net.hu 20031104
>source:       6BONE
>
>
>     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 working development IPv6 infrastructure using prefix 3ffe:2c03::/32.
>This is including Marton Aron Dormitory (Budapest, Hungary), College of 
>Finance
>and Accountancy (Budapest, Hungary), Zipernowsky Karoly Technical Secondary
>School (Pecs, Hungary), PMMFK-PTE (Pecs University, Hungary), SysNet Ltd
>  (ISP, Budapest, Hungary),  Hamex Co. (Tele Communication Corporation, 
> Budapest , Hungary).
>
>Our goals testing various IPv6 implementations using various network 
>equipments.
>
>
>     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 agree with any current and any future 6Bone operational rules and
>policies.
>
>      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 have joined the mailinglist.
>
>-------------------------------------------------------------------------------