ETSI TR 102 235-2003 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) Pre-normative Study for IPv6 Testing (V1 1 1)《测试方法和规范(MTS) 互联网协议测试(IPT) IPv6测试的先期规范_1.pdf

《ETSI TR 102 235-2003 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) Pre-normative Study for IPv6 Testing (V1 1 1)《测试方法和规范(MTS) 互联网协议测试(IPT) IPv6测试的先期规范_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 102 235-2003 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) Pre-normative Study for IPv6 Testing (V1 1 1)《测试方法和规范(MTS) 互联网协议测试(IPT) IPv6测试的先期规范_1.pdf（62页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 102 235 V1.1.1 (2003-07)Technical Report Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT);Pre-normative Study for IPv6 TestingETSI ETSI TR 102 235 V1.1.1 (2003-07) 2 Reference DTR/MTS-00083 Keywords IP, methodology, testing ETSI 650 Route des Lucioles F-06921 Soph

2、ia 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: http:/www.etsi.org Th

3、e 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 the printing on ETSI pr

4、inters 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 at http:/portal.etsi.org

5、/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunicat

6、ions Standards Institute 2003. 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 being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI register

7、ed for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 235 V1.1.1 (2003-07) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 7 2 References 7 3 Abbreviations .10 4 Void11 5 Needs and aims of the EC for IPv6 11 5.1 Introduction 11 5.2 EC

8、policy11 5.3 EC IPv6 priorities.12 5.4 eEurope 2005 guidance 13 5.5 How testing supports these needs and aims13 6 Potential users of TC-MTS IPv6 test specifications.15 6.1 IPv6 Task Force Label Committee.15 6.1.1 Introduction.15 6.1.2 Proposed ETSI Support of the Logo Programme .16 6.2 3GPP 16 6.3 E

9、TSI Technical Bodies and members 17 6.4 ETSI PlugtestsTMservice17 6.5 The IETF 17 6.6 SMEs and other European interests17 7 IPv6 Areas of Interest for testing .18 8 The IETF and testing18 8.1 Introduction 18 8.2 Optional requirements 18 8.3 The Internet draft-test suite cycle .19 9 Elements of IPv6

10、test specifications.19 9.1 Types of test specifications 19 9.2 Minimum sets of requirements.20 9.3 Test methods and architecture 20 9.4 Test Purposes (TPs)21 9.4.1 Feasibility of test purpose compilation and synthesis.21 9.5 Test Suites (TSs) 22 9.6 Implementation Conformance Statements (ICS)22 9.7

11、IPv6 test specification toolkit .22 9.8 Option selection switches.23 10 Proposed work packages for each Area of Interest 23 10.1 Introduction 23 10.2 The minimum set of documents .24 10.3 Task development and analysis 26 11 WP0: The IPv6 test specification toolkit package27 11.1 Test methodologies.2

12、7 11.1.1 Methodologies for conformance and interoperability testing .27 11.1.2 Integration with current 3GPP test suites27 11.1.3 Scheduling the production of test specifications.27 11.2 Toolkit components27 11.3 Identification of tasks and resource estimate28 ETSI ETSI TR 102 235 V1.1.1 (2003-07) 4

13、 12 WP1: The Core package.28 12.1 Introduction 28 12.2 The minimum set of documents .29 12.3 Identification of tasks and resource estimate29 13 WP2: The Transition package 30 13.1 Introduction 30 13.2 The minimum set of documents .31 13.3 Identification of tasks and resource estimate32 14 WP3: The M

14、obility package.32 14.1 Introduction 32 14.2 The minimum set of documents .33 14.3 Identification of tasks and resource estimate33 15 WP4: The IPSec package .34 15.1 Introduction 34 15.2 The minimum set of documents .34 15.3 Identification of tasks and resource estimate34 16 WP5: The QoS package .35

15、 16.1 Introduction 35 16.2 The minimum set of documents .36 16.3 Identification of tasks and resource estimate36 17 WP6: The Routing package37 17.1 Introduction 37 17.2 The minimum set of documents .37 17.3 Identification of tasks and resource estimate38 18 WP7: The Multicast package .40 18.1 Introd

16、uction 40 18.2 The minimum set of documents .40 18.3 Identification of tasks and resource estimate40 19 Resources and funding .41 19.1 Roll-up of resources .41 19.2 Dependencies .41 19.3 Funding 42 Annex A: Informational tables43 Annex B: Patterns59 Annex C: Bibliography61 History 62 ETSI ETSI TR 10

17、2 235 V1.1.1 (2003-07) 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-members, and can be found in ETSI SR 000 31

18、4: “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 to the ETSI IPR Policy,

19、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. Foreword This Technica

20、l Report (TR) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). Introduction The main objective of the present document is to investigate the need for and the scope of conformance and interoperability test specifications to support the European Commissions IP

21、v6 deployment goals, the IPv6 Forums “IPv6 Ready“ certification programme and ETSIs own needs for IPv6 testing (including 3GPP). Effective testing of IPv6 products will be one of the key factors in ensuring the deployment, interoperability, security and reliability of the IPv6 infrastructure on whic

