RFC 7362

Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication, September 2014

File formats:
icon for text file icon for PDF icon for HTML
Status:
INFORMATIONAL
Authors:
E. Ivov
H. Kaplan
D. Wing
Stream:
IETF
Source:
mmusic (rai)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7362

Discuss this RFC: Send questions or comments to the mailing list mmusic@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7362


Abstract

This document describes the behavior of signaling intermediaries in Real-Time Communication (RTC) deployments, sometimes referred to as Session Border Controllers (SBCs), when performing Hosted NAT Traversal (HNT). HNT is a set of mechanisms, such as media relaying and latching, that such intermediaries use to enable other RTC devices behind NATs to communicate with each other.

This document is non-normative and is only written to explain HNT in order to provide a reference to the Internet community and an informative description to manufacturers and users.

Latching, which is one of the HNT components, has a number of security issues covered here. Because of those, and unless all security considerations explained here are taken into account and solved, the IETF advises against use of the latching mechanism over the Internet and recommends other solutions, such as the Interactive Connectivity Establishment (ICE) protocol.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search