1、 ETSI TS 102 517 V1.1.1 (2006-04)Technical Specification Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT); IPv6 Core Protocol;Interoperability Test Suite (ITS)ETSI ETSI TS 102 517 V1.1.1 (2006-04) 2 Reference DTS/MTS-IPT-007-IPv6-CoreITS Keywords IP, IPv6, interoperability
2、, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present docu
3、ment can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispu
4、te, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ET
5、SI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by writ
6、ten permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo ar
7、e Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 517 V1.1.1 (2006-04) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 Ref
8、erences 6 3 Abbreviations .6 3.1 Abbreviations .6 4 IPv6 Core Interoperability Test Specification7 4.1 Introduction 7 4.2 Test Descriptions7 4.2.1 RFC 2460, IPv6 Core Specification7 4.2.1.1 Generate IPv6 Packet 7 4.2.1.2 Process IPv6 Packet 7 4.2.1.2.1 Process IPv6 Header7 4.2.1.2.1.1 Process Hop Li
9、mit .7 4.2.1.2.2 Process Flow Label9 4.2.1.3 Extension Headers.10 4.2.1.3.1 Process Extension Headers10 4.2.1.3.2 Routing Header11 4.2.1.3.2.1 Process Routing Header.11 4.2.1.3.3 Fragment Header .14 4.2.1.3.3.1 Generate Fragmented Packets14 4.2.1.3.3.2 Process Fragmented Packets 14 4.2.2 RFC 2461, N
10、eighbor Discovery for IPv6 .16 4.2.2.1 Generate Neighbor Discovery Messages 16 4.2.2.1.1 Generate Router Advertisement 16 4.2.2.1.1.1 Router Advertisement Behavior.16 4.2.2.1.1.1.1 Router Advertisement Behavior on Reconfiguration .16 4.2.2.1.1.1.2 Startup Router Advertisement Behavior 18 4.2.2.1.1.2
11、 Form Router Advertisement Options.20 4.2.3 TP_COR_8141_01 .20 4.2.3.1 Router Advertisement MTU OPtion .20 4.2.3.1.1 Generate Router Solicitation .21 4.2.3.1.2 Generate Neighbor Advertisement 22 4.2.3.1.2.1 Generate Unsolicited Neighbor Advertisements22 4.2.3.1.3 Generate Redirect Message .22 4.2.3.
12、1.3.1 Determine Redirect Target Address Field22 4.2.4 TP_COR_8546_01 .23 4.2.4.1 Process Neighbor Discovery Messages.23 4.2.4.1.1 Process Router Advertisement.23 4.2.4.1.1.1 Host Processing of Router Advertisement .24 4.2.4.1.1.2 Discover Neighbor by Router Advertisement27 4.2.4.1.2 Process Router S
13、olicitation28 4.2.4.1.2.1 Discover Neighbor by RS 30 4.2.4.1.3 Process Neighbor Advertisement 30 4.2.4.1.4 Process Neighbor Solicitation .31 4.2.4.1.4.1 Generate Solicited Neighbor Advertisement .31 4.2.4.1.4.2 Process Proxy NS.33 4.2.4.1.5 Process Redirect Message .33 4.2.4.1.5.1 Host Processing of
14、 Redirect Message33 4.2.4.1.5.2 Discover Neighbor by Redirect Message.33 4.2.4.2 Next Hop Determination.33 4.2.5 TP_COR_8364_01 .34 4.2.5.1 Neighbor Uneachability Detection34 4.2.5.1.1 Neighbor Reachability Determination.34 ETSI ETSI TS 102 517 V1.1.1 (2006-04) 4 4.2.5.2 Address Resolution .34 4.2.5
15、.2.1 Interface Initialization .36 4.2.6 RFC 2462, IPv6 Stateless Address Autoconfiguration .38 4.2.6.1 Initialize 38 4.2.6.1.1 Configure Address.38 4.2.6.1.1.1 Simultaneous Stateless and Stateful Autoconfiguration 38 4.2.6.1.1.2 Detect Duplicate Address (DAD) 39 4.2.6.1.1.3 Assign Global Address 40
16、4.2.6.1.1.3.1 Use of O-Flag.41 4.2.6.1.1.4 Stateless Autoconfiguration .42 4.2.7 RFC 2463, ICMPv6 43 4.2.7.1 ICMPv6 Functions 43 4.2.7.1.1 Determine ICMPv6 Message Source Address.43 4.2.7.1.2 ICMPv6 Error Messages .45 4.2.7.1.2.1 Destination Unreachable Message .45 4.2.7.1.2.2 Packet Too Big Message
17、46 4.2.7.1.2.3 Time Exceeded Message47 4.2.7.1.3 Information Messages .48 4.2.7.1.3.1 Echo Request and Echo Reply.48 4.2.8 RFC 3513, Address Architecture49 4.2.8.1 Address Architecture.49 4.2.8.2 Unicast Addresses .52 4.2.8.3 Anycast Addresses 53 4.2.8.4 Multicast Addresses 53 4.2.8.4.1 Pre-defined
18、Multicast Addresses .53 4.2.8.4.2 Node 54 4.2.9 RFC 1981, Path MTU Discovery for IPv6 .55 4.2.9.1 Discover PMTU 55 4.2.9.1.1 Multicast PMTU Discovery.57 4.2.10 RFC 2675, Jumbograms .57 Annex A (informative): IPv6 Interoperability Test Purposes 60 Annex B (informative): Interoperability Testing Confi
19、gurations96 History 100 ETSI ETSI TS 102 517 V1.1.1 (2006-04) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-memb
20、ers, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.
21、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 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 p
22、resent document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI TS 102 517 V1.1.1 (2006-04) 6 1 Scope The present document specifies the interoperability Test Descriptions (TDs) with integrated Test Purp
23、oses (TPs) for the IPv6 Core standards. The TDs are presented in the tabular form specified in ETSI TS 102 424 1 and the TPs are defined using the TPLan notation also described in ETSI TS 102 424. The Test Suite Structure is based on the IETF RFCs which, together, form the IPv6 Core specification an
24、d is reflected in the use of “Group/End Group“ statements in the TPLan code presented in annex A. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of public
25、ation and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/do
26、cbox.etsi.org/Reference. 1 ETSI TS 102 424 (2005): “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework“. 2 IETF RFC 1981: “Path MTU Discovery for IP version 6“. 3 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6) Specification“. 4
27、IETF RFC 2461: “Neighbor Discovery for IP Version 6 (IPv6)“. 5 IETF RFC 2462: “IPv6 Stateless Address Autoconfiguration“. 6 IETF RFC 2463: “Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification“. 7 IETF RFC 2675: “IPv6 Jumbograms“. 8 IETF RFC 3513: “Inte
28、rnet Protocol Version 6 (IPv6) Addressing Architecture“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: EUT Equipment Under Test HS Host i/f interface LL Link Local M/cast Multicast MTU Maximum Transmission Unit PMTU Path MTU QE Qualified Equipment RT Ro
29、uter SL Site Local TP Test Purpose TD Test Description TPLan Test Purpose Language TSS Test Suite Structure ETSI ETSI TS 102 517 V1.1.1 (2006-04) 7 4 IPv6 Core Interoperability Test Specification 4.1 Introduction The IPv6 Core Interoperability Test Descriptions (TDs) defined in the following clauses
30、 are derived from the Test Purposes (TPs) specified in annex A. 4.2 Test Descriptions 4.2.1 RFC 2460, IPv6 Core Specification 4.2.1.1 Generate IPv6 Packet No tests specified in this group. 4.2.1.2 Process IPv6 Packet 4.2.1.2.1 Process IPv6 Header TP_COR_1097_01 TP_COR_1097_02 4.2.1.2.1.1 Process Hop
31、 Limit Test Description Identifier: TD_COR_1002_01 Summary: EUT decreases the Hop Limit field of a traversed IPv6 packet and forwards it Test Purpose: TP_COR_1002_01 Reference: RQ_COR_1002 Configuration: CF_022_I with QE1 configured with a unique global unicast address and QE2 configured with a uniq
32、ue global unicast address and EUT configured with two unique global unicast addresses on the link connecting QE1 and EUT, and the link connecting QE2 and EUT, respectively ensure that when EUT receives a packet containing QE1 as source address and QE2 as destination address and containing Hop Limit
33、1 then EUT sends the packet with the Hop Limit decremented to QE2 Pre-test conditions: EUT established as the default router for QE1 Step Test Sequence Verdict Pass Fail 1 Cause QE1 to send an Echo Request with QE2 identified as the destination and hop limit larger than 1 2 Check: Does protocol moni
34、tor on link2 show that the Echo Request was sent from QE1 to QE2, with a decremented hop limit? Yes No 3 Check: Does QE1 receive an Echo Reply from QE2? Yes No Observations Test Description Identifier: TD_COR_1002_02 Summary: EUT drops a traversed IPv6 packets with Hop Limit = 1 and returns an ICMP
35、error message to the source Test Purpose: TP_COR_1002_02 Reference: RQ_COR_1002 Configuration: CF_022_I with QE1 configured with a unique global unicast address ETSI ETSI TS 102 517 V1.1.1 (2006-04) 8 and QE2 configured with a unique global unicast address and EUT configured with two unique global u
36、nicast addresses on the link connecting QE1 and EUT, and on the link connecting QE2 and EUT, respectively ensure that when EUT receives a packet containing QE1 as source address and QE2 as destination address and containing Hop Limit = 1 then EUT discards the packet and EUT sends an ICMP error messa
37、ge to QE1 Pre-test conditions: EUT established as the default router for QE1 Step Test Sequence Verdict Pass Fail 1 Cause QE1 to send an Echo Request with QE2 identified as the destination and hop limit of 1 2 Check: does the protocol monitor on link2 show that the Echo Request was sent from QE1 to
38、QE2? No Yes 3 Check: does the protocol monitor on link1 show that an ICMP error message was sent from EUT to QE1? Yes No Observations Test Description Identifier: TD_COR_1058_01 Summary: Discard packets if Hop Limit 1 Test Purpose: TP_COR_1059_01 Reference: RQ_COR_1059 Configuration: CF_022_I ensure
39、 that when QE1 is requested to send a packet to QE2 ETSI ETSI TS 102 517 V1.1.1 (2006-04) 9 containing Routing header Type = 0 and containing Segments Left value other than zero and containing Segments Left value not greater than the number of addresses in the Routing header and containing an even “
40、Hdr Ext Len“ value and not containing multicast address as next address to be visited or IPv6 Destination and containing IPv6 hop limit 1 and containing EUT as next routing hop then EUT sends the packet to QE2 Pre-test conditions: EUT established as the default router for QE1 Step Test Sequence Verd
41、ict Pass Fail 1 Cause QE1 to send an Echo Request with the following properties: - hop limit 1 - type 0 routing header - EUT as next routing hop - QE2 as final destination 2 Check: does the protocol monitor on link2 show that the Echo Request was sent from QE1 to QE2? Yes No Observations 4.2.1.2.2 P
42、rocess Flow Label Test Description Identifier: TD_COR_1130_01 -* NO TEST SPECIFIED *- Summary: EUT detects two packets with different hop-by-hop option contents but the same source and destination addresses and the same flow label Test Purpose: TP_COR_1130_01 Reference: RQ_COR_1130 Configuration: CF
43、_022_I with QE1 configured with a unique global unicast address and QE2 configured with a unique global unicast address and EUT configured with two unique global unicast addresses on the link connecting QE1 and EUT and, the link connecting QE2 and EUT, respectively ensure that when EUT receives two
44、packets containing QE1 as source address and QE2 as destination address and containing a same flow label and containing different hop-by-hop options then EUT sends an ICMP parameter problem message to QE1 and EUT discards the packets Observations This IOP test is practically impossible. One router c
45、annot guarantee the arrival and processing of two different packets at same time. Test Description Identifier: TD_COR_1130_02 -* NO TEST SPECIFIED *- Summary: EUT detects two packets with different routing header contents but the same source and destination addresses and the same flow label Test Pur
46、pose: TP_COR_1130_02 Reference: RQ_COR_1130 Configuration: CF_022_I with QE1 configured with a unique global unicast address and QE2 configured with a unique global unicast address and EUT configured with two unique global unicast addresses on the link connecting QE1 and EUT and, the link connecting
47、 QE2 and EUT, respectively ensure that when EUT receives two packets containing QE1 as source address and QE2 as destination address and containing a same flow label and containing different hop-by-hop options ETSI ETSI TS 102 517 V1.1.1 (2006-04) 10then EUT sends an ICMP parameter problem message t
48、o QE1 and EUT discards the packets Observations This IOP test is practically impossible. One router cannot guarantee the arrival and processing of two different packets at same time. 4.2.1.3 Extension Headers 4.2.1.3.1 Process Extension Headers Test Description Identifier: TD_COR_1004_01 Summary: EU
49、T does NOT process (modify) a Routing Header contained in a packet NOT destined for the EUT Test Purpose: TP_COR_1004_01 Reference: RQ_COR_1004 Configuration: CF_031_I with QE1 configured with a unique non link-local unicast address and QE2 configured as a router with a unique non link-local unicast address and QE3 configured with a unique non link-local unicast address a
