RFC Errata
Found 3 records.
Status: Verified (2)
RFC 2236, "Internet Group Management Protocol, Version 2", November 1997
Note: This RFC has been updated by RFC 3376
Source of RFC: idmr (rtg)
Errata ID: 470
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jesse Norell
Date Reported: 2004-12-17
Verifier Name: Ross Callon
Date Verified: 2009-11-07
Section 2.1 says:
These two messages are differentiated by the Group Address, as
described in section 1.4 . Membership Query messages are
referred to simply as "Query" messages.
It should say:
These two messages are differentiated by the Group Address, as
described in section 2.4 . Membership Query messages are
referred to simply as "Query" messages.
Notes:
Errata ID: 471
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Stephen Nadas (RL/TNT)
Date Reported: 2006-11-28
Verifier Name: Adrian Farrel
Date Verified: 2010-08-20
Section 2.2 says:
Varying this setting allows IGMPv2 routers to tune the "leave latency" (the time between the moment the last host leaves a group and when the routing protocol is notified that there are no more members), as discussed in section 7.8. It also allows tuning of the burstiness of IGMP traffic on a subnet, as discussed in section 7.3
It should say:
Varying this setting allows IGMPv2 routers to tune the "leave latency" (the time between the moment the last host leaves a group and when the routing protocol is notified that there are no more members), as discussed in section 8.8. It also allows tuning of the burstiness of IGMP traffic on a subnet, as discussed in section 8.3
Notes:
Section 2.2 2nd para refers to section 7.8 and 7.3 neither of which
exist. It should refer to 8.8 and 8.3.
Status: Rejected (1)
RFC 2236, "Internet Group Management Protocol, Version 2", November 1997
Note: This RFC has been updated by RFC 3376
Source of RFC: idmr (rtg)
Errata ID: 3063
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jon Hak Song
Date Reported: 2011-12-26
Rejected by: Adrian Farrel
Date Rejected: 2012-05-08
Section 6 says:
- "set timer", setting the timer to its maximum value [Version 1
Router Present Timeout] and (re)starting it.
________________
| |
| |
| No IGMPv1 |
| Router |
| Present |
| |
---->| |----
| | | |
| |________________| |
timer expires | | IGMPv1 query
| ________________ | received
| | | | (set timer)
| | | |
| | | |
-----| IGMPv1 |<---
| Router |
| Present |
| |
---->| |----
| |________________| |
| |
| IGMPv1 query received |
| (set timer) |
---------------------------
It should say:
- "set timer", setting the timer to its maximum value [Version 1
Router Present Timeout] and starting it.
- "reset timer", resetting the timer to its maximum value [Version 1
Router Present Timeout] and restarting it.
________________
| |
| |
| No IGMPv1 |
| Router |
| Present |
| |
---->| |----
| | | |
| |________________| |
timer expires | | IGMPv1 query
| ________________ | received
| | | | (set timer)
| | | |
| | | |
-----| IGMPv1 |<---
| Router |
| Present |
| |
---->| |----
| |________________| |
| |
| IGMPv1 query received |
| (reset timer) |
---------------------------
Notes:
Resetting timer is obviously different than setting timer.
--VERIFIER NOTES--
I am rejecting this Erratum mainly because RFC 2236 has been obsoleted by RFC 3376, but also because I don't agree that the change is needed. The original text covers the two operations adequately.