[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

6bone pTLA request from DTI starts 2-week review, closes 29 Nov 99

6bone Folk,

DTI (Dream Train Internet) in Japan has applied for a pTLA, thus I'm 
opening a two week review of their pTLA request (see below). This closes on 
29 Nov 99.

Note that this request is being made using the HARDEN I-D, not RFC 2546, 
which are more stringent that 2546:


I think this is appropriate as this I-D passed WG last call last Monday and 
will be forwarded soon to the IESG to replace 2546.




>To: [email protected]
>Cc: [email protected], [email protected]
>Subject: pTLA request from DTI
>From: Koji Kondo <[email protected]>X-Mailer: Mew version 1.95b3 on Emacs 
>20.3 / Mule 4.0 (HANANOEN)
>Date: Tue, 16 Nov 1999 09:57:54 +0900
>We, DTI, would like to request a pTLA prefix.
>In draft-ietf-ngtrans-harden-01.txt Chapter 7:
>   1. The pTLA Applicant must have a minimum of three (3) months
>      qualifying experience as a 6Bone end-site or pNLA transit.
>      During this entire qualifying period the Applicant must be
>      operationally providing the following:
>We are a transit pNLA site under the WIDE pTLA since August 1998.
>Now, we have 6bone connectivity as follows,
>- some pTLAs peering with BGP4+ at NSPIXP6(IPv6-based IX in Tokyo).
>- some NLAs peering with BGP4+ or RIPng.
>      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 object is DTI.
>inet6num object is 3FFE:50A::/32.
>mntner object is MNT-DTI.
>      b. Fully maintained, and reliable, BGP4+ peering and connec-
>         tivity between the Applicant's boundary router with the
>         appropriate hierarchy.  This includes a high uptime
>         availability of the site router (greater than 99%). This
>         router must be IPv6 pingable.
>We maintain BGP4+ router(ix6.v6.dti.ad.jp) at NSPIXP6 in tokyo and have
>high uptime availability.
>      c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>         entries for their site's router, and at least one host ser-
>         ver system.
>DNS forward (AAAA) and reverse (ip6.int) are available.
>      d. A fully maintained, and reliable host server system providing,
>         at a mimimum, one or more web pages describing the applicant's
>         project and service on the 6Bone, available via IPv6.  This
>         server must be IPv6 pingable.
>Web page is available. This server can connect via IPv4 and IPv6,
>and IPv6 pingable.
>    2. The pTLA Applicant MUST have the ability and intent to provide
>       "production-like" 6Bone backbone service to provide a robust
>       and operationally reliable 6Bone backbone. Applicants must pro-
>       vide a statement and some supportable information to support
>       this claim.  This MUST include the following:
>We are now providing connectivity services to three IPv6 leaf sites.
>Our connection details is available at
>"http://www.v6.dti.ad.jp/connections.html"; .
>      a. a support staff of two persons minimum, 3 preferable, with
>         person attributes registered for each in the ipv6-site object
>         for the pTLA applicant.
>Person attributes are "KK1-6BONE" and "ST1-6BONE".
>      b. a common mailbox for support contact purposes that all staff
>         have acess to , pointed to with a notify attribute in the ipv6-
>         site object for the pTLA Applicant.
>All of staffs have accesstable mailbox both via ipv4 and ipv6.
>    3. The pTLA Applicant MUST have a potential "user community" that
>       would be served by 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 some
>       supportable information to support this claim.
>We are one of the major ISPs in Japan. And already offering connectivity
>to three IPv6 leaf sites(see above "connection details page").
>    4. The pTLA Applicant MUST commit to abide by the current 6Bone
>       operational rules and policies as they exist at time of appli-
>       cation, 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 will commit to abide by the 6Bone backbone operational rules and