...
2. Ammendments to the original document (section 4.) related to attributes used (to be edited)
4.Common F-ticks Attributes
In general a log consumer should not assume that any one attribute is present. Depending on the situation any one of these (or any other defined attributes) may be missing from an F-ticks message.
24.1. REALM
The REALM attribute is used to convey the AAA-realm (eg RADIUS) of the authentication event. The presence of the REALM attribute implies that the message was generated by a AAA-based identity provider.
24.2. VISCOUNTRY
The ISO country code of the entity that generated the log messages.
24.3. VISINST
TODO
24.4. CSI
The Calling Station ID of the subject associated with the authentication event. The presence of this attribute implies that the message was generated by an AAA-based identity provider.
24.5. RESULT
The success-state of the event - either 'OK' or 'FAIL'. For identity providers, this implies that a successful authentication request was returned to a relying party. For relying parties it means a successful authentication response was received from an identity provider.
24.6. RP
Relying Party identifier. A string uniquely identifying the relying party involved in the authentication event. This is typically a URI and will often be technology-dependent. Implementations should expect and be able to process any string.
24.7. AP
Asserting party identifier - often an identity provider. A string uniquely identifying the party making the claim towards the relying party. For an authentication event this is the identity provider. This is typically a URI and will often be technology-dependent. Implementations should expect and be able to process any string.
24.8. TS
A POSIX timestamp (aka unix time) associated with the authentication event. If this attribute is absent the consumer MAY choose to use a timestamp provided by the log message system (eg syslog) instead.
24.9. AM
Authentication Method identifier. This is normally a URI that identifies the type of authentication that was used. Values may be technology-dependent.
24.10. AL
Assurance Level Identifier. This is normally a URN that identifies the level of assurance (aka LoA) that was associated with the security association event. Level of assurance identifiers SHOULD be registered according to RFC6711 [RFC6711] and SHOULD NOT be technology-dependent. If registered identifiers are used, their short form may be used depending on the underlying technology used. Long-form (URI) and short-form level-of assurance identifiers are equivalent.
24.11. PN
A unique identifier for the subject involved in the event.
...