[6bone] Who respect RFC2772 ? (8. 6Bone Operations Group, 9. Common rules
enforcement for the 6bone)
Nicolas DEFFAYET
nicolas.deffayet@ndsoftware.net
31 Oct 2002 11:36:05 +0100
6bone folks,
Flames & co > /dev/null
RFC2772: http://www.ietf.org/rfc/rfc2772.txt
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.
Nobody monitoring the policing adherence !
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>.
9. Common rules enforcement for the 6bone
Participation in the 6Bone is a voluntary and benevolent undertaking.
However, participating sites are expected to adhere to the rules and
policies described in this document in order to maintain the 6Bone as
a quality tool for the deployment of, and transition to, IPv6
protocols and the products implementing them.
See my comments, a lot of pTLA (and 6bone sites) don't respect this
rules !
The following is in support of policing adherence to 6Bone rules and
policies:
1. Each pTLA site has committed to implement the 6Bone's rules and
policies, and SHOULD try to ensure they are adhered to by sites
within their administrative control, i.e. those to who prefixes
under their respective pTLA prefix have been delegated.
A lot of pTLA respect this rules only during the pTLA request.
2. When a site detects an issue, it SHOULD first use the 6Bone
registry to contact the site maintainer and work the issue.
How do you contact a pTLA when in the whois you have an invalid email
address that bounce ?
3. If nothing happens, or there is disagreement on what the right
solution is, the issue SHOULD be brought to the 6Bone Operations
Group.
4. When the problem is related to a product issue, the site(s)
involved SHOULD be responsible for contacting the product vendor
and work toward its resolution.
5. When an issue causes major operational problems, backbone sites
SHOULD decide to temporarily set filters in order to restore
service.
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 ?