Found 2 records.

Status: Held for Document Update (2)

RFC 5997, "Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol", August 2010

Errata ID: 2507
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-09-01
Held for Document Update by: Dan Romascanu

Section 3, pg.9 says:

[[  last paragraph on page 9 (extending to page 10): ]]

|  The Access-Accept MAY contain a Reply-Message or Message-
   Authenticator attribute.  It SHOULD NOT contain other attributes.
   The Accounting-Response packets sent in response to a Status-Server
   query SHOULD NOT contain any attributes.  [...]

It should say:

|  The Access-Accept sent in response to a Status-Server query MAY
   contain a Reply-Message or Message-Authenticator attribute.  It
   SHOULD NOT contain other attributes.
   The Accounting-Response packets sent in response to a Status-Server
   query SHOULD NOT contain any attributes.  [...]

Notes:

Rationale: Bare "Access-Accept" is potentially misleading.
The clause needed to properly restrict the scope of the sentence
has been added in most similar instances of specification text
in the RFC, but that has been missed here. So for consistency and
clarity, the New text once more provides this additional clause --
as it already appears in the 3rd sentence of this paragraph.

Errata ID: 2508
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-09-01
Held for Document Update by: Dan Romascanu

Section 4.6.2, pg.17 says:

4.6.2.  Interaction with RADIUS Client MIB Modules

   Clients implementing Status-Server MUST NOT increment [RFC4668] or
   [RFC4670] counters upon reception of Response packets to Status-
|  Server queries.  That is, when a server fully implements Status-
   Server, the counters defined in [RFC4668] and [RFC4670] MUST be
   unaffected by the transmission or reception of packets relating to
   Status-Server.

It should say:

4.6.2.  Interaction with RADIUS Client MIB Modules

   Clients implementing Status-Server MUST NOT increment [RFC4668] or
   [RFC4670] counters upon reception of Response packets to Status-
|  Server queries.  That is, when a client fully implements Status-
   Server, the counters defined in [RFC4668] and [RFC4670] MUST be
   unaffected by the transmission or reception of packets relating to
   Status-Server.

Notes:

Rationale: Confusion between "server" and "client".
This section deals with client implementations only;
the reference to a server apparently is the result of an
oversight in copy-editing text from Section 4.6.1, 2nd para.

Report New Errata