[6bone] pTLA request by RETINA - review closes 30 June 2003

[Bob Fink]

6bone Folk,

RETINA has requested a pTLA allocation and I find their request fully 
compliant with RFC2772. The open review period for this will close 30 June 
2003 (longer than usual... see below). Please send your comments to me or 
the list.

   <www.ipv6.retina.ar>


I am doing a longer time period on this pTLA request as I will be leaving 
on a 2 week vacation on the 12th of June and won't be in email contact 
until 1 July. Also, I won't process any more pTLA requests (there aren't 
many :-) until after I return from vacation (this one was in just before my 
deadline).


Thanks,

Bob

===
Date: Mon, 19 May 2003 19:34:47 -0300
From: Daniel Bellomo <dbellomo@retina.ar>
Subject: RETINA: pTLA prefix requests
To: Bob Fink <bob@thefinks.com>

Dear Bob,

I am a member of the RETINA ipv6 project, RETINA would like to apply a 6bone
pTLA.

Thank you.
Daniel Bellomo

RFC 2772:

7. Guidelines for 6Bone pTLA sites

    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 have been connected to the 6BONE since April 2002
<=================================================================>

       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.

<=================================================================>
$ whois -h whois.6bone.net RETINA
...
ipv6-site:    RETINA
origin:       AS3597
descr:        Red TeleInformatica Academica
country:      AR
prefix:       3FFE:8070:1019::/48
application:  ping 6bone.ipv6.retina.ar
<=================================================================>

       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.

<=================================================================>
tunnel:       IPv6 in IPv4 6bone.retina.ar -> unam-ipv6-1.ipv6.unam.mx UNAM
BGP4+
tunnel:       IPv6 in IPv4 6bone.retina.ar -> 146.83.248.2 UACH BGP4+
tunnel:       IPv6 in IPv4 6bone.retina.ar -> 6bone-gw.rediris.es REDIRIS
BGP4+
tunnel:       IPv6 in IPv4 6bone.retina.ar -> ipv6.rau.edu.uy RAU STATIC
tunnel:       IPv6 in IPv4 6bone.retina.ar -> gwipv6.mty.itesm.mx ITESM BGP4+
<=================================================================>

       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
          entries for the Applicant's router(s) and at least one host
          system.

<=================================================================>
Our DNS server:
ns1.ipv6.retina.ar.	3ffe:8070:1019:200::10
<=================================================================>

       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.

<=================================================================>
Our WEB server:

www.ipv6.retina.ar.	3ffe:8070:1019:200::5
<=================================================================>

    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.


<=================================================================>
4 persons:
Guillermo Cicileo 	gcicileo@retina.ar
Mariela Rocha		mrocha@retina.ar
Santiago Aggio		slaggio@criba.edu.ar
Daniel Bellomo		dbellomo@retina.ar
<=================================================================>

       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@retina.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.

<=================================================================>
RETINA  (REd TeleINformatica Academica) is a project launched
by Asociacion Civil Ciencia Hoy, (a non profit NGO) in 1990 in
order to assure data communication for the  Academic and Research
area in Argentina, among themselves and with the international
community.
The web page is www.retina.ar
<=================================================================>

    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 to all current and future operational rules and policies.
<=================================================================>

    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>.


Thank you!
Daniel Bellomo

----- End forwarded message -----