RFC 2487
E272700
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2487 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2512262 — 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 2487 Context triple: [RFC 3207, obsoletes, RFC 2487]
-
A.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
-
E.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and 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 2487 Target entity description: RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
A.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
-
E.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| abbreviation |
IETF
ⓘ
linked to:
Internet Engineering Task Force
SMTP ⓘ TLS ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
SMTP STARTTLS extension
ⓘ
linked to:
STARTTLS
STARTTLS ⓘ |
| definesCommand | STARTTLS ⓘ |
| definesMechanismFor | upgrading plaintext SMTP connection to TLS ⓘ |
| focusesOn | securing SMTP sessions ⓘ |
| keyword |
STARTTLS
ⓘ
email ⓘ encryption ⓘ security ⓘ |
| language | English ⓘ |
| networkLayer | application layer ⓘ |
| obsoletedBy | RFC 3207 ⓘ |
| obsoletes | none ⓘ |
| protocol |
Simple Mail Transfer Protocol
ⓘ
linked to:
SMTP
|
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo | RFC 3207 ⓘ |
| RFCNumber | 2487 ⓘ |
| specifies | use of TLS with SMTP ⓘ |
| standardizes | advertising TLS capability in SMTP via EHLO ⓘ |
| status | Proposed Standard ⓘ |
| title | SMTP Service Extension for Secure SMTP over TLS ⓘ |
| updatesProtocol | SMTP ⓘ |
| uses |
Transport Layer Security
ⓘ
linked to:
TLS
|
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 2487 Description of subject: RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.