[DNSOP] draft-hardaker-dnsop-private-namespace-options

Wes Hardaker <wjhns1@hardakers.net> Mon, 02 November 2020 22:50 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 983C43A1266 for <dnsop@ietfa.amsl.com>; Mon, 2 Nov 2020 14:50:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KTXbN2AfboX3 for <dnsop@ietfa.amsl.com>; Mon, 2 Nov 2020 14:50:50 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 240603A09B7 for <dnsop@ietf.org>; Mon, 2 Nov 2020 14:50:49 -0800 (PST)
Received: from localhost (unknown []) by mail.hardakers.net (Postfix) with ESMTPA id 9E63721A7A for <dnsop@ietf.org>; Mon, 2 Nov 2020 14:50:47 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: dnsop@ietf.org
Date: Mon, 02 Nov 2020 14:50:47 -0800
Message-ID: <yblsg9r8jaw.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3oIaNuD6WFRE6Jj3TjSV8KSqVIY>
Subject: [DNSOP] draft-hardaker-dnsop-private-namespace-options
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 02 Nov 2020 22:50:52 -0000

I've been thinking for a while what approach to take with respect to
private name spaces.  This document summarizes some of my thinking, and
draws some conclusions (that will likely poke some bears and beehives at
the same time).


A new version of I-D, draft-hardaker-dnsop-private-namespace-options-00.txt
has been successfully submitted by Wes Hardaker and posted to the
IETF repository.

Name:		draft-hardaker-dnsop-private-namespace-options
Revision:	00
Title:		DNS Private Namespace Options
Document date:	2020-11-02
Group:		Individual Submission
Pages:		9
URL:            https://www.ietf.org/archive/id/draft-hardaker-dnsop-private-namespace-options-00.txt
Status:         https://datatracker.ietf.org/doc/draft-hardaker-dnsop-private-namespace-options/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-hardaker-dnsop-private-namespace-options
Htmlized:       https://tools.ietf.org/html/draft-hardaker-dnsop-private-namespace-options-00

   This document discusses the trade-offs between various options about
   creating a private namespace within top level domains within the root


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

Wes Hardaker