Specification of an Adaptation Function Between Two Multicast Networks Supporting Different IP Versions
draft-taylor-multrans-af2-specification-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tom Taylor , Cathy Zhou | ||
| Last updated | 2012-06-23 (Latest revision 2011-12-21) | ||
| 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
In some transitional multicast scenarios, the multicast signalling and content have to pass across network boundaries where one network supports IPv4, the other, IPv6. An adaptation function is required at the boundary to support such a scenario. This memo uses the term "Type 2 Adaptation Function" (AF2) for such a function.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)