[nmrg] FYI: draft-irtf-nmrg-snmp-measure-05.txt is on the IESG agenda
"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Sun, 24 August 2008 11:14 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 m7OBEhll018448 for <nmrg@ibr.cs.tu-bs.de>; Sun, 24 Aug 2008 13:14:49 +0200
Received: (qmail 12042 invoked from network); 24 Aug 2008 11:14:43 -0000
Received: from unknown (HELO BertLaptop) (87.215.199.34) by relay.versatel.net with SMTP; 24 Aug 2008 11:14:43 -0000
Message-ID: <2EDA52689379451A9C4B580116FFEF9A@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: NMRG <nmrg@ibr.cs.tu-bs.de>
Date: Sun, 24 Aug 2008 13:14:16 +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] FYI: draft-irtf-nmrg-snmp-measure-05.txt is on the IESG agenda
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: Sun, 24 Aug 2008 11:14:50 -0000
FYI, the draft-irtf-nmrg-snmp-measure-05.txt is on the IESG agenda for this coming Thursday. I beleive that this is the last step before it moves to the RFC-Editor queue (assuming IESG makes no objections). Bert Wijnen document shepherd --------- extract from IESG telechat agenda for 27 Aug 2008: > 3.3 Independent Submissions Via RFC Editor > The IESG will use RFC 3932 responses: 1) The IESG has not > found any conflict between this document and IETF work; 2) The > IESG thinks that this work is related to IETF work done in WG > <X>, but this does not prevent publishing; 3) The IESG thinks > that publication is harmful to work in WG <X> and recommends > not publishing at this time; 4) The IESG thinks that this > document violates the IETF procedures for <X> and should > therefore not be published without IETF review and IESG > approval; 5) The IESG thinks that this document extends an > IETF protocol in a way that requires IETF review and should > therefore not be published without IETF review and IESG > approval. > > The document shepherd must propose one of these responses in > the Data Tracker note and supply complete text in the IESG > Note portion of the write-up. The Area Director ballot positions > indicate consensus with the response proposed by the > document shepherd. > > Other matters may be recorded in comments, and the comments will > be passed on to the RFC Editor as community review of the > document. > > > 3.3.1 New Item > o draft-irtf-nmrg-snmp-measure-05.txt > SNMP Traffic Measurements and Trace Exchange Formats (Informational) > Note: Proposed 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.. . > Token: Dan Romascanu >
- [nmrg] FYI: draft-irtf-nmrg-snmp-measure-05.txt i… Bert Wijnen (IETF)