ISO/IEC/IEEE 8802-1CB:2019/Amd 1:2023
(Amendment)Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 1CB: Frame replication and elimination for reliability — Amendment 1: Information model, YANG data model, and management information base module
Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 1CB: Frame replication and elimination for reliability — Amendment 1: Information model, YANG data model, and management information base module
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 1CB: Duplication de trame et son élimination pour la fiabilité — Amendement 1: Modèle d'information, modèle de données YANG et module de base d'informations de gestion
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/
STANDARD IEC/IEEE
8802-1CB
First edition
2019-02
AMENDMENT 1
2023-02
Information technology —
Telecommunications and information
exchange between systems — Local
and metropolitan area networks —
Specific requirements —
Part 1CB:
Frame replication and elimination for
reliability
AMENDMENT 1: Information model,
YANG data model, and management
information base module
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseaux locaux et métropolitains —
Exigences spécifiques —
Partie 1CB: Duplication de trame et son élimination pour la fiabilité
AMENDEMENT 1: Modèle d'information, modèle de données YANG et
module de base d'informations de gestion
Reference number
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
© IEEE 2022
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
© IEEE 2022
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
ii
© IEEE 2022 – All rights reserved
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
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 ISO/IEC documents should be noted. This document was drafted in accordance with
the editorial rules of the ISO/IEC Directives, Part 2 (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.
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. Details
of any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC list of patent
declarations received (see https://patents.iec.ch).
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-1CB:2019/Amd1 was prepared by the LAN/MAN of the IEEE Computer Society (as
TM
IEEE 802-1CBcv -2021) 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 2022 – All rights reserved iii
IEEE Std 802.1CBcv™-2021
(Amendment to IEEE Std 802.1CB™-2017)
IEEE Standard for
Local and metropolitan area networks—
Frame Replication and Elimination for Reliability
Amendment 1: Information Model, YANG Data
Model, and Management Information Base Module
Developed by the
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 8 December 2021
IEEE SA Standards Board
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Abstract: This amendment specifies YANG data models and MIB modules that allow configuration
and status reporting for bridges and end systems with the capabilities for Frame Replication and
Elimination for Reliability (FRER) and Stream identification.
Keywords: Bridged Local Area Networks, Bridges, Bridging, Frame Elimination, Frame ®
Replication, IEEE 802 , IEEE 802.1CB™, IEEE 802.1Q™, local area networks (LANs), MAC
Bridges, Redundancy, Time-Sensitive Networking, TSN, Virtual Bridged Local Area Networks
(virtual LANs)
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 18 February 2022. Printed in the United States of America.
IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and
Electronics Engineers, Incorporated.
PDF: ISBN 978-1-5044-8245-5 STD25138
Print: ISBN 978-1-5044-8246-2 STDPD25138
IEEE prohibits discrimination, harassment and bullying.
For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior
written permission of the publisher.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Important Notices and Disclaimers Concerning IEEE Standards
Documents
IEEE Standards documents are made available for use subject to important notices and legal disclaimers.
These notices and disclaimers, or a reference to this page (https://standards.ieee.org/ipr/disclaimers.html),
appear in all standards and may be found under the heading “Important Notices and Disclaimers Concerning
IEEE Standards Documents.”
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards
Documents
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE SA) Standards Board. IEEE develops its standards
through an accredited consensus development process, which brings together volunteers representing varied
viewpoints and interests to achieve the final product. IEEE Standards are documents developed by
volunteers with scientific, academic, and industry-based expertise in technical working groups. Volunteers
are not necessarily members of IEEE or IEEE SA, and participate without compensation from IEEE. While
IEEE administers the process and establishes rules to promote fairness in the consensus development
process, IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the
soundness of any judgments contained in its standards.
IEEE makes no warranties or representations concerning its standards, and expressly disclaims all
warranties, express or implied, concerning this standard, including but not limited to the warranties of
merchantability, fitness for a particular purpose and non-infringement. In addition, IEEE does not warrant or
represent that the use of the material contained in its standards is free from patent infringement. IEEE
standards documents are supplied “AS IS” and “WITH ALL FAULTS.”
Use of an IEEE standard is wholly voluntary. The existence of an IEEE Standard does not imply that there
are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to
the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and
issued is subject to change brought about through developments in the state of the art and comments
received from users of the standard.
In publishing and making its standards available, IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity, nor is IEEE undertaking to perform any duty owed by any
other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his
or her own independent judgment in the exercise of reasonable care in any given circumstances or, as
appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE
standard.
IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: THE
NEED TO PROCURE SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE
UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND
REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Translations
The IEEE consensus development process involves the review of documents in English only. In the event
that an IEEE standard is translated, only the English version published by IEEE is the approved IEEE
standard.
Official statements
A statement, written or oral, that is not processed in accordance with the IEEE SA Standards Board
Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its
committees and shall not be considered to be, nor be relied upon as, a formal position of IEEE. At lectures,
symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall
make it clear that the presenter's views should be considered the personal views of that individual rather than
the formal position of IEEE, IEEE SA, the Standards Committee, or the Working Group.
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE or IEEE SA. However, IEEE does not provide interpretations,
consulting information, or advice pertaining to IEEE Standards documents.
Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is
important that any responses to comments and questions also receive the concurrence of a balance of
interests. For this reason, IEEE and the members of its Societies and Standards Coordinating Committees
are not able to provide an instant response to comments, or questions except in those cases where the matter
has previously been addressed. For the same reason, IEEE does not respond to interpretation requests. Any
person who would like to participate in evaluating comments or in revisions to an IEEE standard is welcome
to join the relevant IEEE working group. You can indicate interest in a working group using the Interests tab
in the Manage Profile & Interests area of the IEEE SA myProject system. An IEEE Account is needed to
access the application.
Comments on standards should be submitted using the Contact Us form.
Laws and regulations
Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the
provisions of any IEEE Standards document does not constitute compliance to any applicable regulatory
requirements. Implementers of the standard are responsible for observing or referring to the applicable
regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not
in compliance with applicable laws, and these documents may not be construed as doing so.
Data privacy
Users of IEEE Standards documents should evaluate the standards for considerations of data privacy and
data ownership in the context of assessing and using the standards in compliance with applicable laws and
regulations.
1. Available at: https://development.standards.ieee.org/myproject-web/public/view.html#landing.
2. Available at: https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Copyrights
IEEE draft and approved standards are copyrighted by IEEE under US and international copyright laws.
They are made available by IEEE and are adopted for a wide variety of both public and private uses. These
include both use, by reference, in laws and regulations, and use in private self-regulation, standardization,
and the promotion of engineering practices and methods. By making these documents available for use and
adoption by public authorities and private users, IEEE does not waive any rights in copyright to the
documents.
Photocopies
Subject to payment of the appropriate licensing fees, IEEE will grant users a limited, non-exclusive license
to photocopy portions of any individual standard for company or organizational internal use or individual,
non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance
Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400; https://
www.copyright.com/. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.
Updating of IEEE Standards documents
Users of IEEE Standards documents should be aware that these documents may be superseded at any time
by the issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect.
Every IEEE standard is subjected to review at least every 10 years. When a document is more than 10 years
old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of
some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that
they have the latest edition of any IEEE standard.
In order to determine whether a given document is the current edition and whether it has been amended
through the issuance of amendments, corrigenda, or errata, visit IEEE Xplore or contact IEEE. For more
information about the IEEE SA or IEEE's standards development process, visit the IEEE SA Website.
Errata
Errata, if any, for all IEEE standards can be accessed on the IEEE SA Website. Search for standard number
and year of approval to access the web page of the published standard. Errata links are located under the
Additional Resources Details section. Errata are also available in IEEE Xplore. Users are encouraged to
periodically check for errata.
Patents
IEEE Standards are developed in compliance with the IEEE SA Patent Policy.
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the
existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has
3. Available at: https://ieeexplore.ieee.org/browse/standards/collection/ieee.
4. Available at: https://standards.ieee.org/standard/index.html.
5. Available at: https://standards.ieee.org/about/sasb/patcom/materials.html.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the
IEEE SA Website at https://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may
indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without
compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of
any unfair discrimination to applicants desiring to obtain such licenses.
Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their
own responsibility. Further information may be obtained from the IEEE Standards Association.
IMPORTANT NOTICE
IEEE Standards do not guarantee or ensure safety, security, health, or environmental protection, or ensure
against interference with or from other devices or networks. IEEE Standards development activities consider
research and information presented to the standards development group in developing any safety
recommendations. Other information about safety practices, changes in technology or technology
implementation, or impact by peripheral systems also may be pertinent to safety considerations during
implementation of the standard. Implementers and users of IEEE Standards documents are responsible for
determining and complying with all appropriate safety, security, environmental, health, and interference
protection practices and all applicable laws and regulations.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Participants
At the time this amendment was submitted to the IEEE SA Standards Board for approval, the IEEE 802.1
Working Group had the following membership:
Glenn Parsons, Chair
Jessy Rouyer, Vice-Chair
János Farkas, Chair, Time-Sensitive Networking Task Group
Stephan Kehrer, Editor
Astrit Ademaj Woojung Huh Maximilian Riegel
Ralf Assmann Satoko Itaya Silvana Rodrigues
Rudy Belliardi Yoshihiro Ito Atsushi Sato
Christian Boiger Michael Karl Frank Schewe
Paul Bottorff Randy Kelsey Michael Seaman
Radhakrishna Canchi Marcel Kiessling Maik Seewald
David Chen Gavin Lai Ramesh Sivakolundu
Feng Chen James Lawlis Johannes Specht
Paul Congdon Joao Lopes Marius Stanica
Lily Lv
Rodney Cummings Guenter Steindl
Josef Dorr Christophe Mangin Liyang Sun
Hesham Elbakoury Scott Mansfield Karim Traore
Anna Engelmann Kenichi Maruhashi Max Turner
Thomas Enzinger Olaf Mater Balazs Varga
Donald Fedyk David McCall Ganesh Venkatesan
Norman Finn Larry McMillan Tongtong Wang
Geoffrey Garner John Messenger Xinyuan Wang
Amrit Gopal Hiroki Nakano Karl Weber
Craig Gunther Bob Noseworthy Ludwig Winkel
Marina Gutierrez Hiroshi Ohue Jordon Woods
Stephen Haddock Donald R. Pannell Takahiro Yamaura
Mark Hantel Michael Potts Yue Yin
Jerome Henry Dieter Proell Nader Zein
Marc Holness Wei Qiu William Zhao
Daniel Hopf Helge Zinner
Karen Randall
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Stephan Kehrer Alon Regev
Christian Boiger Randy Kelsey Maximilian Riegel
Jessy Rouyer
Vern Brethour Stuart Kerry
Frank Schewe
William Byrd Evgeny Khorov
Michael Seaman
Paul Cardinal Yongbum Kim
Maik Seewald
Hyeong Ho Lee
Pin Chang
Eugene Stoudenmire
Diego Chiozzi Ting Li
Walter Struppler
Janos Farkas Christophe Mangin
Mitsutoshi Sugawara
Avraham Freedman Scott Mansfield
Bo Sun
Stephen Haddock Jonathon McLendon
David Tremblay
Marco Hernandez Satoshi Obara
Max Turner
Werner Hoelzl Glenn Parsons
John Vergis
Oliver Holland Bansi Patel
Stephen Webb
Marc Holness Arumugam Paventhan
Karl Weber
Pranav Jha Clinton Powell
Scott Willy
Lokesh Kabra Dieter Proell
Yu Yuan
Piotr Karocki R. K. Rannow Oren Yuen
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
When the IEEE SA Standards Board approved this standard on 8 December 2021, it had the following
membership:
Gary Hoffman, Chair
Jon Walter Rosdahl, Vice Chair
John D. Kulick, Past Chair
Konstantinos Karachalios, Secretary
Edward A. Addy Howard Li Mehmet Ulema
Doug Edwards Daozhuang Lin Lei Wang
Ramy Ahmed Fathy Kevin Lu F. Keith Waters
J. Travis Griffith Daleep C. Mohla Karl Weber
Thomas Koshy Chenhui Niu Sha Wei
Joseph L. Koepfinger* Damir Novosel Howard Wolfman
Annette Reilly Daidi Zhong
David J. Law
Dorothy Stanley
*Member Emeritus
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Introduction
This introduction is not part of IEEE Std 802.1CBcv-2021, IEEE Standard for Local and metropolitan area
networks—Frame Replication and Elimination for Reliability—Amendment 1: Information Model, YANG Data
Model, and Management Information Base Module.
This Standard defines an Information Model, a YANG Data Model, and a Management Information Base
Module.
This standard contains state-of-the-art material. The area covered by this standard is undergoing evolution.
Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, and
to incorporate new related material. Information on the current revision state of this and other IEEE 802
standards can be obtained from
Secretary, IEEE SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854
USA
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
Contents
1. Overview. 13
1.6 Introduction. 13
2. Normative references. 14
4. Acronyms and abbreviations . 15
5. Conformance. 16
5.8 Talker end system optional behaviors . 16
5.11 Listener end system optional behaviors. 16
5.14 Relay system optional behaviors . 16
7. Frame Replication and Elimination for Reliability. 17
7.4 Sequencing function . 17
7.4.1 Sequence generation function. 17
7.4.1.3 SequenceGenerationReset. 17
10. Frame Replication and Elimination for Reliability management . 18
10.3 Sequence generation table . 18
10.3.1 frerSeqGenEntry . 18
10.3.1.3 frerSeqGenReset . 18
11. Management Information Base (MIB) . 19
11.1 Internet Standard Management Framework . 19
11.2 Structure of the MIB . 19
11.2.1 Structure of the IEEE8021-STREAM-IDENTIFICATION-MIB . 21
11.2.2 Structure of the IEEE8021-FRER-MIB. 23
11.3 Relationship to other MIBs. 27
11.3.1 Relationship of the IEEE8021-STREAM-IDENTIFICATION-MIB to other MIBs . 27
11.3.2 Relationship of the IEEE8021-FRER-MIB to other MIBs. 28
11.4 Security considerations . 28
11.4.1 Security considerations of the IEEE8021-STREAM-IDENTIFICATION-MIB . 28
11.4.2 Security considerations of the IEEE8021-FRER-MIB. 28
11.5 MIB modules . 29
11.5.1 Definitions for the IEEE8021-STREAM-IDENTIFICATION-MIB . 29
11.5.2 Definitions for the IEEE8021-FRER-MIB. 50
12. YANG Data Model. 87
12.1 YANG Framework . 87
12.2 IEEE Std 802.1CB YANG model. 88
12.2.1 Stream Identification model. 88
12.2.2 Frame Replication and Elimination for Reliability model. 90
12.3 Structure of the YANG model . 93
12.3.1 Structure of the ieee802-dot1cb-stream-identification YANG module. 94
12.3.2 Structure of the ieee802-dot1cb-frer YANG module . 95
12.4 Relationship to other YANG modules. 96
12.4.1 IEEE 802 Types Module. 96
12.4.2 IEEE 802.1Q Types Module. 96
12.4.3 IETF Inet Types Module. 96
12.4.4 IETF Interfaces YANG Module . 96
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
12.4.5 IEEE 802.1CB Stream Identification Types YANG module . 96
12.4.6 IEEE 802.1CB Stream Identification YANG module. 96
12.4.7 IEEE 802.1CB FRER Types YANG module . 96
12.5 Security Considerations . 97
12.5.1 Security Considerations of the ieee802-dot1cb-stream-identification YANG module 97
12.5.2 Security Considerations of the ieee802-dot1cb-frer YANG module. 97
12.6 Definition of 802.1CB YANG modules . 97
12.6.1 YANG data scheme tree definitions . 97
12.6.1.1 YANG data scheme definition for ieee802-dot1cb-stream-identification YANG
module . 98
12.6.1.2 YANG data scheme definition for ieee802-dot1cb-frer YANG module . 99
12.6.2 YANG data module definitions. 103
12.6.2.1 Definition for the ieee802-dot1cb-stream-identification-types YANG
module . 103
12.6.2.2 Definition for the ieee802-dot1cb-stream-identification YANG module. 105
12.6.2.3 Definition for the ieee802-dot1cb-frer-types YANG module. 123
12.6.2.4 Definition for the ieee802-dot1cb-frer YANG module . 125
Annex A (normative) Protocol Implementation Conformance Statement (PICS) proforma. 153
A.2 PICS proforma for Frame Replication and Elimination for Reliability. 153
A.2.1 Major capabilities/options. 153
A.2.8 Management Information Base (MIB) . 153
A.2.9 YANG. 154
Annex D (informative) Bibliography . 155
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Standard for
Local and metropolitan area networks—
Frame Replication and Elimination for Reliability
Amendment 1: Information Model, YANG Data
Model, and Management Information Base Module
(This amendment is based on IEEE Std 802.1CB™-2017.)
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 italic. 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-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model, and Management Information Base Module
1. Overview
1.6 Introduction
Insert new text at the end of 1.6 as follows:
This standard also specifies a Unified Modeling Language (UML) based information model for the
capabilities currently specified in Clause 9 and Clause 10 of this standard. A YANG data model and a
Management Information Base (MIB) module, both based on that UML model, are provided in order to
support configuration and status reporting.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
2. Normative references
Insert the following references in alphanumeric order in Clause 2:
IETF RFC 2578 (STD 58), Structure of Management Information Version 2 (SMIv2), McCloghrie, K.,
D. Perkins, and J. Schoenwaelder, Apr. 1999.
IETF RFC 2579 (STD 58), Textual Conventions for SMIv2, McCloghrie, K., D. Perkins, and
J. Schoenwaelder, Apr. 1999.
IETF RFC 2580 (STD 58), Conformance Statements for SMIv2, McCloghrie, K., D. Perkins, and
J. Schoenwaelder, Apr. 1999.
IETF RFC 3410, Introduction and Applicability Statements for Internet-Standard Management Framework,
Case, J., R. Mundy, D. Partain, and B. Stewart, Dec. 2002.
IETF RFC 8343 (proposed standard), A YANG Data Model for Interface Management, Bjorklund, M., Mar.
2018.
IETF RFCs are available from the Internet Engineering Task Force (https://www.rfc-archive.org/).
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
4. Acronyms and abbreviations
Insert the following abbreviations in alphanumeric order in Clause 4:
MIB Management Information Base
NETCONF Network Configuration Protocol
SMI Structure of Management Information
SNMP Simple Network Management Protocol
YANG Yet Another Next Generation
UML Unified Modeling Language
YANG is best viewed as a name, not an acronym
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model, and Management Information Base Module
5. Conformance
5.8 Talker end system optional behaviors
Change list items f) and g) in 5.8 as follows:
f) The PRP sequence trailer (7.10); and/or
g) Additional types of Sequence encode/decode functions.;
h) Support SMIv2 MIB modules for the management of talker end system functions (Clause 11) as
required by item e in 5.6; and/or
i) Support YANG modules for the management of talker end system functions (Clause 12) as required
by item e in 5.6.
5.11 Listener end system optional behaviors
Change list items g) and h) in 5.11 as follows:
g) Additional types of Sequence encode/decode functions; and/or
h) At least two instances of Individual recovery functions (7.5), each using the
VectorRecoveryAlgorithm (7.4.3.4).;
i) Support SMIv2 MIB modules for the management of listener end system functions (Clause 11) as
required by item f in 5.9; and/or
j) Support YANG modules for the management of listener end system functions (Clause 12) as
required by item f in 5.9.
5.14 Relay system optional behaviors
Change list items g) to j) in 5.14 as follows:
g) Additional types of Sequence encode/decode functions; and/or
h) Some or all of the functions in 5.12 or 5.13 as both in- and out-facing functions.;
i) At least two instances of Individual recovery functions (7.5), each using the
VectorRecoveryAlgorithm (7.4.3.4).;
j) Autoconfiguration (7.11) and the associated managed objects (10.7).;
k) Support SMIv2 MIB modules for the management of relay systems functions (Clause11) as
required by item g in 5.12; and/or
l) Support YANG modules for the management of relay systems functions (Clause 12) as required by
item g in 5.12.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
7. Frame Replication and Elimination for Reliability
7.4 Sequencing function
7.4.1 Sequence generation function
7.4.1.3 SequenceGenerationReset
Change 7.4.1.3 as follows:
The SequenceGenerationReset function is called whenever the BEGIN event occurs (item a in 7.4.1.1) or
the value True is written to the frerSeqRcvyResetfrerSeqGenReset managed object (10.4.1.410.3.1.3). It
resets GenSeqNum (7.4.1.2.2) and increments frerCpsSeqGenResets (10.8.2).
void SequenceGenerationReset () {
GenSeqNum = 0;
frerCpsSeqGenResets = frerCpsSeqGenResets + 1;
}
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
10. Frame Replication and Elimination for Reliability management
10.3 Sequence generation table
10.3.1 frerSeqGenEntry
Insert subclause 10.3.1.3 after 10.3.1.2, as follows:
10.3.1.3 frerSeqGenReset
A Boolean object indicating that the Sequence generation function (7.4.1) is to be reset by calling its
corresponding SequenceGenerationReset function (7.4.1.3). Writing the value True to frerSeqGenReset
triggers a reset; writing the value False has no effect. When read, frerSeqGenReset always returns the value
False.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
Insert Clause 11 and Clause 12 after Clause 10 as follows:
11. Management Information Base (MIB)
This clause contains a complete SMIv2 MIB set for all features of this standard.
11.1 Internet Standard Management Framework
The MIBs in this standard are designed to operate in a manner consistent with the principles of the Internet
Standard Management Framework, which describes the separation of a data modeling language (for
example, SMIv2) from content-specific data models (for example, the LLDP remote systems MIB), and
from messages and protocol operations used to manipulate the data (for example, SNMPv3).
For a detailed overview of the documents that describe the current Internet Standard Management
Framework, please refer to section 7 of IETF RFC 3410 (2002).
Managed objects are accessed via a virtual information store, termed the Management Information Base or
MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information
(SMI). This clause specifies a MIB module that is compliant to the SMIv2, which is described in IETF RFC
2578 (STD 58), IETF RFC 2579 (STD 58), and IETF RFC 2580 (STD 58).
11.2 Structure of the MIB
The IEEE Std 802.1CB MIB is divided into a number of MIB modules. A summary of the modules
contained in this clause is represented in Table 11-1. The general MIB table structures for the MIB modules
contained in this clause are illustrated in Figure 11-1.
Table 11-1—Structure of the MIB modules
Module Subclause References Notes
IEEE8021-STREAM- 11.5.1 Clause 9 MIB model for Stream identification.
IDENTIFICATION-MIB
IEEE8021-FRER-MIB 11.5.2 Clause 10 MIB model for FRER.
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
IEEE8021-STREAM-
IEEE8021-FRER-MIB
IDENTIFICATION-MIB
StreamIdentification SequenceGeneration
Table Table
NullStream SequenceGeneration
IdentificationTable HandleListTable
SrcMacVlan SequenceRecovery
IdentificationTable Table
ActiveDestMacVlan SequenceRecovery
IdentificationTable HandleListTable
IpStream SequenceRecoveryPort
IdentificationTable HandleListTable
StreamIdInFacOutput SequenceIdentification
PortHandleListTable Table
StreamIdOutFacOutpu SequenceIdentification
PortHandleListTable HandleListTable
StreamIdInFacInput
StreamSplitTable
PortHandleListTable
StreamIdOutFacInput StreamSplitInput
PortHandleListTable HandleListTable
PerPortPerStream StreamSplitOutput
CountersTable HandleListTable
PerPort SequenceAutoconfig
CountersTable Table
SequenceAutoconfig
ReceivePortHandleList
Table
SequenceAutoconfig
VlanListTable
SequenceAutoconfig
RecoveryPort
HandleListTable
OutputAutoconfigTable
OutputAutoconfigPort
HandleListTable
PerPortPerStream
CountersTable
PerPort
CountersTable
Figure 11-1—MIB modules structure
ISO/IEC/IEEE 8802-1CB:2019/Amd.1:2023(E)
IEEE Std 802.1CBcv-2021
IEEE Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability—
Amendment 1: Information Model, YANG Data Model and Management Information Base Module
11.2.1 Structure of the IEEE8021-STREAM-IDENTIFICATION-MIB
The IEEE8021-STREAM-IDENTIFICATION-MIB module is divided into a number of branches
(e.g., subtrees). Each subtree is organized as a set of related objects. Where appropriate, the corresponding
Clause 9 management reference is also included.
Table 11-2 indicates the structure of the IEEE8021-STREAM-IDENTIFICATION-MIB module.
Table 11-2—IEEE8021-STREAM-IDENTIFICATION-MIB structure and
relationship to this standard
Clause 11 MIB table/object Reference
ieee8021StreamIdStreamIdentificationTable 9.1,
9.1.1
ieee8021StreamIdStreamIdentificationIndex —
ieee8021StreamIdStreamIdIdentificationType —
ieee8021StreamIdStreamIdIdentificationTypeOUI —
ieee8021StreamIdStreamIdIdentificationCustomType —
ieee8021StreamIdStreamIdIdentificationCustomTypeOUI —
ieee8021StreamIdStreamIdIdentificationTypeSelect —
ieee8021StreamIdStreamIdIdentificationTypeSelect —
ieee8021StreamIdStreamIdInFacOutputPortList —
ieee8021StreamIdStreamIdOutFacOutputPortList —
ieee8021StreamIdStreamIdInFacInputPortList —
ieee8021StreamIdStreamIdOutFacInputPortList —
ieee8021StreamIdAutoConfigured —
ieee8021StreamIdLanPathId —
ieee8021StreamIdStatus —
ieee8021StreamIdNullStreamIdentificationTable 9.1.2
ieee8021StreamIdCpeNullDownDestMac —
ieee8021StreamIdCPENullDownTagged —
ieee8021StreamIdCpeNullDownVlan —
ieee8021StreamIdSrcMacVlanIdentificationTable 9.1.3
ieee8021Str
...
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...