RFC 1663
E252133
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1663 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777493 — 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 1663 Context triple: [RFC 1901, obsoletes, RFC 1663]
-
A.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
B.
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.
-
C.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
D.
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.
-
E.
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.
- 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 1663 Target entity description: RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
A.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
B.
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.
-
C.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
asynchronous serial lines
ⓘ
point-to-point links ⓘ serial line communication ⓘ synchronous serial lines ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
Routing and transport ⓘ |
| category | Standards Track ⓘ |
| defines |
PPP Reliable Transmission
ⓘ
surface form:
PPP Reliable Transmission Control Protocol
PPP reliable link procedure ⓘ |
| definesExtensionFor |
PPP
ⓘ
Point-to-Point Protocol ⓘ |
| definesField |
acknowledgment number field in PPP frames
ⓘ
sequence number field in PPP frames ⓘ |
| definesMechanism |
acknowledgment of PPP frames
ⓘ
frame retransmission for PPP ⓘ reliable link-layer transmission for PPP ⓘ sequence numbering for PPP frames ⓘ sliding window protocol for PPP ⓘ |
| focusesOn |
error detection and recovery for PPP
ⓘ
reliable transmission over PPP ⓘ |
| goal | improve reliability of PPP over noisy serial lines ⓘ |
| intendedAudience |
implementers of PPP
ⓘ
network protocol designers ⓘ |
| language | English ⓘ |
| partOf | PPP family of specifications ⓘ |
| protocolType | data link layer protocol extension ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedIn |
RFCs
ⓘ
surface form:
RFC series
|
| relatedTo |
RFC 1661
ⓘ
RFC 1662 ⓘ |
| RFCNumber | 1663 ⓘ |
| specifies |
control fields for reliable PPP transmission
ⓘ
frame formats for reliable PPP transmission ⓘ negotiation options for reliable PPP ⓘ state machine for reliable PPP operation ⓘ |
| standardizes | reliable transmission option for PPP links ⓘ |
| status | Historic ⓘ |
| title | PPP Reliable Transmission ⓘ |
| updatesProtocol |
PPP
ⓘ
Point-to-Point Protocol ⓘ |
| uses |
negative acknowledgments
ⓘ
positive acknowledgments ⓘ retransmission timers ⓘ sequence numbers ⓘ |
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 1663 Description of subject: RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.