RFC 2866
E514833
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2866 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5347050 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2866 Context triple: [RADIUS, accountingDefinedInRFC, RFC 2866]
-
A.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
B.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
C.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
D.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2866 Target entity description: RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
A.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
B.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
C.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
D.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
RADIUS clients
ⓘ
RADIUS servers ⓘ network access servers ⓘ |
| area | Operations and Management ⓘ |
| category | Network access accounting ⓘ |
| defines |
Acct-Authentic attribute
ⓘ
Acct-Delay-Time attribute NERFINISHED ⓘ Acct-Input-Octets attribute ⓘ Acct-Input-Packets attribute NERFINISHED ⓘ Acct-Link-Count attribute ⓘ Acct-Multi-Session-Id attribute ⓘ Acct-Output-Octets attribute ⓘ Acct-Output-Packets attribute ⓘ Acct-Session-Id attribute ⓘ Acct-Session-Time attribute NERFINISHED ⓘ Acct-Status-Type attribute ⓘ Acct-Terminate-Cause attribute ⓘ RADIUS Accounting-Request messages NERFINISHED ⓘ RADIUS Accounting-Response messages NERFINISHED ⓘ RADIUS accounting attributes ⓘ RADIUS accounting extensions NERFINISHED ⓘ accounting record format for RADIUS ⓘ error handling for accounting messages ⓘ interim accounting records ⓘ start and stop accounting records ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn | dial-in user services accounting ⓘ |
| intendedUse | Internet-wide accounting for network access ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 2869
NERFINISHED
ⓘ
RFC 5080 NERFINISHED ⓘ |
| protocolFamily | RADIUS NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RADIUS authentication
ⓘ
RFC 2865 ⓘ |
| specifiesProtocolExtensionFor |
RADIUS
NERFINISHED
ⓘ
Remote Authentication Dial-In User Service NERFINISHED ⓘ |
| standardsTrack | Proposed Standard ⓘ |
| status | Obsoleted ⓘ |
| title | RADIUS Accounting NERFINISHED ⓘ |
| updatesSpecificationOf | RADIUS NERFINISHED ⓘ |
| usedFor |
network access usage tracking
ⓘ
resource usage reporting ⓘ user session accounting ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 2866 Description of subject: RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.