Search RFCs

RFC Editor

Found 2 records.

Status:Held for Document Update (1)

RFC 4309, "Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)", December 2005

Errata ID:130
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Aaron Cohen
Date Reported: 2006-01-05
Held for Document Update by: Pasi Eronen

Page heading says:

RFC 4309           Using AEC CCM Mode with IPsec ESP       December 2005

It should say:

RFC 4309           Using AES CCM Mode with IPsec ESP       December 2005

Notes:

In RFC 4309 the page headings have a typo AES is misspelled as AEC.

Status:Rejected (1)

RFC 4309, "Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)", December 2005

Errata ID:129
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-02-03
Rejected by: Russ Housley

Section 5 says:

On page 6, the second paragraph of Section 5 says:   Sequence Numbers are conveyed canonical network byte order.  Extended   Sequence Numbers are conveyed canonical network byte order, placing   the high-order 32 bits first and the low-order 32 bits second.   Canonical network byte order is fully described in RFC 791, Appendix   B.The text should perhaps better say:   Sequence Numbers are conveyed in canonical network byte order.   Extended Sequence Numbers are conveyed in canonical network byte   order, placing the high-order 32 bits first and the low-order 32 bits   second.  Canonical network byte order is fully described in RFC 791,   Appendix B.The second half-sentence of the second sentence might even be consideredredundant, fully comprised by the term 'canonical network byte order',and hence be omitted entirely.  Doing that, and following the maxim of"making RFC text as simple as possible", the above text might beabreviated to say:   Sequence Numbers and Extended Sequence Numbers are conveyed in   canonical network byte order.  Canonical network byte order is fully   described in RFC 791, Appendix B.Finally, considering that the SPI is a 32-bit number and covered bythe same ordering rule as well, the text might - even shorter - say:   All fields are conveyed in canonical network byte order.  Canonical   network byte order is fully described in RFC 791, Appendix B.Please decide whether the initial text correction deserves anErrata Note, possibly including the additional enhancement(s).

Notes:

word omissions - and opportunity to simplify the text

NOTE (2006-02-13)
I do not think that any of these will lead to confusion or
interoperability concerns. Thus, I do not think that they warrant
the time and other resources need to generate Errata.
Russ Housley

from pending

Report New Errata