A method for dots server deployment
draft-chen-dots-server-hierarchical-deployment-02

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
DOTS                                                      M. Chen
Internet-Draft                                                    Li. Su
Intended status: Informational                              China Mobile
Expires: September 10, 2020                                March 9, 2020

                  A method for dots server deployment
           draft-chen-dots-server-hierarchical-deployment-02

Abstract

   As DOTS is used for DDoS Mitigation signaling, in practice, there are
   different deployment scenarios for DOTS agents deployment depending
   on the network deployment mode.  This document made an recommandation
   for DOTS Server deployment, include ISP and enterprise deployment
   scenarios.  The goal is to provide some guidance for DOTS agents
   deployment.

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 September 10, 2020.

Copyright Notice

   Copyright (c) 2020 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
   include Simplified BSD License text as described in Section 4.e of

Chen & Su              Expires September 10, 2020               [Page 1]
Internet-Draft     dots server hierarchical deployment        March 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  DOTS server Considerations  . . . . . . . . . . . . . . . . .   3
   4.  DOTS server deployment inside an ISP  . . . . . . . . . . . .   4
     4.1.  DOTS Agents Deployment  . . . . . . . . . . . . . . . . .   4
     4.2.  DOTS Agents interfaces  . . . . . . . . . . . . . . . . .   6
       4.2.1.  Bandwidth consuming attack  . . . . . . . . . . . . .   7
       4.2.2.  Host resource consuming attack  . . . . . . . . . . .   7
   5.  DOTS server deployment between ISPs . . . . . . . . . . . . .   8
   6.  DOTS server deployment for Enterprise . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   DDoS Open Threat Signaling (DOTS) is a protocol to standardize real-
   time signaling, threat-handling
   requests[I-D.ietf-dots-signal-channel], when attack target is under
   attack, dots client send mitigation request to dots server for help,
   If the mitigation request contains enough messages of the attack,
   then the mitigator can respond very effectively.

   In the architecture draft[I-D.ietf-dots-architecture], when comes to
   the deployment topic, it says this does not necessarily imply that
   the attack target and the DOTS client have to be co-located in the
   same administrative domain, but it is expected to be a common
   scenario.  Although co-location of DOTS server and mitigator within
   the same domain is expected to be a common deployment model, it is
   assumed that operators may require alternative models.

   In the DOTS server discovery draft[I-D.ietf-dots-server-discovery],
   it is says that a key point in the deployment of DOTS is the ability
   of network operators to be able to configure DOTS clients with the
   correct DOTS server(s) information consistently.

   In the DOTS multihoming draft[I-D.ietf-dots-multihoming], it provides
   deployment recommendations for DOTS client and DOTS gateway, it is
   says when conveying a mitigation request to protect the attack

Chen & Su              Expires September 10, 2020               [Page 2]
Show full document text