[DNSOP] clarification on DNSOP charter Re: [dns-operations] dnsop-any-notimp violates the DNS standards

Suzanne Woolf <suzworldwide@gmail.com> Mon, 09 March 2015 17:07 UTC

Return-Path: <suzworldwide@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 D32B31A8AC1 for <dnsop@ietfa.amsl.com>; Mon, 9 Mar 2015 10:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 WU6vlSFFKOQq for <dnsop@ietfa.amsl.com>; Mon, 9 Mar 2015 10:07:38 -0700 (PDT)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (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 E8F0A1A8BC3 for <dnsop@ietf.org>; Mon, 9 Mar 2015 10:07:37 -0700 (PDT)
Received: by qgea108 with SMTP id a108so29985904qge.8 for <dnsop@ietf.org>; Mon, 09 Mar 2015 10:07:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=WmUn3hkimJMJki4y6M784L/3PhyR3K79qee80PYI5pg=; b=BqODFV3+YWSmzFZIpStrJScp0RqtcLH3esBFbWyurxkMT4RwxJHpmgN0D114bn3zBg s/EWBFy1TexdYB147TN2Q9jxeQuKoNRCvPQYCc1WFwOCAc0YGCqu3HhlEe06is6Sq5uk QeaoZXYmn20Md2PF7ioZnGokm8oKYHo2zzDPCafHbvi3BabRB8qpBAhfL9yBHs7WBU35 k4+neO1VAHVwmDInKfnn2rQzquaC8tN5Zbhsd7apKfASwGmVg0yxJeiGwiv8MrSoCo4a c8IxZ/UvlkCz0FsoT0CXpe67G6GDuFZr09kUuOULpdYtPa6GdCYk5i//pCK8SIAlQsmN Ez2Q==
X-Received: by 10.140.51.107 with SMTP id t98mr34954398qga.63.1425920857202; Mon, 09 Mar 2015 10:07:37 -0700 (PDT)
Received: from ?IPv6:2601:6:3a80:77e:8421:1590:c959:863b? ([2601:6:3a80:77e:8421:1590:c959:863b]) by mx.google.com with ESMTPSA id 8sm11896887qhr.32.2015.03.09.10.07.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Mar 2015 10:07:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_52BD8E63-3D84-44E0-9A64-A4ABBCF619BC"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20150309110803.4516.qmail@cr.yp.to>
Date: Mon, 9 Mar 2015 13:07:33 -0400
Message-Id: <9D1319E1-8446-41DE-BB70-ED6734F86F8F@gmail.com>
References: <20150309110803.4516.qmail@cr.yp.to>
To: "DNSOP WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/MOFBFQAaZ2iZUDje3zWNBRn9xKQ>
Cc: joel jaeggli <joelja@bogus.com>, "dnsop-chairs@tools.ietf.org" <dnsop-chairs@tools.ietf.org>
Subject: [DNSOP] clarification on DNSOP charter Re: [dns-operations] dnsop-any-notimp violates the DNS standards
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: <http://www.ietf.org/mail-archive/web/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, 09 Mar 2015 17:07:43 -0000

Hi,

(chair hat on)

To the question of what's on charter for DNSOP:

On Mar 9, 2015, at 7:08 AM, D. J. Bernstein <djb@cr.yp.to> wrote:

> My understanding is that dnsop@ietf.org is not chartered to make DNS
> protocol changes, so any discussion here will have to be repeated in an
> appropriate working group

From our charter as approved (http://datatracker.ietf.org/wg/dnsop/charter/):

"4. Publish documents to address operational issues with the DNS
protocols by extending or performing protocol maintenance 
on them. Act as focal-point for operator discussion and provide 
advice to the Ops ADs and other WGs on EDNS0 options, new 
RRTYPEs, DNSSEC, record synthesis, or other mechanics of 
extending DNS to support other applications.

5. Serve as a home for drafts that document the problem space 
around existing or new DNS issues. The group, with the advice 
and consent of the responsible AD in coordination with other areas, 
will then decide whether these issues belong in DNSOP under 
the existing charter and, if not, will work with the authors and 
appropriate ADs to determine the proper place for the work to be 
carried out. "

It seems to your chairs at least that discussion is in scope for DNSOP, in that we can decide any of: 

a) there's no work here, per open discussion in the WG with operators and implementers;

b) there's work here, per open discussion, and it's within item 4 above, so we can do it in DNSOP;

c) there's work here but it needs to go to another WG, in accordance with item 5, perhaps one to be spun up for the purpose, as was done with DPRIVE

At the very least, the draft seems to have generated some interest, and we're happy to host this initial discussion in DNSOP as an initial step in order to decide whether/how to proceed.


thanks,
Suzanne & Tim