ETSI TS 186 002-1 V1.1.4 (2008-05)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 1: Protocol Implementation Conformance Statement (PICS)

RTS/TISPAN-06028-1-NGN

General Information

• Status: Published
• Publication Date: 20-May-2008
• Technical Committee: TISPAN 6 - TISPAN Testing
• Current Stage: 12 - Completion
• Due Date: 28-May-2008
• Completion Date: 21-May-2008

Standards Content (Sample)

ETSI TS 186 002-1 V1.1.4 (2008-05)
Technical Specification

Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control Protocol (BICC) or
ISDN User Part (ISUP);
Part 1: Protocol Implementation Conformance
Statement (PICS)

---------------------- Page: 1 ----------------------
2 ETSI TS 186 002-1 V1.1.4 (2008-05)



Reference
RTS/TISPAN-06028-1-NGN
Keywords
BICC, interworking, ISUP, PICS, SIP, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document 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 dispute, 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 ETSI 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 written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 186 002-1 V1.1.4 (2008-05)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
2.1 Normative references.5
2.2 Informative references.6
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.7
4 Scenarios.8
4.1 SIP Profile A and B for interworking between SIP and BICC/ISUP .8
4.2 SIP Profile C for Interworking Between SIP with MIME Encoding of ISUP and BICC/ISUP.9
5 PICS proforma.11
5.1 Instructions for completing the PICS proforma.11
5.1.1 Other information.11
5.1.2 Purposes and structure .11
5.1.3 Conventions .12
5.2 Identification of the implementation .13
5.2.1 Date of the statement .13
5.2.2 Implementation Under Test (IUT) identification.13
5.2.3 System Under Test (SUT) identification .13
5.2.4 Product supplier.13
5.2.5 Client.13
5.2.6 PICS contact person.14
5.3 PICS proforma tables .14
5.3.1 Global statement of conformance .14
5.3.2 Roles.14
5.3.3 Connection types.14
5.3.4 Forward address signalling .15
5.3.5 Role independent capabilities .15
5.3.6 Supplementary Services Major Capabilities .16
5.3.7 Timers.19
5.4 Additional information for PICS .19
Annex A (informative): Bibliography.20
History .22

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 186 002-1 V1.1.4 (2008-05)
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 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 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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 1 of a multi-part deliverable covering the Telecommunications and Internet converged
Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP)
and Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP), as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP) for Profile A and B";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) for Profile C";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
for Profile A and B";
Part 5: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
for Profile C".
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 186 002-1 V1.1.4 (2008-05)
1 Scope
The present document specifies the network PICS (Protocol Implementation Conformance Statement) of the
Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or
ISDN User Part.
2 References
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.
• 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 referring 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. Preferably,
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 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 indispensable 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] ITU-T Recommendations Q.761 to Q.764 (1999): "Signalling System No.7 ISDN User Part".
[2] ITU-T Recommendations Q.1902.1 to Q.1902.4 (2001): "Bearer Independent Call Control
Protocol (BICC)".
[3] ITU-T Recommendation Q.731.7 (1997): "Stage 3 description for number identification
supplementary services using Signalling System No. 7: Malicious call identification (MCID)".
[4] ITU-T Recommendation Q.732.2 (1999): "Stage 3 description for call offering supplementary
services using Signalling System No. 7: Call diversion services - Call Forwarding Busy (CFB)".
[5] ITU-T Recommendation Q.732.7 (1996): "Stage 3 description for call offering supplementary
services using Signalling System No. 7: Explicit Call Transfer".
[6] ITU-T Recommendation Q.737.1 (1997): "Stage 3 description for additional information transfer
supplementary services using Signalling System No. 7: User-to-user signalling (UUS)".
[7] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol".
[8] IETF RFC 3262 (2002): "Reliability of Provisional Responses in the Session Initiation Protocol
(SIP)".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 186 002-1 V1.1.4 (2008-05)
[9] ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statements".
[10] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T
Recommendation Q.1912.5, modified]".
[11] ITU-T Recommendation Q.1912.5 (03/2004): "Interworking between Session Initiation Protocol
(SIP) and Bearer Independent Call Control or ISDN User Part".
[12] ITU-T Recommendation E.164 (2005): "The international public telecommunication numbering
plan".
[13] IETF RFC 768 (1980): "User Datagram Protocol".
[14] IETF RFC 761 (1980): "DoD standard Transmission Control Protocol".
[15] ITU-T Recommendation Q.767 (1991): "Application of the ISDN user part of CCITT signalling
system No. 7 for international ISDN interconnections".
[16] ITU-T Recommendation Q.731.1 (1996): "Stage 3 description for number identification
supplementary services using Signalling System No. 7: Direct-dialling-In (DDI)".
[17] ITU-T Recommendation Q.731.5 (1993): "Stage 3 description for number identification
supplementary services using Signalling System No. 7: Connected line identification presentation
(COLP)".
[18] ITU-T Recommendation Q.118 (1997): "Abnormal conditions - Special release arrangements".
[19] ITU-T Technical Report TRQ.2815 / Q.Sup45 (2003): "Requirements for interworking
BICC/ISUP network with originating/destination networks based on Session Initiation Protocol
and Session Description Protocol".
[20] ITU-T Recommendation Q.1902.4: "Bearer Independent Call Control protocol (Capability Set 2):
Basic call procedures".
[21] IETF RFC 3267: "Real-Time Transport Protocol (RTP) Payload Format and File Storage Format
for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio
Codecs".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test
purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and
ending in a stable testing state
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 186 002-1 V1.1.4 (2008-05)
Abstract Test Method (ATM): description of how an SUT is to be tested, given at an appropriate level of abstraction
to make the description independent of any particular realization of a Means of Testing, but with enough detail to
enable abstract test cases to be specified for this method
Abstract Test Suite (ATS): test suite composed of abstract test cases
Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider
relationship, being part of a real open system which is to be studied by testing
Means of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection,
parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a
conformance log
PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes the PICS
PIXIT proforma: document, in the form of a questionnaire, which when completed for the SUT becomes the PIXIT
Point of Control and Observation (PCO): point within a testing environment where the occurrence of test events is to
be controlled and observed, as defined in an Abstract Test Method
Pre-test condition: setting or state in the SUT which cannot be achieved by providing stimulus from the test
environment
Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to
conform to a given specification, stating which capabilities have been implemented
Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of
an SUT (protocol) which contains or references all of the information related to the SUT and its testing environment,
which will enable the test laboratory to run an appropriate test suite against the SUT
SIP number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [12]
System Under Test (SUT): real open system in which the SUT resides
User: access protocol entity at the User side of the user-network interface where a T reference point or coincident S and
T reference point applies
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATC Abstract Test Case
ATM Abstract Test Method
ATS Abstract Test Suite
BICC Bearer Independent Call Control protocol
CIC Circuit Identification Code
ICS Implementation Conformance Statement
ISDN Integrated Services Digital Network
ISUP ISDN User Part
IUT Implementation Under Test
MOT Means Of Testing
PCO Point of Control and Observation
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
SIP Session Initiation Protocol
SUT System Under Test
TP Test Purpose
TSS & TP Test Suite Structure and Test Purposes
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 186 002-1 V1.1.4 (2008-05)
4 Scenarios
4.1 SIP Profile A and B for interworking between SIP and
BICC/ISUP
Profile
scope
G/W Type 1
SIP
BICC or
SIP
ISUP
Proxy
IP
IP, ATM or
TDM

