RFC 3366
E881410
RFC 3366 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines earlier PPP-related specifications to improve performance and behavior over diverse network environments.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3366 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10628727 — 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 3366 Context triple: [RFC 1661, obsoletedBy, RFC 3366]
-
A.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
B.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
C.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
D.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
E.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
- 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 3366 Target entity description: RFC 3366 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines earlier PPP-related specifications to improve performance and behavior over diverse network environments.
-
A.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
B.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
C.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
D.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
E.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
- F. None of above. chosen
Statements (29)
| Predicate | Object |
|---|---|
| instanceOf | RFC ⓘ |
| addresses |
behavior of PPP links under loss and delay
ⓘ
interaction between link-layer ARQ and transport protocols ⓘ performance over diverse network environments ⓘ |
| aimsTo |
avoid adverse interactions with TCP
ⓘ
improve end-to-end performance ⓘ optimize behavior over wireless and error-prone links ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
Transport ⓘ |
| category | Standards Track ⓘ |
| concerns |
PPP operation over various physical media
ⓘ
link-layer reliability mechanisms ⓘ |
| defines |
guidelines for ARQ parameter selection
ⓘ
guidelines for link-layer retransmission strategies ⓘ |
| focusesOn |
ARQ design for Internet links
ⓘ
link-layer Automatic Repeat reQuest mechanisms ⓘ |
| hasNumber | 3366 ⓘ |
| intendedAudience |
implementers of PPP and link-layer protocols
ⓘ
link designers ⓘ network protocol designers ⓘ |
| language | English ⓘ |
| partOfSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| standardizes | advice for link designers ⓘ |
| status | Proposed Standard ⓘ |
| title | Advice to Link Designers on Link Automatic Repeat reQuest (ARQ) ⓘ |
| updatesSpecificationType |
PPP-related specifications
ⓘ
Point-to-Point Protocol ⓘ |
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 3366 Description of subject: RFC 3366 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines earlier PPP-related specifications to improve performance and behavior over diverse network environments.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.