SIST ETS 300 479-2 E1:2003

• Abstract:

  PICS proforma for ETS 300 479-1

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.040.40 - Data communication networks
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 479-2 ed.1 (1998-02) - Network Aspects (NA); Connectionless Broadband Data Service (CBDS) over Asynchronous Transfer Mode (ATM); Protocol specification at the Network Node Interface (NNI) specification; Part 2: Connectionless Network Interface Protocol (CLNIP) Protocol Implementation Conformance Statement (PICS) proforma specification

SIST ETS 300 479-2 E1:2003 is the Slovenian adoption of ETS 300 479-2 Edition 1 from ETSI. It defines the Protocol Implementation Conformance Statement (PICS) proforma for the Connectionless Network Interface Protocol (CLNIP) used for Connectionless Broadband Data Service (CBDS) over Asynchronous Transfer Mode (ATM) at the Network Node Interface (NNI), so suppliers can state which capabilities an implementation supports.

What does SIST ETS 300 479-2 E1:2003 specify?

SIST ETS 300 479-2 E1:2003 specifies the PICS proforma for CLNIP defined in ETS 300 479-1. In practice, it gives a standard questionnaire for describing an implementation's conformance in a way that can be checked against the protocol specification.

The document is organized into four main clauses and one normative annex:

• Clause 1 gives the scope.
• Clause 2 lists the normative references.
• Clause 3 provides definitions and abbreviations.
• Clause 4 sets the conformance rule for the ICS proforma.
• Annex A contains the normative PICS proforma itself, with guidance and the item tables to complete.

Annex A is the working part of the document. It covers how to fill in the statement, how to identify the implementation and system under test, how to record protocol identification, and how to declare supported CLNIP capabilities and transmission features.

What are the key requirements of SIST ETS 300 479-2 E1:2003?

Completing the proforma

SIST ETS 300 479-2 E1:2003 requires the supplier to complete every space in the ICS proforma and to enter an explicit answer in each support field. Clause A.1.3 says additional comments may be added separately if needed.

This matters because the document is not just a description of CLNIP - it is a fill-in form that becomes the formal conformance statement for a specific implementation.

How conformance is declared

SIST ETS 300 479-2 E1:2003 requires the completed ICS proforma to follow the instructions in Annex A and to remain technically equivalent to the annex text. Clause 4 also requires the numbering, naming, and ordering of the proforma items to be preserved.

That makes the form comparable across suppliers and test reports. If the layout or item order changes, the statement is no longer conforming to this proforma.

What the support notation means

SIST ETS 300 479-2 E1:2003 uses the status and support conventions in Annex A to distinguish mandatory, optional, prohibited, not applicable, and conditional items. The same annex explains that the support column is where the supplier records whether each item is supported, not supported, or not applicable.

For a reader, this means the form does not just ask "yes or no" in a general sense - it records support item by item, so an evaluator can see exactly which CLNIP features are implemented.

What counts as support for a PDU or parameter

SIST ETS 300 479-2 E1:2003 states in Annex A that supporting a Protocol Data Unit (PDU) means being able to parse all valid parameters of that PDU. It also says that support for a parameter on a PDU means the semantics of that parameter are supported.

This is important for conformance work. An implementation cannot claim support for a PDU if it cannot correctly process one of its valid parameters.

The mandatory capability summary

SIST ETS 300 479-2 E1:2003 summarizes the main implementation capabilities in Table A.1. These include sending and receiving CLNIP PDU, support for encapsulating CLNIP, support for non-encapsulating CLNIP, and support of bilaterally agreed PI values.

For practical use, Table A.1 is the first checkpoint. It tells the supplier and the tester which broad functions must be claimed before the detailed field-by-field tables are completed.

The two CLNIP PDU forms

SIST ETS 300 479-2 E1:2003 distinguishes between a non-encapsulating CLNIP PDU and an encapsulating CLNIP PDU in Tables A.2 to A.9. The non-encapsulating form includes fields such as Destination Address, Source Address, PI, PAD Length, QOS, CIB, HEL, Reserved, Header Extension, User Information, PAD, and CRC. The encapsulating form has a similar structure but omits the PAD and CRC fields.

This distinction matters because implementers must declare which form they send and receive, and testers must verify the correct fields and field behavior for each form.

Address field and parameter details

SIST ETS 300 479-2 E1:2003 gives separate tables for address fields and parameter values. The address-type and address subfields are shown for both Destination Address and Source Address, and the address content is linked to ETS 300 478-1. The tables also set out the supported values for fields such as PI, PAD Length, QOS, CIB, HEL, and the Header Extension.

In practice, these tables are the detailed checklist for interoperability. They tell the supplier exactly what must be declared and what must be tested for each field.

What terms does SIST ETS 300 479-2 E1:2003 define?

