RFC 5849
E697198
RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5849 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7933958 — 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 5849 Context triple: [RFC 6749, obsoletes, RFC 5849]
-
A.
RFC 3489
RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
-
B.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
C.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 2570
RFC 2570 is an Internet standards document that updates and replaces earlier SNMP-related specifications, refining the framework for network management using the Simple Network Management Protocol.
- 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 5849 Target entity description: RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
-
A.
RFC 3489
RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
-
B.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
C.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 2570
RFC 2570 is an Internet standards document that updates and replaces earlier SNMP-related specifications, refining the framework for network management using the Simple Network Management Protocol.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
desktop applications
ⓘ
mobile applications ⓘ server-side applications ⓘ web applications ⓘ |
| area |
Applications
ⓘ
Security ⓘ |
| category | Standards Track ⓘ |
| defines |
OAuth 1.0
ⓘ
OAuth protocol parameters ⓘ access token ⓘ consumer key ⓘ consumer secret ⓘ nonce parameter ⓘ request token ⓘ signature base string ⓘ signature method parameter ⓘ three-legged OAuth flow ⓘ timestamp parameter ⓘ token secret ⓘ verifier code (oauth_verifier) ⓘ |
| focusesOn |
authorization delegation
ⓘ
secure delegated access ⓘ |
| goal |
avoid sharing user credentials with third-party clients
ⓘ
enable third-party applications to obtain limited access to HTTP resources ⓘ |
| intendedStatus | Proposed Standard ⓘ |
| obsoletes |
OAuth 1.0 (draft specification)
ⓘ
linked to:
OAuth 1.0
|
| protocolType |
authorization protocol
ⓘ
delegated authorization protocol ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo | OAuth 2.0 ⓘ |
| securityProperty |
protection against replay attacks
ⓘ
protection against request tampering ⓘ request signing ⓘ |
| specifies |
HTTP-based authorization protocol
ⓘ
error responses ⓘ protocol parameters ⓘ protocol roles ⓘ security considerations for OAuth 1.0 ⓘ |
| standardizes |
OAuth 1.0 core protocol
ⓘ
linked to:
OAuth 1.0
|
| supersededBy |
RFC 6749
ⓘ
The OAuth 2.0 Authorization Framework ⓘ
linked to:
RFC 6749
|
| title |
The OAuth 1.0 Protocol
ⓘ
linked to:
OAuth 1.0
|
| uses |
HMAC-SHA1
ⓘ
linked to:
HMAC
PLAINTEXT signature method ⓘ RSA-SHA1 ⓘ
linked to:
RSA
|
| usesTransport | HTTP ⓘ |
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 5849 Description of subject: RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.