ISO/IEC/IEEE 8802-1Q:2016/Amd 6:2019

Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 1Q: Bridges and bridged networks - Amendment 6: Per-stream filtering and policing

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 1Q: Ponts et réseaux pontés — Amendement 6: Régulation & filtrage par flux

General Information

• Status: Withdrawn
• Publication Date: 13-Feb-2019
• Withdrawal Date: 13-Feb-2019
• ICS: 35.110 - Networking
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 21-Aug-2020
• Completion Date: 30-Oct-2025

Relations

• Amends: ISO/IEC/IEEE 8802-1Q:2016 - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 1Q: Bridges and bridged networks
• Effective Date: 03-Jul-2021
• Revised: ISO/IEC/IEEE 8802-1Q:2020 - Telecommunications and exchange between information technology systems - Requirements for local and metropolitan area networks - Part 1Q: Bridges and bridged networks
• Effective Date: 23-Apr-2020

Standards Content (Sample)

INTERNATIONAL ISO/IEC/
STANDARD IEEE
8802-1Q
First edition
2016-03-15
AMENDMENT 6
2019-02
Information technology —
Telecommunications and information
exchange between systems — Local
and metropolitan area networks —
Specific requirements —
Part 1Q:
Bridges and bridged networks
AMENDMENT 6: Per-stream filtering and
policing
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseaux locaux et métropolitains —
Exigences spécifiques —
Partie 1Q: Ponts et réseaux pontés
AMENDEMENT 6: Régulation & filtrage par flux
Reference number
ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
©
IEEE 2017
ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)

