Re: [manet] REPORT-MIB - a question and an offer of help to pull it across the finishing line (UNCLASSIFIED)

Thomas Heide Clausen <thomas@thomasclausen.org> Thu, 27 February 2014 22:15 UTC

Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 045FE1A01F3 for <manet@ietfa.amsl.com>; Thu, 27 Feb 2014 14:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 AmWAwWnFaaGJ for <manet@ietfa.amsl.com>; Thu, 27 Feb 2014 14:15:20 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id A42751A0226 for <manet@ietf.org>; Thu, 27 Feb 2014 14:15:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 33A121A778D; Thu, 27 Feb 2014 14:15:19 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id BE16E1A778C; Thu, 27 Feb 2014 14:15:18 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Thomas Heide Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (11B651)
In-Reply-To: <B9468E58D6A0A84AAD66FE4E694BEABB55FB250E@ucolhp9h.easf.csd.disa.mil>
Date: Thu, 27 Feb 2014 23:15:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED1AE1AF-DCFA-4DC1-BB31-116480FF41B8@thomasclausen.org>
References: <8FD6DBB2-2F55-43BF-AC45-BDB53BF90113@thomasclausen.org> <32FD5CCA-AF21-4A02-8E2C-34B8799094E9@gmail.com> <E522A6FC-CA11-4EFA-AB33-48813C1666B7@thomasclausen.org> <B9468E58D6A0A84AAD66FE4E694BEABB55FB250E@ucolhp9h.easf.csd.disa.mil>
To: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/1fQcHLyl08UM2fruFn-ij4sNN3c
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] REPORT-MIB - a question and an offer of help to pull it across the finishing line (UNCLASSIFIED)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 22:15:26 -0000

Bob,

Thank you for the background and guidance - and for confirming my sentiment that with an energetic editorial effort, this document could be really close to a finishing line.

I actually am also (unsurprisingly) well aligned with the two steps you outline below. We need a stable spec, and then some experience - and then fold those together with wherever the rest of the IETF is once we've gotten enough experience to have an informed opinion on what should become standard.

So, I think that 1) is a good - and, even, necessary - stepping sone towards 1. So let's do it?

Thomas

ps: sad to hear that you won't be in London. Might you have time to a teleconf at some point about this?


> On 27 févr. 2014, at 22:08, "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil> wrote:
> 
> Classification: UNCLASSIFIED
> Caveats: NONE
> 
> 
> Thomas said:
> "So, while I am very interested in background and explanations, they're always educational, I'd submit that we should not drag our feet on this any longer: revive the document, do the reviews and re-spins, WGLC it and then get it off to Adrian for further processing. Having recently re-read it, my guestimate is that with a bit of concentrated effort, it shouldn't necessitate many months to see it through.
> 
> As I said, I'm willing to chip in and help out and do my part to make it go forward."
> 
> 
> Two potential ways to proceed:
> 
> 1) The last posted draft of the REPORT-MIB gave a simple bucket style approach to reporting remotely collected measurements back to a centralized manager.  It is straight forward and as Thomas said with some concentrated effort could finish up rather quickly with an energetic editor.  As an experimental RFC this could provide a useful experimental capability to play with and decide how best to improve upon for later efforts. 
> 
> 2) A longer term effort would be to rewrite it in the context of the DISMAN set of MIBs.  But this would take more time and more discussions.  
> 
> My feeling is that 2) is the best long term approach, but that 1) would provide a more immediate capability to experiment with.
> 
> Thanks,  Bob
> 
> 
> 
> Classification: UNCLASSIFIED
> Caveats: NONE
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet