[DNSOP] Call for Contributions: Name Server Control -- Followup Work

Peter Koch <pk@DENIC.DE> Wed, 13 October 2010 20:11 UTC

Return-Path: <peter@denic.de>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69F1D3A6A07 for <dnsop@core3.amsl.com>; Wed, 13 Oct 2010 13:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.95
X-Spam-Level:
X-Spam-Status: No, score=-5.95 tagged_above=-999 required=5 tests=[AWL=0.299, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-71ucYNyFMs for <dnsop@core3.amsl.com>; Wed, 13 Oct 2010 13:11:04 -0700 (PDT)
Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 9BDFD3A6A3C for <dnsop@ietf.org>; Wed, 13 Oct 2010 13:10:49 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1P67gB-0000aY-BJ; Wed, 13 Oct 2010 22:12:03 +0200
Received: from localhost by x27.adm.denic.de with local id 1P67gB-0002jG-7v; Wed, 13 Oct 2010 22:12:03 +0200
Date: Wed, 13 Oct 2010 22:12:03 +0200
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20101013201203.GQ19236@x27.adm.denic.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: [DNSOP] Call for Contributions: Name Server Control -- Followup Work
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 13 Oct 2010 20:11:12 -0000

Dear DNSOP WG,

with draft-ietf-dnsop-name-server-management-reqs-04.txt now on its way to
the IESG, it is time to look at future efforts.  There was followup work
proposed based on this draft that we had postponed until after the requirements
document would have been finished.  Also, there was a proposal to hold a BOF in Beijing to explore potential approaches based on, but not limited to, existing 
IETF management protocol frameworks.
During the IETF79 planning, the IESG decided to assign the necessary work
to DNSOP which lead to a withdrawal of the BOF request.

Our postponement of the work was due to the desire to get the requirements
finished first.  But some approaches were ruled out of charter because:          
 o DNSOP is by definition not allowed to work on protocol (where the
   emphasis is on DNS protocol)

 o the necessary expertise isn't necessarily readily available within the
   DNSOP WG as of today

During the BOF planning there were basically two drafts available:

o draft-dickinson-dnsop-nameserver-control-00.txt (now expired),
  using NETCONF/YANG as a framework,

o draft-kong-dns-conf-auto-sync-01.txt, which suggests mapping DNS
  configuration data into the DNS itself. (It is arguable whether this is
  a modification to the DNS protocol.)

The IESG guidance to go ahead with this work within DNSOP (pending necessary
charter updates) should not be read as a preemptive decision in favor of
YANG or against any other approach.  It was suggested based on the fact
that the administrative overhead of a BOF wasn't necessary to overcome
what might only be a charter update to an existing working group.
That said, we would like to reserve 45 minutes of our 120 minute slot
in Beijing to the topic of "approaches towards a name server control protocol".

What should be achieved during that meeting (with later decision on the list)
is whether there is support for a particular approach to be addressed within
DNSOP.  We'd like to encourage everybody to read the two drafts mentioned
above and, if alternative suggestions exist, submit an individual Internet
Draft by the Beijing deadline (2010-10-18).  Only suggestions with an I-D
are eligible for agenda time and discussion.

An archive of the discussion of the followup work is available at:
<http://www.ietf.org/mail-archive/web/nscp/current/maillist.html>

Further discussion is encouraged on the DNSOP mailing list.

-Peter (for the DNSOP co-chairs)