RFC 6040: Tunnelling of Explicit Congestion Notification

Summary

RFC 6040: Tunnelling of Explicit Congestion Notification is a Request for Comments^[1].

Key Facts

• RFC 6040: Tunnelling of Explicit Congestion Notification authored Tunnelling of Explicit Congestion Notification — author (P50): Bob Briscoe^[2].
• RFC 6040: Tunnelling of Explicit Congestion Notification's instance of is recorded as Tunnelling of Explicit Congestion Notification — instance of (P31): Request for Comments^[3].
• RFC 6040: Tunnelling of Explicit Congestion Notification's publisher is recorded as Tunnelling of Explicit Congestion Notification — publisher (P123): Internet Engineering Task Force^[4].
• RFC 6040: Tunnelling of Explicit Congestion Notification's based on is recorded as Tunnelling of Explicit Congestion Notification — based on (P144): RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP^[5].
• RFC 6040: Tunnelling of Explicit Congestion Notification's based on is recorded as Tunnelling of Explicit Congestion Notification — based on (P144): RFC 4301: Security Architecture for the Internet Protocol^[6].
• RFC 6040: Tunnelling of Explicit Congestion Notification's based on is recorded as Tunnelling of Explicit Congestion Notification — based on (P144): RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field^[7].
• RFC 6040: Tunnelling of Explicit Congestion Notification's DOI is recorded as 10.17487/RFC6040^[8].
• RFC 6040: Tunnelling of Explicit Congestion Notification's language of work or name is recorded as Tunnelling of Explicit Congestion Notification — language of work or name (P407): English^[9].
• RFC 6040: Tunnelling of Explicit Congestion Notification's publication date is recorded as +2010-11-01T00:00:00Z^[10].
• RFC 6040: Tunnelling of Explicit Congestion Notification's RfC ID is recorded as 6040^[11].
• RFC 6040: Tunnelling of Explicit Congestion Notification's work available at URL is recorded as https://tools.ietf.org/html/rfc6040^[12].
• RFC 6040: Tunnelling of Explicit Congestion Notification's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6040.txt^[13].
• RFC 6040: Tunnelling of Explicit Congestion Notification's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6040.txt^[14].
• RFC 6040: Tunnelling of Explicit Congestion Notification's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6040.txt.pdf^[15].
• RFC 6040: Tunnelling of Explicit Congestion Notification's number of pages is recorded as {'unit': '1', 'amount': '+35'}^[16].
• RFC 6040: Tunnelling of Explicit Congestion Notification's title is recorded as Tunnelling of Explicit Congestion Notification^[17].
• RFC 6040: Tunnelling of Explicit Congestion Notification's amended by is recorded as Tunnelling of Explicit Congestion Notification — amended by (P2567): RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim^[18].
• RFC 6040: Tunnelling of Explicit Congestion Notification's DBLP publication ID is recorded as journals/rfc/rfc6040^[19].

Body

Designation and Status

RFC 6040: Tunnelling of Explicit Congestion Notification's instance of is recorded as Tunnelling of Explicit Congestion Notification — instance of (P31): Request for Comments^[3].