©  IEEE 2017
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 either ISO or IEEE at
the respective address below or ISO’s member body in the country of the requester.
ISO copyright office  Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8  3 Park Avenue, New York
CH-1214 Vernier, Geneva  NY 10016-5997, USA
Phone: [phone]
Fax: [phone]
Email: [e-mail]  Email: [e-mail]
Website: www.iso.org  Website: www.ieee.org
Published in Switzerland
© IEEE 2017 – All rights reserved
ii
ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(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. In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1.
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 documents should be noted (see www.iso.org/directives).
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).
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.
ISO/IEC/IEEE 8802‐1Q:2016/Amd.6 was prepared by the LAN/MAN of the IEEE Computer Society
(as IEEE Std 802.1Qci‐2017) 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 SC6, Telecommunications and information exchange between
systems.
A list of all parts in the ISO/IEC/IEEE 8802 series can be found on the ISO website.
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.
© IEEE 2017 – All rights reserved
iii
IEEE Std 802.1Qci™-2017
(Amendment to
IEEE Std 802.1Q™-2014
as amended by
IEEE Std 802.1Qca™-2015,
IEEE Std 802.1Qcd™-2015,
IEEE Std 802.1Q-2014/Cor 1-2015,
IEEE Std 802.1Qbv™-2015,
IEEE Std 802.1Qbu™-2016, and
IEEE Std 802.1Qbz™-2016)
IEEE Standard for
Local and metropolitan area networks—
Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
Sponsor
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 14 February 2017
IEEE-SA Standards Board
ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
Abstract: Enhancements to the forwarding process that support per-stream filtering and policing
are provided in this amendment to IEEE Std 802.1Q-2014. ®
Keywords: Bridged Local Area Networks, IEEE 802 , IEEE 802.1Q™, IEEE Std 802.1Qbu™,
IEEE 802.1Qbv™, IEEE Std 802.1Qbz™, IEEE 802.1Qca™, IEEE 802.1Qcd™, IEEE 802.1Qci™,
local area networks (LANs), MAC Bridges, metropolitan area networks, per-stream filtering and
policing, PSFP, scheduled traffic, Time-Sensitive Networking, 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 6 October 2017. 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.
Print: ISBN 978-1-5044-4051-6 STD22606
PDF: ISBN 978-1-5044-4052-3 STDPD22606
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.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
Important Notices and Disclaimers Concerning IEEE Standards Documents
IEEE documents are made available for use subject to important notices and legal disclaimers. These notices
and disclaimers, or a reference to this page, appear in all standards and may be found under the heading
“Important Notices and Disclaimers Concerning IEEE Standards Documents.” They can also be obtained on
request from IEEE or viewed at http://standards.ieee.org/IPR/disclaimers.html.
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards
Documents
IEEE Standards documents (standards, recommended practices, and guides), both full-use and trial-use, are
developed within IEEE Societies and the Standards Coordinating Committees of the IEEE Standards
Association (“IEEE-SA”) Standards Board. IEEE (“the Institute”) develops its standards through a
consensus development process, approved by the American National Standards Institute (“ANSI”), which
brings together volunteers representing varied viewpoints and interests to achieve the final product. IEEE
Standards are documents developed through scientific, academic, and industry-based technical working
groups. Volunteers in IEEE working groups are not necessarily members of the Institute 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 Standards do not guarantee or ensure safety, security, health, or environmental protection, or ensure
against interference with or from other devices or networks. 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.
IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and
expressly disclaims all warranties (express, implied and statutory) not included in this or any other
document relating to the standard, including, but not limited to, the warranties of: merchantability; fitness
for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of
material. In addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort.
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:
PROCUREMENT OF 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.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(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 should be considered 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, or 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 his or her views should be considered the personal views of that individual rather than the
formal position of IEEE.
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE. However, IEEE does not provide 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 revisions to an IEEE
standard is welcome to join the relevant IEEE working group.
Comments on standards should be submitted to the following address:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854 USA
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 imply 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.
Copyrights
IEEE draft and approved standards are copyrighted by IEEE under U.S. 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.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
Photocopies
Subject to payment of the appropriate fee, 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; [phone]. 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 ten years. When a document is more than ten 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 the IEEE-SA Website at http://
ieeexplore.ieee.org/ or contact IEEE at the address listed previously. For more information about the IEEE-
SA or IEEE’s standards development process, visit the IEEE-SA Website at http://standards.ieee.org.
Errata
Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: http://
standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata
periodically.
Patents
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
filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-
SA Website at http://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
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
Participants
At the time of approval of this standard, the IEEE 802.1 Working Group had the following membership:
Glenn Parsons, Chair
John Messenger, Vice Chair
János Farkas, Chair, Time-Sensitive Networking Task Group
Tony Jeffree, Editor
SeoYoung Baek Marc Holness Dan Romascanu
Shenghua Bao Lu Huang Jessy Rouyer
Jens Bierschenk Michael Johas Teener Eero Ryytty
Steinar Bjørnstad Hal Keen Soheil Samii
Christian Boiger Stephan Kehrer Behcet Sarikaya
Paul Bottorff Philippe Klein Frank Schewe
David Chen Jouni Korhonen Michael Seaman
Feng Chen Yizhou Li Johannes Specht
Weiying Cheng Christophe Mangin Wilfried Steiner
Rodney Cummings Tom McBeath Patricia Thaler
Norman Finn James McIntosh Paul Unbehagen
Geoffrey Garner Tero Mustala Hao Wang
Eric W. Gray Hiroki Nakano Karl Weber
Craig Gunther Bob Noseworthy Brian Weis
Marina Gutierrez Donald R. Pannell Jordon Woods
Stephen Haddock Walter Pienciak Nader Zein
Mark Hantel Helge Zinner
Michael Potts
Patrick Heffernan Karen Randall Juan Carlos Zuniga
Maximilian Riegel
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Marco Hernandez Jeffrey Moore
Richard Alfvin Werner Hoelzl Charles Moorwood
Butch Anton C. Huntley Matthew Mora
Michael Newman
Stefan Aust Noriyuki Ikeuchi
Nick S. A. Nikjoo
Christian Boiger Sergiu Iordanescu
Paul Nikolich
Atsushi Ito
Nancy Bravin
Satoshi Obara
Ashley Butterworth Raj Jain
David Olsen
William Byrd Tony Jeffree
Bansi Patel
Juan Carreon Michael Johas Teener
Alon Regev
Yesenia Cevallos Piotr Karocki
Maximilian Riegel
David Chalupsky Stuart Kerry
Robert Robinson
Keith Chow Yongbum Kim
Osman Sakr
János Farkas John Lemon
Frank Schewe
Norman Finn Jon Lewis
Michael Seaman
Michael Fischer Arthur H. Light
Thomas Starai
Yukihiro Fujimoto Michael Lynch
Walter Struppler
Joel Goergen Elvis Maculuba
Mark-Rene Uchida
Eric W. Gray Roger Marks
Prabodh Varshney
Randall Groves Arthur Marris
George Vlantis
Craig Gunther Jonathon Mclendon
Khurram Waheed
Stephen Haddock Richard Mellitz
Stephen Webb
Mark Hantel Michael Montemurro
Oren Yuen
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
When the IEEE-SA Standards Board approved this standard on 14 February 2017, it had the following
membership:
Jean-Philippe Faure, Chair
Vacant position, Vice Chair
John D. Kulick, Past Chair
Konstantinos Karachalios, Secretary
Chuck Adams Michael Janezic Robby Robson
Masayuki Ariyoshi Thomas Koshy Dorothy Stanley
Ted Burse Joseph L. Koepfinger* Adrian Stephens
Mehmet Ulema
Stephen Dukes Kevin Lu
Phil Wennblom
Doug Edwards Daleep Mohla
Howard Wolfman
J. Travis Griffith Damir Novosel
Ronald C. Petersen Yu Yuan
Gary Hoffman
Annette D. Reilly
*Member Emeritus
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
Introduction
This introduction is not part of IEEE Std 802.1Qci-2017, IEEE Standard for Local and metropolitan area networks—
Bridges and Bridged Networks—Amendment 28: Per-Stream Filtering and Policing.
This amendment to IEEE Std 802.1Q-2014 provides enhancements to the forwarding process that support
per-stream filtering and policing.
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 may be obtained from
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854-4141
USA
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
Contents
1. Overview. 13
1.3 Introduction. 13
2. Normative references. 14
4. Abbreviations. 15
5. Conformance. 16
5.4 VLAN Bridge component requirements. 16
5.13 MAC Bridge component requirements. 16
5.27 End-station requirements—PSFP . 16
8. Principles of bridge operation. 17
8.6 The Forwarding Process . 17
12. Bridge management . 25
12.31 Managed objects for per-stream filtering and policing. 25
17. Management Information Base (MIB) . 31
17.2 Structure of the MIB . 31
17.3 Relationship to other MIBs. 34
17.4 Security considerations . 34
17.7 MIB modules . 36
Annex A (normative) PICS proforma—Bridge implementations . 60
A.5 Major capabilities . 60
A.14 Bridge management . 60
A.24 Management Information Base (MIB) . 60
A.45 Per-stream filtering and policing .61
Annex B (normative) PICS proforma—Bridge implementations . 62
B.5 Major capabilities . 62
B.16 Per-stream filtering and policing .62
Annex U (informative) Bibliography . 63
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 26: Per-Stream Filtering and Policing
List of figures
Figure 8-11 Forwarding process functions . 17
Figure 8-12 Per-stream filtering and policing. 18
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
List of tables
Table 8-7 Stream gate control operations . 21
Table 8-8 Scheduled Traffic and PSFP procedures/variables. 22
Table 12-30 The Stream Parameter Table. 25
Table 12-31 Stream Filter Instance Table . 26
Table 12-32 The Stream Gate Instance Table. 28
Table 12-33 The Flow Meter Instance Table . 30
Table 17-30 IEEE8021-PSFP-MIB Structure and relationship to this standard. 31
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
IEEE Standard for
Local and metropolitan area networks—
Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
(This amendment is based on IEEE Std 802.1Q™-2014 as amended by IEEE Std 802.1Qca™-2015,
IEEEStd 802.1Qcd™-2015, IEEE Std 802.1Q-2014/Cor 1-2015, IEEEStd 802.1Qbv™-2015,
IEEE Std 802.1Qbu™-2016, and IEEE Std 802.1Qbz™-2016.)
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.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
1. Overview
1.3 Introduction
Insert the following item at the end of lettered list, renumbering as necessary:
ch) This standard specifies protocols, procedures, and managed objects that allow for the filtering and
policing of individual traffic streams.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
2. Normative references
Insert the following references in alphanumeric order:
IEEE Std 802.1CB™, IEEE Standard for Local and Metropolitan Area Networks—Frame Replication and
Elimination for Reliability.
MEF Technical Specification 10.3 (MEF 10.3), Ethernet Service Attributes Phase 3.
Delete the reference to MEF 10.3 from the Bibliography [B45] and amend references to it in the text
accordingly.
MEF technical specifications are available from the MEF website (http://www.mef.net).
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
4. Abbreviations
Insert the following abbreviations in alphanumeric order:
IPV internal priority value specification
PSFP per-stream filtering and policing
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
5. Conformance
5.4 VLAN Bridge component requirements
5.4.1 VLAN Bridge component options
Insert new subclause 5.4.1.8 as shown, renumbering as necessary:
5.4.1.8 Per-stream filtering and policing (PSFP) requirements
A VLAN Bridge component implementation that conforms to the provisions of this standard for PSFP shall:
a) Support PSFP as specified in 8.6.5.1 and 8.6.6.1.
b) Support the state machines for stream gate control as specified in 8.6.10.
c) Support the management entities for PSFP as specified in 12.31.
5.13 MAC Bridge component requirements
5.13.1 MAC Bridge component options
Insert new subclause 5.13.1.1 as shown, renumbering as necessary:
5.13.1.1 Per-stream filtering and policing (PSFP) requirements
A MAC Bridge component implementation that conforms to the provisions of this standard for PSFP shall:
a) Support PSFP as specified in 8.6.5.1 and 8.6.6.1.
b) Support the state machines for stream gate control as specified in 8.6.10.
c) Support the management entities for PSFP as specified in 12.31.
Insert the following new subclause at the end of Clause 5, renumbering as necessary:
5.27 End-station requirements—PSFP
An end-station implementation that conforms to the provisions of this standard for PSFP shall:
a) Support PSFP as specified in 8.6.5.1 and 8.6.6.1.
b) Support the state machines for stream gate control as specified in 8.6.10.
c) Support the management entities for PSFP as specified in 12.31.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
8. Principles of bridge operation
8.6 The Forwarding Process
Replace Figure 8-11 with the following figure. The effect of this replacement is to change “Ingress
(8.6.2)” to “Ingress filtering (8.6.2)” and “Egress (8.6.4)” to “Egress filtering (8.6.4)” to match the
subclause headings.
Reception Port
Reception Port
State
Active topology enforcement (8.6.1)
Ingress filtering (8.6.2)
Filtering
Frame filtering (8.6.3)
Database
Transmission
Port State
Egress filtering (8.6.4)
Flow metering (8.6.5)
Queuing frames (8.6.6)
Queue management (8.6.7) Queue management (8.6.7)
Transmission selection (8.6.8)
Transmission Port
Figure 8-11—Forwarding process functions
8.6.5 Flow classification and metering
Insert new list item e) immediately following list item d), and change the sentence immediately following
new item e), renumbering following list items, as shown:
e) connection_identifier
Item c), specifying a VID value, is not applicable to VLAN-unaware MAC Relays. Item e), specifying a
connection_identifier, is only applicable to bridges that support PSFP.
Insert new subclause 8.6.5.1, Figure 8-12, and Table 8-5 as shown, renumbering subsequent figures and
tables as necessary:
8.6.5.1 Per-stream filtering and policing
A Bridge or an end station may support PSFP capabilities that allow filtering and policing decisions, and
subsequent frame queuing decisions (8.6.6.1), to be made on a per-stream basis for received frames.
Support of PSFP requires implementation of the Stream identification function specified in Clause 6 of
IEEE Std 802.1CB, as the stream_handle provided by this function is used in the policing and queuing
decisions taken by PSFP.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
NOTE—The stream_handle specified in Clause 6 of IEEE Std 802.1CB is a sub-parameter of the connection_identifier
parameter of the ISS.
PSFP is supported by the following tables:
a) Stream filter instance table (8.6.5.1.1)
b) Stream gate instance table (8.6.5.1.2)
c) Flow meter instance table (8.6.5.1.3)
The relationship between these tables is illustrated in Figure 8-12. The tables and their parameters can be
modified by management as specified in 12.31.
Egress filtering (8.6.4)
Gate 9
Stream ID 1 Stream ID 2 Stream ID 3 Stream ID N
control list
Gate 1
Priority 3 Priority 3 Priority * Priority 2
control list
Gate ID 1 Gate ID 1 Gate ID 5 Stream
Gate ID 9
Filters
Filters Filters Filters
Filters
T00: o,5
Meter ID 1 Meter ID 5 Meter ID 7 Meter ID 5
T01: C,5
Counters Counters Counters Counters
T02: o,4
T03: C,4
T04: o,3
Gate ID 1 Gate ID 5 Gate ID 9 Gate ID P T05: C,3
Stream
gate = C gate = o gate = o gate = C T06: o,6
Gates
IPV = 3 IPV = 2 IPV = 5 IPV = 6 T07: C,6
........
T78: o,1
T79: C,1
Flow
Meter ID1 Meter ID 5 Meter ID7 Meter ID Q
Meters
C=closed,
o=open
N=IPV
Queuing frames (8.6.6)
KEY
Stream ID: stream identifier specification (8.6.5.1.1)
Gate ID: stream gate instance identifier (8.6.5.1.1, 8.6.5.1.2)
Meter ID: flow meter instance identifier (8.6.5.1.1, 8.6.5.1.3)
Figure 8-12—Per-stream filtering and policing
8.6.5.1.1 Stream filter instance table
The stream filter instance table consists of an ordered list of stream filters that determine the filtering and
policing actions that are to be applied to frames received on a specific stream. Each stream filter contains the
following elements:
a) A stream filter instance identifier. This is an integer value that uniquely identifies the filter instance,
and acts as an index to the table. The ordering of the identifier values defines the ordering of the list
of stream filters; smaller identifier values appear earlier in the ordered list.
b) A stream_handle specification. This can be either of the following:
1) A single stream_handle value, as specified in IEEE Std 802.1CB.
2) A wild-card value that matches any stream_handle value.
c) A priority specification. This can be either of the following:
1) A single priority value.
2) A wild-card value that matches any priority value.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
d) A stream gate instance identifier. Identifies the stream gate instance (8.6.5.1.2) that is used by the
stream filter. A stream gate can be in one of two states:
1) Open: Frames pass through the gate.
2) Closed: Frames do not pass through the gate.
e) Zero or more filter specifications. The actions specified in a filter specification can result in a frame
passing or failing the specified filter. Frames that fail a filter are discarded. The filter specification
can include other actions, such as setting the drop_eligible parameter to TRUE. The following filter
specifications are currently defined:
1) Maximum SDU size. Frames that exceed this SDU size do not pass the stream filter; frames that
do not exceed this SDU size can pass the stream filter if all other filter conditions are met.
NOTE 1—The Maximum SDU size is defined per stream and can therefore differ from the queueMaxSDU specified in
8.6.8.4 of IEEE Std 802.1Qbv. As queueMaxSDU is applied after the stream filters, it is possible that a frame that passes
the Maximum SDU size stream filter will later be discarded because its SDU size exceeds queueMaxSDU.
2) Flow meter instance identifier. The identifier of an instance of a flow metering function as
specified in 8.6.5. The flow meter instance is an index into a flow meter instance table
(8.6.5.1.3) that specifies the operating parameters for each flow meter instance. Flow metering
is always applied after any other filter specifications that could result in frame discard.
f) Frame counters
1) A count of frames matching both the stream_handle and priority specifications.
2) A count of frames that passed the stream gate.
3) A count of frames that did not pass the stream gate.
4) A count of frames that passed the Maximum SDU size filter.
5) A count of frames that did not pass the Maximum SDU size filter.
6) A count of frames that were discarded as a result of the operation of the flow meter.
g) A StreamBlockedDueToOversizeFrameEnable parameter, which takes the value TRUE or FALSE.
A value of TRUE indicates that the StreamBlockedDueToOversizeFrame function is enabled; a
value of FALSE indicates that the StreamBlockedDueToOversizeFrame function is disabled. The
default value of StreamBlockedDueToOversizeFrameEnable is FALSE.
h) A StreamBlockedDueToOversizeFrame parameter, which takes the value TRUE or FALSE. If
StreamBlockedDueToOversizeFrameEnable is TRUE,a value of TRUE in
StreamBlockedDueToOversizeFrame indicates that all frames are to be dropped (i.e., the stream
filter behaves as it would if the maximum SDU size were to be set to 0 octets). If
StreamBlockedDueToOversizeFrame is FALSE, it has no effect. The default value of
StreamBlockedDueToOversizeFrame is FALSE; if any frame is discarded because it exceeds the
Maximum SDU size for the stream, then StreamBlockedDueToOversizeFrame is set TRUE.
The value of the stream_handle and priority parameters associated with a received frame determine which
stream filter is selected by the frame, and therefore what combination of filtering and policing actions is
applied to the frame. If the stream_handle and priority parameters associated with a received frame match
more than one stream filter, the stream filter that is selected is the one that appears earliest in the ordered list.
If a received frame’s stream_handle and priority does not match any of the stream filters in the table, the
frame is processed as would be the case if PSFP was not supported.
NOTE 2—The use of stream identifier and priority, along with the wild-carding rules previously stated, allow
configuration possibilities that go beyond PSFP as implied by the subclause title; for example, per-priority filtering and
policing, or per-priority per-ingress port filtering and policing can be configured using these rules.
NOTE 3—If it is desired to discard frames that do not match any other stream filter, rather than such frames being
processed without filtering, this can be achieved by placing a stream filter at the end of the table, in which the
stream_handle and priority are both wild-carded (set to the null value), and where the stream gate instance identifier
points at a stream gate that is permanently closed.
© IEEE 2017 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2016/Amd.6:2019(E)
IEEE Std 802.1Qci-2017
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks—
Amendment 28: Per-Stream Filtering and Policing
8.6.5.1.2 Stream gate instance table
The stream gate instance table contains a set of parameters for each stream gate instance. The parameters for
each stream gate instance are as follows:
a) A Stream gate instance identifier. An integer value identifying the stream gate instance.
b) An operational and an administrative stream gate state (8.6.10.4, 8.6.10.5, 12.31.3). A stream gate
can be in one of two states:
1) Open: Frames are permitted to pass through the gate.
2) Closed: Frames are not permitted to pass through the gate.
c) An operational and an administrative internal priority value specification (IPV, 8.6.10.6, 8.6.10.7,
12.31.3). An IPV can be either of the following:
1) The null value. For a frame that passes through the gate, the priority value associated with the
frame is used to determine the frame’s traffic class, using the Traffic Class Table as specified in
8.6.6.
2) An internal priority value. For a frame that passes through the gate, the IPV is used, in place of
the priority value associated with the frame, to determine the frame’s traffic class, using the
Traffic Class Table as specified in 8.6.6.
NOTE 1—A use case for the ability to assign internal priority values can be found in IEEE Std 802.1Qch™ [B1].
d) A GateClosedDueToInvalidRxEnable parameter, which takes the value TRUE or FALSE. A value
of TRUE indicates that the GateClosedDueToInvalidRx function is enabled; a value of FALSE
indicates that the GateClosedDueToInvalidRx function is disabled. The default value of
GateClosedDueToInvalidRxEnable is FALSE.
e) A GateClosedDueToInvalidRx parameter, which takes the value TRUE or FALSE. If
GateClosedDueToInvalidRxEnable is TRUE, a value of TRUE in GateClosedDueToInvalidRx
indicates that all frames are dropped (i.e., the gate behaves as if the operational stream gate state is
Closed). If GateClosedDueToInvalidRx is FALSE, it has no effect. The default value of
GateClosedDueToInvalidRx is FALSE; if any frame is discarded bec
...