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

Ted Lemon <mellon@fugue.com> Fri, 24 August 2018 13:55 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 335AE126BED for <dnsop@ietfa.amsl.com>; Fri, 24 Aug 2018 06:55:04 -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 ts57wLWBiuxM for <dnsop@ietfa.amsl.com>; Fri, 24 Aug 2018 06:55:01 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (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 5DCEB124BE5 for <dnsop@ietf.org>; Fri, 24 Aug 2018 06:55:01 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id x7-v6so10197620qtk.5 for <dnsop@ietf.org>; Fri, 24 Aug 2018 06:55:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=S3RL96jccFJc/GmG25OGgA1NvvPJfDYK6BYKqUjBUtc=; b=iy9taEHbrovmn6z26YQYTv73T1IL9UOeyrjWPpFBHVyrUM2+zPmSG7Z7hpb6YT15mC puhLyDBDKz0tKrWOe4X1i/SL771cFIpDQlqLTAZjVLHS1HpFAFfc3AppxMHidTIlrZlj xfQRhFNMg9mHhWk6HM3rLKKQ5AS/kBNN+N0d1sXwnsN2Q53MMWpQDU4qc3pii42my4Q6 yuPIs7wagfAhGc+N5SQik+9dLRCFMnf6DAGufhNWIePr3LnBa2PsRbr5kYFgxwxVKwqV uCGmO26P3nwc3eD8j6WrlBl/bBYq7HtQIzsqKpOClIoft5I9zNvZmpnAvHQscdmlgiF0 vNmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=S3RL96jccFJc/GmG25OGgA1NvvPJfDYK6BYKqUjBUtc=; b=l+GTaTGbm7mP5qdufPPuNlFIPm5XcvDr/bGYkbohIwWTBEli4clkz2aNq6izJIXW4g KkuaKl/jxI2F0YpBW4Gw+5h/ZJ07mDPyMBozo+gDVr1vT1kibG+udeQiSDxNoJdstI0a DQE4W1nVW62XQLLwpg8H0/Tb4WiNCzcJzUcT8t0SEURlgFdrVeu+8Rs1jUvPrO3Pnf6u yGdKoVSwi+ca2lyvFpXXB2TSymKo7JvrkR94obW+GeMAPR3hhSq7nmL6glg3C/jD2tRW pak6M6hYFpJOX9b+MEwiUP4i7i2clCyD4ED2lpl73aaKFPHHl30OuUZfwB6EJJ6YGrX7 pUJg==
X-Gm-Message-State: APzg51CCsB2YWLA+/oEQPm7fwtFiZY1cL7imbJhYp6xzXFFadD47ZSsJ rRPDRIyaFdVAqGAg/xkF6JaW9K3TARs=
X-Google-Smtp-Source: ANB0Vdaqom6BpxHs6eLcSAXquDuvb8uHPqapxqd0tAf566FJy11J0LXMyYNHpruwBhHMvWKKfJWF1A==
X-Received: by 2002:a0c:93ac:: with SMTP id f41-v6mr1788149qvf.151.1535118900480; Fri, 24 Aug 2018 06:55:00 -0700 (PDT)
Received: from [10.0.100.12] (c-73-167-89-221.hsd1.nh.comcast.net. [73.167.89.221]) by smtp.gmail.com with ESMTPSA id g37-v6sm5071703qte.36.2018.08.24.06.54.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Aug 2018 06:54:59 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <3C6100BD-62D6-41ED-B7BF-679F0D4E4113@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_59ACC783-57C5-4F44-AB43-8F58A3709EDC"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.38\))
Date: Fri, 24 Aug 2018 09:54:58 -0400
In-Reply-To: <6D607922-393D-4549-AAFA-49279C260CA4@bangj.com>
Cc: Paul Vixie <paul@redbarn.org>, dnsop WG <dnsop@ietf.org>, Tim Wattenberg <mail@timwattenberg.de>
To: Tom Pusateri <pusateri@bangj.com>
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>
X-Mailer: Apple Mail (2.3445.100.38)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6KgBDy3XIdDhVnygOUX22Mkh628>
Subject: Re: [DNSOP] Fwd: 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 13:55:04 -0000

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?