Re: [DNSOP] DNSOP Call for Adoption draft-vixie-dns-rpz

tjw ietf <tjw.ietf@gmail.com> Thu, 09 March 2017 17:54 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32606129554 for <dnsop@ietfa.amsl.com>; Thu, 9 Mar 2017 09:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TNkDds9QmZTq for <dnsop@ietfa.amsl.com>; Thu, 9 Mar 2017 09:54:27 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 8B74D1293E3 for <dnsop@ietf.org>; Thu, 9 Mar 2017 09:54:27 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id v186so145254061wmd.0 for <dnsop@ietf.org>; Thu, 09 Mar 2017 09:54:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=m4hByyFelHwaV0LkGBrulVCx+JRvna79EoXWhbMBETw=; b=ITOaVDReAmtYYMBrXMbmHLg1qNRsKvEAsVmk5NLgJyEeHzZkDArONudRKYyan4xfxQ dY/17yhoU0xeX6ndIjhHIrPltVzla75KhZ8Iy+LHq6q3pAnRVbvkWlRpBw3VWjdUOEJf rtxZef+u+SM9O37v2+sQYDgd3N0+dkrGR5rY7M3XOy4GCpfA2vDFe9K7QTsAP36VKSpG vBd8AJA/176haw5lqUcY+BzBddIR2F4d2tsLOvcAq2zjQkTMJL/sCOMHpdcy+TvMEftC BQGBgMUu7ia/D8wyzSyTol89zOSlXjMTJCC3uhcrcvpTQu/7UwFIA9R800PSb60To9OQ aAmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=m4hByyFelHwaV0LkGBrulVCx+JRvna79EoXWhbMBETw=; b=CwWHPQtiKnFQa1cQElSNPVwgX0b71NHep7SUFfYHd9WQ9UzknkHtCI6AQNE4VnGb/u xwgLtGvq2jVaLaGyYMvoKJgjVlyPa9hDe6N5K+MDaw1x1B47h4xmITAoCEwfVfBZdxVu WR0JsiHQLeRshGk3f9up3DJIt423MF5ABuIHPUQCNWn9HTBUww0U0kztoNd9PO8taBai 3Vr+ssvcAhVXjJTXHiwR/yMRrBCCwPEWvV6O/USHIoPe+MnQoLROS0spBI+Uy0/9Yu87 B9yICU8aDf6TVNH5peVwnsfdROAF0wM8l6vO6WFClT7SQ6R/kZ9mBuyKMhWmWpKCxcz1 QgAQ==
X-Gm-Message-State: AMke39lO4iIv0aMuuyzO1JWH0RDY+oYpHg/V2dXLbKBnEvy3d7039acS1PgDNr9nNBT3+c74MIG2OQuyOUKzkg==
X-Received: by 10.28.12.13 with SMTP id 13mr10994333wmm.10.1489082065890; Thu, 09 Mar 2017 09:54:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.178.87 with HTTP; Thu, 9 Mar 2017 09:54:25 -0800 (PST)
In-Reply-To: <CADyWQ+ETSd199ok0fgh=PB=--hW7buPgSoCg22aK51Bk4xxBmw@mail.gmail.com>
References: <CADyWQ+ETSd199ok0fgh=PB=--hW7buPgSoCg22aK51Bk4xxBmw@mail.gmail.com>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Thu, 9 Mar 2017 12:54:25 -0500
Message-ID: <CADyWQ+GUDg2iA+MQ9xjNLDVvRgnd9PD=pLBNNvp0xK3UZVSqTA@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=001a114449f4944c2c054a4fef2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Zobqd61WHxPkU4hbXyLCRoaxUeQ>
Subject: Re: [DNSOP] DNSOP Call for Adoption draft-vixie-dns-rpz
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 09 Mar 2017 17:54:29 -0000

All

The Call for Adoption on draft-vixie-dns-rpz ended some time ago, and the
results were a solid in favor of adoption.  However, the legitmacy of the
argument in opposition to adopting seems fairly significant about certain
parts of the draft.

In discussing this with our AD, the opinion is that if this same
opposition  manifests in the IETF last call there would have
reservations about advancing it.

So if we consider this rough consensus for  the purposes of adoption
it means we believe we will be better off with an improved, working-
group-owned document then this one.

We’re going to go ahead and adopt it for DNSOP, with the intention of
resolving the concerns people expressed by keeping the status as
informational (not standards track) and making sure the cautions and
limitations the WG discussed on the use of RPZ are clear in the document.

thanks
tim
suzanne


On Tue, Dec 20, 2016 at 10:16 AM, tjw ietf <tjw.ietf@gmail.com> wrote:

> Why not just wade into this discussion...
>
> The draft is being present as "Informational", and the point here is to
> document current working behavior in the DNS (for the past several years).
>   It is obvious that some feel this draft is a large mistake, but like
> edns-client-subnet, more operators are deploying this than one is aware of.
>
> This starts a Call for Adoption for draft-vixie-dns-rpz
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-vixie-dns-rpz/
>
> Please review this draft to see if you think it is suitable for adoption
> by DNSOP, and comments to the list, clearly stating your view.
>
> Please also indicate if you are willing to contribute text, review, etc.
>
> With the holiday period upon us, we'll make this a three week call for
> adoption. This call for adoption ends on 10 January 2017
>
> Thanks,
> tim wicinski
> DNSOP co-chair
>