Re: [Dots] Mirja Kühlewind's Discuss on draft-ietf-dots-requirements-18: (with DISCUSS and COMMENT)

<mohamed.boucadair@orange.com> Thu, 21 February 2019 12:25 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 6B0F5130F9F; Thu, 21 Feb 2019 04:25:03 -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 feyJwP2vUrVu; Thu, 21 Feb 2019 04:25:01 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C200130FA5; Thu, 21 Feb 2019 04:25:01 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 444tvv5m2Dz5w49; Thu, 21 Feb 2019 13:24:59 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 444tvv4zTdz1xnt; Thu, 21 Feb 2019 13:24:59 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA4.corporate.adroot.infra.ftgroup ([fe80::4538:d7b0:3c64:8ed3%22]) with mapi id 14.03.0435.000; Thu, 21 Feb 2019 13:24:59 +0100
From: mohamed.boucadair@orange.com
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, "Teague, Nik" <nteague@Verisign.com>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "frank.xialiang@huawei.com" <frank.xialiang@huawei.com>, "dots@ietf.org" <dots@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-dots-requirements@ietf.org" <draft-ietf-dots-requirements@ietf.org>
Thread-Topic: Re: [Dots] Mirja Kühlewind's Discuss on draft-ietf-dots-requirements-18: (with DISCUSS and COMMENT)
Thread-Index: AQHUydpqmjkDk7Q0KUymxuFXxQ11XqXqKy0A
Date: Thu, 21 Feb 2019 12:24:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA232C1@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155068522853.31498.10686203344983870104.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA23122@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <66BB8E3D-DEB6-43AC-AAEB-B6EB1A248865@kuehlewind.net> <5CE85A1F-16DC-485C-BA5F-278E0E8CFF3C@Verisign.com> <3089053C-CF9B-491A-ACB0-0BC053C50E88@kuehlewind.net>
In-Reply-To: <3089053C-CF9B-491A-ACB0-0BC053C50E88@kuehlewind.net>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/PNC_QOCl0tgnC55J6hsU5fQmHq4>
Subject: Re: [Dots] Mirja Kühlewind's Discuss on draft-ietf-dots-requirements-18: (with DISCUSS and COMMENT)
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, 21 Feb 2019 12:25:04 -0000

Re-,

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Mirja Kuehlewind (IETF) [mailto:ietf@kuehlewind.net]
> Envoyé : jeudi 21 février 2019 12:42
> À : Teague, Nik
> Cc : BOUCADAIR Mohamed TGI/OLN; dots-chairs@ietf.org;
> frank.xialiang@huawei.com; dots@ietf.org; The IESG; draft-ietf-dots-
> requirements@ietf.org
> Objet : Re: Re: [Dots] Mirja Kühlewind's Discuss on draft-ietf-dots-
> requirements-18: (with DISCUSS and COMMENT)
> 
> Hi,
> 
> please see below.
> 
> > Am 21.02.2019 um 12:18 schrieb Teague, Nik <nteague@Verisign.com>:
> >
> > Hi,
> >
> >
> > On 21 Feb 2019, at 10:58, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net>
> wrote:
> >
> >>>> 3) In SIG-006 you say:
> >>>> "      Due to the higher likelihood of packet loss during a DDoS attack,
> >>>>    DOTS servers MUST regularly send mitigation status to authorized
> >>>>    DOTS clients which have requested and been granted mitigation,
> >>>>    regardless of client requests for mitigation status."
> >>>>
> >>>> Please note that this is only true if a not-reliable transport is used.
> If a
> >>>> reliable transport is used, data is received at the application level
> without
> >>>> loss (but maybe some delay) or the connection is terminated (if loss is
> too
> >>>> high to retransmit successfully).
> >>>>
> >>>
> >>> [Med] The requirement as worded is OK.
> >>
> >> I disagree, because as I said if a reliable transport is used this is not
> true. Maybe you can adapt this sentence slightly to clarify that you probably
> had a scenario in mind where an unreliable transport is used
> >
> > The key part here is ‘packet’ vs ‘data’ - packets will be lost on congested
> links regardless of data integrity.  This may degrade connection re-
> establishment with tcp and cause data loss in an unreliable transport.
> 
> Yes, packet loss also occurs also with reliable transports and might lead to
> connection failure. However, I don’t this how this requirement is derived
> from that effect. If I use a reliable transport and my connection does not
> fail, I can be sure that the mitigation status information have been received
> correctly, so why do I need to re-send frequently then?

[Med] The text you quoted is not about "frequent retransmission" but about sending updates related to the status of a mitigation in progress. The server has to send regular notifications to update the client about the status of a mitigation. 

> 
> Mirja
> 
> 
>