[6bone] pTLA request UACH - review closes 7 August 2002
Pekka Savola
pekkas@netcore.fi
Fri, 26 Jul 2002 08:22:40 +0300 (EEST)
Should uach.cl not inf.uach.cl be the "official" applier?
The AS number of the applicant has been hijacked:
Search results for: 45333
Internet Assigned Numbers Authority
(ASN-IANA-RSVD-ASNBLOCK)
Information Sciences Institute
University of Southern California
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6695
US
Autonomous System Name: IANA-RSVD
Autonomous System Block: 32768 - 64511
Coordinator:
Internet Corporation for Assigned Names and Numbers (IANA-ARIN) res-ip@iana.org
(310) 823-9358
Record last updated on 14-Oct-1999.
Database last updated on 25-Jul-2002 20:00:35 EDT.
On Wed, 24 Jul 2002, Bob Fink wrote:
> 6bone Folk,
>
> UACH has requested a pTLA allocation and I find their request fully
> compliant with RFC2772. The open review period for this will close 7 August
> 2002. Please send your comments to me or the list.
>
> <http://whois.6bone.net/cgi-bin/whois?UACH>
>
> <http://ipv6.inf.uach.cl/>
>
>
> Also note that UACH has permission to use REUNA's ASN (AS11340) for 6bone
> pTLA purposes.
>
>
> Thanks,
>
> Bob
>
> ===
> >From: "Christian Lazo R." <clazo@inf.uach.cl>
> >To: <fink@es.net>
> >Subject: request for pTLA
> >Date: Mon, 24 Jun 2002 12:12:29 -0700
> >
> >Hello,
> >
> >As a SPTLA, I'm very much interested to be a PTLA.
> >
> >Therefore I'm sending my application in the order that you require:
> >
> > 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:
> >
> > I have esperience from june 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: UACH
> >origin: AS45333
> >descr: Universidad Austral de Chile
> > Instituto de Informatica
> >country: CL
> >prefix: 3FFE:8070:100C::/48
> >application: ping routerv6.ipv6.cl
> >tunnel: IPv6 in IPv4 routerv6.inf.uach.cl ->
> >ipv6-gw.compendium.com.ar COMPENDIUM-AR BGP4+
> >tunnel: IPv6 in IPv4 routerv6.inf.uach.cl ->
> >unam-ipv6-1.ipv6.unam.mx UNAM BGP4+
> >tunnel: IPv6 in IPv4 routerv6.inf.uach.cl -> gwipv6.ipv6.itesm.mx
> >ITESM BGP4+
> >tunnel: IPv6 in IPv4 routerv6.inf.uach.cl -> gw6.nic.mx NIC-MX BGP4+
> >contact: CLR1-6BONE
> >url: http://ipv6.inf.uach.cl/
> >notify: clazo@inf.uach.cl
> >mnt-by: MNT-UACH
> >changed: clazo@inf.uach.cl 20010626
> >changed: clazo@inf.uach.cl 20010629
> >changed: clazo@inf.uach.cl 20020618
> >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.
> >
> >
> >
> >
> >
> > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> > entries for the Applicant's router(s) and at least one host
> > system.
> >
> >[clazo@antillanca clazo]$ dig www.ipv6.cl
> >
> >; <<>> DiG 8.2 <<>> www.ipv6.cl
> >;; res options: init recurs defnam dnsrch
> >;; got answer:
> >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
> >;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
> >;; QUERY SECTION:
> >;; www.ipv6.cl, type = A, class = IN
> >
> >;; ANSWER SECTION:
> >www.ipv6.cl. 14h41m4s IN A 146.83.248.3
> >
> >;; AUTHORITY SECTION:
> >ipv6.cl. 14h41m4s IN NS ns.ipv6.cl.
> >ipv6.cl. 14h41m4s IN NS secundario.nic.cl.
> >
> >;; ADDITIONAL SECTION:
> >ns.ipv6.cl. 10h51m50s IN A 146.83.248.2
> >ns.ipv6.cl. 14h23m6s IN AAAA 3ffe:8070:100c:2c01::a
> >secundario.nic.cl. 11h7m54s IN A 216.72.164.136
> >secundario.nic.cl. 11h7m54s IN A 200.27.126.131
> >
> >;; Total query time: 6 msec
> >;; FROM: antillanca.inf.uach.cl to SERVER: default -- 146.83.216.201
> >;; WHEN: Mon Jun 17 21:25:35 2002
> >;; MSG SIZE sent: 29 rcvd: 174
> >
> >
> > 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.
> >
> >www.ipv6.cl
> >
> >
> >
> > 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.
> >
> >
> >
> >
> >
> > 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.
> >
> >ipv6@inf.uach.cl
> >
> >
> > 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.
> >
> >The potential group that we are available to give this service is the
> >following:
> >
> >All the chilean universities counting with Internet and interested in
> >working with ipv6.
> >
> >There are also some other big Chileans firms such as Internet Service
> >Provider
> >
> >Nowadays, we are working with other Latin American universities in order
> >to grow up the interest to use IPv6
> >
> >As you can see, our purpose is to become the IPv6 in Chile.
> >
> > 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.
> >
> > 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>.
> >
> >
> >greeting
> >
> >(sorry , but my Inglish is very bad)
> >
> >Christian
> >________________
> >Christian Lazo R.
> >Instituto de Informatica
> >fono 56-63-221812
> >Fac Cs de la Ingenieria
> >Universidad Austral de Chile
>
>
> _______________________________________________
> 6bone mailing list
> 6bone@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/6bone
>
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords