RFC 6186
E700356
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6186 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928170 — 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 6186 Context triple: [RFC 8314, obsoletes, RFC 6186]
-
A.
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.
-
B.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
C.
RFC 6860
RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
-
D.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
E.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
- 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 6186 Target entity description: RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
-
A.
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.
-
B.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
C.
RFC 6860
RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
-
D.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
E.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
- F. None of above. chosen
Statements (25)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard ⓘ |
| applicationDomain |
email
ⓘ
email access ⓘ email submission ⓘ |
| category | Standards Track ⓘ |
| defines |
use of DNS SRV records to locate email access services
ⓘ
use of DNS SRV records to locate email submission services ⓘ |
| focusesOn | service location for a given domain ⓘ |
| intendedFor |
email client implementers
ⓘ
email service providers ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 8314
ⓘ
RFC 8598 ⓘ |
| protocol |
DNS SRV
ⓘ
linked to:
DNS Service Discovery
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| specifies |
discovery of IMAP access services via SRV records
ⓘ
discovery of POP3 access services via SRV records ⓘ discovery of SMTP submission services via SRV records ⓘ |
| status | Obsoleted ⓘ |
| title | Use of SRV Records for Locating Email Submission/Access Services ⓘ |
| updatesPracticeFor | email client configuration ⓘ |
| uses | DNS ⓘ |
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 6186 Description of subject: RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.