Re: pingCtlDSField in remops
Juergen Schoenwaelder <[email protected]> Sun, 10 Jul 2005 09:28:51 +0200
| Newsgroups | gmane.ietf.disman |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Jul 09, 2005 at 05:59:28PM -0700, Randy Presuhn wrote: > The added text makes it sound like this object is only about the DSCP, > rather than the entire TOS octet. I think this matters because the > two bit positions that RFC 2474 and 3260 call "currently unused" that > are in fact used by RFC 3168 for ECN. > > With perfect foresight we should have made this into two objects, but > we didn't. I think the next best thing is to say that the six high bits go > to the DSCP, and the two low bits go to the ECN field, which would be > more consistent with this object's original definition in terms of the > TOS octet, rather than just talking about DSCPs. > > I suggest adding text and a reference to RFC 3168 for the two > low-order bits. Can you explain why it makes sense to set the ECN bits in this context? /js -- Juergen Schoenwaelder International University Bremen <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany