ETSI ETS 300 273 ed.1 (1994-03)
Network Aspects (NA); Metropolitan Area Network (MAN); Medium Access Control (MAC) layer management
Network Aspects (NA); Metropolitan Area Network (MAN); Medium Access Control (MAC) layer management
DE/NA-053129
Omrežni vidiki (NA) – Velemestno omrežje (MAN) – Upravljanje plasti za krmiljenje dostopa do medijev (MAC)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 273 E1:2003
01-december-2003
Omrežni vidiki (NA) – Velemestno omrežje (MAN) – Upravljanje plasti za krmiljenje
dostopa do medijev (MAC)
Network Aspects (NA); Metropolitan Area Network (MAN); Medium Access Control
(MAC) layer management
Ta slovenski standard je istoveten z: ETS 300 273 Edition 1
ICS:
35.110 Omreževanje Networking
SIST ETS 300 273 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 273 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 273 E1:2003
EUROPEAN ETS 300 273
TELECOMMUNICATION March 1994
STANDARD
Source: ETSI TC-NA Reference: DE/NA-053129
ICS: 33.080
MAN, management
Key words:
Network Aspects (NA);
Metropolitan Area Network (MAN)
Medium Access Control (MAC) layer management
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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 1994. All rights reserved.
New presentation - see History box
---------------------- Page: 3 ----------------------
SIST ETS 300 273 E1:2003
Page 2
ETS 300 273: March 1994
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: 4 ----------------------
SIST ETS 300 273 E1:2003
Page 3
ETS 300 273: March 1994
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .9
3.1 Definitions .9
3.2 Abbreviations .9
4 MAC layer management.10
4.1 MAC layer management architecture .10
4.2 MLM through special purpose layer management protocols within the MAC layer .11
4.2.1 MLM interface.11
4.2.2 MLM protocol.11
4.3 MLM through systems management .12
4.3.1 Interface .14
4.3.2 Protocols .14
4.3.2.1 Introduction.14
4.3.2.2 Short stack protocol suite .14
4.3.2.2.1 Physical layer.14
4.3.2.2.2 Data link layer .15
4.3.2.2.3 Network layer.15
4.3.2.2.4 Mapping functions.15
4.3.2.2.5 Application layer.15
4.3.2.3 Addressing principles for MAN systems management.15
4.3.2.3.1 MAC layer addresses.16
4.3.2.3.2 Logical link addresses .16
4.3.2.3.3 Addressing at higher layers .16
5 Information model for systems management of the MAC layer.16
5.1 Object classes and packages definitions.16
5.1.1 Message identifier page allocation .16
5.1.2 DQDB configuration .17
5.1.3 Distributed queue process.18
5.1.4 Bandwidth balancing process.18
5.1.5 MAN DQDB service access point.19
5.1.6 MAN CL service access point .20
5.1.7 Segment header processing .20
5.1.8 IMPDU reassembly process.21
5.1.9 IMPDU transmission process.22
5.1.10 Physical layer facilities.24
5.2 Name bindings for object classes.24
5.3 Attributes.29
5.4 Actions .40
5.5 Notifications .41
5.6 ASN.1 syntax .42
5.6.1 ASN.1 attributes definitions .42
5.6.2 Action module definitions .44
5.6.3 ASN.1 notification definitions.45
Annex A (informative): Optional packages for the MAC layer information model.46
A.1 MID page allocation.46
A.2 Distributed queue process.47
---------------------- Page: 5 ----------------------
SIST ETS 300 273 E1:2003
Page 4
ETS 300 273: March 1994
A.3 Bandwidth balancing process. 50
A.4 Connectionless service access points. 51
A.5 Segment header processing. 53
A.6 IMPDU reassembly process . 55
A.7 IMPDU transmission process . 59
A.8 ASN.1 syntax . 60
A.8.1 ASN.1 optional attributes definitions . 60
A.8.2 ASN.1 optional notification definitions. 61
Annex B (informative): Bibliography . 62
History. 63
---------------------- Page: 6 ----------------------
SIST ETS 300 273 E1:2003
Page 5
ETS 300 273: March 1994
Foreword
This European Telecommunication Standard (ETS) describes the layer management for the Medium
Access Control (MAC) layer of European Metropolitan Area Networks (MANs) to the ETSs on MANs.
This ETS has been produced by the Network Aspects (NA) Technical Committee of the European
Telecommunications Standards Institute (ETSI) taking into account the guide-lines given in CCITT
Recommendation X.700 [11] and the protocol specification given in ETS 300 212 [2].
Introduction
All the resources of a telecommunication network need to be managed in order to cost effectively provide
the Quality Of Service (QOS) required by customers.
A subset of these resources is constituted by the protocol stack supporting communications between
remote systems.
The structure and process of controlling and/or monitoring activities of different facilities in different
communication layers is the layer management.
---------------------- Page: 7 ----------------------
SIST ETS 300 273 E1:2003
Page 6
ETS 300 273: March 1994
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 273 E1:2003
Page 7
ETS 300 273: March 1994
1 Scope
This European Telecommunication Standard (ETS) describes the Medium Access Control (MAC) layer
management which applies to the European standard Metropolitan Area Network (MAN).
To this end it:
a) defines the reference architecture for MAC Layer Management (MLM);
b) defines services and protocols for MLM;
c) includes the specification of managed objects which permit the operation of the protocol elements
to be remotely managed. The definition of the managed object classes for the Connection Oriented
(CO) and Constant Bit Rate (CBR) services is not contained in this ETS.
Management information within the network is exchanged through systems management protocols and
special purpose layer management protocols.
2 Normative references
This ETS incorporates, by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed below.
For dated references, subsequent amendments to or revisions of these publications apply to this 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 211: "Network Aspects (NA); Metropolitan Area Network (MAN)
Principles and architecture".
[2] ETS 300 212: "Network Aspects (NA); Metropolitan Area Network (MAN) Media
access control layer and physical layer specification".
[3] ETS 300 213: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 2,048 Mbit/s".
[4] ETS 300 214: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 34,368 Mbit/s".
[5] ETS 300 215: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 139,264 Mbit/s".
[6] ETS 300 216: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 155,520 Mbit/s".
[7] IEEE Standard 802.1b, Draft D.19 (1991): "Local Area Networks and
Metropolitan Area Networks - Management".
[8] IEEE Standard 802.1f, Draft D7 (1991): "Guide-lines for the Development of
Layer Management Standard".
[9] IEEE Standard 802.6g, Draft D0 (1991): "Distributed Queue Dual Bus (DQDB)
Subnetwork of a Metroplolitan Area Network (MAN) - Layer Management".
[10] CCITT Recommendation X.208 (1988): "Specification of Abstract syntax
notation one (ASN.1)".
[11] CCITT Recommendation X.700: "OSI Management Framework".
[12] CCITT Recommendation X.701: "Information technology - Open systems
interconnection - Systems management overview".
---------------------- Page: 9 ----------------------
SIST ETS 300 273 E1:2003
Page 8
ETS 300 273: March 1994
[13] CCITT Recommendation X.711 (1991): "OSI Common management information
protocol specification for CCITT applications".
[14] CCITT Draft Recommendation X.720: "Information technology - Open systems
interconnection - Structure of management informations: management
information model".
[15] CCITT Draft Recommendation X.721: "Information technology - Open systems
interconnection - Structure of management informations: definition of
management information".
[16] CCITT Recommendation X.722: "Information technology - Open systems
interconnection - Structure of management informations: Guide-lines for the
Definition of Managed Objects".
[17] CCITT Recommendation X.200 (1988): "Reference model of open system
interconnection for CCITT applications".
[18] IEEE Standard 802.6 (1991): "Distributed Queue Dual Bus (DQDB) Subnetwork
of a Metropolitan Area Network (MAN)".
[19] CCITT Recommendation M.3010 (1992): "Principles for a Telecommunication
Management Network".
[20] CCITT Recommendation G.773 (1988): "Protocol suites for Q-interfaces for
management of transmission systems".
[21] ETS 300 276: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 622,080 Mbit/s CCITT
Recommendations G.707, G.708, and G.709 SDH based systems".
[22] ISO 8802-2 (1988): "Information processing systems - Local area networks -
Part 2: Logical link control".
[23] ISO 8802-2 addendum 2: "Information Processing Systems - Local Area
Networks. Logical Link Control - Addendum 2: Acknowledged connectionless-
mode services and protocol, Type 3 operation".
[24] ISO 8348 addendum 1 (1987): "Information processing systems - Data
communication - Network service definition Addendum 1: Connectionless-mode
transmission".
[25] ISO 8348 addendum 2 (1988): "Information processing systems - Data
communication - Network service definition - Addendum 2: Network layer
addressing".
[26] ISO 8473 (1988): "Information processing systems - Data communications -
Protocol for providing the connectionless-mode network service".
[27] CCITT Recommendation M.3100 (1992): "Generic Network Information Model".
[28] CCITT Draft Recommendation X.738 (1991): "Summarisation Function".
---------------------- Page: 10 ----------------------
SIST ETS 300 273 E1:2003
Page 9
ETS 300 273: March 1994
3 Definitions and abbreviations
3.1 Definitions
This ETS uses the MAN terminology defined in ETS 300 211 [1], specifically:
a) Access Facility 1 (AF1);
b) Access Facility 2 (AF2);
c) Distributed Queue Dual Bus (DQDB);
d) MAN Switching System (MSS);
e) Metropolitan Area Network (MAN);
f) User MAN Interface (UMI).
This ETS also uses the MAN terminology defined in ETS 300 212 [2], specifically:
a) Bus Identification Field (BIF);
b) Default Slot Generator Subfield (DSGS);
c) External Timing Source Subfield (ETSS);
d) Head Of Bus Subfield (HOBS);
e) Medium Access Control (MAC);
f) Message Identifier (MID);
g) Physical Layer Convergence Procedure (PLCP);
h) slot.
This ETS uses some of the terminology defined in the CCITT Draft Recommendation X.738 [28],
specifically:
- granularity period.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AF1 Access Facility 1
AF2 Access Facility 2
AFI Authority and Format Identifier
ASN.1 Abstract Syntax Notation 1
BCD Binary Coded Decimal
BIF Bus Identification Field
BWB Bandwidth Balancing
CBR Constant Bit Rate
CC Configuration Control
CL Connectionless
CO Connection Oriented
CRC Cyclic Redundancy Check
DCN Data Communication Network
DMPDU Derived MAC Protocol Data Unit
DQDB Distributed Queue Dual Bus
DSGS Default Slot Generator Subfield
ETSI MAN European MAN conforming to ETSI ETSs on MANs
ETSS External Timing Source Subfield
---------------------- Page: 11 ----------------------
SIST ETS 300 273 E1:2003
Page 10
ETS 300 273: March 1994
HOB Head Of Bus
HOBS Head Of Bus Subfield
IDI Initial Domain Identifier
IMPDU Initial MAC Protocol Data Unit
LLC Logical Link Control
LMPE Layer Management Protocol Entity
LSAP LLC Service Access Point
MAC Medium Access Control
MAN Metropolitan Area Network
MCF MAC Convergence Functions
MID Message Identifier
MLM MAC Layer Management
MN MAN Node
MSS MAN Switching System
NE Network Element
PDH Plesiochronous Digital Hierarchy
PDU Protocol Data Unit
PLCP Physical Layer Convergence Procedure
PLCSM Physical Layer Connection State Machine
PR Page Request
QA Queued Arbitrated
Q Q interface for specific MAN systems and service management
MAN
QOS Quality Of Service
RDN Relative Distinguished Name
RIT Reassembly IMPDU Timer
RSM Reassembly State Machine
SAP Service Access Point
SDH Synchronous Digital Hierarchy
TMN Telecommunication Management Network
UMI User MAN Interface
VCI Virtual Channel Identifier
4 MAC layer management
The MAC layer of the European MAN conforming to ETSI ETSs on MANs (ETSI MAN) uses IEEE
Standard 802.6 [18] Distributed Queue Dual Bus (DQDB) functions. Management of these functions is
performed in two specific categories: peer-to-peer management of DQDB entities is performed over a
special purpose layer management protocol, and remote management is performed over a systems
management interface. These are described below.
4.1 MAC layer management architecture
This subclause describes the general architecture for MLM.
There are two main aspects of the management function. One is the layer management related
information and operations and the second is the communication services and protocols required to
exchange management information between different open systems.
The information model used in this ETS is based on the definition given in CCITT Draft Recommendation
X.720 [14]. Managed objects for MLM are defined according to guide-lines given in CCITT
Recommendation X.722 [16].
Management communication is effected through the following mechanisms:
a) the use of the special purpose management protocols within the layer;
b) the use of systems management protocols.
---------------------- Page: 12 ----------------------
SIST ETS 300 273 E1:2003
Page 11
ETS 300 273: March 1994
4.2 MLM through special purpose layer management protocols within the MAC layer
The mechanism for the exchange of layer management information between two MAC layer entities is
indicated in IEEE Standard 802.6 [18], sections 9 and 10, as indicated in ETS 300 212 [2]. Figure 1 shows
a schematic representation of this mechanism.
The MAC layer entities communicate with one another via the MLM protocol to support management
control of the layer.
Higher
Higher
layers
layers
Special purpose
MLM protocol
MAC MAC
LMPE LMPE
layer
layer
(via octets M1/M2)
Physical
Physical
layer
layer
Figure 1: Layer Management Protocol Entity (LMPE)
4.2.1 MLM interface
This subclause is based on IEEE Standard 802.6 [18], section 9 (as indicated in ETS 300 212 [2]) and
applies for Access Facility 1 (AF1) and Access Facility 2 (AF2). Section 9.2.4 of IEEE Standard 802.6 [18]
describes functions required for the connection oriented convergence function and is, therefore, for further
study within ETSI. Section 9.7 of IEEE Standard 802.6 [18] describes functions related to configuration
control that are required only for a looped multipoint configuration.
4.2.2 MLM protocol
This subclause is based on IEEE Standard 802.6 [18], section 10 (as indicated in ETS 300 212 [2]) and
applies for AF1 and AF2. Section 10.2 of IEEE Standard 802.6 [18] describes the configuration control
protocol, which is required only for a looped multipoint configuration. In any other case the node on the
MAN Switching System (MSS) side of the interface shall set the MAC layer information octet type 0 to
00111011 (TYPE=0, Bus Identification Field (BIF)=01, Default Slot Generator Subfield (DSGS)=11, Head
of Bus Subfield (HOBS)=01, External Timing Source Subfield (ETSS)=1).
Section 10.3 of IEEE Standard 802.6 [18] describes the Message Identifier (MID) page allocation protocol.
This section applies only where dynamic distributed MID page allocation is implemented.
---------------------- Page: 13 ----------------------
SIST ETS 300 273 E1:2003
Page 12
ETS 300 273: March 1994
4.3 MLM through systems management
The communication structure for the exchange of management information through systems management
protocols is based on manager/agent relationships as indicated in CCITT Recommendation X.701 [12].
Figure 2 shows the communication between the manager and the agent entities, between agent and
managed objects, as well as the protocols and services used for this purpose.
The MAC layer resources are part of the whole MAN resources. Therefore, they are subject to control and
supervision by the MAN systems management.
The interface to the MAN management system is the systems management interface, and the definition of
this interface implies the definition of the management information (the information model) as well as of
the protocols that carry this information.
The DQDB MAC sublayer is implemented both in MSSs and MAN Nodes (MNs). Depending on the type of
managed element, different interfaces can be used for the management of the sublayer resources
through system management.
MSSs can use either DQDB based networks or other networks as access part to the public
Telecommunication Management Network (TMN) Data Communication Network (DCN).
The protocol suite which shall be used is either the Q (described in subclause 4.3.2), the Q (defined in
MAN
CCITT Recommendation G.773 [20]) or the Q3 (defined in CCITT Recommendation Q.961 and CCITT
Recommendation Q.962).
The Q short stack (see subclause 4.3.2.2) management interface shall be provided in the MN.
MAN
Additional interfaces may be provided.
This ETS specifies only the short stack Q protocol suite.
MAN
---------------------- Page: 14 ----------------------
SIST ETS 300 273 E1:2003
Page 13
ETS 300 273: March 1994
MANAGER
OPEN SYSTEM
MANAGER
Request Confirmation
management service
management
protocol
management service
Indication Response
MANAGED
OPEN SYSTEM
AGENT
Managed
Operations Results
object
boundary
MANAGED
OBJECTS
2a: Operations
MANAGER
OPEN SYSTEM
MANAGER
Response Indication
management service
management
protocol
management service
Confirmation Request
MANAGED
OPEN SYSTEM
AGENT
Managed
Notifications
object
boundary
MANAGED
OBJECTS
2b: Notifications
Figure 2: MAN management information exchanges
---------------------- Page: 15 ----------------------
SIST ETS 300 273 E1:2003
Page 14
ETS 300 273: March 1994
4.3.1 Interface
The Q interface is considered for specific MAN systems (and service) management. This interface
MAN
shall be used for systems (and service) management communications among managers and agents
(indicated in subclause 4.2) when they take place via a DQDB based MAN. The protocols for the Q
MAN
interface are specified in subclause 4.3.2. The exchanged information (as far as the MLM is concerned) is
specified in Clause 5, where the MLM information model is defined.
NOTE: The MAC layer information model as defined in this ETS can also be used with system
management interfaces different from the Q .
MAN
4.3.2 Protocols
4.3.2.1 Introduction
In the following, the protocol suites for the Q interface are described.
MAN
The defined communication services and protocols are in accordance with the CCITT Recommendation
X.200 [17]. The protocols for the non-MAC layers are based on CCITT Recommendations and/or ISO
standards, while the MAC layer is defined in relevant IEEE Standard and ETSI standards, IEEE Standard
802.6 [18] and ETS 300 212 [2].
Two protocol suites are considered:
a) short stack protocol suite;
b) full 7 layers stack protocol suite.
A short stack protocol suite is mandatory when the Q interface is placed on MAN Nodes (MNs) and
MAN
shall be implemented as described in subclause 4.3.2.2.
The full 7 layers protocol suite for the Q is not specified in this ETS. However, it should be aligned, for
MAN
the layers above the MAC layer, to the CCITT Draft Recommendations Q.961 (§ 5.3.2.2 and § 5.3.3) and
CCITT Recommendation Q.962 (§ 3.2, § 3.3, § 3.4, § 3.5, § 4.1 and § 4.2).
4.3.2.2 Short stack protocol suite
4.3.2.2.1 Physical layer
The short stack protocol suite employs MAN technology for the physical and data link layers. Therefore,
the following alternatives are considered for the physical layer:
- 2,048 Mbit/s: CCITT Recommendations G.702, G.703, and G.704 Plesiochronous
Digital Hierarchy (PDH);
- 34,368 Mbit/s: CCITT Recommendations G.702, G.703, and G.751 PDH;
- 139,264 Mbit/s: CCITT Recommendations G.702, G.703, and G.751 PDH;
- 155,520 Mbit/s: CCITT Recommendations G.707, G.708, and G.709 Synchronous
Digital Hierarchy (SDH);
- 622,080 Mbit/s: CCITT Recommendations G.707, G.708, and G.709 SDH.
The relevant Physical Layer Convergence Procedures (PLCPs) are indicated respectively in the following
documents: ETS 300 213 [3], ETS 300 214 [4], ETS 300 215 [5], ETS 300 216 [6] and in
ETS 300 276 [21].
---------------------- Page: 16 ----------------------
SIST ETS 300 273 E1:2003
Page 15
ETS 300 273: March 1994
4.3.2.2.2 Data link layer
The data link layer provides the acknowledged connectionless-mode service. The access method
employed is the DQDB in accordance with IEEE Standard 802.6 [18].
The services and protocol of the DQDB access method shall comply with those specified in
ETS 300 211 [1]. The address length used at the MAC sublayer shall be 60 bits.
The definition of the acknowledged connectionless-mode Logical Link Control (LLC) service and protocol
shall comply with that specified in ISO 8802-2 [22] and ISO 8802-2 addendum 2 [23].
4.3.2.2.3 Network layer
The definition of the connectionless-mode network service shall comply with that specified in ISO 8348
addendum 1 [24]. Address formats supported shall conform to ISO 8348 addendum 2 [25].
The network layer requires the normal data transfer service from the data link layer. The network layer
shall provide the N-UNITDATA service as listed in table 8 of CCITT Recommendation G.773 [20]
(equivalent to table 15 of ISO 8348, addendum 1 [24]).
The network protocol is specified in ISO 8473 [26]. The Authority and Format Identifier (AFI) and the Initial
Domain Identifier (IDI) shall be set according to ISO 8348 addendum 2 [25].
The full network layer protocol and its two subsets permit the use of known sub-network characteristics
and are therefore not sub-network independent. Depending on the required usage and the sub-network
architecture, the full network layer protocol, or one or both subsets, shall be supported by the short stack
protocol suite:
- the inactive network layer protocol shall be in accordance with the inactive subset of the protocol as
defined in ISO 8473 [26];
- the non-segmenting network layer protocol shall be in accordance with "Type 1" functions of the
non-segmenting subset of the protocol as defined in ISO 8473 [26]. From the optional functions
("Type 3") defined in the non-segmenting subset only the "priority functions" shall be supported as
defined in ISO 8473 [26];
- the full network layer protocol subset of category "Type 1" functions shall be in accordance with ISO
8473 [26]. An implementation of such a protocol shall not transmit PDUs encoded using the inactive
subset. Received Protocol Data Units (PDUs) encoded using the inactive subset shall be discarded.
An implementation shall not generate data PDUs without a segmentation part, i.e. the segmentation
permitted flag (SP) shall be set to 1 and the segmentation part shall be included. However, an
implementation shall be capable of receiving and correctly processing PDUs which do not contain
the segmentation part.
4.3.2.2.4 Mapping functions
No transport layer, session layer and presentation layer is specified for the short stack protocol suite. To
provide the required service to the application layer and using the provided service of the network layer, a
mapping function is defined. The mapping function for the short stack protocol suite is specified in the
CCITT Recommendation G.773 [20], § 3.4.
4.3.2.2.5 Application layer
The application layer services and protocol for the short stack protocol suite are specified in CCITT
Recommendation G.773 [20], § 3.5.
4.3.2.3 Addressing principles for MAN systems management
System management communications between local and remote managers require communication
facilities (i.e. DCN). A specific protocol suite and interface (i.e. Q ), to be used when the DCN is a
MAN
DQDB-based MAN, have been specified. In the following subclauses a generic scheme for addressing of
management communications is outlined.
---------------------- Page: 17 ----------------------
SIST ETS 300 273 E1:2003
Page 16
ETS 300 273: March 1994
4.3.2.3.1 MAC layer addresses
Management communications shall make use of the Connectionless (CL) service functionalities provided
by the MAN MAC layer. Numbers structured according to CCITT Recommendation E.164 shall be
assigned to address management entities.
The management PDUs that run over the MAC shall be uniquely identified as containing management
informati
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.