RFC 5116, "An Interface and Algorithms for Authenticated Encryption", January 2008Source of RFC: IETF - NON WORKING GROUP
Area Assignment: sec
See Also: RFC 5116 w/ inline errata
Errata ID: 4268
Publication Format(s) : TEXT
Reported By: Martin Thomson
Date Reported: 2015-02-09
Verifier Name: Kathleen Moriarty
Date Verified: 2015-03-31
Section 3.1 says:
As an example, the nonce 100 could be stored, after which the nonces 1 through 99 could be used for encryption. The nonce value 200 could be stored at the same time that nonces 1 through 99 are being used, and so on.
It should say:
As an example, the nonce 100 could be stored, after which the nonces 1 through 99 could be used for encryption. Then, nonces 101 to 199 could be used after the nonce 200 was saved.
This might be confusing in its original form, maybe even suggesting an interpretation where nonces are reused.