Re: [Dots] ietf104-hacthon-issue

"MeiLing Chen" <> Tue, 21 May 2019 02:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F26B712004E for <>; Mon, 20 May 2019 19:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id am7REK0_33Ia for <>; Mon, 20 May 2019 19:39:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CF4D2120026 for <>; Mon, 20 May 2019 19:39:14 -0700 (PDT)
Received: from (unknown[]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec5ce364cf51f-2a596; Tue, 21 May 2019 10:39:11 +0800 (CST)
X-RM-TRANSID: 2eec5ce364cf51f-2a596
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[]) by rmsmtp-syy-appsvr01-12001 (RichMail) with SMTP id 2ee15ce364cb829-f2c9c; Tue, 21 May 2019 10:39:08 +0800 (CST)
X-RM-TRANSID: 2ee15ce364cb829-f2c9c
Date: Tue, 21 May 2019 10:39:12 +0800
From: "MeiLing Chen" <>
To: kaname <>, william.panwei <>
Cc: dots <>
References: <>, <>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/related; boundary="----=_001_NextPart351013341003_=----"
Archived-At: <>
Subject: Re: [Dots] ietf104-hacthon-issue
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 21 May 2019 02:39:23 -0000

Hi kaname,panwei
[Meiling] Mitigation request with sampleMitigationRequestDraft.json use "trigger-mitigation"=true,  panwei think the mitigation request with trigger-mitigation set to false is a pre-configured mitigation request, it is sent before a DDoS attack happens. When DOTS server receives such mitigation request, it just saves this request and won’t trigger mitigation immediately.
Whether the process is correct or not?

> question1:what's the function of Deadman's Trigger?

So-called Deadman's Trigger is the function described in '3.3.3.  Automated Mitigation on Loss of Signal' of draft-ietf-dots-architecture and implemented as 'trigger-mitigation' in the signal channel.

   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.

> question2:Gateway Function、Redirection、Happy Eyeballs,Whether these three functions are not available in the go-dots?
Currently they are not supported by go-dots.


On 2019/05/17 10:59, MeiLing Chen wrote:
Hi kaname,
    I have two questions about this slide of PPT.
question1:what's the function of Deadman's Trigger?
question2:Gateway Function、Redirection、Happy Eyeballs,Whether these three functions are not available in the go-dots?

Dots mailing list