Hi Antony,
> Hi Valery,
>
> While skimming through the draft, I noticed (partial) renaming of ESN to ARP,
> including the proposed IKEv2 IANA registry changes. I have a few concerns
> about
> this.
>
> ESN is a widely recognized term, but admittedly a confusing one, especially
> since it
> app
Hi Valery,
While skimming through the draft, I noticed (partial) renaming of ESN to
ARP, including the proposed IKEv2 IANA registry changes. I have a few concerns
about this.
ESN is a widely recognized term, but admittedly a confusing one, especially
since it applies to both IKEv2 negotiation an
On Nov 28, 2024, at 07:16, Valery Smyslov wrote:
>
>
> "Anti-Replay Protection (ARP)" transform type was originally named
> "Extended Sequence Numbers (ESN)" and was referenced by that name
> in a number of RFCs published prior to [RFC], which gave it
> the current title
On Thu, Nov 28, 2024 at 03:15:36PM +0300, Valery Smyslov wrote:
> Hi Antony,
>
> > Hi Valery,
> >
> > While skimming through the draft, I noticed (partial) renaming of ESN to
> > ARP,
> > including the proposed IKEv2 IANA registry changes. I have a few concerns
> > about
> > this.
> >
> > ESN
Hi,
On Thu, Nov 28, 2024 at 09:48:47AM -0500, Paul Wouters wrote:
> On Nov 28, 2024, at 07:16, Valery Smyslov wrote:
> >
> >
> > "Anti-Replay Protection (ARP)" transform type was originally named
> > "Extended Sequence Numbers (ESN)" and was referenced by that name
> > in a numb
Hi Paul,
> > "Anti-Replay Protection (ARP)" transform type was originally named
> > "Extended Sequence Numbers (ESN)" and was referenced by that name
> > in a number of RFCs published prior to [RFC], which gave it
> > the current title.
> >
> > Do you think this is not enou
