Re: [Dots] WGLC on draft-ietf-dots-server-discovery-05

<mohamed.boucadair@orange.com> Thu, 07 November 2019 13:46 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 400B0120045; Thu, 7 Nov 2019 05:46:01 -0800 (PST)
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 0a8XomVbR2UR; Thu, 7 Nov 2019 05:46:00 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1F5712084A; Thu, 7 Nov 2019 05:45:59 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 4784Rp19GKzBrtN; Thu, 7 Nov 2019 14:45:58 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.42]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 4784Rp01HNz5vNB; Thu, 7 Nov 2019 14:45:58 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42%21]) with mapi id 14.03.0468.000; Thu, 7 Nov 2019 14:45:57 +0100
From: <mohamed.boucadair@orange.com>
To: Valery Smyslov <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>
Thread-Topic: [Dots] WGLC on draft-ietf-dots-server-discovery-05
Thread-Index: AQG7u70viJ1zeDaA3CAo0XFND0KMCQJctfwqp6B7TZCAAAMy8A==
Date: Thu, 7 Nov 2019 13:45:57 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93303135CA81@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <011d01d58974$b70298b0$2507ca10$@smyslov.net> <787AE7BB302AE849A7480A190F8B93303135B8E6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <082d01d5956d$627f4720$277dd560$@smyslov.net>
In-Reply-To: <082d01d5956d$627f4720$277dd560$@smyslov.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/1aw82o3Vu0wDROCJDPDkxX-peJ8>
Subject: Re: [Dots] WGLC on draft-ietf-dots-server-discovery-05
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, 07 Nov 2019 13:46:01 -0000

Re-,

Thank you, Valery.

As per the text you quoted, it should be put it its context:

   The design allows to terminate the base DOTS channels and DOTS Call
   Home on the same or distinct peer DOTS agents.  If distinct peer DOTS
   agents are deployed, the DHCP option can return, for example, a list
                                                  ^^^^^^^^^^^^^^ 
   of IP addresses to a requesting DOTS agent.  This list includes the
   IP address to be used for the base DOTS channels and the IP address
   for the DOTS Call Home.  The DOTS client (or the Call Home DOTS
   server) will then use the address selection specified in Section 4.3
   of [I-D.ietf-dots-signal-channel] to identify the IP address of the
   peer DOTS server (or Call Home Client).

It does only exemplify what an agent may do. The text you quoted does not use any normative language.

Cheers,
Med

> -----Message d'origine-----
> De : Valery Smyslov [mailto:valery@smyslov.net]
> Envoyé : jeudi 7 novembre 2019 14:15
> À : BOUCADAIR Mohamed TGI/OLN; dots@ietf.org
> Cc : dots-chairs@ietf.org
> Objet : RE: [Dots] WGLC on draft-ietf-dots-server-discovery-05
> 
> Hi Med,
> 
> this makes sense for signal-call-home, but why signal-channel?
> You currently directly reference it:
> 
>    The DOTS client (or the Call Home DOTS
>    server) will then use the address selection specified in Section 4.3
>    of [I-D.ietf-dots-signal-channel] to identify the IP address of the
>    peer DOTS server (or Call Home Client).
> 
> Regards,
> Valery.
> 
> > Hi Valery, all,
> >
> > Is there any objection if we move I-D.ietf-dots-signal-call-home and I-
> D.ietf-dots-signal-channel to be
> > informative references.
> >
> > We have listed I-D.ietf-dots-signal-channel as normative because we have
> this text in Section 8:
> >
> > "DOTS agents must
> >    authenticate each other using (D)TLS before a DOTS session is
> >    considered valid according to the [I-D.ietf-dots-signal-channel]."
> >
> > But I'm afraid this is not appropriate given that the above is not a NEW
> requirement but a reminder of the
> > behavior in I-D.ietf-dots-signal-channel. We may call out this better by
> using this text:
> >
> > NEW:
> >   As a reminder, DOTS agents must
> >    authenticate each other using (D)TLS before a DOTS session is
> >    considered valid according to the [I-D.ietf-dots-signal-channel].
> >
> > Any objections?
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Dots [mailto:dots-bounces@ietf.org] De la part de Valery Smyslov
> > > Envoyé : mercredi 23 octobre 2019 09:37
> > > À : dots@ietf.org
> > > Cc : dots-chairs@ietf.org
> > > Objet : [Dots] WGLC on draft-ietf-dots-server-discovery-05
> > >
> > > Hi,
> > >
> > > this message starts a Work Group Last Call (WGLC) for draft-ietf-dots-
> > > server-discovery-05.
> > > The version to be reviewed is here: https://www.ietf.org/id/draft-ietf-
> > > dots-server-discovery-05.txt
> > >
> > > The WGLC will last for two weeks and will end on November the 7th.
> > > Please send your comments to the list before this date.
> > >
> > > Regards,
> > > Frank & Valery.
> > >
> > >
> > > _______________________________________________
> > > Dots mailing list
> > > Dots@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dots