Telecommunications and exchange between information technology systems — Requirements for local and metropolitan area networks — Part 1Q: Bridges and bridged networks — Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing

Télécommunications et échange entre systèmes informatiques — Exigences pour les réseaux locaux et métropolitains — Partie 1Q: Ponts et réseaux pontés — Amendement 36

General Information

Status
Published
Publication Date
25-Feb-2025
Current Stage
6060 - International Standard published
Start Date
26-Feb-2025
Due Date
16-Feb-2027
Completion Date
26-Feb-2025
Ref Project

Relations

Standard
ISO/IEC/IEEE 8802-1Q:2024/Amd 36:2025 - Telecommunications and exchange between information technology systems — Requirements for local and metropolitan area networks — Part 1Q: Bridges and bridged networks — Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing Released:26. 02. 2025
English language
157 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


International
Standard
ISO/IEC/IEEE
8802-1Q
Third edition
Telecommunications and exchange
2024-08
between information technology
systems — Requirements for local
AMENDMENT 36
and metropolitan area networks —
Part 1Q:
Bridges and bridged networks
AMENDMENT 36: YANG Data
Models for Scheduled Traffic, Frame
Preemption, and Per-Stream Filtering
and Policing
Télécommunications et échange entre systèmes informatiques —
Exigences pour les réseaux locaux et métropolitains —
Partie 1Q: Ponts et réseaux pontés
AMENDEMENT 36
Reference number
ISO/IEC/IEEE 8802-1Q:2024/
Amd.36:2025(en) © IEEE 2025
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2025(en)
© IEEE 2025
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 IEEE at the address below.
Institute of Electrical and Electronics Engineers, Inc
3 Park Avenue, New York
NY 10016-5997, USA
Email: stds.ipr@ieee.org
Website: www.ieee.org
Published in Switzerland
© IEEE 2025 – All rights reserved
ii
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form 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.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
document should be noted (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE
administers the process and establishes rules to promote fairness in the consensus development process, the
IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its
standards.
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent database
available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
ISO/IEC/IEEE 8802-1Q:2024/Amd 36 was prepared by the LAN/MAN of the IEEE Computer Society (as IEEE
802.1Qcw-2023) and drafted in accordance with its editorial rules. It was adopted, under the “fast-track
procedure” defined in the Partner Standards Development Organization cooperation agreement between ISO
and IEEE, by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6,
Telecommunications and information exchange between systems.
A list of all parts in the ISO/IEC/IEEE 8802 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
committees.
© IEEE 2023 – All rights reserved
iii
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
Contents
1. Overview. 15
1.3 Introduction. 15
12. Bridge management . 16
12.29 Managed objects for scheduled traffic. 16
12.29.1 The Gate Parameter Table . 16
12.31 Managed objects for per-stream classification and metering . 17
12.31.1 The Stream Parameter Table . 17
12.31.3 The Stream Gate Instance Table . 17
17. Management Information Base (MIB) . 18
17.2 Structure of the MIB . 18
17.2.22 Structure of the IEEE8021-ST-MIB . 18
17.2.24 Structure of the IEEE8021-PSFP-MIB . 18
17.7 MIB modules . 19
17.7.14 Definitions for the IEEE8021-SRP-MIB module . 19
17.7.22 Definitions for the IEEE8021-ST-MIB module . 38
17.7.24 Definitions for the IEEE8021-PSFP-MIB module . 49
35. Stream Reservation Protocol (SRP). 69
35.2 Definition of the MSRP application . 69
35.2.2 Definition of MRP elements . 69
46. Time-Sensitive Networking (TSN) configuration . 70
46.2 User/network configuration information . 70
46.2.3 Talker . 70
48. YANG Data Models . 71
48.2 IEEE 802.1Q YANG models. 71
48.2.1 VLAN Bridge components model . 71
48.2.2 Two-Port MAC Relay (TPMR) model . 73
48.2.4 Provider Bridge model . 74
48.2.5 CFM Model . 77
48.2.7 Asynchronous Traffic Shaping (ATS) model . 79
48.2.8 Congestion Isolation (CI) model . 80
48.2.9 Scheduled Traffic model . 80
48.2.10 Frame Preemption model . 81
48.2.11 Per-Stream Filtering and Policing model . 82
48.3 Structure of the YANG models . 84
48.3.9 Scheduled Traffic model . 84
48.3.10 Frame Preemption model . 85
48.3.11 Per-Stream Filtering and Policing model . 85
................................................................... 86
48.4 Security considerations .
48.4.9 Security considerations of the Scheduled Traffic model . 86
48.4.10 Security considerations of the Frame Preemption model . 86
48.4.11 Security considerations of the Per-Stream Filtering and Policing model . 86
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
48.5 YANG schema tree definitions. 87
48.5.4 Schema for the ieee802-dot1q-bridge YANG module . 87
48.5.17 Schema for the ieee802-dot1q-sched YANG module . 91
48.5.18 Schema for the ieee802-dot1q-sched-bridge YANG module . 91
48.5.19 Schema for the ieee802-dot1q-preemption YANG module . 91
48.5.20 Schema for the ieee802-dot1q-preemption-bridge YANG module . 92
48.5.21 Schema for the ieee802-dot1q-psfp YANG module . 92
48.5.22 Schema for the ieee802-dot1q-psfp-bridge YANG module . 92
48.6 YANG modules . 94
48.6.1 The ieee802-types YANG module . 94
48.6.2 The ieee802-dot1q-types YANG module . 99
48.6.4 The ieee802-dot1q-bridge YANG module . 115
48.6.6 The ieee802-dot1q-pb YANG module . 141
48.6.17 The ieee802-dot1q-sched YANG module . 145
48.6.18 The ieee802-dot1q-sched-bridge YANG module . 151
48.6.19 The ieee802-dot1q-preemption YANG module . 152
48.6.20 The ieee802-dot1q-preemption-bridge YANG module . 156
48.6.21 The ieee802-dot1q-psfp YANG module . 157
48.6.22 The ieee802-dot1q-psfp-bridge YANG module . 167
Annex A (normative) PICS proforma—Bridge implementations . 168
A.47 YANG. 168
Annex B (normative) PICS proforma—End station implementations . 169
B.15 Scheduled traffic . 169
B.16 Frame Preemption. 169
B.17 Per-Stream Filtering and Policing. 169
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
Figures
Figure 48-5 Bridge Port model. 72
Figure 48-7 TPMR port model . 73
Figure 48-9 Provider Edge Bridge C-VLAN Interface model . 75
Figure 48-10 Provider Edge Bridge S-VLAN interface model. 76
Figure 48-12 CFM MEP model relationships . 78
Figure 48-16 Asynchronous Traffic Shaping model . 79
Figure 48-17 Congestion Isolation model . 80
Figure 48-18 Scheduled Traffic model. 81
Figure 48-19 Frame Preemption model. 82
Figure 48-20 PSFP model. 83
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
Tables
Table 12-32 The Gate Parameter Table . 16
Table 12-34 The Stream Parameter Table. 17
Table 17-28 IEEE8021-ST-MIB structure. 18
Table 17-30 IEEE8021-PSFP-MIB structure. 18
Table 48-1 Summary of the YANG modules. 84
Table 48-10 Scheduled Traffic model YANG modules. 84
Table 48-11 Frame Preemption model YANG modules. 85
Table 48-12 Per-Stream Filtering and Policing model YANG modules . 85
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Standard for
Local and Metropolitan Area Networks—
Bridges and Bridged Networks
Amendment 36:
YANG Data Models for Scheduled
Traffic, Frame Preemption, and
Per-Stream Filtering and Policing
(This amendment is based on IEEE Std 802.1Q™-2022 as amended by IEEE Std 802.1Qcz-2023.)
NOTE—The editing instructions contained in this amendment define how to merge the material contained therein into
the existing base standard and its amendments to form the comprehensive standard.
The editing instructions are shown in bold italics. Four editing instructions are used: change, delete, insert, and replace.
Change is used to make corrections in existing text or tables. The editing instruction specifies the location of the change
and describes what is being changed by using strikethrough (to remove old material) and underscore (to add new
material). Delete removes existing material. Insert adds new material without disturbing the existing material. Deletions
and insertions may require renumbering. If so, renumbering instructions are given in the editing instruction. Replace is
used to make changes in figures or equations by removing the existing figure or equation and replacing it with a new
one. Editing instructions, change markings, and this note will not be carried over into future editions because the
changes will be incorporated into the base standard.
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
1. Overview
1.3 Introduction
Insert new list item cs) after item cr) in 1.3 and renumber the subsequent list items accordingly:
cs) Define YANG configuration and operational state models (Clause 48) in support of scheduled
traffic, frame preemption, and Per-Stream Filtering and Policing.
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
12. Bridge management
12.29 Managed objects for scheduled traffic
12.29.1 The Gate Parameter Table
Insert two new rows at the end of Table 12-32 as follows (unchanged rows not shown):
Table 12-32—The Gate Parameter Table
Operations
b
Name Data type Conformance References
a
supported
SupportedCycleMax RationalNumber R B, E 8.6.8.4, 12.29.1.3,
(seconds) 12.29.1.6
SupportedIntervalMax Integer R B, E 8.6.8.4, 12.29.1.7
a
R= Read only access; RW = Read/Write access.
b
B = Required for Bridge or Bridge component support of enhancements for scheduled traffic; E = Required for end station support of
enhancements for scheduled traffic.
12.29.1.2 The gate control list structure and data types
12.29.1.2.1 GateControlEntry
Change 12.29.1.2.1 as follows:
A GateControlEntry consists of an operation name, followed by up to 2 parameters associated with the
operation, as detailed in Table 8-7. The first parameter, if present, is a gateStatesValue (12.29.1.2.2); the
second parameter, if present, is a timeIntervalValue (12.29.1.2.3).
Insert 12.29.1.6 and 12.29.1.7 after 12.29.1.5 as follows:
12.29.1.6 SupportedCycleMax
The maximum value supported by this Port of the AdminCycleTime (8.6.9.4.3) and OperCycleTime
(8.6.9.4.19) parameters.
12.29.1.7 SupportedIntervalMax
The maximum value supported by this Port of the timeIntervalValue (12.29.1.2.3) parameter.
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
12.31 Managed objects for per-stream classification and metering
12.31.1 The Stream Parameter Table
Insert two new rows at the end of Table 12-34 as follows (unchanged rows not shown):
Table 12-34—The Stream Parameter Table
Operations
b
Name Data type Conformance References
a
supported
SupportedCycleMax RationalNumber R PSFP, ATS 8.6.5.4, 12.29.1.3,
(seconds) 12.29.1.6
SupportedIntervalMax Integer R PSFP, ATS 8.6.5.4, 12.29.1.7
a
R= Read only access; RW = Read/Write access.
b
PSFP = Required for Bridge, Bridge component, or end station support of PSFP.
psfp = Optional for Bridge, Bridge component, or end station support of PSFP.
ATS = Required for Bridge or Bridge component support of ATS.
ats = Optional for Bridge or Bridge component support of ATS.
CI = Required for Bridge or Bridge component support of CI.
Insert 12.31.1.7 and 12.31.1.8 after 12.31.1.6 as follows:
12.31.1.7 SupportedCycleMax
The maximum value supported by this Port of the AdminCycleTime (8.6.9.4.3) and OperCycleTime
(8.6.9.4.19) parameters.
12.31.1.8 SupportedIntervalMax
The maximum value supported by this Bridge component of the timeIntervalValue (12.31.3.2.4) parameter.
12.31.3 The Stream Gate Instance Table
12.31.3.2 The gate control list structure and data types
12.31.3.2.2 StreamGateControlEntry
Change 12.31.3.2.2 as follows:
A StreamGateControlEntry consists of an operation name, followed by three mandatory parameters and one
optional parameter associated with the operation, as detailed in Table 8-4. The first parameter is a
StreamGateStatesValue (8.6.10.5, 12.31.3.2.1); the second parameter is an IPV value (8.6.10.7, 12.31.3.2.3),
and; the third parameter is a timeIntervalValue (8.6.9.4.23, 12.31.3.2.4); and the fourth parameter is an
IntervalOctetMaxValue (8.6.10.1, 12.31.3.2.5). IntervalOctetMaxValue is optional.
Insert 12.31.3.2.5 after 12.31.3.2.4 as follows:
12.31.3.2.5 IntervalOctetMaxValue
An unsigned integer, denoting an IntervalOctetMax in MSDU octets (see IntervalOctetMax in Table 8-4).
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
17. Management Information Base (MIB)
17.2 Structure of the MIB
17.2.22 Structure of the IEEE8021-ST-MIB
Insert three new rows at the end of Table 17-28 as follows (unchanged rows not shown):
Table 17-28—IEEE8021-ST-MIB structure
IEEE8021-ST-MIB table/object Reference
ieee8021STSupportedCycleMaxNumerator SupportedCycleMax, 12.29.1.6
ieee8021STSupportedCycleMaxDenominator SupportedCycleMax, 12.29.1.6
ieee8021STSupportedIntervalMax SupportedIntervalMax, 12.29.1.7
17.2.24 Structure of the IEEE8021-PSFP-MIB
Insert three new rows at the end of Table 17-30 as follows (unchanged rows not shown):
Table 17-30—IEEE8021-PSFP-MIB structure
IEEE8021-PSFP-MIB table/object Reference
ieee8021PSFPSupportedCycleMaxNumerator SupportedCycleMax, 12.31.1.7
ieee8021PSFPSupportedCycleMaxDenominator SupportedCycleMax, 12.31.1.7
ieee8021PSFPSupportedIntervalMax SupportedIntervalMax, 12.31.1.8
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
7 8
17.7 MIB modules
17.7.14 Definitions for the IEEE8021-SRP-MIB module
Change 17.7.14 as follows:
IEEE8021-SRP-MIB DEFINITIONS ::= BEGIN
-- =============================================================
-- MIB for support of IEEE 802.1Qat Stream Reservation Protocol
-- (SRP) in IEEE 802.1Q Bridges.
-- =============================================================
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Counter64,
Unsigned32
FROM SNMPv2-SMI
MacAddress,
TEXTUAL-CONVENTION,
TruthValue
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
ieee802dot1mibs,
IEEE8021PriorityCodePoint,
IEEE8021VlanIndex
FROM IEEE8021-TC-MIB
IEEE8021FqtssTrafficClassValue
FROM IEEE8021-FQTSS-MIB
ieee8021BridgeBaseComponentId,
ieee8021BridgeBaseEntry,
ieee8021BridgeBasePort,
ieee8021BridgeBasePortEntry
FROM IEEE8021-BRIDGE-MIB
;
ieee8021SrpMib MODULE-IDENTITY
LAST-UPDATED "202211080000Z" -- November 8, 2022"202309260000Z" -- September 26, 2023
ORGANIZATION "IEEE 802.1 Working Group"
CONTACT-INFO
" WG-URL: http://www.ieee802.org/1/
WG-EMail: stds-802-1-l@ieee.org
Contact: IEEE 802.1 Working Group Chair
Postal: C/O IEEE 802.1 Working Group
IEEE Standards Association
445 Hoes Lane
Piscataway, NJ 08854
USA
E-mail: stds-802-1-chairs@ieee.org"
DESCRIPTION
"The Bridge MIB module for managing devices that support
the IEEE Std 802.1Q Stream Reservation Protocol.
Unless otherwise indicated, the references in this MIB
module are to IEEE Std 802.1Q-2022.
Copyright (C) IEEE (20222023).
This version of this MIB module is part of IEEE Std 802.1Q;
see that standard for full legal notices."
Copyright release for MIBs: Users of this standard may freely reproduce the MIB modules in this standard so that they can be used for
their intended purpose.
An ASCII version of this MIB module is attached to the PDF version of this standard, and can be obtained by Web browser from the
IEEE 802.1 Website at https://1.ieee802.org/mib-modules/.
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
REVISION "202309260000Z" -- September 26, 2023
DESCRIPTION
"Published as part of IEEE 802.1Qcw.
Changed the applicable SYNTAX of object definitions
ieee8021SrpStreamDataFramePriority, and
ieee8021SrpStreamPreloadDataFramePriority
from IEEE8021PriorityCodePoint to INTEGER
to correct an error identifying PCP encoding SYNTAX
instead of PCP values as intended."
REVISION "202211080000Z" -- November 8, 2022
DESCRIPTION
"Published as part of IEEE Std 802.1Q-2022.
Cross references and contact information updated."
REVISION "201810040000Z" -- October 4, 2018
DESCRIPTION
"Published as part of IEEE 802.1Qcc-2018.
Added managed objects for Stream Reservation
Protocol (SRP) Enhancements and Performance
Improvements"
REVISION "201806280000Z" -- June 28, 2018
DESCRIPTION
"Published as part of IEEE Std 802.1Q 2018.
Cross references updated. "
REVISION "201512020000Z" -- December 2, 2015
DESCRIPTION
"Published as part of IEEE Std 802.1Q-2014 Cor-1.
ieee8021SrpReservationFailureBridgeId changed to
ieee8021SrpReservationFailureSystemId."
REVISION "201412150000Z" -- December 15, 2014
DESCRIPTION
"Published as part of IEEE Std 802.1Q 2014 revision.
Cross references updated and corrected."
REVISION   "201102270000Z" -- February 27, 2011
DESCRIPTION
"Minor edits to contact information etc. as part of
2011 revision of Std 802.1Q."
REVISION   "201004190000Z" -- April 19, 2010
DESCRIPTION
"Initial revision, included in IEEE 802.1Qat"
::= { ieee802dot1mibs 19 }
-- =============================================================
-- Textual Conventions
-- =============================================================
IEEE8021SrpStreamRankValue ::= TEXTUAL-CONVENTION
STATUS    current
DESCRIPTION
"An 802.1 SRP Stream Rank value. This is an integer,
with the following interpretation placed on the value:
0: Emergency, high-rank stream,
1: Non-emergency stream."
REFERENCE  "35.2.2.8.5b"
SYNTAX INTEGER {
emergency(0),
nonEmergency(1)
}
IEEE8021SrpStreamIdValue ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:1x:1x:1x:1x:1x.1x:1x"
STATUS    current
DESCRIPTION
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
"Represents an SRP Stream ID, which is often defined
as a MAC Address followed by a unique 16-bit ID."
SYNTAX    OCTET STRING (SIZE (8))
IEEE8021SrpReservationDirectionValue ::= TEXTUAL-CONVENTION
STATUS    current
DESCRIPTION
"An 802.1 SRP Stream Reservation Direction value. This is
an integer, with the following interpretation placed on
the value:
0: Talker registrations,
1: Listener registrations."
REFERENCE  "35.2.1.2"
SYNTAX    INTEGER {
talkerRegistrations(0),
listenerRegistrations(1)
}
IEEE8021SrpReservationDeclarationTypeValue ::= TEXTUAL-CONVENTION
STATUS    current
DESCRIPTION
"An 802.1 SRP Stream Reservation Declaration Type value.
This is an integer, with the following interpretation
placed on the value:
0: Talker Advertise,
1: Talker Failed,
2: Listener Asking Failed,
3: Listener Ready,
4: Listener Ready Failed."
REFERENCE  "35.2.1.3"
SYNTAX    INTEGER {
talkerAdvertise(0),
talkerFailed(1),
listenerAskingFailed(2),
listenerReady(3),
listenerReadyFailed(4)
}
IEEE8021SrpReservationFailureCodeValue ::= TEXTUAL-CONVENTION
STATUS    current
DESCRIPTION
"An 802.1 SRP Stream Reservation Failure Code value.
This is an integer, with the following interpretation
placed on the value:
0: No failure,
1: Insufficient bandwidth,
2: Insufficient Bridge resources,
3: Insufficient bandwidth for Traffic Class,
4: StreamID in use by another Talker,
5: Stream destination address already in use,
6: Stream pre-empted by higher rank,
7: Reported latency has changed,
8: Egress port is not AVBCapable,
9: Use a different destination_address,
10: Out of MSRP resources,
11: Out of MMRP resources,
12: Cannot store destination_address,
13: Requested priority is not an SR Class priority,
14: MaxFrameSize is too large for media,
15: maxFanInPorts limit has been reached,
16: Changes in FirstValue for a registered StreamID,
17: VLAN is blocked on this egress port (Registration Forbidden),
18: VLAN tagging is disabled on this egress port (untagged set),
19: SR class priority mismatch."
REFERENCE  "35.2.2.8.7"
SYNTAX    INTEGER {
noFailure(0),
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
insufficientBandwidth(1),
insufficientResources(2),
insufficientTrafficClassBandwidth(3),
streamIDInUse(4),
streamDestinationAddressInUse(5),
streamPreemptedByHigherRank(6),
latencyHasChanged(7),
egressPortNotAVBCapable(8),
useDifferentDestinationAddress(9),
outOfMSRPResources(10),
outOfMMRPResources(11),
cannotStoreDestinationAddress(12),
priorityIsNoAnSRCLass(13),
maxFrameSizeTooLarge(14),
maxFanInPortsLimitReached(15),
firstValueChangedForStreamID(16),
vlanBlockedOnEgress(17),
vlanTaggingDisabledOnEgress(18),
srClassPriorityMismatch(19)
}
-- =============================================================
-- subtrees in the SRP MIB
-- =============================================================
ieee8021SrpNotifications
OBJECT IDENTIFIER ::= { ieee8021SrpMib 0 }
ieee8021SrpObjects
OBJECT IDENTIFIER ::= { ieee8021SrpMib 1 }
ieee8021SrpConformance
OBJECT IDENTIFIER ::= { ieee8021SrpMib 2 }
ieee8021SrpConfiguration
OBJECT IDENTIFIER ::= { ieee8021SrpObjects 1 }
ieee8021SrpLatency
OBJECT IDENTIFIER ::= { ieee8021SrpObjects 2 }
ieee8021SrpStreams
OBJECT IDENTIFIER ::= { ieee8021SrpObjects 3 }
ieee8021SrpReservations
OBJECT IDENTIFIER ::= { ieee8021SrpObjects 4 }
-- =============================================================
-- The ieee8021SrpConfiguration subtree
-- This subtree defines the objects necessary for the
-- operational management of SRP.
-- =============================================================
ieee8021SrpBridgeBaseTable OBJECT-TYPE
SYNTAX   SEQUENCE OF Ieee8021SrpBridgeBaseEntry
MAX-ACCESS not-accessible
STATUS   current
DESCRIPTION
"A table for SRP main control and status information.
All writable objects in this table must be persistent
over power up restart/reboot. These objects augment
the ieee8021BridgeBasePortTable."
::= { ieee8021SrpConfiguration 1 }
ieee8021SrpBridgeBaseEntry OBJECT-TYPE
SYNTAX   Ieee8021SrpBridgeBaseEntry
MAX-ACCESS not-accessible
STATUS   current
DESCRIPTION
"SRP control and status information for a Bridge."
AUGMENTS { ieee8021BridgeBaseEntry }
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
::= { ieee8021SrpBridgeBaseTable 1 }
Ieee8021SrpBridgeBaseEntry ::=
SEQUENCE {
ieee8021SrpBridgeBaseMsrpEnabledStatus
TruthValue,
ieee8021SrpBridgeBaseMsrpTalkerPruning
TruthValue,
ieee8021SrpBridgeBaseMsrpMaxFanInPorts
Unsigned32,
ieee8021SrpBridgeBaseMsrpLatencyMaxFrameSize
Unsigned32,
ieee8021SrpBridgeBaseMsrpTalkerVlanPruning
TruthValue,
ieee8021SrpBridgeBaseMsrpMaxSRClasses
Unsigned32
}
ieee8021SrpBridgeBaseMsrpEnabledStatus OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-create
STATUS   current
DESCRIPTION
"The administrative status requested by management for
MSRP. The value true(1) indicates that MSRP should
be enabled on this device, in all VLANs, on all ports
for which it has not been specifically disabled. When
false(2), MSRP is disabled, in all VLANs and on all
ports, and all MSRP frames will be forwarded
transparently. This objects affects both Applicant and
Registrar state machines. A transition from false(2)
to true(1) will cause a reset of all MSRP state
machines on all ports.
This object may be modified while the corresponding
instance of ieee8021BridgeBaseRowStatus is active(1).
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE  "35.2.1.4d"
DEFVAL   { true }
::= { ieee8021SrpBridgeBaseEntry 1 }
ieee8021SrpBridgeBaseMsrpTalkerPruning OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-create
STATUS   current
DESCRIPTION
"The value of the talkerPruning parameter, which
controls the propagation of Talker declarations.
The value true(1) indicates that Talker attributes
are only declared on ports that have the Stream
destination_address registered in the MMRP MAC
Address Registration Entries. When false(2),
Talker attribute are declared on all egress ports
in the active topology.
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE  "12.22.1, 35.2.1.4b, 35.2.4.3.1"
DEFVAL   { false }
::= { ieee8021SrpBridgeBaseEntry 2 }
ieee8021SrpBridgeBaseMsrpMaxFanInPorts OBJECT-TYPE
SYNTAX   Unsigned32
MAX-ACCESS read-create
STATUS   current
DESCRIPTION
"The value of the msrpMaxFanInPorts parameter, which
limits the total number of ports on a Bridge that
are allowed to establish reservations for inbound
Streams. A value of zero (0) indicates no fan-in
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
limit is being specified and calculations involving
fan-in will only be limited by the number of MSRP
enabled ports.
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE  "12.22.1, 35.2.1.4f"
DEFVAL   { 0 }
::= { ieee8021SrpBridgeBaseEntry 3 }
ieee8021SrpBridgeBaseMsrpLatencyMaxFrameSize OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of msrpLatencyMaxFrameSize parameter
which is used in the calculation of the maximum
latency through a Bridge. The maximum size is
defined to be 2000 octets by default, but may be
set to a smaller or larger value dependent on the
particular Bridge configuration. This parameter
does not imply any type of policing of frame size,
it is only used in the latency calculations.
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE  "12.22.1, 35.2.1.4g"
DEFVAL   { 2000 }
::= { ieee8021SrpBridgeBaseEntry 4 }
ieee8021SrpBridgeBaseMsrpTalkerVlanPruning OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This parameter allows to limit the Talker declaration
to ports, that have the Stream's VLAN identifier
registered as a member in the VLAN Registration
Entries. The value true(1) indicates that Talker
declarations are only sent out on ports, that have the
Stream's VLAN identifier registered as a member in the
VLAN Registration Entries. When false(2), Talker
declarations are propagated according to the VLAN
spanning tree."
REFERENCE  "12.22.1, 35.2.1.4l"
DEFVAL   { false }
::= { ieee8021SrpBridgeBaseEntry 5 }
ieee8021SrpBridgeBaseMsrpMaxSRClasses OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute provides the maximum number of SR classes
supported by the Bridge."
REFERENCE  "12.22.1, 35.2.1.4m"
::= { ieee8021SrpBridgeBaseEntry 6 }
ieee8021SrpBridgePortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Ieee8021SrpBridgePortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table for SRP control and status information about
every Bridge Port. Augments the ieee8021BridgeBasePortTable."
::= { ieee8021SrpConfiguration 2 }
ieee8021SrpBridgePortEntry OBJECT-TYPE
SYNTAX Ieee8021SrpBridgePortEntry
MAX-ACCESS not-accessible
STATUS current
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
DESCRIPTION
"SRP control and status information for a Bridge Port."
AUGMENTS { ieee8021BridgeBasePortEntry }
::= { ieee8021SrpBridgePortTable 1 }
Ieee8021SrpBridgePortEntry ::=
SEQUENCE {
ieee8021SrpBridgePortMsrpEnabledStatus
TruthValue,
ieee8021SrpBridgePortMsrpFailedRegistrations
Counter64,
ieee8021SrpBridgePortMsrpLastPduOrigin
MacAddress,
ieee8021SrpBridgePortSrPvid
IEEE8021VlanIndex,
ieee8021SrpBridgePortMsrpTalkerPrunningPerPort
TruthValue
}
ieee8021SrpBridgePortMsrpEnabledStatus OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-create
STATUS   current
DESCRIPTION
"The administrative state of MSRP operation on this port. The
value true(1) indicates that MSRP is enabled on this port
in all VLANs as long as ieee8021BridgeMsrpEnabledStatus is
also true(1). A value of false(2) indicates that MSRP is
disabled on this port in all VLANs: any MSRP frames received
will be silently discarded, and no MSRP registrations will be
propagated from other ports. Setting this to a value of
true(1) will be stored by the agent but will only take
effect on the MSRP protocol operation if
ieee8021BridgeMsrpEnabledStatus
also indicates the value true(1). This object affects
all MSRP Applicant and Registrar state machines on this
port. A transition from false(2) to true(1) will
cause a reset of all MSRP state machines on this port.
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE  "35.2.1.4e"
DEFVAL   { true }
::= { ieee8021SrpBridgePortEntry 1 }
ieee8021SrpBridgePortMsrpFailedRegistrations OBJECT-TYPE
SYNTAX   Counter64
UNITS    "failed MSRP registrations"
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"The total number of failed MSRP registrations, for any
reason, in all VLANs, on this port.
Discontinuities in the value of the counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of ifCounterDiscontinuityTime
object of the associated interface (if any)."
REFERENCE  "10.7.12.1"
::= { ieee8021SrpBridgePortEntry 2 }
ieee8021SrpBridgePortMsrpLastPduOrigin OBJECT-TYPE
SYNTAX   MacAddress
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"The Source MAC Address of the last MSRP message
received on this port."
REFERENCE  "10.7.12.2"
::= { ieee8021SrpBridgePortEntry 3 }
ieee8021SrpBridgePortSrPvid OBJECT-TYPE
ISO/IEC/IEEE 8802-1Q:2024/Amd.36:2024(en)
IEEE Std 802.1Qcw™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 36: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing
SYNTAX   IEEE8021VlanIndex
MAX-ACCESS read-create
STATUS   current
DESCRIPTION
"The default VLAN ID that Streams are assigned to.
Talkers learn this VID from the SRP Domain attribute
and tag Streams accordingly.
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE  "35.2.2.8.3b"
DEFVAL   { 2 }
::= { ieee8021SrpBridgePortEntry 4}
ieee8021SrpBridgePortMsrpTalkerPrunningPerPort OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-create
STATUS   current
DESCRIPTION
"This parameter controls the forwarding behavior for
Talker declarations on
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...