ETSI TS 102 369-2004 Methods for Testing and Specification (MTS) Stream Control Transmission Protocol (SCTP) Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)《测试方法和规范(MTS) 流.pdf

《ETSI TS 102 369-2004 Methods for Testing and Specification (MTS) Stream Control Transmission Protocol (SCTP) Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)《测试方法和规范(MTS) 流.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 369-2004 Methods for Testing and Specification (MTS) Stream Control Transmission Protocol (SCTP) Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)《测试方法和规范(MTS) 流.pdf（35页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 369 V1.1.1 (2004-11)Technical Specification Methods for Testing and Specification (MTS);Stream Control Transmission Protocol (SCTP);Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available fr

2、om 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 IPRs not referenced in ET

3、SI 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 102 369 V1.1.1 (2004-11) 5

4、1 Scope The present document proposes a Test Suite Structure and Test Purposes (TSS MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP); Stream Control Transmission Protocol (SCTP) Endorsement of RFC2960 and RFC3309, modified“. 6 draft-ietf-tsvwg-sctpimpguide-10.txt (November 2003): “Stream Contro

5、l Transmission Protocol (SCTP) Implementers Guide“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in RFC 2960 1, ISO/IEC 9646-1 2, ISO/IEC 9646-2 3, ISO/IEC 9646-3 4 and the following apply: inopportune: tests that handle in

6、valid signalling exchanges of messages EXAMPLE: Signalling messages that are properly structured and correctly encoded but are used out of sequence. invalid: tests that handle valid signalling exchanges of messages, which are either not properly structured or incorrectly encoded SCTP Endpoint: logic

7、al sender/receiver of SCTP packets ETSI ETSI TS 102 369 V1.1.1 (2004-11) 6 test purpose: non-formal high-level description of a test, mainly using text NOTE: This test description can be used as the basis for a formal test specification (e.g. Abstract Test Suite in TTCN). See ISO/IEC 9646-23. valid:

8、 tests that handle valid signalling exchanges of messages, which are properly structured and correctly encoded 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: A Acknowledgement AS Association SetupAT Association Termination BDC Bundling of Data Chunks w

9、ith control chunks D Data DM Duplicate Message E Error FH Fault Handling I Invalid behaviour IMH Invalid Message Handling IUT Implementation Under Test M Miscellaneous test cases MAC Message Authentication Code MSB Most Significant Bit MTU Maximum Transmission Unit O inOpportune behaviour RT Retrans

10、mission Timer RTO Retransmission Time-Out rwnd receiver windowSCTP Stream Control Transmission Protocol SUT System Under Test TCB Transmission Control Block TLV Type-Length-Value coding format TP Test Purposes TSN Transmission Sequence Number TSS Test Suite Structure V Valid behaviour 4 Test Suite S

11、tructure (TSS) 4.1 Introduction 4.1.1 SCTP Endpoints Test purposes have been written for SCTP Endpoints according to the TS 102 144 5. The architectural view on an SCTP association is presented in figure 1. ETSI ETSI TS 102 369 V1.1.1 (2004-11) 7 SCTP User Application SCTP Transport Service IP Netwo

12、rk Service Data Link and Physical Layer SCTP Node A SCTP Node B SCTP User Application SCTP Transport Service IP Network Service Data Link and Physical Layer One or more IP address appearances One or more IP address appearances Figure 1: SCTP architectural view 4.1.2 General assumptions Test purposes

13、 have been written for behaviours requested with “MUST“ or that appear as obvious in present form. In addition test purposes have been defined for implementation dependent behaviour, where at least one of the implementation options is mandatory. Test purposes have been written for behaviours request

14、ed with “MUST“ or that appear as obvious in present form for the following functions provided by SCTP: Association startup and takedown. Sequenced delivery within streams. User data fragmentation. Acknowledgement and congestion avoidance. Chunk bundling. Packet validation. Path management. The verb

15、“discards“ in test purpose means that the IUT does not react with an error message and does not take into account the element to be discarded. 4.1.3 System Under Test (SUT) The System Under Test (SUT) is defined as an SCTP Endpoint with an SCTP user. The term IUT (Implementation Under Test) refers t

16、o the SCTP transport entity that resides within the SUT. 4.2 Overview of the Test Suite Structure (TSS) The Test Suite Structure (TSS) is based on the main functionalities as defined 4.1.3. Figure 2 shows the Test Suite Structure (TSS). Last subgroups may be subdivided in three subgroups: Valid beha

17、viour (V), Invalid behaviour (I), inOpportune behaviour (O). ETSI ETSI TS 102 369 V1.1.1 (2004-11) 8 Test suite Main functionalities Test group Association Setup V-I-O Association Termination V Invalid Message Handling I Duplicate Message O Fault Handling V-I-O Error I-O Bundling of Data Chunks with

18、 control chunks V-I Data V-I-O Acknowledgement V-OMiscellaneous test cases I SCTP Retransmission Timer I Figure 2: TSS for SCTP 5 Test Purposes (TP) 5.1 Introduction 5.1.1 TP naming convention Table 1: TP identifier naming convention scheme Identifier: _ SCTP Association Setup (AS), Association Term

