ETSI TS 102 518-2008 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) IPv4 to IPv6 Transitioning Conformance Test Suite Structure and Test Purposes (TSS&_1.pdf

《ETSI TS 102 518-2008 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) IPv4 to IPv6 Transitioning Conformance Test Suite Structure and Test Purposes (TSS&_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 518-2008 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) IPv4 to IPv6 Transitioning Conformance Test Suite Structure and Test Purposes (TSS&_1.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 518 V1.1.1 (2008-02)Technical Specification Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT);IPv4 to IPv6 Transitioning;Conformance Test Suite Structure andTest Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standar

2、ds“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other

3、 IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI TS 1

4、02 518 V1.1.1 (2008-02) 5 1 Scope The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference.

5、For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expecte

6、d life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cann

7、ot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (includin

8、g any amendments) applies. 1 ETSI TS 102 351: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework“. 2 ETSI TS 102 599: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv4 to IPV6 Transitioning; Require

9、ments Catalogue“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: A

10、bstract Test Suite specification“. 5 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 6 IETF RFC 2529: “Transmission of IPv6 over IPv4 Domains without Explicit Tunnels“. 7 IETF RFC 2765: “Stateless

11、IP/ICMP Translation Algorithm (SIIT)“. 8 IETF RFC 3056: “Connection of IPv6 Domains via IPv4 Clouds“. ETSI ETSI TS 102 518 V1.1.1 (2008-02) 6 9 IETF RFC 4213: “Basic Transition Mechanisms for IPv6 Hosts and Routers“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present doc

12、ument, the following terms and definitions given in ISO/IEC 9646-1 3 apply. abstract test case Abstract Test Method (ATM) Abstract Test Suite (ATS) Implementation Under Test (IUT) Lower Tester (LT) Test Purpose (TP) 3.2 Abbreviations For the purposes of the present document, the following abbreviati

13、ons apply: ATS Abstract Test Suite IETF Internet Engineering Task Force IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IUT Implementation Under Test RC Requirements Catalogue RQ Requirement TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Test Purposes have be

14、en written for 6to4-Nodes, 6to4-Routers, IP6/IP4_Nodes and IPtranslators according to the requirements (RQ) of the requirements catalogue (RC) in TS 102 599 2. Test purposes have been written for behaviours requested with “MUST“, optional behaviour described with “SHOULD“, “MAY“ or similar wording i

15、ndicating an option has not been turned into test purposes. The test purposes have been divided into four groups: Group 1: IPv6 Transitioning - RFC 2529 6 Group 2: IPv6 Transitioning - RFC 2765 7 Group 3: IPv6 Transitioning - RFC 3056 8 Group 4: IPv6 Transitioning - RFC 4213 9 The sub-grouping of th

16、ese two groups follows the structure of the RC. Group 1 RFC 2529 6 Group 1.1 Node Tests Group 1.1.1 Encapsulating IPv4 Header frame format validation Group 1.1.2 Stateless Auto-configuration and Link-local addresses on 6over4 ETSI ETSI TS 102 518 V1.1.1 (2008-02) 7 Group 1.1.3 Source and Target Link

17、 layer address options Group 1.1.4 IPv6 Multicast address mapping to IPv4 multicast address to support Neighbor Discovery Group 1.2 Router Tests Group 1.2.1 Boundary routers handling multicast IPv4 packets from 6over4 domain Group 2 RFC 2765 7 Group 2.1 IPv4-to-IPv6 translation Group 2.2 IPv6-to-IPv

18、4 translation Group 3 RFC 3056 8 Group 3.1 Node Tests Group 3.1.1 Test IPv6 Prefix Allocation Group 3.2 Encapsulation in IPv4 Group 3.2.1 Encapsulation of an IPv6Packet in an IPv4Packet Group 3.3 6to4 Site Communication Group 3.3.1 Unicast scenario Group 3.4 Security Consideration Group 3.4.1 Securi

19、ty consideration during Encapsulation of IPv6 packet in an IPv4 packet Group 3.4.2 Security consideration during Decapsulation of IPv6 packet from IPv4 packet Group 4 RFC 4213 9 Group 4.1 Node Tests Group 4.1.1 Resolver libraries Group 4.1.2 Configured tunneling - encapsulation Group 4.1.2.1 Encapsu

20、lation of an IPv6Packet in an IPv4Packet Group 4.1.3 Configured tunneling - decapsulation Group 4.1.3.1 Decapsulation of IPv6Packet from IPv4Packet Group 4.1.3.2 Handling errorneous packet while decapsulation Group 4.1.3.3 Link-local address on tunnel interface Group 4.1.4 Neighbor Discovery message

