[Dots] draft-ietf-dots-signal-channel-33: trigger-mitigation

"MeiLing Chen" <chenmeiling@chinamobile.com> Wed, 15 May 2019 10:17 UTC

Return-Path: <chenmeiling@chinamobile.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1638C120043 for <dots@ietfa.amsl.com>; Wed, 15 May 2019 03:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level:
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZMS3-SkVGxw for <dots@ietfa.amsl.com>; Wed, 15 May 2019 03:17:17 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6D412002E for <dots@ietf.org>; Wed, 15 May 2019 03:17:15 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.17]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee25cdbe7282da-ba13c; Wed, 15 May 2019 18:17:12 +0800 (CST)
X-RM-TRANSID: 2ee25cdbe7282da-ba13c
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[10.2.51.72]) by rmsmtp-syy-appsvr09-12009 (RichMail) with SMTP id 2ee95cdbe727ed6-34155; Wed, 15 May 2019 18:17:12 +0800 (CST)
X-RM-TRANSID: 2ee95cdbe727ed6-34155
Date: Wed, 15 May 2019 18:17:13 +0800
From: MeiLing Chen <chenmeiling@chinamobile.com>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "mohamed.boucadair" <mohamed.boucadair@orange.com>
Cc: dots <dots@ietf.org>
References: <2019051517083625930510@chinamobile.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.115[cn]
Mime-Version: 1.0
Message-ID: <2019051518171308785722@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart415722571370_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/PTcnIvcmZTizLIWfwtTEjgn_OZQ>
Subject: [Dots] draft-ietf-dots-signal-channel-33: trigger-mitigation
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 10:17:22 -0000

Hi Tiru, Med;I read draft-ietf-dots-signal-channel-33, I have a question about the parameter of trigger-mitigation,

 trigger-mitigation:   If the parameter value is set to 'false', DDoS
      mitigation will not be triggered for the mitigation request unless
      the DOTS signal channel session is lost.
      If the DOTS client ceases to respond to heartbeat messages, the
      DOTS server can detect that the DOTS signal channel session is
      lost.  More details are discussed in Section 4.7.
Reddy, et al.           Expires November 11, 2019              [Page 18]
Internet-Draft        DOTS Signal Channel Protocol              May 2019
      The default value of the parameter is 'true' (that is, the
      mitigation starts immediately).  If 'trigger-mitigation' is not
      present in a request, this is equivalent to receiving a request
      with 'trigger-mitigation' set to 'true'.
question1: When send mitigation request first time, trigger-mitigation is set true; when session is lost, trigger-mitigation set false will work, so how to know session is lost?
question2: Why need this parameter and What was the initial requirements scenario?