pTLA request for APAN-JO

[Bob Fink]

6bone Folk,

APAN-JP has requested a pTLA allocation. The open review period for this 
will close 29 Jan 2001. Please send any comments to me or the list.


Thanks,

Bob

======================================
>Date: Tue, 16 Jan 2001 11:33:46 +0900
>From: Yuichiro HEI <hei@kddlabs.co.jp>
>To: fink@es.net
>CC: kdd@jp.apan.net
>Subject: pTLA request for APAN-JP
>
>Dear Mr.Fink,
>
>This is Yuichiro Hei from APAN-JP, requesting 6Bone pTLA address.
>
>I attach the request form of pTLA.
>We hope we meet the 6bone's requirement, but if something is missing,
>please let us know.
>
>Best regards,
>
>Yuichiro Hei
>APAN-JP
>
>-----------------
>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:
>
>A: We have been connected to the 6Bone since 1998.
>
>       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.
>
>A: We do not maintain 6Bone registry entries now (I mean it is mainly for
>    3ffe:... address), but now we maintain a sNLA address space delegated
>    from WIDE, and maintain an up-to-date APNIC registry. Please refer the
>    APNIC registry. For example:
>      % whois -h whois.apnic.net 2001:200:900::/40
>
>       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.
>
>A: We maintain the BGP4+ peering with WIDE(AS2500) via NSPIXP6, which is
>    an IX for IPv6 in Japan. Our IPv6 router is tp6r2.jp.apan.net.
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>A: We maintain DNS forward (AAAA) and reverse (ip6.int) entries on
>    ns.jp.apan.net. For example:
>
>% dig ns2.jp.apan.net aaaa
>...
>
>;; ANSWER SECTION:
>ns2.jp.apan.net.        22h1m44s IN AAAA  2001:200:901:2::2
>...
>
>% dig 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.1.0.9.0.0.0.2.0.1.0.0.2.ip6.int
>       ptr
>
>;; ANSWER SECTION:
>2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.1.0.9.0.0.0.2.0.1.0.0.2.ip6.int.
>1D IN PTR  ns2.jp.apan.net.
>
>
>       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.
>
>A: www.jp.apan.net is the web server that describes our research and
>    development activities. This can be accessed by both IPv4 and IPv6.
>    Our IPv6 activity described in this server is old, so we will update
>    it soon.
>
>    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.
>
>A: Support staff:
>       Kazunori Konishi      (konish@jp.apan.net)
>       Akira Kato            (kato@wide.ad.jp)
>       Yoshinori Kitatsuji   (kitaji@jp.apan.net)
>       Yuichiro Hei          (hei@jp.apan.net)
>
>       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.
>
>A: Common mailbox:
>        ops@jp.apan.net
>
>    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.
>
>A: APAN (Asia Pacific Advanced Network) is a non-profit international
>    consortium for research and development in advanced networking and
>    services in the Asia-Pacific region. APAN provides a high-performance
>    network environment for research community mainly in the country of
>    Asia, for example Japan, Korea, Singapore, Australia, Malaysia,
>    China, etc., and many research communities work actively on APAN network.
>    So we have an Asian-wide potential usr community.
>    We will intent to use pTLA address for these research communities
>    and collaborate on them.
>
>
>    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.
>
>A:  We agree the 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.