21、s on tunnel interface Group 4.1.4.1 Processing Probes packets on tunnel interface Group 4.1.4.2 Processing Neighbor discovery packets on tunnel interface Group 4.1.4.3 Sending Neighbor Discovery packets on tunnel interface ETSI ETSI TS 102 518 V1.1.1 (2008-02) 8 Annex A (normative): Test Purposes (T

22、P) The test purposes have been written in the formal notation TPlan as described in annex A of TS 102 351 1. This original textual output file is contained in an ASCII file (TRANS.tplan) (contained in archive “ts_102518v010101p0.zip“) which accompanies the present document. The raw text file has bee

23、n converted to a table format in this annex to allow better readability. The two formats shall be considered equivalent. In the event that there appears to be syntactical or semantic differences between the two then the textual TPlan representation takes precedence over the table format in this anne

24、x. A.1 IPv6 Transitioning - RFC 2529 A.1.1 Node Tests A.1.1.1 Encapsulating IPv4 Header frame format validation Test Purpose Identifier: TP_TRA_1003_01 Summary: Test Dont fragment bit in an encapsulating IPv4 header References: RQ_003_1003 IUT Role 6over4-Node Test Case: TC_TRA_1003_01 with IUT read

25、y to send IPv6Packet ensure that when IUT generates IPv6Packet then IUT encapsulates IPv6Packet in IPv4Packet and IUT sends IPv4Packet containing dont fragment bit set to 0 Test Purpose Identifier: TP_TRA_1004_01 Summary: Test protocol field in an encapsulating IPv4 header References: RQ_003_1004 IU

26、T Role 6over4-Node Test Case: TC_TRA_1004_01 with IUT ready to send IPv6Packet ensure that when IUT generates IPv6Packet then IUT encapsulates IPv6Packet in IPv4Packet and IUT sends IPv4Packet containing protocol set to 41 ETSI ETSI TS 102 518 V1.1.1 (2008-02) 9 Test Purpose Identifier: TP_TRA_1007_

27、01 Summary: Test TTL field in an encapsulating IPv4 header References: RQ_003_1007 IUT Role 6over4-Node Test Case: TC_TRA_1007_01 with IUT configured TTL value of 8 and IUT ready to send IPv6Packet ensure that when IUT generates IPv6Packet then IUT encapsulates IPv6Packet in IPv4Packet and IUT sends

28、 IPv4Packet containing ttl set to 8 A.1.1.2 Stateless Auto-configuration and Link-local addresses on 6over4 Test Purpose Identifier: TP_TRA_1009_01 Summary: Test IPv6 Link-local address format References: RQ_003_1009, RQ_003_1010, RQ_003_1011, RQ_003_1012 IUT Role 6over4-Node Test Case: TC_TRA_1009_

29、01 with IUT ready to form IPv6 Link-local address ensure that when IUT generates its Link-local address then IUT forms Link-local address containing universal or local bit set to zero and containing last 32 bits as hexadecimal representation of IPv4 address appended to the prefix FE80:/64 A.1.1.3 So

30、urce and Target Link layer address options Test Purpose Identifier: TP_TRA_1013_01 Summary: Test Frame format of Target Link-layer address option in the Neighbor Advertisement References: RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016 IUT Role 6over4-Node Test Case: TC_TRA_1013_01 with IUT ready

31、to send Neighbor Advertisement ensure that when IUT generates a Neighbor Advertisement containing Target Link-layer Address option then IUT sends Neighbor Advertisement containing Link_layer_Address_option containing type set to 2 bit 1 to 8 containing length set to 1 bit 9 to 16 containing reserved

32、 set to 0 bit 17 to 32 containing IPv4_address set to 32 bit address of the interface in network byte order ETSI ETSI TS 102 518 V1.1.1 (2008-02) 10Test Purpose Identifier: TP_TRA_1013_02 Summary: Test Frame format of Source Link-layer address option in the Neighbor Solicitation References: RQ_003_1

33、013,RQ_003_1014, RQ_003_1015, RQ_003_1016 IUT Role 6over4-Node Test Case: TC_TRA_1013_02 with IUT ready to send Neighbor Solicitation ensure that when IUT generates a Neighbor Solicitation containing Source Link-layer Address option then IUT sends Neighbor Solicitation containing Link_layer_Address_

34、option containing type set to 1 bit 1 to 8 containing length set to 1 bit 9 to 16 containing reserved set to 0 bit 17 to 32 containing IPv4_address set to 32 bit address of the interface in network byte order Test Purpose Identifier: TP_TRA_1013_03 Summary: Test Frame format of Source Link-layer add

35、ress option in the Router Advertisement References: RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016 IUT Role 6over4-Router Test Case: TC_TRA_1013_03 with IUT ready to send Router Advertisement ensure that when IUT generates a Router Advertisement containing Source Link-layer Address option then IU

