Hi Alvaro, Thank you. We’ll keep it as normative then and try to progress draft-ietf-bess-evpn-inter-subnet-forwarding asap... We’ll look into Benjamin’s comments first and then try to address the other suggestions given.
Should we wait for the telechat and your go-ahead before we publish a new version? Thank you. Jorge From: Alvaro Retana <[email protected]> Date: Thursday, May 10, 2018 at 3:15 PM To: Benjamin Kaduk <[email protected]>, The IESG <[email protected]>, "Ali Sajassi (sajassi)" <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, Zhaohui Zhang <[email protected]>, "[email protected]" <[email protected]> Subject: Re: Benjamin Kaduk's Discuss on draft-ietf-bess-evpn-prefix-advertisement-10: (with DISCUSS and COMMENT) Resent-From: <[email protected]> Resent-To: <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> Resent-Date: Thursday, May 10, 2018 at 3:15 PM On May 9, 2018 at 5:00:38 PM, Ali Sajassi (sajassi) ([email protected]<mailto:[email protected]>) wrote: Ali: Hi! You are right, the draft-ietf-bess-evpn-inter-subnet-forwarding has passed the WGLC but I need to take care of some last min. comments before publishing the next rev. Since prefix-advertisement draft will become RFC ahead of inter-subnet-forwarding, do we need to move the reference to informative? No, the reference has to be Normative because the Router's MAC Extended Community was defined there. Please focus on addressing the other parts of Benjamin’s DISCUSS. Thanks! Alvaro.
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
