RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
0 sources
RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Summary
RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field is a Request for Comments[1].
Key Facts
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field authored Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — author (P50): Sally Floyd[2].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's instance of is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — instance of (P31): Request for Comments[3].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's publisher is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — publisher (P123): Internet Engineering Task Force[4].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's DOI is recorded as 10.17487/RFC4774[5].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's language of work or name is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — language of work or name (P407): English[6].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's publication date is recorded as +2006-11-01T00:00:00Z[7].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's RfC ID is recorded as 4774[8].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's main subject is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — main subject (P921): Explicit Congestion Notification[9].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's work available at URL is recorded as https://tools.ietf.org/html/rfc4774[10].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4774.txt[11].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4774.txt[12].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4774.txt.pdf[13].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's number of pages is recorded as {'unit': '1', 'amount': '+15'}[14].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's title is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field[15].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's amended by is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — amended by (P2567): RFC 6040: Tunnelling of Explicit Congestion Notification[16].
- RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's DBLP publication ID is recorded as journals/rfc/rfc4774[17].
Body
Designation and Status
RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field's instance of is recorded as Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field — instance of (P31): Request for Comments[3].