From owner-netconf@ops.ietf.org Fri Feb 02 12:32:16 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HD2Gm-0005Tl-J8 for netconf-archive@lists.ietf.org; Fri, 02 Feb 2007 12:32:16 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HD2Gk-0005Ew-AY for netconf-archive@lists.ietf.org; Fri, 02 Feb 2007 12:32:16 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HD27z-000DJN-PQ for netconf-data@psg.com; Fri, 02 Feb 2007 17:23:11 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from [205.178.146.56] (helo=omr6.networksolutionsemail.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HD27w-000DIu-Mj for netconf@ops.ietf.org; Fri, 02 Feb 2007 17:23:10 +0000 Received: from mail.networksolutionsemail.com (ns-omr6.mgt.netsol.com [10.49.6.69]) by omr6.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l12HN0vV019519 for ; Fri, 2 Feb 2007 12:23:02 -0500 Received: (qmail 20666 invoked by uid 78); 2 Feb 2007 17:22:56 -0000 Received: from unknown (HELO ?127.0.0.1?) (andy@andybierman.com@75.83.56.110) by ns-omr6.lb.hosting.dc2.netsol.com with SMTP; 2 Feb 2007 17:22:56 -0000 Message-ID: <45C37352.7000602@andybierman.com> Date: Fri, 02 Feb 2007 09:22:26 -0800 From: Andy Bierman User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Li Yan CC: netconf@ops.ietf.org Subject: Re: a subtree filtering question References: <000001c73afb$eb20dbf0$3b0c6f0a@china.huawei.com> In-Reply-To: <000001c73afb$eb20dbf0$3b0c6f0a@china.huawei.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Li Yan wrote: > Hi, > > I don’t understand the following two sentences in rfc4741. > > 6.2.5. > > o Filtering of mixed content is not supported. Mixed content is text that can have embedded markup language in it. HTML uses a lot of mixed content. (like

within a

within a

) It is not mandatory to support this in NETCONF. > > o Filtering of list content is not supported. > A list is a whitespace-separated list of string values that conform to a specific simple type 1 3 5 7 1 3 5 7 If was a simple string, then this filter will not match because the whitespace is different. As a list, it should match, but the agent has to ignore or normalize whitespace instead of simply comparing the value. IMO, list should be supported, but I guess it is not mandatory. > Who can show me two examples to explain what are ‘mixed content’ and > ‘list content’ respectively? > > Thanks > > > > Yan > Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 09 18:44:23 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFfPj-0007PN-TD for netconf-archive@lists.ietf.org; Fri, 09 Feb 2007 18:44:23 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFfPg-00029P-UL for netconf-archive@lists.ietf.org; Fri, 09 Feb 2007 18:44:23 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HFfEq-00024N-PO for netconf-data@psg.com; Fri, 09 Feb 2007 23:33:08 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from [205.178.146.56] (helo=omr6.networksolutionsemail.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HFfEo-00023x-IS for netconf@ops.ietf.org; Fri, 09 Feb 2007 23:33:07 +0000 Received: from mail.networksolutionsemail.com (ns-omr6.mgt.netsol.com [10.49.6.69]) by omr6.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l19NX6Ko019309 for ; Fri, 9 Feb 2007 18:33:06 -0500 Received: (qmail 22413 invoked by uid 78); 9 Feb 2007 23:33:06 -0000 Received: from unknown (HELO ?127.0.0.1?) (andy@andybierman.com@75.83.56.110) by ns-omr6.lb.hosting.dc2.netsol.com with SMTP; 9 Feb 2007 23:33:06 -0000 Message-ID: <45CD04AE.2020607@andybierman.com> Date: Fri, 09 Feb 2007 15:33:02 -0800 From: Andy Bierman User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Netconf (E-mail)" Subject: netconf update Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Hi, The NETCONF WG is scheduled to meet on Monday evening at the next IETF. The primary goal of the meeting is to get the NETCONF Notifications draft approved by the WG and passed to the IESG for publication consideration. 1) The authors are working on a new version of the Notifications draft. 2) A 3 week WG Last Call will be started when this draft is published. 3) Depending on the new draft and the comments we receive in WGLC, there may be time available at the end of the meeting slot to discuss other drafts besides this one. thanks, Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From service@capitalone.com Mon Feb 12 14:21:08 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGgjc-0006pW-C2 for netconf-archive@megatron.ietf.org; Mon, 12 Feb 2007 14:21:08 -0500 Received: from [72.3.227.178] (helo=s79109.johngaultpress.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGgjb-000091-2Y for netconf-archive@megatron.ietf.org; Mon, 12 Feb 2007 14:21:08 -0500 Received: (qmail 23310 invoked from network); 12 Feb 2007 12:52:00 -0600 Received: from unknown (HELO User) (207.219.92.194) by 72.32.22.203 with SMTP; 12 Feb 2007 12:52:00 -0600 From: "Capital One Bank" Subject: Your Online Banking is Blocked ! Date: Mon, 12 Feb 2007 13:50:41 -0500 MIME-Version: 1.0 Content-Type: text/html; charset="Windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 4.2 (++++) X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd Capital One | Message

Dear Capital One Bank, Capital One, F.S.B., Member,

Because of unusual number of invalid login attempts on you account, we had to believe that, their might be
some security problem on you account. So we have decided to put an extra verification process to ensure your identity
and your account security. Please click the link bellow:.
https://onlinebanking.capitalone.com/capitalone/ID=?COB495886838

It is all about your security. Thank you. and visit the customer service section.

Capital One Bank, Capital One, F.S.B., members FDIC. ©2007 Capital One Services, Inc.
Capital One is a federally registered service mark. All rights reserved.

Capital One ID: COB495886838

From owner-netconf@ops.ietf.org Thu Feb 15 04:55:03 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHdKR-0000v0-QV for netconf-archive@lists.ietf.org; Thu, 15 Feb 2007 04:55:03 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHdKQ-00077V-FE for netconf-archive@lists.ietf.org; Thu, 15 Feb 2007 04:55:03 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HHdBO-000NP1-Ek for netconf-data@psg.com; Thu, 15 Feb 2007 09:45:42 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from [205.178.146.55] (helo=omr5.networksolutionsemail.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HFfDa-0001vO-1p for netconf@ops.ietf.org; Fri, 09 Feb 2007 23:31:51 +0000 Received: from mail.networksolutionsemail.com (ns-omr5.mgt.netsol.com [10.49.6.68]) by omr5.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l19NVlPF013501 for ; Fri, 9 Feb 2007 18:31:47 -0500 Received: (qmail 19350 invoked by uid 78); 9 Feb 2007 23:31:46 -0000 Received: from unknown (HELO ?127.0.0.1?) (andy@andybierman.com@75.83.56.110) by ns-omr5.lb.hosting.dc2.netsol.com with SMTP; 9 Feb 2007 23:31:46 -0000 Message-ID: <45CD045E.9030607@andybierman.com> Date: Fri, 09 Feb 2007 15:31:42 -0800 From: Andy Bierman User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Netconf (E-mail)" Subject: netconf update Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Hi, The NETCONF WG is scheduled to meet on Monday evening at the next IETF. The primary goal of the meeting is to get the NETCONF Notifications draft approved by the WG and passed to the IESG for publication consideration. 1) The authors are working on a new version of the Notifications draft. 2) A 3 week WG Last Call will be started when this draft is published. 3) Depending on the new draft and the comments we receive in WGLC, there may be time available at the end of the meeting slot to discuss other drafts besides this one. thanks, Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Feb 15 11:33:12 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHjXk-0000pP-EL for netconf-archive@lists.ietf.org; Thu, 15 Feb 2007 11:33:12 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHjXg-0006R2-4R for netconf-archive@lists.ietf.org; Thu, 15 Feb 2007 11:33:12 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HHjL2-000PTB-4q for netconf-data@psg.com; Thu, 15 Feb 2007 16:20:04 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HHjKu-000PRo-Cr for netconf@ops.ietf.org; Thu, 15 Feb 2007 16:19:58 +0000 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id l1FGJf529830; Thu, 15 Feb 2007 08:19:46 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (leida.juniper.net [172.18.16.26]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l1FGJaB86974; Thu, 15 Feb 2007 08:19:36 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.12.6/8.11.3) with ESMTP id l1FGN0S9018981; Thu, 15 Feb 2007 11:23:00 -0500 (EST) (envelope-from phil@idle.juniper.net) Message-Id: <200702151623.l1FGN0S9018981@idle.juniper.net> To: Andy Bierman cc: "Netconf (E-mail)" Subject: Re: netconf update In-Reply-To: Your message of "Fri, 09 Feb 2007 15:31:42 PST." <45CD045E.9030607@andybierman.com> Date: Thu, 15 Feb 2007 11:23:00 -0500 From: Phil Shafer Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Andy Bierman writes: > 1) The authors are working on a new version of the Notifications draft. Any estimate on when the new version will be out? Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Feb 15 13:15:57 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHl9B-0001lO-Sy for netconf-archive@lists.ietf.org; Thu, 15 Feb 2007 13:15:57 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHl94-000302-DS for netconf-archive@lists.ietf.org; Thu, 15 Feb 2007 13:15:57 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HHkzk-00083M-6l for netconf-data@psg.com; Thu, 15 Feb 2007 18:06:12 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.1.7 Received: from [62.241.162.32] (helo=ranger.systems.pipex.net) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HHkzc-00082t-NU for netconf@ops.ietf.org; Thu, 15 Feb 2007 18:06:09 +0000 Received: from pc6 (1Cust245.tnt101.lnd4.gbr.da.uu.net [213.116.50.245]) by ranger.systems.pipex.net (Postfix) with SMTP id 7816BE0001ED; Thu, 15 Feb 2007 18:05:55 +0000 (GMT) Message-ID: <052a01c75123$57c9d9e0$0601a8c0@pc6> Reply-To: "tom.petch" From: "tom.petch" To: , "Martin Bjorklund" References: <20061228.094637.74216736.mbj@tail-f.com> Subject: Re: comments on notification-05 Date: Thu, 15 Feb 2007 18:00:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 From: "Martin Bjorklund" To: Sent: Thursday, December 28, 2006 9:46 AM Subject: comments on notification-05 > A couple of comments: > > o 5.2 > > Here's 'neb' again, now transformed into an undeclared prefix! > If "neb:" is removed from the xpath expressions, it will be ok. > I see unmatched single quote and right hand bracket in the xpath; I am innocent in the ways of xpath but imagine that they might not be ok either. I see no reference in the text to xpath and no such reference listed in 9. > > /martin > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with > the word 'unsubscribe' in a single line as the message text body. > archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 16 09:56:56 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HI4W8-0002T4-H2 for netconf-archive@lists.ietf.org; Fri, 16 Feb 2007 09:56:56 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HI4W6-0002dQ-3M for netconf-archive@lists.ietf.org; Fri, 16 Feb 2007 09:56:56 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HI4I6-0004pX-NG for netconf-data@psg.com; Fri, 16 Feb 2007 14:42:26 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [47.140.192.56] (helo=zrtps0kp.nortel.com) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HI4I0-0004p8-OV for netconf@ops.ietf.org; Fri, 16 Feb 2007 14:42:25 +0000 Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l1GEgE515186 for ; Fri, 16 Feb 2007 09:42:14 -0500 (EST) 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 Subject: Proposed Edits to Notification Draft Date: Fri, 16 Feb 2007 09:42:09 -0500 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B40D7B5337@zcarhxm2.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposed Edits to Notification Draft Thread-Index: AcdR2KL9HhNGDDyGSU+rUaygzcYVBg== From: "Sharon Chisholm" To: "netconf" Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Hi The following is the proposed set of edits to the Notification draft to resolve comments received. It may not reflect recently received comments. 1. Put back schema to create and query named profiles, except combine into single schema with the one for event stream discovery. (Source: Martin & Andy) 2. In section 1.2, indicate that RPCs requests received on a notification session may be discarded silently. (Source: Balazs) 3. In section 2.3, indicate that termination may also result from termination of the underlying transport session or reaching a stop time on a replay. (Source: Balazs) 4. In section 3.2.5, delete the first sentence of the second paragraph and merge the second sentence with the first paragraph. (Source: Martin) 5. In section 3.2.5.2, fix namespace. (Source: Martin) 6. In section 3.2.5.2, delete the appInfo reference to netmod tags. (Source: Andy, others) 7. In section 3.2.5.2, fix the schemaLocation to be the proper urn. (source Li Yan) 8. In section 3.3.3, replace "While it is possible" with "While it may be possible". (Source: Balazs) 9. In section 3.4, there is some confusion between individual filter criteria (severity=3Dmajor) and the collective set of filters one gets = in a named profile or with in-line filters. In checking with the base protocol specification, I think the terms should be filter element and filter respectively. The section (and perhaps other parts of the document) will be updated to consistently use these terms to clear things up. (Source: Martin) 10. In section 5, update/add explanation of data model assumptions to the filter examples (Source: Andy) 11. In section 5.1 and 5.2, fix Schema errors. (Source: Martin) 12. In section 5.2, remove the neb prefix. (Source: Martin) 11. In section 6.2, replace the Error-info for start-time-too-early with ": Timestamp of earliest event available for replay". (Source: Balazs; Martin) 12. In section 6.2, add text indicating that in the event of a warning, the event subscription is still created. (Source Martin). Note I also propose changing the severity of start-stop-time-mismatch to an error instead of a warning. 13. In section 6.3, indicate that after the replayComplete notification is sent, the session then becomes a normal Netconf session. (Source: Balazs) 14. In section 6.3, indicate that the replayCompleteNotification can not be filtered out. (Source Martin) Sharon Chisholm Nortel=20 Ottawa, Ontario Canada -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 16 10:10:17 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HI4j3-0005ap-UT for netconf-archive@lists.ietf.org; Fri, 16 Feb 2007 10:10:17 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HI4j2-0005hw-Ie for netconf-archive@lists.ietf.org; Fri, 16 Feb 2007 10:10:17 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HI4UP-0005e3-1k for netconf-data@psg.com; Fri, 16 Feb 2007 14:55:09 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [47.129.242.56] (helo=zcars04e.nortel.com) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HI4UM-0005d0-1p for netconf@ops.ietf.org; Fri, 16 Feb 2007 14:55:07 +0000 Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id l1GEl1Q06324 for ; Fri, 16 Feb 2007 09:47:01 -0500 (EST) 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 Subject: RE: netconf update Date: Fri, 16 Feb 2007 09:54:56 -0500 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B40D7B539A@zcarhxm2.corp.nortel.com> In-Reply-To: <200702151623.l1FGN0S9018981@idle.juniper.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: netconf update Thread-Index: AcdRH21PIKmvH16TQOiFGuT+iLY/FAAurxcA From: "Sharon Chisholm" To: "Netconf \(E-mail\)" Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Hi The edit is basically ready. I just want to give the issue list a chance to air and verify that there are not any new comments that need to be addressed. We'll probably send it in on Monday. Sharon -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Phil Shafer Sent: Thursday, February 15, 2007 11:23 AM To: Andy Bierman Cc: Netconf (E-mail) Subject: Re: netconf update Andy Bierman writes: > 1) The authors are working on a new version of the Notifications draft. Any estimate on when the new version will be out? Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Sun Feb 18 02:18:22 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HIgJS-0002qS-6l for netconf-archive@lists.ietf.org; Sun, 18 Feb 2007 02:18:22 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HIgJM-0005Wt-S3 for netconf-archive@lists.ietf.org; Sun, 18 Feb 2007 02:18:22 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HIg7G-000O2m-2W for netconf-data@psg.com; Sun, 18 Feb 2007 07:05:46 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00, DATE_IN_PAST_12_24 autolearn=no version=3.1.7 Received: from [62.241.162.32] (helo=ranger.systems.pipex.net) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HIg7D-000O2R-SB for netconf@ops.ietf.org; Sun, 18 Feb 2007 07:05:45 +0000 Received: from pc6 (1Cust4.tnt10.lnd4.gbr.da.uu.net [62.188.139.4]) by ranger.systems.pipex.net (Postfix) with SMTP id 0CCE1E0009B5; Sat, 17 Feb 2007 18:35:31 +0000 (GMT) Message-ID: <000301c752b9$cb995700$0601a8c0@pc6> Reply-To: "tom.petch" From: "tom.petch" To: "Sharon Chisholm" , "Netconf (E-mail)" References: <713043CE8B8E1348AF3C546DBE02C1B40D7B539A@zcarhxm2.corp.nortel.com> Subject: Re: netconf update Date: Fri, 16 Feb 2007 21:27:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Sharon MUST the event be properly formed XML? I imagine it must but do not see that explicitly spelt out in the I-D. Equally, MUST there be a DTD or Schema for an event? Tom Petch ----- Original Message ----- From: "Sharon Chisholm" To: "Netconf (E-mail)" Sent: Friday, February 16, 2007 3:54 PM Subject: RE: netconf update Hi The edit is basically ready. I just want to give the issue list a chance to air and verify that there are not any new comments that need to be addressed. We'll probably send it in on Monday. Sharon -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Phil Shafer Sent: Thursday, February 15, 2007 11:23 AM To: Andy Bierman Cc: Netconf (E-mail) Subject: Re: netconf update Andy Bierman writes: > 1) The authors are working on a new version of the Notifications draft. Any estimate on when the new version will be out? Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Feb 19 05:04:15 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJ5NX-0000Hu-7g for netconf-archive@lists.ietf.org; Mon, 19 Feb 2007 05:04:15 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJ5NR-0004HC-Tl for netconf-archive@lists.ietf.org; Mon, 19 Feb 2007 05:04:15 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJ58t-000Lk5-SI for netconf-data@psg.com; Mon, 19 Feb 2007 09:49:07 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [213.180.94.158] (helo=mail.tail-f.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJ58r-000Ljm-C2 for netconf@ops.ietf.org; Mon, 19 Feb 2007 09:49:06 +0000 Received: from localhost (c213-100-166-193.swipnet.se [213.100.166.193]) by mail.tail-f.com (Postfix) with ESMTP id B62D41B80C3 for ; Mon, 19 Feb 2007 10:48:52 +0100 (CET) Date: Mon, 19 Feb 2007 10:49:22 +0100 (CET) Message-Id: <20070219.104922.82140541.mbj@tail-f.com> To: netconf@ops.ietf.org Subject: minor schema bug From: Martin Bjorklund X-Mailer: Mew version 5.1.51 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 There's a bug in the schema in rfc4741. The element 'bad-namespace' is defined as a QName, but it should be a string or token. For example, "http://example.com/bad/namespace" is not a valid QName. On a similar note, I think error-app-tag should have been defined as a QName instead of as a string, since that would have made it possible to define data-model/implementation-specific tags in namespaces, thus avoiding the risk of collisions. /martin -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Feb 20 13:37:17 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJZrZ-0004Mf-Ci for netconf-archive@lists.ietf.org; Tue, 20 Feb 2007 13:37:17 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJZrX-0007xx-1B for netconf-archive@lists.ietf.org; Tue, 20 Feb 2007 13:37:17 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJZfr-0008lv-5K for netconf-data@psg.com; Tue, 20 Feb 2007 18:25:11 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [47.129.242.57] (helo=zcars04f.nortel.com) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJZfo-0008ku-BM for netconf@ops.ietf.org; Tue, 20 Feb 2007 18:25:09 +0000 Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l1KIP3k28615 for ; Tue, 20 Feb 2007 13:25:04 -0500 (EST) 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 Subject: RE: netconf update Date: Tue, 20 Feb 2007 13:24:57 -0500 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B40D8D32C6@zcarhxm2.corp.nortel.com> In-Reply-To: <000301c752b9$cb995700$0601a8c0@pc6> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: netconf update Thread-Index: AcdSwnmfsQCZGWBTQS6J6GALWAAnNwCWc8SQ From: "Sharon Chisholm" To: "Netconf \(E-mail\)" Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Hi It must be well-formed XML. I had been thinking that this was covered, but since we are not re-using rpc messaging for Notifications anymore, I guess we need to explicitly state it. I don't think we can make any more specific claims in this document, but certain can in data model related ones. Sharon=20 -----Original Message----- From: tom.petch [mailto:cfinss@dial.pipex.com]=20 Sent: Friday, February 16, 2007 3:27 PM To: Chisholm, Sharon (CAR:ZZ00); Netconf (E-mail) Subject: Re: netconf update Sharon MUST the event be properly formed XML? I imagine it must but do not see that explicitly spelt out in the I-D. Equally, MUST there be a DTD or Schema for an event? Tom Petch ----- Original Message ----- From: "Sharon Chisholm" To: "Netconf (E-mail)" Sent: Friday, February 16, 2007 3:54 PM Subject: RE: netconf update Hi The edit is basically ready. I just want to give the issue list a chance to air and verify that there are not any new comments that need to be addressed. We'll probably send it in on Monday. Sharon -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Phil Shafer Sent: Thursday, February 15, 2007 11:23 AM To: Andy Bierman Cc: Netconf (E-mail) Subject: Re: netconf update Andy Bierman writes: > 1) The authors are working on a new version of the Notifications draft. Any estimate on when the new version will be out? Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Feb 20 15:57:42 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJc3S-0004m1-5n for netconf-archive@lists.ietf.org; Tue, 20 Feb 2007 15:57:42 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJc3P-0001tM-Ph for netconf-archive@lists.ietf.org; Tue, 20 Feb 2007 15:57:42 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJbvk-000JbV-E7 for netconf-data@psg.com; Tue, 20 Feb 2007 20:49:44 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [47.140.192.56] (helo=zrtps0kp.nortel.com) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJbvh-000Jb7-JX for netconf@ops.ietf.org; Tue, 20 Feb 2007 20:49:43 +0000 Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l1KKnbp17207 for ; Tue, 20 Feb 2007 15:49:37 -0500 (EST) 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 Subject: RE: Proposed Edits to Notification Draft Date: Tue, 20 Feb 2007 15:49:27 -0500 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B40D8D3656@zcarhxm2.corp.nortel.com> In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B40D7B5337@zcarhxm2.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposed Edits to Notification Draft Thread-Index: AcdR2KL9HhNGDDyGSU+rUaygzcYVBgDV7jYA From: "Sharon Chisholm" To: "netconf" Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Hi The draft has been submitted with two addition edits. I clarified that the XML in a Notification was well formed and I added a reference to XPATH. Either Hector fixed the quotation mark issue in section 5.2, or I was unable to detect it so I didn't change anything as a result of that comment. Sharon=20 -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Chisholm, Sharon (CAR:ZZ00) Sent: Friday, February 16, 2007 9:42 AM To: netconf Subject: Proposed Edits to Notification Draft Hi The following is the proposed set of edits to the Notification draft to resolve comments received. It may not reflect recently received comments. 1. Put back schema to create and query named profiles, except combine into single schema with the one for event stream discovery. (Source: Martin & Andy) 2. In section 1.2, indicate that RPCs requests received on a notification session may be discarded silently. (Source: Balazs) 3. In section 2.3, indicate that termination may also result from termination of the underlying transport session or reaching a stop time on a replay. (Source: Balazs) 4. In section 3.2.5, delete the first sentence of the second paragraph and merge the second sentence with the first paragraph. (Source: Martin) 5. In section 3.2.5.2, fix namespace. (Source: Martin) 6. In section 3.2.5.2, delete the appInfo reference to netmod tags. (Source: Andy, others) 7. In section 3.2.5.2, fix the schemaLocation to be the proper urn. (source Li Yan) 8. In section 3.3.3, replace "While it is possible" with "While it may be possible". (Source: Balazs) 9. In section 3.4, there is some confusion between individual filter criteria (severity=3Dmajor) and the collective set of filters one gets = in a named profile or with in-line filters. In checking with the base protocol specification, I think the terms should be filter element and filter respectively. The section (and perhaps other parts of the document) will be updated to consistently use these terms to clear things up. (Source: Martin) 10. In section 5, update/add explanation of data model assumptions to the filter examples (Source: Andy) 11. In section 5.1 and 5.2, fix Schema errors. (Source: Martin) 12. In section 5.2, remove the neb prefix. (Source: Martin) 11. In section 6.2, replace the Error-info for start-time-too-early with ": Timestamp of earliest event available for replay". (Source: Balazs; Martin) 12. In section 6.2, add text indicating that in the event of a warning, the event subscription is still created. (Source Martin). Note I also propose changing the severity of start-stop-time-mismatch to an error instead of a warning. 13. In section 6.3, indicate that after the replayComplete notification is sent, the session then becomes a normal Netconf session. (Source: Balazs) 14. In section 6.3, indicate that the replayCompleteNotification can not be filtered out. (Source Martin) Sharon Chisholm Nortel Ottawa, Ontario Canada -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Feb 21 09:52:28 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJspY-0007Dz-CL for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 09:52:28 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJspW-0001Hh-Ud for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 09:52:28 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJsiV-0005fd-Se for netconf-data@psg.com; Wed, 21 Feb 2007 14:45:11 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=ham version=3.1.7 Received: from [62.241.163.7] (helo=blaster.systems.pipex.net) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJsiQ-0005fF-N8 for netconf@ops.ietf.org; Wed, 21 Feb 2007 14:45:10 +0000 Received: from pc6 (1Cust244.tnt27.lnd4.gbr.da.uu.net [62.188.154.244]) by blaster.systems.pipex.net (Postfix) with SMTP id 4B50DE00036E; Wed, 21 Feb 2007 14:44:54 +0000 (GMT) Message-ID: <006201c755be$3e159ee0$0601a8c0@pc6> Reply-To: "tom.petch" From: "tom.petch" To: "Sharon Chisholm" , "Netconf (E-mail)" References: <713043CE8B8E1348AF3C546DBE02C1B40D8D32C6@zcarhxm2.corp.nortel.com> Subject: Re: netconf update Date: Wed, 21 Feb 2007 11:26:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e Tom Petch ----- Original Message ----- From: "Sharon Chisholm" To: "Netconf (E-mail)" Sent: Tuesday, February 20, 2007 7:24 PM Subject: RE: netconf updatei It must be well-formed XML. I had been thinking that this was covered, but since we are not re-using rpc messaging for Notifications anymore, I guess we need to explicitly state it. I don't think we can make any more specific claims in this document, but certain can in data model related ones. Sharon What I am wrestling with, after reading the SIP RFC you pointed us at, is the idea that the document must be well-formed XML, that filters may have removed mandatory elements and that the 'principal' may not be authorised to view a mandatory element. I am not sure how this can be resolved. eg suppose has minoccurs="1" maxoccurs="1" for each of the elements of which the last has very restricted access. I can envisage either access restrictions forcing a document not to conform to its Schema or multiple document definitions to allow for different combinations of access rights to different combinations of the elements, both of which seem unattractive. I think that this is a generic consideration, not one that should be left to individual data models, even if all we can say is that the data models should consider it. In SNMP, I do not see the issue arising because access rights win and there is no concept of a well-formed document to be in conflict with. Ditto syslog. Tom Petch -----Original Message----- From: tom.petch [mailto:cfinss@dial.pipex.com] Sent: Friday, February 16, 2007 3:27 PM To: Chisholm, Sharon (CAR:ZZ00); Netconf (E-mail) Subject: Re: netconf update Sharon MUST the event be properly formed XML? I imagine it must but do not see that explicitly spelt out in the I-D. Equally, MUST there be a DTD or Schema for an event? Tom Petch ----- Original Message ----- From: "Sharon Chisholm" To: "Netconf (E-mail)" Sent: Friday, February 16, 2007 3:54 PM Subject: RE: netconf update Hi The edit is basically ready. I just want to give the issue list a chance to air and verify that there are not any new comments that need to be addressed. We'll probably send it in on Monday. Sharon -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Phil Shafer Sent: Thursday, February 15, 2007 11:23 AM To: Andy Bierman Cc: Netconf (E-mail) Subject: Re: netconf update Andy Bierman writes: > 1) The authors are working on a new version of the Notifications draft. Any estimate on when the new version will be out? Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Feb 21 11:11:46 2007 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJtub-0006Vw-AS for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 11:01:45 -0500 Received: from psg.com ([147.28.0.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HJttl-00019A-4D for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 11:01:45 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJtjf-000DQ6-Er for netconf-data@psg.com; Wed, 21 Feb 2007 15:50:27 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO,MIME_BOUND_NEXTPART,NO_REAL_NAME autolearn=no version=3.1.7 Received: from [156.154.16.158] (helo=ns0.neustar.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJtjG-000DLw-SB for netconf@ops.ietf.org; Wed, 21 Feb 2007 15:50:10 +0000 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 08DB5329DC; Wed, 21 Feb 2007 15:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HJtjF-0008S1-T6; Wed, 21 Feb 2007 10:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: netconf@ops.ietf.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-netconf-notification-06.txt Message-Id: Date: Wed, 21 Feb 2007 10:50:01 -0500 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.3 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Configuration Working Group of the IETF. Title : NETCONF Event Notifications Author(s) : H. Trevino, S. Chisholm Filename : draft-ietf-netconf-notification-06.txt Pages : 34 Date : 2007-2-21 This document defines mechanisms which provide an asynchronous message notification delivery service for the NETCONF protocol. This is an optional capability built on top of the base NETCONF definition. This document defines the capabilities and operations necessary to support this service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-06.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-netconf-notification-06.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-netconf-notification-06.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-2-21083438.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-netconf-notification-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-netconf-notification-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-21083438.I-D@ietf.org> --OtherAccess-- --NextPart-- -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Feb 21 11:49:34 2007 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJues-0004f1-CF for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 11:49:34 -0500 Received: from psg.com ([147.28.0.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HJuel-0004zR-OD for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 11:49:34 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJuPE-000HlX-E5 for netconf-data@psg.com; Wed, 21 Feb 2007 16:33:24 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [193.180.251.62] (helo=mailgw4.ericsson.se) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJuPA-000Hl8-Ft for netconf@ops.ietf.org; Wed, 21 Feb 2007 16:33:23 +0000 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 7451D2104C; Wed, 21 Feb 2007 17:33:18 +0100 (CET) X-AuditID: c1b4fb3e-b1ed7bb0000007e1-a8-45dc744e220c Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 481EB2021B; Wed, 21 Feb 2007 17:33:18 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Feb 2007 17:33:16 +0100 Received: from [159.107.196.23] ([159.107.196.23]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Feb 2007 17:33:15 +0100 Message-ID: <45DC744A.5080901@ericsson.com> Date: Wed, 21 Feb 2007 17:33:14 +0100 From: Balazs Lengyel User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: "tom.petch" CC: Sharon Chisholm , "Netconf (E-mail)" Subject: Re: netconf update References: <713043CE8B8E1348AF3C546DBE02C1B40D8D32C6@zcarhxm2.corp.nortel.com> <006201c755be$3e159ee0$0601a8c0@pc6> In-Reply-To: <006201c755be$3e159ee0$0601a8c0@pc6> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Feb 2007 16:33:15.0317 (UTC) FILETIME=[FC54F650:01C755D5] X-Brightmail-Tracker: AAAAAA== Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243 Hello, You can just leave out the restricted elements (and their children). The XML will still be well formed, although it might not comply with some schema defining the content of the notification. However as Sharon's draft does not deal with the content of notifications, I thinks this issue is not Sharon's problem. regards Balazs tom.petch wrote: > > Tom Petch > > ----- Original Message ----- > From: "Sharon Chisholm" > To: "Netconf (E-mail)" > Sent: Tuesday, February 20, 2007 7:24 PM > Subject: RE: netconf updatei > > It must be well-formed XML. I had been thinking that this was covered, > but since we are not re-using rpc messaging for Notifications anymore, I > guess we need to explicitly state it. I don't think we can make any more > specific claims in this document, but certain can in data model related > ones. > > Sharon > > > > What I am wrestling with, after reading the SIP RFC you pointed us at, is the > idea that the document must be well-formed XML, that filters may have removed > mandatory elements and that the 'principal' may not be authorised to view a > mandatory element. I am not sure how this can be resolved. > > eg suppose has minoccurs="1" maxoccurs="1" for each of the elements > > > > of which the last has very restricted access. I can envisage either access > restrictions forcing a document not to conform to its Schema or multiple > document definitions to allow for different combinations of access rights to > different combinations of the elements, both of which seem unattractive. > > I think that this is a generic consideration, not one that should be left to > individual data models, even if all we can say is that the data models should > consider it. > > In SNMP, I do not see the issue arising because access rights win and there is > no concept of a well-formed document to be in conflict with. Ditto syslog. > > Tom Petch > > -----Original Message----- > From: tom.petch [mailto:cfinss@dial.pipex.com] > Sent: Friday, February 16, 2007 3:27 PM > To: Chisholm, Sharon (CAR:ZZ00); Netconf (E-mail) > Subject: Re: netconf update > > Sharon > > MUST the event be properly formed XML? I imagine it must but do not see > that explicitly spelt out in the I-D. Equally, MUST there be a DTD or > Schema for an event? > > Tom Petch > > > ----- Original Message ----- > From: "Sharon Chisholm" > To: "Netconf (E-mail)" > Sent: Friday, February 16, 2007 3:54 PM > Subject: RE: netconf update > > > Hi > > The edit is basically ready. I just want to give the issue list a chance > to air and verify that there are not any new comments that need to be > addressed. We'll probably send it in on Monday. > > Sharon > > -----Original Message----- > From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On > Behalf Of Phil Shafer > Sent: Thursday, February 15, 2007 11:23 AM > To: Andy Bierman > Cc: Netconf (E-mail) > Subject: Re: netconf update > > Andy Bierman writes: >> 1) The authors are working on a new version of the Notifications > draft. > > Any estimate on when the new version will be out? > > Thanks, > Phil > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with the > word 'unsubscribe' in a single line as the message text body. > archive: > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with the > word 'unsubscribe' in a single line as the message text body. > archive: > > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with > the word 'unsubscribe' in a single line as the message text body. > archive: > > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with > the word 'unsubscribe' in a single line as the message text body. > archive: -- Balazs Lengyel Ericsson Hungary Ltd. TSP System Manager ECN: 831 7320 Fax: +36 1 4377792 Tel: +36-1-437-7320 email: Balazs.Lengyel@ericsson.com -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Feb 21 12:22:12 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJvAS-0001ma-Tb for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 12:22:12 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJvAR-0004bl-Bj for netconf-archive@lists.ietf.org; Wed, 21 Feb 2007 12:22:12 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJv1p-000LnM-Sy for netconf-data@psg.com; Wed, 21 Feb 2007 17:13:17 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from [205.178.146.57] (helo=omr7.networksolutionsemail.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HJv1j-000Lmz-By for netconf@ops.ietf.org; Wed, 21 Feb 2007 17:13:16 +0000 Received: from mail.networksolutionsemail.com (ns-omr7.mgt.hosting.dc2.netsol.com [10.49.6.70]) by omr7.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l1LHDAPk004678 for ; Wed, 21 Feb 2007 12:13:10 -0500 Received: (qmail 5739 invoked by uid 78); 21 Feb 2007 17:13:09 -0000 Received: from unknown (HELO ?127.0.0.1?) (andy@andybierman.com@75.83.56.110) by ns-omr7.lb.hosting.dc2.netsol.com with SMTP; 21 Feb 2007 17:13:09 -0000 Message-ID: <45DC7D95.20106@andybierman.com> Date: Wed, 21 Feb 2007 09:12:53 -0800 From: Andy Bierman User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Balazs Lengyel CC: "tom.petch" , Sharon Chisholm , "Netconf (E-mail)" Subject: Re: netconf update References: <713043CE8B8E1348AF3C546DBE02C1B40D8D32C6@zcarhxm2.corp.nortel.com> <006201c755be$3e159ee0$0601a8c0@pc6> <45DC744A.5080901@ericsson.com> In-Reply-To: <45DC744A.5080901@ericsson.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb Balazs Lengyel wrote: > Hello, > You can just leave out the restricted elements (and their children). The > XML will still be well formed, although it might not comply with some > schema defining the content of the notification. However as Sharon's > draft does not deal with the content of notifications, I thinks this > issue is not Sharon's problem. To be even more clear: An agent is required to process the subtree filter regardless of its contents -- there is no schema to validate here. Any error (invalid namespace, attribute, simple or complex content) is just a "no match" condition, not any error. > regards Balazs Andy > > tom.petch wrote: >> >> Tom Petch >> >> ----- Original Message ----- >> From: "Sharon Chisholm" >> To: "Netconf (E-mail)" >> Sent: Tuesday, February 20, 2007 7:24 PM >> Subject: RE: netconf updatei >> >> It must be well-formed XML. I had been thinking that this was covered, >> but since we are not re-using rpc messaging for Notifications anymore, I >> guess we need to explicitly state it. I don't think we can make any more >> specific claims in this document, but certain can in data model related >> ones. >> >> Sharon >> >> >> >> What I am wrestling with, after reading the SIP RFC you pointed us at, >> is the >> idea that the document must be well-formed XML, that filters may have >> removed >> mandatory elements and that the 'principal' may not be authorised to >> view a >> mandatory element. I am not sure how this can be resolved. >> >> eg suppose has minoccurs="1" maxoccurs="1" for each of the >> elements >> >> >> >> of which the last has very restricted access. I can envisage either >> access >> restrictions forcing a document not to conform to its Schema or multiple >> document definitions to allow for different combinations of access >> rights to >> different combinations of the elements, both of which seem unattractive. >> >> I think that this is a generic consideration, not one that should be >> left to >> individual data models, even if all we can say is that the data models >> should >> consider it. >> >> In SNMP, I do not see the issue arising because access rights win and >> there is >> no concept of a well-formed document to be in conflict with. Ditto >> syslog. >> >> Tom Petch >> >> -----Original Message----- >> From: tom.petch [mailto:cfinss@dial.pipex.com] >> Sent: Friday, February 16, 2007 3:27 PM >> To: Chisholm, Sharon (CAR:ZZ00); Netconf (E-mail) >> Subject: Re: netconf update >> >> Sharon >> >> MUST the event be properly formed XML? I imagine it must but do not see >> that explicitly spelt out in the I-D. Equally, MUST there be a DTD or >> Schema for an event? >> >> Tom Petch >> >> >> ----- Original Message ----- >> From: "Sharon Chisholm" >> To: "Netconf (E-mail)" >> Sent: Friday, February 16, 2007 3:54 PM >> Subject: RE: netconf update >> >> >> Hi >> >> The edit is basically ready. I just want to give the issue list a chance >> to air and verify that there are not any new comments that need to be >> addressed. We'll probably send it in on Monday. >> >> Sharon >> >> -----Original Message----- >> From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On >> Behalf Of Phil Shafer >> Sent: Thursday, February 15, 2007 11:23 AM >> To: Andy Bierman >> Cc: Netconf (E-mail) >> Subject: Re: netconf update >> >> Andy Bierman writes: >>> 1) The authors are working on a new version of the Notifications >> draft. >> >> Any estimate on when the new version will be out? >> >> Thanks, >> Phil >> >> -- >> to unsubscribe send a message to netconf-request@ops.ietf.org with the >> word 'unsubscribe' in a single line as the message text body. >> archive: >> >> -- >> to unsubscribe send a message to netconf-request@ops.ietf.org with the >> word 'unsubscribe' in a single line as the message text body. >> archive: >> >> >> -- >> to unsubscribe send a message to netconf-request@ops.ietf.org with >> the word 'unsubscribe' in a single line as the message text body. >> archive: >> >> >> -- >> to unsubscribe send a message to netconf-request@ops.ietf.org with >> the word 'unsubscribe' in a single line as the message text body. >> archive: > -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 23 03:04:41 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKVQ1-0007ES-OG for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 03:04:41 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKVPu-0003o2-8g for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 03:04:41 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKVBT-0008PS-Dy for netconf-data@psg.com; Fri, 23 Feb 2007 07:49:39 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [193.180.251.62] (helo=mailgw4.ericsson.se) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKVBP-0008Oo-B0 for netconf@ops.ietf.org; Fri, 23 Feb 2007 07:49:38 +0000 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 4EF9A211BD for ; Fri, 23 Feb 2007 08:49:33 +0100 (CET) X-AuditID: c1b4fb3e-aeed1bb0000007e1-fe-45de9c8daf3f Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3CC50200E1 for ; Fri, 23 Feb 2007 08:49:33 +0100 (CET) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 08:49:32 +0100 Received: from [159.107.196.23] ([159.107.196.23]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 08:49:32 +0100 Message-ID: <45DE9C89.2090408@ericsson.com> Date: Fri, 23 Feb 2007 08:49:29 +0100 From: Balazs Lengyel User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: "Netconf (E-mail)" Subject: Comments on notification-6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Feb 2007 07:49:32.0788 (UTC) FILETIME=[27DF0B40:01C7571F] X-Brightmail-Tracker: AAAAAA== Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Hello, Generally the document is in good shape, I could except it as is, but still I have some comments: 1.) Consider adding: content of notification messages is out of scope. 1.2 paragraph 2) The sentence starting with "These event notifications..." might need some rewording. 2.1.1) An example could be useful. 2.2.1) An example could be useful. 3.2.5.1) Change title to Stream Retrieval ... 3.3) Why do we need more then one namespace? I feel we should put everything into one. 3.5) Remove first sentence. There can be only one filter. 5.1) The sample event list is hard to understand. I would rather like to know which bit of XML will go into each event. Is it the element as a whole or just the contents of ? The example on page 24 indicates only the contents, the example on page 25 indicates the whole . The two examples contradict each other. 5.1 page 25) In my understanding the example is faulty. The last clause is useless as the first fault clause will always let through all "faults". The first clause should be removed. 6.2) I would mention that in replay sessions events are always sent in order of their timestamps. Events occurring during a replay will not be sent immediately, but only after all previous events are sent. Balazs -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 23 13:25:57 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKf7F-00069u-2J for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 13:25:57 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKf7D-0004dt-Ox for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 13:25:57 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKeuL-000Ff1-Tx for netconf-data@psg.com; Fri, 23 Feb 2007 18:12:37 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from [205.178.146.59] (helo=omr9.networksolutionsemail.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKeuI-000Fej-NS for netconf@ops.ietf.org; Fri, 23 Feb 2007 18:12:36 +0000 Received: from mail.networksolutionsemail.com (ns-omr9.mgt.hosting.dc2.netsol.com [10.49.6.72]) by omr9.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l1NICW4E023034 for ; Fri, 23 Feb 2007 13:12:34 -0500 Received: (qmail 19189 invoked by uid 78); 23 Feb 2007 18:12:32 -0000 Received: from unknown (HELO ?127.0.0.1?) (andy@andybierman.com@75.83.56.110) by ns-omr9.lb.hosting.dc2.netsol.com with SMTP; 23 Feb 2007 18:12:32 -0000 Message-ID: <45DF2E7F.70907@andybierman.com> Date: Fri, 23 Feb 2007 10:12:15 -0800 From: Andy Bierman User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: NETCONF WG Subject: Begin Working Group Last Call: draft-ietf-netconf-notification-06.txt Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Hi, The NETCONF WG is concluding work on the NETCONF Notifications document. WG members are urged to review the latest draft carefully and send comments to the WG mailing list. http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-06.txt This is the Last Call for comments before the document is advanced to the IESG for publication consideration as a Proposed Standard. Comments will be accepted until 5PM ET March 16, 2007. The NETCONF WG will meet the following week at IETF #68 to address all unresolved WGLC comments. thanks, Andy and Simon -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 23 14:18:53 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKfur-0000zv-Kw for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 14:17:13 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKfuZ-0004ob-4e for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 14:17:12 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKflS-000OJk-Nd for netconf-data@psg.com; Fri, 23 Feb 2007 19:07:30 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [62.241.162.31] (helo=galaxy.systems.pipex.net) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKflK-000OIi-Ft for netconf@ops.ietf.org; Fri, 23 Feb 2007 19:07:24 +0000 Received: from pc6 (1Cust159.tnt16.lnd4.gbr.da.uu.net [62.188.145.159]) by galaxy.systems.pipex.net (Postfix) with SMTP id 9AE22E000715; Fri, 23 Feb 2007 19:07:15 +0000 (GMT) Message-ID: <001501c75775$3486fb40$0601a8c0@pc6> Reply-To: "tom.petch" From: "tom.petch" To: "Sharon Chisholm" , "netconf" References: <713043CE8B8E1348AF3C546DBE02C1B40D8D3656@zcarhxm2.corp.nortel.com> Subject: Re: Proposed Edits to Notification Draft Date: Fri, 23 Feb 2007 18:10:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243 Tom Petch ----- Original Message ----- From: "Sharon Chisholm" To: "netconf" Sent: Tuesday, February 20, 2007 9:49 PM Subject: RE: Proposed Edits to Notification Draft Hi The draft has been submitted with two addition edits. I clarified that the XML in a Notification was well formed and I added a reference to XPATH. Either Hector fixed the quotation mark issue in section 5.2, or I was unable to detect it so I didn't change anything as a result of that comment. Sharon, I am looking at section 5.2 and seeing which appears to have seven single quotes, one left hand round bracket and three right hand round brackets, three left hand square brackets and two right hand square brackets. Sharon -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Chisholm, Sharon (CAR:ZZ00) Sent: Friday, February 16, 2007 9:42 AM To: netconf Subject: Proposed Edits to Notification Draft Hi The following is the proposed set of edits to the Notification draft to resolve comments received. It may not reflect recently received comments. 1. Put back schema to create and query named profiles, except combine into single schema with the one for event stream discovery. (Source: Martin & Andy) 2. In section 1.2, indicate that RPCs requests received on a notification session may be discarded silently. (Source: Balazs) 3. In section 2.3, indicate that termination may also result from termination of the underlying transport session or reaching a stop time on a replay. (Source: Balazs) 4. In section 3.2.5, delete the first sentence of the second paragraph and merge the second sentence with the first paragraph. (Source: Martin) 5. In section 3.2.5.2, fix namespace. (Source: Martin) 6. In section 3.2.5.2, delete the appInfo reference to netmod tags. (Source: Andy, others) 7. In section 3.2.5.2, fix the schemaLocation to be the proper urn. (source Li Yan) 8. In section 3.3.3, replace "While it is possible" with "While it may be possible". (Source: Balazs) 9. In section 3.4, there is some confusion between individual filter criteria (severity=major) and the collective set of filters one gets in a named profile or with in-line filters. In checking with the base protocol specification, I think the terms should be filter element and filter respectively. The section (and perhaps other parts of the document) will be updated to consistently use these terms to clear things up. (Source: Martin) 10. In section 5, update/add explanation of data model assumptions to the filter examples (Source: Andy) 11. In section 5.1 and 5.2, fix Schema errors. (Source: Martin) 12. In section 5.2, remove the neb prefix. (Source: Martin) 11. In section 6.2, replace the Error-info for start-time-too-early with ": Timestamp of earliest event available for replay". (Source: Balazs; Martin) 12. In section 6.2, add text indicating that in the event of a warning, the event subscription is still created. (Source Martin). Note I also propose changing the severity of start-stop-time-mismatch to an error instead of a warning. 13. In section 6.3, indicate that after the replayComplete notification is sent, the session then becomes a normal Netconf session. (Source: Balazs) 14. In section 6.3, indicate that the replayCompleteNotification can not be filtered out. (Source Martin) Sharon Chisholm Nortel Ottawa, Ontario Canada -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 23 15:35:58 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKh94-0003Iu-Sj for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 15:35:58 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKh93-0004Zf-Bj for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 15:35:58 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKgzW-000BsI-E4 for netconf-data@psg.com; Fri, 23 Feb 2007 20:26:06 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKgzO-000Bqb-3T for netconf@ops.ietf.org; Fri, 23 Feb 2007 20:26:04 +0000 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 23 Feb 2007 12:25:57 -0800 X-IronPort-AV: i="4.14,212,1170662400"; d="scan'208"; a="115701658:sNHT89547615" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l1NKPua0019198; Fri, 23 Feb 2007 12:25:56 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l1NKPqV0004306; Fri, 23 Feb 2007 12:25:52 -0800 (PST) Received: from xmb-sjc-223.amer.cisco.com ([128.107.191.124]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 12:25:52 -0800 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 Subject: RE: Proposed Edits to Notification Draft Date: Fri, 23 Feb 2007 12:25:51 -0800 Message-ID: <6E21698722408147BEA594E073E2B0AB034F969B@xmb-sjc-223.amer.cisco.com> In-Reply-To: <001501c75775$3486fb40$0601a8c0@pc6> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposed Edits to Notification Draft Thread-Index: AcdXff4HHORfnobTRL2r1OpwaqzJTgACl5Dw References: <713043CE8B8E1348AF3C546DBE02C1B40D8D3656@zcarhxm2.corp.nortel.com> <001501c75775$3486fb40$0601a8c0@pc6> From: "Hector Trevino \(htrevino\)" To: "tom.petch" , "Sharon Chisholm" , "netconf" X-OriginalArrivalTime: 23 Feb 2007 20:25:52.0100 (UTC) FILETIME=[D00C8A40:01C75788] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4777; t=1172262356; x=1173126356; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=htrevino@cisco.com; z=From:=20=22Hector=20Trevino=20\(htrevino\)=22=20 |Subject:=20RE=3A=20Proposed=20Edits=20to=20Notification=20Draft |Sender:=20; bh=PupqOuEjzWBu0EHn1GdLI7ui7cK3BdxsdFKFSNlsy4c=; b=lbLE7aPlMHmf8Zr1+vwYBhrgcM5S4qmplffGpO+vpeAiPnYpqeHhMtgSZ9pye0G3CCVcoW/Z SG/wp0d/xbbkehkMHRIadPVe4mDRi9Kkk9cREO/wQxGK/qatMtDw+eyF; Authentication-Results: sj-dkim-3; header.From=htrevino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78 Tom, Hi, I was looking at your comment and noticed that this section (5.2) was not get updated properly. We'll update. Thanks Hector =20 =20 -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of tom.petch Sent: Friday, February 23, 2007 10:10 AM To: Sharon Chisholm; netconf Subject: Re: Proposed Edits to Notification Draft Tom Petch ----- Original Message ----- From: "Sharon Chisholm" To: "netconf" Sent: Tuesday, February 20, 2007 9:49 PM Subject: RE: Proposed Edits to Notification Draft Hi The draft has been submitted with two addition edits. I clarified that the XML in a Notification was well formed and I added a reference to XPATH. Either Hector fixed the quotation mark issue in section 5.2, or I was unable to detect it so I didn't change anything as a result of that comment. Sharon, I am looking at section 5.2 and seeing which appears to have seven single quotes, one left hand round bracket and three right hand round brackets, three left hand square brackets and two right hand square brackets. Sharon -----Original Message----- From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of Chisholm, Sharon (CAR:ZZ00) Sent: Friday, February 16, 2007 9:42 AM To: netconf Subject: Proposed Edits to Notification Draft Hi The following is the proposed set of edits to the Notification draft to resolve comments received. It may not reflect recently received comments. 1. Put back schema to create and query named profiles, except combine into single schema with the one for event stream discovery. (Source: Martin & Andy) 2. In section 1.2, indicate that RPCs requests received on a notification session may be discarded silently. (Source: Balazs) 3. In section 2.3, indicate that termination may also result from termination of the underlying transport session or reaching a stop time on a replay. (Source: Balazs) 4. In section 3.2.5, delete the first sentence of the second paragraph and merge the second sentence with the first paragraph. (Source: Martin) 5. In section 3.2.5.2, fix namespace. (Source: Martin) 6. In section 3.2.5.2, delete the appInfo reference to netmod tags. (Source: Andy, others) 7. In section 3.2.5.2, fix the schemaLocation to be the proper urn. (source Li Yan) 8. In section 3.3.3, replace "While it is possible" with "While it may be possible". (Source: Balazs) 9. In section 3.4, there is some confusion between individual filter criteria (severity=3Dmajor) and the collective set of filters one gets = in a named profile or with in-line filters. In checking with the base protocol specification, I think the terms should be filter element and filter respectively. The section (and perhaps other parts of the document) will be updated to consistently use these terms to clear things up. (Source: Martin) 10. In section 5, update/add explanation of data model assumptions to the filter examples (Source: Andy) 11. In section 5.1 and 5.2, fix Schema errors. (Source: Martin) 12. In section 5.2, remove the neb prefix. (Source: Martin) 11. In section 6.2, replace the Error-info for start-time-too-early with ": Timestamp of earliest event available for replay". (Source: Balazs; Martin) 12. In section 6.2, add text indicating that in the event of a warning, the event subscription is still created. (Source Martin). Note I also propose changing the severity of start-stop-time-mismatch to an error instead of a warning. 13. In section 6.3, indicate that after the replayComplete notification is sent, the session then becomes a normal Netconf session. (Source: Balazs) 14. In section 6.3, indicate that the replayCompleteNotification can not be filtered out. (Source Martin) Sharon Chisholm Nortel Ottawa, Ontario Canada -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Feb 23 17:45:38 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKjAY-0007mc-1u for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 17:45:38 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKjAW-0003E6-CN for netconf-archive@lists.ietf.org; Fri, 23 Feb 2007 17:45:38 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKj3U-0002WL-9j for netconf-data@psg.com; Fri, 23 Feb 2007 22:38:20 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from [205.178.146.53] (helo=omr3.networksolutionsemail.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HKj3R-0002Vy-Bd for netconf@ops.ietf.org; Fri, 23 Feb 2007 22:38:19 +0000 Received: from mail.networksolutionsemail.com (ns-omr3.mgt.netsolmail.com [10.49.6.66]) by omr3.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l1NMcGcY002544 for ; Fri, 23 Feb 2007 17:38:16 -0500 Received: (qmail 1912 invoked by uid 78); 23 Feb 2007 22:38:16 -0000 Received: from unknown (HELO ?127.0.0.1?) (andy@andybierman.com@75.83.56.110) by ns-omr3.lb.hosting.dc2.netsol.com with SMTP; 23 Feb 2007 22:38:16 -0000 Message-ID: <45DF6CC6.5060004@andybierman.com> Date: Fri, 23 Feb 2007 14:37:58 -0800 From: Andy Bierman User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Hector Trevino (htrevino)" CC: "tom.petch" , Sharon Chisholm , netconf Subject: Re: Proposed Edits to Notification Draft References: <713043CE8B8E1348AF3C546DBE02C1B40D8D3656@zcarhxm2.corp.nortel.com> <001501c75775$3486fb40$0601a8c0@pc6> <6E21698722408147BEA594E073E2B0AB034F969B@xmb-sjc-223.amer.cisco.com> In-Reply-To: <6E21698722408147BEA594E073E2B0AB034F969B@xmb-sjc-223.amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Hector Trevino (htrevino) wrote: > Tom, > > Hi, I was looking at your comment and noticed that this section (5.2) > was not get updated properly. We'll update. At this point, only post proposed edits to the mailing list. Do not make any edits or publish a new draft until after the WGLC is over. > Thanks > Hector > thanks, Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From gvrdtrvrtte6vtv563v6@yahoo.co.jp Sun Feb 25 13:10:54 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLNpm-0007J5-GS for netconf-archive@lists.ietf.org; Sun, 25 Feb 2007 13:10:54 -0500 Received: from [221.201.227.50] (helo=lists.ietf.org) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HLNpk-0005od-0G for netconf-archive@lists.ietf.org; Sun, 25 Feb 2007 13:10:54 -0500 To: From: =?iso-2022-jp?B?d2ViGyRCQ0s9dxsoQm5ld3M=?= Subject: =?iso-2022-jp?B?GyRCRk1BMyROJWEhPCVrJEc8Ok5pQ1ckNyReJDkhIxsoQg==?= MIME-Version: 1.0 Reply-To: Content-Type:text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Spam-Score: 4.1 (++++) X-Scan-Signature: 93238566e09e6e262849b4f805833007 $B:#2s$O9-9pHq$N$_$G<}F~$rF@$F$$$kBg?M$N=P2q$$$N>l$r>R2p$7$^$9!#(B $BEvA3A4$F$N%3%s%F%s%D$rL5NA$GMxMQ=PMh$k$N$G0B?4$G$9!#(B $BF~8}$O$3$A$i"M!!(Bhttp://kzjw.com/ajn/ $B!!!!!!EPO?NA(B-----------------------$B!ZL5NA![(B $B!!!!!!%a!<%k$NAwpJs%a!<%k$rITMW$JJ}$O$*) id 1HLSAa-0006nK-7O for netconf-data@psg.com; Sun, 25 Feb 2007 22:48:40 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [213.180.94.158] (helo=mail.tail-f.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HLSAX-0006mZ-Dw for netconf@ops.ietf.org; Sun, 25 Feb 2007 22:48:39 +0000 Received: from localhost (c213-100-166-193.swipnet.se [213.100.166.193]) by mail.tail-f.com (Postfix) with ESMTP id 501C41B80C3 for ; Sun, 25 Feb 2007 23:48:33 +0100 (CET) Date: Sun, 25 Feb 2007 23:49:18 +0100 (CET) Message-Id: <20070225.234918.21759948.mbj@tail-f.com> To: netconf@ops.ietf.org Subject: comments on draft-ietf-netconf-notification-06.txt From: Martin Bjorklund X-Mailer: Mew version 5.1.51 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576 Hi, Here are my comments on draft-ietf-netconf-notification-06.txt. o 3.2.5.1 Uses the URI "urn:ietf:params:xml:ns:netmod:base:1.0" for event streams in the example. But the schema in 3.3 uses "urn:ietf:params:xml:ns:netmod:event:1.0". These should be the same. I suggest that this info is put into the "urn:ietf:params:xml:ns:netconf:notification:1.0" schema. o 3.3 /namedProfiles/namedProfile/name xs:key is not used for namedProfile/name. If it's not unique or a key, then there can be several namedProfiles with the same name. I suspect this is not the intention. The text in 3.2.5.1 says that the value is unique. Maybe that is sufficient. It also says about 'name' that it is modifiable. How is this supposed to be done over NETCONF? (how do you modifify the key? or even worse if it's not a key). o 3.3 /namedProfiles/namedProfile/stream Why is this element included here? A stream is always specified in the (or defaults to NETCONF) when a namedProfile is used. Are these supposed to match?? o 3.3 /namedProfiles/namedProfile/filter This element has a minOccurs="0". It means that the element may or may not be present in an instance document. Why is it used here? o 5.1 The text shows a sample event list which doesn't match the examples that follows. I also don't understand the container. I suggest that the container is removed, and is changed to in this list. The second example must also be modified to match this. o 5.1 and 5.2 All four examples use an undeclared prefix "netconf" on the element 'filter' (it shouldn't be there; 'filter' is defined in the new namespace), and lacks a xmlns attribute. Both xpath examples use the element name 'eventClasses' but the text and other examples use 'eventClass'. o 6.1 Section 2.1.1 says that an element is returned for a if the request can be satisfied. This section (6.1) says "If a client requests a replay of notifications that predate the oldest notification available, then the NETCONF server must return a warning message in the RPC reply and start replaying the notifications it does have available" But, according to 4.4 of rfc4741, "The element is sent in messages if no errors or warnings occurred during the processing of an request." This is also consistent with the XML schema in rfc4741. Thus, it is not possible to return and a warning. I suppose the intention of 6.1 is that a warning only (i.e no element) is returned. The text in 2.1.1 should be updated to reflect this. o 6.2 This section lists additional "Negative Response" to . I think these should be moved to 2.1.1, where is defined. Also, two new error-tags are defined. If I understand the schema in rfc4741 correctly, it is not possible to define new error-tags. An error-app-tag can be used though. Also, I don't think start-stop-time-mismatch is needed - the standard 'invalid-value' can be used. o 6.3 I think that the replayCompleteNotifcation should be defined in the "urn:ietf:params:xml:ns:netconf:notification:1.0" schema. I.e. use a single schema (instead of three) for everything. Other Minor issues: o 1.2 "A capability may be advertised to announce that a server is able to process RPCs while a notification stream is active on a session." Should this text really be here? There is no such capability defined. o 2.1.1 "until the subscription to terminates." ^^^ ?? o 3.2.5.2 This section (including 3.2.5.2.1) seems to be redundant. Compare with 2.1.1. o 3.3 The schema uses xs:import to import a namespace which isn't used (1998/namespace), and two imports with a bad (?) schemaLocation. The prefix ncEvent is defined but not used. The documentation for namedProfile: "A named profile, which is a saved set of parameters associated that may be associated with zero or more active ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ?? subscriptions." o 3.3 You're using two top-level elements in this schema. This means that you can't create a single standalone XML instance document which lists the eventStreams and namedProfiles (since an XML document must have a single top-level element). This isn't an error per se, but I thought I should mention it. o 3.5 "Note that when multiple filters are specified," Multiple filters cannot be defined anymore, right? o 4 The xs:import in this schema seems to be copy-and-pasted from thee netconf schema. It is not needed here. /martin -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Feb 26 14:18:45 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLlMz-00087e-RY for netconf-archive@lists.ietf.org; Mon, 26 Feb 2007 14:18:45 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLlMx-0008DU-H1 for netconf-archive@lists.ietf.org; Mon, 26 Feb 2007 14:18:45 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HLlFH-000Jho-KW for netconf-data@psg.com; Mon, 26 Feb 2007 19:10:47 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [213.180.94.158] (helo=mail.tail-f.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HLlF2-000Jdn-G4 for netconf@ops.ietf.org; Mon, 26 Feb 2007 19:10:34 +0000 Received: from localhost (c213-100-166-193.swipnet.se [213.100.166.193]) by mail.tail-f.com (Postfix) with ESMTP id 294271B80C5 for ; Mon, 26 Feb 2007 20:10:24 +0100 (CET) Date: Mon, 26 Feb 2007 20:11:11 +0100 (CET) Message-Id: <20070226.201111.05571084.mbj@tail-f.com> To: netconf@ops.ietf.org Subject: Re: comments on draft-ietf-netconf-notification-06.txt From: Martin Bjorklund In-Reply-To: <20070225.234918.21759948.mbj@tail-f.com> References: <20070225.234918.21759948.mbj@tail-f.com> X-Mailer: Mew version 5.1.51 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 I forgot one comment. In 6.2, about the warning message, it says Error-info: : Timestamp of earliest event available for replay This element (log-starttime) should be defined in the schema. Also, the short description could be clarified. What exactly does "available for replay" mean? Does it mean available using the filters and access rules currently in effect? I assume it does not, since if it did, the warning would be pretty useless - the same info will be included in the first event replayed. /martin -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From j7nknkkytyrt3vettrt43@yahoo.co.jp Mon Feb 26 21:00:10 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLrdS-0003L1-Bf for netconf-archive@lists.ietf.org; Mon, 26 Feb 2007 21:00:10 -0500 Received: from [221.201.226.254] (helo=lists.ietf.org) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HLrdO-0001Vs-T6 for netconf-archive@lists.ietf.org; Mon, 26 Feb 2007 21:00:10 -0500 To: From: =?iso-2022-jp?B?d2ViGyRCQ0s9dxsoQm5ld3M=?= Subject: =?iso-2022-jp?B?GyRCRk1BMyROJWEhPCVrJEc8Ok5pQ1ckNyReJDkhIxsoQg==?= MIME-Version: 1.0 Reply-To: Content-Type:text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Spam-Score: 4.6 (++++) X-Scan-Signature: 93238566e09e6e262849b4f805833007 $B:#2s$O9-9pHq$N$_$G<}F~$rF@$F$$$kBg?M$N=P2q$$$N>l$r>R2p$7$^$9!#(B $BEvA3A4$F$N%3%s%F%s%D$rL5NA$GMxMQ=PMh$k$N$G0B?4$G$9!#(B $BF~8}$O$3$A$i"M!!(Bhttp://kzjw.com/ajn/ $B!!!!!!EPO?NA(B-----------------------$B!ZL5NA![(B $B!!!!!!%a!<%k$NAwpJs%a!<%k$rITMW$JJ}$O$*) id 1HMJgk-0002ip-Ar for netconf-data@psg.com; Wed, 28 Feb 2007 07:57:26 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [61.144.161.54] (helo=szxga02-in.huawei.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HMJgc-0002hs-Nj for netconf@ops.ietf.org; Wed, 28 Feb 2007 07:57:24 +0000 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JE500AVXXTWPL@szxga02-in.huawei.com> for netconf@ops.ietf.org; Wed, 28 Feb 2007 15:51:32 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JE500FCJXTVA9@szxga02-in.huawei.com> for netconf@ops.ietf.org; Wed, 28 Feb 2007 15:51:32 +0800 (CST) Received: from l48181 ([10.111.12.171]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JE5004KCXTRGQ@szxml03-in.huawei.com> for netconf@ops.ietf.org; Wed, 28 Feb 2007 15:51:31 +0800 (CST) Date: Wed, 28 Feb 2007 15:51:27 +0800 From: Li Yan Subject: RE: subtree filtering question In-reply-to: <4463A7EB.9010307@andybierman.com> To: 'Andy Bierman' , 'Martin Bjorklund' Cc: netconf@ops.ietf.org Message-id: <000001c75b0d$40ac61d0$ab0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdbDUAwJA13yZ8uSQ+jBIQwqA36UQ== Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.5 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba Hi, I have reviewed the following discussion. I found that Andy's answer conflict with the example in 6.4.7 of rfc4741. Section 6.4.7 says: The "barney" subtree filter contains three containment nodes (, , ), two content match nodes (, ), and one selector node (). The subtree selection criteria is not met because user "barney" is not a "superuser", and the entire subtree for "barney" (including its parent entry) is excluded from the filter output. Should the empty node be removed? /Yan > -----Original Message----- > From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On > Behalf Of Andy Bierman > Sent: Friday, May 12, 2006 5:09 AM > To: Martin Bjorklund > Cc: netconf@ops.ietf.org > Subject: Re: subtree filtering question > > Martin Bjorklund wrote: > > Hi again. > > > > Actually, I think that - from reading the specs - the answer is > > alternative 3. > > > > If this is the correct answer, the follow-up question is how subtree > > filtering is supposed to be used to match a notification. With XPath, > > it is defined that an expression which results in an empty node set is > > interpreted as 'false', and a non-empty node set is interpreted as > > 'true'. If the same rule is applies to subtree filtering, a filter > > such as that shown below (which produces a non-empty node set even for > > a "no match") would be interpreted as true. > > > You are correct. > I sure do not like it, but you are correct. > The same conceptual netconf filter in xpath and subtree form > will not return the same output. That is awful. > > I remember this issue came up, and the notion of removing the > entire 'dead-end' subtree from the result (back to the root) > was discussed. That was the original intent. > > The current text seems to indicate that (2) should be returned > if the container is totally empty, and (3) if > it is not empty, but the requested entry 'fred' does not exist. > > In either case, this is not very useful as-is for > notification filtering. Not so great for filtering either. > > > > > > > > /martin > > Andy > > > > > > > > > > Martin Bjorklund wrote: > >> Hi, > >> > >> While reading the subtree filtering specs again, I found something > >> which is a bit unclear. > >> > >> Consider this example from the draft. > >> > >> > >> > >> > >> > >> fred > >> > >> > >> > >> > >> > >> The question is what is the result if no user 'fred' exists? > >> > >> Is it (1): > >> > >> > >> > >> > >> or (2): > >> > >> > >> > >> > >> > >> > >> > >> > >> or maybe (3): > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Section 6.2.3 on containment node says: > >> > >> For each containment node specified in a subtree filter, all data > >> model instances which exactly match the specified namespaces, > >> element hierarchy, and any attribute match expressions are included > >> in the filter output. > >> > >> which seems to imply that alternative 3 is the right choice. But in > >> section 6.3. it says: > >> > >> If the entire subtree data-fragment filter (starting from the root > >> to the innermost element specified in the filter) exactly matches a > >> corresponding portion of the supported data model, then that node > >> and all its children are included in the result data. > >> > >> Which seems to indicate that alternative 1 is right. This might also > >> be implied by the text on content match nodes: > >> > >> o If any containment nodes are present in the sibling set then they > >> are processed further, and included if any nested filter criteria > >> are also met. > >> > >> (although this only seems to apply to containment nodes which are > >> siblings to content match nodes) > >> > >> > >> /martin > >> > >> -- > >> to unsubscribe send a message to netconf-request@ops.ietf.org with > >> the word 'unsubscribe' in a single line as the message text body. > >> archive: > > > > -- > > to unsubscribe send a message to netconf-request@ops.ietf.org with > > the word 'unsubscribe' in a single line as the message text body. > > archive: > > > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with > the word 'unsubscribe' in a single line as the message text body. > archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Feb 28 05:07:00 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMLi8-00057b-Pd for netconf-archive@lists.ietf.org; Wed, 28 Feb 2007 05:07:00 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMLi3-0003S4-G9 for netconf-archive@lists.ietf.org; Wed, 28 Feb 2007 05:07:00 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HMLaI-000EW4-Gr for netconf-data@psg.com; Wed, 28 Feb 2007 09:58:54 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [213.180.94.158] (helo=mail.tail-f.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HMLaF-000EVe-HD for netconf@ops.ietf.org; Wed, 28 Feb 2007 09:58:53 +0000 Received: from localhost (c213-100-166-193.swipnet.se [213.100.166.193]) by mail.tail-f.com (Postfix) with ESMTP id 9DDF01B80C4; Wed, 28 Feb 2007 10:58:49 +0100 (CET) Date: Wed, 28 Feb 2007 10:58:42 +0100 (CET) Message-Id: <20070228.105842.05559996.mbj@tail-f.com> To: liyan_77@huawei.com Cc: ietf@andybierman.com, netconf@ops.ietf.org Subject: Re: subtree filtering question From: Martin Bjorklund In-Reply-To: <000001c75b0d$40ac61d0$ab0c6f0a@china.huawei.com> References: <4463A7EB.9010307@andybierman.com> <000001c75b0d$40ac61d0$ab0c6f0a@china.huawei.com> X-Mailer: Mew version 5.1.51 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Li Yan wrote: > Hi, > I have reviewed the following discussion. > I found that Andy's answer conflict with the example in 6.4.7 of rfc4741. This was a discussion which was resolved later. > Section 6.4.7 says: > The "barney" subtree filter contains three containment nodes > (, , ), two content match nodes (, > ), and one selector node (). The subtree selection > criteria is not met because user "barney" is not a "superuser", and > the entire subtree for "barney" (including its parent entry) > is excluded from the filter output. > > Should the empty node be removed? Yes. /martin -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Feb 28 18:25:06 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMYAU-0006xa-Oy for netconf-archive@lists.ietf.org; Wed, 28 Feb 2007 18:25:06 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMYAR-0000NV-Cy for netconf-archive@lists.ietf.org; Wed, 28 Feb 2007 18:25:06 -0500 Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HMY3e-000FyE-9g for netconf-data@psg.com; Wed, 28 Feb 2007 23:18:02 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7 Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HMY3b-000Fy2-Qm for netconf@ops.ietf.org; Wed, 28 Feb 2007 23:18:00 +0000 Received: from ind-dkim-2.cisco.com ([64.104.140.59]) by sj-iport-6.cisco.com with ESMTP; 28 Feb 2007 15:17:58 -0800 X-IronPort-AV: i="4.14,232,1170662400"; d="scan'208"; a="116899530:sNHT40650543" Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by ind-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l1SNHu0L012783 for ; Thu, 1 Mar 2007 04:47:57 +0530 Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l1SNHtU3019466 for ; Thu, 1 Mar 2007 07:17:56 +0800 (CST) Received: from xmb-hkg-411.apac.cisco.com ([64.104.123.77]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Mar 2007 07:17:54 +0800 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 Subject: am I missing some error code Date: Thu, 1 Mar 2007 07:17:54 +0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: am I missing some error code Thread-Index: Acdbjqy0wkr2+fXeR9mO+7EwNltCBg== From: "James Balestriere \(jbalestr\)" To: X-OriginalArrivalTime: 28 Feb 2007 23:17:54.0685 (UTC) FILETIME=[ACDAC2D0:01C75B8E] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=624; t=1172704677; x=1173568677; c=relaxed/simple; s=inddkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jbalestr@cisco.com; z=From:=20=22James=20Balestriere=20\(jbalestr\)=22=20 |Subject:=20am=20I=20missing=20some=20error=20code |Sender:=20; bh=GBID7hvGZZnxDhBJNZnz8zOOmEjVRJgBV8PO0MnMsLE=; b=zwNNLdEVcGqpGxNkRFhuXLwsMgepIpA0RxJmrjGqYq1AjsucdzCZvB79zgC8lJubL0WP++02 TMmlLgmGBWJrjIlkXqtxyf7yS5UeL5ZFm6LEyT7hJ2lBj24KDmhEPGRo; Authentication-Results: ind-dkim-2; header.From=jbalestr@cisco.com; dkim=pass ( sig from cisco.com/inddkim2002 verified; ); Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Hi , Someone sends this request =20 and gets an operation-failed error and starts questioning the capabilities my box supports. But, when I go through the error codes in Appendix A, I do not see any error code which deals with malformed XML so I have to use the catch-all operation-failed.=20 I think in some cases returning operation-failed to malformed xml could be a bit misleading. Have I missed some error code somewhere which is more appropriate ? or do we need to add one ? James. -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: