[6bone] Who respect RFC2772 ? (7. Guidelines for 6Bone pTLA sites)

[Nicolas DEFFAYET]

6bone folks,

Flames & co > /dev/null


RFC2772: http://www.ietf.org/rfc/rfc2772.txt



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. 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 lot of pTLA don't update their whois objects.

      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 lot of pTLA are not announced:
6COM (3FFE:1900::/24)
MREN (3FFE:1700::/24)
MOTOROLA-LABS (3FFE:4002::/32)
CAIRN (3FFE:1A00::/24)
LDCOM (3FFE:82E0::/28)
NL-BIT6 (3FFE:8350::/28)
UCB-BR (3FFE:3A00::/24)
ZAMA (3FFE:80F0::/28)
IFB (3FFE:0E00::/24)
ANSNET (3FFE:0D00::/24)
INFN-CNAF (3FFE:2300::/24)
EURNETCITY (3FFE:400D::/32)
UL (3FFE:1B00::/24)
BME-FSZ (3FFE:2F00::/24)
TIAI-PTLA (3FFE:8180::/28)


      c. Fully maintained DNS forward (AAAA) and reverse (ip6.int)
         entries for the Applicant's router(s) and at least one host
         system.

Many pTLA don't have reverse delegation for their pTLA.

      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 lot of pTLA respect this only during the pTLA request.

   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.

      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.

Many pTLA don't have valid email address (email bounce).

   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 lot of pTLA don't help IPv6 community and don't have a real potential
"user community".

   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.

   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.

A lot of pTLA meets the criteria above only during the pTLA request.

The pTLA said in their pTLA request that they agree to all current and
future rules and policies !

Do you think that this pTLA who don't respect the RFC2772 must keep
their pTLA ?