@@ -192,17 +192,15 @@ receiver MUST enable Reply Protection.
192192# NOTE STK: I'd say MUST above as we want to negotiate Anti-Replayservice
193193# and not just the presense of the seq nr field.
194194
195- When the Transform Type [[IKEv2-SN]] is not present in initiator's
196- Child SA proposal during negotiation of an EESP Child SA, the
197- Sequence Number field MUST NOT be transmitted in the EESP packet.
198-
199- When the Replay Prtection is not negotiated, i.e., when the 64 bit
200- sequence number is not carried in the EESP packet, an EESP receiver
201- should not act on address or port changes. It should not initiate a
202- dynamic address update without the use of IKEv2 Mobility [[RFC4555]].
203- Since the Replay Protection service is disabled, an attacker could
204- replay packets with a different source address. An attacker could disrupt
205- the connection by capturing and replaying a single packet with different
195+ To disable sequence numbering, and thus replay protection based on
196+ sequence numbers, the initiator MUST propose SN=None (TBD10). When the
197+ sequence numbers are disabled, there won't be any SN in the
198+ EESP packet, the receiver SHOULD NOT dynamically modify ports or
199+ addresses without using IKEv2 Mobility [RFC4555].
200+
201+ Because the Replay Protection service is disabled, an attacker can re
202+ play packets with a different source address. Such an attacker could
203+ disrupt the connection by replaying a single packet with a different
206204source address or port number.
207205
208206** Explicit Initialization Vector
@@ -220,7 +218,7 @@ packet. To enable this functionality, IIV transforms defined in
220218the [[IKEv2-SN]] extension MUST be negotiated to support the use of
221219a Full 64-bit Sequence Numbers in EESP packets. If the the proposal
222220does not include Full 64-bit Sequence Numbers return error
223- INVALID_SN .
221+ NO_PROPOSAL_CHOSEN .
224222
225223** EESP Version
226224Each SA need an EESP Base Header version which is specified
@@ -482,17 +480,17 @@ This document defines new Notify Message types in the
482480|-------------+----------------------+-----------------+
483481| [TBD2] | INVALID_SESSION_ID | [this document] |
484482| [TBD3] | INVALID_SUB_SA | [this document] |
485- | [TBD10]| INVALID_SN | [this document] |
486483
487484
488485*** Sequence Number
489486
490487This document defines a new value in the IKEv2 "Transform Type 5 - Sequence
491488 Numbers Properties Transform IDs" registry:
492489
493- | Value | Name | Reference |
494- |-------------+--------------------------+-----------------+
495- | [TBD9] | Full 64-bit Sequence Numbers | [this document] |
490+ | Value | Name | Reference |
491+ |---------+-------------------------------+-----------------+
492+ | [TBD9] | Full 64-bit Sequence Numbers | [this document] |
493+ | [TBD10] | Full 64-bit Sequence Numbers | [this document] |
496494
497495** New Registries
498496
664662:REF_ORG: NIST
665663:END:
666664
665+ ** Keccak-vs-AES
666+ :PROPERTIES:
667+ :REF_TARGET: https://cryptography.gmu.edu/athena/papers/GMU_DATE_2015.pdf
668+ :REF_TITLE: Comparison of Multi-Purpose Cores of Keccak and AES
669+ :REF_ORG: NIST
670+ :END:
671+
667672* Additional Stuff
668673
669674TBD
0 commit comments