RFC 1071
E325860
RFC 1071 is an early Internet standard that specifies the algorithm for computing the standard Internet checksum used in IP, TCP, and UDP headers.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1071 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081745 — 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.
Target entity: RFC 1071 Context triple: [RFC 1122, obsoletes, RFC 1071]
-
A.
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.
-
B.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
C.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
-
D.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 1071 Target entity description: RFC 1071 is an early Internet standard that specifies the algorithm for computing the standard Internet checksum used in IP, TCP, and UDP headers.
-
A.
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.
-
B.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
C.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
-
D.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesToProtocol |
IP
ⓘ
Internet Protocol ⓘ Transmission Control Protocol ⓘ
surface form:
TCP
Transmission Control Protocol ⓘ UDP ⓘ UDP ⓘ
surface form:
User Datagram Protocol
|
| area |
the internet
ⓘ
surface form:
Internet
Transport ⓘ |
| category | Standards Track ⓘ |
| checksumType | 16-bit ones-complement sum ⓘ |
| definesOperationOn |
IP header
ⓘ
TCP header ⓘ UDP header ⓘ |
| definesPropertyOf |
IP checksum field
ⓘ
TCP checksum field ⓘ UDP checksum field ⓘ |
| describes | algorithm for computing standard Internet checksum ⓘ |
| documentType | technical specification ⓘ |
| focusesOn |
implementation issues of Internet checksum
ⓘ
performance considerations of Internet checksum ⓘ |
| language | English ⓘ |
| networkLayer |
Internet layer
ⓘ
Transport layer ⓘ |
| obsoletedBy |
RFC 1141
ⓘ
RFC 1624 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Internet Society ⓘ |
| relatedTo |
RFC 768
ⓘ
RFC 791 ⓘ RFC 793 ⓘ |
| RFCNumber | 1071 ⓘ |
| specifies | Internet checksum algorithm ⓘ |
| standardizes | Internet checksum computation ⓘ |
| status | Historic ⓘ |
| title | Computing the Internet Checksum ⓘ |
| topic |
error detection in Internet protocols
ⓘ
ones-complement arithmetic ⓘ |
| usedInContext |
end-to-end protocol checksums
ⓘ
packet header error detection ⓘ |
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.
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.
Subject: RFC 1071 Description of subject: RFC 1071 is an early Internet standard that specifies the algorithm for computing the standard Internet checksum used in IP, TCP, and UDP headers.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.