[¤1] IPv6 Ready Logo Committee Test Suite Maintenance
[¤2] Procedure Document
[¤3]

Version 1.0
[¤5]

1. Version definitions: Major Version and Major Revision apply to both Interoperability and Conformance test suites. Minor Version applies only to Interoperability or Conformance test suites. The test suite version syntax is as follows:  
[¤9]
[¤10] MajorVersion.MajorRevision.MinorVersion.
[¤11]

a. Major Version: Compatibility requirements may change when the RFC is revised. A change in compatibility requires a change in test suite.
[¤13]

b. Major Revision: Additional tests to support additional product types.
[¤14]

c. Minor Revision: Test issues cause the removal or modification of controversial tests.
[¤15]

2. Official Release: If there are any changes to the test plan, a new revision will be released in May and November of each year (every 6 months). There will be no new revisions between these periods (with the exception of an Urgent Release). This is to create stability in the test plans. Official releases are considered "Major Version" releases or "Major Revision" Release. "Major Version" releases include updates that may breakcompatibility, such as restructuring of the test suite when the RFC is revised. "Major Revision" releases would include additional tests to support new features such as "1 interface" routers. Official releases may only be released if there is agreement between the laboratories that are defined in this document in section 3.
[¤17]

a. Transition period: New revisions of the test plan (except for the Minor Revision) will be disclosed 4 weeks before the official release. The purpose of this pre-release is to address technical comments and run the new tests in a "dry run" setting.
[¤20]

b. Pre-release Testing: Any testing that is executed before the official release on the new test suite version will not receive an IPv6 Ready logo, as the draft specification may change.
[¤22]

c. Urgent Release: If there is a serious technical problem and the entire logo committee agrees the test is important enough to fix, the test will be fixed. Urgent releases are considered "Minor Version" releases and may include fixes for typos. If the logo committee agrees that the test should be removed, the test will be removed.
[¤24]

3. Agreement is defined by consensus from the following parties:
[¤26]
[¤27]

Latif Ladid, President of the IPv6 Forum
[¤28] Jim Bound, CTO of the IPv6 Forum
[¤29] Hiroshi Esaki, Chair of the IPv6 Ready Logo Committee
[¤30] IRISA and ETSI in Europe
[¤31] TTA in Korea
[¤32] NICI IPv6 Lab in Taiwan
[¤33] BII in China
[¤34] TAHI in Japan
[¤35] UNH-IOL in North America
[¤36]

This consensus is reached on the mailing list.
[¤38]

4. New revisions of the test plan do NOT invalidate any vendors who have already received a logo. However, new revisions of a vendor's IPv6 implementation do NOTautomatically receive the logo if earlier versions have been tested. When new features are added, there is the potential to introduce bugs. New IPv6 implementation revisions must apply with the latest logo test specification once the new release is official. Please refer to Figure 1.
[¤40]

5. Each test suite documentation set (Interoperability + Conformance) is to be maintained individually (Core, IPsec, MIP, and future test suites).
[¤42]

6. Applications for the former test suite shall be accepted by the IPv6 Ready Logo Committee 4 weeks after the pre-release of the new version.
[¤44]

7. This maintenance document may only be altered if there is agreement between the laboratories that are defined in this document.
[¤46]