Figure 1: Profile Scope for SIP Interworking with BICC/ISUP with a Type 1 Gateway
Profile
G/W Type 2 SN
scope
SIP BICC
BICC or
SIP
CSF-T
ISUP
Proxy
IP
IP, ATM or
TDM

Figure 2: Profile Scope for SIP Interworking with BICC/ISUP with a Type 2 Gateway
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 186 002-1 V1.1.4 (2008-05)
4.2 SIP Profile C for Interworking Between SIP with MIME
Encoding of ISUP and BICC/ISUP
Profile
G/W Type 3 G/W Type 3
scope
BICC or SIP with MIME encoding of ISUP BICC or
ISUP ISUP
IP IP
IP, ATM or IP, ATM or
TDM TDM

Figure 3: Profile Scope for SIP with MIME encoding of ISUP Interworking with BICC/ISUP
with Type 3 Gateways
Profile
SN G/W Type 4 G/W Type 3
scope
BICC
BICC or SIP with MIME encoding BICC or
ISUP of ISUP ISUP
CSF-T
IP IP
IP, ATM or IP, ATM or
TDM TDM

Figure 4: Profile Scope for SIP, with MIME Encoding of ISUP, Interworking with BICC/ISUP
with Type 3 & 4 Gateways
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 186 002-1 V1.1.4 (2008-05)

