Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps
"John R Levine" <johnl@taugh.com> Tue, 26 May 2015 21:33 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 4437F1B31C0 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 14:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.962
X-Spam-Level: *
X-Spam-Status: No, score=1.962 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_64=0.6, J_CHICKENPOX_74=0.6, 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 KmtrpJG0PrQn for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 14:33:06 -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 5B2481ACE23 for <dnsop@ietf.org>; Tue, 26 May 2015 14:33:06 -0700 (PDT)
Received: (qmail 6563 invoked from network); 26 May 2015 21:33:12 -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=19a2.5564e698.k1505; bh=2WVVmluW3ID4Smg/vy5CnWDZnPHkpqUYICIuicDcErc=; b=H+OKWZCa9e22v36RUE7G6j4wHdXbX1/s+65Yw9JyTSayi03NrxCWP1fdq1nVsAAqv9CgzTPV4Fo2hLM8891CrLxUG64f83X8GWY4Vv+uV1bkteoSCg4ixipU5IW5zkrGBlVvF3y0d+GJI2wTeA51Z+k/yYpSXMHOz/JnNH+Gsu2R7ESKfdG5dyqLxRPRP4YLeJkGzRoYkkRztp4n6wXDYAJYejv+14u45rorV3wIgZuvz0M/khxK1QJqQtv2KjjV
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=19a2.5564e698.k1505; bh=2WVVmluW3ID4Smg/vy5CnWDZnPHkpqUYICIuicDcErc=; b=nlJJBrPCyxBKWEWLia8LS8lBTDOQLuVacr/Uv992KabOotvbkqxuCgcEecksJHcRkCGoQyBw7A9M+pQfFqGf3AWxixj3bnxB+W04VRPC6VUsAjGf5to1TA4en58dmjs/G/jSA0l82ahcSTNqVD20AGh3e5Yf3rS6qjUYmXcRcZthsIVm2Yk++woe5z85h1dCpuCErxMOWSO3OGbbvMhoU9T0tBNWCgkn9e4/nAyo3k40oiwmkce2NRdbYNuEeqq7
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:33:12 -0000
Date: Tue, 26 May 2015 17:33:04 -0400
Message-ID: <alpine.OSX.2.11.1505261730060.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/VbkqvvbxwUx2W-DYyD9hUjCfX-c>
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:33:07 -0000
>> Could you clarify how it's supposed to work? > > I would certainly like to have: obispo.home, be a real FQDN, so I can name my home devices, printer.obispo.home, etc. Ah, you expect the thousands of people with printer.home all to change the domain names they use. Could you explain, preferably in detail, how you plan to do that? R's, John
- [DNSOP] followup and proposed actions: RFC 6761 i… Suzanne Woolf
- Re: [DNSOP] followup and proposed actions: RFC 67… Tom Ritter
- Re: [DNSOP] followup and proposed actions: RFC 67… Warren Kumari
- Re: [DNSOP] followup and proposed actions: RFC 67… Daniel Kahn Gillmor
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Tom Ritter
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Wouters
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Wouters
- [DNSOP] dotless names (was Re: followup and propo… David Conrad
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] dotless names (was Re: followup and p… Paul Vixie
- Re: [DNSOP] dotless names (was Re: followup and p… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Jim Reid
- Re: [DNSOP] dotless names (was Re: followup and p… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Patrik Fältström
- Re: [DNSOP] followup and proposed actions: RFC 67… Suzanne Woolf
- Re: [DNSOP] followup and proposed actions: RFC 67… Bob Harold
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… Andrew Sullivan