DNS Reverse IP AMT (Automatic Multicast Tunneling) Discovery
draft-ietf-mboned-driad-amt-discovery-13

Document Type Active Internet-Draft (mboned WG)
Last updated 2019-12-24 (latest revision 2019-12-20)
Replaces draft-jholland-mboned-driad-amt-discovery
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Chown
Shepherd write-up Show (last changed 2019-09-24)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Tim Chown <tim.chown@jisc.ac.uk>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Mboned                                                        J. Holland
Internet-Draft                                 Akamai Technologies, Inc.
Updates: 7450 (if approved)                            December 20, 2019
Intended status: Standards Track
Expires: June 22, 2020

      DNS Reverse IP AMT (Automatic Multicast Tunneling) Discovery
                draft-ietf-mboned-driad-amt-discovery-13

Abstract

   This document updates RFC 7450 (Automatic Multicast Tunneling, or
   AMT) by modifying the relay discovery process.  A new DNS resource
   record named AMTRELAY is defined for publishing AMT relays for
   source-specific multicast channels.  The reverse IP DNS zone for a
   multicast sender's IP address is configured to use AMTRELAY resource
   records to advertise a set of AMT relays that can receive and forward
   multicast traffic from that sender over an AMT tunnel.  Other
   extensions and clarifications to the relay discovery process are also
   defined.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 22, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Holland                   Expires June 22, 2020                 [Page 1]
Internet-Draft                    DRIAD                    December 2019

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
       1.2.1.  Relays and Gateways . . . . . . . . . . . . . . . . .   4
       1.2.2.  Definitions . . . . . . . . . . . . . . . . . . . . .   4
   2.  Relay Discovery Overview  . . . . . . . . . . . . . . . . . .   6
     2.1.  Basic Mechanics . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Signaling and Discovery . . . . . . . . . . . . . . . . .   6
     2.3.  Example Deployments . . . . . . . . . . . . . . . . . . .   9
       2.3.1.  Example Receiving Networks  . . . . . . . . . . . . .   9
       2.3.2.  Example Sending Networks  . . . . . . . . . . . . . .  12
   3.  Relay Discovery Operation . . . . . . . . . . . . . . . . . .  14
     3.1.  Optimal Relay Selection . . . . . . . . . . . . . . . . .  14
       3.1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  14
       3.1.2.  Preference Ordering . . . . . . . . . . . . . . . . .  15
       3.1.3.  Connecting to Multiple Relays . . . . . . . . . . . .  18
     3.2.  Happy Eyeballs  . . . . . . . . . . . . . . . . . . . . .  18
       3.2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  18
       3.2.2.  Algorithm Guidelines  . . . . . . . . . . . . . . . .  19
       3.2.3.  Connection Definition . . . . . . . . . . . . . . . .  20
     3.3.  Guidelines for Restarting Discovery . . . . . . . . . . .  20
       3.3.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  20
       3.3.2.  Updates to Restarting Events  . . . . . . . . . . . .  21
       3.3.3.  Tunnel Stability  . . . . . . . . . . . . . . . . . .  22
       3.3.4.  Traffic Health  . . . . . . . . . . . . . . . . . . .  22
       3.3.5.  Relay Loaded or Shutting Down . . . . . . . . . . . .  24
       3.3.6.  Relay Discovery Messages vs. Restarting Discovery . .  24
       3.3.7.  Independent Discovery Per Traffic Source  . . . . . .  25
     3.4.  DNS Configuration . . . . . . . . . . . . . . . . . . . .  25
     3.5.  Waiting for DNS resolution  . . . . . . . . . . . . . . .  26
   4.  AMTRELAY Resource Record Definition . . . . . . . . . . . . .  26
     4.1.  AMTRELAY RRType . . . . . . . . . . . . . . . . . . . . .  26
     4.2.  AMTRELAY RData Format . . . . . . . . . . . . . . . . . .  27
       4.2.1.  RData Format - Precedence . . . . . . . . . . . . . .  27
Show full document text