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

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc7362.html

Published

2014-09-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust legal provisions; code components BSD; RFC text may be reproduced under IETF Trust terms; excerpts and locators used here

Source notes citing this source

• RFC 7362 (Informational) describes latching: a media relay takes the source address and port of the media packets it receives and uses them as the destination for media going the other way. in context
• RFC 7362 lists security risks in latching: an attacker can flood latching ports to exhaust resources, or send spoofed packets to a relay port to capture a session's media. It says SRTP helps mitigate these threats. in context
• RFC 7362 says latching is usually done once per peer and is not allowed to change until a new offer/answer exchange takes place. in context
• RFC 7362 says that for latching to work, a media relay must start receiving media before it starts sending. in context

Cite this source record

APA

WarmTransfer. (2014, September 1). Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-7362-latching

BibTeX

@misc{warmtransfer-rfc-7362-latching,
  title  = {Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication},
  author = {{WarmTransfer}},
  year   = {2014},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-7362-latching},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}