• Implementation Conformance Statement (ICS) - a statement from the supplier describing which capabilities of an implementation are implemented.
• ICS proforma - a questionnaire-style document that becomes an ICS when it is completed for a specific implementation or system.
• Protocol Implementation Conformance Statement (PICS) - an ICS for an implementation or system claimed to conform to a given protocol specification.
• Implementation Under Test (IUT) - the implementation whose conformance is being described and assessed.
• System Under Test (SUT) - the system that contains the IUT and is identified in the statement.
• Connectionless Network Interface Protocol (CLNIP) - the protocol covered by this PICS proforma.
• Protocol Data Unit (PDU) - the protocol message unit whose fields and parameters are listed in the annex tables.

Who uses SIST ETS 300 479-2 E1:2003?

SIST ETS 300 479-2 E1:2003 is used by suppliers of CLNIP implementations, conformance test teams, and people preparing implementation statements for telecommunication equipment. It is also useful for system integrators and quality or compliance staff who need to document what a product supports against ETS 300 479-1.

In practice, the document is filled in by the product supplier, identified for a specific IUT and SUT, and used by whoever needs a structured record of protocol support for CBDS over ATM at the NNI.

Which standards are used with SIST ETS 300 479-2 E1:2003?

• ETS 300 479-1 - defines the CLNIP protocol that this PICS proforma describes.
• ETS 300 406 - gives the standardization methodology for protocol and profile conformance testing.
• ISO/IEC 9646-1 - provides the general concepts for conformance testing methodology and framework.
• ISO/IEC 9646-7 - gives the rules for Implementation Conformance Statements and their proformas.
• ETS 300 478-1 - supplies the related UNI framework and protocol specification referenced for address field coding and related parameter handling.

What does the SIST ETS 300 479-2 E1:2003 document contain?

SIST ETS 300 479-2 E1:2003 contains a questionnaire-style proforma in Annex A, plus guidance on how to complete it. The annex includes identification fields for the statement date, IUT, SUT, supplier, client, and ICS contact person.

It also contains a global conformance question, a major capabilities table, and detailed transmission capability tables for non-encapsulating and encapsulating CLNIP PDUs. Those tables are the practical core of the document because they are used to record support for PDU fields, parameter values, and direction-specific behavior.

The annex further explains the status codes, support entries, conditional expressions, and item references used in the tables. That makes it suitable for conformance recording, test preparation, and supplier declarations based on ETS 300 479-1.

SLOVENSKI STANDARD
01-december-2003
2PUHåQLYLGLNL1$±1HSRYH]DYQDãLURNRSDVRYQDSRGDWNRYQDVWRULWHY&%'6]
DVLQKURQLPSUHQRVQLPQDþLQRP$70±6SHFLILNDFLMDSURWRNRODQDYPHVQLNX
RPUHåQHJDYR]OLãþD11,±GHO3URWRNROQHSRYH]DYQHJDRPUHåQHJDYPHVQLND
&/1,3±,]MDYDRVNODGQRVWLL]YHGEHSURWRNROD3,&6±3URIRUPDVSHFLILNDFLMD
Network Aspects (NA); Connectionless Broadband Data Service (CBDS) over
Asynchronous Transfer Mode (ATM); Protocol specification at the Network Node
Interface (NNI) specification; Part 2: Connectionless Network Interface Protocol (CLNIP)
Protocol Implementation Conformance Statement (PICS) proforma specification
Ta slovenski standard je istoveten z: ETS 300 479-2 Edition 1
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 479-2
TELECOMMUNICATION February 1998
STANDARD
Source: NA Reference: DE/NA-053210
ICS: 33.020
Key words: ATM, Broadband, CBDS, CL, NNI, PICS
Network Aspects (NA);
Connectionless Broadband Data Service (CBDS)
over Asynchronous Transfer Mode (ATM);
Protocol specification at the Network Node Interface (NNI);
Part 2: Connectionless Network Interface Protocol (CLNIP)
Protocol Implementation Conformance Statement (PICS)
proforma specification
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
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 1998. All rights reserved.

Page 2
ETS 300 479-2: February 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 479-2: February 1998
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Conformance to this ICS proforma specification.8
Annex A (normative): PICS proforma for ETS 300 479 .9
A.1 Guidance for completing the PICS proforma .9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions.9
A.1.3 Instructions for completing the ICS proforma .11
A.2 Identification of the implementation.11
A.2.1 Date of the statement .11
A.2.2 Implementation Under Test (IUT) identification .11
A.2.3 System Under Test (SUT) identification .12
A.2.4 Product supplier.12
A.2.5 Client.13
A.2.6 ICS contact person .13
A.3 Identification of the protocol .14
A.4 Global statement of conformance .14
A.5 Major capabilities.14
A.6 Transmission capabilities .15
A.6.1 The non-encapsulating CLNIP PDU .15
A.6.1.1 Fields.15
A.6.1.1.1 Address fields .16
A.6.1.2 Parameters.16
A.6.1.2.1 Parameters of the non-address fields .16
A.6.1.2.2 Parameters of the address fields.17
A.6.2 The encapsulating CLNIP PDU .17
A.6.2.1 Fields.17
A.6.2.1.1 Address fields .18
A.6.2.2 Parameters.18
A.6.2.2.1 Parameters of the non-address fields .18
A.6.2.2.2 Parameters of the address fields.19
History.20

