[Netconf] FW: DISCUSS and COMMENT: draft-ietf-netconf-monitoring
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 17 June 2010 11:53 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31FF03A681D for <netconf@core3.amsl.com>; Thu, 17 Jun 2010 04:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.594
X-Spam-Level:
X-Spam-Status: No, score=-1.594 tagged_above=-999 required=5 tests=[AWL=1.005, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyhMILSQhD+E for <netconf@core3.amsl.com>; Thu, 17 Jun 2010 04:53:53 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id DFAB03A699C for <netconf@ietf.org>; Thu, 17 Jun 2010 04:53:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,431,1272859200"; d="scan'208";a="21049038"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 17 Jun 2010 07:53:57 -0400
X-IronPort-AV: E=Sophos;i="4.53,431,1272859200"; d="scan'208";a="473348694"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 17 Jun 2010 07:53:26 -0400
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: Thu, 17 Jun 2010 13:53:21 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022B8F76@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: DISCUSS and COMMENT: draft-ietf-netconf-monitoring
Thread-Index: AcsOEUgqvP5pdvo1S4aSh6Z0graHRwAAlMhA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: netconf@ietf.org
Subject: [Netconf] FW: DISCUSS and COMMENT: draft-ietf-netconf-monitoring
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 11:53:57 -0000
A new DISCUSS - please address the issues raised by Adrian. Thanks and Regards, Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Adrian Farrel Sent: Thursday, June 17, 2010 2:36 PM To: iesg@ietf.org Cc: draft-ietf-netconf-monitoring@tools.ietf.org; netconf-chairs@tools.ietf.org Subject: DISCUSS and COMMENT: draft-ietf-netconf-monitoring Discuss: I think [4741bis] is used normatively. Please makeit a normative reference. --- Aren't the RFCs cited from Reference clauses really normative references? (As Dave says, to avoid citation issues, you should include some text such as... "This module makes use of references to [1], [2], ..." ) Comment: Section 3.1 Are there no other negative responses to get-schema? What about policy failures? --- Please think about whether the Reference clauses that cite RFC4741 should actually point to 4741bis.
- [Netconf] FW: DISCUSS and COMMENT: draft-ietf-net… Romascanu, Dan (Dan)
- [Netconf] FW: DISCUSS and COMMENT: draft-ietf-net… Ersue, Mehmet (NSN - DE/Munich)
- Re: [Netconf] DISCUSS and COMMENT: draft-ietf-net… Martin Bjorklund
- Re: [Netconf] DISCUSS and COMMENT: draft-ietf-net… Juergen Schoenwaelder
- [Netconf] FW: DISCUSS and COMMENT: draft-ietf-net… Romascanu, Dan (Dan)