[nmrg] Fw: Informational RFC to be: draft-irtf-nmrg-snmp-measure-05.txt

"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Tue, 02 September 2008 20:31 UTC

Received: from relay.versatel.net (relay.versatel.net [62.250.3.110]) by bierator.ibr.cs.tu-bs.de (8.13.4/8.13.4/Debian-3sarge3) with SMTP id m82KVjGh027707 for <nmrg@ibr.cs.tu-bs.de>; Tue, 2 Sep 2008 22:31:51 +0200
Received: (qmail 25176 invoked from network); 2 Sep 2008 20:31:45 -0000
Received: from unknown (HELO BertLaptop) (87.215.199.34) by relay.versatel.net with SMTP; 2 Sep 2008 20:31:45 -0000
Message-ID: <A89A2CE9344C429E9DFC3ED552B5862E@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: NMRG <nmrg@ibr.cs.tu-bs.de>
Date: Tue, 02 Sep 2008 22:31:03 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
X-IBRFilter-SpamReport: 0.001 () BAYES_50
X-Scanned-By: MIMEDefang 2.51 on 134.169.34.9
Subject: [nmrg] Fw: Informational RFC to be: draft-irtf-nmrg-snmp-measure-05.txt
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://mail.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <http://mail.ibr.cs.tu-bs.de/pipermail/nmrg>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Subscribe: <https://mail.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2008 20:31:55 -0000

FYI

Bert Wijnen
document shepherd

----- Original Message ----- 
From: "The IESG" <iesg-secretary@ietf.org>
To: "RFC Editor" <rfc-editor@rfc-editor.org>
Cc: <iana@iana.org>; "The IESG" <iesg@ietf.org>; <ietf-announce@ietf.org>
Sent: Tuesday, September 02, 2008 8:22 PM
Subject: Re: Informational RFC to be: draft-irtf-nmrg-snmp-measure-05.txt


> The IESG has no problem with the publication of 'SNMP Traffic
> Measurements and Trace Exchange Formats'
> <draft-irtf-nmrg-snmp-measure-05.txt> as an Informational RFC.
>
> The IESG would also like the RFC-Editor to review the comments in the
> datatracker
> (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14654&rfc_flag=0)
> related to this document and determine whether or not they merit
> incorporation into the document. Comments may exist in both the ballot
> and the comment log.
>
> The IESG contact person is Dan Romascanu.
>
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-irtf-nmrg-snmp-measure-05.txt
>
>
> The process for such documents is described at 
> http://www.rfc-editor.org/indsubs.html.
>
> Thank you,
>
> The IESG Secretary
>
> Technical Summary
>
>   The Simple Network Management Protocol (SNMP) is widely deployed to
>   monitor, control and (sometimes also) configure network elements.
>   Even though the SNMP technology is well documented, it remains
>   relatively unclear how SNMP is used in practice and what typical SNMP
>   usage patterns are.
>
>   This document proposes to carry out large scale SNMP traffic
>   measurements in order to develop a better understanding how SNMP is
>   used in real world production networks.  It describes the motivation,
>   the measurement approach, and the tools and data formats needed to
>   carry out such a study.
>
>
> Working Group Summary
>
>   This document was produced within the IRTF's Network Management
>   Research Group (NMRG) and represents the consensus of all of the
>   active contributors to this group.
>
> Document Quality
>
>   SNMP is quite widely deployed. Measurements on SNMP traffic are being
>   performed by various tools and different organizations.
>
> Personnel
>
>   Bert Wijnen shephereded the document in the NMRG. Dan Romascanu is
>   the shepherding AD.
>
> IESG Note
>
> The IESG thinks that this work is related to IETF work done in the
> Operations and Management Area related to SNMP, but this does not prevent
> publishing. This RFC is not a candidate for any level of Internet
> Standard.
>
> The IETF disclaims any knowledge of the fitness of this RFC for
> any purpose and notes that the decision to publish is not based on
> IETF review apart from the IETF Last Call on the allocation of an URI by
> IANA and the IESG review for conflict with IETF work.
> The RFC Editor has chosen to publish this document at its
> discretion.  See RFC 3932 for more information.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>