Re: [DNSOP] Fwd: New Version Notification for draft-pusateri-dnsop-update-timeout-01.txt

Mark Andrews <marka@isc.org> Thu, 21 February 2019 19:34 UTC

Return-Path: <marka@isc.org>
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 68B7213114A for <dnsop@ietfa.amsl.com>; Thu, 21 Feb 2019 11:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 jLUzxhLmIZtI for <dnsop@ietfa.amsl.com>; Thu, 21 Feb 2019 11:34:08 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 48EA1131148 for <dnsop@ietf.org>; Thu, 21 Feb 2019 11:34:07 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id ED9573AB05B; Thu, 21 Feb 2019 19:34:06 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B32FB160073; Thu, 21 Feb 2019 19:34:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9A112160072; Thu, 21 Feb 2019 19:34:06 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GZsIar3JT8Np; Thu, 21 Feb 2019 19:34:06 +0000 (UTC)
Received: from [172.30.42.88] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 0CA08160050; Thu, 21 Feb 2019 19:34:06 +0000 (UTC)
Content-Type: multipart/alternative; boundary=Apple-Mail-B948910D-045B-4365-8358-F9F74A6B0E1A
Mime-Version: 1.0 (1.0)
From: Mark Andrews <marka@isc.org>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <CAJE_bqd3cAqtv_FkvhuCC6jubzZLx9v5ud2WzrL9bQE+8tLB8w@mail.gmail.com>
Date: Fri, 22 Feb 2019 06:34:04 +1100
Cc: Joe Abley <jabley@hopcount.ca>, dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>
Content-Transfer-Encoding: 7bit
Message-Id: <FC8037A8-37E2-4457-A410-6CECBB709D49@isc.org>
References: <155053239541.25848.12960190085730298684.idtracker@ietfa.amsl.com> <969D8BA1-6ED3-47E8-AFFD-2BEE8EA3E66B@bangj.com> <alpine.DEB.2.20.1902191219070.766@grey.csi.cam.ac.uk> <0DE33073-93B1-4CF5-B12D-B7266E21E8B2@timwattenberg.de> <alpine.LRH.2.21.1902191715230.30381@bofh.nohats.ca> <1F461BFA-638A-4607-84BD-F8B8597A1114@isc.org> <alpine.LRH.2.21.1902200028210.29865@bofh.nohats.ca> <646C86F6-C10D-43DF-ADE8-19222994E4D1@hopcount.ca> <CAJE_bqd3cAqtv_FkvhuCC6jubzZLx9v5ud2WzrL9bQE+8tLB8w@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Yp6NOLl_W49AkBc6Vf_OC-UEgyM>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-pusateri-dnsop-update-timeout-01.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: Thu, 21 Feb 2019 19:34:11 -0000

Machines die. Machines are unplugged.  Server are unreachable at critical times. Externally driven cleanup can never be reliable. 

-- 
Mark Andrews

> On 22 Feb 2019, at 06:21, 神明達哉 <jinmei@wide.ad.jp> wrote:
> 
> At Wed, 20 Feb 2019 07:51:51 -0500,
> Joe Abley <jabley@hopcount.ca> wrote:
> 
> > The crux of the use case seems to be that it is commonplace for names in the DNS to exist for short periods of time and that for some applications a name that overstays its welcome can cause an operational problem.
> > 
> > While I can understand the philosophical desire to complete the UPDATE specification so that it is possible to engineer around this scenario, I don't see the practical application.
> 
> I happen to know there's a practical application related to this
> proposal..  As Mark says not all DHCP servers behave politely; there
> are servers that just add RRs via DDNS and forget them.  We could say
> that it's a problem of poorly implemented DDNS clients, not something
> that should be solved in the DNS protocol.  I wouldn't necessarily be
> opposed to that view.  In fact, given the higher bar with the "camel"
> test, I'm not yet really convinced about the need for a protocol-based
> solution to this problem either.  But at least this is related to a
> practical problem, not just a philosophical one.
> 
> --
> JINMEI, Tatuya
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop