Minutes IETF114: bier
minutes-114-bier-01
Meeting Minutes | Bit Indexed Explicit Replication (bier) WG | |
---|---|---|
Date and time | 2022-07-25 14:00 | |
Title | Minutes IETF114: bier | |
State | Active | |
Other versions | markdown | |
Last updated | 2022-09-01 |
minutes-114-bier-01
IETF114 BIER Working Group minutes
- WG status
- Toerless: BIER TE draft passed Auth-48, becoming RFC soon.
- Stig : MLD draft was waiting on PIM extension. document is ready for
WGLC. - Andrew : only draft sitting is OSPFv3 extension.
- Jeffery: IDR extension draft, spoke to main author. we may need some
other co-author to address comments.
-
draft-ietf-bier-multicast-as-a-service
- adopted draft
- new section got added
- for each customer device bit, there would be provider bit.
- Fanghong: Scaling question
- Jeffery: there is slide which covers the scaling aspect.
- Toerless: provider as control to plan number of bits.
- comments expected.
-
draft-zzhang-bier-extension-headers
- Waiting for more comments.
- working with all major vendors to come up with single solution
in this area
-
BIFT-ID of BIER-TE advertisement
draft-zwx-bier-te-isis-extensions
draft-zwx-bier-te-ospf-extensions
draft-zwx-bier-te-ospfv3-extensions- Toerless: BIER TE RFC does has some input about similar area.
will take to list - Jeffery: BIER TE we need to worry about BIFT ID and content of
BIT. each BFR only need to care of local bit adjecency. its
better to populate using controller rather than IGP. - Sandy: For the controller part, draft-ietf-bier-te-yang
obviously can assign the BP of adjecency and the BIFT-ID for
forwarding table looking up. In case the IGP signaling rather
than the controller is used, the BIFT-ID advertisement must be
provided, otherwise the forwarding table looking up cannot be
achieved correctly.
- Toerless: BIER TE RFC does has some input about similar area.