Pseudowire Congestion Considerations

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 27
Abstract: Pseudowires (PWs) have become a common mechanism for tunneling traffic and may be found in unmanaged scenarios competing for network resources both with other PWs and with non-PW traffic, such as TCP/IP flows. Thus, it is worthwhile specifying under what conditions such competition is acceptable, i.e., the PW traffic does not significantly harm other traffic or contribute more than it should to congestion. We conclude that PWs transporting responsive traffic behave as desired without the need for additional mechanisms. For inelastic PWs (such as Time Division Multiplexing (TDM) PWs), we derive a bound under which such PWs consume no more network capacity than a TCP flow. For TDM PWs, we find that the level of congestion at which the PW can no longer deliver acceptable TDM service is never significantly greater, and is typically much lower, than this bound. Therefore, as long as the PW is shut down when it can no longer deliver acceptable TDM service, it will never do significantly more harm than even a single TCP flow. If the TDM service does not automatically shut down, a mechanism to block persistently unacceptable TDM pseudowires is required.
Publication Date: 2016-06-01
Status Note: Informational
DOI: 10.17487/RFC7893
Link: https://doi.org/10.17487/RFC7893
Author(s): Yaakov (J) Stein
David L. Black
Bob Briscoe
Keyword(s): Pseudowire, Congestion Control, TCP Friendliness

Latest version of IETF RFC 7893

Document Versions — IETF RFC 7893

▶ IETF RFC 7893 (2016-06-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IETF.draft-ietf-tsvwg-circuit-breaker-15 — CIRCUIT-BREAKER EXTERNAL
IETF.draft-stein-pwe3-tdm-packetloss-01 — PACKET-LOSS EXTERNAL
IETF RFC 2784 [Active*]
IETF RFC 2914 [Active*]
IETF RFC 3031 [Active*]
IETF RFC 3931 [Active*]
IETF RFC 3985 [Active*]
IETF RFC 4023 [Active*]
IETF RFC 4553 [Active*]
IETF RFC 5033 [Superseded*]
IETF RFC 5086 [Active*]
IETF RFC 5087 [Active*]
IETF RFC 5348 [Active*]
T-REC-G.703.2016 — G703 EXTERNAL
T-REC-G.775.1998 — G.775 EXTERNAL
T-REC-G.826.2002 — G826 EXTERNAL
T-REC-P.50.1998 — P50App1 EXTERNAL
T-REC-P.800.1998 — P800 EXTERNAL
T-REC-P.826.2001 — P862 EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC7893.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 7893, Pseudowire Congestion Considerations. Available at https://doi.org/10.17487/RFC7893

Snippet:

IETF RFC 7893, Pseudowire Congestion Considerations. Available at https://doi.org/10.17487/RFC7893

HTML (ISO 690 compliant)

Preview:

IETF RFC 7893, Pseudowire Congestion Considerations. Available at https://doi.org/10.17487/RFC7893

Snippet:

<span class="citation"><cite>IETF RFC 7893</cite>, Pseudowire Congestion Considerations. Available at <a href="https://doi.org/10.17487/RFC7893" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7893</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 7893, Pseudowire Congestion Considerations
doi: 10.17487/RFC7893
url: https://doi.org/10.17487/RFC7893

Snippet:

<li>
<cite id="bib-rfc7893">IETF RFC 7893</cite>, Pseudowire Congestion Considerations
<span class="doi">10.17487/RFC7893</span>
</li>

Referenced By

IETF RFC 8084 [Active*]
IETF RFC 9347 [Active*]