RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim

Summary

RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim is a Request for Comments^[1].

Key Facts

• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's instance of is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — instance of (P31): Request for Comments^[2].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's publisher is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — publisher (P123): Internet Engineering Task Force^[3].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's based on is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — based on (P144): RFC 2661: Layer Two Tunneling Protocol "L2TP"^[4].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's based on is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — based on (P144): RFC 2784: Generic Routing Encapsulation (GRE)^[5].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's based on is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — based on (P144): RFC 3931: Layer Two Tunneling Protocol - Version 3 (L2TPv3)^[6].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's based on is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — based on (P144): RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)^[7].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's based on is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — based on (P144): RFC 6040: Tunnelling of Explicit Congestion Notification^[8].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's based on is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — based on (P144): RFC 7450: Automatic Multicast Tunneling^[9].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's DOI is recorded as 10.17487/RFC9601^[10].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's language of work or name is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — language of work or name (P407): English^[11].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's publication date is recorded as +2024-08-01T00:00:00Z^[12].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's RfC ID is recorded as 9601^[13].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's work available at URL is recorded as https://tools.ietf.org/html/rfc9601^[14].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's title is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim^[15].
• RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's author name string is recorded as B. Briscoe^[16].

Body

Designation and Status

RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim's instance of is recorded as Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim — instance of (P31): Request for Comments^[2].