Working group update                                Chairs           15    14:30 - 14:45

- 6 new RFC published since last IETF. 
- draft-mackenzie-bess-evpn-l3mh-proto-06 needs to be potentially updated after AC aware draft makes progress. Jeffery to work with author to get it updated. 
- Keyur : For MUP safi draft should we explain in mailing list about it fitting BESS charter ? 
- Matthew : send email and may be add some information in introduction or abstract.  
- Jeffery : In document itself you can point of its relation to VPN service.  


draft-ietf-bess-rfc7432bis-13                       Krishnaswamy     10    14:45 - 14:55

- Document updates and adds more clarification. 
- Ready for WGLC. 
- Jeffery : I will review once again and provide comments if there is any. 
- Himanshu Shah : Have you put all delta from RFC 7432 ? having delta will be good . 
- Luc : We had it in previous version, and were asked to remove since it was too noisy. 
- Ali : IETF tool can be used where delta can be looked on . 
- Ketan : Thanks for covering the error handling. I would encourage all the BGP work to make sure handle error . WG needs to take look closely since there is inter op implication. it would be good to send it to IDR WG as well. 
- Keyur : IDR makes note of it and will review it. 
- Ali : thanks to ketan for providing input on error handling. 
- Himanshu : Document is very mature. i would like to have one liner on each change. 

draft-ietf-bess-evpn-ac-aware-bundling              Mankamana        05    14:55 - 15:00
- Some pending comment will be addressed. 
- Jeff Hass :  We have problem in past where extended community reserved field being used. Be careful with procedures. 

draft-ietf-bess-evpn-per-mcast-flow-df-election     Mankamana        05    15:00 - 15:05
 - Document updated based on early review. 
 - Document is ready for WGLC . 
 - Shasha : what happens if one of the draft supports and other one does not ? 
 - Mankamana : There is capability exchange between peer. so there is no problem handling it. 

draft-ietf-bess-evpn-unequal-lb                     Neeraj           05    15:05 - 15:10

 - addressed all comment, ready for WGLC . 

Individual Drafts:
draft-sajassi-bess-evpn-l3-optimized-irb            Chuanfa          05    15:10 - 15:15
 - Ready for adoption call. 

draft-sajassi-bess-evpn-fabric-migration            Chuanfa          05    15:15 - 15:20
 - new clarification added. 
 - input from WG needed. 
 - Jorge : it was good analysis done in this draft. it will be good to analyze other use cases for example RFC 8560 and associated used cases.  Another use case will be inter as option B the previous draft which was presented. 

draft-sajassi-bess-evpn-umr-mobility-03             Krishnaswamy     10    15:20 - 15:30
 - multivendor support 
 - ready for adoption call 
 - Poll was done by chairs about who read the draft. Few people have read the draft. 

draft-rabnag-bess-evpn-anycast-aliasing-04          Jorge            10    15:30 - 15:40
 - Feedback from WG needed. 
 - Ready for adoption call. 

draft-rabadan-bess-evpn-inter-domain-opt-b-06       Jorge            05    15:40 - 15:45

 - Feedback from WG needed. 
 - Ready for adoption call. 

draft-mpmz-bess-mup-safi                            Keyur Patel      10    15:45 - 15:55
 - presented multiple times. 
 - multiple implementation 
 - Jeffery : MUP architecture is not SRv6 specific. please clean up the draft. 
 - Jeffery : There is relevance in this draft which comes under BESS charter . 

draft-liu-bess-srv6-service-sid-anycast-flag        Changwang Lin    05     15:55 - 16:00
 - ready for adoption 
draft-wang-bess-l3-accessible-evpn                  Wei              05     16:00 - 16:05
 - Shasha : Has authors considered using the PWs crossing the L3 domains as Virtual Ethernet Segments as described in Section 1.3 of RFC 9784?
 - Wei : We will investigate this comment. 
 - Jorge : We discussed it few times, i agree with shasha . looks like we are not understanding all the procedure in draft. right now draft is under specified. Add data packet flow and some more detail. At this point of time we don't think we can move forward.