RFC 1654
E235766
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1654 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777484 — 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 1654 Context triple: [RFC 1901, obsoletes, RFC 1654]
-
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 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
C.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
D.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 1654 Target entity description: RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
-
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 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
C.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
D.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
E.
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.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
PPP specification ⓘ Request for Comments ⓘ |
| appliesTo |
asynchronous links
ⓘ
serial point-to-point links ⓘ synchronous links ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
Routing ⓘ |
| category | Standards Track ⓘ |
| defines |
PPP control protocols
ⓘ
PPP encapsulation for network layer datagrams ⓘ PPP frame fields ⓘ PPP negotiation procedures ⓘ PPP state machine ⓘ |
| definesProtocol | Point-to-Point Protocol ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 1661 ⓘ |
| obsoletes | RFC 1548 ⓘ |
| protocolLayer |
OSI layer 2
ⓘ
data link layer ⓘ |
| protocolType | data link layer protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedIn |
RFCs
ⓘ
surface form:
RFC series
|
| RFCNumber | 1654 ⓘ |
| shortName | PPP ⓘ |
| specifies |
Link Control Protocol for PPP
ⓘ
PPP configuration options ⓘ PPP frame format ⓘ PPP link establishment ⓘ PPP link termination ⓘ PPP multiplexing of different network layer protocols ⓘ encapsulation of network layer datagrams over point-to-point links ⓘ framing for PPP ⓘ link control procedures for PPP ⓘ |
| standardizes | PPP operation over point-to-point links ⓘ |
| status | Obsoleted ⓘ |
| supports |
AppleTalk
ⓘ
IP ⓘ IPX ⓘ |
| title |
PPP over Ethernet
ⓘ
surface form:
The Point-to-Point Protocol (PPP)
|
| useCase |
dial-up connections
ⓘ
point-to-point leased lines ⓘ |
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 1654 Description of subject: RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.