[6bone] pTLA request by TOWARDEX - review closes 15 December 2003

[Bob Fink]

6bone Folk,

TOWARDEX has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this closes 15 December 
2003. Please send your comments to me or the list.

   <http://www.occaid.org>


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: Sun, 30 Nov 2003 19:57:27 -0500
>From: Haesu <haesu@towardex.com>
>To: bob@thefinks.com
>Cc: rad@towardex.com, tim@towardex.com, clifford@cnacs.occaid.org
>Subject: pTLA request by TOWARDEX
>
>Hello Bob,
>
>I would like to request a pTLA for TOWARDEX. Please see the relevant
>information below:
>
>Thank you,
>-hc
>Haesu C.
>TowardEX Technologies, Inc.
>
>P.S.: I've tried to send you this to fink@es.net according to the 6bone
>web site, but it bounced, so I am sending this to you at thefinks.com.
>Thanks
>
>---
>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:
>
>TOWARDEX established 6bone connectivity since June of 2003.
>
>         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:    TOWARDEX
>origin:       AS30071
>descr:        OCCAIDTowardEX IPv6 Backbone Network
>               Network Center - Weehawken, NJ
>country:      US
>prefix:       2001:470:112::/48
>prefix:       3FFE:4010:A00E::/48
>application:  http www.twdx.net
>application:  http www.occaid.org
>application:  ping www.occaid.org
>application:  ping 6to4relay.ngtran.twdx.net
>tunnel:       IPv6 in IPv4 oct.towardex.com -> 6bone.enterzone.net 
>ENTERZONE BGP4+
>tunnel:       IPv6 in IPv4 oct.towardex.com -> nyc.ipv6.he.net HURRICANE BGP4+
>tunnel:       IPv6 in IPv4 isc.towardex.com -> fmt.ipv6.he.net HURRICANE BGP4+
>tunnel:       IPv6 in IPv4 oct.towardex.com -> 66.252.21.200 CIT BGP4+
>tunnel:       IPv6 in IPv4 isc.towardex.com -> 6bone.lava.net LAVANET BGP4+
>tunnel:       IPv6 in IPv4 sfo.towardex.com -> core1.dllstx1.syn2.net 
>VLINK BGP4+
>tunnel:       IPv6 in IPv4 isc.towardex.com -> 69.22.171.192 EMIC BGP4+
>contact:      RAD-6BONE
>contact:      HDJ1-6BONE
>contact:      TWDX-6BONE
>contact:      ATD7-6BONE
>remarks:      The OCCAID/TowardEX IPv6 network has been operational since 
>June of 2003.
>remarks:      ip6.int and ip6.arpa zones for 3ffe:4010:a00e::/48 and 
>2001:470:112::/48 has been operational since October of 2003.
>remarks:      OCCAID/TowardEX runs a national IPv6 network, with access 
>POPs in Boston, New York, San Francisco, Houston, and more.
>remarks:      Tunnel and peering requests are welcome - send to 
>ip-admin@twdx.net
>mnt-by:       MAINT-TOWARDEX
>changed:      rad@towardex.com 20031016
>changed:      rad@towardex.com 20031017
>changed:      haesu@towardex.com 20031130
>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 upstream connectivity with ENTERZONE, HURRICANE and LAVANET at two
>different routers and locations of our network.
>
>Our routers (isc.towardex.com, oct.towardex.com, sfo.towardex.com) 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 isc.towardex.com
>isc.towardex.com has address 2001:470:1f00:758::205
>$ host -t aaaa oct.towardex.com
>oct.towardex.com has address 2001:470:112:0:feed::1
>$ host -t aaaa sfo.towardex.com
>sfo.towardex.com has address 2001:470:1f00:758::105
>$ host -t aaaa twdx.net
>twdx.net has address 2001:470:112:c0ff:ee:0:e1ee:7
>$ host 2001:470:112:c0ff:ee:0:e1ee:7
>7.0.0.0.e.e.1.e.0.0.0.0.e.e.0.0.f.f.0.c.2.1.1.0.0.7.4.0.1.0.0.2.IP6.ARPA 
>domain name pointer 2001-470-112-c0ff-ee--e1ee-7.towardex.com
>
>primary DNS server ns1.twdx.net
>secondary DNS server ns2.twdx.net
>
>         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.twdx.net) as well as our IPv6 project site www 
>(www.occaid.org)
>
># ping6 -c 1 www.twdx.net
>PING6(56=40+8+8 bytes) 2001:470:112:c0ff:ee:0:e1ee:7 --> 
>2001:470:112:c0ff:ee:0:e1ee:7
>16 bytes from 2001:470:112:c0ff:ee:0:e1ee:7, icmp_seq=0 hlim=64 time=0.098 ms
>
>--- twdx.net ping6 statistics ---
>1 packets transmitted, 1 packets received, 0% packet loss
>round-trip min/avg/max/std-dev = 0.098/0.098/0.098/0.000 ms
># ping6 -c 1 www.occaid.org
>PING6(56=40+8+8 bytes) 2001:470:1f00:758:c0ff:ee:0:1 --> 
>2001:470:1f00:758:c0ff:ee:0:1
>16 bytes from 2001:470:1f00:758:c0ff:ee:0:1, icmp_seq=0 hlim=64 time=0.110 ms
>
>--- www.occaid.org ping6 statistics ---
>1 packets transmitted, 1 packets received, 0% packet loss
>round-trip min/avg/max/std-dev = 0.110/0.110/0.110/0.000 ms
>
>
>      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:      RAD-6BONE
>contact:      HDJ1-6BONE
>contact:      ATD7-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:       IPv6 Technical Operations Team
>address:      Network Operations Center
>address:      TowardEX Technologies, Inc.
>address:      1740 Massachusetts Avenue
>address:      Boxborough, MA 01719
>address:      US
>phone:        +1-978-263-3399 170
>e-mail:       ip-admin@twdx.net
>nic-hdl:      TWDX-6BONE
>mnt-by:       MAINT-TOWARDEX
>changed:      rad@towardex.com 20031129
>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 backbone IPv6 network using prefix 
>3ffe:4010:a00e::/48 as
>well as 2001:470:112::/48. We run a national North American training and 
>lab network
>called OCCAID (www.occaid.org) with total of 227 members as of now 
>connected to POP routers
>through both tunnel and native connectivity. Our network was started using 
>IPv4 initially,
>and since June we have a complete IPv6 infrastructure deployed and 
>operational.
>
>Our goals are to test and deploy various IPv6 implementations through use 
>of different
>vendor implementations and also to develop software products surrounding 
>the use of IPv6
>technology.
>
>      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 with all concurrent and 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've joined the 6Bone mailing list.