Aggregation of Diffserv Service Classes
RFC 5127
Yes
No Objection
Note: This ballot was opened for revision 07 and is now closed.
Lars Eggert No Objection
(Dan Romascanu; former steering group member) Yes
(Magnus Westerlund; former steering group member) Yes
(Chris Newman; former steering group member) No Objection
(Cullen Jennings; former steering group member) No Objection
(David Ward; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) (was No Record, Discuss) No Objection
Figure 2 seems to subdivide the DSCP field markings for Assured Elastic and Elastic treatment aggregates. For Assured Elastic, the DSCP codes represented in three groups (on three rows); for Elastic the codes are in two groups. However, the text to this point would seem to indicate they should be grouped into a single set, as with Real Time. Later text (in 4.1.3 and 4.1.4) seems to indicate these groupings are priorities within the treatment aggregate. If that is correct, a brief mention near Figure 2 in section 4.1 would be helpful. Alternatively, consider whether that level of detail is needed in this document.