Éric,
The following edits are ready for submission. Confirm these are what you want
in -13 and they'll go out.
-- Jeff
> On Oct 17, 2024, at 2:29 AM, Eric Vyncke (evyncke) wrote:
>
> Jeff and other authors,
>
> Thanks for your patience on this one.
>
> Except for the point below EVY2>,
then I will move forward with the IETF last call.
Regards
-éric
From: Jeffrey Haas
Date: Friday, 11 October 2024 at 17:59
To: Eric Vyncke (evyncke)
Cc: rtg-bfd@ietf.org , John Scudder ,
af...@bloomberg.net , Reshad Rahman
Subject: Re: Alternate AD review of draft-ietf-bfd-large-packets-11
[Re
Thanks, Reshad.
Éric, I think this means all outstanding items are addressed and we can
progress the document to the next step?
-- Jeff
> On Oct 15, 2024, at 11:17 AM, Reshad Rahman wrote:
>
> Eric, Jeff,
>
>
> On Friday, October 11, 2024 at 12:00:39 PM EDT, Jeffrey Haas
> wrote:
>
>
>
Eric, Jeff,
On Friday, October 11, 2024 at 12:00:39 PM EDT, Jeffrey Haas
wrote:
# shepherd write-up It contains `we will discuss further at the next
IETF`, but it is unclear which IETF meeting ;) and if it was IETF-120, then
what was the outcome of the discussion ?
We briefly disc
[Response to original mail to track the main points.]
Thanks for your patience for this next update. My responses here will be
reflected in an updated version that will ship in parallel with this email.
> On Aug 14, 2024, at 7:58 AM, Eric Vyncke (evyncke) wrote:
>
> Dear BFD, dear authors,
>
af...@bloomberg.net , Reshad Rahman
Subject: Re: Alternate AD review of draft-ietf-bfd-large-packets-11
Éric,
I'm deep in the last stages of getting some important day-job stuff out the
door, so the edits may linger for a little bit. But let me at least answer the
questions portion.
Note t
Éric,
I'm deep in the last stages of getting some important day-job stuff out the
door, so the edits may linger for a little bit. But let me at least answer the
questions portion.
Note that this draft's text is checked into github as noted in the datatracker.
Many of your edits could have av
Dear BFD, dear authors,
To lighten John Scudder’s workload, I will be the alternate responsible AD for
draft-ietf-bfd-large-packets. As I am an INT AD, please bear with me if I state
something wrong about BFD ;-)
Before proceeding with the publication process, I usually do my AD review
before
