1、 ETSI TS 102 514 V1.1.1 (2006-04)Technical Specification Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT);IPv6 Core Protocol; Requirements CatalogueETSI ETSI TS 102 514 V1.1.1 (2006-04) 2 Reference DTS/MTS-IPT-003-IPv6-CoreReqCa Keywords IP, IPv6, testing ETSI 650 Route de
2、s 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 document can be downloaded from
3、: 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 dispute, the reference shall be
4、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 ETSI documents is available a
5、t 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 written permission. The copyrig
6、ht 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 are Trade Marks currently bei
7、ng 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 514 V1.1.1 (2006-04) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Abbreviations .
8、6 4 Requirements Catalogue.6 4.1 Requirements extracted from TS 123 0606 4.2 Requirements extracted from TS 123 2218 4.3 Requirements extracted from TS 123 2288 4.4 Requirements extracted from TS 129 0618 4.5 Requirements extracted from RFC 198120 4.6 Requirements extracted from RFC 246043 4.7 Requi
9、rements extracted from RFC 246177 4.8 Requirements extracted from RFC 2462238 4.9 Requirements extracted from RFC 2463271 4.10 Requirements extracted from RFC 2464294 4.11 Requirements extracted from RFC 2675298 4.12 Requirements extracted from RFC 3513305 Annex A (informative): Bibliography.341 His
10、tory 342 ETSI ETSI TS 102 514 V1.1.1 (2006-04) 4 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-members, and can be
11、 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.asp). Pursuant
12、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 present document
13、. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI TS 102 514 V1.1.1 (2006-04) 5 1 Scope The purpose of the present document is to provide a catalogue of requirements extracted from the core IPv6 RFCs (see
14、 references in clause 2) and from ETSI Specifications. The catalogue follows the guidelines defined by the MTS IPv6 Testing: Methodology and Framework (see TS 102 351 in bibliography). 2 References The following documents contain provisions which, through reference in this text, constitute provision
15、s of the present document. References are either specific (identified by date of publication 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
16、 not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 IETF RFC 1122: “Requirements for Internet Hosts - Communication Layers“. 2 IETF RFC 1981: “Path MTU Discovery for IP version 6“. 3 IETF RFC 2373: “IP Version 6 Addressing Architecture“.
17、4 IETF RFC 2402: “IP Authentication Header“. 5 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6) Specification“. 6 IETF RFC 2461: “Neighbor Discovery for IP Version 6 (IPv6)“. 7 IETF RFC 2462: “IPv6 Stateless Address Autoconfiguration“. 8 IETF RFC 2463: “Internet Control Message Protocol (ICMPv6)
18、for the Internet Protocol Version 6 (IPv6) Specification“. 9 IETF RFC 2464: “Transmission of IPv6 Packets over Ethernet Networks“. 10 IETF RFC 2675: “IPv6 Jumbograms“. 11 IETF RFC 3513: “ Internet Protocol Version 6 (IPv6) Addressing Architecture“. 12 ETSI TS 123 060: “Digital cellular telecommunica
19、tions system (Phase 2+); Universal Mobile Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service description; Stage 2 (3GPP 23.060)“. 13 ETSI TS 123 221: “ Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Architectural
20、requirements (3GPP 23.221)“. 14 ETSI TS 123 228: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP 23.228)“. 15 ETSI TS 129 061: “Digital cellular telecommunications system (Phase 2+); Universal Mob
21、ile Telecommunications System (UMTS); Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) (TS 129 061)“. ETSI ETSI TS 102 514 V1.1.1 (2006-04) 6 3 Abbreviations For the purposes of the present document, the following abbreviation
22、s apply: CIDR Common InterDomain Routing ICMP Internet Control Message Protocol IE Information Element MTU Maximum Transmission Unit ND Neighbor Discovery PDP Packet Data Protocol PMTU Path MTU TCP Transfer Control Protocol UDP User Datagram Protocol 4 Requirements Catalogue The requirements below h
23、ave been extracted from IETF RFCs 1981 2, 2460 5, 2461 6, 2462 7, 2463 8, 2464 9, 2675 10, 351311), and ETSI specifications TS 123 060 12, TS 123 221 13, TS 123 228 14, TS 129061 15). 4.1 Requirements extracted from TS 123 060 RQ_COR_7003 Configure Address TS 123 060 Clause: 9.2.1.1 5 Type: MUST app
24、lies to: Host Context: Implementation has started PDP context activation session. Requirement: Implementation obtains interface identifier from GGSN prior to performing stateless or stateful address autoconfiguration. RFC text: To ensure that the link-local address generated by the MS does not colli
25、de with the link-local address of the GGSN, the GGSN shall provide an interface identifier (see RFC 2462) to the MS and the MS shall use this interface identifier to configure its link-local address. This is applicable for both stateful and stateless IPv6 address autoconfiguration. RQ_COR_7004 Detec
26、t Duplicate Address TS 123 060 Clause: 9.2.1.1 10 Type: MAY applies to: Host Context: Implementation is performing stateless address autoconfiguration. The prefix that the router (GGSN) advertises in a PDP context is unique within the scope of the prefix (i.e. global). Requirement: Implementation do
27、es not perform duplicate address detection. RFC text: Because any prefix that the GGSN advertises in a PDP context is unique within the scope of the prefix (i.e. site-local or global), there is no need for the MS to perform Duplicate Address Detection for this IPv6 address. ETSI ETSI TS 102 514 V1.1
28、.1 (2006-04) 7 RQ_COR_7005 Detect Duplicate Address TS 123 060 Clause: 9.2.1.1 10 Type: MUST applies to: Router Context: Implementation (GGSN) advertises prefixes in a PDP context that are unique (i.e. global). The implementation receives Neighbor Solicitation messages for Duplicate Address Detectio
29、n. Requirement: Implementation silently discards the Neighbor Solicitation messages. RFC text: Because any prefix that the GGSN advertises in a PDP context is unique within the scope of the prefix (i.e. site-local or global), there is no need for the MS to perform Duplicate Address Detection for thi
30、s IPv6 address. Therefore, the GGSN shall silently discard Neighbor Solicitation messages that the MS may send to perform Duplicate Address Detection. . RQ_COR_7006 Stateless Autoconfiguration TS 123 060 Clause: 9.2.1.1 10 Type: MUST applies to: Router Context: The implementation is activating PDP c
31、ontexts for IPv6. Requirement: Implementation does not advertise the same prefix on more than one PDP context on a given APN or set of APNs, within the same addressing scope. RFC text: A given prefix shall not be advertised on more than one PDP context on a given APN or set of APNs within the same a
32、ddressing scope. . RQ_COR_7007 Stateless Autoconfiguration TS 123 060 Clause: 9.2.1.1 10 Type: MUST applies to: Host Context: Implementation has received a Router Advertisement message which contains more than one prefix. Requirement: The implementation uses the first prefix and silently discards th
33、e others. RFC text: After the MS has received the Router Advertisement message, it constructs its full IPv6 address by concatenating the interface identifier received in step 3, or a locally generated interface identifier, and the prefix received in the Router Advertisement. RQ_COR_7009 Router Adver
34、tisement Behavior TS 123 060 Clause: 9.2.1.1 2 Type: MUST applies to: Router Context: Implementation (GGSN) has activated a PDP context of type IPv6. Requirement: The implementation sends automatic and periodic router advertisement messages towards the node (MS). RFC text: The GGSN informs the MS th
35、at it shall perform stateful address autoconfiguration by means of the Router Advertisements, as defined in RFC 2461. For this purpose, the GGSN shall automatically and periodically send Router Advertisement messages towards the MS after a PDP context of type IPv6 is activated. ETSI ETSI TS 102 514
36、V1.1.1 (2006-04) 8 4.2 Requirements extracted from TS 123 221 RQ_COR_7010 3GPP UE supports IPv6 TS 123 221 Clause: 5.6 2 Type: MUST applies to: Host Context: 3GPP UE supports IPv6 Requirement: The implementation complies with the Basic IP group of specifications as defined in RFC 3316. RFC text: The
37、 set of IPv6 functionality a 3GPP UE will require is dependent on the services (IMS, Packet Streaming etc.) it will use. As a minimum, a 3GPP UE shall comply with the Basic IP group of specifications as defined in RFC 3316 . This IPv6 functional is sufficient to provide compatibility towards IPv6 en
38、tities external to 3GPP. 4.3 Requirements extracted from TS 123 228 RQ_COR_7060 Configure Address TS 123 228 Clause: 4.3.1 Type: MAY applies to: Host Context: Implementation is assigned an IPv6 prefix. Requirement: Implementation changes its global IPv6 address currently in use via the mechanism def
39、ined in RFC 3041 or similar means. RFC text: According to the procedures defined in TS 123 060 , when a UE is assigned an IPv6 prefix, it can change the global IPv6 address it is currently using via the mechanism defined in RFC 3041, or similar means. 4.4 Requirements extracted from TS 129 061 RQ_CO
40、R_7000 Configure Address TS 129 061 Clause: 11.2.1.3 4-5 Type: MUST applies to: Host Context: The implementation is capable of both stateless and stateful autoconfiguration and receives a Router Advertisement indicating both stateless and stateful autoconfiguration capabilities. Requirement: The imp
41、lementation uses stateless to configure the address and stateful to configure additional parameters. RFC text: Stateful and Stateless Autoconfiguration may also co-exist. In that case, the MS shall use Stateless to configure the address and stateful to configure additional parameters only. The selec
42、tion between Stateful and Stateless Autoconfiguration is dictated by the Router Advertisements sent by the GGSN as described in the corresponding subclauses below and according to the principles defined in RFC 2461 and RFC 2462. RQ_COR_7001 Configure Address TS 129 061 Clause: 11.2.1.3 4 Type: MUST
43、applies to: Host Context: The implementation is capable of both stateless and stateful autoconfiguration and router advertise both stateless and stateful autoconfiguration. Requirement: The implementation does not use both stateless and stateful autoconfiguration simultaneously. RFC text: The MS sha
44、ll not use Stateless and Stateful Address Autoconfiguration simultaneously since GPRS only supports one prefix per PDP Context. ETSI ETSI TS 102 514 V1.1.1 (2006-04) 9 RQ_COR_7002 Configure Address TS 129 061 Clause: 11.2.1.3 5 Type: MUST applies to: Host Context: The implementation does not support
45、 optional stateful autoconfiguration and router advertises both stateful and stateless autoconfiguration. Requirement: The implementation uses stateless autoconfiguration only. RFC text: For MS, IPv6 Stateless Address Autoconfiguration is mandatory, and IPv6 Stateful Address Autoconfiguration is opt
46、ional. RQ_COR_7008 Router Advertisement Behavior TS 129 061 Clause: 11.2.1.3.2 Type: MAY applies to: Router Context: Implementation (GGSN) is sending Router Advertisements. Requirement: The implementation omits random sending of the Advertisements. RFC text: The handling of Router Advertisements sha
47、ll be consistent with what is specified in RFC 2461 . For the MS-GGSN link however, some specific handling shall apply. The randomisation part to determine when Router Advertisements shall be sent may be omitted since the GGSN is the only router on the link. RQ_COR_7012 MaxRtrAdvInterval TS 129 061
48、Clause: 11.2.1.3.4 Type: MUST applies to: Router Context: The implementation is being configured for operation and MaxRtrAdvInterval is left at the default 3GPP value. Requirement: The implementation uses the default value of 21,600s (6 hours) for MaxRtrAdvInterval. RFC text: RFC 2461 specifies a se
49、t of conceptual router configuration variables. Some of these variables require particular attention in GPRS in order to preserve radio resources and MS power consumption while still allowing for appropriate robustness and fast use. RQ_COR_7013 MinRtrAdvInterval TS 129 061 Clause: 11.2.1.3.4 Type: MUST applies to: Router Context: The implementation is being configured for operation and MinRtrAdvInterval is left at the default 3GPP value. Requirement: The imple
