c068352_ISO_IEC_8824-3_2015.pdf

Reference number ISO/IEC 8824-32015E ISO/IEC 2015 INTERNATIONAL STANDARD ISO/IEC 8824-3 Fifth edition 2015-11-15 Ination technology Abstract Syntax Notation One ASN.1 Constraint specification Technologies de lination Notation de syntaxe abstraite numro un ASN.1 Spcification des contraintes ISO/IEC 8824-32015E COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any 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 Case postale 56  CH-1211 Geneva 20 Tel. 41 22 749 01 11 Fax 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2015 – All rights reserved ISO/IEC 8824-32015E ISO/IEC 2015 – All rights reserved iii Foreword ISO the International Organization for Standardization and IEC the International Electrotechnical Commission the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of ination technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. This fifth edition cancels and replaces the fourth edition of ISO/IEC 8824-32008 which has been technically revised. It also incorporates ISO/IEC 8824-32008/Cor.12014. ISO/IEC 8824-3 was prepared by Joint Technical Committee ISO/IEC JTC 1, Ination technology Subcommittee SC 6, Telecommunications and ination exchange between systems, in collaboration with ITU-T. The identical text is published as ITU-T X.682 08/2015. I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T X.682 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU 08/2015 SERIES X DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY OSI networking and system aspects – Abstract Syntax Notation One ASN.1 Ination technology – Abstract Syntax Notation One ASN.1 Constraint specification Recommendation ITU-T X.682 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY PUBLIC DATA NETWORKS Services and facilities X.1–X.19 Interfaces X.20–X.49 Transmission, signalling and switching X.50–X.89 Network aspects X.90–X.149 Maintenance X.150–X.179 Administrative arrangements X.180–X.199 OPEN SYSTEMS INTERCONNECTION Model and notation X.200–X.209 Service definitions X.210–X.219 Connection-mode protocol specifications X.220–X.229 Connectionless-mode protocol specifications X.230–X.239 PICS proas X.240–X.259 Protocol Identification X.260–X.269 Security Protocols X.270–X.279 Layer Managed Objects X.280–X.289 Conance testing X.290–X.299 INTERWORKING BETWEEN NETWORKS General X.300–X.349 Satellite data transmission systems X.350–X.369 IP-based networks X.370–X.379 MESSAGE HANDLING SYSTEMS X.400–X.499 DIRECTORY X.500–X.599 OSI NETWORKING AND SYSTEM ASPECTS Networking X.600–X.629 Efficiency X.630–X.639 Quality of service X.640–X.649 Naming, Addressing and Registration X.650–X.679 Abstract Syntax Notation One ASN.1 X.680–X.699 OSI MANAGEMENT Systems management framework and architecture X.700–X.709 Management communication service and protocol X.710–X.719 Structure of management ination X.720–X.729 Management functions and ODMA functions X.730–X.799 SECURITY X.800–X.849 OSI APPLICATIONS Commitment, concurrency and recovery X.850–X.859 Transaction processing X.860–X.879 Remote operations X.880–X.889 Generic applications of ASN.1 X.890–X.899 OPEN DISTRIBUTED PROCESSING X.900–X.999 INATION AND NETWORK SECURITY X.1000–X.1099 SECURE APPLICATIONS AND SERVICES X.1100–X.1199 CYBERSPACE SECURITY X.1200–X.1299 SECURE APPLICATIONS AND SERVICES X.1300–X.1399 CYBERSECURITY INATION EXCHANGE X.1500–X.1599 CLOUD COMPUTING SECURITY X.1600–X.1699 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T X.682 08/2015 i INTERNATIONAL STANDARD ISO/IEC 8824-3 RECOMMENDATION ITU-T X.682 Ination technology – Abstract Syntax Notation One ASN.1 Constraint specification Summary Recommendation ITU-T X.682 | ISO/IEC 8824-3 provides the ASN.1 notation for the general case of constraint and exception specification by which the data values of a structured data type can be limited. The notation also provides for signalling if and when a constraint is violated. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T X.682 1994-07-01 7 11.1002/1000/3044 2.0 ITU-T X.682 1997-12-12 7 11.1002/1000/4445 2.1 ITU-T X.682 1997 Technical Cor. 1 2000-03-31 7 11.1002/1000/5047 2.2 ITU-T X.682 1997 Technical Cor. 2 2001-02-02 7 11.1002/1000/5334 2.3 ITU-T X.682 1997 Technical Cor. 3 2001-03-15 7 11.1002/1000/5434 3.0 ITU-T X.682 2002-07-14 17 11.1002/1000/6087 4.0 ITU-T X.682 2008-11-13 17 11.1002/1000/9606 4.1 ITU-T X.682 2008 Cor. 1 2014-03-01 17 11.1002/1000/12145 5.0 ITU-T X.682 2015-08-13 17 11.1002/1000/12481 * To access the Recommendation, type the URL http//handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http//handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T X.682 08/2015 FOREWORD The International Telecommunication Union ITU is the United Nations specialized agency in the field of telecommunications, ination and communication technologies ICTs. The ITU Telecommunication Standardization Sector ITU-T is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly WTSA, which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of ination technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions to ensure, e.g., interoperability or applicability and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest ination and are therefore strongly urged to consult the TSB patent database at http//www.itu.int/ITU-T/ipr/.  ITU 2015 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T X.682 08/2015 iii CONTENTS Page Introduction ............................................................................................................................................................... iv Ination technology – Abstract Syntax Notation One ASN.1 Constraint specification ............................. 1 1 Scope .............................................................................................................................................................. 1 2 Normative references ...................................................................................................................................... 1 2.1 Identical Recommendations | International Standards ......................................................................... 1 3 Definitions ...................................................................................................................................................... 1 3.1 Specification of basic notation ............................................................................................................ 1 3.2 Ination object specification .......................................................................................................... 1 3.3 Parameterization of ASN.1 specification ............................................................................................ 1 3.4 Additional definitions .......................................................................................................................... 1 4 Abbreviations ................................................................................................................................................. 2 5 Convention ..................................................................................................................................................... 2 6 Notation .......................................................................................................................................................... 2 6.1 Constraint ............................................................................................................................................ 2 7 ASN.1 lexical items ........................................................................................................................................ 2 7.1 Additional keywords ........................................................................................................................... 2 8 General constraint specification ..................................................................................................................... 2 9 User-defined constraints ................................................................................................................................. 3 10 Table constraints, including component relation constraints .......................................................................... 4 11 Contents constraints ........................................................................................................................................ 7 Annex A – Constraining instance-of types ................................................................................................................. 8 A.4 Example .............................................................................................................................................. 8 Annex B – Summary of the notation ................................................................................................... 9 iv Rec. ITU-T X.682 08/2015 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 components, or using a specified ination 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 ally 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 v