IETF 121 BIER Session Agenda
WG info: https://datatracker.ietf.org/group/bier/about/
Chairs:
Greg Shepherd (gjshep@gmail.com)
Tony Przygienda (tonysietf@gmail.com)
Secretary:
Zheng(Sandy) Zhang (zhang.zheng@zte.com.cn)
Monday Session IV 17:30-19:00 Local time, Nov 4, 2024
Jeffrey Zhang: for bgp-ls draft, was it reviewed in LSR WG or IDR WG?
Zheng Zhang: the draft has been sent to both LSR WG and IDR WG.
Tony Przygienda: no feedback received.
Toerless Eckert: may be better to ping specific persons for reviewing.
Tony Przygienda: good suggestion. may try to connect Jeff Haas or
somebody else.
Gregory Mirsky: for bier-bfd draft, Donald agreed to be the shepherd and
will remind him for the shepherd work.
Toerless Eckert: try to understand the incorporate referencing of pim
light draft.
Hooman Bidgoli: pim light is used for pim join and prune processing, for
edge routers specifically.
Toerless Eckert: it's not necessary make so complex for signaling the
BFR-ids of egress routers to ingress routers in BIER, igp has been used
for this. There may be confliction between igp and pim signaling.
Hooman Bidgoli: the ingress router needs to know the BFR-ids of egress
routers for specific multicast flow.
Stig Venaas: the join in pim light is used to let the ingress router
know the egress routers which connect the receivers. it's not the BFR-id
assignment. pim may lost the BFR-id information of egress router if we
don't carry the info in pim join message.
Jeffrey Zhang: there are three aspects here, one is the pim extensions
include not only the BFR-id of egress router but also the sub-domain id.
the second is the BFR-id carried in the pim extension brings convenience
though it can be discussed, and pim light simplify the pim adjacency
relationship. the third is that how to select the ingress router is the
same for all the bier overlay protocols, such as pim, mldp, mld, etc.
that's separate things.
Hooman Bidgoli: we need to track the edge routers associated with (s,
g).
Stig Venaas: it's used for interconnecting the pim islands. though we
can get the sub-domain id and bfr-id information through the outside
bier encapsulation, it's more convenient to get the information through
the PIM join attributes.
Gregory Mirsky: volunteer to be the shepherd of
draft-ietf-bier-mldp-signaling-over-bier.
Tony Przygienda: how to participate the work, central or distribute?
what if the topology changes?
Toerless Eckert: in te world it's good to have central control.
David Lamparter: in te the id is used to identify the link and is known
at the beginning, right?
Toerless Eckert: yes. when the packet needs to be rerouted, needs to
know the new link ids in advance.
Gunter Van de Velde: two clarify questions: the first one is that when
in large topology with thousand links, if you want to prune links, is
administrative group used here? the second is the link has two sites,
when it has only one number, how to know the direction.
Toerless Eckert: the function used by pce may be applied here.
Tony Przygienda: share group has share risk.
Toerless Eckert: in rfc9262 two ids assigned for the two directions of a
link. for p2p links one id can be used.