Port Mapping Between Unicast and Multicast RTP Sessions
draft-begen-avt-ports-for-ucast-mcast-rtp-02
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ali C. Begen , Bill Ver Steeg | ||
Last updated | 2010-04-08 (Latest revision 2010-02-05) | ||
Replaced by | draft-ietf-avt-ports-for-ucast-mcast-rtp | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-avt-ports-for-ucast-mcast-rtp | |
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 the details of two port mapping solutions that allow RTP receivers to choose their own RTP and RTCP receive ports for the unicast session(s) in RTP applications using both unicast and multicast services.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)