RFC 1664
E254614
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1664 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777494 — 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 1664 Context triple: [RFC 1901, obsoletes, RFC 1664]
-
A.
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.
-
B.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
-
C.
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.
-
D.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
E.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
- 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 1664 Target entity description: RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
A.
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.
-
B.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
-
C.
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.
-
D.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
E.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
- F. None of above. chosen
Statements (31)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| aimsTo | support global mapping of email-style addresses ⓘ |
| area | Applications ⓘ |
| category | Experimental ⓘ |
| defines | mechanism for distributing MIXER-conformant global address mapping using DNS ⓘ |
| documentType | technical specification ⓘ |
| format |
PDF
ⓘ
PostScript ⓘ text ⓘ |
| language | English ⓘ |
| networkScope |
the internet
ⓘ
surface form:
Internet
|
| obsolete | true ⓘ |
| obsoletedBy | RFC 1901 ⓘ |
| protocolFamily |
the internet
ⓘ
surface form:
Internet
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
Domain Name System
ⓘ
surface form:
DNS
Domain Name System ⓘ MIXER ⓘ email address mapping ⓘ |
| RFCNumber | 1664 ⓘ |
| series | RFC series ⓘ |
| standardizationLevel | Experimental ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Obsoleted ⓘ |
| supersededByMechanism | mechanisms described in RFC 1901 ⓘ |
| title | Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM) ⓘ |
| topic |
email interoperability
ⓘ
messaging services ⓘ |
| uses | DNS resource records ⓘ |
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 1664 Description of subject: RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.