ISO/IEC DIS 8824-3

Information technology -- Abstract Syntax Notation One (ASN.1)

Technologies de l'information -- Notation de syntaxe abstraite numéro un (ASN.1)

Standards Content (sample)

DRAFT INTERNATIONAL STANDARD
ISO/IEC DIS 8824-3
ISO/IEC JTC 1/SC 6 Secretariat: KATS
Voting begins on: Voting terminates on:
2020-09-28 2020-12-21
Information technology — Abstract Syntax Notation One
(ASN.1) —
Part 3:
Constraint specification

Technologies de l'information — Notation de syntaxe abstraite numéro un (ASN.1) —

Partie 3: Spécification des contraintes
ICS: 35.100.60
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
This document is circulated as received from the committee secretariat.
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC DIS 8824-3:2020(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. ISO/IEC 2020
---------------------- Page: 1 ----------------------
ISO/IEC DIS 8824-3:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2020

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC DIS 8824-3:2020(E)
CONTENTS
Page

Introduction ........................................................................................................................................................... lvi

Information technology – Abstract Syntax Notation One (ASN.1): Constraint specification ........... 56

1 Scope .......................................................................................................................................................... 56

2 Normative references .................................................................................................................................. 56

2.1 Identical Recommendations | International Standards ..................................................................... 56

3 Definitions .................................................................................................................................................. 56

3.1 Specification of basic notation ........................................................................................................ 56

3.2 Information object specification ...................................................................................................... 56

3.3 Parameterization of ASN.1 specification ........................................................................................ 56

3.4 Additional definitions ...................................................................................................................... 56

4 Abbreviations ............................................................................................................................................. 56

5 Convention ................................................................................................................................................. 56

6 Notation ...................................................................................................................................................... 56

6.1 Constraint ........................................................................................................................................ 56

7 ASN.1 lexical items .................................................................................................................................... 56

7.1 Additional keywords ....................................................................................................................... 56

8 General constraint specification ................................................................................................................. 56

9 User-defined constraints ............................................................................................................................. 56

10 Table constraints, including component relation constraints ...................................................................... 56

11 Contents constraints .................................................................................................................................... 56

Annex A Constraining instance-of types ............................................................................................................. 56

A.4 Example .......................................................................................................................................... 56

Annex B Summary of the notation ............................................................................................ 56

© ISO/IEC 2020 – All rights reserved
Rec. ITU-T X.682 (08/2015) iii
---------------------- Page: 3 ----------------------
ISO/IEC DIS 8824-3:2020(E)
Introduction

Application designers require a notation to define a structured data type to convey their semantics. This is provided in

Rec. ITU-T X.680 | ISO/IEC 8824-1 and Rec. ITU-T X.681 | ISO/IEC 8824-2. A notation is also required to further

constrain the values that can appear. Examples of such constraints are restricting the range of some component(s), or

using a specified information object set to constrain an "ObjectClassFieldType" component, or using the "AtNotation"

to specify a relation between components.

This Recommendation | International Standard provides the notation for the general case of constraint specification.

NOTE 1 – For historical reasons the special case of a "subtype constraint" is specified in Rec. ITU-T X.680 | ISO/IEC 8824-1.

Constraint notation can appear (in round brackets) after any use of the syntactic construct "Type", and the purpose of

this Recommendation | International Standard is to specify the general case of what goes in the round brackets.

NOTE 2 – Multiple constraints (each inside its own round brackets) can be applied to the same "Type", as the result of

constraining a "Type" is itself formally a "Type" construct.

When a constraint is applied to the textually outermost use of a "Type" construct, it results in the creation of a new type

which is a subtype of the original (parent) type.

A subtype of a parent type can itself be used in defining other subtypes of the same parent type in other uses of the

constraint notation. Thus the subset of values constituting a subtype can be defined either by limiting the range of the

parent type, or by specifying the subtype as a union of sets of values.

NOTE 3 – The "ValueSet" notation specified in Rec. ITU-T X.680 | ISO/IEC 8824-1, 16.7, provides a further means of

specifying a subtype.

Constraints may also be used to produce a subtype of a parent type (as described above) when the notation is embedded

within another type. However, some "component relation" constraints are textually included following a "Type" (within

a set or sequence type definition), but are not used to restrict the set of possible values of the "Type" which they follow

(the referencing component). Rather, they specify a relation between the value of the referencing component and the

value of one or more other "Type"s in the same set or sequence type (called the referenced components).

Component relation constraints can be seen as subtyping the sequence type within which they are embedded, but not

necessarily the referencing type.

A constraint on an "ObjectClassFieldType" component can be applied by restricting the type or values in the component

by using an information object set. Such constraints are called table constraints, since they are specified in terms of the

"associated table" of the object set. The component relation constraints defined in this Recommendation | International

Standard are a special case of table constraints.

Finally, a "Type" may be subtyped by specifying the set of values in the subtype by human-readable text. Such a

constraint is called a user-defined constraint. For example, a user-defined constraint can be specified to constrain a BIT

STRING to the set of values produced by the encryption of a value of a specified ASN.1 type.

It is the purpose of this Recommendation | International Standard to provide the notation to be used for specifying table

constraints (including component relation constraints), and user-defined constraints.

NOTE 4 – In general, full support for the specification of constraints in a flexible way (particularly component relation

constraints, subtyping constraints, and user-defined constraints with a formally defined body) would require notation with a

power comparable to that of programming languages. Such power can only be sensibly provided by the establishment of links

from the ASN.1 notation into some other defined computer language. This version of this Recommendation | International

Standard does not provide such links, and hence supports only a small number of constraining mechanisms.

While the embedding of notation defining constraints (subtypes and relationships) will frequently be the most

convenient form of specification (particularly for the simple subtyping of primitive components of structures), separate

(external) specification will sometimes be preferred, particularly where the constraints are being imposed by a separate

group from that which defined the basic protocol.

NOTE 5 – The parameterization defined in Rec. ITU-T X.683 | ISO/IEC 8824-4 is specifically designed to enable a piece of

ASN.1 specification (and in particular, a constraint) to be parameterized, allowing the actual constraint to be imposed by some

other group that provides actual parameters for the parameterized construct.
© ISO/IEC 2020 – All rights reserved
iv Rec. ITU-T X.682 (08/2015)
---------------------- Page: 4 ----------------------
ISO/IEC DIS 8824-3:2020(E)
The notations for constraint specification supported here are:
– user-defined constraints (see clause 9);

– table constraints, including component relation constraints between two components which are

carrying values related to an information object, defined using the notation of Rec. ITU-T X.681 |

ISO/IEC 8824-2 (see clause 10);
– contents constraints (see clause 11).

The application of table constraints to the "InstanceOfType" construct of Rec. ITU-T X.681 | ISO/IEC 8824-2, Annex

C, is specified in Annex A.
© ISO/IEC 2020 – All rights reserved
Rec. ITU-T X.682 (08/2015) v
---------------------- Page: 5 ----------------------
ISO/IEC DIS 8824-3:2020(E)
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC DIS 8824-3:2020(E)
ISO/IEC 8824-3:2015 (E)
INTERNATIONAL STANDARD
Rec. ITU-T X.682 (2015 E)
ITU-T RECOMMENDATION
Information technology –
Abstract Syntax Notation One (ASN.1):
Constraint specification
1 Scope

This Recommendation | International Standard is part of Abstract Syntax Notation One (ASN.1) and provides notation

for specifying user-defined constraints, table constraints, and contents constraints.

2 Normative references

The following Recommendations and International Standards contain provisions which, through reference in this text,

constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated

were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this

Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent

edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently

valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently

valid ITU-T Recommendations.
2.1 Identical Recommendations | International Standards

– Recommendation ITU-T X.680 (2020) | ISO/IEC 8824-1:2020, Information technology – Abstract

Syntax Notation One (ASN.1): Specification of basic notation.

– Recommendation ITU-T X.681 (2020) | ISO/IEC 8824-2:2020, Information technology – Abstract

Syntax Notation One (ASN.1): Information object specification.

– Recommendation ITU-T X.683 (2020) | ISO/IEC 8824-4:2020, Information technology – Abstract

Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications.
3 Definitions

For the purposes of this Recommendation | International Standard, the following definitions apply.

3.1 Specification of basic notation

This Recommendation | International Standard uses the terms defined in Rec. ITU-T X.680 | ISO/IEC 8824-1.

3.2 Information object specification

This Recommendation | International Standard uses the terms defined in Rec. ITU-T X.681 | ISO/IEC 8824-2.

3.3 Parameterization of ASN.1 specification

This Recommendation | International Standard uses the following term defined in Rec. ITU-T X.683 | ISO/IEC 8824-4:

– parameterized type.
3.4 Additional definitions

3.4.1 component relation constraint: A constraint on the values of a set type or sequence type which is textually

associated with one of the component types (the referencing component) of the set type or sequence type, and which

specifies the relationship between the value of that component and the values of one or more other components (the

referenced components).
© ISO/IEC 2020 – All rights reserved
Rec. ITU-T X.682 (08/2015) 1
---------------------- Page: 7 ----------------------
ISO/IEC DIS 8824-3:2020(E)
ISO/IEC 8824-3:2015 (E)

3.4.2 constrained type: The innermost "Type" which contains the referencing component and all of the referenced

components of some component relation constraint.

3.4.3 constraining set: The information object set referenced in some component relation constraint.

3.4.4 constraining table: The associated table (see Rec. ITU-T X.681 | ISO/IEC 8824-2, clause 13) corresponding

to a constraining set.

3.4.5 referenced component: A component of a set type or sequence type identified in a component relation

constraint.

3.4.6 referencing component: A component of a set type or sequence type which has an associated component

relation constraint.

3.4.7 selected rows: Those rows of a constraining table which contain, in the appropriate columns, the values of all

of the referenced components.

3.4.8 table constraint: A constraint applied to an object class field type which demands that its values conform to

the contents of the appropriate column of some table.

3.4.9 user-defined constraint: A constraint which requires a more complicated statement than can be

accommodated by the other forms of constraint, and which must therefore involve specification by some means outside

of ASN.1.
4 Abbreviations

For the purposes of this Recommendation | International Standard, the following abbreviation applies:

ASN.1 Abstract Syntax Notation One
5 Convention

This Recommendation | International Standard employs the notational convention defined in Rec. ITU-T X.680 |

ISO/IEC 8824-1, clause 5.
6 Notation

This clause summarizes the notation defined in this Recommendation | International Standard.

6.1 Constraint

The following notation which can be used as an alternative for "ConstraintSpec" (see Rec. ITU-T X.680 |

ISO/IEC 8824-1, 49.6) is defined in this Recommendation | International Standard:

– GeneralConstraint (see 8.1).
7 ASN.1 lexical items

In addition to the lexical items specified in Rec. ITU-T X.680 | ISO/IEC 8824-1, clause 12, this Recommendation |

International Standard makes use of the lexical items specified in the following subclauses. The general rules applicable

to these lexical items are as defined in Rec. ITU-T X.680 | ISO/IEC 8824-1, 12.1. These new lexical items make use of

the ASN.1 character set, as specified in Rec. ITU-T X.680 | ISO/IEC 8824-1, clause 11.

7.1 Additional keywords

The names CONSTRAINED, CONTAINING, ENCODED and BY are listed in Rec. ITU-T X.680 | ISO/IEC 8824-1, 12.38, as

reserved words.
8 General constraint specification
8.1 The notation for a "GeneralConstraint" is as follows:
© ISO/IEC 2020 – All rights reserved
2 Rec. ITU-T X.682 (08/2015)
---------------------- Page: 8 ----------------------
ISO/IEC DIS 8824-3:2020(E)
ISO/IEC 8824-3:2015 (E)
GeneralConstraint ::=
UserDefinedConstraint
| TableConstraint
| ContentsConstraint

8.2 The various possibilities for specification of the constraint are defined as follows:

a) "UserDefinedConstraint", in clause 9;
b) "TableConstraint", in clause 10;
c) "ContentsConstraint", in clause 11.
9 User-defined constraints

