RFC Errata
Found 11 records.
Status: Verified (5)
RFC 2544, "Benchmarking Methodology for Network Interconnect Devices", March 1999
Note: This RFC has been updated by RFC 6201, RFC 6815, RFC 9004
Source of RFC: LegacyArea Assignment: ops
Errata ID: 421
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Lu Jian Xiong
Date Reported: 2002-08-07
Section 6 says:
Since the tester both sends the test traffic and receives it back, after the traffic has been forwarded but the DUT, the tester can easily determine if all of the transmitted packets were received and verify that the correct packets were received.
It should say:
Since the tester both sends the test traffic and receives it back, after the traffic has been forwarded by the DUT, the tester can easily determine if all of the transmitted packets were received and verify that the correct packets were received.
Errata ID: 423
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Scott Campbell
Date Reported: 2001-09-20
In Section C.2.2:
The network addresses 192.18.0.0 through 198.19.255.255 are have been assigned to the BMWG by the IANA for this purpose.
It should say:
The network addresses 198.18.0.0 through 198.19.255.255 have been assigned to the BMWG by the IANA for this purpose.
Errata ID: 424
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Shiang-Ming Huang
Date Reported: 2004-09-08
Section 3 says:
The authors understand that it will take a considerable period of time to perform all of the recommended tests nder all of the recommended conditions. We believe that the results are worth the effort. Appendix A lists some of the tests and conditions that we believe should be included for specific cases.
It should say:
The authors understand that it will take a considerable period of time to perform all of the recommended tests under all of the recommended conditions. We believe that the results are worth the effort. Appendix A lists some of the tests and conditions that we believe should be included for specific cases.
Notes:
Errata ID: 422
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Al Morton
Date Reported: 2006-11-05
Verifier Name: ron bonica
Date Verified: 2010-11-01
Section 26.1 says:
Procedure: Send a specific number of frames at a specific rate
through the DUT and then count the frames that are transmitted by the
DUT. If the count of offered frames is equal to the count of received
frames, the fewer frames are received than were transmitted, the rate
of the offered stream is reduced and the test is rerun.
It should say:
Procedure:
Send a specific number of frames at a specific rate through the
DUT and then count the frames that are transmitted by the DUT. If
the count of offered frames is equal to the count of received
frames, the rate of the offered stream is raised and the test
rerun. If fewer frames are received than were transmitted, the
rate of the offered stream is reduced and the test is rerun.
Errata ID: 4998
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Daniel Andrei Minca
Date Reported: 2017-04-18
Verifier Name: Benoit Claise
Date Verified: 2017-04-18
Section 2 says:
The authors understand that it will take a considerable period of time to perform all of the recommended tests nder all of the recommended conditions.
It should say:
The authors understand that it will take a considerable period of time to perform all of the recommended tests under all of the recommended conditions.
Notes:
It's missing the letter 'u'
Status: Held for Document Update (6)
RFC 2544, "Benchmarking Methodology for Network Interconnect Devices", March 1999
Note: This RFC has been updated by RFC 6201, RFC 6815, RFC 9004
Source of RFC: LegacyArea Assignment: ops
Errata ID: 5203
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: James Bensley
Date Reported: 2017-12-13
Held for Document Update by: Warren Kumari (Ops AD)
Date Held: 2017-12-14
Section 26.3 says:
Note: See section 18 for the maximum frame rates that SHOULD be used.
It should say:
Note: See section 20 for the maximum frame rates that SHOULD be used.
Notes:
Section 18 is "Multiple frame sizes", section 20 is "Maximum frame rate".
Errata ID: 5207
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Benoît Monin
Date Reported: 2017-12-14
Held for Document Update by: Warren Kumari (Ops AD)
Date Held: 2017-12-31
Section 25 says:
The DUT SHOULD be able to respond to address resolution requests sent by the DUT wherever the protocol requires such a process.
It should say:
The DUT and tester SHOULD both be able to respond to address resolution requests wherever the protocol requires such a process.
Notes:
DUT responding to its own address resolution requests does not make sense.
[Original corrected text was "The DUT SHOULD be able to respond to address resolution requests sent by the tester wherever the protocol requires such a process." - after discussions with the BMWG I edited the corrected text as above - the tester also needs to respond, as otherwise the DUT will age out its resolution -- WK ]
Errata ID: 1484
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2008-08-08
Held for Document Update by: ron bonica
Section C.2.4.1 Lear says:
This request should be
seen as coming from the immediate destination of the test frame
stream. (i.e. the phantom router (Figure 2) or the end node if
adjacent network routing is being used.) It is assumed that the
router will cache the MAC address of the requesting device. The ARP
request should be sent 5 seconds before the test frame stream starts
in each trial. Trial lengths of longer than 50 seconds may require
that the router be configured for an extended ARP timeout.
+--------+ +------------+
| | | phantom |------ P LAN A
IN A------| DUT |------------| |------ P LAN B
| | OUT A | router |------ P LAN C
+--------+ +------------+
Figure 2
It should say:
This request should be
seen as coming from the immediate destination of the test frame
stream. (i.e. the phantom router (Figure 4) or the end node if
adjacent network routing is being used.) It is assumed that the
router will cache the MAC address of the requesting device. The ARP
request should be sent 5 seconds before the test frame stream starts
in each trial. Trial lengths of longer than 50 seconds may require
that the router be configured for an extended ARP timeout.
+--------+ +------------+
| | | phantom |------ P LAN A
IN A------| DUT |------------| |------ P LAN B
| | OUT A | router |------ P LAN C
+--------+ +------------+
Figure 4
Errata ID: 1488
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2008-08-15
Held for Document Update by: ron bonica
Section 26.2 says:
The latency is timestamp B minus timestamp A as per the relevant definition frm RFC 1242, namely latency as defined for store and forward devices or latency as defined for bit forwarding devices.
It should say:
The latency is timestamp B minus timestamp A as per the relevant definition from RFC 1242, namely latency as defined for store and forward devices or latency as defined for bit forwarding devices.
Errata ID: 1490
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2008-08-19
Held for Document Update by: ron bonica
Section C.2.4.2 says:
If the test does not involve adjacent net routing the tester must supply proper routing information using a routing update. A single routing update is used before each trial on each "destination" port (see section C.24).
It should say:
If the test does not involve adjacent net routing the tester must supply proper routing information using a routing update. A single routing update is used before each trial on each "destination" port (see section C.2.6.2).
Errata ID: 2711
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Wang Haojian
Date Reported: 2011-02-11
Held for Document Update by: ron bonica
Section Appendix C says:
Notes:
Is there something wrong in the sub section title ?
C.2.5 is missing while the C.2.6.1 and C.2.6.2 exists ?