RFC 903
E207717
RFC 903 is the Internet standard document that specifies the Reverse Address Resolution Protocol (RARP), which maps link-layer (hardware) addresses to IP addresses in early TCP/IP networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 903 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1866715 — 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 903 Context triple: [Reverse ARP, definedIn, RFC 903]
-
A.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
B.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- 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 903 Target entity description: RFC 903 is the Internet standard document that specifies the Reverse Address Resolution Protocol (RARP), which maps link-layer (hardware) addresses to IP addresses in early TCP/IP networks.
-
A.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
B.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ |
| abbreviation | RARP specification ⓘ |
| addressFamily | IPv4 ⓘ |
| assumes |
host does not know its IP address
ⓘ
host knows its hardware address ⓘ |
| category | Internet protocol standard ⓘ |
| definesMessageType |
RARP reply
ⓘ
RARP request ⓘ |
| definesProtocol |
Reverse ARP
ⓘ
surface form:
Reverse Address Resolution Protocol
|
| field |
TCP/IP
ⓘ
surface form:
Internet Protocol Suite
TCP/IP ⓘ computer networking ⓘ |
| hasNumber | 903 ⓘ |
| influenced | subsequent network boot protocols ⓘ |
| influencedBy | ARP design ⓘ |
| layer | network layer support protocol ⓘ |
| obsoletedBy |
BOOTP
ⓘ
DHCP ⓘ |
| operatesOver | broadcast-capable local networks ⓘ |
| partOf | Internet Standards history ⓘ |
| primaryFunction | map hardware addresses to IP addresses ⓘ |
| protocolAcronym |
Reverse ARP
ⓘ
surface form:
RARP
|
| protocolType | network bootstrapping protocol ⓘ |
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| relatedToProtocol |
ARP
ⓘ
ARP ⓘ
surface form:
Address Resolution Protocol
|
| relationshipToARP | reverse of ARP ⓘ |
| specifiesMappingFrom | link-layer address ⓘ |
| specifiesMappingTo | Internet Protocol address ⓘ |
| standardizes |
Reverse ARP
ⓘ
surface form:
Reverse Address Resolution Protocol
|
| status | historic ⓘ |
| title |
Reverse ARP
ⓘ
surface form:
Reverse Address Resolution Protocol
|
| useContext |
diskless workstations
ⓘ
early TCP/IP networks ⓘ hosts without local storage ⓘ |
| usesAddressType |
IP address
ⓘ
hardware address ⓘ |
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 903 Description of subject: RFC 903 is the Internet standard document that specifies the Reverse Address Resolution Protocol (RARP), which maps link-layer (hardware) addresses to IP addresses in early TCP/IP networks.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.