IETF Logo Mail Archive

Re: [Dots] ietf104-hacthon-issue

kaname nishizuka <kaname@nttv6.jp> Fri, 24 May 2019 09:05 UTC

Return-Path: <kaname@nttv6.jp>
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 EAA85120126 for <dots@ietfa.amsl.com>; Fri, 24 May 2019 02:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nttv6.jp
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 Eh75tYTsfFYV for <dots@ietfa.amsl.com>; Fri, 24 May 2019 02:04:58 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.228.140]) by ietfa.amsl.com (Postfix) with ESMTP id B9B4412009E for <dots@ietf.org>; Fri, 24 May 2019 02:04:57 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [IPv6:2402:c800:ff06:6::f]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 848A725F68C; Fri, 24 May 2019 18:04:56 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820; t=1558688696; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hUEwjpcXIkKYKPYgwjnq6icV/VzGI0ExRhH9sd84qgU=; b=A3rgEVbwKieblO85TKRHes9NCC+VNMxeGBmrcbGSeDfHqDz8V8E/HOfmYRZKXDeucwO6qn poT6zNVECgBE6oG5jA5QtiLA0XqlwgWlX001mOSzp3q5Xj9HYXDEG5baSx+NSxbv+tsD29 11iBk4iOdbUXWB+3I1AVUJS0WKNoiX0=
Received: from MacBook-Pro-17.local (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 4E01B75900F; Fri, 24 May 2019 18:04:56 +0900 (JST)
To: MeiLing Chen <chenmeiling@chinamobile.com>, "william.panwei" <william.panwei@huawei.com>
Cc: dots <dots@ietf.org>
References: <201905170959127925896@chinamobile.com> <a191d165-3d9d-1bdc-741f-f718f5d4277b@nttv6.jp> <201905171401262764501@chinamobile.com>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <f63639a5-429d-05e3-cca8-1bce18202075@nttv6.jp>
Date: Fri, 24 May 2019 18:04:55 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <201905171401262764501@chinamobile.com>
Content-Type: multipart/alternative; boundary="------------9C549F05A53B7DA802C06C64"
Content-Language: en-US
Authentication-Results: guri.nttv6.jp; spf=pass smtp.mailfrom=kaname@nttv6.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9z_9PEWkmIWaKiT8VPQPM29w6ZU>
Subject: Re: [Dots] ietf104-hacthon-issue
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: Fri, 24 May 2019 09:05:01 -0000

Hi MeiLing,

The process you described is correct.

regards,
Kaname



On 2019/05/21 11:39, MeiLing Chen wrote:
>
>     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.
>
>     regards,
>     Kaname
>
>     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
>>     Dots@ietf.org
>>     https://www.ietf.org/mailman/listinfo/dots
>

v2.23.0 | Report a Bug | By Email