NOTE 1 – This form of constraint specification can be regarded as a special form of ASN.1 comment, since it is not fully

machine-processable. However, it would be possible for an automatic tool to use the presence of a particular user-defined

constraint to invoke user-supplied constraint checking.

NOTE 2 – Protocol designers should be aware that since the definition of a constraint in this way is not fully machine-

processable, a specification which employs this capability may be less easy to handle with automatic tools.

9.1 A user-defined constraint is specified by the syntax:
UserDefinedConstraint ::=
CONSTRAINED BY "{" UserDefinedConstraintParameter "," * "}"

9.2 It is recommended that the actual constraint be referenced by a comment anywhere inside the braces

( "{" and "}" ). This comment should clearly state what constraint is imposed by the "UserDefinedConstraint".

NOTE – If there are any "UserDefinedConstraintParameter"s within the braces (see 9.3), the comments may precede, follow, or

be interspersed among them, at the definer's convenience.

9.3 The actual constraint to be applied may depend on some parameters. For each such parameter, a

"UserDefinedConstraintParameter" shall be included in the "UserDefinedConstraint". Each

"UserDefinedConstraintParameter" shall be any "Value", "Object", "DefinedObjectSet", "Type" or

"DefinedObjectClass" which is specified by a reference name or, in the case of "Value", "Object" or "Type", can also be

defined inline.

NOTE – The reference name may be a dummy parameter if the "UserDefinedConstraint" is used within a

"ParameterizedAssignment".
UserDefinedConstraintParameter ::=
Governor ":" Value
| Governor ":" Object
| DefinedObjectSet
| Type
| DefinedObjectClass

The notation "Governor" is defined in Rec. ITU-T X.683 | ISO/IEC 8824-4, 8.3. When the first alternative is used, the

"Governor" shall be a "Type". When the second alternative is used, the "Governor" shall be a "DefinedObjectClass".

9.4 Example

If an application designer wishes to specify that certain components are to be bit strings carrying an encryption of the

value of some ASN.1 type (different for each component), then (using the par
...