pTLA request for INTEC (www.v6.intec.co.jp) - review closes 9 June 2001

[Bob Fink]

6bone Folk,

INTEC (www.v6.intec.co.jp) has requested a pTLA allocation. The open review 
period for this will close 9 June 2001. Please send your comments to me or 
the list.


Thanks,

Bob

===
>From: Tomohiko Kusuda <kusuda@isl.intec.co.jp>
>Subject: pTLA request
>To: fink@es.net
>Cc: info@v6.intec.co.jp
>Date: Thu, 24 May 2001 16:44:41 +0900
>
>Dear Bob,
>
>We want to provide IPv6 connectivity to regional users.
>Please allocate us 6Bone pTLA addresses.
>
>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:
>
>We have experimented with IPv6 as 6Bone pNLA 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.
>
>inet6num:     3FFE:1800:2040::/48
>netname:      INTEC
>descr:        SLA delegation for the NTT-ECL
>country:      JP
>admin-c:      NO2-6BONE
>tech-c:       NO2-6BONE
>remarks:      This object is automatically converted from the RIPE181 registry
>mnt-by:       NTT-ECL-MNT
>changed:      nin@slab.ntt.co.jp 19990825
>changed:      auto-dbm@whois.6bone.net 20010117
>source:       6BONE
>
>ipv6-site:    INTEC
>origin:       AS9612
>descr:        INTEC
>country:      JP
>prefix:       3FFE:508::/32
>prefix:       3FFE:1CFA::/32
>prefix:       3FFE:1800:2040::/48
>application:  ping knight.v6.intec.co.jp
>application:  http www.v6.intec.co.jp
>contact:      TK4-6BONE
>contact:      YK60-AP
>notify:       info@v6.intec.co.jp
>mnt-by:       MAINT-JP-INTEC
>changed:      kusuda@isl.intec.co.jp 20010507
>changed:      kusuda@isl.intec.co.jp 20010522
>changed:      kusuda@isl.intec.co.jp 20010524
>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.
>
>Our router(knight.v6.intec.co.jp) connect natively with 
>pc6.otemachi.wide.ad.jp
>using BGP4+ at NSPIXP6.
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>Our name server is pawn.v6.intec.co.jp.
>
># host -t aaaa pawn.v6.intec.co.jp pawn.v6.intec.co.jp
>Using domain server:
>Name: pawn.v6.intec.co.jp
>Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53
>Aliases:
>
>pawn.v6.intec.co.jp. has AAAA address 2001:200:500:1800:200:f8ff:fe01:6ab8
>
># host -n 2001:200:500:1800:200:f8ff:fe01:6ab8 pawn.v6.intec.co.jp
>Using domain server:
>Name: pawn.v6.intec.co.jp
>Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53
>Aliases:
>
>8.b.a.6.1.0.e.f.f.f.8.f.0.0.2.0.0.0.8.1.0.0.5.0.0.0.2.0.1.0.0.2.ip6.int. 
>domain name pointer pawn.v6.intec.co.jp.
>
># host -t aaaa knight.v6.intec.co.jp pawn.v6.intec.co.jp
>Using domain server:
>Name: pawn.v6.intec.co.jp
>Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53
>Aliases:
>
>knight.v6.intec.co.jp. has AAAA address 2001:200:500:1800:2a0:c9ff:fea6:7add
>
># host -n 2001:200:500:1800:2a0:c9ff:fea6:7add pawn.v6.intec.co.jp
>Using domain server:
>Name: pawn.v6.intec.co.jp
>Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53
>Aliases:
>
>d.d.a.7.6.a.e.f.f.f.9.c.0.a.2.0.0.0.8.1.0.0.5.0.0.0.2.0.1.0.0.2.ip6.int. 
>domain name pointer knight.v6.intec.co.jp.
>
>
>       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.v6.intec.co.jp
>
>    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.
>
>contact:      TK4-6BONE
>contact:      YK60-AP
>
>       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:       info@v6.intec.co.jp
>
>
>    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.
>
>We provide IPv6 connectibity to users in regional area Toyama,
>Japan. Both individual and organization customers are already
>using our network to access 6bone or other IPv6 resources.
>
>    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.
>
>Yes, We commit and agree.
>
>--------
>Tomohiko Kusuda(kusuda@isl.intec.co.jp)
>INTEC Web and Genome Informatics Corporation
-end