Re: [Dots] AD review of draft-ietf-dots-signal-channel-25 (1st Part)

"Jon Shallow" <supjps-ietf@jpshallow.com> Thu, 17 January 2019 10:08 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 38578130F4A; Thu, 17 Jan 2019 02:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LOdfofniH_Bt; Thu, 17 Jan 2019 02:08:40 -0800 (PST)
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 78054130F30; Thu, 17 Jan 2019 02:08:40 -0800 (PST)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.91) (envelope-from <jon.shallow@jpshallow.com>) id 1gk4bE-0002jw-Ut; Thu, 17 Jan 2019 10:08:37 +0000
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@mcafee.com>, mohamed.boucadair@orange.com, dots@ietf.org, 'Benjamin Kaduk' <kaduk@mit.edu>, draft-ietf-dots-signal-channel@ietf.org
References: <787AE7BB302AE849A7480A190F8B93302EA08123@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <BYAPR16MB2790F718420DF7D6C1061870EA820@BYAPR16MB2790.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302EA08E05@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <BYAPR16MB2790BB23E26F2B213F8C388FEA830@BYAPR16MB2790.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302EA08EAE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <BYAPR16MB279093FB1F979E9D76E5933EEA830@BYAPR16MB2790.namprd16.prod.outlook.com>
In-Reply-To: <BYAPR16MB279093FB1F979E9D76E5933EEA830@BYAPR16MB2790.namprd16.prod.outlook.com>
Date: Thu, 17 Jan 2019 10:08:38 -0000
Message-ID: <06d301d4ae4c$9f60b650$de2222f0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIt0G4x4nPcIh7QQng3Q2EVCDCD8wHV6n3VAd+HKegCtUmiPwJcfUooAnnMJEukpu73UA==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/cbMmXEfiTYTv3uf2wxOrgFVJvnk>
Subject: Re: [Dots] AD review of draft-ietf-dots-signal-channel-25 (1st Part)
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, 17 Jan 2019 10:08:43 -0000


> -----Original Message-----
> From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of Konda,
> Tirumaleswar Reddy
> Sent: 17 January 2019 09:33
> To: mohamed.boucadair@orange.com; Benjamin Kaduk; draft-ietf-dots-signal-
> channel@ietf.org
> Cc: dots@ietf.org
> Subject: Re: [Dots] AD review of draft-ietf-dots-signal-channel-25 (1st Part)
> 
> > -----Original Message-----
> > From: Dots <dots-bounces@ietf.org> On Behalf Of
> > mohamed.boucadair@orange.com
> > Sent: Thursday, January 17, 2019 1:16 PM
> > To: Konda, Tirumaleswar Reddy
> <TirumaleswarReddy_Konda@McAfee.com>;
> > Benjamin Kaduk <kaduk@mit.edu>; draft-ietf-dots-signal-channel@ietf.org
> > Cc: dots@ietf.org
> > Subject: Re: [Dots] AD review of draft-ietf-dots-signal-channel-25 (1st Part)
> >
> > This email originated from outside of the organization. Do not click links or
> > open attachments unless you recognize the sender and know the content is
> > safe.
> >
> > Re-,
> >
> > OK.
> >
> > Given that we don't have an explicit mention about this in 8305, I added
> this
> > NEW sentence echoing what was in 6555:
> >
> >    Note that the DOTS client must cache information regarding the
> >    outcome of each connection attempt, and it uses that information to
> >    avoid thrashing the network with subsequent attempts.
> 
> Minor change:
> 
> Note that the DOTS client must cache information regarding the
> outcome of each connection attempt for a specific time period (e.g. 10
> minutes), and it uses that information to
> avoid thrashing the network with subsequent attempts.

How frequently should the client retry when all 4 connection methods fail - 10 minutes is excessive to me?

~Jon

