RFC 1661
E250392
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1661 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777491 — 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 1661 Context triple: [RFC 1901, obsoletes, RFC 1661]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- 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 1661 Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard specification
ⓘ
Request for Comments ⓘ |
| abbreviation | PPP ⓘ |
| appliesTo | point-to-point links ⓘ |
| area | Internet Area ⓘ |
| category | Network protocol specification ⓘ |
| defines |
Link Control Protocol for PPP
ⓘ
surface form:
PPP Link Control Protocol
PPP authentication phase framework ⓘ PPP code points ⓘ PPP configuration options ⓘ PPP encapsulation ⓘ PPP frame format ⓘ PPP maximum receive unit negotiation ⓘ PPP negotiation procedures ⓘ PPP protocol field values ⓘ PPP state machine ⓘ Point-to-Point Protocol ⓘ standard method for transporting multi-protocol datagrams over point-to-point links ⓘ |
| intendedUse |
the internet
ⓘ
surface form:
Internet
dial-up links ⓘ serial links ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 1331
ⓘ
RFC 2153 ⓘ RFC 2472 ⓘ RFC 2516 ⓘ RFC 2615 ⓘ RFC 2661 ⓘ RFC 3366 ⓘ RFC 5072 ⓘ RFC 5172 ⓘ |
| obsoletes | RFC 1548 ⓘ |
| protocolType | Data link layer protocol specification ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
Link Control Protocol for PPP
ⓘ
surface form:
PPP Network Control Protocols
PPP authentication protocols ⓘ PPP over ATM ⓘ PPP over Ethernet ⓘ PPP over SONET/SDH ⓘ |
| RFCNumber | 1661 ⓘ |
| shortTitle | PPP ⓘ |
| standardizes | PPP operation over point-to-point links ⓘ |
| status | Internet Standard ⓘ |
| stream | IETF Stream ⓘ |
| supports |
encapsulation of network layer datagrams
ⓘ
multiprotocol operation ⓘ |
| title |
Point-to-Point Protocol
ⓘ
surface form:
The Point-to-Point Protocol (PPP)
|
| workingGroup |
Point-to-Point Protocol
ⓘ
surface form:
Point-to-Point Protocol Extensions (pppext)
|
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 1661 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.