CAN CSA Z243.134-M88 (2004) HDLC Procedures – Elements of Procedures, Scope, and Compliance

A comprehensive technical overview of the Canadian standard for High-Level Data Link Control procedure elements

The standard CAN CSA Z243.134-M88 (2004) is the Canadian implementation of the international standard for High-Level Data Link Control (HDLC) procedures — specifically, the Elements of Procedures. Originally published by the Canadian Standards Association (CSA) in 1988 and reaffirmed in 2004, it defines the fundamental building blocks for bit-oriented data link control protocols widely used in telecommunications, networking, and industrial control systems. This article provides a detailed technical breakdown of the standard’s scope, core technical requirements, practical implementation highlights, and compliance considerations.

Scope and Purpose

CAN CSA Z243.134-M88 (2004) is identical in technical content to ISO 4335:1987. Its scope encompasses the essential procedural elements required to establish, maintain, and terminate data link connections using HDLC. The standard covers:

  • Frame structure — flag, address, control, information, and frame check sequence (FCS) fields.
  • Control field formats — definition of Information (I), Supervisory (S), and Unnumbered (U) frames, including the use of the Poll/Final (P/F) bit.
  • Commands and responses — standard set of station-to-station instructions (e.g., SABM, DISC, RR, RNR, REJ, UI, etc.).
  • Modes of operation — Normal Response Mode (NRM), Asynchronous Balanced Mode (ABM), and Asynchronous Response Mode (ARM).
  • Exception handling — procedures for invalid frames, retransmission, and timeout recovery.

The standard applies to any data communication system that requires reliable, connection-oriented or connectionless data transfer at the link layer.

Technical Requirements and Architecture

Frame Structure

Every HDLC frame conforms to the following format (bits transmitted left to right):

| Flag (01111110) | Address (8+ bits) | Control (8 or 16 bits) | Information (variable) | FCS (16 or 32 bits) | Flag (01111110) |

The Control field determines the frame type and carries sequence numbers, commands, and responses. The standard defines three control field formats:

Frame TypeControl Field Bits (8-bit example)Description
I-frame0 – N(S) – P/F – N(R)Information transfer with sequence numbering (N(S), N(R)).
S-frame10 – SS – P/F – N(R)Supervisory functions (RR, RNR, REJ, SREJ).
U-frame11 – MMM – P/F – MMMUnnumbered commands and responses (e.g., SABM, DISC, UA, DM).

Table 1: Control Field Format Summary (where N(S) = send sequence number, N(R) = receive sequence number, SS = supervisory function bits, MMM = modifier bits, P/F = Poll/Final bit).

Tip: When implementing the control field, always verify the bit ordering per the standard’s definition. Misplacing the P/F bit is a common source of interoperability issues.

Commands, Responses, and Modes

The standard enumerates all standard HDLC commands and responses. The table below lists the most widely used:

MnemonicTypeFunction
RRSReceiver Ready
RNRSReceiver Not Ready
REJSReject (go-back-N)
SREJSSelective Reject
SABMUSet Asynchronous Balanced Mode
SABMEUSet ABM Extended
DISCUDisconnect
UAUUnnumbered Acknowledge
DMUDisconnected Mode
UIUUnnumbered Information

Modes of operation (NRM, ABM, ARM) define the relationship between primary and secondary stations. ABM is most common in modern peer-to-peer links; NRM is used with a controlling primary station.

Parameter Negotiation and Extensions

CAN CSA Z243.134-M88 (2004) supports extended control fields (16 bits) modulo 128 for window sizes larger than 7. The standard also documents procedures for parameter negotiation using XID frames, though the basic elements of procedures remain unchanged.

Implementation Highlights

Successful implementation of this standard requires attention to:

  • Bit stuffing — after five consecutive 1s, a 0 is inserted to preserve flag uniqueness.
  • Timer management — timers T1 (acknowledgment wait), T2 (response timeout), and T3 (idle link detection) must be configured per application.
  • Sequence number handling — modulo 8 or 128 arithmetic, with proper window sliding and reject procedures.
  • Addressing — address field can be 8 bits (common) or extended to 16+ bits using the ‘0’ extension bit.
Warning: Mixing modulo 8 and modulo 128 implementations on the same link will cause unrecoverable mismatches. Ensure both ends agree on the control field length during initial mode setting.
Success: Following CAN CSA Z243.134-M88 (2004) guarantees interoperability with legacy HDLC systems and simplifies certification for telecom equipment used in Canadian networks.

Compliance and Certification

To claim compliance with CAN CSA Z243.134-M88 (2004), a product must implement all mandatory elements of procedures defined in this standard. Key compliance requirements include:

  • Correct interpretation of all mandatory commands (SABM, DISC, RR, RNR, REJ) and responses (UA, DM).
  • Accurate frame delineation and bit stuffing.
  • Proper FCS calculation using the standard 16-bit or 32-bit polynomial.
  • Implementation of at least one defined mode of operation (typically ABM).

Certification bodies in Canada often require a statement of conformance referencing this reaffirmed standard. Note that the standard does not specify physical layer attributes; it is purely a data link layer specification.

Danger: Relying on older versions of HDLC procedures without adopting the correction and clarification in the 2004 reaffirmation may lead to frame rejection in multi-vendor environments.

Where applicable, consult the Canadian Radio-television and Telecommunications Commission (CRTC) or the Innovation, Science and Economic Development (ISED) Canada for additional regulatory requirements that may reference this HDLC standard.

Frequently Asked Questions

Q: Is CAN CSA Z243.134-M88 (2004) still current?
A: Yes, it remains the active Canadian implementation of HDLC elements of procedures. Although originally published in 1988, the standard was reaffirmed in 2004 and continues to be referenced by many telecommunications and industry protocols.
Q: How does this standard differ from ISO 4335?
A: CAN CSA Z243.134-M88 (2004) is technically identical to ISO 4335:1987. The only differences are editorial and formatting changes applied by CSA for Canadian adoption.
Q: Can I use this standard for satellite or high-latency links?
A: The standard supports extended sequence numbers (modulo 128) and selective reject (SREJ), which improve performance over high-latency links. However, the standard itself is media-independent; the user must select appropriate timers and parameters.
Q: Is compliance mandatory in Canada?
A: Compliance is mandatory when a procurement specification or contract explicitly references CAN CSA Z243.134-M88 (2004). For many telecommunications products, it is a de facto requirement for proving interoperability with existing Canadian infrastructure.


International Standards Documentation – 2026. All references to CAN CSA Z243.134-M88 (2004) are for informational purposes. Always consult the official CSA publication for authoritative text.

📥 Standard Documents Download

🔒
Please wait 10 seconds, the download links will appear after the ad loads

Leave a Reply

Your email address will not be published. Required fields are marked *