Skip to main content

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

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Emil Ivov , Hadriel Kaplan , Dan Wing
Last updated 2013-02-20 (Latest revision 2012-10-22)
Replaces draft-kaplan-mmusic-latching
Replaced by RFC 7362
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mmusic-latching
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document describes behavior of signalling intermediaries in 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 IETF community, as well as an informative description to manufacturers, and users.


Emil Ivov
Hadriel Kaplan
Dan Wing

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)