[6bone] pTLA request by HP - review closes 22 January 2003

[Bob Fink]

6bone Folk,

HP 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.

<www.hwp6.net>


Thanks,

Bob

===
>From: "UPPENDAHL,MICKEY (HP-Corvallis,ex1)" <mickey_uppendahl@hp.com>
>To: "'fink@es.net'" <fink@es.net>, "'bob@thefinks.com'" <bob@thefinks.com>
>Cc: "UPPENDAHL,MICKEY (HP-Corvallis,ex1)" <mickey_uppendahl@hp.com>,
>    "FROELICH,STEVE (HP-Corvallis,ex1)" <steve_froelich@hp.com>
>Subject:
>Date: Mon, 6 Jan 2003 13:28:42 -0800
>
>Mr. Fink,
>
>On behalf of the Hewlett-Packard IT IPv6 Testbed Project, I would like to
>submit our application for a pTLA.
>
>-Mickey Uppendahl
>  HP - MSDD Strategic Communications Architecture
>  mickey.uppendahl@hp.com
>
>
>---------------- from RFC 2772 -------------------------------------------
>
>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've been running since 21 June 2002, meeting all requirements since that
>date.
>
>       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?HP
>http://whois.6bone.net/cgi-bin/whois?HP-Americas
>
>       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 boundary router is corgw01.hwp6.net, and is pingable via both v6 and v4.
>
>We currently maintain external connections to Sprint (who gave us our
>current
>block of IPv6 addresses) and internal connections (tunneled and native v6)
>between
>our 4 internal "core" sites, cascading to other edge site groups.  All
>connections
>are via BGP4+ using AS71.
>
>We have resisted making further external connections until we obtain pTLA
>space
>so that we can do full external peering relationships.  We've been using
>BGP4+
>within our testbed network, and members of our groups have extensive
>experience
>using both I-BGP and E-BGP in HP's IPv4 network.
>
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>
>Our current authoritative name servers:
>         corns01.hwp6.net
>         palns01.hwp6.net
>
>       d. A fully maintained, and reliable, IPv6-accessible system
>          providing, at a minimum, one or more web pages, describing the
>          Applicant's IPv6 services.  This server must be IPv6 pingable.
>
>www.hwp6.net (externally accessible)
>www.ipv6.hp.com (only accessible from inside HP's private network)
>
>
>    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.
>
>SFF-6BONE
>JLH-6BONE
>MJU-6BONE
>DDC-6BONE
>
>       b. A common mailbox for support contact purposes that all support
>          staff have access to, pointed to with a notify attribute in the
>          ipv6-site object for the pTLA Applicant.
>
>ipv6-admin@ipv6.hp.com
>
>    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 HP IT IPv6 Testbed provides IPv6 connectivity to internal
>Hewlett-Packard
>product development teams.  There well over 100,000 current HP employees and
>many IPv6 product development projects are underway, the details of which we
>would (obviously) prefer not to disclose publicly.  We expected to soon be
>required to provide connectivity to certain external business partners.
>
>The HP IT IPv6 is part of the company Information Services organization,
>currently located in the Managed Services Design & Delivery group.
>
>    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 agree to abide by all 6Bone rules and policies now and for as long as
>we continue to use the 6Bone.
>
>    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.
-end