IPv6 READY Logo Phase 2
Session Initiation Protocol

The explanationof the submission
Version 2.0.1

IPv6 Forum
Converged Test Specification
IPv6 Ready Logo Committee
IPv6 Promotion Council (Japan)

http://www.ipv6forum.org
http://www.ipv6ready.org

Modification Record
Version 0.1

Mar. 16, 2007

- First release

Version 1.0.0

Apr. 27, 2007

- Modify the name syntax in section 3.4.5.

Version 1.0.1

Jul.31, 2007

- Added UNH-IOL members in Author's List.
- Added UNH-IOL in copyright.

Version 1.0.2

May.30, 2008

- Changed some explanation.
- Changed "3.3 Submission for conformance test".

Version 1.1.0

Dec. 12, 2008

- Major revision up.
- Some typos were corrected.

Version 2.0.0

Nov. 27, 2009

Version 2.0.1

Jan. 13, 2010

-Modified for Major Version up- Modified some misspellings.
- Modified some incorrect parts.

＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿
IPv6 FORUM TECHNICAL DOCUMENT

IPv6 Ready Logo Program
Guidelines
SIP IPv6

Acknowledgement
IPv6 Forum would like to acknowledge the efforts of the following organizations andcommentators in the development of this test specification.
-

IPv6 Promotion Council
Certification Working GroupSIP IPv6 Sub Working Group-

Commentators:＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿
IPv6 FORUM TECHNICAL DOCUMENT

IPv6 Ready Logo Program
Guidelines
SIP IPv6

Table of Contents
1. Overview .......................................................................................................................... 1
2. Reference Standards ....................................................................................................... 2
3. About the submission ......................................................................................................3
3.1 The list of the submission..........................................................................................3
3.2 Application form......................................................................................................... 4
3.3 Submission for conformance test..............................................................................5
3.4 Submission for interoperability test ........................................................................ 6
3.5 Directory structure ...................................................................................................8＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿
IPv6 FORUM TECHNICAL DOCUMENT

IPv6 Ready Logo Program
Guidelines
SIP IPv6

1. Overview
This document describes about the required submission to obtain the SIP IPv6 Ready
Logo Phase-2.

1

