You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IGMPv3 (RFC 3376) adds a group-record list to the Membership Report (type 0x22) and an extended Query format with source-list filtering. #2439/#2444 deliberately scoped this out — PR #2444's dispatch raises ProtocolError for any type outside {0x11, 0x12, 0x16, 0x17}. For a v3 Report (0x22) this correctly falls back to Raw. For a v3 Query, correction (verified by cross-review): v3 reuses type 0x11 (same as v1/v2 Membership Query), so it currently decodes as a v1/v2 Query with the extra v3-only octets (S flag, QRV, QQIC, source list) kept as trailing Raw — RFC 2236 §2.5 explicitly permits this and no bytes are lost, so it is not a defect in #2444. One real gap to fix here: v3 Max Resp Codes ≥128 encode as floating point (RFC 3376 §4.1.1), which the current v1/v2 code reads as a plain integer tenths-of-a-second value — e.g. code 0x8c decodes as 14.0s when the real value is 22.4s. A v3 Query parser needs the floating-point decode for this field.
Scope: a new schema/data model for the v3 Membership Report's group-record list, the v3 Query's extended fields, and the floating-point Max Resp Code/QQIC decode. Likely shares IGMP's base rather than needing its own ICMP_Family-style split, since v3 is a strict superset dispatched by the same type bytes.
Relabeled blocked -> wip: PR #2465 covers this issue (Closes #2448) and is now review: good-to-go, pending only the owner's merge. No comment here stated a checkable blocking condition, and blocked implies nothing is actively being worked -- that's no longer true.
Activity
feat(internet): implement IGMPv3 (#2448)
fix(internet): refuse non-8-octet IGMP Queries as IGMPv1/v2 (#2439)
4 remaining items
feat(internet): implement IGMPv3 (#2448)
feat(internet): implement IGMPv3 (#2448)
feat(internet): implement IGMPv3 (#2448)
fix(tests): repair fused merge text and bump census pins for IGMPv3
JarryShaw commentedon Oct 31, 2026
Relabeled
blocked->wip: PR #2465 covers this issue (Closes #2448) and is nowreview: good-to-go, pending only the owner's merge. No comment here stated a checkable blocking condition, andblockedimplies nothing is actively being worked -- that's no longer true.feat(internet): implement IGMPv3 (#2448)
fix(tests): repair fused merge text and bump census pins for IGMPv3
feat(internet): implement IGMPv3 (#2448)
fix(tests): repair fused merge text and bump census pins for IGMPv3
docs(internet): align IGMP alias and family docs with the id() ruling (…