Re: [OPSAWG] Plans for advancing RFC7860 to full standard?
Robert Story <rstory@tislabs.com> Tue, 02 August 2016 15:17 UTC
Return-Path: <rstory@tislabs.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0347212D7BA for <opsawg@ietfa.amsl.com>; Tue, 2 Aug 2016 08:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level:
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-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 VvwCQYL8UxjY for <opsawg@ietfa.amsl.com>; Tue, 2 Aug 2016 08:17:36 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E71D12D16C for <OPSAWG@ietf.org>; Tue, 2 Aug 2016 08:17:36 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 0E65C28B0043; Tue, 2 Aug 2016 11:17:36 -0400 (EDT)
Received: from ispx.vb.futz.org (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id D1E6C1F8055; Tue, 2 Aug 2016 11:17:35 -0400 (EDT)
Date: Tue, 02 Aug 2016 11:17:31 -0400
From: Robert Story <rstory@tislabs.com>
To: Matjaz Vrecko <matjaz@mg-soft.si>
Message-ID: <20160802111731.5ec4c603@ispx.vb.futz.org>
In-Reply-To: <57A09C14.9030201@mg-soft.si>
References: <57A09C14.9030201@mg-soft.si>
Organization: Parsons
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; boundary="Sig_/fC493sJwtAmVp9h5N6lRRJ."; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/-QsTxDwqFdi9Cyx23JCHE2vtAgs>
Cc: manfred.lochter@bsi.bund.de, OPSAWG@ietf.org
Subject: Re: [OPSAWG] Plans for advancing RFC7860 to full standard?
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 15:17:43 -0000
On Tue, 02 Aug 2016 15:11:48 +0200 Matjaz wrote: MV> I would appreciate if you could be so kind and please let MV> me know if there are any plans for advancing RFC-7860 to MV> full standard level? MV> MV> I am aware that in order to advance it, IETF would need to MV> conduct interoperability tests between certain number of MV> independent implementations. So, here I would like to offer MV> MG-SOFT's (currently still in the process of adding 7860 MV> features to our SNMP stack, but it will be concluded soon) MV> SNMP implementation to participate in such interoperability MV> tests. Net-SNMP has patches to implement RFC-7860, and it will appear in the next release (5.8). We have done interoperability testing with one other vendor, and welcome others. Anyone wanting to do interoperability testing with Net-SNMP, contact me off-list and we can set something up. Robert
- Re: [OPSAWG] Plans for advancing RFC7860 to full … Robert Story
- Re: [OPSAWG] Plans for advancing RFC7860 to full … Johannes Merkle
- Re: [OPSAWG] Plans for advancing RFC7860 to full … Matjaz Vrecko
- [OPSAWG] Plans for advancing RFC7860 to full stan… Matjaz Vrecko