RFC 6409
E702942
RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6409 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928171 — 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 6409 Context triple: [RFC 8314, obsoletes, RFC 6409]
-
A.
RFC 6096
RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
-
B.
RFC 6189
RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 6790
RFC 6790 is an IETF standard that specifies the use of entropy labels to improve load balancing and path diversity in MPLS networks.
-
E.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
- 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 6409 Target entity description: RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
-
A.
RFC 6096
RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
-
B.
RFC 6189
RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 6790
RFC 6790 is an IETF standard that specifies the use of entropy labels to improve load balancing and path diversity in MPLS networks.
-
E.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| associatedPort | TCP 587 ⓘ |
| category | Standards Track ⓘ |
| defines | Message Submission protocol NERFINISHED ⓘ |
| definesPort | 587 ⓘ |
| definesRole |
Mail User Agent
NERFINISHED
ⓘ
Message Submission Agent NERFINISHED ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn | separation of message submission from message relay ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 8314 NERFINISHED ⓘ |
| obsoletes | RFC 2476 NERFINISHED ⓘ |
| partOf | Internet Standards for email NERFINISHED ⓘ |
| portUsage | Message Submission ⓘ |
| protocolFamily | Simple Mail Transfer Protocol NERFINISHED ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| recommends | use of port 587 for message submission ⓘ |
| relatedTo |
SMTP
NERFINISHED
ⓘ
email ⓘ |
| RFCNumber | 6409 ⓘ |
| specifies |
requirements for mail submission agents
ⓘ
requirements for mail user agents during submission ⓘ |
| standardizes | procedures for message submission separate from message relay ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| supersededBy | RFC 8314 NERFINISHED ⓘ |
| title | Message Submission for Mail NERFINISHED ⓘ |
| updatesSpecificationOf | email message submission ⓘ |
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 6409 Description of subject: RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.