BIER Anycast Support via Shared BFR-ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Bit Index Explicit Replication (BIER) protocol does not currently support anycast, which is necessary for egress protection purposes, as it requires unique BFR-prefixes and BFR-IDs, leading to duplicate ID detection and logging issues.
Innovation Solution
Configuring a BIER sub-domain with a common, non-zero BFR-ID and BFR-prefix shared by multiple BFRs, allowing them to advertise anycast addresses without treating the common ID as a duplicate, and using this configuration to calculate routes and generate bit index forwarding tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If BIER protocol uses unique BFR-prefixes and BFR-IDs for each router, then routing precision and identifier uniqueness are improved, but anycast support and egress protection capability deteriorate
Solution Approach 1:
The patent merges the identification functions of BFR-prefix and BFR-ID by allowing multiple routers to share the same BFR-prefix and BFR-ID combination. This combining approach enables anycast functionality where multiple egress routers can be identified by a common prefix, resolving the contradiction between maintaining unique identifiers and supporting anycast for egress protection.
2Reliability
If BIER protocol detects and logs duplicate BFR-IDs, then identifier uniqueness validation is improved, but network operation complexity and advertisement overhead increase
Solution Approach 1:
The patent introduces dynamic behavior in duplicate ID detection by implementing a suppression mechanism. When a router detects a duplicate BFR-ID advertisement, it logs the event but suppresses further duplicate advertisements after a certain threshold or time period. This dynamic approach maintains reliability through initial detection while reducing operational complexity by preventing advertisement flooding.
Solution Approach 2:
The patent implements feedback mechanisms where routers monitor and track BFR-ID advertisements from multiple sources. The system uses this feedback information to make intelligent decisions about whether to continue advertising or suppress advertisements, thereby managing the trade-off between validation reliability and operational complexity.
Data Source
AI summary
BIER architecture currently does not support anycast, in that each BIER Forwarding Router (BFR) has its own unique BFR-prefix and BFR-ID. BIER signaling protocols also check if there are duplicate BFR-IDs advertised. Anycast support with BIER is described. The description updates (e.g., relaxes and/or removes some requirements of) RFC 8279, RFC 8401, and RFC 8444.