RFC 2195
E761753
RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2195 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8828708 — 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 2195 Context triple: [CRAM-MD5, definedIn, RFC 2195]
-
A.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
B.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
C.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
D.
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.
-
E.
RFC 2156
RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
- 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 2195 Target entity description: RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
-
A.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
B.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
C.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
D.
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.
-
E.
RFC 2156
RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
- F. None of above. chosen
Statements (34)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesToProtocol |
IMAP
ⓘ
POP3 ⓘ |
| area | Applications ⓘ |
| authenticationType | challenge-response ⓘ |
| author | John G. Myers ⓘ |
| category | Standards Track ⓘ |
| defines | Simple Challenge/Response authentication mechanism ⓘ |
| definesHeader | AUTH=CRAM-MD5 ⓘ |
| definesMechanismName | CRAM-MD5 ⓘ |
| definesSASLMechanism | CRAM-MD5 ⓘ |
| documentType | Standards-track RFC ⓘ |
| intendedFor | email retrieval protocols ⓘ |
| language | English ⓘ |
| monthPublished | September ⓘ |
| number | 2195 ⓘ |
| obsoletedBy | RFC 3501 ⓘ |
| organization | Internet Society ⓘ |
| provides | secure password-based login ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
SASL
ⓘ
Simple Authentication and Security Layer ⓘ
linked to:
SASL
|
| securityProperty | prevents cleartext password transmission ⓘ |
| specifies | CRAM-MD5 authentication mechanism ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | IMAP/POP AUTHorize Extension for Simple Challenge/Response ⓘ |
| updates |
IMAP4
ⓘ
linked to:
IMAP
POP3 ⓘ |
| usesAlgorithm |
HMAC-MD5
ⓘ
linked to:
HMAC
MD5 ⓘ |
| yearPublished | 1997 ⓘ |
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 2195 Description of subject: RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.