[midcom] MIDCOM mib design team rough draft available
"Mary Barnes" <mbarnes@nortelnetworks.com> Fri, 28 March 2003 22:14 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21624 for <midcom-archive@odin.ietf.org>; Fri, 28 Mar 2003 17:14:24 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h2SMaMp13239 for midcom-archive@odin.ietf.org; Fri, 28 Mar 2003 17:36:22 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SMZcO13206; Fri, 28 Mar 2003 17:35:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SMWpO13044 for <midcom@optimus.ietf.org>; Fri, 28 Mar 2003 17:32:51 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21525 for <midcom@ietf.org>; Fri, 28 Mar 2003 17:10:22 -0500 (EST)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2SMChS28528 for <midcom@ietf.org>; Fri, 28 Mar 2003 16:12:44 -0600 (CST)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id <HNP4N8W0>; Fri, 28 Mar 2003 16:12:44 -0600
Message-ID: <1B54FA3A2709D51195C800508BF9386A09DABBEE@zrc2c000.us.nortel.com>
From: Mary Barnes <mbarnes@nortelnetworks.com>
To: "'midcom@ietf.org'" <midcom@ietf.org>
Date: Fri, 28 Mar 2003 16:12:42 -0600
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [midcom] MIDCOM mib design team rough draft available
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Hi all, Per the discussion at last week's meeting, I have submitted a preliminary document outlining an initial view of existing mibs applicable to the MIDCOM problem domain and the general framework for the solution. Until it appears in the repository, it's available at: <http://home.attbi.com/~mbarnes42/IETF/draft-barnes-midcom-mib-00.txt> We'd appreciate any general feedback on the document and ideally, we'd like feedback on aspects of the existing mibs which are deemed applicable, per David's request a couple weeks ago on the applicability of ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-ipsp-ipsec-conf -mib-06.txt on the firewall and ACL aspects of MIDCOM. Note, this document is based on the premise that the WG will continue forward with the current charter of producing a mib, so I'd rather focus on this document with that objective in mind than have the discussion of this document center around whether we should be using XML - let's leave that for another discussion thread. Regards, Mary H. Barnes mbarnes@nortelnetworks.com ESN 444-5432 _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom