RFC 1700
E745992
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1700 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8530334 — 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 1700 Context triple: [RFC 870, obsoletedBy, RFC 1700]
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
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.
-
C.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
D.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
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 1700 Target entity description: RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
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.
-
C.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
D.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
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 ⓘ |
| area | Internet NERFINISHED ⓘ |
| author |
Jon Postel
NERFINISHED
ⓘ
Joyce K. Reynolds NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
Assigned Numbers registry
NERFINISHED
ⓘ
Internet protocol parameter assignments NERFINISHED ⓘ |
| documents |
ARP hardware types
ⓘ
BOOTP vendor extensions ⓘ Ethernet numbers ⓘ ICMP type and code numbers ⓘ IP multicast addresses ⓘ IP option numbers ⓘ IP protocol numbers ⓘ Protocol and service names ⓘ SNMP enterprise numbers ⓘ TCP and UDP port numbers ⓘ TCP option numbers NERFINISHED ⓘ Telnet option codes ⓘ UDP option numbers ⓘ |
| format | Text ⓘ |
| intendedAudience |
Network implementers
ⓘ
Protocol designers ⓘ System administrators ⓘ |
| language | English ⓘ |
| length | ~200 pages ⓘ |
| maintainedBy |
IANA
NERFINISHED
ⓘ
Internet Assigned Numbers Authority NERFINISHED ⓘ |
| obsoletedBy |
IANA online registries
ⓘ
RFC 3232 NERFINISHED ⓘ |
| partOfSeries | RFC series NERFINISHED ⓘ |
| publicationDate | 1994-10 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Network Working Group NERFINISHED ⓘ |
| replacedBy | Online IANA protocol registries NERFINISHED ⓘ |
| RFCNumber | 1700 ⓘ |
| role |
Catalog of Internet protocol parameters
ⓘ
Central Assigned Numbers registry NERFINISHED ⓘ |
| scope | Internet-wide ⓘ |
| standardizes |
Dynamic and/or private port numbers
ⓘ
Registered port numbers ⓘ Well-known port numbers ⓘ |
| status | Historic ⓘ |
| supersedes | Earlier Assigned Numbers RFCs NERFINISHED ⓘ |
| title | Assigned Numbers 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 1700 Description of subject: RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.