[OPSAWG] draft-ietf-opsawg-operations-and-management-00.txt
"Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com> Fri, 21 September 2007 14:41 UTC
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYjgq-0006s5-Ge; Fri, 21 Sep 2007 10:41:08 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43) id 1IYjgq-0006s0-5j for opsawg-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 10:41:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYjgp-0006oi-Nk for opsawg@ietf.org; Fri, 21 Sep 2007 10:41:07 -0400
Received: from ihemail2.lucent.com ([135.245.0.35]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYjgj-0005aD-QU for opsawg@ietf.org; Fri, 21 Sep 2007 10:41:02 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id l8LEetnq022189 for <opsawg@ietf.org>; Fri, 21 Sep 2007 09:41:01 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Sep 2007 09:40:58 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.30]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Sep 2007 16:40:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Sep 2007 16:40:49 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F7E5AFD@DEEXC1U02.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-ietf-opsawg-operations-and-management-00.txt
Thread-Index: Acf6+3iW7u1v5dLtS+Cr1h/iKZ2zUwAmyEJAADCuZyA=
From: "Wijnen, Bert (Bert)" <bwijnen@alcatel-lucent.com>
To: opsawg@ietf.org
X-OriginalArrivalTime: 21 Sep 2007 14:40:56.0473 (UTC) FILETIME=[6B3DF890:01C7FC5D]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Subject: [OPSAWG] draft-ietf-opsawg-operations-and-management-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org
I have read the document and here are some minor comments: 1. the document is quite long. I know this is an easy comment as a reader and no so easy to address as an editor. but we should realize that WG members who need to read this as preparation for their protocol-to-be-developed will be less inclined to do so when the document is too long. 2. Section 4.3.1 [DISCUSS:: 'control plane' and 'data plane' are such slippery terms that I think they need to be defined.] I don't think we need to define them We are not giving any hard recommendations/requirements, just guidelines on how to think about these management aspects. In that context, I don't think we need to be precise. So we can avoid many long discussions to try to agree on an exact (or at least acceptable) definition. 3. Section 5.1 starts off with SNMP [RFC3410] is a Full Standard Well, RFC3410 is Informational. I know that SNMP (Specifically SNMPv3) is at IETF Full Standard level. But people who quickly check the rfc-index for RFC3410 might get confused. 4. Section 6.5 IPsec Security Policy IPsec Action MIB [I-D.ietf-ipsp-ipsecaction-mib] defines a MIB module for configuration of an IPsec action within the IPsec security policy database (SPD). [TODO: this is not yet a PS, and has dependencies on a dead document?] IPsec Security Policy IKE Action MIB [I-D.ietf-ipsp-ikeaction-mib] defines a MIB module for configuration of an Internet Key Exchange (IKE) [RFC4306] action within the IPsec security policy database (SPD). [TODO: this is not yet a PS, and has dependencies on a dead document?] These 2 MIB modules have been back and forth between MIB-doctor review and new revision for many (3-4) years now (cycles are around a year at least). As far as I can tell, I do not see them making much (if any progress). SO I think we should not discuss them here at all. Bert Wijnen -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, September 20, 2007 5:00 PM To: ops-area@ietf.org Subject: [OPS-AREA] FW: I-DACTION:draft-ietf-opsawg-operations-and-management-00.txt The Guidelines for operations and management of new protocols document was submitted as OPSAWG I-D. Please use the OPSAWG list for comments and discussions. Dan -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, September 19, 2007 10:15 PM To: i-d-announce@ietf.org Cc: opsawg@ietf.org Subject: I-D ACTION:draft-ietf-opsawg-operations-and-management-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF. Title : Guidelines for Considering Operations and Management of New Protocols Author(s) : D. Harrington Filename : draft-ietf-opsawg-operations-and-management-00.txt Pages : 37 Date : 2007-9-19 New protocols or protocol extensions are best designed with due consideration of operations and management issues related to the protocol. Retrofitting operations and management recommendations to protocols is sub-optimal. The purpose of this document is to provide guidance to authors of protocol documents about aspects to consider related to the operations and management that should be considered for inclusion in documents defining requirements or functionality of new protocols or protocol extensions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-opsawg-operations-and-man agement-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-opsawg-operations-and-management-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-opsawg-operations-and-management-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg
- [OPSAWG] draft-ietf-opsawg-operations-and-managem… Wijnen, Bert (Bert)
- RE: [OPSAWG] draft-ietf-opsawg-operations-and-man… David Harrington
- RE: [OPSAWG] draft-ietf-opsawg-operations-and-man… David Harrington