> 
> -Tiru
> 
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Konda, Tirumaleswar Reddy
> > > [mailto:TirumaleswarReddy_Konda@McAfee.com]
> > > Envoyé : jeudi 17 janvier 2019 08:16
> > > À : BOUCADAIR Mohamed TGI/OLN; Benjamin Kaduk; draft-ietf-dots-signal-
> > > channel@ietf.org Cc : dots@ietf.org Objet : RE: AD review of
> > > draft-ietf-dots-signal-channel-25 (1st Part)
> > >
> > > > -----Original Message-----
> > > > From: mohamed.boucadair@orange.com
> > > > <mohamed.boucadair@orange.com>
> > > > Sent: Thursday, January 17, 2019 12:33 PM
> > > > To: Konda, Tirumaleswar Reddy
> > <TirumaleswarReddy_Konda@McAfee.com>;
> > > > Benjamin Kaduk <kaduk@mit.edu>;
> > > > draft-ietf-dots-signal-channel@ietf.org
> > > > Cc: dots@ietf.org
> > > > Subject: RE: AD review of draft-ietf-dots-signal-channel-25 (1st
> > > > Part)
> > > >
> > > >
> > > >
> > > > Hi Tiru,
> > > >
> > > > As you know RFC8305 obsoletes RFC6555.
> > > >
> > > > I fail to see where caching results is mentioned in 8305. Do you?
> > >
> > > Though RFC8035 obsoletes RFC6555, it is still compatible with RFC6555
> > > (see https://tools.ietf.org/html/rfc8305#appendix-A)
> > > It is useful to cache the happy eyeball results for a specific time.
> > >
> > > -Tiru
> > >
> > > >
> > > > Cheers,
> > > > Med
> > > >
> > > > > -----Message d'origine-----
> > > > > De : Konda, Tirumaleswar Reddy
> > > > > [mailto:TirumaleswarReddy_Konda@McAfee.com]
> > > > > Envoyé : mercredi 16 janvier 2019 12:11 À : BOUCADAIR Mohamed
> > > > > TGI/OLN; Benjamin Kaduk; draft-ietf-dots-signal- channel@ietf.org Cc :
> > > > > dots@ietf.org Objet : RE: AD review of
> > > > > draft-ietf-dots-signal-channel-25 (1st Part)
> > > > >
> > > > > Hi Med,
> > > > >
> > > > > Please see inline
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dots <dots-bounces@ietf.org> On Behalf Of
> > > > > > mohamed.boucadair@orange.com
> > > > > > Sent: Wednesday, January 16, 2019 1:30 PM
> > > > > > To: Benjamin Kaduk <kaduk@mit.edu>; draft-ietf-dots-signal-
> > > > > > channel@ietf.org
> > > > > > Cc: dots@ietf.org
> > > > > > Subject: Re: [Dots] AD review of
> > > > > > draft-ietf-dots-signal-channel-25 (1st
> > > > > Part)
> > > > > >
> > > > > > >
> > > > > > >                                   These connection attempts are
> > > > > > >    performed by the DOTS client when it initializes.  The
> > > > > > > results of
> > > the
> > > > > > >    Happy Eyeballs procedure are used by the DOTS client for
> > > > > > > sending
> > > its
> > > > > > >    subsequent messages to the DOTS server.
> > > > > > >
> > > > > > > I see this is scoped to "when the client initializes", so I
> > > > > > > don't know whether it adds more or not to end with "for the
> > > > > > > duration of the DOTS session" or some similar scoping for the
> > > > > > > caching of the happy eyeballs results.
> > > > > >
> > > > > > [Med] The connection attempts are performed each time the client
> > > > > > has to select among a list of v4, v6 (tls, dtls). This is
> > > > > > particularly true when
> > > > > the client
> > > > > > initiates, but this may also be true each time the client has to
> > > > > > select
> > > > > among
> > > > > > v4, v6, DTLS, TLS (e.g., the client attaches to a new network).
> > > > > >
> > > > > > I updated the text to:
> > > > > >
> > > > > > "These connection attempts are performed by the DOTS client when
> > > > > > it initializes, or in general when it has to select an address
> > > > > > family and
> > > > > transport
> > > > > > to contact its DOTS server."
> > > > >
> > > > > Happy eyeballs mandates caching the results, see
> > > > > https://tools.ietf.org/html/rfc6555#section-4 (to avoid thrashing
> > > > > the network).
> > > > > We may want to update the above line accordingly.
> > > > >
> > > > > Cheers,
> > > > > -Tiru
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots