IETF Logo Mail Archive

Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps

Randy Bush <randy@psg.com> Tue, 04 July 2017 14:03 UTC

Return-Path: <randy@psg.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 80E5912EB21; Tue, 4 Jul 2017 07:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 g6yEsN2BvBSD; Tue, 4 Jul 2017 07:03:38 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 3A5A0129459; Tue, 4 Jul 2017 07:03:38 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSOQS-0000mg-Ib; Tue, 04 Jul 2017 14:03:36 +0000
Date: Tue, 04 Jul 2017 16:03:35 +0200
Message-ID: <m2o9t0xps8.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
In-Reply-To: <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-8859-7"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SmiXUfLi86yUM9tyU27x1yp9HR8>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
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: Tue, 04 Jul 2017 14:03:39 -0000

>> i would offer to put my keyboard where my mouth is.  but i fear that,
>> at the bottom, i would have the unreasonable desire for dns classes
>> to support these kinds of things.  i.e. i don't think we have a clean
>> fix.  but it would be nice to document the good with the bad.
> 
> That sounds like a solution, not a motivation. That is, you care about
> the problem hypothetically, and have a hypothetical solution. In
> practice when we’ve talked about using dns classes to solve problems
> that have motivated rfc6761 allocations, it hasn’t really helped,
> because the infrastructure required to use them this way is not
> present, and this isn’t how they were originally intended to be used.
> 
> For example, is ICANN.org with a different class not a subdomain of
> the .org TLD? Would ICANN not object to us designating it for use by
> someone else?  I suspect yes, and I wouldn’t blame them.

sorry.  maybe it would have helped if i had put UNREASONABLE DESIRE in
upper case.

randy

v2.23.0 | Report a Bug | By Email