RFC 2156
E750290
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2156 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8650251 — 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 2156 Context triple: [RFC 1443, obsoletedBy, RFC 2156]
-
A.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
B.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
C.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
- 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 2156 Target entity description: 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.
-
A.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
B.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
C.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
- F. None of above. chosen
Statements (37)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Internet mail ⓘ |
| category | Standards Track ⓘ |
| defines |
MIXER protocol
ⓘ
linked to:
MIXER
address mapping rules between X.400 O/R addresses and RFC 822 addresses ⓘ error and notification mapping between X.400 and Internet mail ⓘ header field mapping between X.400 and RFC 822 headers ⓘ message body mapping between X.400 body parts and MIME entities ⓘ |
| focusesOn |
X.400 to Internet mail gatewaying
ⓘ
email interoperability ⓘ |
| goal |
interoperability between X.400 and Internet mail systems
ⓘ
preservation of message semantics across gateways ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc2156 ⓘ |
| intendedAudience |
email system implementers
ⓘ
gateway developers ⓘ |
| language | English ⓘ |
| networkScope |
Internet
ⓘ
linked to:
the internet
|
| number | 2156 ⓘ |
| obsoletes |
RFC 1327
ⓘ
RFC 1494 ⓘ |
| protocolDomain | application layer ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| relatedStandard |
MIME
ⓘ
RFC 822 ⓘ X.400 ⓘ |
| replaces | earlier guidance on X.400 and RFC 822 interoperability ⓘ |
| shortTitle | MIXER ⓘ |
| specifies |
mapping between X.400 and Internet mail addressing
ⓘ
mapping between X.400 and RFC 822/MIME message formats ⓘ procedures for X.400 and Internet mail gateway operation ⓘ |
| status | Proposed Standard ⓘ |
| title | MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME ⓘ |
| updatesSpecification | mapping between X.400 and RFC 822 mail systems ⓘ |
| uses | MIME ⓘ |
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 2156 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.