IETF Logo Mail Archive

[Dots] Question: SignalChannel Mitigation using Mitigator with asynchronous

Takahiko Nagata <nagata@lepidum.co.jp> Sun, 10 February 2019 07:30 UTC

Return-Path: <nagata@lepidum.co.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 F1B4A128AFB for <dots@ietfa.amsl.com>; Sat, 9 Feb 2019 23:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lepidum-co-jp.20150623.gappssmtp.com
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 u8fjF2IEadJk for <dots@ietfa.amsl.com>; Sat, 9 Feb 2019 23:30:42 -0800 (PST)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40AE5130E11 for <dots@ietf.org>; Sat, 9 Feb 2019 23:30:42 -0800 (PST)
Received: by mail-pf1-x436.google.com with SMTP id h1so921018pfo.7 for <dots@ietf.org>; Sat, 09 Feb 2019 23:30:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lepidum-co-jp.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=rhwabr8/Feb11Fqrj4uezpd7GQH7jQMwHbM7Qh9GF3A=; b=1LAkHRdg//+meBX0JNjmT2w+nJ0YYfuHh1QomZ0pd49VzJN4qN9mapL8kew7O7Ph/C IERPxiYm2K54ril8t11AiuKx6jT07sRSlMPb+B4dX0FIr4mzQ/nB382HRR5iwpdXimMO p+iPCI4cl/h/mtCohXHf71ztQflWH1fwwvoomvLZubI51lv4ZAiOQv3BFGkPwWeYXhEx mKoKu6DlgZfMMRRLJ8eDlOOmTOrIRCsJJbYcoItga10rDslCUuBQEMb+XYmeLTbPF72X o/Z0TkyZh/VOir0ph1abPPh3z7HHAZfU5DE2U03sZpZ+6H+8iL+2UvOcMPHS/iCcrzUs 2caA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=rhwabr8/Feb11Fqrj4uezpd7GQH7jQMwHbM7Qh9GF3A=; b=uckc3qmhgQ3AQCWtt1zv7CzJChl0aIdasK1hEpwwmBw4XfqmF0ZnFPWt26WlNnDHFr CvH+KYhnkG9oPq7ILvMTafHpxH9parUsqzHX4mZ9byWb0HWQ2eamR2cuuQwHXOoqv0d3 sooFeZOFhlNZdGw5hirRxZ30hV/ZMejfwDPKavGieV6myvHFuwPyP/fwRd3NXksGZbDh LWOKbVmK/Qf7wJ7lPC1nGzi+OsZ0ycqtmSzpqQln/AinZDknndlwf9FajtsO2V9X+fgI BuKJt6uA1ce4s52rHkxX14m7bXOU7klDXAaCj19kSY7QMnaPBfnWK+SY0H1mRwSSQflJ VSKw==
X-Gm-Message-State: AHQUAuaJw/mUDNgKBmjLiiWio1wc7ABtpk7ZBfRoVih2/TLQjG/q7BsD hCbiMBHQM7N4cbVwEVV02y/mox85xBE=
X-Google-Smtp-Source: AHgI3IY3HlwNjpOsSTtMDvNhsrsSliQXJYgXKVhdACuexu0ueI7jbJf1ocz5AB7/nsuGH4yod0Zuyg==
X-Received: by 2002:a63:f91c:: with SMTP id h28mr4047978pgi.14.1549783841286; Sat, 09 Feb 2019 23:30:41 -0800 (PST)
Received: from [192.168.10.106] (softbank126225096048.bbtec.net. [126.225.96.48]) by smtp.gmail.com with ESMTPSA id f8sm8245496pga.24.2019.02.09.23.30.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Feb 2019 23:30:40 -0800 (PST)
To: dots@ietf.org
From: Takahiko Nagata <nagata@lepidum.co.jp>
Message-ID: <1842c1bf-96b2-8757-f8b1-8a8efd84a491@lepidum.co.jp>
Date: Sun, 10 Feb 2019 16:30:36 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/fa6Eb9XWd8whTsKVdQRzlesMz7c>
Subject: [Dots] Question: SignalChannel Mitigation using Mitigator with asynchronous
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: Sun, 10 Feb 2019 07:30:46 -0000

Hi all,

I confirmed latest(-28 version) SignalChannel and I have questions.
I would like to use Mitigator with asynchronous request/response.

In success case is OK:
1. DOTS Server recieve Mitigation request.
2. DOTS Server response with status=1
   (Attack mitigation setup is in progress)
3. Call Mitigator with asynchronous
4. If success mitigation, DOTS Server response(via observe)
   with status=2
   (2: Attack is being successfully mitigated)

But in failure case:
1. DOTS Server recieve Mitigation request.
2. DOTS Server response with status=1
   (Attack mitigation setup is in progress)
3. Call Mitigator with asynchronous
4. If failure mitigation, DOTS Server response(via observe)
   with status=7?
   (7: Attack mitigation is withdrawn (by the DOTS server))


(Question1) status=7(withdrawn) is correct in this case?
(Question2) How to notify reason of withdrawn to DOTS client?


Best Regards,
Takahiko Nagata

v2.39.1 | Report a Bug | By Email | System Status