RFC Errata
RFC 6003, "Ethernet Traffic Parameters", October 2010
Source of RFC: ccamp (rtg)See Also: RFC 6003 w/ inline errata
Errata ID: 2552
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-10-12
Verifier Name: Adrian Farrel
Date Verified: 2010-11-10
Section 4.1, pg.7 says:
Index: 8 bits [...] A given index value j can be associated to at most N Class-Type values CTi (i =< N) of the EXTENDED_CLASSTYPE object. This | association applies when a set of one or more CTIs maps to a single (shared) BW profile. An example of value setting consists in assigning an arbitrary value comprised within the range [0x08,0xF8] associated to a set of CTi, the values in the range | [0xF8,0xFF] being selected for reserved sets. This allows mapping to one of 248 predefined CTi sets.
It should say:
Index: 8 bits [...] A given index value j can be associated to at most N Class-Type values CTi (i =< N) of the EXTENDED_CLASSTYPE object. This | association applies when a set of one or more CTis maps to a single (shared) BW profile. An example of value setting consists in assigning an arbitrary value comprised within the range [0x08,0xF8] associated to a set of CTi, the values in the range | [0xF9,0xFF] being selected for reserved sets. This allows mapping to one of 248 predefined CTi sets.
Notes:
Rationale:
a) consistent use of "CTi" -- 'i' essentially is a subscript index;
b) avoid ambiguity due to overlap in ranges given
[The first item is Editorial, but the second one clearly Technical]