IETF Logo Mail Archive

Fwd: [netmod] [OPS-AREA] configuration: writable MIB modules versus NETCONF/YANG modules

Giles Heron <giles.heron@gmail.com> Fri, 14 February 2014 14:49 UTC

Return-Path: <giles.heron@gmail.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B7E1A0254 for <l2vpn@ietfa.amsl.com>; Fri, 14 Feb 2014 06:49:44 -0800 (PST)
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 q7KtIA7EIBjV for <l2vpn@ietfa.amsl.com>; Fri, 14 Feb 2014 06:49:41 -0800 (PST)
Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 93BBF1A025B for <l2vpn@ietf.org>; Fri, 14 Feb 2014 06:49:37 -0800 (PST)
Received: by mail-ee0-f54.google.com with SMTP id e53so5761090eek.13 for <l2vpn@ietf.org>; Fri, 14 Feb 2014 06:49:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=Ci1ocfrOMVPiX1nKqEJ8IVa91AF34tWzq/kMJnoJO+w=; b=Bv7mevXwjrQ/XIpcc5Y+rV6klzfwaBSbE39QVBlyhRCbUw8OllUnAfS9Vx6Qcu7ZNG fVk2kbI8u59JDwmddsw60D80A6GonxAW0nrG5Qja2CDRfO40xh83YjkqQ+dRBeSBVgg+ x2+P51UG77u35ZmpvxKKGi7FHhDhZEryk7jAkNCzLmrw0Dzk5WKx/AZgMlbaBjYQHRee J4kCobZIw6lNx0FhxtJfsFUg2COJrDILOxbwsUj01R5jkvEqT1mpL5z+cKFNhCvw3C5h WXic8NRgsVgH6lWjXDtmeWXcDiPdIl9nJmkCdgi1PxARrt4rqJssM4odCEKWOXxP/vPL c+Pg==
X-Received: by 10.14.110.68 with SMTP id t44mr3063973eeg.74.1392389375640; Fri, 14 Feb 2014 06:49:35 -0800 (PST)
Received: from ams3-vpn-dhcp7025.cisco.com (173-38-208-169.cisco.com. [173.38.208.169]) by mx.google.com with ESMTPSA id j41sm20581285eeg.10.2014.02.14.06.49.32 for <l2vpn@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Feb 2014 06:49:34 -0800 (PST)
From: Giles Heron <giles.heron@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D5DE569D-E4C2-49E0-A464-3D9D5C6C1D59"
Subject: Fwd: [netmod] [OPS-AREA] configuration: writable MIB modules versus NETCONF/YANG modules
Date: Fri, 14 Feb 2014 14:49:26 +0000
References: <876DDDF4-C991-4C03-81C3-81417F48FE0A@lucidvision.com>
To: "l2vpn@ietf.org" <l2vpn@ietf.org>
Message-Id: <D985BE1A-830D-4007-8069-CB9E120B9CF5@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/B7d2Icd3xy2FBgI2n2W3N7A4Mbw
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 14:49:44 -0000

Worth noting.

Giles

Begin forwarded message:

> From: Thomas Nadeau <tnadeau@lucidvision.com>
> Subject: [netmod] Fwd: [OPS-AREA] configuration: writable MIB modules versus NETCONF/YANG modules
> Date: 14 February 2014 01:41:34 GMT
> To: netmod@ietf.org
> 
> 
> 	FYI in case you are not on the ops dir list...
> 
> 	--Tom
> 
> 
> Begin forwarded message:
> 
>> From: Benoit Claise <bclaise@cisco.com>
>> Subject: [OPS-AREA] configuration: writable MIB modules versus NETCONF/YANG modules
>> Date: February 13, 2014 at 7:39:57 PM EST
>> To: "ops-area@ietf.org" <ops-area@ietf.org>
>> 
>> Dear all,
>> 
>> We occasionally see read-write MIB module proposals within the IETF.
>> However, the write capabilities of those MIB modules are rarely implemented.
>> 
>> While discussing this issue with the MIB doctors, we arrive to the conclusion that it's now time to set the direction for future MIB developments within the IETF. Basically, let's not specify read-write MIB modules unless we have a good reason. Read-only MIB modules are still fine though, as SNMP is clearly used for monitoring purposes.
>> 
>> Here is the statement we came up with:
>> The OPS area recommends the use of NETCONF/YANG standards for configuration. IETF working groups are therefore encouraged to use the NETCONF/YANG standards for configuration, specifically in new charters. SNMP MIB modules modifying persistent configuration state should only be produced by working groups in cases of clear utility 
>> and consensus to use SNMP write operations for configuration.
>> Ideally, this should become an IESG statement.
>> Your feedback is most welcome.
>> 
>> Regards, the MIB doctors & Benoit
>> 
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-area
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

v2.8.7 | Report a Bug | By Email