udder"
Date: Saturday, October 10, 2020 at 7:16 PM
To: "Satya Mohanty (satyamoh)"
Cc: "Ali Sajassi (sajassi)" ,
"draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org"
, BESS
Subject: Re: [bess] Second try: Router's MAC Extended Community in
draft-ietf-bess-ev
2020 at 12:15 PM
To: "John G. Scudder"
Cc: "draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org"
, BESS
Subject: Re: [bess] Second try: Router's MAC Extended Community in
draft-ietf-bess-evpn-inter-subnet-forwarding
Hi John,
Thanks for your feedback. I was also think
quot;draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org"
, BESS
Subject: Re: [bess] Second try: Router's MAC Extended Community in
draft-ietf-bess-evpn-inter-subnet-forwarding
Hi John,
Thanks for your feedback. I was also thinking along the line of (2). I’ll take
care of it in th
t;
, BESS
Subject: Re: Second try: Router's MAC Extended Community in
draft-ietf-bess-evpn-inter-subnet-forwarding
Resent-From:
Resent-To: Cisco Employee , ,
, ,
Resent-Date: Thursday, October 8, 2020 at 11:57 AM
Thanks, Ali.
Yes, I think this should be explicit in the spec. I’d also suggest being
rward...@ietf.org>>
Cc: BESS mailto:bess@ietf.org>>
Subject: Second try: Router's MAC Extended Community in
draft-ietf-bess-evpn-inter-subnet-forwarding
Resent-From: mailto:alias-boun...@ietf.org>>
Resent-To: Cisco Employee mailto:saja...@cisco.com>>,
mailto:ssa...@cisco.com>>
Scudder
Date: Thursday, October 8, 2020 at 11:12 AM
To: "draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org"
Cc: BESS
Subject: Second try: Router's MAC Extended Community in
draft-ietf-bess-evpn-inter-subnet-forwarding
Resent-From:
Resent-To: Cisco Employee , ,
, ,
Resent-Date
Hi Authors,
I haven’t seen a reply to this message from almost a month ago, trying again.
Even if you are still debating the answer amongst yourselves, it would be
comforting to me to receive a reply to the effect of “we’re still thinking
about this and will get back to you by $date”.
Thanks,
