1、 ETSI TS 102 517 V2.0.1 (2008-01)Technical Specification Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT): IPv6 Core Protocol;Interoperability Test Suite (ITS)ETSI ETSI TS 102 517 V2.0.1 (2008-01) 2 Reference RTS/MTS-IPT-0072-IPv6-CorITS 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 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of i
7、ts 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 V2.0.1 (2008-01) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 3 Abbreviations .7 4 IPv6 Core
8、Interoperability Test Specification7 4.1 Introduction 7 4.2 Test Descriptions8 4.2.1 Group 1 RFC 24608 4.2.1.1 Group 1.2 Process IPv6 Packet .8 4.2.1.1.1 Group 1.2.4 Process IPv6 Header8 4.2.1.1.2 Group 1.2.6 Process Flow Label .10 4.2.1.2 Group 1.4 Extension Headers11 4.2.1.2.1 Group 1.4.2 Process
9、Extension Headers11 4.2.1.2.2 Group 1.4.4 Routing Header13 4.2.1.2.3 Group 1.4.5 Fragment Header .15 4.2.2 Group 2 RFC 246117 4.2.2.1 Group 2.1 Generate Neighbor Discovery Messages .17 4.2.2.1.1 Group 2.1.5 Generate Router Advertisement 17 4.2.2.1.2 Group 2.1.6 Generate Router Solicitation .24 4.2.2
10、.1.3 Group 2.1.7 Generate Neighbor Advertisement 24 4.2.2.1.4 Group 2.1.8 Generate Redirect Message .25 4.2.2.2 Group 2.2 Process Neighbor Discovery Messages26 4.2.2.2.1 Group 2.2.5 Process Router Advertisement.26 4.2.2.2.2 Group 2.2.6 Process Router Solicitation31 4.2.2.2.3 Group 2.2.7 Process Neig
11、hbor Advertisement 35 4.2.2.2.4 Group 2.2.8 Process Neighbor Solicitation .35 4.2.2.3 Group 2.5 Next Hop Determination37 4.2.2.4 Group 2.6 Neighbor Uneachability Detection.38 4.2.2.4.1 Group 2.6.6 Neighbor Reachability Determination.38 4.2.2.5 Group 2.7 Address Resolution 39 4.2.2.5.1 Group 2.7.1 In
12、terface Initialization .41 4.2.3 Group 3 RFC 246244 4.2.3.1 Group 3.1 Initialize .44 4.2.3.1.1 Group 3.1.1 Configure Address.44 4.2.4 Group 4 RFC 246349 4.2.4.1 Group 4.1 ICMPv6 Functions .49 4.2.4.1.1 Group 4.1.1 Determine ICMPv6 Message Source Address 49 4.2.4.1.2 Group 4.1.2 ICMPv6 Error Messages
13、 .51 4.2.4.1.3 Group 4.1.3 Information Messages .54 4.2.5 Group 5 RFC 351355 4.2.5.1 Group 5.2 Address Architecture55 4.2.5.2 Group 5.5 Unicast Addresses58 4.2.5.2.1 Group 5.5.6 Link Local Unicast Addresses.59 4.2.5.3 Group 5.6 Anycast Addresses .60 4.2.5.4 Group 5.7 Multicast Addresses .60 4.2.5.4.
14、1 Group 5.7.1 Pre-defined Multicast Addresses .60 4.2.5.4.2 Group 5.7.2 Node 61 4.2.6 Group 6 RFC 198162 4.2.6.1 Group 6.1 Discover PMTU.62 4.2.6.1.1 Group 6.1.1 Multicast PMTU Discovery 64 4.2.7 Group 7 RFC 267565 ETSI ETSI TS 102 517 V2.0.1 (2008-01) 4 Annex A (informative): IPv6 Interoperability
15、Test Purposes 67 Annex B (informative): Interoperability Testing Configurations103 History 106 ETSI ETSI TS 102 517 V2.0.1 (2008-01) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these esse
16、ntial IPRs, if any, is publicly available for ETSI members and non-members, 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 update
17、s 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 IPRs not referenced in ETSI SR 000 314 (or the updates on the E
18、TSI 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 102 517 V2.0.1 (2008-01) 6 1 Scope The present document specifies
19、 the interoperability Test Descriptions (TDs) with integrated Test Purposes (TPs) for the IPv6 Core standards. The TDs are presented in the tabular form specified in TS 102 424 1 and the TPs are defined using the TPLan notation also described in TS 102 424 1. The Test Suite Structure is based on the
20、 IETF RFCs which, together, form the IPv6 Core specification and is reflected in the use of “Group/End Group“ statements in the TPLan code presented in annex A. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. Fo
21、r a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the refer
22、ring document; - 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. For online referenced documents, information sufficient to identify and locate the source shall be provided. Pref
23、erably, 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 expected life of the document. The reference shall include the method of access to the referenced document and the full
24、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 cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensa
25、ble 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 (including any amendments) applies. 1 ETSI TS 102 424 (2005): “Telecommunications and Internet converged Services and Prot
26、ocols for Advanced Networking (TISPAN); Requirements of the NGN network to support Emergency Communication from Citizen to Authority“. 2 IETF RFC 1981: “Path MTU Discovery for IP version 6“. 3 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6) Specification“. 4 IETF RFC 2461: “Neighbor Discovery fo
27、r 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: “Internet Protocol Version 6 (IPv6) Addres
28、sing Architecture“. ETSI ETSI TS 102 517 V2.0.1 (2008-01) 7 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
29、 RouTer SL Site Local TP Test Purpose TD Test Description TPLan Test Purpose Language TSS Test Suite Structure 4 IPv6 Core Interoperability Test Specification 4.1 Introduction The IPv6 Core Interoperability Test Descriptions (TDs) defined in the following clauses are derived from the Test Purposes (
30、TPs) specified in annex A. ETSI ETSI TS 102 517 V2.0.1 (2008-01) 8 4.2 Test Descriptions 4.2.1 Group 1 RFC 2460 4.2.1.1 Group 1.2 Process IPv6 Packet 4.2.1.1.1 Group 1.2.4 Process IPv6 Header 4.2.1.1.1.1 Group 1.2.4.4 Process Hop Limit Test Description Identifier: TD_COR_1002_01 Test Purpose: TP_COR
31、_1002_01 Summary: EUT decreases the Hop Limit field of a traversed IPv6 packet and forwards it Roles: Router Configuration: CF_CORE_22 References: RQ_000_1002 with QE1 configured with a unique global unicast address and QE2 configured with a unique global unicast address and EUT configured with two
32、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 1 then EUT sends the packet with the Hop Limit decreme
33、nted to QE2 Pre-test conditions: EUT established as the default router for QE1 Verdict Step Test SequencePass 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 monitor on link2 show that the Echo Request was sent from Q
34、E1 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 Test Purpose: TP_COR_1002_02 Summary: EUT drops a traversed IPv6 packets with a zero Hop Limit and returns an ICMP error message to the s
35、ource Roles: Router Configuration: CF_CORE_22 References: RQ_000_1002 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 on the link conne
36、cting 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 = 0 then EUT discards the packet and EUT sends an ICMP error message to QE1 Pre-test conditions: EUT established as the default router for Q
37、E1 Verdict Step Test Sequence 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 QE2? No Yes 3 Check: Does the protocol monitor on link1 show that an ICMP
38、error message was sent from EUT to QE1? Yes No Observations: ETSI ETSI TS 102 517 V2.0.1 (2008-01) 9 Test Description Identifier: TD_COR_1058_01 Test Purpose: TP_COR_1058_01 Summary: Discard packets if Hop Limit 1 Roles: Host, Router Configuration: CF_CORE_22 References: RQ_000_1058 ensure that when
39、 QE1 is requested to send a packet to QE2 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 “Hdr Ext Len“ value and not containing multicast ad
40、dress 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 ICMP “Time Exceeded“ error message to QE1 and EUT discards the packet Pre-test conditions: EUT established as the default router for QE1 Verdict Step Test Seq
41、uencePass 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? No Yes 3 Check: Does the prot
42、ocol monitor on link1 show that an ICMP Time Exceeded error message was sent from EUT to QE1? Yes No Observations: A QE cannot send out any message with hop limit = 0, thus hop limit = 1 is chosen for this test. Test Description Identifier: TD_COR_1059_01 Test Purpose: TP_COR_1059_01 Summary: Proces
43、s packets if Hop Limit 1 Roles: Host, Router Configuration: CF_CORE_22 References: RQ_000_1059 ensure that when QE1 is requested to send a packet to QE2 containing Routing header Type = 0 and containing Segments Left value other than zero and containing Segments Left value not greater than the numbe
44、r of addresses in the Routing header and containing an even “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 esta
45、blished as the default router for QE1 Verdict Step Test Sequence 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 Requ
46、est was sent from QE1 to QE2? Yes No Observations: ETSI ETSI TS 102 517 V2.0.1 (2008-01) 104.2.1.1.2 Group 1.2.6 Process Flow Label Test Description Identifier: TD_COR_1130_01 Test Purpose: TP_COR_1130_01 Summary: EUT detects two packets with different hop-by-hop option contents but the same source
47、and destination addresses and the same flow label Roles: Host, Router Configuration: CF_CORE_22 References: RQ_000_1130 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
48、link connecting QE1 and EUT and, the link connecting 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 then EUT sends an ICMP parameter probl
49、em message to QE1 and EUT discards the packets Pre-test conditions: Verdict Step Test SequencePass Fail Observations: This IOP test is practically impossible. One router cannot guarantee the arrival and processing of two different packets at same time. Test Description Identifier: TD_COR_1130_02 Test Purpose: TP_COR_1130_02 Summary: EUT detects two packets with different routing header co
