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

pTLA request for MICROSOFT - review closes 2 January 2002

6bone Folk,

MICROSOFT has requested a pTLA allocation. The open review period for this 
will close 2 January 2002. Please send your comments to me or the list.




>Subject: pTLA Request for Microsoft
>Date: Fri, 14 Dec 2001 10:02:27 -0800
>From: "Chris Engdahl" <[email protected]>
>To: "Bob Fink" <[email protected]>
>Cc: "ITG IPv6 Engineering Team" <[email protected]>
>Hi Bob & the 6Bone-
>I'd like to request a pTLA for Microsoft Corporation, please find
>relevant info below.
>Thank you-
>Chris Engdahl
>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.
>       the entire qualifying period the Applicant must be operationally
>       providing the following:
>       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:    MICROSOFT
>origin:       AS8070
>descr:        Microsoft IPv6 Site
>country:      US
>prefix:       3FFE:2900:201::/48
>prefix:       3FFE:C00:8036::/48
>tunnel:       IPv6 in IPv4 iusdxbonec7501-l1.ipv6.microsoft.com ->
>sl-bb1v6-nyc.sprintlink.net SPRINT BGP4+
>tunnel:       IPv6 in IPv4 iusdxbonec7501-l1.ipv6.microsoft.com ->
>ipv6-lab-gw.cisco.com CISCO BGP4+
>contact:      CE1-6BONE
>contact:      DF4-6BONE
>contact:      DML1-6BONE
>notify:       [email protected]
>mnt-by:       MNT-MSFT
>changed:      [email protected] 20011113
>changed:      [email protected] 20011213
>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.
>See router above: iusdxbonec7501.ipv6.microsoft.com currently peers with
>Sprint and Cisco.
>       c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
>          entries for the Applicant's router(s) and at least one host
>          system.
>6to4                    A
>                         AAAA  2002:836b:213c:1:e0:8f08:f020:8
>iusdxbonec7501-l1       AAAA  2002:836b:213c:1:e0:8f08:f020:8
>iusdxbonec7501-tun1     AAAA  3ffe:2900:2:1:0:0:0:2
>iusdxbonec7501-tun2     AAAA  3ffe:c00:8023:3a:0:0:0:2
>www                     A
>                         AAAA  2002:836b:9820:0:0:0:836b:9886
>         IN   PTR      iusdxbonec7501-l1.ipv6.microsoft.com.
>         IN   PTR      iusdxbonec7501-tun1.ipv6.microsoft.com.
>         IN   PTR      iusdxbonec7501-tun2.ipv6.microsoft.com.
>         IN   PTR      www.ipv6.microsoft.com.
>       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.
>[see above]
>    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:      CE1-6BONE
>contact:      DF4-6BONE
>contact:      DML1-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.
>notify:       [email protected]
>    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.
>Statement of User Community and Intent to Provide Production-Quality
>IPv6 Backbone Services:
>Microsoft Information Technology Group provides enterprise-wide network
>connectivity to Microsoft research and development sites across the
>globe.  Prefixes derived from the pTLA would be used to address sites
>across several different geographic regions and will interconnect
>externally with diverse providers.  In addition, this will serve as
>initial research toward eventual deployment of IPv6 services across
>Microsoft's Internet network properties.
>    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 do indeed.]
>    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.
>8. 6Bone Operations Group
>    The 6Bone Operations Group is the group in charge of monitoring and
>    policing adherence to the current rules. Membership in the 6Bone
>    Operations Group is mandatory for, and restricted to, sites connected
>    to the 6Bone.
>    The 6Bone Operations Group is currently defined by those members of
>    the existing 6Bone mailing list who represent sites participating in
>    the 6Bone. Therefore it is incumbent on relevant site contacts to
>    join the 6Bone mailing list. Instructions on how to join the list are
>    maintained on the 6Bone web site at < http://www.6bone.net>.