Working Group Draft Update : * Concern : We have many working group document which are not making progress and lots of new work being produced as rev_0 drafts. * Thanks for AD Gunter for moving queue fast and many draft's being reviewed. * draft-ietf-bess-evpn-unequal-lb - Susan Hares: Submitted review during oct , authors already exchanged correction. Will post in mailer again. Did finish Genev and controller drafts review as well. - Stephane : We need to finish review of IPVPN interconnect. - Jeff : We have gone through an agreement of content - Matthew : We want to close loop on open discussion about BESS / IDR review . - Jeff : Loop has been closed, will check once again. - Jorge : loop has been closed and ready to move. * draft geneve mathew is chasing editors to make change. * 7432 bis : - not much discussion in mail - 10 people think its ready for WGLC during poll in room. * Need to close existing drafts before making more Adoption of document. Susan : draft-ietf-bess-evpn-unequal-lb-23 - still needs to use RFC7606 language. The text is going in the right direction, but needs to use RFC7606 language draft-ietf-bess-evpn-vpws-seamless-01 * Ready for last call * Ali - There is sister draft and its natural extension . Its long overdue to go over last call. draft-ietf-bess-weighted-hrw-01 * Some modification may be needed to add more detail about HRW. draft-ietf-bess-secure-evpn-01 Stephane : As chair, which WG making data plane part Ali - no data port modification Stephane : you adding new UDP port Ali : Yes Stephane : This work can not be done in BESS Ali : it was done in NVO3 Matthew : there will be discussion to merge NVO + BESS Susan : will send side note to include tunnel encap description in draft. draft-sajassi-bess-rfc8317bis-02 * Ready for adoption call. * Jeffery : please send email also in list. please check Wiki as well. draft-lrss-bess-evpn-group-policy-01 Ali - 7348 bis to be expedited. Matthew : There is no much work in NVO, so may be we present it in routing WG so there is enough visibility. Jeff : republish the draft in routing group and there was agreement about it . Mathew : Not sure if need to be republished, but we need to be present it. Aijun Wang : supporting the work since we need to update VxLAN header Gunter : what we learnt from Trustee that 7348 is not IETF owned document. it was individual submission. publish new draft and just add IANA section. Matthew: it was informational draft (RFC 7348) and changed towards end. * Jeff Hass: This is opportunity to take it to full standard. * Jeff : will it create problem with reference. it will be misref for standard. * Gunter : It has not been discussed. right now idea is to bring informational document. for standard it has to be reviewed and modified. draft-rabnag-bess-evpn-anycast-aliasing-02 Janos Farkas : Multi chassis is part of standard , deployment do use proprietary deployment. Ali : The implementation we know all the vendor, all implementation are proprietary. Jeff : operational consideration section needs to be added. Patrice : convergence is really fast. It will be good to mention that . draft-burdet-bess-evpn-fast-reroute-08 * Next draft will be merged with next draft and ready for adoption call. * Yao Liu : any consideration for L3VPN and SRv6 * Patrice : After merging we will see the next step draft-liu-bess-srv6-service-sid-nffrr-flag-02 Ketan : We have agreement to merge and co-operate in EVPN document. Jorge : argument is not in current version of draft. Ketan : it was part of offline discussion. After merge it will be clear. draft-levyabegnoli-bess-evpn-savi-03 draft-rbickhart-evpn-ip-mac-proxy-adv-02 Sasha : comment has been sent to WG please take look Aijun : Some question about MH PE and related binding. Will Discuss it offline draft-sajassi-bess-evpn-first-hop-security-03 * Ready for adoption David Lamparter : Do we need this work ? we need to reference DHCP6 as well. why not to use DHCP active lease query RFC. Krishna : MAy be not valid for MH point and we can sync up offline and close on this. draft-sajassi-bess-evpn-umr-mobility-02 * Ready for adoption draft-lz-bess-srv6-service-capability-06 Jorge : RFC9252 timeframe would have been good time to write . Now its hard to implement it in brownfield scenario . Ketan : ability to understand capability is well known. MPLS , SRv6 talking together will require lots of planning. we will not get any benifit. draft-xie-bess-evpn-extension-evn6-00 Ali - Solution is well documented but problem statement not documented. Krishna - Route type 12 and 13 have been already used.