Requested revision
Standard: | 802.1Q-2011 | Clause: | 35.2.1.4(c) |
Clause title: | streamAge |
Rationale for revision
The goal -- Stream age starts when the stream starts forwarding, not
when the entry is first made to the DRE (Dynamic Reservations Entries)
35.2.1.4(c) the current language (below) (region for comparison marked
by *** )
""
streamAge: A per-port per-stream 32-bit unsigned value used to represent
the time, in seconds, since
***
a stream’s destination_address was first added to the Dynamic
Reservations Entries (8.8.7) for the
associated port.
***
This value is used when determining which streams have been configured the
longest. Streams with a numerically larger streamAge are considered to
be configured earlier than
other streams, and therefore carry a higher implicit importance.
""
The text between **** should be:
the control element for the associated outbound Port most recently
became forwarding in the Dynamic Reservation Entry (8.8.7) corresponding
to the stream’s destination_address
Proposed text
35.2.1.4(c) proposed language (below)
""
streamAge: A per-stream 32-bit unsigned value used to represent the
time, in seconds, since
the control element for the associated port most recently became
forwarding in the Dynamic Reservation Entry (8.8.7)
corresponding to the stream’s destination_address.
This value is used when determining which streams have been configured the
longest. Streams with a numerically larger streamAge are considered to
be configured earlier than
other streams, and therefore carry a higher implicit importance."
""
Impact on existing networks
By current definition, a stream age starts as soon as a declaration is
received. This is unintended and results in inappropriate determination
of stream importance.
Originator
Name: | Aaron Stewart, Bob Noseworthy | Email: | astewart@iol.unh.edu; ren@iol.unh.edu |
Affiliation: | University of New Hamsphire's InterOperability Lab | ||
Submitted: | 2012-08-23 |