IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Fri, 24 August 2018 18:05 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 0A97B130E03 for <dnsop@ietfa.amsl.com>; Fri, 24 Aug 2018 11:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 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] 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 kVtCQU6nbGYg for <dnsop@ietfa.amsl.com>; Fri, 24 Aug 2018 11:05:03 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 2BF86130DD0 for <dnsop@ietf.org>; Fri, 24 Aug 2018 11:05:03 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id w11-v6so7850443iob.2 for <dnsop@ietf.org>; Fri, 24 Aug 2018 11:05:03 -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=UQs2It/dTPIlufWNH+UpNAC9+T7RE59yuG4puWusB50=; b=Qa8U5P7WSSDNRiegci88c/+YLbFUZL+flGNFtiCFbpy0LRVZr/sNIELLnq9gwKjHpH HxBi9QaMMrOmNcxvROUltTGCXW5C5Hp4H00oIoqKfymWgOYKjD2F3LHTsMjjfJfASZeC Jqc5q77+yFnggdfLg/lCDVJLt+6aIjUOfNAlJDJ+35BIdCR65riTiZ8y2DwUiJUEL8ws idoW19GqhJnkQ6JE+UeGbB9B519cMCbHUJNbgErYBnAa6KkmNeA/UWtpdHIZ1FcMq07p JFrdVA5Yz+m8MxgW28MF/MkipY5hSUVToL42MQjRJTg59kYR8pbeLxYSJg6Gg+tYGoKm UZLw==
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=UQs2It/dTPIlufWNH+UpNAC9+T7RE59yuG4puWusB50=; b=XA6gHMqL83BqDbV8zDRAF/i4bWVhWYRg2tO3/hdNH7RwyDQjA3tDyPZSJkArYlSzfK NKiRPx8ApP8/M5wXW3GtsaASd+huzpqHeqsnCIq8pAWwMA70XmsRCNmObxsJCdttkaiB ApD+7+TfDc1Ei3D1RrQlrDbNIaDFSTitYYNn8yfhtuKqlBBEWWmMdEvB0oGlEpFZunQq lSsEqPn/3i6RPhLtJUb+IcgWcClFxzgZeOKaa10V8GCMf+mt8bHdS86rFVwK/NNirPld fj+puwRXNmbPVC5Sqe1veM0/LbKeSA6KKkCLF+8rv7hppKHJZogUhodhDkZPfcpVRdxD UpDQ==
X-Gm-Message-State: APzg51Bksd4uRa1Yb2rvG2XeegsmjiJgHQmDs+hqOwBfenQhEuKCmdEW XiwzyJ74i2KMbIA6YeObyJ4xrj/t8kZNAxSeg8yYXnux
X-Google-Smtp-Source: ANB0Vdb9Mq7Mj1dBp8QpA15tXz4KihC+uxxrQeDXXgcz4lQlj89Fa5iorrOElC5zKR+W3Jkq939jVnF+DO6+zFoAeUM=
X-Received: by 2002:a6b:dd01:: with SMTP id f1-v6mr2094828ioc.45.1535133902319; Fri, 24 Aug 2018 11:05:02 -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>
In-Reply-To: <98EF2CAC-7C13-4E68-8D2B-EC0659EA9646@bangj.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 24 Aug 2018 14:04:26 -0400
Message-ID: <CAPt1N1kFNY4=CUMsTvXmeRREeLAkY8xpBdw4vPDxujgke6QT8A@mail.gmail.com>
To: Tom Pusateri <pusateri@bangj.com>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ee540405743236bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CXEADvxIwMbqji9VGtc7Kzvmn_g>
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: Fri, 24 Aug 2018 18:05:05 -0000

Can you give us an example?

On Fri, Aug 24, 2018 at 1:56 PM Tom Pusateri <pusateri@bangj.com> wrote:

> Sure. It’s not the thoughtful, well-behaved implementations that we worry
> about. It’s the ones that aren’t. This is a protection mechanism. (Belt AND
> suspenders..)
>
> Thanks,
> Tom
>
>
> On Aug 24, 2018, at 1:36 PM, Ted Lemon <mellon@fugue.com> wrote:
>
> The DHCP case isn't actually a problem today.   DHCP servers automatically
> remove these records.   The ISC server has been doing this for 20 years,
> and I'm pretty sure all the other servers that compete with it do too.
>
> On Fri, Aug 24, 2018 at 12:50 PM, Tom Pusateri <pusateri@bangj.com> wrote:
>
>>
>>
>> On Aug 24, 2018, at 9:54 AM, Ted Lemon <mellon@fugue.com> wrote:
>>
>> On Aug 24, 2018, at 9:52 AM, Tom Pusateri <pusateri@bangj.com> wrote:
>>
>> Yes, it was intended to be more general than for service registration.
>> It’s directly applicable to name registration for IP addresses. I can add a
>> section on other uses if more motivation is desired. Mark Andrews had some
>> uses as well that hopefully, he can share. If others have uses in mind that
>> this solves I would love to hear about them.
>>
>>
>> The reason I'm asking is not that I don't think there are theoretical use
>> cases for what you are proposing.   I'm asking if there are actual use
>> cases.   How would this be used in practice?   What can't someone do right
>> now that they need to do and that this new technology enables?
>>
>>
>> Specifically, there are two applications mentioned in the draft.
>>
>> 1. When a DNS server receives a dynamic DNS Update from a client
>> registering its name after having received an IP address from an DHCP
>> lease, the length of the DHCP lease can be tied to the length that the DNS
>> address/PTR records stay in the authoritative server.
>>
>> 2. When an RFC 6763 DNS-SD service is registered (including PTR, SRV, &
>> TXT records), these records can timeout according to the lease lifetime
>> contained in the update lease EDNS(0) option.
>>
>> These are not theoretical. They solve practical problems that exist
>> today. I think there are others associated with existing problems for
>> sleeping devices and IoT devices that I need to research to more clearly
>> answer your specific question but I think these two already fulfill that
>> requirement.
>>
>> Tom
>>
>>
>>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
>

v2.23.0 | Report a Bug | By Email