22、h the success of e-Government, e-Business, e-Health, e-Learning and e-Procurement will eventually depend. The complexity of implementing IPv6 technology means that rigorous testing is absolutely necessary, especially in the context of NGN, convergence and wireless communications. This fact is alread

23、y recognized by the IPv6 Forum who have set up an ambitious testing and certification scheme known as “IPv6 Ready“ as part of their strategy for fast deployment of IPv6. North American and Japanese testing activities are well represented in the IPv6 Forum and there is a good case for promoting a str

24、ong European representation in the “IPv6 Ready“ programme. ETSI participation by providing formal test specifications would be welcomed and encouraged by the Forum. The present document has two main technical goals: 1) to contribute to making the IPv6 testing process more flexible, efficient and cos

25、t-effective by the development of an IPv6 test suite development kit based on TTCN-3; 2) to identify the priorities and Areas of Interest for testing; 3) to propose work packages that can be used as a basis for making proposals for STFs to perform the work identified in the present document. The pre

26、sent document is structured as follows: needs and aims of the European Commission for IPv6, with a focus on eEurope 2005 and testing (see clause 5); identification and discussion on the potential users of the test specifications recommended by the present document (see clause 6); identification of t

27、he major Areas of Interest for IPv6 test specifications (see clause 7); discussion of the IETF approach to testing (see clause 8); ETSI ETSI TR 102 235 V1.1.1 (2003-07) 6 description of the test specification components with an emphasis on minimum requirements and the toolkit approach recommended by

28、 the present document (see clause 9); details of Work Packages for each Area of Interest (see clauses 10 to 18); informational tables summarizing the necessary IETF RFCs, 3GPP IPv6-related documents and existing IPv6 test specifications (see annex A). ETSI ETSI TR 102 235 V1.1.1 (2003-07) 7 1 Scope

29、The present document defines the scope of an IPv6 test specification programme that supports the “IPv6 Ready“ certification programme, the European Commissions IPv6 deployment goals and priorities, and ETSIs own needs for IPv6 testing. Analyses, justifications, and supporting documentation are inclu

30、ded. The testing programme is closely associated with the eEurope 2005 action plan. This plan asks the European standardization organizations to propose a 3-year work plan (for 2003, 2004, and 2005) to support new priorities, some of which concern IPv6 testing. Thus, the testing programme is compose

31、d of short and medium-term plans (from 2003 through 2005) using resources from eEurope 2005 and ETSI members voluntary and funded contributions. The present document also contains proposals to request 2003 funding via the eEurope 2005 action plan. 2 References For the purposes of this Technical Repo

32、rt (TR), the following references apply: 1 COM(2002)96: “Next Generation Internet - priorities for action in migrating to the new Internet protocol IPv6“. 2 COM(2002)263: “eEurope 2005: An information society for all“. 3 IETF RFC 791: “Internet Protocol“. 4 IETF RFC 1006: “iso transport services on

33、top of the tcp: version 3“. 5 IETF RFC 1058: “Routing Information Protocol“, C.L. Hedrick, June1988. 6 IETF RFC 1771: “A Border Gateway Protocol 4 (BGP-4)“. 7 IETF RFC 1809: “Using the Flow Label Field in IPv6“, C. Partridge, June 1995. 8 IETF RFC 1886: “DNS Extensions to support IP version 6“, S. T

34、homson, C. Huitema, December 1995, PROPOSED STANDARD. 9 IETF RFC 1981: “Path MTU Discovery for IP version 6“, J. McCann, S. Deering, J. Mogul, August 1996. 10 IETF RFC 1990: “The PPP Multilink Protocol (MP)“. 11 IETF RFC 2026: “The Internet Standards Process - Revision 3“, S. Bradner, October 1996.

35、12 IETF RFC 2119: “Key words for use in RFCs to Indicate Requirement Levels“, S. Bradner, March 1997. 13 IETF RFC 2080: “RIPng for IPv6“, G. Malkin, R. Minnear, January 1997. 14 IETF RFC 2126: “ISO Transport Service on top of TCP (ITOT)“. 15 IETF RFC 2328: “OSPF Version 2“, J. Moy, April 1998, STAND

36、ARD. 16 IETF RFC 2373: “IP Version 6 Addressing Architecture“, R. Hinden, S. Deering, July 1998. 17 IETF RFC 2401: “Security Architecture for the Internet Protocol“, S. Kent, R. Atkinson, November 1998. 18 IETF RFC 2402: “IP Authentication Header“, S. Kent, R. Atkinson, November 1998. 19 IETF RFC 24

37、03: “The Use of HMAC-MD5-96 within ESP and AH“, C. Madson, R. Glenn, November 1998. 20 IETF RFC 2404: “The Use of HMAC-SHA-1-96 within ESP and AH“, C. Madson, R. Glenn, November 1998. ETSI ETSI TR 102 235 V1.1.1 (2003-07) 8 21 IETF RFC 2405: “The ESP DES-CBC Cipher Algorithm With Explicit IV“, C. Ma

