Valery,
In English, adjectives are *never* declined. So, whether you are
referring to a single number or a set of numbers, it must always be
written as "Sequence Number Properties".
However, if you need to bring the plural into the equation, the fix is
simple: you just write "Properties of Sequence Numbers".
So, you have two choices:
1) change "Numbers" to "Number" or
2) change "Sequence Number Properties" to "Properties of Sequence Numbers".
This change will need to be done in the Abstract as well as in the body
of the draft.
Bill Atwood
On 12/12/2024 3:43 AM, Valery Smyslov wrote:
Attention This email originates from outside the concordia.ca domain. // Ce
courriel provient de l'extérieur du domaine de concordia.ca
Hi Antony,
Hi Tero,
I support advancing this document.
Valery,
I wonder Number or Numbers. May be double check?
I think following are the correct use, in singular.
My reasoning for using plural form is that we here are speaking about the
properties
of not a single sequence number (in some packet sent by some sender),
but about the properties that sequence numbers from all packets of a given
SA (as a whole) hold.
Perhaps this is not a good argument from native speaker PoV,
so I'm open for suggestions and corrections :-)
"Sequence Number Properties (SNP)" instead of "Sequence Numbers Properties
(SNP)"
"Partially Transmitted 64-bit Sequential Number" instead of "Partially
Transmitted
64-bit Sequential Numbers"
"No Extended Sequence Number" instead of "No Extended Sequence Numbers" to
"No Extended Sequence Numbers" (as well as "Extended Sequence Numbers")
is the existing name of transform ID in the RFC7296, so this case is
correct.
RFC4303 use mostly singular for ESN, only in Appendix A it use plural.
That's right, but only when it defines how a single sequence number is
generated
and verified, thus it is appropriate to use singular form.
When RFC 4303 speaks about the properties of sequence number as a whole,
(whether they are 32-bit SN or 64-bit ESN), it uses plural form. See Section
2.2.1, 3.4.2
as examples.
Regards,
Valery.
-antony
On Fri, Dec 06, 2024 at 02:17:30AM +0200, Tero Kivinen wrote:
As we talked earlied when doing g-ikev2 IETF last call, the text
talking about renaming ESN transform type got separated to this new
draft, and this will start one (1) week working group last call of the
draft.
I try to make this fast so it can catch up the g-ikev2 draft (which is
in IETF LC until 2024-12-10), so unless we get objections during WGLC,
I will request publication of ths draft almst immediately after the
WGLC ends.
Send your comments about the draft to the ipsec list before
2024-12-13.
--
kivi...@iki.fi
_______________________________________________
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org
_______________________________________________
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org
--
Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046
Distinguished Professor Emeritus fax: +1 (514) 848-2830
Department of Computer Science
and Software Engineering
Concordia University ER 1234 email:william.atw...@concordia.ca
1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8
_______________________________________________
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org
