IETF Logo Mail Archive

Re: [Dots] Comments on dots-signal-control-filtering-01

<mohamed.boucadair@orange.com> Fri, 18 January 2019 07:07 UTC

Return-Path: <mohamed.boucadair@orange.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 80E02131136 for <dots@ietfa.amsl.com>; Thu, 17 Jan 2019 23:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] 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 TjuIcBzqJu6M for <dots@ietfa.amsl.com>; Thu, 17 Jan 2019 23:07:18 -0800 (PST)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1D00130D7A for <dots@ietf.org>; Thu, 17 Jan 2019 23:07:17 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 43gsT00fr6z10pn; Fri, 18 Jan 2019 08:07:16 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 43gsSz6tphzDq78; Fri, 18 Jan 2019 08:07:15 +0100 (CET)
Received: from OPEXCAUBM7E.corporate.adroot.infra.ftgroup (10.114.13.76) by OPEXCLILM32.corporate.adroot.infra.ftgroup (10.114.31.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 18 Jan 2019 08:07:15 +0100
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM7E.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0415.000; Fri, 18 Jan 2019 08:07:15 +0100
From: mohamed.boucadair@orange.com
To: Takahiko Nagata <nagata@lepidum.co.jp>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] Comments on dots-signal-control-filtering-01
Thread-Index: AQHUrjQnkWiStgbyYE2xxNF5buShSqW0llQw
Date: Fri, 18 Jan 2019 07:07:14 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA09E84@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <e508fc49-fe2f-8160-8f0b-cba1868be738@lepidum.co.jp>
In-Reply-To: <e508fc49-fe2f-8160-8f0b-cba1868be738@lepidum.co.jp>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/6IzoCMZUhDulhRIvfGYDnYv9PHY>
Subject: Re: [Dots] Comments on dots-signal-control-filtering-01
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, 18 Jan 2019 07:07:19 -0000

Hi Takahiko, 

Thank you for sharing the comments. 

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Takahiko Nagata
> Envoyé : jeudi 17 janvier 2019 08:13
> À : dots@ietf.org
> Objet : [Dots] Comments on dots-signal-control-filtering-01
> 
> Hi Kaname,
> 
> I would like to 2 comments on dots-signal-control-filtering-01.
> 
> (Comment1) Minimal attributes for control-filtering. ("lifetime" behavior)
>   Minimal attributes of SignalChannel MitigationRequest
>   for control-filtering is only the followings, I think.
>   - acl-list(acl-name, activation-type)
>   - lifetime
> 
>   So, We can send acl-list via SignalChannel without
>   other Mitigation request parameters.

[Med] When the same mid is used, the request is considered as a refresh. As such the attributes that were included in the first request must be included.  

> 
>   In this case, we need to decide behavior of "lifetime".
>   I think "lifetime" is ignored in this case.

[Med] No. This is a particular case of this text from the signal channel spec:

   For a mitigation request to continue beyond the initial negotiated
   lifetime, the DOTS client has to refresh the current mitigation
   request by sending a new PUT request.  This PUT request MUST use the
   same 'mid' value, and MUST repeat all the other parameters as sent in
   the original mitigation request apart from a possible change to the
   lifetime parameter value.

>   Because acl-list(acl-name, activation-type) should be
>   managed only DataChannel side for specification simply.
> 
> 
> (Comment2) Should be specified behavior.
> (a) Not be affected by "trigger-mitigation"
>   acl-list(acl-name, activation-type) is soon be applied
>   even if "trigger-mitigation" is false.

[Med] The procedure applies independently of the value of "trigger-mitigation". We can say this explicitly on the draft.

> 
> (b) Do not affect to "Efficacy Update"
>   acl-list(acl-name, activation-type) would be ignored
>   at "Efficacy Update" success or reject.

[Med] Agree. We are not updating that part of the signal channel spec. acl-list clauses won't be included in the efficacy update. 

> 
> (c) GET response of Mitigation Request
>   acl-list(acl-name, activation-type) would not be included
>   on respose of GET Mitigation Request.

[Med] Yes. Will be make this clear in the draft.

> 
> (d) In DELETE, no behavior(ex: rollback) for acl-list.

[Med] Yes. 

> 
> 
> Best Regards,
> Takahiko Nagata
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

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