Writable MIB Module IESG Statement

The IESG <iesg@ietf.org> Sun, 02 March 2014 18:01 UTC

Return-Path: <iesg@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 38F931A09AC for <ietf-announce@ietfa.amsl.com>; Sun, 2 Mar 2014 10:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4hNHYsj6EcJ3 for <ietf-announce@ietfa.amsl.com>; Sun, 2 Mar 2014 10:01:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 32DD91A0221 for <ietf-announce@ietf.org>; Sun, 2 Mar 2014 10:01:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Writable MIB Module IESG Statement
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140302180143.31340.22881.idtracker@ietfa.amsl.com>
Date: Sun, 02 Mar 2014 10:01:43 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/JmZx1LHtxdEoY-ZrX6d2l2HnPjY
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Mar 2014 18:01:44 -0000

The IESG is aware of discussions in the OPS area and in a number of 
working groups about the current practice for standards-based approaches 
to configuration. The OPS area has shown strong support for the use of 
NETCONF/YANG while many working groups continue to specify MIB modules 
for this purpose. The IESG wishes to clarify this situation with this 

- IETF working groups are therefore encouraged to use the NETCONF/YANG 
  standards for configuration, especially in new charters. 

- SNMP MIB modules creating and modifying configuration state should 
  only be produced by working groups in cases of clear utility and 
  consensus to use SNMP write operations for configuration,  and in 
  consultation with the OPS ADs/MIB doctors.