RFC 7362: Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7362
- Published
- September 2014
- Authors
- E. Ivov; H. Kaplan; D. Wing
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 6716Definition of the Opus Audio CodecUpdated
September 2012
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8016Mobility with Traversal Using Relays around NAT (TURN)Current
November 2016
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 6405Voice over IP (VoIP) SIP Peering Use CasesCurrent
November 2011
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
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?