Skip to content

Commit 6cca9e7

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 189 new elements (2026-07-06)
1 parent b1fdfd1 commit 6cca9e7

189 files changed

Lines changed: 1779 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎corpus/elements/rfc-8775__design-rationale-gdr-candidate-addresses-in-the-drlb-list-are.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8775
2+
kind: design-rationale
3+
summary: GDR Candidate addresses in the DRLB-List are recommended to be sorted in descending order so that hash-based GDR assignment is deterministic regardless of the order in which the DR learns of new candidates.
4+
section: "5.3"
5+
topics:
6+
- multicast
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__design-rationale-the-assert-mechanism-is-reused-for-gdr-transitions.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8775
2+
kind: design-rationale
3+
summary: The Assert mechanism is reused for GDR transitions (with near-maximum metric values) to minimize packet loss while tolerating a brief period of duplicates, rather than requiring a coordinated cut-over that would risk traffic black-holing.
4+
section: "5.7"
5+
topics:
6+
- multicast
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__design-rationale-the-modulo-hash-algorithm-has-poor-failover-characteristics.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8775
2+
kind: design-rationale
3+
summary: 'The modulo hash algorithm has poor failover characteristics with more than two GDRs: when one GDR fails, all groups may be reassigned to different GDRs rather than only those previously served by the failed router. This is acknowledged as a known limitation; future work may define consistent-hashing alternatives.'
4+
section: 5.2.2
5+
topics:
6+
- multicast
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__design-rationale-this-extension-applies-only-to-last-hop-routers.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8775
2+
kind: design-rationale
3+
summary: This extension applies only to last-hop routers, not first-hop routers, because source tree building uses the sender's IP address rather than the DR's address, and first-hop load balancing can be achieved naturally via IGP equal-cost multipath without additional protocol complexity.
4+
section: "3"
5+
topics:
6+
- multicast
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__interoperability-note-backward-compatibility-if-the-dr-does-not-support.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8775
2+
kind: interoperability-note
3+
summary: 'Backward compatibility: if the DR does not support DRLB, no load balancing occurs. If non-DR routers do not support DRLB, they are simply not considered GDR Candidates and load balancing may still operate among supporting routers.'
4+
section: "5.8"
5+
topics:
6+
- multicast
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__interoperability-note-if-different-hash-algorithms-are-advertised-among-routers.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8775
2+
kind: interoperability-note
3+
summary: If different hash algorithms are advertised among routers on a LAN, only routers advertising the same hash algorithm as the DR (and with the same DR priority) are eligible for GDR election; others are excluded from load balancing.
4+
section: "5.1"
5+
topics:
6+
- multicast
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__normative-requirement-all-gdr-candidates-must-use-the-hash-masks.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8775
2+
kind: normative-requirement
3+
summary: All GDR Candidates MUST use the hash masks advertised in the DRLB-List Option, even if they differ from those the candidate was locally configured with.
4+
section: "5.6"
5+
rfc2119_level: MUST
6+
topics:
7+
- multicast
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__normative-requirement-all-hash-masks-in-the-drlb-list-option.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8775
2+
kind: normative-requirement
3+
summary: All hash masks in the DRLB-List Option MUST have the same number of bits as the IP source address in the PIM Hello IP header, and all GDR Candidate addresses MUST be in the same address family as the PIM Hello IP header.
4+
section: 5.3.2
5+
rfc2119_level: MUST
6+
topics:
7+
- multicast
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__normative-requirement-all-routers-must-ignore-the-drlb-list-hello.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8775
2+
kind: normative-requirement
3+
summary: All routers MUST ignore the DRLB-List Hello Option if received from a PIM router that is not the DR; it MUST only be processed by routers announcing the DRLB-Cap Option with the same hash algorithm as the DR.
4+
section: "5.6"
5+
rfc2119_level: MUST
6+
topics:
7+
- multicast
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8775__normative-requirement-default-hash-mask-values-should-be-rp-hash.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8775
2+
kind: normative-requirement
3+
summary: 'Default hash mask values SHOULD be: RP Hash Mask zero (no bits set), Source and Group Hash Masks all-bits-set. These simplify configuration for most deployments.'
4+
section: "5.1"
5+
rfc2119_level: SHOULD
6+
topics:
7+
- multicast
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

0 commit comments

Comments
 (0)