RFC Errata
Found 7 records.
Status: Verified (3)
RFC 5412, "Lightweight Access Point Protocol", February 2010
Source of RFC: INDEPENDENT
Errata ID: 8460
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2025-06-13
Verifier Name: RFC Editor
Date Verified: 2025-07-10
Section 7.4 says:
7.4.11. Add Static Blacklist Entry [...] Type: 70 for Delete Blacklist Entry [...] 7.4.12. Delete Static Blacklist Entry [...] Type: 71 for Delete Blacklist Entry
It should say:
7.4.11. Add Static Blacklist Entry [...] Type: 70 for Add Static Blacklist Entry [...] 7.4.12. Delete Static Blacklist Entry [...] Type: 71 for Delete Static Blacklist Entry
Notes:
The message element numbers do not immediately look incorrect, but the names clearly have been repeated with no change from Section 7.4.10.
Errata ID: 8467
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2025-06-19
Verifier Name: RFC Editor
Date Verified: 2025-06-25
Section 9.2 says:
The Mobile Configuration Response is used to acknowledge a previously received Mobile Configuration Request, and includes a Result Code message element that indicates whether an error occurred on the WTP. This message requires no special processing and is only used to acknowledge the Mobile Configuration Request. The Data Transfer Request message MUST contain the message elements described in the next subsection.
It should say:
The Mobile Config Response is used to acknowledge a previously received Mobile Config Request, and includes a Result Code message element that indicates whether an error occurred on the WTP. This message requires no special processing and is only used to acknowledge the Mobile Config Request. The Mobile Config Response message MUST contain the message element described in the next subsection.
Notes:
Section 9.2 describes "Mobile Config Response", not "Mobile Configuration Response" (incorrect spelling) or "Data Transfer Request" (an entirely different message type). "Mobile Config Response" is an acknowledgement of "Mobile Config Request", not "Mobile Configuration Request" (incorrect spelling). The next subsection describes exactly one message element.
Errata ID: 8473
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2025-06-20
Verifier Name: RFC Editor
Date Verified: 2025-06-25
Section 8.5 says:
When an AC receives a WTP Event Request, it will respond with a WTP Event Request.
It should say:
When an AC receives a WTP Event Request, it will respond with a WTP Event Response.
Notes:
This statement tries to rephrase what the immediately following Section 8.6 says. The second instance of "Request" in the original text should be "Response".
Status: Reported (3)
RFC 5412, "Lightweight Access Point Protocol", February 2010
Source of RFC: INDEPENDENT
Errata ID: 8510
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2025-07-12
Section 4.2.2 says:
The message element is used to carry information pertinent to a control message. Every message element is identified by the Type field, whose numbering space is managed via IANA (see Section 16).
It should say:
The message element is used to carry information pertinent to a control message. Every message element is identified by the Type field, whose numbering space is not managed via IANA.
Notes:
This document does not have an "IANA Considerations" section (Section 16 is "Acknowledgements"). IANA does not define a registry for LWAPP.
Errata ID: 8509
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2025-07-12
Section 8.1.1 says:
The Image Download message element is sent by the WTP to the AC and contains the image filename. The value is a variable-length byte string. The string is NOT zero terminated.
It should say:
The Image Download message element is sent by the WTP to the AC and contains the image filename. The value is a variable-length byte string. The string is NOT zero terminated. Note that this document does not assign a Type value to this message element.
Notes:
This seems to be the only message element in this document without an assigned code point.
Errata ID: 8511
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2025-07-12
Section 4.2.1.1 says:
The Message Type field identifies the function of the LWAPP control message. The valid values for a Message Type are the following:
It should say:
The Message Type field identifies the function of the LWAPP control message. This document does not assign a Message Type value to the following messages: Key Update ACK (Section 6.9), Key Update Confirm (Section 6.10), Key Update Trigger (Section 6.11) and IEEE 802.11 WTP Event (Section 11.8.3). For all other messages the valid values for a Message Type are the following:
Notes:
This document defines a few message types that do not have an assigned code point.
Status: Held for Document Update (1)
RFC 5412, "Lightweight Access Point Protocol", February 2010
Source of RFC: INDEPENDENT
Errata ID: 4536
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Tony Deng
Date Reported: 2015-11-18
Held for Document Update by: Nevil Brownlee
Date Held: 2017-07-20
Section 7.2.3 says:
The AC Name with Index message element is sent by the AC to the WTP
to configure preferred ACs. The number of instances where this
message element would be present is equal to the number of ACs
configured on the WTP.
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index | AC Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 90 for AC Name with Index
Length: 5
Index: The index of the preferred server (e.g., 1=primary,
2=secondary).
AC Name: A variable-length ASCII string containing the AC's name.
Notes:
This entire section is in the wrong location or needs to be revised. Section 7.2 is the definition for Configure Request, which is suppose to be a message sent from the WTP to the AC. But here at 7.2.3, this message element clearly states it is an element to be sent from the AC to the WTP. Does this section belong in the Configure Response section instead?
[This section does seem to be in the wrong place. However, moving it will need to wait fo a new (revised) RFC. ISE, July 2017]