38、dson, N. Doraswamy, November 1998. 22 IETF RFC 2406: “IP Encapsulating Security Payload (ESP)“, S. Kent, R. Atkinson, November 1998. 23 IETF RFC 2408: “Internet Security Association and Key Management Protocol (ISAKMP)“. 24 IETF RFC 2409: “The Internet Key Exchange (IKE)“. 25 IETF RFC 2410: “The NUL

39、L Encryption Algorithm and Its Use With IPSec“, R. Glenn, S. Kent, November 1998. 26 IETF RFC 2412: “The OAKLEY Key Determination Protocol“. 27 IETF RFC 2453: “RIP Version 2“, November 1998. 28 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6) Specification“, S. Deering, R. Hinden, December 1998.

40、29 IETF RFC 2461: “Neighbor Discovery for IP Version 6 (IPv6)“, T. Narten, E. Nordmark, W. Simpson, December 1998. 30 IETF RFC 2462: “IPv6 Stateless Address Autoconfiguration“, S. Thomson, T. Narten, December 1998. 31 IETF RFC 2463: “Internet Control Message Protocol (ICMPv6) for the Internet Protoc

41、ol Version 6 (IPv6) Specification“, A. Conta, S. Deering, December 1998. 32 IETF RFC 2472: “IP Version 6 over PPP“. 33 IETF RFC 2473: “Generic Packet Tunneling in IPv6 Specification“, A. Conta, S. Deering, December 1998. 34 IETF RFC 2474: “Definition of the Differentiated Services Field (DS Field) i

42、n the IPv4 and IPv6 Headers“, K. Nichols, S. Blake, F. Baker, D. Black, December 1998. 35 IETF RFC 2475: “An Architecture for Differentiated Services“, S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss, December 1998. 36 IETF RFC 2507: “IP Header Compression“. 37 IETF RFC 2508: “Compressi

43、ng IP/UDP/RTP Headers for Low-Speed Serial Links“. 38 IETF RFC 2509: “IP Header Compression over PPP“. 39 IETF RFC 2529: “Transmission of IPv6 over IPv4 Domains without Explicit Tunnels“, B. Carpenter, C Jung, March 1999. 40 IETF RFC 2545: “Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain

44、 Routing“, P. Marques, F. Dupont, March 1999. 41 IETF RFC 2597: “Assured Forwarding PHB Group“, J. Heinanen, F. Baker, W. Weiss, J. Wroclawski, June 1999. 42 IETF RFC 2598: “An Expedited Forwarding PHB“, V. Jacobson, K. Nichols, K. Poduri, June 1999. 43 IETF RFC 2641: “Cabletrons VlanHello Protocol

45、Specification Version 4“. 44 IETF RFC 2642: “Cabletrons VLS Protocol Specification“. 45 IETF RFC 2675: “IPv6 Jumbograms“, D. Borman, S. Deering, R. Hinden, August 1999. 46 IETF RFC 2686: “The Multi-Class Extension to Multi-Link PPP“. ETSI ETSI TR 102 235 V1.1.1 (2003-07) 9 47 IETF RFC 2710: “Multica

46、st Listener Discovery (MLD) for IPv6“, S. Deering, W. Fenner, B. Haberman, October 1999. 48 IETF RFC 2711: “IPv6 Router Alert Option“, C. Partridge, A. Jackson, October 1999. 49 IETF RFC 2740: “OSPF for IPv6“, R. Coltun, D. Ferguson, J. Moy, December1999. 50 IETF RFC 2765: “Stateless IP/ICMP Transla

47、tion Algorithm (SIIT)“, E. Nordmark, February 2000. 51 IETF RFC 2766: “Network Address Translation - Protocol Translation (NAT-PT)“, G. Tsirtsis, P. Srisuresh, February 2000. 52 IETF RFC 2767: “Dual Stack Hosts using the Bump-In-the-Stack Technique (BIS)“, K. Tsuchiya, H. Higuchi, Y. Atarashi, Febru

48、ary 2000. 53 IETF RFC 2858: “Multiprotocol Extensions for BGP-4“, T. Bates, Y. Rekhter, R. Chandra, D. Katz, June 2000. 54 IETF RFC 2865: “Remote Authentication Dial In User Service (RADIUS)“. 55 IETF RFC 2874: “DNS Extensions to Support IPv6 Address Aggregation and Renumbering“, M. Crawford, C. Hui

49、tema, July 2000. 56 IETF RFC 2893: “Transition Mechanisms for IPv6 Hosts and Routers“, R. Gilligan, E. Nordmark, August 2000. 57 IETF RFC 3041: “Privacy Extensions for Stateless Address Autoconfiguration in IPv6“. 58 IETF RFC 3053: “IPv6 Tunnel Broker“, A. Durand, P. Fasano, I. Guardini, D. Lento, January 2001. 59 IETF RFC 3056: “Connection of IPv6 Domains via IPv4 Clouds“, B. Carpenter, K. Moore, February 2001. 60 IETF RFC 3095: “RObust H