Summary

  • RFC 5412 is a Historic record of LWAPP, not an Internet Standards Track deployment specification.
  • Its access-controller, WTP, security and 802.11 message elements describe a protocol snapshot, not present product support.
  • RFC 5415, implementation matrices, interoperability tests and live controller telemetry are separate evidence.

Historic status changes the question

RFC 5412 describes a centralized controller managing lightweight access points and includes an 802.11 binding. The protocol can be useful for understanding the design path toward CAPWAP. But the RFC Editor says the document was published solely for the historical record, was not thoroughly reviewed, may contain errors and omissions, and should not be used as a basis for deployment.

A message element is not a WLAN outcome

LWAPP configuration elements can describe SSIDs, radios, authentication types, supported rates and other WTP state. Seeing a field in the document does not show that a current access point accepts it, that a controller can negotiate it, or that a client received the intended service. Credentials and authorization in the protocol description also do not prove a production policy decision.

Replacement and evidence boundary

RFC 5415 documents the standards-track CAPWAP solution and obsoletes the mechanisms in RFC 5412. A migration decision therefore needs the exact controller and WTP versions, the negotiated protocol, the replacement's conformance evidence, the security exchange, the applied WLAN configuration and observed client traffic. Historic documentation reduces archaeology cost; it does not certify today's wireless control plane.