IETF Logo Mail Archive

Re: [DNSOP] Some thoughts on special-use names, from an application standpoint

Tim Wicinski <tjw.ietf@gmail.com> Sat, 28 November 2015 09:58 UTC

Return-Path: <tjw.ietf@gmail.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 EDDE41A8AC7 for <dnsop@ietfa.amsl.com>; Sat, 28 Nov 2015 01:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 yGg199R6-ZEV for <dnsop@ietfa.amsl.com>; Sat, 28 Nov 2015 01:58:54 -0800 (PST)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (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 2A53C1A88C8 for <dnsop@ietf.org>; Sat, 28 Nov 2015 01:58:54 -0800 (PST)
Received: by igcmv3 with SMTP id mv3so43436370igc.0 for <dnsop@ietf.org>; Sat, 28 Nov 2015 01:58:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=ZHpkgmklqqExiJXYqAnWPlBGspNFVFSWbIzVBWn9tfg=; b=O9wz8zW1UY4/Gd1NX57shR16fS6Ezt4hJp1CabVqj90Ozhs/Dh3PffEBLu3I8b3MYi fIv2uRQoTiEN+OQEiAv+sC8NMXy8RFuKZhf5oYsrFJSFCNdyQSNc1i1cqnuphryn3+F+ 4ujJMAbHBD4Y0onunyAk+faqw68rh1HCQk6u9xSG81TJr3YksIAN44nK8pjWtlDLzqBK 3ycD3n/84s9KGbe06ZpP2Dm39gLn/kPFIsdfydESPtNK1IBY35UVyKj69AEwr5povEPP bouTLpguNC5DELUSE7rlQ2EBPqzGvjK50IhWqCBCKDLkgLTz7oAoqJZEEWbOCHqxKQEy +5kg==
X-Received: by 10.50.78.231 with SMTP id e7mr12348625igx.93.1448704733538; Sat, 28 Nov 2015 01:58:53 -0800 (PST)
Received: from still.local ([184.13.114.26]) by smtp.googlemail.com with ESMTPSA id rj10sm4554701igc.20.2015.11.28.01.58.52 for <dnsop@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 28 Nov 2015 01:58:52 -0800 (PST)
To: dnsop@ietf.org
References: <7E4C1956-8477-4F07-BC29-3D163B7160AA@mnot.net> <5656F43D.9060401@gnu.org>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <56597ADC.4090404@gmail.com>
Date: Sat, 28 Nov 2015 04:58:52 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:44.0) Gecko/20100101 Thunderbird/44.0a2
MIME-Version: 1.0
In-Reply-To: <5656F43D.9060401@gnu.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/JA6V-6-XmTtj-nFEt23POPc4bJc>
Subject: Re: [DNSOP] Some thoughts on special-use names, from an application standpoint
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: <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: Sat, 28 Nov 2015 09:58:56 -0000

I'm not the WG Chair who is handling the day-to-day responsibilities (I 
just do all the other boring DNS stuff), but I do know this:

- design team is being put together but was not complete
- Ralph Droms (AD for 6761) is the head of the design team
- they are still looking for 1-2 people with experience in the 
application area

My co-chair has family obligations this weekend but I suspect we will 
hear next week from her or Ralph.

tim

On 11/26/15 6:59 AM, hellekin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 11/26/2015 06:38 AM, Mark Nottingham wrote:
>>
>> Given this context, I was disturbed to hear the design team presentati
> on
>> in Yokohama
>>
>
> So you mean there's an already working team on the revision of RFC6761,
> and that team had the time to prepare a presentation, while the DNSOP
> chairs didn't have the time to respond to volunteers nor to announce
> this team.  This is simply unacceptable.  I concur that the revision of
> RFC6761 should go to another group where "Internet community" makes some
> sense and corporate dissent is not silenced by ignoring legitimate
> requests.  Please don't expect any apologies from me for telling the
> truth.  This is a carnival of an inclusive process.
>
> Thank you Mark for the heads up.
>
> ==
> hk
>
> -----BEGIN PGP SIGNATURE-----
>
> iQJ8BAEBCgBmBQJWVvQ8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0
> ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9ewoQALD1dF/Wqyh2Lo5qZ35PUANA
> bvq2k5BZd1UsN488+V4v7PnAHxO7XgR8IQSYYnp1oYNaZl5WbFEPjT6HOSR3O4lr
> 7iSVeSxPux8hssSxorkWtBVk8oAnImGEPyIlYunBLcTyasXLY5+2fzmR1+P4/9Kk
> ahjHvuQa6dOAXhqTMBizwb3kZ2PC2hFlM5LKMIBcf9GfTVmH//fbEalHYPYEwMCY
> AvX9mkMvvWcWhn15OXRi50r3kQl65d0KQA2euQ8mUIe5qafDHASBtZLc81t0rAXv
> fjaWT4REu+KUHexWKgI7NFF3uZ0M0Cm7imYN6+YG+AWFtPrr4SPh1BA0L4td93q8
> bGxGEJrDTWRVaW2c98UO5bFxm3kqcM4oTdBD1Rg4yC1OatvuKzZp6nPrFG09G5rn
> PjorrqoNx0MHxwejrTHkkhnmvmgTfPUTvkT/7zUYLTwRITDrjzOyj932COrZV+A3
> dak5M5hRLhR8jswx/lh+SmY1RFAtCuNDcoFuXTOJygwSpj7WvigIORiT6ATLFlfW
> mxYxkVP/Tc76anRTk5O/AIu87c5K9fr6TPiFRIL/0eKnFBEMn2qbaW7TLvAl6o89
> kgYYp4u59ve0vCL6gE2sn1w1EYnctFVxpzcg9HkFl/MFuQyWdc4yb5OdFWW8sema
> 8hpTT/KiW1/KDHGj0kcB
> =IZoh
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

v2.29.0 | Report a Bug | By Email | System Status