RFC 7778: Mobile Communication Congestion Exposure Scenario
In plain English — editorial summary, not part of the RFC
This memo describes a mobile communications use case for congestion exposure (ConEx) with a particular focus on those mobile communication networks that are architecturally similar to the 3GPP Evolved Packet System (EPS). This memo provides a brief overview of the architecture of these networks (both access and core networks) and current QoS mechanisms and then discusses how congestion exposure concepts could be applied. Based on this discussion, this memo suggests a set of requirements for ConEx mechanisms that particularly apply to these mobile networks.
Document record
- Document ID
- RFC7778
- Published
- March 2016
- Authors
- D. Kutscher; F. Mir; R. Winter; S. Krishnan; Y. Zhang; CJ. Bernardos
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7786TCP Modifications for Congestion Exposure (ConEx)Current
May 2016
- RFC 7806On Queuing, Marking, and DroppingCurrent
April 2016
- RFC 7837IPv6 Destination Option for Congestion Exposure (ConEx)Current
May 2016
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
- RFC 7846Peer-to-Peer Streaming Tracker Protocol (PPSTP)Current
May 2016
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 7928Characterization Guidelines for Active Queue Management (AQM)Current
July 2016
- RFC 7574Peer-to-Peer Streaming Peer Protocol (PPSPP)Current
July 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?