I echo that, there is a number of implementations in the field which uses this mechanism
From: Yu Tianpeng <[email protected]> Date: Friday, 7 June 2019 at 11:15 To: "Bocci, Matthew (Nokia - GB)" <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [bess] Second WG Last Call on draft-ietf-bess-evpn-proxy-arp-nd-06 Resent-From: <[email protected]> Resent-To: Jorge Rabadan <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, Greg HANKINS <[email protected]>, <[email protected]>, Daniel Melzer <[email protected]>, <[email protected]> Resent-Date: Friday, 7 June 2019 at 11:15 Dear WG, support this is useful optimization mechanism and has couple of known implementations and well documented. Thanks, Tim On Fri, 7 Jun 2019, 10:07 Bocci, Matthew (Nokia - GB), <[email protected]<mailto:[email protected]>> wrote: WG We ran a working group last call on this draft in August 2018. Although we had an Ops Area review, we did not get a lot of responses from participants who were not already authors of the draft. We are therefore running another working group last call on draft-ietf-bess-evpn-proxy-arp-nd-06. Please indicate to the list if you have read the draft and support its publication as an RFC. Please also indicate to the list if you have read the draft and do not support its publication. Please also send any other last call comments to the BESS list. This last call ends on Friday 21st June 2019. Regards Matthew and Stephane _______________________________________________ BESS mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/bess
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
