RFC 3289, "Management Information Base for the Differentiated Services Architecture", May 2002Source of RFC: diffserv (tsv)
See Also: RFC 3289 w/ inline errata
Errata ID: 301
Publication Format(s) : TEXT
Reported By: Tom Irwin
Date Reported: 2002-08-27
1. During implementation, there has been some confusion on the "reuse of structural elements" in section 2.2. It is clear from the comments and the MIB that counters cannot be effectively reused. What appears confusing is the case when an entire (or partial) DiffServ tree used for a specific interface ifIndex and direction is reused. Is the DiffServ tree in this case just a template such that all of the data path elements are replicated (counters will not work properly) for another interface? This seems reasonable since other data path elements such as queues and schedulers are clearly interface dependent. It is important to remove this ambiguity since the RowPointer usage does not prohibit this "not generally recommended" application. What is the intent? 2. Minor update in section 3.2.2: ' Differentiated Services Code Point ' to ' Differentiated Services Code Point, including "any" ' 3. Figure 9b in section 188.8.131.52 is somewhat difficult at first to follow due to how the multiplexing is shown in the Yellow "Count Action" (an action only has a single input).