Requested revision
Standard: | 802.1CB-2017 | Clause: | 10.9 |
Clause title: | Operational per-port FRER counters |
Rationale for revision
Clause 10.9 states that "The counters are indexed by port number and
facing (in-facing or out-facing)". However, in the description for the
managed objects for the table it states that the respective values of
the counters equal the sum of all of their per port per stream
counterparts on the same port (e.g. 10.9.1 frerCpSeqRcvyPassedPackets
states "Its value equals the sum (modulo the size of the counters) of
all of the frerCpsSeqRcvyPassedPackets (10.8.5) counters on this same
port.". Taking into account the discussion on counters for stream
identification during the July 2020 electronic plenary meeting it
seems that the description of the actual managed objects is correct
and that the per port counters should be per port only, not per port
and direction. Please also see the maintenance request submitted by
Christophe Mangin on July 24, 2020
(http://www.ieee802.org/1/private/email_mq/msg00268.html).
Proposed text
Change clause 10.9 to read as follows:
"The following counters are instantiated for each port on which any of
the Stream identification function (6.2), Sequencing function (7.4),
or Sequence encode/decode function (7.6) is configured. The counters
are indexed by port number. All counters are unsigned integers. If
used on links faster than 650 000 000 bits per second, they shall be
64 bits in length to ensure against excessively short wrap times.
A Stream identification component (5.3) shall implement the first two
counters tsnCpSidInputPackets (9.3.1) and tsnCpSidOutputPackets
(9.3.2); the remainder of the counters in 10.9 are optional for such a
system."
Impact on existing networks
There is no impact on existing networks since there is no standard
management module available yet.
Originator
Name: | Stephan Kehrer | Email: | stephan.kehrer.committees@gmail.com |
Affiliation: | Hirschmann Automation and Control GmbH | ||
Submitted: | 2020-08-18 |