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

Ted Lemon <mellon@fugue.com> Sat, 25 August 2018 12:53 UTC

Return-Path: <mellon@fugue.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 5ECBA130E00 for <dnsop@ietfa.amsl.com>; Sat, 25 Aug 2018 05:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 9r2T6MEE1vXg for <dnsop@ietfa.amsl.com>; Sat, 25 Aug 2018 05:53:38 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 622E4130DC2 for <dnsop@ietf.org>; Sat, 25 Aug 2018 05:53:38 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id 75-v6so9234937iou.11 for <dnsop@ietf.org>; Sat, 25 Aug 2018 05:53:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zlTaedVCS/DppehMr5tLBjegBtxuAdQxXXF5BumqdxM=; b=kzhHkomv2TditAsID9kLonnike7DCZb4y/KxrLDvojx6mAdF2neau/Fq5aijwbqyO6 2MV+ZpL5hllNkImFbUCoq+PJypua9f12KovE3bMk8lYVXSgK24TKL7IjIN6eqIGyE2I0 uVsrdAgYdZrAn5/DHP4/PDZk/C2PD29bFL+w4Qv/0+UBFueYf+X0GvuKYT0griwGLXMA xhR/23KF0XyxVHOQODY7ZLhO6J4rjLCsSSZKWdoLs5zihJXG1eAk4f5SddztGjAvLgy0 ijnRmgbfxKqWohytaDkgpyh0u2VbcJ4qWolwNultP3fP2pzthPN9q2urgcOuyXo2tVPD i4+w==
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=zlTaedVCS/DppehMr5tLBjegBtxuAdQxXXF5BumqdxM=; b=F7nRyRFG9DnRub3T3hMH4G4XDVJvcv+/XIpusw1Uif5JjyH99sIoZNRvf5c3zoMaMX eHtbadzHWF6QHzZn7dikFfcXMQZabutV71rigiq+4xtPyR+JLeHUzhmcAl9dX/ztkj2V KHMiwtUX3E94dpkKYfwxWSwhF6139Nm5WXpM5ybNDBKO8oWz74SpkD9KbEFoM3nS3BsX Ko3VK61QGvauFzbCVSEOfA+nZidgpyfLTRKpDOAcDugrMAMVbAzB4Bm8mRW61piG1mcw XT1/VrESPYXmch5j8ctE3k8bv5qKTRhqM1KTB43l+bVTNRy/CqRlI96Ypn+hMQIkDQw5 ykGw==
X-Gm-Message-State: APzg51Bq7k0nZTl/NBjvm0IVBDyX6P3ofVTWlKRtVHyndbSt6UVvSnue yRy7YyfQH7MsQKwtYlHHN/wjqGbikNqllmQFH7snMA==
X-Google-Smtp-Source: ANB0VdaiY1wvhVOGb+h+bVgOULQEEol9PSeUAYPz6ka3DjynXDMZMh5W7lB9tFsbfMKNdGztVQtNwJy4MEORTXGZGQQ=
X-Received: by 2002:a6b:9d0b:: with SMTP id g11-v6mr4619751ioe.85.1535201617447; Sat, 25 Aug 2018 05:53:37 -0700 (PDT)
MIME-Version: 1.0
References: <153507165910.12116.7113196606839876181.idtracker@ietfa.amsl.com> <AFB90F6F-5D99-4403-AAB6-1123727973E6@bangj.com> <5B7F5E07.5080100@redbarn.org> <7F91FFF7-71C3-4F8E-82CD-266B170983E0@bangj.com> <C0EE2719-B662-4231-AF51-D3B98B00AD0D@fugue.com> <6D607922-393D-4549-AAFA-49279C260CA4@bangj.com> <3C6100BD-62D6-41ED-B7BF-679F0D4E4113@fugue.com> <5063A32B-4877-4860-BA73-CCB068AB7FCB@bangj.com> <CAPt1N1=tXZNgT6ygAaLFfOMze7hbGZ6q_eN1C3iEo9ryBNcyLg@mail.gmail.com> <98EF2CAC-7C13-4E68-8D2B-EC0659EA9646@bangj.com> <CAPt1N1kFNY4=CUMsTvXmeRREeLAkY8xpBdw4vPDxujgke6QT8A@mail.gmail.com> <963460AA-14BB-44AA-87CA-7F09A707DB5D@bangj.com> <47AE41F8-9F5F-4CC8-B4F0-7E8191011E99@bangj.com> <F4335D3A-0241-437F-A428-8EA95F0A1C18@fugue.com> <56E8B2A6-7B65-4D25-B102-9EFA7E2CBE7B@bangj.com> <86D465A4-F390-4370-83EC-0E72FBE115BE@isc.org> <CAPt1N1=xy+JAtgvvF_+9LiTiefbpTy_Vd0b8gswozA1K1C57Nw@mail.gmail.com> <99FA0B76-D225-45FC-A33C-B65E2673A45E@isc.org>
In-Reply-To: <99FA0B76-D225-45FC-A33C-B65E2673A45E@isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 25 Aug 2018 08:53:01 -0400
Message-ID: <CAPt1N1kp8Tg5tWEiDCMuMNTmehRsBSkkC1=u+RcvkG6ZCegE-g@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: Tom Pusateri <pusateri@bangj.com>, dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001126b0057441fb6f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IvtfZgUaudhiVwHEs9DwgtvUstQ>
Subject: Re: [DNSOP] New Version Notification for draft-pusateri-dnsop-update-timeout-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 25 Aug 2018 12:53:42 -0000

