Migrating SIP to IPv6 Media Without Connectivity Checks
draft-wing-dispatch-v6-migration-00
Document | Type |
Withdrawn by Submitter Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Dan Wing , Andrew Yourtchenko | ||
Last updated | 2010-10-13 (Latest revision 2010-08-27) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Withdrawn by Submitter | |
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
During the migration from IPv4 to IPv6, it is anticipated that an IPv6 path might be broken for a variety of reasons, causing endpoints to not receive RTP data. Connectivity checks would detect and avoid the user noticing such a problem, but there is industry reluctance to implement connectivity checks. This document describes a mechanism allowing dual-stack SIP endpoints to attempt communications over IPv6 and fall back to IPv4 if the IPv6 path is not working. The mechanism does not require connectivity checks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)