[IPsec] Re: I-D Action: draft-ietf-ipsecme-g-ikev2-17.txt

2024-12-02 Thread Antony Antony
Hi Valery, On Mon, Dec 02, 2024 at 06:18:35PM +0300, Valery Smyslov wrote: > Hi Antony, > > > > > Number NameReference > > > > 0 32-bit Sequential Numbers (SN) [RFC7296] > [this ID] > > > > 1 64-bit Sequential Numbers (ESN) [RFC7296] [this ID] > > > >

[IPsec] Re: I-D Action: draft-ietf-ipsecme-g-ikev2-17.txt

2024-12-02 Thread Valery Smyslov
Hi Antony, > > > Number NameReference > > > 0 32-bit Sequential Numbers (SN) [RFC7296] [this ID] > > > 1 64-bit Sequential Numbers (ESN) [RFC7296] [this ID] > > > 2 32-bit Unspecified [this ID] > > > 3-65535

[IPsec] Re: Rechartering IPsecME

2024-12-02 Thread Daniel Migault
Hi Paul, In a charter discussion, references to drafts typically serve to demonstrate that some progress has been made or is currently underway within the solution space. These drafts are presented as a starting point, which does not preclude the consideration of alternative proposals. On Tue, No

[IPsec] Re: I-D Action: draft-ietf-ipsecme-g-ikev2-17.txt

2024-12-02 Thread Antony Antony
Hi Valery, On Mon, Dec 02, 2024 at 09:28:05AM +0300, Valery Smyslov wrote: > Hi Tero, > > > Valery Smyslov writes: > > > Hi Antony, > > > Combining with the proposal above: > > > > > > Number NameReference > > > 0 32-bit Sequential Numbers (SN) [RFC7296] [this > > >

[IPsec] Re: I-D Action: draft-ietf-ipsecme-g-ikev2-17.txt

2024-12-02 Thread Antony Antony
On Mon, Dec 02, 2024 at 05:31:00AM +0200, Tero Kivinen wrote: > Valery Smyslov writes: > > Hi Antony, > > Combining with the proposal above: > > > > Number NameReference > > 0 32-bit Sequential Numbers (SN) [RFC7296] [this ID] > > 1 64-bit Sequential Numbers (ESN)

[IPsec] Re: Rechartering IPsecME

2024-12-02 Thread Tero Kivinen
Daniel Migault writes: > In a charter discussion, references to drafts typically serve to demonstrate > that some progress has been made or is currently underway within the solution > space. These drafts are presented as a starting point, which does not preclude > the consideration of alternative p

[IPsec] Re: [Last-Call] Secdir last call review of draft-ietf-ipsecme-g-ikev2-17

2024-12-02 Thread Russ Housley
Valery: >> I find the use of GIKE_REKEY and GSA_REKEY a little bit confusing. >> I think it would help the reader if these were discussed a bit in the >> Introduction. > > GSA_REKEY is an type of G-IKEv2 (pseudo) exchange, it appears in the G-IKEv2 > Header (Exchange Type field). > The GIKE_REK

[IPsec] Re: I-D Action: draft-ietf-ipsecme-g-ikev2-17.txt

2024-12-02 Thread Tero Kivinen
Valery Smyslov writes: > Some candidates: > > Sequence Number Properties (SNP) > Sequence Number Interpretation (SNI) (can be mixed up with SNI in TLS) > Sequence Number Features (SNF) > > Thoughts? Other proposals? All of those works for me, just pick whatever you like. SNP sounds fine...

[IPsec] Re: Rechartering IPsecME

2024-12-02 Thread Antony Antony
On Mon, Dec 02, 2024 at 06:54:02AM +0200, Tero Kivinen wrote: > Antony Antony writes: > > I have a minor clarification question. > > Would this cover the work proposed in draft-antony-ipsecme-ikev2-beet-mode? > > > > I imagine it does, but I’m seeking confirmation because at the Dublin > > meet

[IPsec] Re: I-D Action: draft-ietf-ipsecme-g-ikev2-17.txt

2024-12-02 Thread Valery Smyslov
Hi Antony, > > Some candidates: > > > > Sequence Number Properties (SNP) Got it, thanks. > SNP sounds good to me as well. However, I have a question about the IKEv2 IANA > document. Would the registry end up being titled simply 'Sequence Number > Properties Transforms ID'? Yes (to be pedantic: