RFC 3168
E64274
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 3168 canonical | 12 |
| A Specification for Explicit Congestion Notification (ECN) (RFC 3168) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T515890 — 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 3168 Context triple: [Transmission Control Protocol, updatedBy, RFC 3168]
-
A.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
B.
RFC 3418
RFC 3418 is an Internet standard that specifies the Management Information Base (MIB) for the Simple Network Management Protocol (SNMP), defining core managed objects used for network monitoring and control.
-
C.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
D.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
-
E.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- 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 3168 Target entity description: RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
A.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
B.
RFC 3418
RFC 3418 is an Internet standard that specifies the Management Information Base (MIB) for the Simple Network Management Protocol (SNMP), defining core managed objects used for network monitoring and control.
-
C.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
D.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
-
E.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- F. None of above. chosen
Statements (52)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| abbreviation | RFC 3168 ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ multicast traffic ⓘ unicast traffic ⓘ |
| area | Transport Area ⓘ |
| author |
D. Black
ⓘ
K. Ramakrishnan ⓘ S. Floyd ⓘ |
| BCPFor | deployment and use of ECN in IP networks ⓘ |
| category | Standards Track ⓘ |
| defines |
Explicit Congestion Notification
ⓘ
host behavior for reacting to ECN marks ⓘ negotiation of ECN capability during TCP connection setup ⓘ router behavior for setting ECN codepoints ⓘ |
| definesAbbreviation |
CWR
ⓘ
ECE ⓘ ECN ⓘ |
| definesField |
Congestion Window Reduced flag in the TCP header
ⓘ
ECN bits in the IP header ⓘ ECN field in the IP header ⓘ ECN-Echo flag in the TCP header ⓘ |
| definesMechanism |
end-to-end congestion notification without relying solely on packet loss
ⓘ
marking of packets instead of dropping to signal congestion ⓘ |
| extendsProtocol |
IP
ⓘ
Internet Protocol ⓘ TCP ⓘ
linked to:
Transmission Control Protocol
Transmission Control Protocol ⓘ |
| goal |
improve congestion control in the Internet
ⓘ
maintain end-to-end semantics of congestion control ⓘ reduce packet loss due to congestion ⓘ |
| month | September ⓘ |
| obsoletes | RFC 2481 ⓘ |
| publicationDate | September 2001 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedConcept |
Active Queue Management
ⓘ
RED ⓘ Random Early Detection ⓘ |
| RFCNumber | 3168 ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | The Addition of Explicit Congestion Notification (ECN) to IP ⓘ |
| updates |
RFC 1122
ⓘ
RFC 2003 ⓘ RFC 2018 ⓘ RFC 2401 ⓘ RFC 2474 ⓘ RFC 793 ⓘ |
| year | 2001 ⓘ |
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 3168 Description of subject: RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
Referenced by (13)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 3168