Hi John,
The duplication itself is a problem - a receiver should not receive duplicates.
However, a source should not send the same packet to two BDs. That's what the
paragraph is supposing:
... (This does assume that source S does not
send the same (S,G) datagram on two
On Mar 7, 2024, at 9:47 AM, Jeffrey (Zhaohui) Zhang wrote:
>
> zzh> If the source host is also connected to another BD3 that is attached to
> PE2 and it is sending to both BD2 and BD3, then both copies will be switched
> to PE1 via the SBD
So the only consequence is suboptimality because of
I support this document for WG adoption.
I'm not aware of any related undisclosed IPR.
From: Jeffrey (Zhaohui) Zhang
Date: Wednesday, March 6, 2024 at 1:32 PM
To: 'BESS' , draft-sr-bess-evpn-dp...@ietf.org
Cc: idr@ietf. org , 'bess-cha...@ietf.org'
Subject: WG Adoption and IPR Poll for
The following errata report has been held for document update
for RFC8214, "Virtual Private Wire Service Support in Ethernet VPN".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7837
--
Hi John,
Thank you for your review and comments. A new revision will be posted after the
pre-IETF119 quiescence period.
Please see zzh> below.
-Original Message-
From: John Scudder via Datatracker
Sent: Wednesday, March 6, 2024 8:08 PM
To: The IESG
Cc:
Thanks, Rob.
I have changed that. A new revision with some other minor changes will be
posted after the pre-IETF119 quiescence period.
Jeffrey
Juniper Business Use Only
-Original Message-
From: Robert Wilton via Datatracker
Sent: Thursday, March 7, 2024 6:34 AM
To: The IESG
Cc:
As a co-author, I support this document for WG adoption.
I'm not aware of any related undisclosed IPR.
Thanks,
Mallika
-Original Message-
From: Jeffrey (Zhaohui) Zhang
Sent: Wednesday, March 6, 2024 10:32 AM
To: 'BESS' ; draft-sr-bess-evpn-dp...@ietf.org
Cc: idr@ietf. org ;
Robert Wilton has entered the following ballot position for
draft-ietf-bess-evpn-irb-mcast-11: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
