Hello Greg,
Thank you very much for addressing all my points were applicable. I am changing
my ABSTAIN into a NO OBJECTION (even if it does not really matter)
Regards
-éric
From: iesg on behalf of Greg Mirsky
Date: Monday, 21 December 2020 at 01:56
To: Eric Vyncke
Cc: Stephane Litkowski ,
Hi Eric,
apologies for the belated response. Please find my answers below in-lined
tagged by GIM>>.
Regards,
Greg
On Wed, Dec 16, 2020 at 2:05 AM Éric Vyncke via Datatracker <
nore...@ietf.org> wrote:
> Éric Vyncke has entered the following ballot position for
> draft-ietf-bess-mvpn-fast-failove
ss-cha...@ietf.org" ,
"draft-ietf-bess-mvpn-fast-failo...@ietf.org"
, "bess@ietf.org"
Subject: RE: [bess] Éric Vyncke's Abstain on
draft-ietf-bess-mvpn-fast-failover-13: (with COMMENT)
Ah. Perhaps vendors forgot/neglected to respond on the implement
'The IESG'
Cc: bess-cha...@ietf.org; draft-ietf-bess-mvpn-fast-failo...@ietf.org;
bess@ietf.org
Subject: Re: [bess] Éric Vyncke's Abstain on
draft-ietf-bess-mvpn-fast-failover-13: (with COMMENT)
[External Email. Be cautious of content]
Hi Eric,
Speaking as BESS WG chair, you rai
Hi Eric,
You say "because of the use outside of a node of the IPv4-mapped IPv6 addresses
in section 3.1.6.1. A reply on this topic will be welcome."
I understand your point about using IPv4-mapped IPv6 address
":::127.0.0.0/104", as it is assumed to never leave a node and should never
be t
Hi Eric,
Speaking as BESS WG chair, you raised a very valid point on the publication of
documents that have no implementation (or plan of implementation). This is also
a concern that I have in general, as we cannot really prove that a
technology/specification is working properly if it hasn't be
