API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Preference is stored in this browser only.

IETF RFC 6056
[ACTIVE]

Recommendations for Transport-Protocol Port Randomization

Metadata

Publisher
IETF
Doc Type
Best Practice
Pages
29
Abstract
During the last few years, awareness has been raised about a number of "blind" attacks that can be performed against the Transmission Control Protocol (TCP) and similar protocols. The consequences of these attacks range from throughput reduction to broken connections or data corruption. These attacks rely on the attacker's ability to guess or know the five-tuple (Protocol, Source Address, Destination Address, Source Port, Destination Port) that identifies the transport protocol instance to be attacked. This document describes a number of simple and efficient methods for the selection of the client port number, such that the possibility of an attacker guessing the exact value is reduced. While this is not a replacement for cryptographic methods for protecting the transport-protocol instance, the aforementioned port selection algorithms provide improved security with very little effort and without any key management overhead. The algorithms described in this document are local policies that may be incrementally deployed and that do not violate the specifications of any of the transport protocols that may benefit from them, such as TCP, UDP, UDP-lite, Stream Control Transmission Protocol (SCTP), Datagram Congestion Control Protocol (DCCP), and RTP (provided that the RTP application explicitly signals the RTP and RTCP port numbers). This memo documents an Internet Best Current Practice.
Publication Date
2011-01-01
Status Note
Best Current Practice
DOI
10.17487/RFC6056
Link
https://doi.org/10.17487/RFC6056
Author(s)
Michael Larsen
Fernando Gont
Keyword(s)
TCP, Blind Attacks
Latest version of IETF RFC 6056

Document Versions — IETF RFC 6056

  • ▶ IETF RFC 6056 (2011-01-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6056.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 6056, Recommendations for Transport-Protocol Port Randomization. Available at https://doi.org/10.17487/RFC6056
Snippet:
IETF RFC 6056, Recommendations for Transport-Protocol Port Randomization. Available at https://doi.org/10.17487/RFC6056

HTML (ISO 690 compliant)

Preview:
IETF RFC 6056, Recommendations for Transport-Protocol Port Randomization. Available at https://doi.org/10.17487/RFC6056
Snippet:
<span class="citation"><cite>IETF RFC 6056</cite>, Recommendations for Transport-Protocol Port Randomization. Available at <a href="https://doi.org/10.17487/RFC6056" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6056</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 6056, Recommendations for Transport-Protocol Port Randomization
doi: 10.17487/RFC6056
url: https://doi.org/10.17487/RFC6056
Snippet:
<li>
<cite id="bib-rfc6056">IETF RFC 6056</cite>, Recommendations for Transport-Protocol Port Randomization
<span class="doi">10.17487/RFC6056</span>
</li>

Referenced By