IETF Logo Mail Archive

Re: [dbound] The Fate of DBOUND

Dave Crocker <dhc@dcrocker.net> Wed, 11 January 2017 16:47 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7BF7129F18 for <dbound@ietfa.amsl.com>; Wed, 11 Jan 2017 08:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 KphzFVecJ_ly for <dbound@ietfa.amsl.com>; Wed, 11 Jan 2017 08:47:03 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 007FC129F03 for <dbound@ietf.org>; Wed, 11 Jan 2017 08:47:02 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v0BGmPPI024308 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Jan 2017 08:48:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1484153305; bh=AE8vvhtkDNTQT6HOGmfhQZ2kAulLTp53svYN8d3NV9s=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=VPBlB62QgObItTL1ODQDc3Fc+iPlDK3JdcLLrAE5kG3Re7TtXxsBNKN2tUkA+6d8S wr5HPfUWvO/hk7MlXW1JnjjPUF4axMXSBlXuuFAz6K9zAE2AGSTPA5Z9Jnow2y+1mA j+x1IRVYx5V/Ln/BljvsiZ6wXg4D/GA1ZD2gzHcc=
To: Kurt Andersen <kurta@drkurt.com>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <CAL0qLwb_JzkL9x=mikNrk8z943vHgJ2qrwew7Ucrd+PbL_wRqA@mail.gmail.com> <CB3C24CC-9FB8-4F41-BC36-4773968934B0@vpnc.org> <CAL0qLwaW2umAumVjGds8mYhSQfwtLf2+Fbgdo+zOqx_9QV3urw@mail.gmail.com> <CABuGu1ovcO7EvmOOJEW9FqkTqRdp-2zoxrKn9AZbQCMtHDmSjg@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <fa5f054b-95ac-a2a5-6c91-487345b17489@dcrocker.net>
Date: Wed, 11 Jan 2017 08:46:48 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <CABuGu1ovcO7EvmOOJEW9FqkTqRdp-2zoxrKn9AZbQCMtHDmSjg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/pCg4iB0Ug7wzRYjbo75_VfVxxTQ>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "dbound@ietf.org" <dbound@ietf.org>
Subject: Re: [dbound] The Fate of DBOUND
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2017 16:47:04 -0000

On 11/16/2016 4:36 PM, Kurt Andersen wrote:
> What about publishing an experimental design spec along with the four
> drafts? That could put a framework around the entire process and perhaps
> avoid some of the challenges that SPFbis had when trying to move from
> experimental to standards track. The WG could become the manager of the
> experiment for a designated duration and responsible for collecting and
> publishing the results.


There might not be agreement about how to solve this topic (or topic/s/) 
but there seems to be agreement that it is an interesting and possibly 
important topic.  And there's been quite a bit of serious effort, here.

So marking that effort in the RFC archive makes sense to me, even if 
standards status isn't attached to any of it.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email