Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication
draft-ivov-mmusic-latching-03

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2013-02-20 (latest revision 2012-10-22)
Replaces draft-kaplan-mmusic-latching
Replaced by draft-ietf-mmusic-latching
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-mmusic-latching
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ivov-mmusic-latching-03.txt

Abstract

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.

Authors

Emil Ivov (emcho@jitsi.org)
Hadriel Kaplan (hkaplan@acmepacket.com)
Dan Wing (dwing@cisco.com)

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