I support adoption as contributor and am unaware of any relevant undisclosed
IPR.
Iman Ghamari
From: Patrice Brissette (pbrisset)
Date: Monday, June 12, 2023 at 11:21 AM
To: Iman Ghamari
Subject: FW: [bess] WG adoption for draft-brissette-bess-evpn-vpws-seamless
FYI
Regards,
Patrice Brissette
I support adoption as contributor and am unaware of any undisclosed IPR
Regards,
Luc André
Luc André Burdet | Cisco | laburdet.i...@gmail.com | Tel: +1 613 254 4814
From: BESS on behalf of slitkows.i...@gmail.com
Date: Wednesday, May 24, 2023 at 04:02
To: bess@ietf.org
Cc: bess-cha...@
Support as a co-author. I am unaware of any IPRs.
Thanks,
Wen
Juniper Business Use Only
From: BESS on behalf of Mankamana Mishra (mankamis)
Date: Thursday, May 25, 2023 at 11:31 AM
To: slitkows.i...@gmail.com , bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WG adoption for dra
Shunwan,
Good catch! ID length is in bytes and Nonce length is also in bytes. I will
update the draft accordingly.
Cheers,
Ali
From: Zhuangshunwan
Date: Monday, June 12, 2023 at 1:36 AM
To: draft-sajassi-bess-secure-e...@ietf.org
Cc: bess@ietf.org
Subject: Mail regarding draft-sajassi-bess-
Menachem,
You are welcome.
As for the text in Sections 9.1 and 15 – personally I do not see the need for
updated wording.
Regards,
Sasha
From: Menachem Dodge
Sent: Monday, June 12, 2023 4:04 PM
To: Alexander Vainshtein
Cc: bess@ietf.org
Subject: Re: [EXTERNAL] [bess] MAC Mobility Section 9.1
Hello Sasha,
Thanks very much for your response.
Should the wording in section 9.1 and section 15 be modified to indicate this
more clearly?
Best Regards,
Menachem
From: Alexander Vainshtein
Date: Monday, 12 June 2023 at 15:21
To: Menachem Dodge
Cc: bess@ietf.org
Subject: RE: [EXTERNAL] [be
Menachem and all,
Inline below.
Hope this helps.
Regards,
Sasha
From: BESS On Behalf Of Menachem Dodge
Sent: Monday, June 12, 2023 2:46 PM
To: bess@ietf.org
Subject: [EXTERNAL] [bess] MAC Mobility Section 9.1 and 15 - Draft
draft-ietf-bess-7432bis-07
Hello All,
In Section 9.1 of it states:
Th
Hello All,
In Section 9.1 of it states:
There are applications where a MAC address that is reachable via a
given PE on a locally attached segment (e.g., with ESI X) may move,
such that it becomes reachable via another PE on another segment
(e.g., with ESI Y). This is referred to as "MA
Dear Co-Authors,
Thank you for contributing this very useful document! I support the adoption of
this document.
One comment:
Regarding the "ID Length" and "Nonce Length" in the Base (Minimal Set) DIM
Sub-TLV, Figure 6 shows the following:
0 1 2
