Minutes BIER 113

0. WG status: 
Jeffrey: Adoption Call for BAAS, IDR draft needs revision
Alvaro: Response to FRR was given by Sandy, we¡¯d like the issue to be addressed before officially accepting it. how will github work? policy?
AI chairs: get to GIT working group and read their drafts

1. draft-ietf-bier-lsr-non-mpls-extensions:
Tony: why discussion about signalling/local/non-local?
Jeffrey: no new things, global based on algorithm BIFT-ID doesn¡¯t need signalling, otherwise it does within domain, between domains no need to signal them if leaking

2. draft-xzlnp-bier-ioam:
Tony: should we have OAM going to all receivers? because IOAM does that
Jeffrey: defer encoding to GDF preso
Tianran: I mailed to the list. should we put the OAM into the payload of BIER?
Greg: well, OAM follows same path as BIER packets so it¡¯s not clear IOAM does not make things worse by e.g. causing fragmentation
Fanghong: ?
Xiao: IOAM in-situ. Payload already has OAM
tony: Not really. lots of protocols that BIER carry does not have OAM.
Robin: same as Xiao, how the v6 IPSEC will work
Jeffrey: direct you can use ether, in v6 tunnel BIER is carried as payload with OAM
Zhenbin: will that be possibly extended for other things than OAM
Jeffrey: defer extenxtion header discussion to last GDF preso

3. draft-trossen-bier-frrm: 
Toerless: that would be a good opportunity to promote per packet destination set capability
Sandy: looks useful, I will help

4. draft-wang-bier-rh-bier: 
Fanghong: ?
Jingrong: conclusion as to WG consensus to encode BIER in v6 EH changed?
Tony: why should it? we ran the IETF consensus process but people can always present if there is time even if consensus was not to adopt the work. I didn¡¯t see any changes really between last two revisions.
Aijun: decided to defer to the list/chat

5. draft-zzhang-intarea-generic-delivery-functions: 
Tony: ok, cannot follow header, need read draft