Re: [DNSOP] comments on draft-ietf-dnsop-serve-stale-03

Frederico A C Neves <fneves@registro.br> Mon, 25 March 2019 16:24 UTC

Return-Path: <fneves@registro.br>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 032CA1203BD for <dnsop@ietfa.amsl.com>; Mon, 25 Mar 2019 09:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 v4VLSaHtQQ0f for <dnsop@ietfa.amsl.com>; Mon, 25 Mar 2019 09:24:13 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) (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 022661200B3 for <dnsop@ietf.org>; Mon, 25 Mar 2019 09:24:12 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id 4809F3EEF01; Mon, 25 Mar 2019 13:24:10 -0300 (-03)
Date: Mon, 25 Mar 2019 13:24:10 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Ray Bellis <ray@bellis.me.uk>
Cc: Puneet Sood <puneets@google.com>, IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20190325162410.GL76919@registro.br>
References: <CAJE_bqdugE3oMqyHres4hwhs4-NpO8yW2FwGDrk2WDAtbweBiQ@mail.gmail.com> <23682.53436.400539.805166@gro.dd.org> <8ffa4b04-324a-36c8-a9ff-e0cda726a54c@NLnetLabs.nl> <841f8174-c7d5-c702-e6be-ccb9a7c2c048@redbarn.org> <fe4aecac-aa46-e269-bc77-5250b383685a@bellis.me.uk> <CA+9_gVsfrJVtqqsniJ_f4NKkbtz5J4Q=eHxvxX9Ud86u5=j9Hw@mail.gmail.com> <e75aa69c-e02b-72a1-6375-660151afbdd2@bellis.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e75aa69c-e02b-72a1-6375-660151afbdd2@bellis.me.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IkJu1Vs8-KvYDbDJyabR6p5xKM0>
Subject: Re: [DNSOP] comments on draft-ietf-dnsop-serve-stale-03
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 16:24:15 -0000

On Mon, Mar 25, 2019 at 04:30:01PM +0100, Ray Bellis wrote:
> 
> 
> On 25/03/2019 16:08, Puneet Sood wrote:
> 
> > you mean lots of changes or lots of agreement with the quoted text?
> > They mean very different things.
> 
> I was agreeing with the quoted text - I believe that any serving of 
> stale records must be predicated on the presence of a valid delegation 
> from the parent zone.
> 
> Serve stael must not become a vector whereby malware can keep its C&C 
> systems artificially alive even if the parent has removed the C&C domain 
> name.

+1

Fred