assume any combinations to just work without being specified.
Thx,
Ice.
Jeffrey
From: BIER [mailto:bier-boun...@ietf.org] On Behalf Of IJsbrand Wijnands
(iwijnand)
Sent: Wednesday, February 21, 2018 8:40 AM
To: Jeffrey (Zhaohui) Zhang <zzh...@juniper.net<mailto:zzh...@juniper.net&g
Ice: No, BART is not being slaved here. If BARM is 0, BART is all yours.
Zzh> BART is BIER’s no matter what BARM is; not only when BARM is 0.
Ice: Yes, sorry, I agree, BART is always BIER and BARM is always IGP.
Ice: What I meant to clarify is that BART is not slaved to BARM (IGP) and v.s.,
Inline.
Future specifications may specify BART values that change the
interpretation of the BARM octet. Those specifications must handle backwards
ICE: This creates a potential dependency which I think we should avoid. I think
there are possible use-cases where the combination of the two
