Skip to main content

Port Mapping Between Unicast and Multicast RTP Sessions
draft-ietf-avt-ports-for-ucast-mcast-rtp-11

Document Type Replaced Internet-Draft (avtcore WG)
Expired & archived
Authors Ali C. Begen , Dan Wing , Tom VanCaenegem
Last updated 2011-02-04 (Latest revision 2011-01-05)
Replaces draft-begen-avt-ports-for-ucast-mcast-rtp
Replaced by draft-ietf-avtcore-ports-for-ucast-mcast-rtp
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-avtcore-ports-for-ucast-mcast-rtp
Consensus boilerplate Unknown
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:

Abstract

This document presents a port mapping solution that allows RTP receivers to choose their own ports for an auxiliary unicast session in RTP applications using both unicast and multicast services. The solution provides protection against denial-of-service or packet amplification attacks that could be used to cause one or more RTP packets to be sent to a victim client.

Authors

Ali C. Begen
Dan Wing
Tom VanCaenegem

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