19、ination (AT), Invalid Message Handling (IMH), Duplicate Message (DM) Fault Handling (FH), Error (E), Bundling of Data Chunks with control chunks (BDC), Data (D), Acknowledgement (A), Miscellaneous test cases (M) Retransmission Timer (RT). Valid behaviour (V), Invalid behaviour (I), inOpportune behav

20、iour (O). sequential number (01-99). (optional) sequential number (01-99). 5.1.2 TP structure Each test purpose is decomposed in five keywords: The “TPId“ gives a unique identifier to each test purpose. The “Status“ specifies whether the test purpose or the group is mandatory or optional according t

21、o RFC 2960 1. The group status applies to all test purposes belonging to this group. Within the current version of this document only test purposes that are mandatory have been defined. The “Precondition“ determines the initial state of the SUT for the evaluating the test purpose. The “Ref“ outlines

22、 the references in RFC 2960 1 used to create the test purpose. The “Purpose“ describes the objective of the test. ETSI ETSI TS 102 369 V1.1.1 (2004-11) 9 5.2 Test Purposes (TP) for Association Setup (AS) 5.2.1 Valid, invalid and inopportune behaviour TPId: SCTP_AS_V_1_1_1 Status: Mandatory Precondit

23、ion: Association is not established between tester and SUT. Configure the IUT to send an INIT to the tester. Ref: RFC 2960 1, sections 5.1 and 5.1.6. Purpose: Ensure that the IUT makes a complete association procedure. TPId: SCTP_AS_V_1_1_2 Status: Mandatory Precondition: Association is not establis

24、hed between tester and SUT. Arrange the data at the tester such that INIT is sent to IUT. Ref: RFC 2960 1, sections 5.1 and 5.1.6. Purpose: Ensure that the IUT can establish a complete association after receiving an INIT from the tester. TPId: SCTP_AS_I_1_2_1 Status: Mandatory Precondition: Associat

25、ion is not established between tester and SUT. Configure the SUT to send an INIT to the tester. Arrange the data at the tester such that INIT-ACK is not sent in response to INIT message. Ref: RFC 2960 1, sections 4 and 5.1.6. Purpose: Ensure that the IUT, if T1-Init timer expires, transmits the INIT

26、 message again. TPId: SCTP_AS_I_1_2_2 Status: Mandatory Precondition: Association is not established between tester and SUT. Configure the SUT to send an INIT to the tester. Arrange the data at the tester such that COOKIE-ACK is not sent in response to COOKIE-ECHO message. Ref: RFC 2960 1, sections

27、4 and 5.1.6. Purpose: Ensure that the IUT, if T1-Cookie timer expires, transmits the COOKIE-ECHO message again. TPId: SCTP_AS _I_1_3_1 Status: Mandatory Precondition: Association is not established between tester and SUT. Configure the SUT to send an INIT to the tester. Arrange the data at the teste

28、r such that INIT-ACK is never sent in response to INIT message. Ref: RFC 2960 1, section 4 (note 2). Purpose: Ensure that the IUT, if INIT is retransmitted for MAX.INIT.RETRANS times, stops the initialization process. ETSI ETSI TS 102 369 V1.1.1 (2004-11) 10TPId: SCTP_AS_I_1_3_2 Status: Mandatory Pr

29、econdition: Association not established between tester and SUT. Configure the SUT to send an INIT to the tester. Arrange the data at the tester such that COOKIE-ACK is never sent in response to COOKIE-ECHO message. Ref: RFC 2960 1, section 4 (note 3) and section 5.1.6. Purpose: Ensure that the IUT,

30、if COOKIE-ECHO message is retransmitted for MAX.INIT.RETRANS times, stops the initialization process. TPId: SCTP_AS _I_1_4 Status: Mandatory Precondition: Association not established between tester and SUT. Arrange the data at the tester such that COOKIE-ECHO is not sent in response to INIT-ACK mess

31、age. Also let maximum no of association which SUT can establish is n and n-1 of them are already established. Try to make the nth association. Ref: RFC 2960 1, section 5.1 B (note). Purpose: Ensure that the IUT remains in closed state if COOKIE-ECHO message is not received. TPId: SCTP _AS _V_1_5_1 S

32、tatus: Mandatory Precondition: Association is not established between tester and SUT. Arrange the data at the tester such that normal association can be established and terminated between tester and SUT. Ref: RFC 2960 1, section 5.3.1. Purpose: Ensure that the IUT on re-establishing an association t

33、o a peer, uses a random Initiate-Tag value in the INIT message. TPId: SCTP _AS _V_1_5_2 Status: Mandatory Precondition: Association is not established between tester and SUT. Arrange the data at the tester such that normal association can be established and terminated between tester and SUT. Ref: RF

34、C 2960 1, section 5.3.1. Purpose: Ensure that the IUT on re-establishing an association to a peer, uses a random Initiate-Tag value in the INIT-ACK message. TPId: SCTP _AS _V_1_6_1 Status: Optional Precondition: Association is not established between tester and SUT. Arrange the data at the tester su

