| rfc9827v3.txt | rfc9827.txt | |||
|---|---|---|---|---|
| skipping to change at line 178 ¶ | skipping to change at line 178 ¶ | |||
| network and not for the packets that receivers get. This is | network and not for the packets that receivers get. This is | |||
| because network behavior may break some of these properties (e.g., | because network behavior may break some of these properties (e.g., | |||
| packet duplication would break sequence number uniqueness). | packet duplication would break sequence number uniqueness). | |||
| * The properties of sequence numbers are interpreted in a broad | * The properties of sequence numbers are interpreted in a broad | |||
| sense, which includes the case when sequence numbers are absent. | sense, which includes the case when sequence numbers are absent. | |||
| Given this updated definition, Transform Type 5 in the "Transform | Given this updated definition, Transform Type 5 in the "Transform | |||
| Type Values" registry [IKEV2-IANA] has been renamed from "Extended | Type Values" registry [IKEV2-IANA] has been renamed from "Extended | |||
| Sequence Numbers (ESN)" to "Sequence Numbers (SN)" in the sense that | Sequence Numbers (ESN)" to "Sequence Numbers (SN)" in the sense that | |||
| it defines the properties of the sequence numbers in a broad sense. | it defines the properties of the sequence numbers in general. | |||
| It is expected that new Transform IDs will be defined for this | It is expected that new Transform IDs will be defined for this | |||
| Transform Type in the future (like in G-IKEv2 [G-IKEv2] for the case | Transform Type in the future (like in G-IKEv2 [G-IKEv2] for the case | |||
| of multicast SAs). Documents defining new Transform IDs should | of multicast SAs). Documents defining new Transform IDs should | |||
| include descriptions of the properties the sequence numbers would | include descriptions of the properties the sequence numbers would | |||
| have if the new Transform ID was selected. In particular, the | have if the new Transform ID was selected. In particular, the | |||
| descriptions should include discussion of whether these properties | descriptions should include discussion of whether these properties | |||
| allow replay protection to be achieved. | allow replay protection to be achieved. | |||
| Some existing protocols (like Implicit IV in ESP [RFC8750] or | Some existing protocols (like Implicit IV in ESP [RFC8750] or | |||
| End of changes. 1 change blocks. | ||||
| 1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||