36、T sends Router Advertisement containing Link_layer_Address_option containing type set to 1 bit 1 to 8 containing length set to 1 bit 9 to 16 containing reserved set to 0 bit 17 to 32 containing IPv4_address set to 32 bit address of the interface in network byte order ETSI ETSI TS 102 518 V1.1.1 (200

37、8-02) 11Test Purpose Identifier: TP_TRA_1013_04 Summary: Test Frame format of Source Link-layer address option in the Router Solicitation References: RQ_003_1013,RQ_003_1014, RQ_003_1015, RQ_003_1016 IUT Role 6over4-Node Test Case: TC_TRA_1013_04 with IUT ready to send Router Solicitation ensure tha

38、t when IUT generates a Router Solicitation containing Source Link-layer Address option then IUT sends Router Solicitation containing Link_layer_Address_option containing type set to 1 bit 1 to 8 containing length set to 1 bit 9 to 16 containing reserved set to 0 bit 17 to 32 containing IPv4_address

39、set to 32 bit address of the interface in network byte order A.1.1.4 IPv6 Multicast address mapping to IPv4 multicast address to support Neighbor Discovery Test Purpose Identifier: TP_TRA_1017_01 Summary: Test IPv6 all-node multicast address mapped to IPv4 multicast address References: RQ_003_1017,

40、RQ_003_1018, RQ_003_1020, RQ_003_1027 IUT Role 6over4-Node Test Case: TC_TRA_1017_01 with IUT configured organization local scope address block i.e: 192 and IUT 6over4 interface is enabled ensure that when IUT generates IPv6Packet with IPv6 destination address set to all-nodes multicast address FF02

41、:1 then IUT sends IPv6Packet tunneled in IPv4Packet containing ipv4_dst_addr set to IPv4 multicast address 239.192.0.1 Test Purpose Identifier: TP_TRA_1017_02 Summary: Test IPv6 all-routers multicast address mapped to IPv4 multicast address References: RQ_003_1017, RQ_003_1018, RQ_003_1020, RQ_003_1

42、027 IUT Role 6over4-Node Test Case: TC_TRA_1017_02 with IUT configured organization local scope address block i.e: 192 and IUT 6over4 interface is enabled ensure that when IUT generates IPv6Packet with IPv6 destination address set to all-routers multicast address FF02:2 then IUT sends IPv6Packet tun

43、neled in IPv4Packet containing ipv4_dst_addr set to IPv4 multicast address 239.192.0.2 ETSI ETSI TS 102 518 V1.1.1 (2008-02) 12Test Purpose Identifier: TP_TRA_1017_03 Summary: Test IPv6 solicited-node multicast address mapped to IPv4 multicast address References: RQ_003_1017, RQ_003_1018, RQ_003_102

44、0, RQ_003_1027 IUT Role 6over4-Node Test Case: TC_TRA_1017_03 with IUT configured organization local scope address block i.e: 192 and IUT 6over4 interface is enabled ensure that when IUT generates IPv6Packet with IPv6 destination address set to solicited-node multicast address FF02:1:FF28:9C5A then

45、IUT sends IPv6Packet tunneled in IPv4Packet containing ipv4_dst_addr set to IPv4 multicast address 239.192.156.90 A.1.2 Route Tests A.1.2.1 Boundary routers handling multicast IPv4 packets from 6over4 domain Test Purpose Identifier: TP_TRA_1024_02 Summary: Test multicast IPv4 packets with unknown or

46、ganization-local scope destination address References: RQ_003_1024 IUT Role 6to4-Router Test Case: TC_TRA_1024_02 with IUT configured organization local scope address block i.e: 192 ensure that when IUT ready to receive IPv4Packet then IUT discards IPv4 multicast packets containing destination addre

47、ss set to unknown organization-local scope address block i.e: 50 A.2 IPv6 Transitioning - RFC 2765 A.2.1 IPv4-to-IPv6 translation Test Purpose Identifier: TP_TRA_3003_01 Summary: Test 4to6 packet translation where DF bit is not set and fragmentation is necessary References: RQ_003_3003, RQ_003_3006,

48、 RQ_003_3007, RQ_003_3011, IUT Role IPtranslator Test Case: TC_TRA_3003_01 with IUT ready to translate IPv4Packet ensure that when IUT receives IPv4Packet with data leading to overall size 1280 bytes containing protocol and containing ip_identification and containing DF_bit set to 0 and containing ttl and containing ipv4_src_addr and containing ipv4_dst_addr then IUT sends IPv6Packet containing flow_Label set to all zero bits ETSI ETSI TS 102 518 V1.1.1 (2008-02) 13and containing next_header set to 44 and containing hop_limit se