Hi Alvaro, 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?
Cheers, Ali From: Alvaro Retana <aretana.i...@gmail.com> Date: Wednesday, May 9, 2018 at 1:17 PM To: Benjamin Kaduk <ka...@mit.edu>, The IESG <i...@ietf.org> Cc: "bess-cha...@ietf.org" <bess-cha...@ietf.org>, "draft-ietf-bess-evpn-prefix-advertisem...@ietf.org" <draft-ietf-bess-evpn-prefix-advertisem...@ietf.org>, Zhaohui Zhang <zzh...@juniper.net>, "bess@ietf.org" <bess@ietf.org> Subject: Re: Benjamin Kaduk's Discuss on draft-ietf-bess-evpn-prefix-advertisement-10: (with DISCUSS and COMMENT) Resent-From: <alias-boun...@ietf.org> Resent-To: <jorge.raba...@nokia.com>, <wim.henderi...@nokia.com>, <jdr...@juniper.net>, <w...@juniper.net>, Cisco Employee <saja...@cisco.com> Resent-Date: Wednesday, May 9, 2018 at 1:17 PM On May 9, 2018 at 11:14:15 AM, Benjamin Kaduk (ka...@mit.edu<mailto:ka...@mit.edu>) wrote: Hi! Not exactly a DISCUSS, but is there a plan for resolving the normative reference to the expired draft-ietf-bess-evpn-inter-subnet-forwarding? There are several overlapping authors and that document already had gone through WGLC. I believe the expiration has been due to other issues (day job, and other documents) capturing the attention of the authors. I’m not concerned about their ability to progress it. Thanks! Alvaro.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