2. Reference Standards(1) RFC3261: SIP: Session Initiation Protocol (http://www.ietf.org/rfc/rfc3261.txt)(2) RFC3264: An Offer/Answer Model with Session Description Protocol(http://www.ietf.org/rfc/rfc3264.txt)(3) RFC4566: SDP: Session Description Protocol (http://www.ietf.org/rfc/rfc4566.txt)(4) RFC2617: HTTP Authentication: Basic and Digest Access Authentication(http://www.ietf.org/rfc/rfc2617.txt)(5) RFC3665: SIP Basic Call Flow Examples (http://www.ietf.org/rfc/rfc3665.txt)(6) IPv6 Ready Logo Phase 2 Policy(7) SIP IPv6 Test Scope23. About the Submission
3.1 The List of the Submission
These files that are shown in Table 3-1 are necessary to submit for obtaining the SIP
IPv6 Ready Logo Phase-2.

Table 3-1 The list of the submission
Category

Submission

Explanation

Application

Application Form

Application form of SIP IPv6 Ready Logo

Form
Conformance

Phase-2.
Test log

test

The HTML log generated when conformance
test was executed.

Configuration file

The config.txt set up when conformance test
was executed.

Test tool

The

test

tool

which

was

used

when

conformance test was executed.
Interoperability

Test Result Table

test

The sheet that describes the information oftest results in interoperability test.

Topology Map

The sheet that describes the information of
topology

map

and

IP

address

wheninteroperability test was executed.
Packet Capture File

The Packet Capture File (e.g. tcpdump(pcap))

of

each

link

acquiredwheninteroperability test was executed.
The detail of each submission is described in the following subsections. Also, thedirectory structure is described in subsection 3.5.

3

3.2 Application Form
The application form has been released on IPv6 Ready Logo Web Site
(http://www.ipv6ready.org/). The name of application form is as below.
- User Agent:- Endpoint:

app_form_Phase2_SIP-IPv6_UA.txt
app_form_Phase2_SIP-IPv6_EP.txt.

- Back to Back User Agent: app_form_Phase2_SIP-IPv6_B2BUA.txt.
- Proxy Server: app_form_Phase2_SIP-IPv6_PX.txt.
- Registrar Server: app_form_Phase2_SIP-IPv6_RG.txt.
For information on how to fill in the application form, see the following:-- Target Information
Fill in name, country, version (version of the product), and explanation of applicant
device. You can just write the explanation of product briefly.
-- Contact Person
Fill in name and e-mail address of applicant.
-- Test Information
Fill in name of OS/Protocol stack that the applicant implementation includes,
the Logo ID of IPv6 Ready Logo Phase-2 for IPv6 Core, the version of the
Conformance test / interoperability test document.
Fill in OS/Protocol stack ONLY WHEN the applicant implementation uses that.
-- Test results
Fill in the information of the applicant implementation in the interoperability test.
Write vender name and device / product, and version.
There must be two or more different types (different vendors) of equipments.
-- Target Supporting Functions
Select the functions that the applicant implementation supports. All BASIC
functions MUST be supported. Select ADVANCED functions if the applicant
implementation supports ADVANCED functions and executed the related
Conformance test scenario to obtain ADVANCED Logo.

4

3.3 Submission for Conformance Test
3.3.1. Conformance Test Log
Submit all HTML logs that have been generated and stored in a configured directoryduring conformance test. The directory structure is described in subsection 3.5.

3.3.2. Conformance Test Configuration File
Submit the config.txt that has been configured and stored in the same directory as
subsection 3.3.1 during conformance test.

3.3.3. Conformance Test Tool
Submit the test tool that was used during conformance test. The directory structure is
described in subsection 3.5.

5

3.4 Submission for Interoperability Test
3.4.1. Interoperability Test Result Table
Fill in the information of interoperability test results. Fill out the Result Table sheets
included in Interoperability test Scenario document and submit it to us (You can use
any formats for sending Result Table to us. For example, you can use txt format.). The
directory structure for submission is described in subsection 3.5.
For information on how to fill out Result Table sheets, see the following.
-- Result Table
Fill out interoperability test results, as the examples at the end of Result Table
sheets. You can submit it only if all blanks are filled in “PASS”.

3.4.2. Topology Map
Fill in vender name, device name, topology map of UA /EP/B2BUA/PX/RG that is used
in interoperability test.
Fill in the information of test topology in interoperability test. Fill out the Topology
Map sheets included in Interoperability test Scenario document and submit it to us(You can use any formats for sending Topology Map to us. For example, you can use txt
format.). The directory structure for submission is described in subsection 3.5.
For information on how to fill out Topology Map sheets, see the following.
Fill in the configuration of interoperability test as the examples in Topology Map
sheets.
-- Topology Map
Fill in Interoperability test scenario Item number, vender name, device name,topology map of UA / EP / B2BUA / PX / RG that is used in interoperability test.
-- IP address information
Fill in the prefix of each link and IP address / MAC address of UA / EP / B2BUA /PX / RG / Router. Fill in the address of when you have executed interoperability
test.

6

3.4.3. Scenario Check SheetThis sheet is used to check items of “Observable Result” in interoperability scenario
when interoperability test is executed. This document does not have to be submitted
for the SIP IPv6 Ready Logo Phase-2. It is included in this document.

3.4.4. Packet Capture File
Submit packet capture files (e.g. tcpdump (pcap)) of links in interoperability test. The
file name of this packet capture file must be:[ScenarioName]_[Send Vendor]_[Receive Vendor]_[Link No].cap.
Ex.)In case of executing test of Interop.1.1, Foo Corp is a send vendor, HogeCorp is areceiving vendor, and uses Link1, the file name should be:
Interop.1.1_FooCorp_HogeCorp_Link1.cap

7

3.5 Directory Structure
Before submitting, check and organize your all data as following directory structure:
IPv6ReadyLogoForSip_YourVenderName /||-----app_form_Phase2_SIP-IPv6_[UA|EP|B2BUA|PX|RG].txt|-----ConformanceTestLog/||----- ct-sip-ipv6[ua|ep|b2bua|px|rg]||-----Makefile||-----Makefile.inc||----- sip-ipv6[ua|ep|b2bua|px|rg]||-----index.html||-----config.txt||-----result.html||-----1.html||-----2.html||-----3.html||-----|-----IOTestLog/|-----Result_Table.txt|-----TargetVenderName_01/||-----Topology_Map.txt||-----PacketCaptureFile/||----- Interop.1.1_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap||-----|-----TargetVenderName_02/|-----Topology_Map.txt|-----PacketCaptureFile/|-----Interop.1.1_SendVender_RecieveVendor_LinkNo.cap|----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap|----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap|-----Put your all data file under “IPv6ReadyLogoForSip_YourVenderName” directory.
Also, make and submit a tar.gz archive file instead of uncompressed files themselves.
8

Example of User Agent
IPv6ReadyLogoForSip_YourVenderName /||-----app_form_Phase2_SIP-IPv6 UA.txt|-----ConformanceTestLog/|-----<Conformance Test results (e.g. ct-sip-ipv6ua.tar.gz)>|||--ct-sip-ipv6ua|----Makefile|----Makefile.inc|----sip-ipv6-ua|-----index.html|-----config.txt|-----result.html|-----1.html|-----2.html|-----3.html|-----

|
|
|
|
|
|
|
|
|-----IOTestLog/||-----Result_Table.txt|----- TargetVenderName_01/||-----Topology_Map.txt||----- PacketCaptureFile /||----- Interop.1.1_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap||-----|----- TargetVenderName_02/|-----Topology_Map.txt|----- PacketCaptureFile /|----- Interop.1.1_SendVender_RecieveVendor_LinkNo.cap|----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap|----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap|-----Put your all data file under “IPv6ReadyLogoForSip_YourVenderName” directory.
Also, make and submit a tar.gz archive file instead of uncompressed files themselves.

9Example of Proxy Server
IPv6ReadyLogoForSip_YourVenderName /||-----app_form_Phase2_SIP-IPv6_PX.txt|-----ConformanceTestLog/||-----<Conformance Test results (e.g. ct-sip-ipv6px.tar.gz)>|||--ct-sip-ipv6px|----Makefile||----Makefile.inc||----sip-ipv6-px||-----index.html|-----config.txt||-----result.html||-----1.html||-----2.html|-----3.html||----|-----IOTestLog/||-----Result_Table.txt|----- TargetVenderName_01/||-----Topology_Map.txt||-----PacketCaptureFile/||----- Interop.1.1_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap||----|----- TargetVenderName_02/||-----Topology_Map.txt||----- PacketCaptureFile /||----- Interop.1.1_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap||----|----- TargetVenderName_03/||-----Topology_Map.txt||----- PacketCaptureFile /||----- Interop.1.1_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.2_SendVender_RecieveVendor_LinkNo.cap||----- Interop.1.3_SendVender_RecieveVendor_LinkNo.cap||----|----- TargetVenderName_AA01/ (If the ADVANCED architecture is executed.)||----- ... (same as above “TargetVenderName_01”)|----- TargetVenderName_AA02/ (If the ADVANCED architecture is executed.)||----- ... (same as above “TargetVenderName_01”)|----- TargetVenderName_AA03/ (If the ADVANCED architecture is executed.)||----- ... (same as above “TargetVenderName_01”)|----- TargetVenderName_AA04/ (If the ADVANCED architecture is executed.)|----- ... (same as above “TargetVenderName_01”)

Put your all data file under “IPv6ReadyLogoForSip_YourVenderName” directory.
Also, make and submit a tar.gz archive file instead of uncompressed files themselves.

10

APPENDIX
Checksheet of IPv6 Ready Logo Program Phase-2 for SIP IPv6
Interoperability Test Scenario
This sheet is for checking the files that should be submitted for the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory
files are ready to submit.

Category : UA / Endpoint / B2BUA / Proxy Server / Registrar Server
Required submission
Test Result Table

Reference
Chapter 3*1

Description

OK or NGEnd Result*1 : Document of “The explanation of the submission”.

For UA /Requiredsubmission

Reference

Description

Check item *2
CmbPtn 11

Topology Map

Chapter 3*1

Network Topology map
The information of nodeaddress, link etc

Packet Capture File*3

Chapter 3*1

Save the packet logs oneach link

CmbPtn 2*1 : Document of “The explanation of the submission”.
*2 : The number of combinations of the vendor.
*3 : Refer to the next section “Packet Capture File for UA” to see all the Packet Capture Files.

For Endpoint
Requiredsubmission
Topology Map

Reference

Description

Check item *2
CmbPtn 1

Chapter 3*1

CmbPtn 2

Network Topology map
The information of nodeaddress, link etc
Packet Capture File Chapter 3
Save the packet logs on*3*1each link*1 : Document of “The explanation of the submission”.
*2 : The number of combinations of the vendor.
*3 : Refer to the next section “Packet Capture File for Endpoint” to see all the Packet Capture Files.

1 CmbPtn : Combination Pattern

11For B2BUA
Requiredsubmission
Topology Map

Reference
Chapter 3*1

Description

Check item *2

Network Topology map *4
The information ofnode address, link etc*5*6

Packet Capture File*3

Chapter 3*1

Save the packet logs on *4each link*5*6

CmbPtn 1

CmbPtn 1

CmbPtn 1

CmbPtn 2

CmbPtn 2

CmbPtn 2

CmbPtn 3

CmbPtn 1

CmbPtn 1

CmbPtn 1

CmbPtn 3

CmbPtn 4

CmbPtn 2

CmbPtn 2

CmbPtn 2

CmbPtn 3

CmbPtn 3

CmbPtn 4*1 : Document of “The explanation of the submission”.
*2 : The number of combinations of the vendor.
*3 : Refer to the next section “Packet Capture File for B2BUA” to see all the Packet Capture Files.
*4 : interop.1.1-1.4, interop.2.9-2.12*5 : interop.3.1-3.3, interop.3.6*6 : interop.3.4-3.5

For Proxy Server
Requiredsubmission
Topology Map

Reference
Chapter 3*1

Description

Check item *2

Network Topology map *4
The information ofnode address, link etc*5Packet Capture File*3

Chapter 3*1

Save the packet logs on *4each link*5*1 : Document of “The explanation of the submission”.
*2 : The number of combinations of the vendor.

12

CmbPtn 1

CmbPtn 1

CmbPtn 1

CmbPtn 1

CmbPtn 2

CmbPtn 2

CmbPtn 3

CmbPtn 2

CmbPtn 2

CmbPtn 3

CmbPtn 4

CmbPtn 3

CmbPtn 3

CmbPtn 4

*3 : Refer to the next section “Packet Capture File for Server” to see all the Packet Capture Files.
*4 : BASIC architecture*5 : ADVANCED architecture

For Registrar Server
Required
Referencesubmission
Topology Map

Description

Check item *2
CmbPtn 1

Chapter 3*1

CmbPtn 2

Network Topology map
The information of nodeaddress, link etc
Packet Capture File Chapter 3
Save the packet logs on*3*1each link*1 : Document of “The explanation of the submission”.
*2 : The number of combinations of the vendor.
*3 : Refer to the next section “Packet Capture File for Endpoint” to see all the Packet Capture Files.

13

1 Confirmation of Topology Map
Topology Map File for UA
Confirm the files that should be submitted under theInteroperability Test.
Fill in “OK” or “NG” on the following blanks (checkitem) to check that the mandatory files are ready tosubmit.

Node

Vendor Name
CmbPtn 1

CmbPtn 2UA0UA1
Server0* UA1 : The node that is necessary to execute Interop.2.1-2.12.

CN

Category

U

Registration

Test
num

Item
num

1

Interop.1.1

2

Interop.1.2

3Interop.1.3

4Interop.1.4

5Interop.2.1

6Interop.2.2

7Interop.2.3

8Interop.2.4

9Interop.2.5

10Interop.2.6

11Interop.2.7

12Interop.2.8

13Interop.2.9

14Interop.2.10

15Interop.2.11

16

Interop.2.12

Topology Map FileA

Session: BASIC- Confirm that the each topology map is based on Topologyof “Interoperability Test Scenario” document.
- Confirm the description of the each node information,
configured MAC Address on the interface, Link-Local
Address and Global Address, with the topology in the
scenario.
- Confirm that the combinations of vendor names and thedevice name of each node are consistent on all Topology
Map. And confirm that these information are consistent
with the Target node information (vendor name and devicename) of the Topology Map and Target node information(vendor name) of the Application form.

: ADVANCED*1 : The number of combinations of the vendor.

14

Check item *1
CmbPtn 1

CmbPtn 2

Topology Map File for Endpoint
Confirm the files that should be submitted under theInteroperability Test.
Fill in “OK” or “NG” on the following blanks (checkitem) to check that the mandatory files are ready tosubmit.

Node

Vendor Name
CmbPtn 1

CmbPtn 2UA0UA1
Server0* UA1 : The node that is necessary to execute Interop2.1-2.12.

CN

Category

E

Registration

Test
num

Item
num

1

Interop.1.1

2

Interop.1.2

3Interop.1.3

4Interop.1.4

5Interop.2.1

6Interop.2.2

7Interop.2.3

8Interop.2.4

9Interop.2.5

10Interop.2.6

11Interop.2.7

12Interop.2.8

13Interop.2.9

14Interop.2.10

15Interop.2.11

16

Interop.2.12

Topology Map FileP

Session: BASIC- Confirm that the each topology map is based on Topologyof “Interoperability Test Scenario” document.
- Confirm the description of the each node information,
configured MAC Address on the interface, Link-Local
Address and Global Address, with the topology in the
scenario.
- Confirm that the combinations of vendor names and thedevice name of each node are consistent on all Topology
Map. And confirm that these information are consistent
with the Target node information (vendor name and devicename) of the Topology Map and Target node information(vendor name) of the Application form.

: ADVANCED*1 : The number of combinations of the vendor.

15

Check item *1
CmbPtn 1

CmbPtn 2

Topology Map File for B2BUA
Confirm the files that should be submitted under the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready to submit.

For Interop.1.1-1.4, Interop.2.9-2.12
Node

For Interop.3.1-3.6

Vendor Name
CmbPtn 1

Node

CmbPtn 2

B2BUA
UA0Server0

Vendor Name
CmbPtn 1

CmbPtn 2

CmbPtn 3

CmbPtn 4

B2BUA
UA0
UA1
Server0* UA1 : The node that may necessary to execute* UA1 : The node that is necessary to execute Interop.3.4-3.5

Interop.2.9-2.12, Interop.3.1-3.6.

*Server0 : The node that isn’t necessary to execute Interop.3-1-3-3, Interop.3-6
CN

Category

B

Registration

Test
num

Item
num

1

Interop.1.1

2

Interop.1.2

3Interop.1.3

4Interop.1.4

5Interop.2.9

6Interop.2.10

Check item *1

Topology Map File

CmbPtn 1

CmbPtn 2

2
B
UA

Session- Confirm that the each topology map is based on
Topology of “Interoperability Test Scenario”
document.

7

Interop.2.11

8Interop.2.12

Test
num

Item
num

9

Interop.3.1- Confirm that the combinations of vendor names

10Interop.3.2

all Topology Map. And confirm that these

11Interop.3.3

information (vendor name and device name) of the

Test
num

Item
num

12

Interop.3.4

13Interop.3.5

Test
num

Item
num

14

Interop.3.6- Confirm the description of the each node

B2BUA

information, configured MAC Address on theinterface, Link-Local Address and Global Address,
with the topology in the scenario.

CmbPtn 1

CmbPtn 2

CmbPtn 3

and the device name of each node are consistent on
information are consistent with the Target node
Topology Map and Target node information (vendor
name) of the Application form.

CmbPtnCmbPtnCmbPtnCmbPtn1

2

3

4

CmbPtn 1: BASIC: ADVANCED*1 : The number of combinations of the vendor.
16

CmbPtn 2

CmbPtn 3

Topology Map File for Proxy Server
Confirm the files that should be submitted
under the Interoperability Test.
Fill in “OK” or “NG” on the following
blanks (check item) to check that the
mandatory files are ready to submit.

Node

Vendor Name
CmbPtn 1

CmbPtn 2

CmbPtn 3

CmbPtn 4Server0
UA0
UA1
Server1*Server1 : The node that isn’t necessary to execute Interop.2.1-2.6, Interop.2.9-2.12

CN

Category
SessionCheck item *1

Test
num

Item
num

1

Interop.2.1

2Interop.2.2

3Interop.2.3

4Interop.2.4

5Interop.2.5

6Interop.2.6

7Interop.2.9

document.

8

Interop.2.10- Confirm the description of the each node

Topology Map File

CmbPtn 1

CmbPtn 2

CmbPtn 3

P
X- Confirm that the each topology map is based on
Topology of “Interoperability Test Scenario”

information, configured MAC Address on the
9Interop.2.11

10Interop.2.12

Test
num

Item
num

interface, Link-Local Address and Global Address,
with the topology in the scenario.
- Confirm that the combinations of vendor names andthe device name of each node are consistent on all
Topology Map. And confirm that these information are
consistent with the Target node information (vendor

11

Interop.1.5

12Interop.2.13

13

Interop.2.14

14Interop.2.15

15

Interop.2.16

16

Interop.2.17

17Interop.2.18

CmbPt

CmbPt

CmbPt

CmbPtn

n1

n2

n3

4

name and device name) of the Topology Map andTarget node information (vendor name) of the
Application form.

: BASIC: ADVANCED: The architecture on 2 proxies: If an applicant implementation obtains Proxy Logo and Registrar Logo, it is BASIC.
In other case, it is ADVANCED.
*1 : The number of combinations of the vendor.

17

Topology Map File for Registrar Server
Confirm the files that should be submitted under theInteroperability Test.
Fill in “OK” or “NG” on the following blanks (checkitem) to check that the mandatory files are ready tosubmit.

C
N

Category

Test
num

CmbPtn 1

Interop.1.1

G

Topology Map File

Topology of “Interoperability Test Scenario”
document.
- Confirm the description of the each node2

Interop.1.2

information, configured MAC Address on theinterface, Link-Local Address and Global Address,
with the topology in the scenario.
- Confirm that the combinations of vendor names and3Interop.1.3

device name of each node are consistent on all
Topology Map. And confirm that these information
are consistent with the Target node information(vendor name and device name) of the Topology Map

4Interop.1.4

CmbPtn 2

Server0
UA0- Confirm that the each topology map is based on
1

Vendor Name

Check item *1

Item
num

RegistrationR

Nodeand Target node information (vendor name) of the
Application form.

: BASIC*1 : The number of combinations of the vendor.

18

CmbPtn 1

CmbPtn 2

2 Confirmation of Packet Capture File
Packet Capture File for UA
Confirm the files that should be submitted under the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready to submit.
C
N

Category

U

Registration

Test
num

Item
num

1

Interop.1.1

Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Interop.1.2_SendVendor_RecieveVendor_Link1.cap

3Interop.1.3

Interop.1.3_SendVendor_RecieveVendor_Link1.cap

4Interop.1.4

Interop.1.4_SendVendor_RecieveVendor_Link1.cap

5Interop.2.1

Interop.2.1_SendVendor_RecieveVendor_Link1.cap

6Interop.2.2

Interop.2.2_SendVendor_RecieveVendor_Link1.cap

7Interop.2.3

Interop.2.3_SendVendor_RecieveVendor_Link1.cap

8Interop.2.4

Interop.2.4_SendVendor_RecieveVendor_Link1.cap

9Interop.2.5

Interop.2.5_SendVendor_RecieveVendor_Link1.cap

10Interop.2.6

Interop.2.6_SendVendor_RecieveVendor_Link1.cap

11Interop.2.7

Interop.2.7_SendVendor_RecieveVendor_Link1.cap

12Interop.2.8

Interop.2.8_SendVendor_RecieveVendor_Link1.cap

13Interop.2.9

Interop.2.9_SendVendor_RecieveVendor_Link1.cap

14Interop.2.10

Interop.2.10_SendVendor_RecieveVendor_Link1.cap

15Interop.2.11

Interop.2.11_SendVendor_RecieveVendor_Link1.cap

16Interop.2.12

Interop.2.12_SendVendor_RecieveVendor_Link1.cap

Packet Capture FileA

Session: BASIC: ADVANCED*1 : The number of combinations of the vendor.

19

Check item *1
CmbPtn 1

CmbPtn 2

Packet Capture File for Endpoint
Confirm the files that should be submitted under the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready to submit.
C
N

Category

E

Registration

Test
num

Item
num

1

Interop.1.1

Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Interop.1.2_SendVendor_RecieveVendor_Link1.cap

3Interop.1.3

Interop.1.3_SendVendor_RecieveVendor_Link1.cap

4Interop.1.4

Interop.1.4_SendVendor_RecieveVendor_Link1.cap

5Interop.2.1

Interop.2.1_SendVendor_RecieveVendor_Link1.cap

6Interop.2.2

Interop.2.2_SendVendor_RecieveVendor_Link1.cap

7Interop.2.3

Interop.2.3_SendVendor_RecieveVendor_Link1.cap

8Interop.2.4

Interop.2.4_SendVendor_RecieveVendor_Link1.cap

9Interop.2.5

Interop.2.5_SendVendor_RecieveVendor_Link1.cap

10Interop.2.6

Interop.2.6_SendVendor_RecieveVendor_Link1.cap

11Interop.2.7

Interop.2.7_SendVendor_RecieveVendor_Link1.cap

12Interop.2.8

Interop.2.8_SendVendor_RecieveVendor_Link1.cap

13Interop.2.9

Interop.2.9_SendVendor_RecieveVendor_Link1.cap

14Interop.2.10

Interop.2.10_SendVendor_RecieveVendor_Link1.cap

15Interop.2.11

Interop.2.11_SendVendor_RecieveVendor_Link1.cap

16Interop.2.12

Interop.2.12_SendVendor_RecieveVendor_Link1.cap

Packet Capture FileP

Session: BASIC: ADVANCED*1 : The number of combinations of the vendor.

20

Check item *1
CmbPtn 1

CmbPtn 2

Packet Capture File for B2BUA
Confirm the files that should be submitted under the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready tosubmit.
C
N

Category

B

Registration

Test
num

Item
num

1

Interop.1.1

Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Interop.1.2_ SendVendor_RecieveVendor _Link1.cap

3Interop.1.3

Interop.1.3_ SendVendor_RecieveVendor _Link1.cap

4Interop.1.4

Interop.1.4_ SendVendor_RecieveVendor _Link1.cap

5Interop.2.9

Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

6Interop.2.10

Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

7Interop.2.11

Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

8Interop.2.12

Interop.2.12_SendVendor_RecieveVendor_Link1.cap

Test
num

Item
num

9

Interop.3.1

Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

10Interop.3.2

Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

11Interop.3.3

Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

Test
num

Item
num

Packet Capture File

12Interop.3.4

Interop.2.12_SendVendor_RecieveVendor_Link1.cap

13Interop.3.5

Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

Test
num

Item
num

14

Interop.3.6

2
B
U
A

Session

B2BUA: BASIC

Check item *1

Packet Capture File

Packet Capture File

Packet Capture File
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap: ADVANCED*1 : The number of combinations of the vendor.

21

CmbPtn 1

CmbPtn 2

CmbPtn 1

CmbPtn 2

CmbPtn 3

CmbPtnCmbPtnCmbPtnCmbPtn1

2

3

4

CmbPtn 1

CmbPtn 2

CmbPtn 3

Packet Capture File for Proxy Server
Confirm the files that should be submitted under the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready tosubmit.
C
N

Category
SessionP
X

Check item *1

Test
num

Item
num

1

Interop.2.1

Interop.2.1_SendVendor_RecieveVendor_Link1.cap

2Interop.2.2

Interop.2.2_SendVendor_RecieveVendor_Link1.cap

3Interop.2.3

Interop.2.3_SendVendor_RecieveVendor_Link1.cap

4Interop.2.4

Interop.2.4_SendVendor_RecieveVendor_Link1.cap

5Interop.2.5

Interop.2.5_SendVendor_RecieveVendor_Link1.cap

6Interop.2.6

Interop.2.6_SendVendor_RecieveVendor_Link1.cap

7Interop.2.9

Interop.2.9_SendVendor_RecieveVendor_Link1.cap

8Interop.2.10

Interop.2.10_SendVendor_RecieveVendor_Link1.cap

9Interop.2.11

Interop.2.11_SendVendor_RecieveVendor_Link1.cap

10Interop.2.12

Interop.2.12_SendVendor_RecieveVendor_Link1.cap

Test
num

Item
num

11

Interop.1.5

Interop.1.5_SendVendor_RecieveVendor_Link1.cap

12Interop.2.13

Interop.2.13_SendVendor_RecieveVendor_Link1.cap

13Interop.2.14

Interop.2.14_SendVendor_RecieveVendor_Link1.cap

14Interop.2.15

Interop.2.15_SendVendor_RecieveVendor_Link1.cap

15Interop.2.16

Interop.2.16_SendVendor_RecieveVendor_Link1.cap

16Interop.2.17

Interop.2.17_SendVendor_RecieveVendor_Link1.cap

17Interop.2.18

Interop.2.18_SendVendor_RecieveVendor_Link1.cap

Packet Capture File

Packet Capture File

CmbPtn 1

CmbPtn 2

CmbPt

CmbPt

CmbPt

CmbPtn

n1

n2

n3

4

: BASIC: ADVANCED: The architecture on 2 proxies: If an applicant implementation obtains Proxy Logo and Registrar Logo, it is BASIC.
In other case, it is ADVANCED.
*1 : The number of combinations of the vendor.

22

CmbPtn 3

Packet Capture File for Registrar Server
Confirm the files that should be submitted under the Interoperability Test.
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready tosubmit.
C
N

Category

Check item *1

Test
num

Item
num

1

Interop.1.1

Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Interop.1.2_SendVendor_RecieveVendor_Link1.cap

3Interop.1.3

Interop.1.3_SendVendor_RecieveVendor_Link1.cap

4Interop.1.4

Interop.1.4_SendVendor_RecieveVendor_Link1.cap

Topology Map File

Registration
R
G: BASIC*1 : The number of combinations of the vendor.

23

CmbPtn 1

CmbPtn 2

3 Confirmation of Judgment
Packet Judgment for UA
Fill in “OK” or “NG” on the following blanks(check item) to check that the mandatory files
are ready to submit.

Node

Vendor Name
CmbPtn 1

CmbPtn 2UA0UA1
Server0* UA1 : The node that is necessary to execute Interop.2.1-2.12.

CN

Category

U

Registration

Test
num

Item
num

1

Interop.1.1

Refer to Section 3.1 - [6]. *2
Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Refer to Section 3.2 - [6]. *2
Interop.1.2_ SendVendor_RecieveVendor _Link1.cap

3Interop.1.3

Refer to Section 3.3 - [6]. *2
Interop.1.3_ SendVendor_RecieveVendor _Link1.cap

4Interop.1.4

Refer to Section 3.4 - [6]. *2
Interop.1.4_ SendVendor_RecieveVendor _Link1.cap

5Interop.2.1

Refer to Section 3.5 - [6]. *2
Interop.2.1_SendVendor_RecieveVendor_Link1.cap

6Interop.2.2

Refer to Section 3.6- [6]. *2
Interop.2.2_ SendVendor_RecieveVendor _Link1.cap

7Interop.2.3

Refer to Section 3.7 - [6]. *2
Interop.2.3_ SendVendor_RecieveVendor _Link1.cap

8Interop.2.4

Refer to Section 3.8 - [6]. *2
Interop.2.4_ SendVendor_RecieveVendor _Link1.cap

9Interop.2.5

Refer to Section 3.9 - [6]. *2
Interop.2.5_SendVendor_RecieveVendor_Link1.cap

10Interop.2.6

Refer to Section 3.10 - [6]. *2
Interop.2.6_ SendVendor_RecieveVendor _Link1.cap

11Interop.2.7

Refer to Section 3.11 - [6]. *2
Interop.2.7_ SendVendor_RecieveVendor _Link1.cap

12Interop.2.8

Refer to Section 3.12 - [6]. *2
Interop.2.8_SendVendor_RecieveVendor_Link1.cap

13Interop.2.9

Refer to Section 3.13- [6]. *2
Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

14Interop.2.10

Refer to Section 3.14 - [6]. *2
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

15Interop.2.11

Refer to Section 3.15 - [6]. *2
Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

16Interop.2.12

Refer to Section 3.16 - [6]. *2
Interop.2.12_SendVendor_RecieveVendor_Link1.cap

A

Session: BASIC

Judgment: ADVANCED*1 : The number of combinations of the vendor.
*2 : The Interoperability Test Scenario.

24

Check item *1
CmbPtn 1

CmbPtn 2

Check item : CmbPtn 1 / CmbPtn 2 *1
Use the following lists for the confirmation of the IP/MAC address when confirming above Packet Judgment.
Test
num

Item
num

Link no1

Interop.1.1

Link 1

2

Interop.1.2

Link 1

3

Interop.1.3

Link 1

4

Interop.1.4

Link 1

5Interop.2.1

Link 1

6

Interop.2.2

Link 1

7

Interop.2.3

Link 1

8

Interop.2.4

Link 1

9Interop.2.5

Link 1

10Interop.2.6

Link 1

11

Interop.2.7

Link 1

12

Interop.2.8

Link 1

13

Interop.2.9

Link 1

14

Interop.2.10

Link 1

15

Interop.2.11

Link 1

16

Interop.2.12

Link 1

SourceIP address*1 : The number of combinations of the vendor.

25

Destination
IP address

Source
MAC address

Destination
MAC address

Packet Judgment for Endpoint
Fill in “OK” or “NG” on the following blanks(check item) to check that the mandatory files
are ready to submit.

Node

Vendor Name
CmbPtn 1

CmbPtn 2UA0UA1
Server0* UA1 : The node that is necessary to execute Interop.2.1-2.12.

CN

Category

E

Registration

Test
num

Item
num

1

Interop.1.1

Refer to Section 3.1 - [6]. *2
Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Refer to Section 3.2 - [6]. *2
Interop.1.2_ SendVendor_RecieveVendor _Link1.cap

3Interop.1.3

Refer to Section 3.3 - [6]. *2
Interop.1.3_ SendVendor_RecieveVendor _Link1.cap

4Interop.1.4

Refer to Section 3.4 - [6]. *2
Interop.1.4_ SendVendor_RecieveVendor _Link1.cap

5Interop.2.1

Refer to Section 3.5 - [6]. *2
Interop.2.1_SendVendor_RecieveVendor_Link1.cap

6Interop.2.2

Refer to Section 3.6- [6]. *2
Interop.2.2_ SendVendor_RecieveVendor _Link1.cap

7Interop.2.3

Refer to Section 3.7 - [6]. *2
Interop.2.3_ SendVendor_RecieveVendor _Link1.cap

8Interop.2.4

Refer to Section 3.8 - [6]. *2
Interop.2.4_ SendVendor_RecieveVendor _Link1.cap

9Interop.2.5

Refer to Section 3.9 - [6]. *2
Interop.2.5_SendVendor_RecieveVendor_Link1.cap

10Interop.2.6

Refer to Section 3.10 - [6]. *2
Interop.2.6_ SendVendor_RecieveVendor _Link1.cap

11Interop.2.7

Refer to Section 3.11 - [6]. *2
Interop.2.7_ SendVendor_RecieveVendor _Link1.cap

12Interop.2.8

Refer to Section 3.12 - [6]. *2
Interop.2.8_SendVendor_RecieveVendor_Link1.cap

13Interop.2.9

Refer to Section 3.13- [6]. *2
Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

14Interop.2.10

Refer to Section 3.14 - [6]. *2
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

15Interop.2.11

Refer to Section 3.15 - [6]. *2
Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

16Interop.2.12

Refer to Section 3.16 - [6]. *2
Interop.2.12_SendVendor_RecieveVendor_Link1.cap

P

Session: BASIC

Judgment: ADVANCED*1 : The number of combinations of the vendor.
*2 : The Interoperability Test Scenario.

26

Check item *1
CmbPtn 1

CmbPtn 2

Check item : CmbPtn 1 / CmbPtn 2 *1
Use the following lists for the confirmation of the IP/MAC address when confirming above Packet Judgment.
Test
num

Item
num

Link no1

Interop.1.1

Link 1

2

Interop.1.2

Link 1

3

Interop.1.3

Link 1

4

Interop.1.4

Link 1

5Interop.2.1

Link 1

6

Interop.2.2

Link 1

7

Interop.2.3

Link 1

8

Interop.2.4

Link 1

9Interop.2.5

Link 1

10Interop.2.6

Link 1

11

Interop.2.7

Link 1

12

Interop.2.8

Link 1

13

Interop.2.9

Link 1

14

Interop.2.10

Link 1

15

Interop.2.11

Link 1

16

Interop.2.12

Link 1

SourceIP address*1 : The number of combinations of the vendor.

27

Destination
IP address

Source
MAC address

Destination
MAC address

Packet Judgment for B2BUA
Fill in “OK” or “NG” on the following blanks (check item) to check that the mandatory files are ready to submit.

For Interop.1.1-1.4, Interop.2.9-2.12
Node

For Interop.3.1-3.6

Vendor Name
CmbPtn 1

Node

CmbPtn 2

CmbPtn 1

B2BUA
UA0Server0

CmbPtn 2

CmbPtn 3

CmbPtn 4

B2BUA
UA0
UA1
Server0* UA1 : The node that may necessary to execute
Interop.2.9-2.12, Interop.3.1-3.6.

Vendor Name

* UA1 : The node that is necessary to execute Interop.3.4-3.5*Server0 : The node that isn’t necessary to execute Interop.3-1-3-3, Interop.3-6

CN

Category

B

Registration

Test
num

Item
num

1

Interop.1.1

Refer to Section 3.1 - [6]. *2
Interop.1.1_SendVendor_RecieveVendor_Link1.cap

2Interop.1.2

Refer to Section 3.2 - [6]. *2
Interop.1.2_ SendVendor_RecieveVendor _Link1.cap

3Interop.1.3

Refer to Section 3.3 - [6]. *2
Interop.1.3_ SendVendor_RecieveVendor _Link1.cap

4Interop.1.4

Refer to Section 3.4 - [6]. *2
Interop.1.4_ SendVendor_RecieveVendor _Link1.cap

5Interop.2.9

Refer to Section 3.13- [6]. *2
Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

6Interop.2.10

Refer to Section 3.14 - [6]. *2
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

7Interop.2.11

Refer to Section 3.15 - [6]. *2
Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

8Interop.2.12

Refer to Section 3.16 - [6]. *2
Interop.2.12_SendVendor_RecieveVendor_Link1.cap

Test
num

Item
num

9

Interop.3.1

Refer to Section 3.23 [6]. *2
Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

10Interop.3.2

Refer to Section 3.24 - [6]. *2
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

11Interop.3.3

Refer to Section 3.25 - [6]. *2
Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

Test
num

Item
num

Judgment

12

Interop.3.4

Refer to Section 3.26 - [6]. *2
Interop.2.12_SendVendor_RecieveVendor_Link1.cap

13Interop.3.5

Refer to Section 3.27- [6]. *2
Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

Test
num

Item
num

Judgment

14

Interop.3.6

Refer to Section 3.28 - [6]. *2
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

2
B
U
A

SessionB2BUA

Check item *1

Judgment

Judgment: BASIC: ADVANCED*1 : The number of combinations of the vendor.
*2 : The Interoperability Test Scenario.

28

CmbPtn 1

CmbPtn 2

CmbPtn 1

CmbPtn 2

CmbPtn 3

CmbPtnCmbPtnCmbPtnCmbPtn1

2

3

4

CmbPtn 1

CmbPtn 2

CmbPtn 3

Check item : CmbPtn 1 / CmbPtn 2 *1
Use the following lists for the confirmation of the IP/MAC address when confirming above Packet Judgment.
Test
num

Item
num

Link no1

Interop.1.1

Link 1

2

Interop.1.2

Link 1

3

Interop.1.3

Link 1

4

Interop.1.4

Link 1

5Interop.2.9

Link 1

6

Interop.2.10

Link 1

7

Interop.2.11

Link 1

8

Interop.2.12

Link 1

9Interop.3.1

Link 1

10Interop.3.2

Link 1

11

Interop.3.3

Link 1

12

Interop.3.4

Link 1

13

Interop.3.5

Link 1

14

Interop.3.6

Link 1

SourceIP address

Destination
IP address 1*1 : The number of combinations of the vendor.

29

Destination
IP address 2

Source
MAC address

Destination
MAC
address 1

Destination
MAC
address 2

Packet Judgment for Proxy Server
Fill in “OK” or “NG” on the following
blanks (check item) to check that the
mandatory files are ready to submit.

C
N

Category
SessionPX

Node

Vendor Name
CmbPtn 1

CmbPtn 2

CmbPtn 3

CmbPtn 4UA0UA1
Server0
Server1
Check item *1

Test
num

Item
num

1

Interop.2.1

Refer to Section 3.5 - [6]. *2
Interop.2.1_SendVendor_RecieveVendor_Link1.cap

2Interop.2.2

Refer to Section 3.6- [6]. *2
Interop.2.2_ SendVendor_RecieveVendor _Link1.cap

3Interop.2.3

Refer to Section 3.7 - [6]. *2
Interop.2.3_ SendVendor_RecieveVendor _Link1.cap

4Interop.2.4

Refer to Section 3.8 - [6]. *2
Interop.2.4_ SendVendor_RecieveVendor _Link1.cap

5Interop.2.5

Refer to Section 3.9 - [6]. *2
Interop.2.5_SendVendor_RecieveVendor_Link1.cap

6Interop.2.6

Refer to Section 3.10 - [6]. *2
Interop.2.6_ SendVendor_RecieveVendor _Link1.cap

7Interop.2.9

Refer to Section 3.13- [6]. *2
Interop.2.9_ SendVendor_RecieveVendor _Link1.cap

8Interop.2.10

Refer to Section 3.14 - [6]. *2
Interop.2.10_ SendVendor_RecieveVendor _Link1.cap

9Interop.2.11

Refer to Section 3.15 - [6]. *2
Interop.2.11_ SendVendor_RecieveVendor _Link1.cap

10Interop.2.12

Refer to Section 3.16 - [6]. *2
Interop.2.12_SendVendor_RecieveVendor_Link1.cap

Test
num

Item
num

11

Interop.1.5

Refer to Section 3.5 - [6]. *2
Interop.1.5_SendVendor_RecieveVendor_Link1.cap

12Interop.2.14

Refer to Section 3.18 - [6]. *2
Interop.2.14_SendVendor_RecieveVendor_Link1.cap

13Interop.2.13

Refer to Section 3.17 - [6]. *2
Interop.2.13_SendVendor_RecieveVendor_Link1.cap

14Interop.2.14

Refer to Section 3.18 - [6]. *2
Interop.2.14_SendVendor_RecieveVendor_Link1.cap

15Interop.2.16

Refer to Section 3.20 - [6]. *2
Interop.2.16_SendVendor_RecieveVendor_Link1.cap

16Interop.2.17

Refer to Section 3.21 - [6]. *2
Interop.2.17_SendVendor_RecieveVendor_Link1.cap

17Interop.2.18

Refer to Section 3.22 - [6]. *2
Interop.2.18_SendVendor_RecieveVendor_Link1.cap

Judgment

Packet Capture File

CmbPtn 1

CmbPtn 2

CmbPt

CmbPt

CmbPt

CmbPtn

n1

n2

n3

4

: BASIC: ADVANCED: The architecture on 2 proxies: If an applicant implementation obtains Proxy Logo and Registrar Logo, it is BASIC.
In other case, it is ADVANCED.
*1 : The number of combinations of the vendor.
*2 : The Interoperability Test Scenario.
30

CmbPtn 3

Check item : CmbPtn 1 / CmbPtn 2/ CmbPtn 3/ CmbPtn 4 *1
Use the following lists for the confirmation of the IP/MAC address when confirming above Packet Judgment.
Test
num

Item
num

Link No

1

Interop.2.1

Link 1

2

Interop.2.2

Link 1

3

Interop.2.3

Link 1

4

Interop.2.4

Link 1

5Interop.2.5

Link 1

6

Interop.2.6

Link 1

7

Interop.2.9

Link 1

8

Interop.2.10

Link 1

9Interop.2.11

Link 1

10Interop.2.12

Link 1

11

Interop.1.5

Link 1

12

Interop.2.13

SourceIP address

Destination
IP address 1

Link 1
Link 2
Link 1
13

Interop.2.14
Link 2
Link 1

14

Interop.2.15
Link 2
Link 1

15

Interop.2.16
Link 2
Link 1

16

Interop.2.17
Link 2
Link 1

17

Interop.2.18
Link 2*1 : The number of combinations of the vendor.

31

Destination
IP address 2

Source
MAC address

Destination
MAC
address 1

Destination
MAC
address 2

Packet Judgment for Registrar Server
NodeFill in “OK” or “NG” on the following
blanks (check item) to check that the
mandatory files are ready to submit.

C
N

Category

Test
num

Item
num

1

Interop.1.1

Registration
R

Vendor Name
CmbPtn 1

Server0
UA0
Check item *1
Judgment

Refer to Section 1.1 - [6].

*2Interop.1.1_SendVendor_RecieveVendor_Link1.cap

G

Refer to Section 1.2 - [6].
2*2Interop.1.2
Interop.1.2_SendVendor_RecieveVendor_Link1.cap
Refer to Section 1.3 - [6].

3*2Interop.1.3
Interop.1.3_SendVendor_RecieveVendor_Link1.cap
Refer to Section 1.4 - [6].

4CmbPtn 2*2

Interop.1.4
Interop.1.4_SendVendor_RecieveVendor_Link1.cap: BASIC*1 : The number of combinations of the vendor.
*2 : The Interoperability Test Scenario.

32

CmbPtn 1

CmbPtn 2

Check item : CmbPtn 1 / CmbPtn 2 *1
Use the following lists for the confirmation of the IP/MAC address when confirming above Packet
Judgment.
Test
num

Item
num

Link no1

Interop.1.1

Link 1

2

Interop.1.2

Link 1

3

Interop.1.3

Link 1

4

Interop.1.4

Link 1

SourceIP address*1 : The number of combinations of the vendor.

33

Destination
IP address

Source
MAC address

Destination
MAC address************************************************************************************

Copyright (C) 2005-2010 IPv6 Forum. All Rights Reserved.
This original documentation is produced by SIP IPv6 SWG members of Certification WG in the IPv6
Promotion Council. The SWG members currently include Nippon Telegraph and Telephone Corporation(NTT), Yokogawa Electric Corporation, University of New Hampshire InterOperability Laboratory(UNH-IOL), and NTT Advanced Technology Corporation (NTT-AT).
No part of this documentation may be reproduced for any purpose without prior permission.
34

Authors’ List
Hiroshi Miyata (Yokogawa Electric Corporation)
Yukiyo Akisada (Yokogawa Electric Corporation)
Erica Johnson (UNH-IOL)
Timothy Winters (UNH-IOL)
Yoshio Yoshida (NTT-AT)
Kenzo Kodama (NTT-AT)
Yoshihiro Inoue (NTT-AT)
Naomi Orimo(NTT-AT)

35