IETF Logo Mail Archive

Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps

"John R Levine" <johnl@taugh.com> Tue, 26 May 2015 21:53 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE1E1A8AEC for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 14:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.263
X-Spam-Level:
X-Spam-Status: No, score=0.263 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 fEReK6ld6A2P for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 14:53:19 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2218E1A89B1 for <dnsop@ietf.org>; Tue, 26 May 2015 14:53:19 -0700 (PDT)
Received: (qmail 8552 invoked from network); 26 May 2015 21:53:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=2167.5564eb55.k1505; bh=afJj2BT2TezFVB0t9FheQVCDX9IXcyhYHfcAuvl3pZs=; b=vv3dL0DvRwxgzzNofHq00rUtMzrs0PV2dNodHCgdkhUneohvAIgfVsE7DtF6UAesMz6cmXWmaLmJM9vHCN2W4IHhEuDboGezX/2ACMHWYx54SV4lcQZt7N0nC6hUtgGYXwMc8wskyPeIuTyU55i/SbwpeOo1C7L04Gv+Y3BQYZR8Q/8Znl7XWjDdVzgvI0geACWSFRhmJz7AAT4av3YJn9Nrz/qj4kzmKGG+G15eWdaGU+SECaDqB8QGKNe4hiI7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=2167.5564eb55.k1505; bh=afJj2BT2TezFVB0t9FheQVCDX9IXcyhYHfcAuvl3pZs=; b=qiU/qrZx5RLVlvTHfj64HB6OhPg/sweErw7lXb/COqX1gF+LWY8pDkL5E0athhwgi0EPrF6W9P/TeJlls12G08iklHWwIkeTET5O+XchxYm9TQ4JwuUshAisQt436fi87wm1LFV/j2kXB4xhzoitO9egoqxzQZBp1aFAx4Bjm0qGUWHj2N34QQTI/wpr3U0qLfDG07Il/a88JrcBP+TYRFeR65xQCQbWu9yKhUnk5scbNOIKO25PG6bKPkzjc8uN
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 26 May 2015 21:53:25 -0000
Date: Tue, 26 May 2015 17:53:16 -0400
Message-ID: <alpine.OSX.2.11.1505261733270.65578@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Francisco Obispo <fobispo@uniregistry.com>
In-Reply-To: <3B05F60A-8865-45B8-A36C-042E0F5CC92C@uniregistry.com>
References: <20150526200703.15413.qmail@ary.lan> <3B05F60A-8865-45B8-A36C-042E0F5CC92C@uniregistry.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/mAwm50UcN9ngNNqJUH9osaGMo-w>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 May 2015 21:53:20 -0000

PS:

> Should we also add a .BELKIN TLD?, there are tons of devices that use it 
> (to name a few), what if in 10 years someone decides to create 
> .FOOBARBAZ are we going to add it to the list later?,

If those names were leaking as badly as the three we're talking about, 
sure.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email