[Dots] WGLC Signal: Table 2 tidy up
"Jon Shallow" <supjps-ietf@jpshallow.com> Tue, 07 August 2018 14:03 UTC
Return-Path: <supjps-ietf@jpshallow.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 28A23130FF7 for <dots@ietfa.amsl.com>; Tue, 7 Aug 2018 07:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 UNb-n76z8ych for <dots@ietfa.amsl.com>; Tue, 7 Aug 2018 07:03:23 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91723130E8E for <dots@ietf.org>; Tue, 7 Aug 2018 07:03:23 -0700 (PDT)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.90_1) (envelope-from <jon.shallow@jpshallow.com>) id 1fn2a0-000186-SG for ietf-supjps-dots@ietf.org; Tue, 07 Aug 2018 15:03:21 +0100
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: dots@ietf.org
Date: Tue, 07 Aug 2018 15:03:21 +0100
Message-ID: <097401d42e57$664a6110$32df2330$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0975_01D42E5F.C80FB370"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdQuV2NrHnZjM+p6R46PFi+AZSkrAQ==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/LY22jAhWhtmXyXXocoYZ-4Lwjv0>
Subject: [Dots] WGLC Signal: Table 2 tidy up
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 07 Aug 2018 14:03:29 -0000
Hi There,
One of my implementers mis-read Table 2, so good to have some extra clarity
in the Table 2 text.
OLD:
1. Attack mitigation is in progress (e.g., changing the
NEW:
1. Attack mitigation setup is in progress (e.g., changing the
OLD
2 Attack is successfully mitigated (e.g., traffic is
NEW:
2 Attack is being successfully mitigated (e.g., traffic is
Regards
Jon
- [Dots] WGLC Signal: Table 2 tidy up Jon Shallow
- Re: [Dots] WGLC Signal: Table 2 tidy up mohamed.boucadair