IETF Logo Mail Archive

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

tjw ietf <tjw.ietf@gmail.com> Tue, 20 December 2016 15:17 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 5F1061299E9 for <dnsop@ietfa.amsl.com>; Tue, 20 Dec 2016 07:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 x0pDba99Hpuq for <dnsop@ietfa.amsl.com>; Tue, 20 Dec 2016 07:17:00 -0800 (PST)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 E52F7129A3A for <dnsop@ietf.org>; Tue, 20 Dec 2016 07:16:59 -0800 (PST)
Received: by mail-io0-x22c.google.com with SMTP id d9so181550040ioe.0 for <dnsop@ietf.org>; Tue, 20 Dec 2016 07:16:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=dfT6mG3GtsSWp0S21cBc+K5qY35lI4pH0pou4IxB3Ak=; b=h3XKgmpr0EJ8fzvoivDclpusiqW3G/ZJEk7JlF4QD+H6fJQ2dRzC/W7MF3d6IJrALr fEDAb/oYZQzglwMVF2ecKE0FkfN83mZ9vga6NxF5F4TEJUFXAC9EzQVbddlXgZ/DM3a1 m+7RxBBWgwzJLKz9VcSOVw7fmIehozVa40s/Qeu/jz0qQ3PfvcEqPwu/zTfd4mapa4Qf wK8qCGBeUdl61jvXf/EZo1cyd0r7Pw8nQ2Tiow91EeYet1/skRHEH4tlfsCnCLEGKR1p qCafsWJ3L3kypo0OHabL9S9H1fpeTrHN78+YtTyfAS/CE0uemeMvg4FV7d9n503jpuyw cIDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dfT6mG3GtsSWp0S21cBc+K5qY35lI4pH0pou4IxB3Ak=; b=I81nrwdnDRTzpQPV3lJZ/bh5JkSr1KPCb/vbUMCKajhYoFMQy4uoznYJ3KTrKLgRmx OjYqc7eZ3wirWZ5G43EdAhSZn197lHK9R20q745BeGyaUI+0DObl9TqqDwsoVfpkrtxQ NW+XSkDQC0torCt4LH0c20hwXF+1Y6joHtlmIOZ2M+1bxaBur79L7jkjVr8yN5qxYS1d RlPPsQHAtHFmWXV3AXk2FOCh64231zaugnP/PjJNZMrx9qhH+vJvwz8Si3zCshxgIEKi 6HmrhR70XlNgqsgCHXTrzS3MW0S1eZt3vb1zMFsitVz3QxdQLFE/DJ5kFekMOJgx6Ikq X/lQ==
X-Gm-Message-State: AIkVDXIbOHzObiXkoSy0ej/wzX7Kjz92PvKngtldaD4eWP8+M6NtaEkwM7szOh9hK9nCZFLQQQxKBPxpR3Z64Q==
X-Received: by 10.107.174.88 with SMTP id x85mr459850ioe.125.1482247018871; Tue, 20 Dec 2016 07:16:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.163.19 with HTTP; Tue, 20 Dec 2016 07:16:58 -0800 (PST)
From: tjw ietf <tjw.ietf@gmail.com>
Date: Tue, 20 Dec 2016 10:16:58 -0500
Message-ID: <CADyWQ+ETSd199ok0fgh=PB=--hW7buPgSoCg22aK51Bk4xxBmw@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114468dc0782c7054418877a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ekhWA_ADPauAVaTS_Xey8o32Clk>
Subject: [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: Tue, 20 Dec 2016 15:17:01 -0000

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

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