RFC 1497
E700348
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1497 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7927966 — 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 1497 Context triple: [RFC 1533, obsoletes, RFC 1497]
-
A.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
B.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
-
C.
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.
-
D.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
E.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
- 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 1497 Target entity description: RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
A.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
B.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
-
C.
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.
-
D.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
E.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ |
| appliesToProtocol | IPv4 ⓘ |
| areaOfStandardization |
IP address configuration
ⓘ
Internet protocols ⓘ Network configuration ⓘ |
| category | Protocol specification ⓘ |
| defines |
BOOTP vendor information area format
NERFINISHED
ⓘ
BOOTP vendor magic cookie NERFINISHED ⓘ BOOTP vendor tag 10: Impress Server ⓘ BOOTP vendor tag 11: Resource Location Server ⓘ BOOTP vendor tag 12: Host Name ⓘ BOOTP vendor tag 13: Boot File Size ⓘ BOOTP vendor tag 14: Merit Dump File ⓘ BOOTP vendor tag 15: Domain Name ⓘ BOOTP vendor tag 16: Swap Server ⓘ BOOTP vendor tag 17: Root Path ⓘ BOOTP vendor tag 18: Extensions Path ⓘ BOOTP vendor tag 1: Subnet Mask ⓘ BOOTP vendor tag 255: End ⓘ BOOTP vendor tag 2: Time Offset ⓘ BOOTP vendor tag 3: Router ⓘ BOOTP vendor tag 4: Time Server ⓘ BOOTP vendor tag 5: Name Server ⓘ BOOTP vendor tag 6: Domain Name Server ⓘ BOOTP vendor tag 7: Log Server ⓘ BOOTP vendor tag 8: Cookie Server ⓘ BOOTP vendor tag 9: LPR Server ⓘ BOOTP vendor tag length-value encoding ⓘ BOOTP vendor tags ⓘ BOOTP vendor-specific extensions ⓘ |
| definesExtensionFor |
BOOTP
NERFINISHED
ⓘ
Bootstrap Protocol NERFINISHED ⓘ |
| influenced | Dynamic Host Configuration Protocol NERFINISHED ⓘ |
| language | English ⓘ |
| protocolLayer | Application layer ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| relatedSpecification |
RFC 1542
NERFINISHED
ⓘ
RFC 2131 NERFINISHED ⓘ RFC 951 NERFINISHED ⓘ |
| relatedTo | DHCP NERFINISHED ⓘ |
| RFCNumber | 1497 ⓘ |
| status | Informational ⓘ |
| title | BOOTP Vendor Information Extensions NERFINISHED ⓘ |
| usesMagicCookie | 99.130.83.99 ⓘ |
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 1497 Description of subject: RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.