RTP media failover: problem statement
draft-taylor-mmusic-rtp-failover-problem-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Taylor , Nic Larkin | ||
| Last updated | 2017-03-04 (Latest revision 2016-08-31) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Network-based functions that terminate large numbers of RTP media streams and that offer high availability, such as session border controllers or conference bridges, typically preserve the same IP address towards sources of RTP media across a failover event because it is impractical to signal a change of IP address towards large numbers of RTP sources sufficiently rapidly to keep media interruption intervals within acceptable limits. The need to preserve the IP address of RTP media terminating functions across a failover event imposes architectural requirements that can be difficult or costly to meet, particularly in network function virtualization environments. This document describes the problem, outlines the key requirements for a solution, and discusses the merits and shortcomings of various existing approaches to solving the problem, before arguing that a new solution is needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)