Re: [Dots] WGLC on draft-ietf-dots-signal-call-home-06

Benjamin Kaduk <kaduk@mit.edu> Mon, 11 November 2019 18:06 UTC

Return-Path: <kaduk@mit.edu>
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 6B5991208FB; Mon, 11 Nov 2019 10:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 mfWQy9jRSRtl; Mon, 11 Nov 2019 10:06:12 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 DC19D12085B; Mon, 11 Nov 2019 10:06:11 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xABI66Mi017934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 11 Nov 2019 13:06:08 -0500
Date: Mon, 11 Nov 2019 10:06:05 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: mohamed.boucadair@orange.com
Cc: Jon Shallow <supjps-ietf@jpshallow.com>, "'Valery Smyslov'" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>
Message-ID: <20191111180605.GA32847@kduck.mit.edu>
References: <011c01d58974$74529b00$5cf7d100$@smyslov.net> <1bfc01d594c5$61631810$24294830$@jpshallow.com> <787AE7BB302AE849A7480A190F8B93303135A639@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <1ca401d59549$6839d730$38ad8590$@jpshallow.com> <787AE7BB302AE849A7480A190F8B93303135B754@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <1cbb01d59557$9bfb78e0$d3f26aa0$@jpshallow.com> <787AE7BB302AE849A7480A190F8B93303135B8A2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <1e6101d5963b$d63f7ee0$82be7ca0$@jpshallow.com> <787AE7BB302AE849A7480A190F8B93303135FB38@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <787AE7BB302AE849A7480A190F8B93303135FB38@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/xqkF88r87D4bKtq4zmVIRL-ubCU>
Subject: Re: [Dots] WGLC on draft-ietf-dots-signal-call-home-06
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: Mon, 11 Nov 2019 18:06:15 -0000

On Fri, Nov 08, 2019 at 02:21:24PM +0000, mohamed.boucadair@orange.com wrote:
> Hi Jon,
> 
> Thank you for the feedback. 
> 
> Please see inline.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Jon Shallow [mailto:supjps-ietf@jpshallow.com]
> > Envoyé : vendredi 8 novembre 2019 14:53
> > À : BOUCADAIR Mohamed TGI/OLN; 'Valery Smyslov'; dots@ietf.org; dots-
> > chairs@ietf.org
> > Objet : RE: [Dots] WGLC on draft-ietf-dots-signal-call-home-06
> > 
> > Hi Med et al,
> > 
> > I have gone back over the heartbeat call home and have a couple of comments
> > 
> > In
> > https://tools.ietf.org/html/draft-ietf-dots-signal-channel-38#section-4.5..1
> > 
> > OLD
> > 
> >    Figure 18 shows how to obtain acceptable configuration parameters for
> >    the DOTS server.
> >
> 
> [Med] "for" is used in reference to "acceptable" from the perspective of the server. Sure, the information will be retrieved from the server.  

perhaps "how to obtain configuration parameters that the DOTS server will
find acceptable", then?

-Ben

>  
> > NEW
> > 
> >    Figure 18 shows how to obtain acceptable configuration parameters for
> >    the DOTS client.
> > 
> > or NEW
> > 
> >    Figure 18 shows how to obtain acceptable configuration parameters from
> >    the DOTS server.
> >