[Dots] About modification of draft-ietf-dots-use-cases-18

H Y <yuuhei.hayashi@gmail.com> Thu, 25 July 2019 19:28 UTC

Return-Path: <yuuhei.hayashi@gmail.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 D0BFC12019F; Thu, 25 Jul 2019 12:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.596
X-Spam-Level:
X-Spam-Status: No, score=-0.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aeN7Uf86GYFJ; Thu, 25 Jul 2019 12:28:33 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 6278F1201A0; Thu, 25 Jul 2019 12:28:32 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id y17so24537105ljk.10; Thu, 25 Jul 2019 12:28:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=+iMiH34aEEzOkawVe88Ppko9GIxIAl7omKQX2A7B6do=; b=T4AHBk6Q4qW+oo7KqtvD0KrqMmi4LnVR6bb3Q1KPrkfsYyxoFw5C6Yd/z0K31cVSbV alsxdPlJr40H9qscV9zffNNUJIpkYuYfwQ7OE47UgdLu1eTJn0BVw3In2RTgGTR5hb6z VSRm2ds6TlEYsbNhYf1ewV3OcOHvg0kS9xleIlIdaG/d7/l5fNbBjPuBYyi6VhwB8ph+ dBr0kFVM4aiTVqjmN4PZlIO9mXiRE/x8NVrUmUpNFUKUIal02cdSnKlBC0+c15HYuzEJ l7R+BUgqyfJ5eW4+9B/CFBK6O8Myw/6WyLvqFi4erpl1/MbtKHo61pxrZgyGAMIEx7Oc oVuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=+iMiH34aEEzOkawVe88Ppko9GIxIAl7omKQX2A7B6do=; b=FR7o4NztMjm8vLjK3CiAxJhO0Wog7QTdEodQotsUsJCx4QzBWQP2fjHKYS9y+tfESS AvRfQgaxKo8KrvQQn5mVaTL209Lm1WDoGyy7nWmImtVeIBbuKq0tGQFZROtin1x1F0CB EpigORNXK5Ny17ivLDilZmAt7bf5BbkfOMg7Vlufw5xi8nFrIueVZB6OUzqNM7RyaM2I sr3YKkhra7JbpOoyzIBgXX0IJ6KqIv9x7rlMXjAA0n57TA+BQ7N17uNAkkISCSzv/iZZ WCrJ6oe06r9ovG7BknqIn+ALpZkQYc3x1So1o79fzrwM2sqzSqz0vZo/5K3xJZKlTHOh LJfg==
X-Gm-Message-State: APjAAAVDhE2K6ZfTcPN9rCxNqqiRw9jjwC7MuJJ1mgp+JeIXaP5+xOk+ kaocSw4LllDp6gpeYWjq3I7QH7mCxfg8/XFXMm53D1elMjU=
X-Google-Smtp-Source: APXvYqwRFIUc3qEO2W2Hs9NrRCtG0v0odSMVVeFOq/LE5Goeq0INlhhiaOprl5OOMfB6wcjdyb86Ts04k9nLsCblK+w=
X-Received: by 2002:a2e:9dc1:: with SMTP id x1mr47377457ljj.0.1564082910124; Thu, 25 Jul 2019 12:28:30 -0700 (PDT)
MIME-Version: 1.0
From: H Y <yuuhei.hayashi@gmail.com>
Date: Thu, 25 Jul 2019 15:33:12 -0400
Message-ID: <CAA8pjUM-5QPQZNfFAwG_1rQ02-Hy7pDjyBn2fZ1RRank+UaHRw@mail.gmail.com>
To: "draft-ietf-dots-use-cases@ietf.org" <draft-ietf-dots-use-cases@ietf.org>
Cc: dots <dots@ietf.org>
Content-Type: multipart/mixed; boundary="00000000000042036a058e866ef4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/XJ0JSjDr-B45M1Wnhh9hBTPbA0I>
Subject: [Dots] About modification of draft-ietf-dots-use-cases-18
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 19:28:38 -0000

Hi  dots-use-cases draft authors,

At my presentation at last DOTS WG meeting, Ben said that if I modify
the use case WG draft in 1 week, it is in time for the review process.
In accordance with it, I modified the use case WG draft.

I just appended the below sentence to 3.3. DDoS Orchestration of
draft-ietf-dots-use-cases-18. The modification was reviewed by Kaname
Nishizuka.

   In addition to the above DDoS Orchestration, the selected DDoS
   mitigation systems can return back a mitigation request to the
   orchestrator as an offloading.  When the DDoS attack becomes severe
   and the DDoS mitigation system's utilization rate reaches its maximum
   capacity, the DDoS mitigation system can send mitigation requests
   with additional hints such as its blocked traffic information to the
   orchestrator.  Then the orchestrator can take further actions like
   requesting forwarding nodes such as routers to filter the traffic.
   In this case, the DDoS mitigation system implements a DOTS client
   while the orchestrator implements a DOTS server.

How is this?

Thanks,
Yuhei

-- 
----------------------------------
Yuuhei HAYASHI
08065300884
yuuhei.hayashi@gmail.com
iehuuy_0220@docomo.ne.jp
----------------------------------