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

"Valery Smyslov" <valery@smyslov.net> Thu, 07 November 2019 14:26 UTC

Return-Path: <valery@smyslov.net>
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 0E8D7120821; Thu, 7 Nov 2019 06:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smyslov.net
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 2-avBl8f7wBq; Thu, 7 Nov 2019 06:26:35 -0800 (PST)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 0AB13120232; Thu, 7 Nov 2019 06:26:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:In-Reply-To:References:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2HpTVJSAZV/lvH+GdaL1R6/p2uUejBkjgUbyobv/awA=; b=Xl8VNs/5Vp++Gq3cJCOA+rjq3r OXPT98dJUE5AJj+oaqUPBOpmhp0fJyD1GyegvWORHFibtZvDmzfWbTnF84hmVHZe9mgNNHHGWTgkm w0C/i1xlyYlQOsVmdQ7B36BoYGbvfQugUyYMUdtTUboIw1zqUmvQ5qKgJmc3NM6sa5iG4fB/oCGUC 2kuOi/QP7DciMhx+LyL/50WdGx4scJmalOo6eB0tP3DvNbVh8cosWS7oUQ7T86DfRge1NNufoLn9z d37euqBrUtMNnBE/uUypeJNbZHSL6/S3n6TV84pkmsE9kG8V5WM58U5EJrDRxVrlz9PQtSOvpDvD/ zjJ7D8wQ==;
Received: from [82.138.51.4] (port=3071 helo=buildpc) by direct.host-care.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.92) (envelope-from <valery@smyslov.net>) id 1iSik4-0007B8-6M; Thu, 07 Nov 2019 09:26:32 -0500
From: "Valery Smyslov" <valery@smyslov.net>
To: <mohamed.boucadair@orange.com>, <dots@ietf.org>
Cc: <dots-chairs@ietf.org>
References: <011d01d58974$b70298b0$2507ca10$@smyslov.net> <787AE7BB302AE849A7480A190F8B93303135B8E6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <082d01d5956d$627f4720$277dd560$@smyslov.net> <787AE7BB302AE849A7480A190F8B93303135CA81@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93303135CA81@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Thu, 7 Nov 2019 17:26:34 +0300
Message-ID: <083701d59577$5d0bd100$17237300$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG7u70viJ1zeDaA3CAo0XFND0KMCQJctfwqAkbP+1QCkdMBS6d5y18Q
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/fX2NcJHcbKEqsKU19kB2Up7W7qc>
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 14:26:36 -0000

Hi Med,

if you think that readers of this document are not required to read and understand 
signal-channel in order to implement this spec, then it's perfectly OK to make it Informative.

Regards,
Valery.


> 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