[6bone] pTLA request by NECTEC-TH - review closes 10 March 2003
Bob Fink
bob@thefinks.com
Mon, 24 Feb 2003 09:27:45 -0800
6bone Folk,
NECTEC-TH has requested a pTLA allocation and I find their request fully
compliant with RFC2772. The open review period for this will close 22
January 2003. Please send your comments to me or the list.
<<http://www.ipv6.nectec.or.th>http://www.ipv6.nectec.or.<http://www.ipv6.nectec.or.th>th>
Thanks,
Bob
===
>From: "NECTEC-IPv6" <ipv6@nectec.or.th>
>To: <bob@thefinks.com>
>Subject: pTLA request
>Date: Fri, 21 Feb 2003 09:33:40 +0700
>
>Dear Mr. Bob Fink,
>
>This letter is being written on behalf of
> Thailand's IPv6 Testbed Project ,
> Thai Social/Sciencetific Academic and Research Network ,
> National Electronics and Computer Technology Center of Thailand
>
>to request pTLA allocation. Being qualified with RFC2772, please
>find details below :
>
>===============================================
>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:
>
>=> Our testbed's connected to 6bone and launched since 9 August 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.
>
>=>
><http://whois.6bone.net/cgi-bin/whois?NECTEC-TH>http://whois.6bone.net/cgi-bin/whois?NECTEC-TH
>
> 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.
>
>=> BGP4+ peering with regional and domestic 6bone's backbone
>sites : INET-TH, CERNET-CN, NBEN-TW, MIMOS-MY
>
> >sh bgp ipv6 sum
>Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>State/PfxRcd
>3FFE:3200:1:1A::1
> 4 4538 12902 27646 19481 0 0 1d08h 16
>3FFE:3600:2000:888::3640:7
> 4 9681 29337 26177 19481 0 0 1d07h 236
>3FFE:400B:400B::8
> 4 4618 21510 23789 19481 0 0 1w0d 415
>3FFE:80D0:FFFC:10::42
> 4 2042 39314 17080 19481 0 0 1d19h 287
>
>=> Router, ep.ipv6.nectec.or.th, IPv6 pingable.
>PING6(56=40+8+8 bytes) 3ffe:8140:101:7::1 --> 3ffe:400b:400b::9
>16 bytes from 3ffe:400b:400b::9, icmp_seq=0 hlim=58 time=783.453 ms
>16 bytes from 3ffe:400b:400b::9, icmp_seq=1 hlim=58 time=817.015 ms
>16 bytes from 3ffe:400b:400b::9, icmp_seq=2 hlim=58 time=1435.44 ms
>16 bytes from 3ffe:400b:400b::9, icmp_seq=3 hlim=58 time=838.53 ms
>16 bytes from 3ffe:400b:400b::9, icmp_seq=4 hlim=58 time=1074.85 ms
>
>--- ep.ipv6.nectec.or.th ping6 statistics ---
>5 packets transmitted, 5 packets received, 0% packet loss
>round-trip min/avg/max/std-dev = 783.453/989.858/1435.441/245.416 ms
>
> c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
> entries for the Applicant's router(s) and at least one host
> system.
>
>=> The current DNS server is leo.ipv6.nectec.or.th maintaining both forward
>and reverse entries for ep.ipv6.nectec.or.th (router) and
><http://www.ipv6.nectec.or.th>www.ipv6.nectec.or.th
>
>$ORIGIN ipv6.nectec.or.th.
>@ 1D IN SOA leo root.leo (
> 2002101001 ; serial
> 8H ; refresh
> 2H ; retry
> 1W ; expiry
> 1D ) ; minimum
>
> 1D IN NS leo
>
>ep 1D IN AAAA 3ffe:400b:400b::9
> 1D IN A 203.185.132.158
>www 1D IN CNAME leo
>leo 1D IN AAAA 3ffe:400b:6003::9
> 1D IN A 203.185.132.132
>
>=> Reverse DNS Delegation :
>$ dig -t any 3.0.0.6.b.0.0.4.e.f.f.3.ip6.int @rns1.v6.inet.co.th
>
>; <<>> DiG 8.3 <<>> -t 3.0.0.6.b.0.0.4.e.f.f.3.ip6.int @rns1.v6.inet.co.th
>; (1 server found)
>;; res options: init recurs defnam dnsrch
>;; got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
>;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
>;; QUERY SECTION:
>;; 3.0.0.6.b.0.0.4.e.f.f.3.ip6.int, type = ANY, class = IN
>
>;; AUTHORITY SECTION:
>3.0.0.6.b.0.0.4.e.f.f.3.ip6.int. 12H IN NS leo.ipv6.nectec.or.th.
>
>;; ADDITIONAL SECTION:
>leo.ipv6.nectec.or.th. 4h32m34s IN A 203.185.132.132
>
>;; Total query time: 51 msec
>;; FROM: leo.ipv6.nectec.or.th to SERVER: rns1.v6.inet.co.th 203.150.14.111
>;; WHEN: Fri Jan 31 11:26:55 2003
>;; MSG SIZE sent: 49 rcvd: 100
>
> 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://www.ipv6.nectec.or.th>http://www.ipv6.nectec.or.th --v4/v6
>accessible
>
>=> The result of ping6 <http://www.ipv6.nectec.or.th>www.ipv6.nectec.or.th
>PING6(56=40+8+8 bytes) 3ffe:8140:101:7::1 --> 3ffe:400b:6003::9
>16 bytes from 3ffe:400b:6003::9, icmp_seq=0 hlim=57 time=679.311 ms
>16 bytes from 3ffe:400b:6003::9, icmp_seq=1 hlim=57 time=1159.21 ms
>16 bytes from 3ffe:400b:6003::9, icmp_seq=2 hlim=57 time=655.809 ms
>16 bytes from 3ffe:400b:6003::9, icmp_seq=3 hlim=57 time=876.863 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.
>
>=> TB6-6BONE,
> CC8-6BONE,
> PT4-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.
>
>=> <mailto:ipv6@nectec.or.th>ipv6@nectec.or.th
>
> 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 Thailand's IPv6 Testbed project was formally established in October
>2001, under the management of Thai Social/Science Academic and Research
> Network (ThaiSARN-3) project
> (<http://www.thaisarn.net.th>http://www.thaisarn.net.th),
> National Electronics and Computer Technology Center
>(<http://www.nectec.or.th>http://www.nectec.or.th).
>With a mission to promote the next generation Internet in the country,
>this project is proposed in order to establish national IPv6 gateway and
>provide IPv6 testing services to support research and experimentally
>operational activities towards development of IPv6-related technologies
>and IPv6-ready networks for all Thai public.
>
> 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 present and future operational rules and policies
> of 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.
>
>===================
>
>Thank you
>Thailand's IPv6 Testbed