Page 4
ETS 300 479-2: February 1998
Blank page
Page 5
ETS 300 479-2: February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Network Aspects (NA)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
The present document is part 2 of a multi-part ETS covering the protocol specification at the Network
Node Interface (NNI), for the Connectionless Broadband Data Service (CBDS) over Asynchronous
Transfer Mode (ATM), as identified below:
Part 1: "Specification";
Part 2: "Connectionless Network Interface Protocol (CLNIP) Protocol
Implementation Conformance Statement (PICS) proforma specification".
Transposition dates
Date of adoption of this ETS: 6 February 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998
Introduction
To evaluate conformance of a particular implementation, it is necessary to have a statement of which
capabilities and options have been implemented for a telecommunication specification. Such a statement
is called an Implementation Conformance Statement (ICS).

Page 6
ETS 300 479-2: February 1998
Blank page
Page 7
ETS 300 479-2: February 1998
1 Scope
This second part of ETS 300 479 provides the Implementation Conformance Statement (ICS) proforma
for the Connectionless Network Interface Protocol (CLNIP) defined in the first part of ETS 300 479-1 [1] in
compliance with the relevant requirements, and in accordance with the relevant guidance given in
ISO/IEC 9646-7 [4] and ETS 300 406 [2].
2 Normative references
This part of ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this part of ETS only when incorporated in it by amendment or revision. For undated references
the latest edition of the publication referred to applies.
[1] ETS 300 479-1 (1995): "Network Aspects (NA); Connectionless Broadband Data
Service (CBDS) over Asynchronous Transfer Mode (ATM); Protocol
specification at the Network Node Interface (NNI); Part 1: Specification".
[2] ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".
[3] ISO/IEC 9646-1 (1995): "Information technology - Open systems interconnection
- Conformance testing methodology and framework - Part 1: General concepts".
[4] ISO/IEC 9646-7 (1995): "Information technology - Open systems interconnection
- Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
[5] ETS 300 478-1: "Network Aspects (NA); Connectionless Broadband Data
Service (CBDS) over Asynchronous Transfer Mode (ATM); Framework and
protocol specification at the User-Network Interface (UNI); Part 1: Specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this part of ETS, the following definitions apply:
- terms defined in ETS 300 479-1 [1];
- terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-7 [4].
In particular, the following terms defined in ISO/IEC 9646-1 [3] apply:
Implementation Conformance Statement (ICS): A statement made by the supplier of an implementation
or system claimed to conform to a given specification, stating which capabilities have been implemented.
The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc.
ICS proforma: A document, in the form of a questionnaire, which when completed for an implementation
or system becomes an ICS.
Protocol ICS (PICS): An ICS for an implementation or system claimed to conform to a given protocol
specification.
Page 8
ETS 300 479-2: February 1998
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
CLNIP Connectionless Network Interface Protocol
ICS Implementation Conformance Statement
IUT Implementation Under Test
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
SCS System Conformance Statement
SUT System Under Test
4 Conformance to this ICS proforma specification
If it claims to conform to this ETS, the actual ICS proforma to be filled in by a supplier shall be technically
equivalent to the text of the ICS proforma in annex A, and shall preserve the numbering/naming and
ordering of the proforma items.
An ICS which conforms to this ETS shall be a conforming ICS proforma completed in accordance with the
instructions for completion given in clause A.1.

Page 9
ETS 300 479-2: February 1998
Annex A (normative): PICS proforma for ETS 300 479
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for its
intended purpose and may further publish the completed PICS.
A.1 Guidance for completing the PICS proforma
A.1.1 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 300 479-1 [1] may provide information about the implementation in a
standardized manner.
The PICS proforma is subdivided into subclauses for the following categories of information:
- instructions for completing the ICS proforma;
- identification of the implementation;
- identification of the protocol;
- global statement of conformance;
- ICS proforma tables.
A.1.2 Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with
the guidelines presented in ISO/IEC 9646-7 [4].
Item column
It contains a number which identifies the item in the table.
Item description column
It describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is description> supported by the implementation?".
Status column
The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column:
m mandatory - the capability is required to be supported;
o optional - the capability may be supported or not;
n/a not applicable - in the given context, it is impossible to use the capability;
x prohibited (excluded) - there is a requirement not to use this capability in the
given context;
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is
an integer which identifies an 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", "x" or "n/a") depends on
the support of other optional or conditional items. "i" is an integer identifying an
unique conditional status expression which is defined immediately following the
table.
Page 10
ETS 300 479-2: February 1998
Reference column
It gives reference to 300 479-1 [1], except where explicitly stated otherwise.
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 [4], are used for the support column:
Y or y supported by the implementation;
N or n not supported by the implementation;
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation
of a conditional status).
If this ICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary
to be able to answer that a capability is supported for one profile and not supported for another. In that
case, the supplier shall enter the unique reference to a conditional expression, preceded by "?" (e.g. ?3).
This expression shall be given in the space for comments provided at the bottom of the table. It uses
predicates defined in the System Conformance Statement (SCS), each of which refers to a single profile
and which takes the value TRUE if and only if that profile is to be used.
EXAMPLE: ?3: IF prof1 THEN Y ELSE N
It is possible to provide a commen
...