I'm not saying nobody does it.   I'm trying to understand how this helps.

On Fri, Aug 24, 2018 at 11:24 PM Mark Andrews <marka@isc.org>; wrote:

> Ted stop being daft. People have been registering addresses of machines in
> the public DNS for decades.   SLAAC. Is just one source of addresses. DHCP
> is another. Come up with a third method and they will do it with it.
>
> Also DHCP servers from ISPs don’t have authority to update DNS servers for
> my machines. Only those machines have such authority so don’t discount DHCP
> derived addresses.
>
> --
> Mark Andrews
>
> On 25 Aug 2018, at 12:53, Ted Lemon <mellon@fugue.com>; wrote:
>
> When would that happen?
>
> On Fri, Aug 24, 2018 at 10:52 PM Mark Andrews <marka@isc.org>; wrote:
>
>> Registering slaac derived addresses in the DNS.  These are tied to prefix
>> lifetimes.
>>
>>
>> --
>> Mark Andrews
>>
>> On 25 Aug 2018, at 05:02, Tom Pusateri <pusateri@bangj.com>; wrote:
>>
>>
>>
>> On Aug 24, 2018, at 2:59 PM, Ted Lemon <mellon@fugue.com>; wrote:
>>
>> On Aug 24, 2018, at 2:43 PM, Tom Pusateri <pusateri@bangj.com>; wrote:
>>
>> It seems odd to take the position that the authoritative server shouldn’t
>> need to clean up stale entries because it assumes the client will do it for
>> you. I can’t imagine you taking this position under any other scenario.
>>
>>
>> The issue here is that this is a pretty major change to the DNS.   If we
>> really want something this heavy, we should have a good reason for wanting
>> it.   That's all.
>>
>> The idea that some unnamed DHCP server somewhere doesn't do the right
>> thing with cleaning up stale entries doesn't seem like a good enough
>> reason, particularly given that the DHCID record tags the thing as having
>> been added by the DHCP server, and considering that there are several open
>> source implementations that do automatically delete records when the lease
>> expires.
>>
>> I think it might make sense to just wait on this.  I agree that it's an
>> interesting idea for completeness, but we don't have enough operational
>> experience yet to know whether we have a problem worth solving.   With
>> respect to the DHCP use case, I'm certain we don't.
>>
>> The good news is that if we do need this, you've done a design, and we
>> also have Paul's design to look at.   So if operational experience a few
>> years down the road shows us that we have a gap here, we can move on it
>> pretty easily. I just don't see any reason to rush into it.
>>
>>
>> Ok, great. Hopefully others have some use cases they can share. In the
>> mean time, back to learning Rust…
>>
>> Thanks,
>> Tom
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>>