RFC 1602
E877062
RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1602 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10623784 — 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 1602 Context triple: [RFC 2026, obsoletes, RFC 1602]
-
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 1642
RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
-
C.
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.
-
D.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
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 1602 Target entity description: RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
-
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 1642
RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
-
C.
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.
-
D.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
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 (20)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards process document
ⓘ
Request for Comments ⓘ |
| appliesTo | Internet protocol standardization ⓘ |
| area | Internet standards ⓘ |
| category | Best Current Practice (historical context) ⓘ |
| defines |
procedures for developing Internet protocols
ⓘ
procedures for standardizing Internet protocols ⓘ |
| documentType | standards process specification ⓘ |
| governs | IETF standards track procedures (historical) ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 2026 ⓘ |
| partOf |
RFC series
ⓘ
linked to:
RFC Series Working Group
|
| publishedBy |
Internet Engineering Task Force
ⓘ
Internet Society ⓘ |
| publisher | RFC Editor ⓘ |
| relationship | earlier version of the Internet Standards Process description ⓘ |
| RFCNumber | 1602 ⓘ |
| status | obsolete ⓘ |
| supersededBy | RFC 2026 ⓘ |
| title |
The Internet Standards Process
ⓘ
linked to:
IETF Internet standards process
|
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 1602 Description of subject: RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.