IETF Logo Mail Archive

Re: [DNSOP] ALT-TLD and (insecure) delgations.

Suzanne Woolf <suzworldwide@gmail.com> Fri, 03 February 2017 21:01 UTC

Return-Path: <suzworldwide@gmail.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 8295F128B37 for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 13:01:22 -0800 (PST)
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=gmail.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 lTLDR7GqyP7C for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 13:01:21 -0800 (PST)
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 E122C129407 for <dnsop@ietf.org>; Fri, 3 Feb 2017 13:01:20 -0800 (PST)
Received: by mail-qt0-x22e.google.com with SMTP id v23so54222981qtb.0 for <dnsop@ietf.org>; Fri, 03 Feb 2017 13:01:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=V6PB6q2REMmPgV0ojIqp/9mG/N9JD0DN7oIueYTzeZs=; b=WNEQ7IZc9dXuRzHJt+NfMURlubq2Rgf4o2qHxFGPPLX0HcEKPIKBUgcjk4KFgXiFV1 Uh8NbUhuTHwQKkOg/PfoVyiUma8Q3gtr/qsWh0/UxYvDhBL5Lrhji7sw2K26cncVAFau 2rdn29Qpa0/qeALi8483mP5/0Gw8XElxLPLsFXOSeqb4K9FYM79Tv72KLzTZRtdZjEaf Etfj5oOIjfGfU4bkN2CBjLOxPMlHZWfYWOy75vEN3GMUbje6donaTrJ58oHFphaPI5bx nEN14xLForYJXogskYNJd9XOuW2YlwIbK6W24mMC9vHS0Lu/tYIiUrXFSPWIXkQ3984C nzgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=V6PB6q2REMmPgV0ojIqp/9mG/N9JD0DN7oIueYTzeZs=; b=jdEJHHwz29hq//BeXMhGDsFSu+nKzwTLDx+Tar0hHRNuv5LJ99ivytVHPJwW0Lz11A 8YAMI1MJeTiyCTcihsBr7ONbCEmH0PLSM9FnE0H5fZIAXonOCPFzgCgI/LDJWv+UF3X2 rJKcwmOnHCL9Zq+lAv0s9ncuKSXvYTNlBrgjmVoCIGxzCUofGAdpQJhzF+DiIex2S7QP NMKpLnWbX3eoPc4EHxjroY+FPFxO66zk74VLjsxdPrFe3De7OnqIGAzoim+K2iLaKRWN AmZVkubxi8VbxFydSROLclTRtV8egGMyn5eWBULFbR2u6je1j6uTvBezkWy8mNGosLqU 7EQQ==
X-Gm-Message-State: AMke39ln7IAcsQVocVJcyAcL30Sn4EkEhwlY2khA/T21URtPErARYcFPpNWrpnunymshYg==
X-Received: by 10.55.24.8 with SMTP id j8mr16594461qkh.181.1486155679837; Fri, 03 Feb 2017 13:01:19 -0800 (PST)
Received: from ?IPv6:2601:181:c381:c20:902c:8449:d637:4e18? ([2601:181:c381:c20:902c:8449:d637:4e18]) by smtp.gmail.com with ESMTPSA id c41sm25515013qtd.3.2017.02.03.13.01.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 03 Feb 2017 13:01:19 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20170201205656.CB3356115F8E@rock.dv.isc.org>
Date: Fri, 03 Feb 2017 16:01:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEBDFD91-F759-44DD-B19C-BDFB3B2AFF17@gmail.com>
References: <CAHw9_i+8PA3FQx8FqW-xQ_96it7k-g5UrMB7fxARUi1gwQ++hw@mail.gmail.com> <20170201205656.CB3356115F8E@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zmR0hyz4JHAaNK3Fv7Loe6Mm-co>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] ALT-TLD and (insecure) delgations.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 03 Feb 2017 21:01:22 -0000

Mark,


> On Feb 1, 2017, at 3:56 PM, Mark Andrews <marka@isc.org> wrote:
> 
> 
> In message <CAHw9_i+8PA3FQx8FqW-xQ_96it7k-g5UrMB7fxARUi1gwQ++hw@mail.gmail.com>, Warren K
> umari writes:
>> This is a fine thing to request in an IANA consideratons, but isn't
>> necessarily *useful* -- the IANA has the technical ability to add
>> stuff to the root zone, but not the mandate (this is like walking into
>> a bank and requesting the teller gives you a bunch of money - they may
>> be able to do so, but aren't actually allowed to.. :-)).
> 
> Actually it isn't the same.
> 
> Implicit in the agreement that the IETF can get names in the root
> namespace is the ability to use them.  Some uses require that there
> be a entry in the root zone.
> 
> It doesn't say that the IETF can "RESERVE" a name.  The IETF gets
> the name.

Can you suggest a citation for this belief that can be included in the problem statement draft?

It’s not a view that’s ever been discussed as far as I can recall and it seems to me that it would be difficult to get consensus on it across the affected communities. But I’m always willing to be wrong.


thanks,
Suzanne

v2.23.0 | Report a Bug | By Email