Re: [Dots] Adoption call for draft-reddy-dots-home-network-04

Daniel Migault <daniel.migault@ericsson.com> Fri, 26 April 2019 12:25 UTC

Return-Path: <mglt.ietf@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 061E8120091; Fri, 26 Apr 2019 05:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 4oAvZENfLDHV; Fri, 26 Apr 2019 05:25:32 -0700 (PDT)
Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) (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 5D3C4120045; Fri, 26 Apr 2019 05:25:31 -0700 (PDT)
Received: by mail-lj1-f178.google.com with SMTP id t10so1706614ljg.7; Fri, 26 Apr 2019 05:25:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aMlNtfzE6hB9AasH1i61gw50xxEsBx+8EH6iCBN00Ew=; b=o5IKPwbUVMuFbwgVV6H5ibsCUefbLCiB7ilXTwh2TbhI+vrSWjt9zJI1LK/UMX9Ptj FBVUaxMoJbAg1kTQBX77SDsHWyqvGkUe2FsQkY4H0u0lMS6RdbYhxDftURkUdsl4FeWz ET+EBKF5bM+gKNfJc2i5oH6TJonGiKwzL8kNlr9N+G/tDZHzOucoJybwWsLmgaMNdEfU QvQFjaYSNvW9zQUm/OccvKdLhjppNOfV7JM/lJknFalQbJu2pmHk8Vtsdh2jvoAH0Rvh VkjYgIx1Gupve9qg7s14NE1uFZJoEgzzbCAez16wYQpJ1x9qYL2BrmDlXNE+Af+Bn6x9 93OQ==
X-Gm-Message-State: APjAAAVKLtGxpW6yPxmgbkIf5MSlAJ3gjH20+IT5+2IF3SNK4WXl+xAK 6Y0IuhtPFu2cjtExR7oouf5OekVpXns/wNCcy5E=
X-Google-Smtp-Source: APXvYqzrbkEin48dd4CxPyrPosShqbAE8UyoEcKJG8FPI6oqZ0a7ItOrWdpaf1HqsgqZqAwDvZjp4KXooEAcdS5+6Hs=
X-Received: by 2002:a2e:9753:: with SMTP id f19mr26118691ljj.54.1556281529586; Fri, 26 Apr 2019 05:25:29 -0700 (PDT)
MIME-Version: 1.0
References: <023d01d4ee1f$c2bcb190$483614b0$@smyslov.net> <30E95A901DB42F44BA42D69DB20DFA6A69F3A581@nkgeml513-mbx.china.huawei.com> <CADZyTkmtyO25-JiHMicZDUL2F+5RXpnFPsYHmyn67yfHTns5fA@mail.gmail.com> <BYAPR16MB2790ECCDECA7EA5E62F76F0DEA260@BYAPR16MB2790.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302EA62879@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CADZyTkkCWV5Y8i=R6SEKpAwGCpZDMzFP_GaSa3LtvtPa2mYKaQ@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA66260@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA66260@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 26 Apr 2019 08:25:17 -0400
Message-ID: <CADZyTkkphbAiQuX330FZZxZQPzgEptuy5BQOAa-vtK6X5MrW9A@mail.gmail.com>
To: mohamed.boucadair@orange.com
Cc: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>, Valery Smyslov <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "kaduk@mit.edu" <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary="000000000000bdda4205876e07ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/emI7dSTEkiW-RkyZMRvOqTs3bCA>
Subject: Re: [Dots] Adoption call for draft-reddy-dots-home-network-04
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, 26 Apr 2019 12:25:35 -0000

Thanks for the response.
Yours,
Daniel

On Fri, Apr 26, 2019 at 2:16 AM <mohamed.boucadair@orange.com> wrote:

> Hi Daniel,
>
>
>
> Please see inline.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Daniel Migault [mailto:daniel.migault@ericsson.com]
> *Envoyé :* vendredi 26 avril 2019 03:01
> *À :* BOUCADAIR Mohamed TGI/OLN
> *Cc :* Konda, Tirumaleswar Reddy; dots-chairs@ietf.org; Valery Smyslov;
> dots@ietf.org; kaduk@mit.edu
> *Objet :* Re: [Dots] Adoption call for draft-reddy-dots-home-network-04
>
>
>
> Hi,
>
>
>
> Please find my comments inline. I believe my initial comment is
> addressed.  Igot confused between the DOTS and DTLS Client.
>
>
>
> Yours,
>
> Daniel
>
>
>
> On Thu, Apr 18, 2019 at 9:13 AM <mohamed.boucadair@orange.com> wrote:
>
> Hi Tiru, Daniel,
>
>
>
> With regards to:
>
>
>
> “ I believe that
>
> the same mechanism could be deployed between a DDoS target, its Cloud
>
> provider major ISPs up to the origin.”
>
>
>
> This is not currently doable with DOTS. Some key functional components are
> needed:
>
> (1) To identify the appropriate ISP which is hosting a DDoS source once a
> DDoS target has detected/reported an attack to its DOTS server/provider.
> The target may not be on the same network as the source.
>
> <mglt>I might be wrong, but it seems to me that when the IP address is not
> spoof, you can relatively easily go back to the ISP of that IP address. (at
> least). Am I missing something ?</mglt>
>
> [Med] That’s a good starting point (assuming workarounds for some issues
> such as: registries are not always up to date due to secondary market and
> so on.)
>
>
>
> (2) That ISP needs to expose a service to receive these notifications.
>
> <mglt>Theoretically, you would need an mesh of ISP DOTS communications
> (for DTLS). but I imagine we could start with ISP you peer with or have
> servers at the RIR level....</mglt>
>
> [Med] That’s an option. A solution is missing in that space, IMO. Such
> solution would also be used, for example, by IP reputation systems which
> currently add IP addresses to blacklists without even informing the ISPs.
> If that information is made available using some dynamic means, appropriate
> actions can be enforced by ISPs rather than assigning a “polluted” IP
> address to customers who will experience a bad quality because of
> restrictions induced by the reputation of the assigned IP address. We can
> discuss this offline as this is not specific to DOTS.
>
>
>
> Of course, if the ISP is capable of receiving these notifications, it can
> invoke the procedure in draft-reddy-dots-home-network.
>
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots
>