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

<mohamed.boucadair@orange.com> Wed, 17 July 2019 08:10 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 472541201D1; Wed, 17 Jul 2019 01:10:12 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 RmswuBrlShkR; Wed, 17 Jul 2019 01:10:10 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A26612009C; Wed, 17 Jul 2019 01:10:10 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 45pVLS3GzkzCrPp; Wed, 17 Jul 2019 10:10:08 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.23]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 45pVLS0RjRzFpWM; Wed, 17 Jul 2019 10:10:08 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM41.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Wed, 17 Jul 2019 10:10:08 +0200
From: <mohamed.boucadair@orange.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
CC: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "Roman Danyliw" <rdd@cert.org>, "dots@ietf.org" <dots@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "draft-ietf-dots-data-channel@ietf.org" <draft-ietf-dots-data-channel@ietf.org>
Thread-Topic: =?utf-8?B?W0RvdHNdICBNaXJqYSBLw7xobGV3aW5kJ3MgRGlzY3VzcyBvbiBkcmFmdC1p?= =?utf-8?B?ZXRmLWRvdHMtZGF0YS1jaGFubmVsLTI4OiAod2l0aCBESVNDVVNTIGFuZCBD?= =?utf-8?Q?OMMENT)?=
Thread-Index: AQHVO+lrEOXXRpBeYEyBEBxuCEvpM6bOZzig
Date: Wed, 17 Jul 2019 08:10:07 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EC96FC2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155679628494.24951.9145538661531263463.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA68C8B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20190701154032.GB13810@kduck.mit.edu> <A4BD2109-EC58-4FED-A8B0-2EE5AC47A69C@kuehlewind.net> <DM5PR16MB1705BED0F42996593B0C0A70EAF80@DM5PR16MB1705.namprd16.prod.outlook.com> <24FFE7CE-B91A-4CF4-BB85-D6108ACE0043@kuehlewind.net> <DM5PR16MB170529399AC19B88B321A35DEAF80@DM5PR16MB1705.namprd16.prod.outlook.com> <642531B0-3E3A-4A5C-BD20-C74AA3698936@kuehlewind.net> <DM5PR16MB170519F8C328B05B9ED61EECEAFB0@DM5PR16MB1705.namprd16.prod.outlook.com> <AD83F907-35D8-4F44-9DEC-8ABB8E27A6EF@kuehlewind.net> <787AE7BB302AE849A7480A190F8B93302EAB345F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <5C02462E-0067-4A56-940D-15D434676CC6@kuehlewind.net>
In-Reply-To: <5C02462E-0067-4A56-940D-15D434676CC6@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/Pqb6LkvL4oVv4XSU0X0FdG0zQSw>
Subject: Re: [Dots] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-?= =?utf-8?q?dots-data-channel-28=3A_=28with_DISCUSS_and_COMMENT=29?=
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: Wed, 17 Jul 2019 08:10:12 -0000

Hi Mirja, 

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Mirja Kuehlewind [mailto:ietf@kuehlewind.net]
> Envoyé : mardi 16 juillet 2019 17:16
> À : BOUCADAIR Mohamed TGI/OLN
> Cc : Konda, Tirumaleswar Reddy; Roman Danyliw; dots@ietf.org; Benjamin
> Kaduk; The IESG; dots-chairs@ietf.org; draft-ietf-dots-data-
> channel@ietf.org
> Objet : Re: [Dots] Mirja Kühlewind's Discuss on draft-ietf-dots-data-
> channel-28: (with DISCUSS and COMMENT)
> 
[snip]
> >>>
> >>> Sure, will add the following text:
> >>>
> >>>  A DOTS client can either maintain a persistent connection or periodic
> >>>  connections with its DOTS server(s).  If the DOTS client needs to
> >>>  frequently update the drop-list or accept-list filtering rules or
> >>>  aliases, it maintains a persistent connection with the DOTS server.
> >>>  For example, CAPTCHA and cryptographic puzzles can be used by the
> >>>  mitigation service in the DOTS client domain to determine whether the
> >>>  IP address is used for legitimate purpose or not, and the DOTS client
> >>>  can frequently update the drop-list filtering rules.  A persistent
> >>>  connection is also useful if the DOTS client subscribes to event
> >>>  notifications (Section 6.3 of [RFC8040]).
> >>>
> >>> - Tiru and Med
> >>
> >> Thanks!
> >>
> >> Two more small comments:
> >>
> >> At least to me the term “periodic" is not clear. I guess mean something
> >> like short-lived connections, where you have a request, you open a
> >> connection, send it, get a reply, and close the connection immediately
> or
> >> after a short idle period. Or is there actually any kind of periodicity
> in
> >> the dots protocol in general? Can you pleas clarify.
> >
> > [Med] We are trying to reuse the same terminology as RESTCONF (draft-
> ietf-netconf-restconf-client-server).
> >
> > For the DOTS case, the DOTS client is required to register and send
> requests to refresh the registration in regular intervals (otherwise, the
> DOTS client won't be able to created filters). Likewise, cycles will be
> observed because the client will need to maintains the aliases and ACLs it
> created. The client may use these cycles for any planned activity (create
> new aliases, create a new filter, etc.) or not.
> >
> >>
> >> Also if a persistent connection is used, I think it would (again) be
> good
> >> to clarify what should be done if the connection fails. I think the
> right
> >> advise in this case, is to not reconnect immediately but only if you
> have
> >> another request to send, right?
> >>
> >
> > [Med] draft-ietf-netconf-restconf-client-server voices for the
> following:
> >
> >   Maintain a persistent connection to the
> >   RESTCONF server. If the connection goes down,
> >   immediately start trying to reconnect to the
> >   RESTCONF server, using the reconnection strategy.
> >
> > Which is the right approach, IMO.
> >
> > We didn't touched on connection management because we are relying on
> RESTCONF. DOTS will use whatever strategy adopted for RESTCONF.
> >
> > I don't think it is a good idea to add specific behavior into our spec.
> 
> That is fine. I wasn’t aware that this is specified like this in RESTCONF
> and that your are replying on it. Instead of (re-)specifying in this in
> document, I would recommend to actually add a reference to this part  of
> the RESTCONF document and make clear that this is what you are replying
> on.

[Med] We can cite draft-ietf-netconf-restconf-client-server as an informative reference with the following text:

   Additional considerations
   related to RESTCONF connection management (including, configuring the
   connection type or the reconnect strategy) can be found in
   [I-D.ietf-netconf-restconf-client-server].

Better?

> 
> Thanks!
> Mirja