RFC Errata
RFC 2866, "RADIUS Accounting", June 2000
Note: This RFC has been updated by RFC 2867, RFC 5080, RFC 5997
Source of RFC: radius (ops)
Errata ID: 5417
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Nick Lowe
Date Reported: 2018-07-06
Held for Document Update by: Ignas Bagdonas
Date Held: 2019-10-28
Section 5.11 says:
This attribute is a unique Accounting ID to make it easy to link together multiple related sessions in a log file. Each session linked together would have a unique Acct-Session-Id but the same Acct-Multi-Session-Id. It is strongly recommended that the Acct- Multi-Session-Id contain UTF-8 encoded 10646 [7] characters.
It should say:
This attribute is a unique Accounting ID to make it easy to link together multiple related sessions in a log file. Each session linked together would have a unique Acct-Session-Id but the same Acct-Multi-Session-Id. The start and stop records for a given session MUST have the same Acct-Multi-Session-Id. An Access-Request packet MAY contain Acct-Multi-Session-Id; if it does, then the NAS MUST use the same Acct-Multi-Session-Id in the Accounting-Request packets for that session. It is strongly recommended that the Acct-Multi-Session-Id contain UTF-8 encoded 10646 [7] characters.
Notes:
RFC2866 does not make clear that an Access-Request packet MAY contain Acct-Multi-Session-Id in section 5.11 as it does for the Acct-Session-Id in section 5.5 or that consistency is expected between the start and stop records.