RFC 6750
E185472
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 6750 canonical | 3 |
| Mechanisms for using bearer tokens in HTTP requests | 1 |
| The OAuth 2.0 Authorization Framework: Bearer Token Usage | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1634860 — 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 6750 Context triple: [OAuth 2.0, standardizedIn, RFC 6750]
-
A.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
B.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
C.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
D.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
E.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
- 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 6750 Target entity description: RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
A.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
B.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
C.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
D.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
E.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard specification ⓘ |
| addresses |
Replay attack considerations
ⓘ
Token leakage risks ⓘ Token transport over TLS ⓘ |
| appliesTo |
HTTP
ⓘ
HTTPS ⓘ |
| area | Security ⓘ |
| assumes | Transport Layer Security for confidentiality ⓘ |
| authenticationScheme | Bearer ⓘ |
| category | Standards Track ⓘ |
| defines |
Bearer token type for OAuth 2.0
ⓘ
Mechanisms for using bearer tokens in HTTP requests ⓘ
linked to:
RFC 6750
OAuth 2.0 bearer token usage ⓘ Use of bearer tokens in HTTP Authorization header ⓘ Use of bearer tokens in HTTP request URI ⓘ Use of bearer tokens in HTTP request body ⓘ |
| definesHeaderField |
Authorization: Bearer
ⓘ
WWW-Authenticate: Bearer ⓘ |
| definesParameter |
access_token
ⓘ
error ⓘ error_description ⓘ error_uri ⓘ scope ⓘ |
| focusesOn |
Access token transport
ⓘ
HTTP request security ⓘ |
| format | Text ⓘ |
| intendedStatus | Proposed Standard ⓘ |
| language | English ⓘ |
| networkProtocolDomain | Application layer ⓘ |
| protocolFramework |
OAuth 2.0 Authorization Framework
ⓘ
linked to:
OAuth 2.0
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo | RFC 6749 ⓘ |
| RFCNumber | 6750 ⓘ |
| securityConsiderationsSection | Yes ⓘ |
| securityModel | Bearer token ⓘ |
| specifies |
Authorization request header field for bearer tokens
ⓘ
Error codes for bearer token authentication ⓘ Token scope indication in responses ⓘ WWW-Authenticate response header fields for bearer tokens ⓘ |
| standardsBody |
IETF OAuth Working Group
ⓘ
linked to:
OAuth Working Group
|
| status | Proposed Standard ⓘ |
| title |
The OAuth 2.0 Authorization Framework: Bearer Token Usage
ⓘ
linked to:
RFC 6750
|
| updates | OAuth 2.0 core specification usage details ⓘ |
| useCase |
API authorization
ⓘ
Web service access control ⓘ |
| usedIn | OAuth 2.0 protected resource access ⓘ |
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 6750 Description of subject: RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.