Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home
draft-ietf-dots-signal-call-home-02
Document Type Active Internet-Draft (dots WG)
Last updated 2019-05-31
Replaces draft-reddy-dots-home-network
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-dots-call-home@2019-04-25.yang
- Yang impact analysis for draft-ietf-dots-signal-call-home
- Mailing list discussion
Stream WG state WG Document
Document shepherd Valery Smyslov
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Valery Smyslov <valery@smyslov.net>
Email authors Email WG IPR 2 References Referenced by Nits 
DOTS                                                            T. Reddy
Internet-Draft                                                    McAfee
Intended status: Standards Track                            M. Boucadair
Expires: December 2, 2019                                         Orange
                                                              J. Shallow
                                                            May 31, 2019

   Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal
                           Channel Call Home
                  draft-ietf-dots-signal-call-home-02

Abstract

   This document specifies the DOTS signal channel Call Home service,
   which enables a DOTS server to initiate a secure connection to a DOTS
   client, and to receive the attack traffic information from the DOTS
   client.  The DOTS server in turn uses the attack traffic information
   to identify the compromised devices launching the outgoing DDoS
   attack and takes appropriate mitigation action(s).

   The DOTS Call Home service is not specific to the home networks; the
   solution targets any deployment which requires to block DDoS attack
   traffic closer to the source(s) of a DDoS attack.

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 December 2, 2019.

Copyright Notice

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

Reddy, et al.           Expires December 2, 2019                [Page 1]
Internet-Draft            DOTS Signal Call Home                 May 2019

   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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  The Problem . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  The Solution  . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Applicability Scope . . . . . . . . . . . . . . . . . . .   5
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  DOTS Signal Channel Call Home . . . . . . . . . . . . . . . .   7
     3.1.  Procedure . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Heartbeat Mechanism . . . . . . . . . . . . . . . . . . .   8
     3.3.  DOTS Signal Channel Extension . . . . . . . . . . . . . .   9
       3.3.1.  Mitigation Request  . . . . . . . . . . . . . . . . .   9
       3.3.2.  DOTS Signal Call Home YANG Module . . . . . . . . . .  14
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     4.1.  DOTS Signal Channel Call Home UDP and TCP Port Number . .  17
     4.2.  DOTS Signal Channel CBOR Mappings Registry  . . . . . . .  17
     4.3.  New DOTS Conflict Cause . . . . . . . . . . . . . . . . .  18
     4.4.  DOTS Signal Call Home YANG Module . . . . . . . . . . . .  18
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  19
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  20
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  21
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  21
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

1.1.  The Problem

   The DOTS signal channel protocol [I-D.ietf-dots-signal-channel] is
   used to carry information about a network resource or a network (or a
   part thereof) that is under a Distributed Denial of Service (DDoS)
   attack.  Such information is sent by a DOTS client to one or multiple
   DOTS servers so that appropriate mitigation actions are undertaken on
   traffic deemed suspicious.  Various use cases are discussed in
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools