[Dots] draft-ietf-dots-signal-filter-control: Wei's comment about the behavior when 5.03 is received

<mohamed.boucadair@orange.com> Thu, 25 July 2019 07:42 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 AD1F61202F2 for <dots@ietfa.amsl.com>; Thu, 25 Jul 2019 00:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 vuHucdJ9fnmq for <dots@ietfa.amsl.com>; Thu, 25 Jul 2019 00:42:53 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 068B31202C6 for <dots@ietf.org>; Thu, 25 Jul 2019 00:42:53 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 45vPMH2HK5zBsCJ; Thu, 25 Jul 2019 09:42:51 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.70]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 45vPMH19hHzCqlH; Thu, 25 Jul 2019 09:42:51 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM33.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Thu, 25 Jul 2019 09:42:51 +0200
From: mohamed.boucadair@orange.com
To: Wei Pan <william.panwei@huawei.com>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: draft-ietf-dots-signal-filter-control: Wei's comment about the behavior when 5.03 is received
Thread-Index: AdVCvI7Mq4TGAis2SHeruWD46fP7NQ==
Date: Thu, 25 Jul 2019 07:42:50 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330312E84ED@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330312E84EDOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/kIeYgU6VNCxw8z_rE6vW-CDo4-w>
Subject: [Dots] draft-ietf-dots-signal-filter-control: Wei's comment about the behavior when 5.03 is received
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: Thu, 25 Jul 2019 07:42:55 -0000

Hi Wei, all,

You raised a comment during the meeting about the behavior when a 5.03 is received for a request including ACLs.

The spec says the following:


   If the DOTS client receives a 5.03 (Service Unavailable) with a

   ^^

   diagnostic payload indicating a failed ACL update as a response to an

   initial mitigation or a mitigation with adjusted scope, the DOTS

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   client MUST immediately send a new request which repeats all the

   parameters as sent in the failed mitigation request but without

   including the ACL attributes.

The slides are referring to this case.

Cheers,
Med