pTLA request for COMPENDIUM-AR - review closes 18 July 2001

[Bob Fink]

6bone Folk,

COMPENDIUM-AR has requested a pTLA allocation. The open review period for 
this request will close 18 July 2001. Please send your comments to me or 
the list. As has been noted by various comments to this list, your comments 
on these pTLA requests do matter, so please don't hesitate to voice your 
support or concerns.

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

<http://www.compendium.net.ar>


Thanks,

Bob

===
>Date: Wed, 4 Jul 2001 20:19:20 -0300
>From: horape@tinuviel.compendium.net.ar
>To: Bob Fink <fink@es.net>
>Subject: pTLA request
>
>¡Hola!
>
>This is a pTLA request for COMPENDIUM-AR. We're a R&D lab and do consulting
>on networking in Hispan America (including Spain)
>
>-----
>  From RFC 2772:
>
>    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're active as a pNLA in the 6bone since early 1999.
>
>          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:    COMPENDIUM-AR
>inet6num:     3FFE:29A1::/32
>
>          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.
>
>ipv6-gw.compendium.net.ar (3ffe:29a1::201:2ff:febf:1dc1) is
>our main IPv6 gateway.
>
>          c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>             entries for the Applicant's router(s) and at least one host
>             system.
>
>ipv6-gw.compendium.net.ar. 86400 IN     AAAA    3ffe:29a1::201:2ff:febf:1dc1
>
>Main router.
>
>tinuviel.compendium.net.ar. 86400 IN    AAAA    3ffe:29a1::200:21ff:fe47:2d95
>
>DNS and IRC server.
>
>palermo.compendium.net.ar. 86400 IN     AAAA    3ffe:29a1::2e0:7dff:fe83:a68
>
>IPv6 only host (lent by Universidad de Palermo for own joint network research
>projects)
>
>Reverse is set up at our DNS server (tinuviel.compendium.net.ar), but Sprint
>haven't delegated it yet, so it's non functional.
>
>          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.
>
>http://ipv6-gw.compendium.net.ar/
>
>       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:
>
>We have the ability and intent to provide production-quality 6Bone backbone
>service.
>
>          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.
>
>person:       Horacio Jose Penya
>nic-hdl:      HJP1-6BONE
>
>(BTW, it's Peña, not Penya, but the registry don't allow my real name in)
>
>person:       Florencia Ithurralde
>nic-hdl:      FI-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.
>
>notify:       ipv6@compendium.net.ar
>
>       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've two different potential user communities.
>
>We work very closely with PuntoAr, a local ISP. They provide dialup and
>wireless access. We're planning to start providing their wireless customers
>IPv6 connectivity in the next months.
>
>And, we're organizing Uninet's "IPv6 en Hispanoamérica" project, where we're
>promoting IPv6 in the region. We're providing connections to 8 islands in
>the region, with 14 more in preparation.
>
>We've introduced IPv6 in Colombia (by CORUNIVERSITEC university) and are
>working on creating new islands in countries where there isn't any 6bone
>project yet, as Republica Dominicana, Nicaragua, Cuba and Venezuela.
>
>       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 by current and future 6bone operational rules.
>
>-----
>
>Saludos,
>                                         HoraPe
>---
>Horacio J. Peña
>horape@compendium.com.ar
>horape@uninet.edu
>bofh@puntoar.net.ar
>horape@hcdn.gov.ar
-end