Optimal AMT Relay Discovery via DNS in Multi-Network SSM Multicast Environment
draft-nortz-optimal-amt-relay-discovery-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Doug Nortz , Robert Sayko , David Segelstein , Percy Tarapore | ||
| Last updated | 2016-05-05 (Latest revision 2015-11-02) | ||
| 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
One of the obstacles to implementing AMT Multicast in a multi- network environment is the difficulty an AMT Gateway may have in finding an AMT Relay that is optimal. Optimal in this context means that the AMT Relay has multicast connectivity to the Source, and its location minimizes the unicast (tunneled) portion of the path to the Gateway. Blind use of the global anycast address specified for AMT Relays in "Automatic IP Multicast Without Explicit Tunnels (AMT)" (RFC 7450) could result in reaching an AMT Relay that does not have multicast connectivity to the source, which would yield a failure to obtain the multicast content; or it could result in reaching an AMT Relay that is otherwise less than optimal. This document proposes a method for implementing standard DNS procedures so that an AMT Gateway using normal DNS queries can virtually always find the optimal AMT Relay for a given Source..
Authors
Doug Nortz
Robert Sayko
David Segelstein
Percy Tarapore
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)