Re: [Idr] Query on draft-ietf-idr-bgp4-mibv2-15

Nick Hilliard <nick@foobar.org> Mon, 20 November 2017 15:38 UTC

Return-Path: <nick@foobar.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C92129BD8 for <idr@ietfa.amsl.com>; Mon, 20 Nov 2017 07:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 y_LfYdVEKCKu for <idr@ietfa.amsl.com>; Mon, 20 Nov 2017 07:38:43 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD637129B81 for <idr@ietf.org>; Mon, 20 Nov 2017 07:36:29 -0800 (PST)
X-Envelope-To: idr@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vAKEa9a1094492 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Nov 2017 14:36:10 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <5A12F675.2030106@foobar.org>
Date: Mon, 20 Nov 2017 15:36:21 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.20 (Macintosh/20171012)
MIME-Version: 1.0
To: "Acee Lindem (acee)" <acee@cisco.com>
CC: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>, "idr@ietf.org" <idr@ietf.org>
References: <CAKz0y8yesGQrmmLNm4rJL_=W53tr-Kp2OpgqR_q9qkp3rPa2gQ@mail.gmail.com> <D6385A04.DA762%acee@cisco.com>
In-Reply-To: <D6385A04.DA762%acee@cisco.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/znTFoIowuJ56h6toAdsF8-LYyAk>
Subject: Re: [Idr] Query on draft-ietf-idr-bgp4-mibv2-15
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 15:38:47 -0000

Acee Lindem (acee) wrote:
> The IETF has moved on from SNMP-based management to YANG, refer to this
> IESG statement:
> 
> https://www.ietf.org/iesg/statement/writable-mib-module.html

the rest of the world is going to take many years to catch up with this
decision - usable YANG is only beginning to make its way into a small
segment of high-end kit out there, and there is a large segment of
market kit where it is likely never to be deployed.

In the meantime - in this particular situation - we have no means of
monitoring ipv6 or vrf-enabled bgp sessions, other than screen-scraping.
 It shouldn't need pointing out that this is a deficit with serious
operational consequences.

Nick