DNS Reverse IP AMT Discovery
draft-ietf-mboned-driad-amt-discovery-09

The information below is for an old version of the document
Document Type Active Internet-Draft (mboned WG)
Author Jake Holland 
Last updated 2019-12-04 (latest revision 2019-10-27)
Replaces draft-jholland-mboned-driad-amt-discovery
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Doc Shepherd Follow-up Underway
Document shepherd Tim Chown
Shepherd write-up Show (last changed 2019-09-24)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Needs one more YES or NO OBJECTION position to pass.
Responsible AD Warren Kumari
Send notices to Tim Chown <tim.chown@jisc.ac.uk>
IANA IANA review state IANA OK - Actions Needed
Mboned                                                        J. Holland
Internet-Draft                                 Akamai Technologies, Inc.
Updates: 7450 (if approved)                             October 27, 2019
Intended status: Standards Track
Expires: April 29, 2020

                      DNS Reverse IP AMT Discovery
                draft-ietf-mboned-driad-amt-discovery-09

Abstract

   This document updates RFC 7450 (Automatic Multicast Tunneling, or
   AMT) by extending the relay discovery process to use a new DNS
   resource record named AMTRELAY when discovering 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.

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 April 29, 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Holland                  Expires April 29, 2020                 [Page 1]
Internet-Draft                    DRIAD                     October 2019

   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  . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
       1.2.1.  Relays and Gateways . . . . . . . . . . . . . . . . .   4
       1.2.2.  Definitions . . . . . . . . . . . . . . . . . . . . .   4
   2.  Relay Discovery Operation . . . . . . . . . . . . . . . . . .   5
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Signaling and Discovery . . . . . . . . . . . . . . . . .   6
     2.3.  Optimal Relay Selection . . . . . . . . . . . . . . . . .   8
       2.3.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .   8
       2.3.2.  Preference Ordering . . . . . . . . . . . . . . . . .  10
       2.3.3.  Connecting to Multiple Relays . . . . . . . . . . . .  12
     2.4.  Happy Eyeballs  . . . . . . . . . . . . . . . . . . . . .  12
       2.4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  12
       2.4.2.  Algorithm Guidelines  . . . . . . . . . . . . . . . .  13
       2.4.3.  Connection Definition . . . . . . . . . . . . . . . .  14
     2.5.  Guidelines for Restarting Discovery . . . . . . . . . . .  14
       2.5.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  14
       2.5.2.  Updates to Restarting Events  . . . . . . . . . . . .  15
       2.5.3.  Tunnel Stability  . . . . . . . . . . . . . . . . . .  16
       2.5.4.  Traffic Health  . . . . . . . . . . . . . . . . . . .  16
       2.5.5.  Relay Loaded or Shutting Down . . . . . . . . . . . .  18
       2.5.6.  Relay Discovery Messages vs. Restarting Discovery . .  18
       2.5.7.  Independent Discovery Per Traffic Source  . . . . . .  19
     2.6.  DNS Configuration . . . . . . . . . . . . . . . . . . . .  19
     2.7.  Waiting for DNS resolution  . . . . . . . . . . . . . . .  20
   3.  Example Deployments . . . . . . . . . . . . . . . . . . . . .  20
     3.1.  Example Receiving Networks  . . . . . . . . . . . . . . .  20
       3.1.1.  Tier 3 ISP  . . . . . . . . . . . . . . . . . . . . .  20
       3.1.2.  Small Office  . . . . . . . . . . . . . . . . . . . .  21
     3.2.  Example Sending Networks  . . . . . . . . . . . . . . . .  23
       3.2.1.  Sender-controlled Relays  . . . . . . . . . . . . . .  23
       3.2.2.  Provider-controlled Relays  . . . . . . . . . . . . .  24
   4.  AMTRELAY Resource Record Definition . . . . . . . . . . . . .  25
     4.1.  AMTRELAY RRType . . . . . . . . . . . . . . . . . . . . .  25
Show full document text