Re: [Idr] [Bier] FW: New Version Notification for draft-xu-idr-bier-extensions-01.txt

[Antoni Przygienda <[e-mail]>]

> 
> The draft never quite says that if the BIER path attribute is present, the NLRI is
> treated by BIER as a "BFR-prefix".  Unless I'm misunderstanding something, I
> think this needs to be said explicitly.

 [Tony saiz:]  I made the same comment and a larger discussion is whether only a single NLRI (BFR-prefix) is allowed in such an update (i.e. update carrying BIER attributes). 

> 
> It might be worth mentioning that, when creating a BIER attribute, a BFR needs
> to include one BIER TLV for every <sub-domain, bsl> pair that it supports.

 [Tony saiz:] I made the same comment. Alternative is to have a single BIER attribute per sub-domain in an update to allow e.g. a loopback per sub-domain (which does not sound right to me since the architecture seems to imply  a 1-1 assocation between a BFR prefix and a BIER domain).   

> I wonder (warning, half-baked idea approaching) if the BIER TLV needs
> something like a "BIER next hop" sub-TLV.  This could be changed to 'self' by
> every BFR that redistributes the route, but would be left unchanged by non-
> BFRs. Then you'd always know the next BFR in the path to a given BFER.

 [Tony saiz:]  hmm, yes, given the tunneling in the architecture this is something I have to think through as well. 

--- tony