Find Standards: Errata and Correction Sheets

Access to recent IEEE standards errata sheets, as well as other corrections.

 

IEEE Standards Errata for IEEE Std 802.12™-1995 IEEE Standards for Local and Metropolitan Area Networks: Demand Priority Access Method, Physical Layer and Repeater Specifications

Sponsor

LAN/MAN Standards Committee of the IEEE Computer Society

Correction Sheet

Page 3

Reverse the text descriptions for Annexes C and D. They should read as follows:

Annex C (GDMO specifications for demand-priority managed objects) defines the Guidelines for the Definition of Managed Objects (GDMO) notation used for layer management objects (normative if the optional LME is implemented).

Annex D (Allocation of object identifier values) contains a summary of all object identifier values that have been allocated for layer management purposes (normative if the optional LME is implemented).

Page 21

In the fourth line at the top of the page:
Delete "End {if}" from the example pseudo code.

Page 36

At the top of the page, in the last sentence:
packet start frame delimiter should be packet start of stream delimiter

Replace the last paragraph of 7.4 with the following:

The formats for M_UNITDATA.indications and M_UNITDATA.requests are the same as formats for MA_UNITDATA.indications and MA_UNITDATA.requests, except for the addition of an optional parameter for the FCS and two parameters that indicate the frame_type and the requested mac_action. The FCS parameter may be used to preserve the FCS value when bridging between LANs using like formats. The frame_type and mac_action parameters are not explicitly encoded in the MAC frames, but are included as constants in bridging service requests and indications as specified in 2.4 of ISO/IEC 10038: 1993.

Pages 50, 56, and 62

In subparagraph e) of 10.2.4, 10.3.6, and 10.6.5, the reference:
(see A.1.1) should be (see [B5])

Page 51

In the second line of the first paragraph of 10.3, the reference:
ISO/IEC 8802-3 should be ISO/IEC 8802-5

In the second line of the first paragraph of 10.3, the reference:
ISO/IEC 8802-3:1993 should be ISO/IEC 8802-5: 1996

Pages 63-64

Replace the last paragraph of 11.2 and footnotes 21 and 22 with the following two paragraphs (and footnotes):

The MAC also reacts to control signals from the repeater indicating a possible incoming packet by requesting the physical sublayers to switch to the receive mode. When data packets are received, the MAC verifies the destination address, performs an FCS check on the received frame, and checks whether any other transmission errors have been detected, or if an IPM has been received. If all error checks are negative in an end node, the MAC frame is converted back to LLC frame format and an MA_UNITDATA.indication (DA, SA, Routing Information, msdu, priority)21 is made to the LLC. If all error checks are negative in a bridge, the MAC makes an M_UNITDATA.indication (frame_type, mac_action, DA, SA, Routing Information, msdu, user_priority, FCS)22 to the bridge entity.

The definition of the MAC sublayer in the remainder of this clause is based on service to an LLC sublayer. If the upper sublayer is a bridge entity, the MA_UNITDATA.request and MA_UNITDATA.indication primitives identified in Autonomous process 1: Wait for MA_UNITDATA.request (11.4.1.1), in the PROCEDURE Process_Received_MAC_Frame (11.5.6), and in the FUNCTION Build_Frame (11.5.7) are replaced by the appropriate M_UNITDATA.request or M_UNITDATA.indication primitive with appropriate additional parameters as indicated in 7.4.

FOOTNOTES

21The Routing Information field in an MA_UNITDATA.indication is only applicable to the ISO/IEC 8802-5 format (see 7.3, figures 15 and 16).

22The frame_type and mac_action parameters are encoded as constants. The Routing Information field in an M_UNITDATA.indication is only applicable to the ISO/IEC 8802-5 format (see 7.4).

Page 71

At the end of the first paragraph of 11.4.1.1:
(see 11.3.5.5) should be (see 11.5.7).

Page 71

In the last sentence of 11.4.1.2:
used in MAC2_REMOVE_CONTROL_SIGNAL and MAC9_RETRAIN_DELAY. should be
used in MAC3_IDLE_OR_REQUEST.

Page 79

In 11.5.5:
move the last sentence in the text description of FRAME_TYPE to SOURCE_MAC_ADDRESS.

Page 83

In the frame_type_802_5 case of FRAME_STATUS:
Add a coma (,) after MSDU in the following statement:
MA_UNITDATA.indication (DA, SA, ROUTING_INFORMATION, MSDU, LLC_PRIORITY);

Page 88

In the second line of the text description of FUNCTION ComputePad():
procedure Build_Frame() should be function Build_Frame()

Page 88

In the last line of the text description of FUNCTION CRC32():
the procedures Process_Received_MAC_Frame() and Build_Frame() should be
the procedure Process_Received_MAC_Frame() and the function Build_Frame()

Page 112

Move the definition of Link_Warning from 12.3.1 to 12.3.2 (page 113).

Page 169

In the second line of ERROR_INDICATION, the phrase:
as specified below, under Length Monitoring, Control of Onward Transmission, and Frame
Transmission. should be as specified in 12.9.6 and 12.9.7.

Page 178

At the end of the second line in 12.9.8:
figure 61 should be figure 89.

Page 235

In the second paragraph of BEHAVIOUR DEFINED AS under aPortAdministrativeState:
acPortAdminControl should be acPortAdministrativeControl

Page 261

In the first line of the paragraph above 14.4.4:
figure 117 should be figure 118

Page 272

In SSDN[i], in the true and false values:
high-priority ssd should be normal priority ssd

Page 292

In the second line of 16.6.1:
(see 0) should be (see 16.8.3.3)

Page 293

