Distributed-Denial-of-Service Open Threat Signaling (DOTS) Server Discovery
draft-boucadair-dots-server-discovery-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-06-30
Replaces draft-boucadair-dots-dhcp
Replaced by draft-ietf-dots-server-discovery
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       M. Boucadair
Internet-Draft                                                    Orange
Intended status: Standards Track                                T. Reddy
Expires: January 1, 2018                                          McAfee
                                                                P. Patil
                                                                   Cisco
                                                           June 30, 2017

   Distributed-Denial-of-Service Open Threat Signaling (DOTS) Server
                               Discovery
                draft-boucadair-dots-server-discovery-01

Abstract

   It may not be possible for a network to determine the cause for an
   attack, but instead just realize that some resources seem to be under
   attack.  To fill that gap, Distributed-Denial-of-Service Open Threat
   Signaling (DOTS) allows a network to inform a server that it is under
   a potential attack so that appropriate mitigation actions are
   undertaken.

   This document specifies mechanisms to configure nodes with DOTS
   servers.

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 http://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 January 1, 2018.

Copyright Notice

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

Boucadair, et al.        Expires January 1, 2018                [Page 1]
Internet-Draft            DOTS Server Discovery                June 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
   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
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Why Multiple Discovery Mechanisms?  . . . . . . . . . . . . .   4
   5.  How to Build the List of DOTS Servers?  . . . . . . . . . . .   7
   6.  DHCP Options for DOTS . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Design Rationale  . . . . . . . . . . . . . . . . . . . .   7
     6.2.  DHCPv6 DOTS Option  . . . . . . . . . . . . . . . . . . .   8
       6.2.1.  Format  . . . . . . . . . . . . . . . . . . . . . . .   8
       6.2.2.  DHCPv6 Client Behavior  . . . . . . . . . . . . . . .   9
     6.3.  DHCPv4 DOTS Option  . . . . . . . . . . . . . . . . . . .   9
       6.3.1.  Format  . . . . . . . . . . . . . . . . . . . . . . .   9
       6.3.2.  DHCPv4 Client Behavior  . . . . . . . . . . . . . . .   9
   7.  Discovery using Service Resolution  . . . . . . . . . . . . .  10
     7.1.  Retrieving Domain Name  . . . . . . . . . . . . . . . . .  10
       7.1.1.  DHCP  . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.2.  Resolution  . . . . . . . . . . . . . . . . . . . . . . .  11
   8.  DNS Service Discovery . . . . . . . . . . . . . . . . . . . .  14
     8.1.  DNS-SD  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.2.  mDNS  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   9.  Anycast . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  15
     10.1.  DHCP . . . . . . . . . . . . . . . . . . . . . . . . . .  16
     10.2.  Service Resolution . . . . . . . . . . . . . . . . . . .  16
     10.3.  DNS Service Discovery  . . . . . . . . . . . . . . . . .  16
     10.4.  Anycast  . . . . . . . . . . . . . . . . . . . . . . . .  16
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  DHCPv6 Option  . . . . . . . . . . . . . . . . . . . . .  16
     11.2.  DHCPv4 Option  . . . . . . . . . . . . . . . . . . . . .  17
     11.3.  Application Service & Application Protocol Tags  . . . .  17
       11.3.1.  DOTS Application Service Tag Registration  . . . . .  17
       11.3.2.  signal.udp Application Protocol Tag Registration . .  17
Show full document text