RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (1)

RFC 3376, "Internet Group Management Protocol, Version 3", October 2002

Source of RFC: idmr (rtg)

Errata ID: 1501

Status: Verified
Type: Editorial

Reported By: Dave Thaler
Date Reported: 2008-09-08
Verifier Name: Adrian Farrel
Date Verified: 2013-05-11

The header says:

Network Working Group                                            B. Cain
Request for Comments: 3376                               Cereva Networks
Obsoletes: 2236                                               S. Deering
Category: Standards Track                                    I. Kouvelas
                                                           Cisco Systems
                                                               B. Fenner
                                                    AT&T Labs - Research
                                                          A. Thyagarajan
                                                                Ericsson
                                                            October 2002

It should say:

Network Working Group                                            B. Cain
Request for Comments: 3376                               Cereva Networks
Updates: 2236                                                 S. Deering
Category: Standards Track                                    I. Kouvelas
                                                           Cisco Systems
                                                               B. Fenner
                                                    AT&T Labs - Research
                                                          A. Thyagarajan
                                                                Ericsson
                                                            October 2002

Notes:

RFC 3376 does not completely replace RFC 2236, so it should say "updates" instead of "obsoletes". Specifically, to have a compliant implementation of RFC 3376 section 4, one MUST understand and implement the "Version 2 Membership Report" and "Version 2 Leave Group" messages. This is why RFC 2236 is listed as a normative reference of RFC 3376.

Status: Held for Document Update (1)

RFC 3376, "Internet Group Management Protocol, Version 3", October 2002

Source of RFC: idmr (rtg)

Errata ID: 4375

Status: Held for Document Update
Type: Technical

Reported By: Yechiel Rosengarten
Date Reported: 2015-05-26
Held for Document Update by: Alvaro Retana
Date Held: 2016-02-16

Section 8.13 says:

8.12. Older Version Querier Present Timeout

   The Older Version Querier Interval is the time-out for transitioning
   a host back to IGMPv3 mode once an older version query is heard.
   When an older version query is received, hosts set their Older
   Version Querier Present Timer to Older Version Querier Interval.

   This value MUST be ((the Robustness Variable) times (the Query
   Interval in the last Query received)) plus (one Query Response
   Interval).

It should say:

8.12. Older Version Querier Present Timeout

   The Older Version Querier Interval is the time-out for transitioning
   a host back to IGMPv3 mode once an older version query is heard.
   When an older version query is received, hosts set their Older
   Version Querier Present Timer to Older Version Querier Interval.

   This value MUST be ((the Robustness Variable) times (the Query
   Interval )) plus (one Query Response Interval in the last Query 
   received).

Notes:

The last query received is older version query.
As such - it does not include query interval.
It looks like it should be operator responsibility to configure identical robustness variable and query interval values network-wide for supporting older versions.

=== Alvaro Retana ===

The pim WG was consulted on the proposed text of this errata, but no clear direction was determined. In fact, no significant discussion took place.

Given that this issue doesn't seem to be causing a problem that the WG wants to address wight away, I'm disposing of this errata as "Held for Document Update". If this RFC is updated the WG must then address the issue.

https://mailarchive.ietf.org/arch/msg/pim/s9dMx_O3cFUyn38CHj81yw4Wp2o

Status: Rejected (2)

RFC 3376, "Internet Group Management Protocol, Version 3", October 2002

Source of RFC: idmr (rtg)

Errata ID: 770

Status: Rejected
Type: Technical

Reported By: Rajesh Garg
Date Reported: 2006-03-21
Rejected by: Adrian Farrel
Date Rejected: 2011-07-24

Section 5.2 says:

If new query is Group and Source Specific query and there is pending 
response for this group and recorded source list for the group is empty 
(i.e. previous query was Group Specific query)

It should say:

[see note]

Notes:

In section 5.2 of RFC 3376, 5 sequential steps are given to handle the
received query from the multicast router.
I feel the following case is not handled properly in these steps (see above)

In this case, source list will be cleared as per step 4 of section 5.2.
But I feel the source list should be recorded to generate the report
accordingly.

from pending
--VERIFIER NOTES--
The RFC is correct in saying that recorded source-list should be cleared if the newly received query is group-specific query.

Errata ID: 3092

Status: Rejected
Type: Editorial

Reported By: Jon Hak Song
Date Reported: 2012-01-18
Rejected by: Adrian Farrel
Date Rejected: 2012-05-08

Section 6.6.3.1 says:

6.6.3.1. Building and Sending Group Specific Queries

   When a table action "Send Q(G)" is encountered, then the group timer
   must be lowered to LMQT.  The router must then immediately send a
   group specific query as well as schedule [Last Member Query Count -
   1] query retransmissions to be sent every [Last Member Query
   Interval] over [Last Member Query Time].

   When transmitting a group specific query, if the group timer is
   larger than LMQT, the "Suppress Router-Side Processing" bit is set in
   the query message.

It should say:

6.6.3.1. Building and Sending Group Specific Queries

   When a table action "Send Q(G)" is encountered, then the group timer
   must be lowered to LMQT.  The router must then immediately send a
   group specific query as well as schedule [Last Member Query Count -
   1] query retransmissions to be sent every [Last Member Query
   Interval] over [Last Member Query Time].

   When a group specific query is being transmitted, if the group timer is
   larger than LMQT, the "Suppress Router-Side Processing" bit is set in
   the query message.

Notes:


--VERIFIER NOTES--
I am rejecting this editorial erratum because the original English is perfectly comprehensible. (It is true that it is not very elegant, but the proposed replacement isn't too good either:-)

Report New Errata



Search RFCs
Advanced Search
×