Hash and Stuffing: Overlooked Factors in Network Device Benchmarking
RFC 4814
Yes
No Objection
Note: This ballot was opened for revision 08 and is now closed.
Lars Eggert No Objection
I don't see why this document should use RFC2119 terms anywhere. Section 4.5., paragraph 3: > In addition, it may be desirable to pick pseudorandom values from a > selected pool of numbers. Many services identify themselves through > use of reserved destination port numbers between 1 and 1023 > inclusive. Unless specific port numbers are required, it is > RECOMMENDED to pick randomly distributed destination port numbers > between these lower and upper boundaries. The IANA registered ports extend to 49151, which should be the default upper bound. Section 8.2., paragraph 0: > 8.2. Informative References Nit: All three are uncited. Appendix C., paragraph 2: > | Source IP | 192.168.13.1-192.168.13.254 | > | Destination IP | 192.168.1.10 | Should use 192.0.2.0/24 - the block assigned as "TEST-NET" for use in documentation and example code. Appendix D., paragraph 2: > | Source IP | DEAD:0:0:1::1-DEAD:0:0:1::FF | > | Destination IP | DEAD:0:0:2::10 | Should use 2001:DB8::/32 - the block assigned as "TEST-NET" for use in documentation and example code.
(David Kessens; former steering group member) Yes
(Brian Carpenter; former steering group member) (was Discuss) No Objection
Minor points from Gen-ART review by Joel Halpern:
In section 4.2, in describing how to create the MAC address, the upper byte is anded with 0xFC to clear the global/local and unicast/multicast bit so that the address will be a global multicast. there are two minor issues here:
Using a global MAC address construct from a random number and a port number is probably appropriate, but violates the standard. It would probably be a good idea to acknowledge this fact, and explain why global (rather than local) addresses need to be used.
The text refers to the two bits that are being controlled as the "high order two bits of that byte." While those are the first two bits that will be clocked out over the ethernet, they are not the "high order" bits in most peoples understanding of the term.
(Dan Romascanu; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sam Hartman; former steering group member) (was Discuss) No Objection
(Ted Hardie; former steering group member) No Objection