Profile
G/W Type 3
scope

SIP SIP with MIME encoding of ISUP BICC or
ISUP
Proxy*

IP
IP, ATM or
TDM

Figure 5: Profile Scope for SIP with MIME encoding of ISUP Interworking with BICC/ISUP
with Type 3 Gateways

Profile
SN
scope
G/W Type 4
SIP (with MIME encoding of
ISUP)
BICC
BICC or
SIP CSF-T
ISUP
Proxy
IP
IP, ATM or
TDM

Figure 6: Profile Scope for SIP, with MIME Encoding of ISUP, Interworking with BICC/ISUP
with Type 4 Gateway
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 186 002-1 V1.1.4 (2008-05)
NNI
Profile scope
G/W Type 3
SIP with MIME encoding of ISUP
BICC
SIP
Proxy*
IP
IP or ATM

Figure 7: Profile for SIP, with MIME Encoding of ISUP, Interworking with BICC/ISUP
with Type 3 Gateway
5 PICS proforma
5.1 Instructions for completing the PICS proforma
5.1.1 Other information
More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the
supplier may provide additional comments separately in clause 5.4.
5.1.2 Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in reference specification [1] to [10] may provide information about the implementation in a
standardized manner.
The PICS proforma is subdivided into clauses for the following categories of information:
• instructions for completing the PICS proforma;
• identification of the implementation;
• identification of the reference protocol specification;
• PICS proforma tables (containing the global statement of conformance).
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 186 002-1 V1.1.4 (2008-05)
5.1.3 Conventions
The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in
ISO/IEC 9646-7 [9].
Item column
It contains a number that identifies the item in the table.
Item description column
It describes each respective item (e.g. parameters, timers, etc.).
Reference column
It gives reference to the specification(s) [1] to [10], except where explicitly stated otherwise.
Status column
The following notations, defined in ISO/IEC 9646-7 [9], are used for the status column:
m mandatory - the capability is required to be supported.
n/a not applicable - in the given context, it is impossible to use the capability. No answer in the support column is
required.
o optional - the capability may be supported or not.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a
unique group of related optional items and the logic of their selection which is defined immediately following
the table.
ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or
conditional items. "i" is an integer identifying a unique conditional status expression that is defined
immediately following the table. For nested conditional expressions, the syntax "IF . THEN
(IF . THEN . ELSE.) ELSE ." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE
n/a" shall be implied.
NOTE: Support of a capability means that the capability is implemented in conformance to the
specification(s) [1] to [10].
Support column
The support column shall be filled in by the supplier of the implementation. The following common notations, defined
in ISO/IEC 9646-7 [9], are used for the support column:
• Y or y supported by the implementation.
• N or n not supported by the implementation.
• N/A or n/a or "no answer required" (allowed only if the status is N/A, directly or after evaluation
of a conditional status).
Values allowed column
This column contains the values or the ranges of values allowed.
Values supported column
The support column shall be filled in by the supplier of the implementation. In this column the values or the ranges of
values supported by the implementation shall be indicated.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 186 002-1 V1.1.4 (2008-05)
References to items
For each possible item answer (answer in the support column) within the PICS proforma, a unique reference exists. It is
defined as the table identifier, followed by a slash character "/", followed by the item number in the table. If there is
more than one support column in a table, the columns shall be discriminated by letters (a, b, etc.) respectively.
EXAMPLE: 5/4 is the reference to the answer of item 4 in table 5.
5.2 Identification of the implementation
Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test
(SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration
options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the ICS should be named as the contact person.
5.2.1 Date of the statement
Date of the statement:

5.2.2 Implementation Under Test (IUT) identification
IUT name:
IUT version:

5.2.3 System Under Test (SUT) identification
SUT name:
Hardware configuration:
Operating system:

5.2.4 Product supplier
Name:
Address:
Telephone number:
Facsimile number:
Additional information:

5.2.5 Client
Name:
Address:
Telephone number:
Facsimile number:
Additional information:

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 186 002-1 V1.1.4 (2008-05)
5.2.6 PICS contact person
Name:
Telephone number:
Facsimile number:
Additional information:

5.3 PICS proforma tables
5.3.1 Global statement of conformance

(Yes/No)
Are all mandatory capabilities implemented?

NOTE: Answering "No" to this question indicates non-conformance to the reference protocol specification.
Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the
implementation is non-conforming.
5.3.2 Roles
Table 1: Roles
Item Is the implementation . Reference Status Support
1 Profile A? ITU-T TRQ.2815 [19] o.11
2
Profile B? ITU-T TRQ.2815 [19] o.11
3
Profile C? ITU-T TRQ.2815 [19] o.11
4
connected with a BICC Network? ITU-T Q.1902.2 [2] o.12
5 connected with a ISUP Network? ITU-T Q.764 [1] o.12
6 connected with a µ-law network? Clauses 6.1 and 7.1 of o
ITU-T TRQ.2815 [19]
7 an outgoing international exchange? ITU-T Rec Q.764 [1] o
8 an incoming international exchange? ITU-T Rec Q.764 [1] o
9 an implementation according EN 383 001 [10] o
EN 383 001 [[10]?
NOTE: o.11: It is mandatory to support at least one of these items.
o.12: It is mandatory to support one of these items.

5.3.3 Connection types
Table 2: Connection types
Item Is the exchange able to . Reference Status Support
1 support the media type "audio" and Clauses 6.1.3.5.1 and 7.1.1.1 of o.21
media format 0, 8? ITU-T Rec Q.1912.5 [11]
2 support the media type "audio" and Clauses 6.1.3.5.1 and 7.1.1.1 of o.21
media format 9? ITU-T Rec Q.1912.5 [11]
3 support the media type "audio" and Clauses 6.1.3.5.1 and 7.1.1.1 of o.21
attribute value CLEARMODE? ITU-T Rec Q.1912.5 [11]
4 support the media type "image" and Clauses 6.1.3.5.1 and 7.1.1.1 of o.21
media format t38? ITU-T Rec Q.1912.5 [11]
5 support the dynamic assignment for Clauses 6.1.3.5.1 and 7.1.1.1 of o.21
codec? ITU-T Rec Q.1912.5 [11]
6
use the transport protocol udptl? RFC 768 [13] o
7
use the transport protocol tcptl? RFC 761 [14] o
8 Support the transcoding of the AMR IETF RFC 3267 [21] o
codec to G.711 PCM
NOTE: o.21: It is mandatory to support at least one of these items.

ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 186 002-1 V1.1.4 (2008-05)
5.3.4 Forward address signalling
Table 3: Forward address signalling
Item Is the exchange [role] able to . Reference Status Support
1 SIP use the en bloc operation in the Clause 7.1 of o.31
forward address signalling (sending)? ITU-T Rec Q.1912.5 [11]
2
SIP use the overlap operation in the Clause 7.1 of o.31
forward address signalling (sending)? ITU-T Rec Q.1912.5 [11]
3 SIP support the en bloc operation in the Clause 6.1 of o
forward address signalling (receiving)? ITU-T Rec Q.1912.5 [11]
4
SIP support the overlap operation in the Clause 6.1 of o
forward address signalling (receiving)? ITU-T Rec Q.1912.5 [11]
5 ISUP use the en bloc operation in the Clause 6.1 of o.32
forward address signalling (sending)? ITU-T Rec Q.1912.5 [11]
6 ISUP use the overlap operation in the Clause 6.1 of o.32
forward address signalling (sending)? ITU-T Rec Q.1912.5 [11]
7 ISUP support the en bloc operation in the Clause 7.1 of o
forward address signalling (receiving)? ITU-T Rec Q.1912.5 [11]
8 ISUP support the overlap operation in the Clause 7.1 of o
forward address signalling (receiving)? ITU-T Rec Q.1912.5 [11]
NOTE: o.31: It is mandatory to support at least one of these items.
o.32: It is mandatory to support one of these items.

5.3.5 Role independent capabilities
Table 4: Role independent capabilities
Item Is the exchange able to . Reference Status Support
1 use the Continuity check procedures Clause 6.1.2 of o
during call setup? ITU-T Rec Q.1912.5 [11]
2
support the Continuity check procedures Clause 2.1.8 of ITU-T Rec Q.764 [1]; m
during call setup? clauses 7.2 and 7.3 of
ITU-T Rec Q.1902.4 [20]
3 support hop counter procedure? Clauses 6.1.3.9 and 7.1.4 of c41
EN 383 001 [10]
4 support internal resource reservations Clause 6.1.2 2 of EN 383 001 [10] o
(preconditions used)?
5 support the reliability of provisional RFC 3262 [8] o
responses?
6 perform the automatic repeat attempt? Clause 2.8
...