Re: [Dots] I-D Action: draft-ietf-dots-rfc8782-bis-00.txt

kaname nishizuka <kaname@nttv6.jp> Mon, 24 August 2020 07:27 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 9BDB93A0B46 for <dots@ietfa.amsl.com>; Mon, 24 Aug 2020 00:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.148
X-Spam-Level:
X-Spam-Status: No, score=-1.148 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.948, SPF_PASS=-0.001, 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 na6KzbSkt4_g for <dots@ietfa.amsl.com>; Mon, 24 Aug 2020 00:27:34 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.228.140]) by ietfa.amsl.com (Postfix) with ESMTP id C719D3A0B45 for <dots@ietf.org>; Mon, 24 Aug 2020 00:27:33 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [192.168.8.15]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 81E1F25F6BB; Mon, 24 Aug 2020 16:27:31 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820; t=1598254051; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wSuguoUEQeo8I1avRwjE892clCklb+Do9TVHai/ySbs=; b=p+xZFipKgaabLG9FGLZ/WAAjHX85OdYAXlKZEXrsoaEv9qazTHrZSEUa58WAf+drlk9f1J XSM5cGRW6fEEcRjelpwq8Cij0w+n21PIPIUnBVmg3ZbSSMhsKoghnaVF90wAkrDxg1/bZB q2v/WLBP11STgjp/BU3MsHY1oOT85m8=
Received: from UG023-kaname.local (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 4072175907D; Mon, 24 Aug 2020 16:27:30 +0900 (JST)
To: Valery Smyslov <valery@smyslov.net>, dots@ietf.org
References: <159774885713.10211.5341151302930796088@ietfa.amsl.com> <04af01d675f7$3cedd600$b6c98200$@smyslov.net>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <7239960d-0de3-801a-dd9f-e82b93580ae9@nttv6.jp>
Date: Mon, 24 Aug 2020 16:27:30 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <04af01d675f7$3cedd600$b6c98200$@smyslov.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/X4UR4fsZ1fG0mo2qYkeTTe-o_Zc>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-rfc8782-bis-00.txt
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: Mon, 24 Aug 2020 07:27:36 -0000

Hi Med, all.

`attack-status` is now under server-to-client-only in RFC8782 bis, but I just want to clarify whether it's correct.

In 4.4.3, it is said:
    The 'attack-status' parameter is a mandatory attribute when
    performing an efficacy update.  The various possible values contained
    in the 'attack-status' parameter are described in Table 4.
             +-----------+-------------------------------------+
             | Parameter | Description                         |
             |     Value |                                     |
             +===========+=====================================+
             |         1 | The DOTS client determines that it  |
             |           | is still under attack.              |
             +-----------+-------------------------------------+
             |         2 | The DOTS client determines that the |
             |           | attack is successfully mitigated    |
             |           | (e.g., attack traffic is not seen). |
             +-----------+-------------------------------------+

                 Table 4: Values of 'attack-status' Parameter


regards,
Kaname Nishizuka


On 2020/08/19 16:06, Valery Smyslov wrote:
> Hi,
>
> according to the roadmap we discussed for the replacement
> of RFC 8782, we are going to request yangdoctors
> and opsdir reviews for the just adopted draft to double check
> that all the changes in YANG module are fine with them.
> We are going to issue WGLC shortly after the reviews are complete.
>
> Regards,
> Frank & Valery.
>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.
>>
>>          Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
>>          Authors         : Mohamed Boucadair
>>                            Jon Shallow
>>                            Tirumaleswar Reddy.K
>> 	Filename        : draft-ietf-dots-rfc8782-bis-00.txt
>> 	Pages           : 119
>> 	Date            : 2020-08-18
>>
>> Abstract:
>>     This document specifies the Distributed Denial-of-Service Open Threat
>>     Signaling (DOTS) signal channel, a protocol for signaling the need
>>     for protection against Distributed Denial-of-Service (DDoS) attacks
>>     to a server capable of enabling network traffic mitigation on behalf
>>     of the requesting client.
>>
>>     A companion document defines the DOTS data channel, a separate
>>     reliable communication layer for DOTS management and configuration
>>     purposes.
>>
>>     This document obsoletes RFC 8782.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-dots-rfc8782-bis/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-dots-rfc8782-bis-00
>> https://datatracker.ietf.org/doc/html/draft-ietf-dots-rfc8782-bis-00
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>
>> _______________________________________________
>> Dots mailing list
>> Dots@ietf.org
>> https://www.ietf.org/mailman/listinfo/dots
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots