RFC 2069
E752386
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2069 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8672361 — 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 2069 Context triple: [RFC 2617, obsoletes, RFC 2069]
-
A.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
-
B.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
C.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
D.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
E.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
- 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 2069 Target entity description: RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
-
A.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
-
B.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
C.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
D.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
E.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| aimsTo | Provide stronger authentication than HTTP Basic authentication ⓘ |
| appliesTo |
HTTP client
ⓘ
HTTP server ⓘ |
| area | Applications ⓘ |
| authenticationScheme | Digest ⓘ |
| category | Standards Track ⓘ |
| comparedWith | HTTP Basic authentication ⓘ |
| definesMechanism | Digest access authentication for HTTP ⓘ |
| definesProtocol |
HTTP Digest Access Authentication
ⓘ
linked to:
RFC 2617
|
| definesTerm |
digest-uri
ⓘ
nonce (for HTTP authentication) ⓘ opaque (for HTTP authentication) ⓘ realm (for HTTP authentication) ⓘ |
| documentIdentifier | RFC 2069 ⓘ |
| documentType | Internet Standards Track specification ⓘ |
| field |
Computer networking
ⓘ
Internet security ⓘ |
| intendedUse | Web access authentication ⓘ |
| language | English ⓘ |
| objective | Improve security of HTTP access control ⓘ |
| obsoletedBy |
RFC 2617
ⓘ
RFC 7616 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | Internet Society ⓘ |
| relatedToProtocol |
HTTP/1.0
ⓘ
HTTP/1.1 ⓘ |
| replacesMechanism | Basic access authentication for HTTP (in some use cases) ⓘ |
| securityProperty |
Does not send passwords in clear text
ⓘ
Provides protection against replay attacks using nonces ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifiesHeader |
Authentication-Info
ⓘ
Authorization ⓘ WWW-Authenticate ⓘ |
| standardizes | Digest authentication scheme for HTTP ⓘ |
| status | Obsoleted ⓘ |
| successorConcept |
HTTP Digest Access Authentication as refined in RFC 2617
ⓘ
HTTP Digest Access Authentication as refined in RFC 7616 ⓘ
linked to:
RFC 2617
|
| title | An Extension to HTTP : Digest Access Authentication ⓘ |
| updatesSpecificationOf |
Hypertext Transfer Protocol
ⓘ
linked to:
HTTP
|
| uses |
Challenge-response authentication
ⓘ
MD5 hashing ⓘ Nonce values ⓘ |
| workingGroup | HTTP Working Group ⓘ |
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 2069 Description of subject: RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.