- changed status to resolved
Typo in referencing OSCORE's technique for persistent storage of sequence numbers
Issue #45
resolved
Tag: WGLC
As per discussion with Jim Schaad (https://mailarchive.ietf.org/arch/msg/6tisch/PwMRvb_zG6VmUwmVMqk2NLJmBbI):
Mališa Vučinić wrote:
Currently, Section 8.1.1. of draft-ietf-6tisch-minimal-security states:
Implementations MUST ensure that mutable OSCORE context parameters (Sender Sequence Number, Replay Window) are stored in persistent memory. A technique that prevents reuse of sequence numbers, detailed in Section 6.5.1 of [I-D.ietf-core-object-security], MUST be implemented. Each update of the OSCORE Replay Window MUST be written to persistent memory.
In the text above, there is a typo: s/Section 6.5.1/Section 7.5.1
Comments (2)
-
reporter -
reporter - edited description
- Log in to comment
Commit: f57115efda7633