35、ch that the listed parameters (Ipv4 Address Parameter, IPv6 Address Parameter, CookiePreservative, Supported Address Type Parameter) are sent in INIT message. Ref: RFC 2960 1, section 3.3.2 and TS 102 144 5, section 4.6. Purpose: Ensure that the IUT on receipt of an INIT message with the listed para

36、meters accepts this message and responds to it. ETSI ETSI TS 102 369 V1.1.1 (2004-11) 11TPId: SCTP _AS _V_1_6_2 Status: Optional Precondition: Association is not established between tester and SUT. Arrange the data at the tester such that the list parameters (Ipv4 Address Parameter, IPv6 Address Par

37、ameter, CookiePreservative) are sent in INIT-ACK message. Ref: RFC 2960 1, section 3.3.3 and TS 102 144 5, section 4.6. Purpose: Ensure that the IUT on receipt of an INIT-ACK message with the listed parameters accepts this message and responds to it. TPId: SCTP_AS _V_1_7_1 Status: Mandatory Precondi

38、tion: Association is not established between tester and SUT. Also let the OutboundStreams of the SUT is Z. Arrange data at the tester such that INIT message is sent from tester with MaximumInboundStreams YZ. Ref: RFC 2960 1, section 5.1.1. Purpose: Ensure that the IUT, if there is a mismatch in the

39、Outbound Stream and Inbound Stream parameters in INIT and INIT-ACK message, either aborts the association or settles with minimum of the two parameters. TPId: SCTP_AS _I_1_7_2 Status: Mandatory Precondition: Association is not established between tester and SUT. Arrange data at the tester such that

40、INIT message with OutboundStreams equal to 0 is sent from tester. Ref: RFC 2960 1, section 3.3.2. Purpose: Ensure that the IUT, if OutboundStreams are found zero in the received INIT message, sends an ABORT message for that INIT. or silently discards the received message. TPId: SCTP_AS _V_1_7_3 Stat

41、us: Mandatory Precondition: Association is not established between tester and SUT. Also let the OutboundStreams of the SUT is Z. Arrange data at the tester such that INIT-ACK message is sent from tester with MaximumInboundStreams XZ. Ref: RFC 2960 1, section 5.1.1. Purpose: Ensure that the IUT, if t

42、here is a mismatch in the Outbound Stream and Inbound Stream parameters in INIT and INIT-ACK message, either aborts the association or settles with minimum of the two parameters. TPId: SCTP_AS _I_1_7_4 Status: Mandatory Precondition: Association is not established between tester and SUT. Also let th

43、e OutboundStreams of the SUT is Z. Arrange data at the tester such that INIT-ACK message with OutboundStreams equal to 0 is sent from tester. Ref: RFC 2960 1, section 3.3.3. Purpose: Ensure that the IUT, if OutboundStreams is found zero in the received INIT-ACK message, destroys its TCB and may send

44、 an ABORTmessage for that INIT-ACK. Further message exchanges between tester and IUT need to take place to verify the TCB removal from outside the SUT. ETSI ETSI TS 102 369 V1.1.1 (2004-11) 12TPId: SCTP_AS _V_1_7_5 Status: Mandatory Precondition: Association is not established between tester and SUT

45、. Arrange data at the tester such that INIT message is sent from tester with OutboundStreams and MaximumInboundStreams set to 2. Ref: TS 102 144 5, section 4.2. Purpose: Ensure that the IUT supports at least 2 incoming streams and 2 outgoing streams. TPId: SCTP_AS _I_1_8_1 Status: Mandatory Precondi

46、tion: Association is not established between tester and SUT. Arrange data at the tester such that a datagram with undefined parameter type and MSB two bits in the parameter type equal to 11 is sent to tester. Ref: RFC 2960 1, section 3.3.3.1. Purpose: Ensure that the IUT on receipt of unrecognized T

47、LV parameters in received INIT message fills them in the Unrecognized Parameters of the INIT-ACK and continues on processing of further parameters. TPId: SCTP_AS _I_1_8_2 Status: Mandatory Precondition: Association is not established between tester and SUT. Arrange data at the tester such that a dat

48、agram with undefined parameter type and MSB two bits in the parameter type equal to 00 is sent to the IUT. Ref: RFC 2960 1, section 3.3.3.1. Purpose: Ensure that the IUT on receipt of an unrecognized parameter in the INIT-chunk does not process any further parameters and does not report it. TPId: SC

49、TP_AS _I_1_8_3 Status: Mandatory Precondition: Association is not established between tester and SUT. Arrange data at the tester such that a datagram with undefined parameter type and MSB two bits in the parameter type equal to 01 is sent to the IUT. Ref: RFC 2960 1, section 3.3.3.1. Purpose: Ensure that the IUT on receipt of an unrecognized parameter in the INIT-chunk does not process any further parameters and report it using an Unrecognized Parameters field. TPId: SCTP_AS _I_1_8_4 Status: Mandatory Pr