IPv6 Ready Logo Phase-2

Objectives

• Encourage every organization to deploy IPv6.
• Provide end-users with information on interoperability and conformance testing of equipments.

Test Category

• IPv6 Core Protocols (Now Available!)
• IPsec (Now Available!)
• IKEv2 (Now Available!)
• MIPv6 (Now Available!)
• NEMO (Now Available!)
• DHCPv6 (Now Available!)
• SIP (Now Available!)
• Management(SNMP-MIBs) (Now Available!)
• MLD (Under Developing)
• Transition (Under Developing)
• IKE (Experimental)

Target

• IPv6 Core Protocols
  • Router BOX
  • Host BOX
  • Operation System
  • Protocol Stack
  • Special Devices (Under Discussion)
• IPsec
  • End-Node
  • Security Gateway
• IKEv2
  • End-Node
  • Security Gateway
• MIPv6
  • Correspondent Node
  • Home Agent
  • Mobile Node
• NEMO
  • Home Agent
  • Mobile Router
• DHCPv6
  • Client
  • Server
  • Relay Agent
• SIP
  • SIP Server (Proxy and Registrar)
  • SIP User Agent
• Management(SNMP-MIBs)
  • Agent
  • Nanager

Procedures

The target product must pass the 100% of self-test items.
For about interoperability, there are two ways in the self-test (inhouse test) base and interoperability test event base.

1. Obtain the test specification and the self-testing tools or submit the product to an IPv6 Ready testing laboratory.
2. Get test result log with the self-testing tool or get the result log from an IPv6 Ready testing laboratory.
3. If you are a participant of a interoperability test event, you can use the event logs for the interoperability.(*1)
4. Fill the Application Form.
5. Send the Application Form and the test evidence(*2) to v6-appli@ipv6ready.org by e-mail.(*3)
6. You will receive a Application ID for a acknowledgement and a URL of the Usage Agreement Confirmation page.
7. You should confirm the Usage Agreement on this page by to fill the entry information and press "apply button" to show your intention of agreement.(*4)
8. The Local Interface Person will contact to you in order to guide the examination process of your application.
9. Examination will start by the technical officers. If the applicant does not get any response within 1 month, please inform to ipv6ready-info@ipv6ready.org.
10. If the result of examination is judged successful, you will get the Phase-2 IPv6 Ready Logo and associated Logo ID.
11. Approved information of this application will be put on this Website.
12. If you want to update informations of approved product (i.e. version no.), please follow this instruction.

(*1) The participation to the interoperability event is not mandatory. The approval of logo usage is based on the test specification. This means that the test procedure for logo of Phase-2 at the interoperability event must be exectly based on the test specification. And, when the product does not satisfy the test specification, the product can not be approved, even if the product has far advanced functions and interoperability with many other products.With regards to the validation by the interoperability event, there needs to be a coordinator's endorsement for test report.

(*2) The test evidence should include the following items.

• Configuration
• Command result
• Test result
• Packet dump file
• Others (If required)

(*3) You can also send the test evidence via web page, if your evidence is very huge to send by e-mail. Please go this page.

(*4) You can see this Usage Agreement to get reference document before your application. If you don't agree with this Usage Agreement, we can't approve your usage of the Phase-2 IPv6 Ready Logo.

Criteria

1) Self-test base application

• 100% pass for Self-test based on the test specification.
• 4 interoperable devices(*5) from other vendors including 2 hosts and 2 routers.

2) Interoperability test event base application

• 100% pass for Self-test based on the test specification.
• 4 interoperable devices(*5) from other vendors including 2 hosts and 2 routers.
• The interoperability test report is required.

(*5) 4 interoperable devices should be different. Different devices have different software origins and knowledge of this resides in the public domain. If devices have the same software origins, they are not "different".

1. The devices are not "different" if they contain the same stack on different hardware platforms. This may cause slight variation in software behavior, but it will not vary enough to be defined as "different".
   

   Example:
   ROUTER: OS-A on Vendor-A PC
   ROUTER: OS-A on Vendor-B PC
   HOST: OS-A on Vendor-C PC
   HOST: OS-A on Vendor-D PC

2. The devices are not "different" if they contain the same stack on different operating systems or operating system versions. This may cause slight variation in software behavior, but it will not vary enough to be defined as "different".

   Example1:
   ROUTER: OS-A Version.A
   ROUTER: OS-A Version.B
   HOST: OS-A Version.C
   HOST: OS-A Version.D
   
   Example2:
   ROUTER: OS-A Version.A
   ROUTER: OS-A Version.B
   HOST: OS-B Version.A
   HOST: OS-B Version.B
   
   Example3:
   ROUTER: Kame Stack on NetBSD
   ROUTER: Kame Stack on FreeBSD
   HOST: Usagi Stack on Linux
   HOST: Kame Stack on OpenBSD
   

3. Devices may be "different" if they contain an embeded component. Some devices may be "different" if they contain a software stack that was integrated onto 2 different types of hardware where the origins are not distinguishable. In this case it will be assumed that the systems in question are "different" unless the knowledge that they come from the same software stack is in the public domain.

Technical Issues

• The test specification
  • Latest version is here.
  • At this moment, the target device is limited to HOST and ROUTER.
• The self-testing tools
  • Latest version is here.

Last Modified at 2008/12/25