RFC 2481
E325863
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2481 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081781 — 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 2481 Context triple: [RFC 3168, obsoletes, RFC 2481]
-
A.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
B.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
C.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
-
D.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
E.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
- 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 2481 Target entity description: RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
A.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
B.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
C.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
-
D.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
E.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ networking specification ⓘ |
| abbreviation | ECN ⓘ |
| aimsTo | maintain throughput while reducing packet loss due to congestion ⓘ |
| area | Transport ⓘ |
| author |
David L. Black
ⓘ
K. Ramakrishnan ⓘ
surface form:
K. K. Ramakrishnan
Sally Floyd ⓘ |
| category | Experimental ⓘ |
| definesCodepoint |
Congestion Experienced (CE)
ⓘ
The Addition of Explicit Congestion Notification (ECN) to IP ⓘ
surface form:
ECN-Capable Transport (ECT)
|
| definesConcept |
The Addition of Explicit Congestion Notification (ECN) to IP
ⓘ
surface form:
Explicit Congestion Notification
|
| definesField |
Congestion Window Reduced (CWR) flag in the TCP header
ⓘ
ECN field in the IP header ⓘ ECN-Echo flag in the TCP header ⓘ |
| definesMechanism | signaling network congestion without packet loss ⓘ |
| documentType | Proposed experimental mechanism for ECN in IP and TCP ⓘ |
| extendsProtocol |
IP
ⓘ
Transmission Control Protocol ⓘ
surface form:
TCP
|
| focusesOn | congestion control in IP networks ⓘ |
| format | text ⓘ |
| intendedUse | experimental deployment of ECN in the Internet ⓘ |
| introduces |
ECN negotiation between TCP endpoints
ⓘ
use of ECN marks by routers to indicate incipient congestion ⓘ |
| language | English ⓘ |
| objective |
avoid packet loss as the primary congestion signal
ⓘ
improve congestion control behavior in IP networks ⓘ |
| obsoletedBy |
RFC 3168
ⓘ
surface form:
A Specification for Explicit Congestion Notification (ECN) (RFC 3168)
RFC 3168 ⓘ |
| organization |
IETF Areas
ⓘ
surface form:
IETF Transport Area
|
| proposes |
use of ECN bits in IP header to indicate congestion
ⓘ
use of ECN-Echo and CWR flags in TCP to react to congestion ⓘ |
| publicationMonth | January ⓘ |
| publicationYear | 1999 ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
Active Queue Management
ⓘ
Internet Protocol type of service field ⓘ
surface form:
Differentiated Services
Random Early Detection ⓘ |
| RFCNumber | 2481 ⓘ |
| series |
RFCs
ⓘ
surface form:
RFC
|
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
The Addition of Explicit Congestion Notification (ECN) to IP
ⓘ
surface form:
A Proposal to add Explicit Congestion Notification (ECN) to IP
|
| updatesProtocolBehaviorOf |
IP congestion indication
ⓘ
TCP congestion control ⓘ |
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 2481 Description of subject: RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.