RFC 1327
E749672
RFC 1327 is an Internet standards document that specifies mechanisms for interworking between X.400 electronic mail and Internet (RFC 822/SMTP) email systems.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1327 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8650252 — 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 1327 Context triple: [RFC 1443, updates, RFC 1327]
-
A.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
B.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
-
C.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
D.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 1067
RFC 1067 is an early Internet standard that defined the first Management Information Base (MIB-I) for use with the Simple Network Management Protocol (SNMP).
- 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 1327 Target entity description: RFC 1327 is an Internet standards document that specifies mechanisms for interworking between X.400 electronic mail and Internet (RFC 822/SMTP) email systems.
-
A.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
B.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
-
C.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
D.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 1067
RFC 1067 is an early Internet standard that defined the first Management Information Base (MIB-I) for use with the Simple Network Management Protocol (SNMP).
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ email interoperability specification ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| concernsStandard |
ISO 10021
NERFINISHED
ⓘ
RFC 822 NERFINISHED ⓘ X.400(1988) ⓘ |
| defines |
gatewaying rules between X.400 and Internet mail
ⓘ
mapping of RFC 822 headers to X.400 message components ⓘ mapping of X.400 message components to RFC 822 headers ⓘ representation of RFC 822 addresses in X.400 ⓘ representation of X.400 addresses in RFC 822 ⓘ |
| definesMappingBetween |
RFC 822 electronic mail
ⓘ
SMTP-based Internet mail ⓘ X.400 electronic mail ⓘ |
| documentType | technical specification ⓘ |
| focusesOn | electronic mail interoperability ⓘ |
| hasApplicationProtocol |
RFC 822
NERFINISHED
ⓘ
X.400 message handling system ⓘ |
| hasTransportProtocol | SMTP NERFINISHED ⓘ |
| intendedUse | deployment of X.400/Internet mail gateways ⓘ |
| language | English ⓘ |
| networkScope | Internet NERFINISHED ⓘ |
| obsoletes |
RFC 1026
NERFINISHED
ⓘ
RFC 987 NERFINISHED ⓘ |
| protocolFamily |
Internet mail
ⓘ
X.400 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| relatedTo |
MIME
NERFINISHED
ⓘ
SMTP NERFINISHED ⓘ X.400 gateway ⓘ |
| RFCNumber | 1327 ⓘ |
| specifiesMechanismsFor |
address mapping between X.400 and RFC 822
ⓘ
error and notification mapping between X.400 and RFC 822 ⓘ interworking between X.400 and RFC 822/SMTP email systems ⓘ message body mapping between X.400 and RFC 822 ⓘ service elements mapping between X.400 and RFC 822 ⓘ |
| status | Proposed Standard ⓘ |
| title | Mapping between X.400(1988)/ISO 10021 and RFC 822 ⓘ |
| updatedBy |
RFC 1494
NERFINISHED
ⓘ
RFC 1495 NERFINISHED ⓘ RFC 1496 NERFINISHED ⓘ RFC 1648 NERFINISHED ⓘ RFC 2156 NERFINISHED ⓘ |
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 1327 Description of subject: RFC 1327 is an Internet standards document that specifies mechanisms for interworking between X.400 electronic mail and Internet (RFC 822/SMTP) email systems.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.