In the first line of 16.6.5:
Subject to the requirements of 0 and 16.6.6 should be
Subject to the requirements of 16.8.3.3 and 16.6.6

Page 331

In 18.2, at the end of item a):
Add (see figure 163).

Page 357

In A.5.1, in the reference for the protocol feature "Are the following Management capabilities supported?"
E.2 should be C.2

Page 358

In A.5.2, for items EMrn and EMrh in the reference column of the table:
7.3 should be 11.4.1.4

Page 360

In A.5.4, in the reference column of the table:
11.3.4.2 should be 11.5.2.2

Page 361

In A.6.1, in the references for the following items under the protocol feature "What RMAC capability levels are supported?"

RCsr 12.7.1, 12.7.6, 12.7.7, 12.7.9 should be 12.7.1, 12.7.7, 12.7.8, 12.7.10
RCt 12.7.1, 12.7.5 thru 12.7.7, 12.7.9 should be 12.7.1, 12.7.6 thru 12.7.8, 12.7.10
*RCbr 12.7.1 thru 12.7.4, 12.7.6 thru 12.7.10 should be 12.7.1 thru 12.7.5, 12.7.7 thru 12.7.11
*RCmr 12.7.1 thru 12.7.10 should be 12.7.1 thru 12.7.11

In the references for the protocol feature "Are the following Management capabilities supported?"
E.1 should be C.1

In the references for the following items under the protocol feature "Are the following training capabilities supported?"

RTdc 10.6.3.6 should be 10.6.3.7
RTnb 10.6.3.4 should be 10.6.3.5

Pages 365, 366, and 368

In the "Are the PMD receive functions supported" section of the PMD/MDI feature columns in A.7.2, A.7.3, and A.7.4:

Receive Control State indication should be Receiver Control State indication

Pages 373 and 374

In C.1.1.2, add exclamation point syntax delimiters (!) at both the beginning and the end of the "DEFINED AS" specification for the following attributes:

aCurrentFramingType
See "aCurrentFramingType BEHAVIOUR DEFINED AS" in 3.2.4.2.1.;
should be
!See "aCurrentFramingType BEHAVIOUR DEFINED AS" in 3.2.4.2.1!;

aDesiredFramingType
See "aDesiredFramingType BEHAVIOUR DEFINED AS" in 13.2.4.2.1.;
should be
!See "aDesiredFramingType BEHAVIOUR DEFINED AS" in 13.2.4.2.1!;

aFramingCapability
See "aFramingCapability BEHAVIOUR DEFINED AS" in 13.2.4.2.1.;
should be
!See "aFramingCapability BEHAVIOUR DEFINED AS" in 13.2.4.2.1!;

aGroupMap
See "aGroupMap BEHAVIOUR DEFINED AS" in 13.2.4.2.1.;
should be
!See "aGroupMap BEHAVIOUR DEFINED AS" in 13.2.4.2.1!;

aMACAddress
See "aMACAddress BEHAVIOUR DEFINED AS" in 13.2.4.2.1.;
should be
!See "aMACAddress BEHAVIOUR DEFINED AS" in 13.2.4.2.1!;

Page 381

In C.1.4.2, for aAllowableTrainingType, exchange the order of the BEHAVIOUR and MATCHES FOR lines of the definition:

BEHAVIOURbAllowableTrainingType;
MATCHES FOREQUALITY;
should be
MATCHES FOREQUALITY;
BEHAVIOURbAllowableTrainingType;

Page 382

For aLastTrainedAddress, change DERIVED FROM to WITH ATTRIBUTE SYNTAX and exchange the order of the BEHAVIOUR and MATCHES FOR lines of the definition:

DERIVED FROMIEEE802CommonDefinitions.MACAddress;
BEHAVIOURbLastTrainedAddress;
MATCHES FOREQUALITY;
should be
WITH ATTRIBUTE SYNTAXIEEE802CommonDefinitions.MACAddress;
MATCHES FOREQUALITY;
BEHAVIOURbLastTrainedAddress;

Page 388

For nbMACMonitor, in the SUBORDINATE OBJECT CLASS definition, change EWMA to lowercase:
"IEEE802.1F":EWMAMetricMonitor;
should be
"IEEE802.1F":ewmaMetricMonitor;

Page 391

For aLastTrainingConfig, add a semicolon (;) after the WITH ATTRIBUTE SYNTAX definition:
IEEE802dot12-MgmtAttributeModule.TrainingConfig
should be
IEEE802dot12-MgmtAttributeModule.TrainingConfig;

Page 392

For aMACVersion, Add a dash (-) between "IEEE802dot12" and "MgmtAttributeModule:"
IEEE802dot12MgmtAttributeModule.VersionBitString;
should be
IEEE802dot12-MgmtAttributeModule.VersionBitString;

Page 397

In C.4, for IEEE802dot12-MgmtAttributeModule, in the second line of the definition, remove the
space between "version" and "1(1)}:"
asn1Module(2) commonDefinitions(0) version 1(1)} DEFINITIONS
should be
asn1Module(2) commonDefinitions(0) version1(1)} DEFINITIONS

Page 399

Add "End" below the last line of the GDMO code.

Pages 400 through 406

In all tables of annex D, all references to annex D and its associated subclauses should be
to annex C and its associated subclauses.

Page 401

In the first table of D.3, "Allocations for repeater object class identifiers," the numbering of
the references are incorrect:
Reference D.1.1.1 should be C.1.1
Reference D.1.1.2 should be C.1.3
Reference D.1.1.3 should be C.1.4

Page 404

In the first table of D.4, "Allocations for end node object class identifiers," the numbering of the reference is incorrect:
Reference D.2.1.1 should be C.2.1