RFC 6797
E849481
RFC 6797 is the Internet Engineering Task Force (IETF) document that defines the HTTP Strict Transport Security (HSTS) mechanism for enforcing secure HTTPS connections in web browsers.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6797 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10208188 — 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 6797 Context triple: [HTTP Strict Transport Security specification, standardizedIn, RFC 6797]
-
A.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
B.
RFC 7519
RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
-
C.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
D.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
E.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
- 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 6797 Target entity description: RFC 6797 is the Internet Engineering Task Force (IETF) document that defines the HTTP Strict Transport Security (HSTS) mechanism for enforcing secure HTTPS connections in web browsers.
-
A.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
B.
RFC 7519
RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
-
C.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
D.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
E.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard document
ⓘ
Request for Comments ⓘ |
| abbreviation | HSTS specification ⓘ |
| appliesTo |
HTTP
ⓘ
HTTPS ⓘ |
| area | Applications ⓘ |
| associatedProtocol |
TLS
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| category | Standards Track ⓘ |
| concerns | secure web browsing ⓘ |
| defines |
HTTP Strict Transport Security
ⓘ
linked to:
HTTP Strict Transport Security specification
|
| definesBehaviorFor |
servers advertising HSTS policies
ⓘ
user agents processing HSTS headers ⓘ |
| definesDirective |
includeSubDomains
ⓘ
max-age ⓘ preload (non-normative reference) ⓘ |
| definesHeaderFieldName | Strict-Transport-Security ⓘ |
| definesTerm |
HSTS Host
ⓘ
HSTS Policy ⓘ HSTS User Agent ⓘ |
| focusesOn |
transport layer security for HTTP
ⓘ
web security ⓘ |
| identifier | RFC 6797 ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 9110
ⓘ
RFC 9111 ⓘ RFC 9112 ⓘ RFC 9113 ⓘ RFC 9114 ⓘ |
| obsoletes | None ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relevantTo |
web browsers
ⓘ
web servers ⓘ |
| securityGoal |
ensure persistent use of HTTPS
ⓘ
protect users from man-in-the-middle attacks ⓘ |
| specifiesMechanism |
enforcing HTTPS connections in user agents
ⓘ
mitigating cookie hijacking over HTTP ⓘ preventing protocol downgrade attacks ⓘ |
| standardizes |
HTTP Strict Transport Security header field
ⓘ
Strict-Transport-Security header ⓘ
linked to:
HTTP Strict Transport Security specification
|
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title |
HTTP Strict Transport Security (HSTS)
ⓘ
linked to:
HTTP Strict Transport Security specification
|
| updatesSpecification | HTTP security model ⓘ |
| useCase | enforcing secure HTTPS connections in web browsers ⓘ |
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 6797 Description of subject: RFC 6797 is the Internet Engineering Task Force (IETF) document that defines the HTTP Strict Transport Security (HSTS) mechanism for enforcing secure HTTPS connections in web browsers.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.