Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-serve-stale-03.txt

Christopher Morrow <morrowc.lists@gmail.com> Tue, 05 March 2019 02:36 UTC

Return-Path: <christopher.morrow@gmail.com>
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 E1ED5130E95 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 18:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JHFef9h4_0bg for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 18:36:21 -0800 (PST)
Received: from mail-it1-x133.google.com (mail-it1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A767F12D4E7 for <dnsop@ietf.org>; Mon, 4 Mar 2019 18:36:21 -0800 (PST)
Received: by mail-it1-x133.google.com with SMTP id m137so2038609ita.0 for <dnsop@ietf.org>; Mon, 04 Mar 2019 18:36:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wu1GxeIKvjiqpe3VPwj9cRb+eSp59PP8xPdwUaEYlz4=; b=Cg5xz/zT32YwYjlB4cARgk6bPTuRtv/U4xTlwAT8NcfOBFxUiH7gcMHOdUB7M7cC/f +NRaBG2ls9BcXoC4uFCrfA1lkokNiWJ5Bt1i0Z5/Vh6xxzyHVpvbmw5mH7PxZJ0RmHJX k3cFRUKGd0382d67Qzsj+74f3Dx87wK1GUOch6Z0Q56YSF4hW+j1Wg54cv7hJ1aJdlWz o0znrJe5wkNGaGaHB6T5ofYEoOo8dvlB4Hxy/XX1XqIzNCdnoAxFdWZJXTiUVCVQDSIR vY/1NqEFRTkFwK9RgJR5L2LhFUUDsjQ2/4rGheELAD9WS269BMBdhz5mf61qCVPlrZEI jkJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wu1GxeIKvjiqpe3VPwj9cRb+eSp59PP8xPdwUaEYlz4=; b=jGfzlbj2hYMQVahtqx/BNAM87IauNl0yMLMvHr3/ihQoINXFRAG9+oEIPL41SlJx3g K1IiFlIShTjgCxuqN0B+XCp1CiVIVGw8LGkwqjBrCiLUMPX/JO1WGd98/2HvUas8ZUZ2 H5AnSSOyY/4bH/t2lSI9nUlJjfEvDe8dQcdgca9hJct4dAxhb9aYICbBThPTk/RZ5SkO L+Y10VAXCbHbHYUuOYYIOHICMcrlGi37hXhj+XTU9siDC35NUjzRKut8k/qwtFaMnKQj w6ytdu/GYw+P0nGg3w0XKR8kYUozhN+CIQjwrNou/2yan2ztFjMFs78e48TgvX6vt7Vr cBNA==
X-Gm-Message-State: APjAAAWFxlTgQ9XrC6x2JJXO13g0rp5w3NIHU7m4hY/npNKsOKtShLIG UWbe/BGS7OBPGKKGWXIVzbqEHjOQPeWrmwaGKhg=
X-Google-Smtp-Source: APXvYqwSCigvsB2Manw+2lnoW1Xj632YzizXZBJwXaKnytqPCpnSUM8LrgSrNuMcNBgHx4Vl5RVWbboDhOhx6Lz1RDE=
X-Received: by 2002:a24:6cc8:: with SMTP id w191mr1409719itb.139.1551753380670; Mon, 04 Mar 2019 18:36:20 -0800 (PST)
MIME-Version: 1.0
References: <155094804613.28045.8648150477440044197@ietfa.amsl.com> <CA+9_gVscCzr0S8A0Z23q0V1B+BZeLtDoZRSKyEJDPZ3P=KT-tw@mail.gmail.com> <CAL9jLaYo5JH6vf+djEn0O=YGhLV2AkytMg_eKQmWn=Pma5yBFQ@mail.gmail.com> <4253851.Zqd2zPpPcC@linux-9daj>
In-Reply-To: <4253851.Zqd2zPpPcC@linux-9daj>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Mon, 4 Mar 2019 21:36:09 -0500
Message-ID: <CAL9jLaZU2k7LF4HrwXGts_-wTuiX51erBaCPOf-KTzPoMJrmAg@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop <dnsop@ietf.org>, Puneet Sood <puneets=40google.com@dmarc.ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>, Paul Hoffman <paul.hoffman@icann.org>
Content-Type: multipart/alternative; boundary="00000000000008b5f605834fbdf5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/R_TBbfTnv-WFsQKaLvW77Zfwlxw>
Subject: Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-serve-stale-03.txt
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: Tue, 05 Mar 2019 02:36:24 -0000

On Mon, Mar 4, 2019 at 9:26 PM Paul Vixie <paul@redbarn.org> wrote:

> On Tuesday, 5 March 2019 02:21:42 UTC Christopher Morrow wrote:
> > can I ask, what happens when a domain is intentionally down though? For
> > instance, take .eg... ~4yrs back? (maybe 5?) Someone requested that the
> > master/shadow NS go down, hard. All public auth servers eventually (in a
> > day or so) went dark too.
>
> i already raised that question, very far up-thread. got no answer.
>
>
apologies for repeat-asking :( whoops! It'd still be good to hear an answer.
I can think of simple product and not 'life safety' reasons that I might
darken a zone as well, so if you don't want to answer for an abundance of
caution for your fellow folken... think of the product marketing folk who
mistakenly launch a day early, or who would like to retire a service in a
clearly delineated manner.

:)

> If someone is 'ordered' to make a zone dark, there may be reasons for that
> > action, and real penalties if the request is not honored.
> > Is this draft suggesting that the DNS operations folk go against the
> wishes
> > of the domain owner by keeping a domain alive after the auth servers have
> > become unreachable? How would a recursive resolver know that the auth is
> > down: "By mistake" vs: "By design" ?
>
> this the essence of the argument against utility for this entire proposal.
> no
> data should be served beyond its TTL unless some new leasing protocol is
> first
> defined, to obtain permission and to provide a cache invalidation method.
>

this is what I was thinking as well. thanks for more clarity.