Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.txt

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 21 March 2018 18:58 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 7BC9212DA4D; Wed, 21 Mar 2018 11:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, 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=fastmail.fm header.b=iLu8rqSb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ej9k+kqW
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 P3noDHnm_0xr; Wed, 21 Mar 2018 11:58:50 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AD3F127201; Wed, 21 Mar 2018 11:58:50 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 1449920F5B; Wed, 21 Mar 2018 14:58:50 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 21 Mar 2018 14:58:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=8SHlieUYV/TFd3Pw6RxbtO6kqPihF XW7VJXFHDu7ock=; b=iLu8rqSb2bH5a02wgVbP8+5KxjPS4lip9pXgynn8e/evJ aGJUVzpBAfpi/eLdmhxI8s3PgRgOsZSKrppE90nlabWAqY2AQdIBlfsFRQhM7yhx 6LwdaZXUo8+dacrDgQjSNhMnC5ngHFT3QAlyqRJ0WUfOh0JJEWVtJndD+h44Oj24 0nagX29Nd2OilLit3uNsgmrFa61ArIHMfA2AIzuGW6kUvaorx72j6ageb4zoLsQK tTibADhiMowTD4/jprEPWgMmP5JL+JjgKaUTmyLWYJTQUMWlxpHCeQiSfrPhDv2T jwp9NrgcFZiHSqzfreNkNbMPZ3WiOe2Y6MmxPv8aA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=8SHlie UYV/TFd3Pw6RxbtO6kqPihFXW7VJXFHDu7ock=; b=ej9k+kqWWUS+XnpVGVk1NH Uis7PwtvbkQvzYM/8HIVM3VLBpnTGOkA1P+8pEuOJn4iirU11WMZnF0XFkw0Ulr5 6kiru+Qd9SUT7rjCsQqjIuAYAMK1OxaFidwcS42a+C861Xj7exCu2wIXfNGeYJAq bTaSFNCo64E8cbepZ7vcVGX2j14HjaEggJ7Nrr0ZoPxPAR1KgZrOyMLodFG9zuf1 ZIL8BOjx0b4GS7PrjUiv2Njxb9jX/wEuBbaoToToN2a7U2pRzuREqV91jHGpnMAU 2OFr4ShJ1899K7T+tI2gN4pN8CZQi4poomxLF+LmLeOfU1DHVFl0GOTh8nAma5Jw ==
X-ME-Sender: <xms:aquyWtQ4NH8GY97Yio55_r0kDPCIuxAJfLmLkKumwj4pNN9gKRbRCw>
Received: from [31.133.138.227] (dhcp-8ae3.meeting.ietf.org [31.133.138.227]) by mail.messagingengine.com (Postfix) with ESMTPA id C07A3240DB; Wed, 21 Mar 2018 14:58:49 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <alpine.OSX.2.21.1803211832350.10672@dhcp-8344.meeting.ietf.org>
Date: Wed, 21 Mar 2018 19:08:47 +0000
Cc: art@ietf.org, dnsop@ietf.org, "John R. Levine" <johnl@iecc.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0FDAA37-61AE-4971-B261-F0A15B2B753F@fastmail.fm>
References: <f7b85bac-b050-5003-2df0-a48b1ef2f929@dcrocker.net> <e1f41670-ada8-eaac-468c-c712b338a10b@dcrocker.net> <alpine.OSX.2.21.1803201804440.8940@dhcp-8344.meeting.ietf.org> <A7711F58-5145-49E8-9158-B2F94D0EABBF@redbarn.org> <7c168dc1-2ea7-d47e-78b7-0380e5d0aa84@dcrocker.net> <alpine.OSX.2.21.1803211104210.9553@ary.local> <5244d327-f8ea-1590-c663-1d92e0b194c4@dcrocker.net> <5AB27439.40801@redbarn.org> <72e481c6-b8f7-4c75-d187-b49b5fa9a735@dcrocker.net> <alpine.OSX.2.21.1803211832350.10672@dhcp-8344.meeting.ietf.org>
To: dcrocker@bbiw.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qLOYQ-yw8kApXfUPgPgl65359x0>
Subject: Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Mar 2018 18:58:52 -0000

Dave,

> On 21 Mar 2018, at 18:36, John R. Levine <johnl@iecc.com> wrote:
> 
>> On Wed, 21 Mar 2018, Dave Crocker wrote:
>> I prefer to take as simple an approach as possible: have a single registry control all allocations out of a name space.
> 
> It's a little late for that.  The SRV RFC was published 18 years ago.
> 
> How exactly do you plan to grandfather all of the existing SRV records if you don't use the existing registry that existing records use to select their existing names?

Possibly related to this question: what is the relationship of this draft to RFC 6335?

Thank you,
Alexey