From phil@juniper.net Wed Dec 1 05:15:34 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE35E28C21B for ; Wed, 1 Dec 2010 05:15:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.585 X-Spam-Level: X-Spam-Status: No, score=-6.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hphYHhwuUHPN for ; Wed, 1 Dec 2010 05:15:33 -0800 (PST) Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id 16A5B28C129 for ; Wed, 1 Dec 2010 05:15:31 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKTPZKvGV0xY1zNiAPOdNnfA2ilHoSKbNB@postini.com; Wed, 01 Dec 2010 05:16:47 PST Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Dec 2010 05:12:34 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id oB1DCYU95427; Wed, 1 Dec 2010 05:12:34 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id oB1CovZq061932; Wed, 1 Dec 2010 12:50:58 GMT (envelope-from phil@idle.juniper.net) Message-ID: <201012011250.oB1CovZq061932@idle.juniper.net> To: Martin Bjorklund In-Reply-To: <20101130.212537.163045157.mbj@tail-f.com> Date: Wed, 1 Dec 2010 07:50:57 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 13:15:34 -0000 Martin Bjorklund writes: >> C: >> C: #271 >> C: >Yes this is correct. I find the leading LF somewhat odd. Should we consider changing this to be: chunk = "#" chunk-size LF chunk-data LF Not a big dea, but.... Thanks, Phil From j.schoenwaelder@jacobs-university.de Wed Dec 1 06:10:51 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FB373A6B38 for ; Wed, 1 Dec 2010 06:10:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.095 X-Spam-Level: X-Spam-Status: No, score=-103.095 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PfsyeFcsXiPt for ; Wed, 1 Dec 2010 06:10:42 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id B474A3A6B48 for ; Wed, 1 Dec 2010 06:10:42 -0800 (PST) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id E9B0EC03F0; Wed, 1 Dec 2010 15:11:55 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id ExJhEblGkunF; Wed, 1 Dec 2010 15:11:55 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id EA7CFC0458; Wed, 1 Dec 2010 15:11:54 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 243BB15D8959; Wed, 1 Dec 2010 15:11:53 +0100 (CET) Date: Wed, 1 Dec 2010 15:11:53 +0100 From: Juergen Schoenwaelder To: Phil Shafer Message-ID: <20101201141153.GA1674@elstar.local> Mail-Followup-To: Phil Shafer , Martin Bjorklund , netconf@ietf.org References: <20101130.212537.163045157.mbj@tail-f.com> <201012011250.oB1CovZq061932@idle.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201012011250.oB1CovZq061932@idle.juniper.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 14:10:51 -0000 On Wed, Dec 01, 2010 at 07:50:57AM -0500, Phil Shafer wrote: > Martin Bjorklund writes: > >> C: > >> C: #271 > >> C: > >Yes this is correct. > > I find the leading LF somewhat odd. Should we consider changing > this to be: > > chunk = "#" chunk-size LF chunk-data LF > > Not a big dea, but.... I prefer if the # mark is always in column 0. Since there is no need to end the XML with a LF (or is there?), there does not need to be an empty line. /js PS: I think we are taking the examples too literally. -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From phil@juniper.net Wed Dec 1 07:59:34 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00DE03A6C7E for ; Wed, 1 Dec 2010 07:59:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.587 X-Spam-Level: X-Spam-Status: No, score=-6.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lKPSBTxOhbev for ; Wed, 1 Dec 2010 07:59:33 -0800 (PST) Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by core3.amsl.com (Postfix) with ESMTP id E77383A6BC1 for ; Wed, 1 Dec 2010 07:59:28 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTPZxKkRztJdDyeqna50NtvUIx9K3hPQO@postini.com; Wed, 01 Dec 2010 08:00:47 PST Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Dec 2010 07:56:16 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id oB1FuGU68751; Wed, 1 Dec 2010 07:56:16 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id oB1FYefP063137; Wed, 1 Dec 2010 15:34:40 GMT (envelope-from phil@idle.juniper.net) Message-ID: <201012011534.oB1FYefP063137@idle.juniper.net> To: Juergen Schoenwaelder In-Reply-To: <20101201141153.GA1674@elstar.local> Date: Wed, 1 Dec 2010 10:34:40 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 15:59:34 -0000 Juergen Schoenwaelder writes: >I prefer if the # mark is always in column 0. Since there is no need >to end the XML with a LF (or is there?), there does not need to be an >empty line. My suggestion does not alter "# mark is always in column 0". I'm suggesting moving the LF from the start to the end of the production: vv---- Move this LF ... - chunk = LF "#" chunk-size LF chunk-data + chunk = "#" chunk-size LF chunk-data LF ... to the end over here ---^^ In both rules, the "#" will always be in column 0. The only real difference is that the first message starts with a "#" not with a LF. old: LF # len LF msg LF # len LF msg LF # len LF msg LF # len LF msg ... new: # len LF msg LF # len LF msg LF # len LF msg LF # len LF msg LF ... So the message sending code will change like: - printf("\n#%u\n%s", strlen(msg), msg); + printf("#%u\n%s\n", strlen(msg), msg); IMHO this is cleaner (trailing LF is more normal than a leading one) and makes the initial message (which we'll have in our examples) less odd. >PS: I think we are taking the examples too literally. If the examples are not literally correct, then they are broken and will mislead implementors. Thanks, Phil From mbj@tail-f.com Wed Dec 1 08:38:26 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F13B23A6C55 for ; Wed, 1 Dec 2010 08:38:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id phwpkV+ZxWH1 for ; Wed, 1 Dec 2010 08:38:25 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 1785B3A6C60 for ; Wed, 1 Dec 2010 08:38:23 -0800 (PST) Received: from localhost (c213-100-166-57.swipnet.se [213.100.166.57]) by mail.tail-f.com (Postfix) with ESMTPSA id 0039A616001; Wed, 1 Dec 2010 17:39:24 +0100 (CET) Date: Wed, 01 Dec 2010 17:39:24 +0100 (CET) Message-Id: <20101201.173924.77794571.mbj@tail-f.com> To: phil@juniper.net From: Martin Bjorklund In-Reply-To: <201012011534.oB1FYefP063137@idle.juniper.net> References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 16:38:26 -0000 Hi, Phil Shafer wrote: > Juergen Schoenwaelder writes: > >I prefer if the # mark is always in column 0. Since there is no need > >to end the XML with a LF (or is there?), there does not need to be an > >empty line. > > My suggestion does not alter "# mark is always in column 0". But it does. Consider the hello + first rpc from the client: C: C: C: C: C: urn:ietf:params:xml:ns:netconf:base:1.0 C: C: C: C: ]]>]]> C: #271 C: C: C: ... The client sends ]]>]]>, and that marks the end of the hello msg. If the LF is not present before the first chunk we would get ... C: C: ]]>]]>#271 C: ... since the sequence is "]]>]]>", not "]]>]]>\n". Same issue after each message, since an XML message doesn't have to end with a LF. > >PS: I think we are taking the examples too literally. > > If the examples are not literally correct, then they are broken > and will mislead implementors. Then we'd have to say that in the examples each line is ended with a single LF, except the line with ]]>]]>. /martin From j.schoenwaelder@jacobs-university.de Wed Dec 1 08:52:54 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BB473A6C0F for ; Wed, 1 Dec 2010 08:52:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.099 X-Spam-Level: X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DunllbIclH9z for ; Wed, 1 Dec 2010 08:52:53 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 2FCC83A69C5 for ; Wed, 1 Dec 2010 08:52:52 -0800 (PST) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id B6192C0241; Wed, 1 Dec 2010 17:54:05 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id rZGb6pb41dZj; Wed, 1 Dec 2010 17:54:05 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1A95BC0178; Wed, 1 Dec 2010 17:54:05 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 81C5915D8C8C; Wed, 1 Dec 2010 17:54:04 +0100 (CET) Date: Wed, 1 Dec 2010 17:54:04 +0100 From: Juergen Schoenwaelder To: Phil Shafer Message-ID: <20101201165403.GA2247@elstar.local> Mail-Followup-To: Phil Shafer , Martin Bjorklund , netconf@ietf.org References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201012011534.oB1FYefP063137@idle.juniper.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 16:52:54 -0000 On Wed, Dec 01, 2010 at 10:34:40AM -0500, Phil Shafer wrote: > Juergen Schoenwaelder writes: > >I prefer if the # mark is always in column 0. Since there is no need > >to end the XML with a LF (or is there?), there does not need to be an > >empty line. > > My suggestion does not alter "# mark is always in column 0". I'm > suggesting moving the LF from the start to the end of the production: > > vv---- Move this LF ... > - chunk = LF "#" chunk-size LF chunk-data > + chunk = "#" chunk-size LF chunk-data LF > ... to the end over here ---^^ > > In both rules, the "#" will always be in column 0. The only real > difference is that the first message starts with a "#" not with a > LF. Sorry, now I understand. I fully agree. > >PS: I think we are taking the examples too literally. > > If the examples are not literally correct, then they are broken > and will mislead implementors. My fear is that people will believe there must be an empty line between the closing XML tag and the # mark while this is really just an artefact of translating the whitespace literally. I would rather remove the empty lines (and maybe add a clarifying sentence that the translation is not necessaryly preserving all whitespace). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From biermana@Brocade.com Wed Dec 1 09:02:45 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2631E3A6C80 for ; Wed, 1 Dec 2010 09:02:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.183 X-Spam-Level: X-Spam-Status: No, score=-2.183 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HW4o3BI6x3wt for ; Wed, 1 Dec 2010 09:02:44 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id 313E628C16F for ; Wed, 1 Dec 2010 09:02:08 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oB1H23Wd008529; Wed, 1 Dec 2010 09:03:21 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.141.11]) by mx0b-000f0801.pphosted.com with ESMTP id swrgq023c-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 01 Dec 2010 09:03:20 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE02.corp.brocade.com (144.49.141.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Dec 2010 09:09:03 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Wed, 1 Dec 2010 09:03:19 -0800 From: Andy Bierman To: Juergen Schoenwaelder , Phil Shafer Date: Wed, 1 Dec 2010 09:03:17 -0800 Thread-Topic: [Netconf] WG Last Call on one more change to RFC4742bis Thread-Index: AcuReGE3nC1dM1oKQiO0aErQZ9n+JAAANgtQ Message-ID: References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> <20101201165403.GA2247@elstar.local> In-Reply-To: <20101201165403.GA2247@elstar.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-01_08:2010-12-01, 2010-12-01, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012010083 Cc: "netconf@ietf.org" Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 17:02:45 -0000 Hi, It is very important to get the examples correct. People read the normative text, but check their code against the examples. I agree with Martin that a sentence explaining the newline details would help. The examples should be exactly correct -- not altered in any way for readability or RFC Editor formatting. Andy -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Juergen Schoenwaelder Sent: Wednesday, December 01, 2010 8:54 AM To: Phil Shafer Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis On Wed, Dec 01, 2010 at 10:34:40AM -0500, Phil Shafer wrote: > Juergen Schoenwaelder writes: > >I prefer if the # mark is always in column 0. Since there is no need > >to end the XML with a LF (or is there?), there does not need to be an > >empty line. >=20 > My suggestion does not alter "# mark is always in column 0". I'm > suggesting moving the LF from the start to the end of the production: >=20 > vv---- Move this LF ... > - chunk =3D LF "#" chunk-size LF chunk-data > + chunk =3D "#" chunk-size LF chunk-data LF > ... to the end over here ---^^ >=20 > In both rules, the "#" will always be in column 0. The only real > difference is that the first message starts with a "#" not with a > LF. Sorry, now I understand. I fully agree. =20 > >PS: I think we are taking the examples too literally. >=20 > If the examples are not literally correct, then they are broken > and will mislead implementors. My fear is that people will believe there must be an empty line between the closing XML tag and the # mark while this is really just an artefact of translating the whitespace literally. I would rather remove the empty lines (and maybe add a clarifying sentence that the translation is not necessaryly preserving all whitespace). /js --=20 Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From phil@juniper.net Wed Dec 1 09:14:26 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E1503A6C75 for ; Wed, 1 Dec 2010 09:14:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.588 X-Spam-Level: X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGSL8hFKsJoU for ; Wed, 1 Dec 2010 09:14:25 -0800 (PST) Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 4DEB73A6C1C for ; Wed, 1 Dec 2010 09:14:21 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTPaCt6GfYb7t+8qpDJzwlq8rNkL0tVMO@postini.com; Wed, 01 Dec 2010 09:15:39 PST Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Dec 2010 09:11:35 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id oB1HBYU00809; Wed, 1 Dec 2010 09:11:35 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id oB1GnwUG063890; Wed, 1 Dec 2010 16:49:58 GMT (envelope-from phil@idle.juniper.net) Message-ID: <201012011649.oB1GnwUG063890@idle.juniper.net> To: Martin Bjorklund In-Reply-To: <20101201.173924.77794571.mbj@tail-f.com> Date: Wed, 1 Dec 2010 11:49:58 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 17:14:26 -0000 Martin Bjorklund writes: >But it does. Consider the hello + first rpc from the client: Rats. Hadn't thought about the hello. Could you please add text to explain this, since the normal reader (me ;^) will miss it completely? I guess adding a special LF for the first message would not be slick. Thanks, Phil From kwatsen@juniper.net Wed Dec 1 09:32:02 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCE223A6C82 for ; Wed, 1 Dec 2010 09:32:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdcZsv2dV3nc for ; Wed, 1 Dec 2010 09:32:00 -0800 (PST) Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 369CC3A6C13 for ; Wed, 1 Dec 2010 09:31:25 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTPaGtV0RF8xav9wJN5qIaSSlWrWDSAXY@postini.com; Wed, 01 Dec 2010 09:32:39 PST Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Wed, 1 Dec 2010 09:32:29 -0800 From: Kent Watsen To: Phil Shafer , Juergen Schoenwaelder Date: Wed, 1 Dec 2010 09:32:27 -0800 Thread-Topic: [Netconf] WG Last Call on one more change to RFC4742bis Thread-Index: AcuRcOxt8qglfAd8SsmPBmeUsupVygABJ8rw Message-ID: <84600D05C20FF943918238042D7670FD374405EA0B@EMBX01-HQ.jnpr.net> References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> In-Reply-To: <201012011534.oB1FYefP063137@idle.juniper.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "netconf@ietf.org" Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 17:32:03 -0000 If we move the LF to the end of "chunk", should we also remove the LF at th= e beginning of "end-of-chunks", so that there won't be a blank/empty line b= efore the "##"? Regarding Martin's concern for "]]>]]>#271", I don't think it's a problem, = being a streaming protocol, but we could let an LF show up at the beginning= of a chunked message: Chunked-Message =3D 0*1LF 1*chunk end-of-chunks Though as Phil points out, this wouldn't be slick... Thanks, Kent -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Phil Shafer Sent: Wednesday, December 01, 2010 10:35 AM To: Juergen Schoenwaelder Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis Juergen Schoenwaelder writes: >I prefer if the # mark is always in column 0. Since there is no need >to end the XML with a LF (or is there?), there does not need to be an >empty line. My suggestion does not alter "# mark is always in column 0". I'm suggesting moving the LF from the start to the end of the production: vv---- Move this LF ... - chunk =3D LF "#" chunk-size LF chunk-data + chunk =3D "#" chunk-size LF chunk-data LF ... to the end over here ---^^ In both rules, the "#" will always be in column 0. The only real difference is that the first message starts with a "#" not with a LF. old: LF # len LF msg LF # len LF msg LF # len LF msg LF # len LF msg ... new: # len LF msg LF # len LF msg LF # len LF msg LF # len LF msg LF ... So the message sending code will change like: - printf("\n#%u\n%s", strlen(msg), msg); + printf("#%u\n%s\n", strlen(msg), msg); IMHO this is cleaner (trailing LF is more normal than a leading one) and makes the initial message (which we'll have in our examples) less odd. >PS: I think we are taking the examples too literally. If the examples are not literally correct, then they are broken and will mislead implementors. Thanks, Phil _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From biermana@Brocade.com Wed Dec 1 09:34:23 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 586B13A6B48 for ; Wed, 1 Dec 2010 09:34:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.191 X-Spam-Level: X-Spam-Status: No, score=-2.191 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhXUBcihFy4M for ; Wed, 1 Dec 2010 09:34:22 -0800 (PST) Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by core3.amsl.com (Postfix) with ESMTP id C514D3A6AAC for ; Wed, 1 Dec 2010 09:34:21 -0800 (PST) Received: from pps.filterd (m0000542 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oB1HWjjN009437; Wed, 1 Dec 2010 09:35:35 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.141.11]) by mx0a-000f0801.pphosted.com with ESMTP id swpabg4g9-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 01 Dec 2010 09:35:35 -0800 Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXEDGE02.corp.brocade.com (144.49.141.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Dec 2010 09:41:18 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Wed, 1 Dec 2010 09:35:34 -0800 From: Andy Bierman To: Kent Watsen , Phil Shafer , "Juergen Schoenwaelder" Date: Wed, 1 Dec 2010 09:35:32 -0800 Thread-Topic: [Netconf] WG Last Call on one more change to RFC4742bis Thread-Index: AcuRcOxt8qglfAd8SsmPBmeUsupVygABJ8rwAAIabRA= Message-ID: References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> <84600D05C20FF943918238042D7670FD374405EA0B@EMBX01-HQ.jnpr.net> In-Reply-To: <84600D05C20FF943918238042D7670FD374405EA0B@EMBX01-HQ.jnpr.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-01_08:2010-12-01, 2010-12-01, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012010089 Cc: "netconf@ietf.org" Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 17:34:23 -0000 Hi, I prefer a deterministic algorithm. Letting the sender choose multiple forms is not a feature. IMO, a line that starts with a NL is not a bug. Let's not solve a non-problem by introducing flexibility. Andy -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Kent Watsen Sent: Wednesday, December 01, 2010 9:32 AM To: Phil Shafer; Juergen Schoenwaelder Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis If we move the LF to the end of "chunk", should we also remove the LF at th= e beginning of "end-of-chunks", so that there won't be a blank/empty line b= efore the "##"? Regarding Martin's concern for "]]>]]>#271", I don't think it's a problem, = being a streaming protocol, but we could let an LF show up at the beginning= of a chunked message: Chunked-Message =3D 0*1LF 1*chunk end-of-chunks Though as Phil points out, this wouldn't be slick... Thanks, Kent -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Phil Shafer Sent: Wednesday, December 01, 2010 10:35 AM To: Juergen Schoenwaelder Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis Juergen Schoenwaelder writes: >I prefer if the # mark is always in column 0. Since there is no need >to end the XML with a LF (or is there?), there does not need to be an >empty line. My suggestion does not alter "# mark is always in column 0". I'm suggesting moving the LF from the start to the end of the production: vv---- Move this LF ... - chunk =3D LF "#" chunk-size LF chunk-data + chunk =3D "#" chunk-size LF chunk-data LF ... to the end over here ---^^ In both rules, the "#" will always be in column 0. The only real difference is that the first message starts with a "#" not with a LF. old: LF # len LF msg LF # len LF msg LF # len LF msg LF # len LF msg ... new: # len LF msg LF # len LF msg LF # len LF msg LF # len LF msg LF ... So the message sending code will change like: - printf("\n#%u\n%s", strlen(msg), msg); + printf("#%u\n%s\n", strlen(msg), msg); IMHO this is cleaner (trailing LF is more normal than a leading one) and makes the initial message (which we'll have in our examples) less odd. >PS: I think we are taking the examples too literally. If the examples are not literally correct, then they are broken and will mislead implementors. Thanks, Phil _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From j.schoenwaelder@jacobs-university.de Wed Dec 1 14:57:14 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EB053A6811 for ; Wed, 1 Dec 2010 14:57:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.102 X-Spam-Level: X-Spam-Status: No, score=-103.102 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBA1Aan6gVKp for ; Wed, 1 Dec 2010 14:57:13 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id D09BC3A6808 for ; Wed, 1 Dec 2010 14:57:12 -0800 (PST) Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6EA58C0022; Wed, 1 Dec 2010 23:58:26 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id QRN856geQA6U; Wed, 1 Dec 2010 23:58:25 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7770DC0019; Wed, 1 Dec 2010 23:58:25 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id AD8F415D9215; Wed, 1 Dec 2010 23:58:24 +0100 (CET) Date: Wed, 1 Dec 2010 23:58:23 +0100 From: Juergen Schoenwaelder To: Andy Bierman Message-ID: <20101201225823.GA2629@elstar.local> Mail-Followup-To: Andy Bierman , Phil Shafer , "netconf@ietf.org" References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> <20101201165403.GA2247@elstar.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "netconf@ietf.org" Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 22:57:14 -0000 On Wed, Dec 01, 2010 at 09:03:17AM -0800, Andy Bierman wrote: > Hi, > > It is very important to get the examples correct. > People read the normative text, but check their code against > the examples. I agree with Martin that a sentence explaining > the newline details would help. The examples should be exactly > correct -- not altered in any way for readability or RFC Editor > formatting. He? I want them correct, but not misguiding. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From biermana@Brocade.com Wed Dec 1 23:52:00 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AADF3A6827 for ; Wed, 1 Dec 2010 23:52:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.198 X-Spam-Level: X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46+iS6xzIQDX for ; Wed, 1 Dec 2010 23:51:59 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id 0FD3A3A6818 for ; Wed, 1 Dec 2010 23:51:58 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oB27qiGs005650; Wed, 1 Dec 2010 23:52:44 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.140.11]) by mx0b-000f0801.pphosted.com with ESMTP id sx45f82b0-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 01 Dec 2010 23:52:44 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE01.corp.brocade.com (144.49.140.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Dec 2010 23:53:44 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Wed, 1 Dec 2010 23:52:42 -0800 From: Andy Bierman To: Juergen Schoenwaelder Date: Wed, 1 Dec 2010 23:52:39 -0800 Thread-Topic: [Netconf] WG Last Call on one more change to RFC4742bis Thread-Index: AcuRq0XKeLEipdOESOCKynL5Ai4PfgAShkqQ Message-ID: References: <20101201141153.GA1674@elstar.local> <201012011534.oB1FYefP063137@idle.juniper.net> <20101201165403.GA2247@elstar.local> <20101201225823.GA2629@elstar.local> In-Reply-To: <20101201225823.GA2629@elstar.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-02_03:2010-12-02, 2010-12-02, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012010248 Cc: "netconf@ietf.org" Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2010 07:52:00 -0000 We all want them correct and not misguiding. Some note is needed so it is obvious why 1 example looks different than the rest. IMO, this document needs another WGLC. I think we should all re-read the entire 4742bis (and 4741bis related sections) to make sure we didn't break anything at the last minute. Sort of a regression test for an I-D. Andy -----Original Message----- From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de]=20 Sent: Wednesday, December 01, 2010 2:58 PM To: Andy Bierman Cc: Phil Shafer; netconf@ietf.org Subject: Re: [Netconf] WG Last Call on one more change to RFC4742bis On Wed, Dec 01, 2010 at 09:03:17AM -0800, Andy Bierman wrote: > Hi, >=20 > It is very important to get the examples correct. > People read the normative text, but check their code against > the examples. I agree with Martin that a sentence explaining > the newline details would help. The examples should be exactly > correct -- not altered in any way for readability or RFC Editor > formatting. He? I want them correct, but not misguiding. /js --=20 Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From kwatsen@juniper.net Thu Dec 2 20:19:16 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6C6B28C14E for ; Thu, 2 Dec 2010 20:19:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63gl5j2NbqG0 for ; Thu, 2 Dec 2010 20:19:13 -0800 (PST) Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by core3.amsl.com (Postfix) with ESMTP id A57203A6A59 for ; Thu, 2 Dec 2010 20:19:13 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKTPhwDuowf2Lal5SX/O70zRk4Qo/9kCyt@postini.com; Thu, 02 Dec 2010 20:20:30 PST Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Thu, 2 Dec 2010 20:18:21 -0800 From: Kent Watsen To: "netconf@ietf.org" Date: Thu, 2 Dec 2010 20:18:20 -0800 Thread-Topic: 4741bis-04 has non-deterministic schema Thread-Index: AcuSoR4T/0jFyft0TaKOVVwvT5veKg== Message-ID: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_84600D05C20FF943918238042D7670FD374419AF64EMBX01HQjnprn_" MIME-Version: 1.0 Subject: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 04:19:16 -0000 --_000_84600D05C20FF943918238042D7670FD374419AF64EMBX01HQjnprn_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I loaded the schema from 4741bis-04 into XMLSpy (2006) and got the followin= g error: '' makes the content model non-deterministic = against ''. Removing the element as follows: - Then gives the error: '' makes the content model n= on-deterministic against ''. Removing the element as follows: - Enables the XSD to be valid. While this schema will still validate everyth= ing from before, it's not ideal either as it doesn't explicitly show the or elements anymore, but I don't see how else to make it val= id... BTW, I believe there is an error in the netconf-monitoring RFC, shouldn't t= his example be updated as follows? - - Thanks, Kent --_000_84600D05C20FF943918238042D7670FD374419AF64EMBX01HQjnprn_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I loaded the schema from 4741bis-04 into XMLSpy (2006) and got the fol= lowing error:
 
‘<xs:element ref=3D”rpc-error”>’ makes t= he content model non-deterministic against ‘<xs:any namespace-R= 20;##any”>’.
 
 
Removing the <rpc-error> element as follows:
 
     <xs:= group name=3D"rpcResponse">
     &n= bsp; <xs:sequence>
-     &= nbsp;  <xs:element ref=3D"rpc-error"
-     &= nbsp;           &nbs= p;  minOccurs=3D"0" maxOccurs=3D"unbounded"/>
     &n= bsp;   <xs:any namespace=3D"##any" processContents= =3D"lax"
     &n= bsp;           minOccurs= =3D"0" maxOccurs=3D"unbounded"/>
     &n= bsp; </xs:sequence>
     </xs= :group>
 
 
Then gives the error:  ‘<xs:element name=3D”okR= 21;>’ makes the content model non-deterministic against ‘<= ;xs:any namespace-“##any”>’.
 
 
Removing the <ok> element as follows:
 
     <xs:= complexType name=3D"rpcReplyType">
     &n= bsp; <xs:choice>
-     &= nbsp;   <xs:element name=3D"ok"/>
     &n= bsp;   <xs:group ref=3D"rpcResponse"/>
     &n= bsp; </xs:choice>
     &n= bsp; <xs:attribute name=3D"message-id" type=3D"messageIdT= ype"
     &n= bsp;   use=3D"optional"/>
     &n= bsp; <!--
     &n= bsp;   Any attributes supplied with <rpc> element must be r= eturned
     &n= bsp;   on <rpc-reply>.
     &n= bsp; -->
     &n= bsp; <xs:anyAttribute processContents=3D"lax"/>
     </xs= :complexType>
 
 
Enables the XSD to be valid.  While this schema will still valida= te everything from before, it’s not ideal either as it doesn’t = explicitly show the <ok> or <rpc-error> elements anymore, but I= don’t see how else to make it valid…
 
 
 
BTW, I believe there is an error in the netconf-monitoring RFC, should= n’t this example be updated as follows?
 
     &n= bsp; <rpc-reply message-id=3D"101"
     &n= bsp;     xmlns=3D"urn:ietf:params:xml:ns:netconf:b= ase:1.0">
-      = <data>
      &= nbsp;    <netconf-state
      &= nbsp;      xmlns=3D"urn:ietf:params:xml:ns:ya= ng:ietf-netconf-monitoring">
      &= nbsp;      <schemas>
     &n= bsp;         <!-- SNIP -->
      &= nbsp;      </schemas>
      &= nbsp;   </netconf-state>
-     &= nbsp; </data>
     &n= bsp; </rpc-reply>
 
 
Thanks,
Kent
 
 
 --_000_84600D05C20FF943918238042D7670FD374419AF64EMBX01HQjnprn_-- From biermana@Brocade.com Thu Dec 2 20:34:46 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDA4D3A6888 for ; Thu, 2 Dec 2010 20:34:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.203 X-Spam-Level: X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3tfP7WpfOb3g for ; Thu, 2 Dec 2010 20:34:43 -0800 (PST) Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by core3.amsl.com (Postfix) with ESMTP id 880803A686A for ; Thu, 2 Dec 2010 20:34:43 -0800 (PST) Received: from pps.filterd (m0000542 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oB34Y232026651; Thu, 2 Dec 2010 20:36:00 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.140.11]) by mx0a-000f0801.pphosted.com with ESMTP id sxq0h81xx-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 02 Dec 2010 20:35:59 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE01.corp.brocade.com (144.49.140.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 2 Dec 2010 20:37:00 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Thu, 2 Dec 2010 20:35:59 -0800 From: Andy Bierman To: Kent Watsen , "netconf@ietf.org" Date: Thu, 2 Dec 2010 20:35:57 -0800 Thread-Topic: 4741bis-04 has non-deterministic schema Thread-Index: AcuSoR4T/0jFyft0TaKOVVwvT5veKgAAhBHA Message-ID: References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> In-Reply-To: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABE0HQ1EXCH01corp_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-03_02:2010-12-03, 2010-12-03, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012020192 Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 04:34:47 -0000 --_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABE0HQ1EXCH01corp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, These XSD changes do not reflect the correct syntax. Maybe another variant is needed because you can't just remove from the= schema. Also, the monitoring example is correct. The response is for the following . The operation returns everything within the element . Andy From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Kent Watsen Sent: Thursday, December 02, 2010 8:18 PM To: netconf@ietf.org Subject: [Netconf] 4741bis-04 has non-deterministic schema I loaded the schema from 4741bis-04 into XMLSpy (2006) and got the followin= g error: '' makes the content model non-deterministic = against ''. Removing the element as follows: - Then gives the error: '' makes the content model n= on-deterministic against ''. Removing the element as follows: - Enables the XSD to be valid. While this schema will still validate everyth= ing from before, it's not ideal either as it doesn't explicitly show the or elements anymore, but I don't see how else to make it val= id... BTW, I believe there is an error in the netconf-monitoring RFC, shouldn't t= his example be updated as follows? - - Thanks, Kent --_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABE0HQ1EXCH01corp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,<= /o:p>

 

These XSD changes do not reflect the correct synta= x.

Maybe another variant i= s needed because you can’t just remove <ok> from the schema.

 

=

Also, the monitoring example is correct.

The response is for the followin= g <get>.

The <get= > operation returns everything within the element <data>.

 

&= lt;rpc message-id=3D"101"

  &= nbsp;  xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0">=

  <get>

&nb= sp;   <filter type=3D"subtree">=

      <netconf-state xmlns=3D

      "urn:ietf:params:xml:= ns:yang:ietf-netconf-monitoring">

 &= nbsp;      <schemas/>

<= p class=3DMsoNormal>      </netconf-state>=

    </filter>

&nb= sp; </get>

</rpc>

 

 <= /o:p>

 

Andy

 

 

From: netconf-bounces@ietf.or= g [mailto:netconf-bounces@ietf.org] On Behalf Of Kent Watsen
S= ent: Thursday, December 02, 2010 8:18 PM
To: netconf@ietf.org=
Subject: [Netconf] 4741bis-04 has non-deterministic schema<= /o:p>

 

=

I loaded the schema from 4741bis-04 into XMLSpy (2006) and go= t the following error:

 =

‘<xs:element ref=3D= ”rpc-error”>’ makes the content model non-deterministi= c against ‘<xs:any namespace-“##any”>’. =

 

 

Re= moving the <rpc-error> element as follows:

 

  = ;   <xs:group name=3D"rpcResponse">

       <xs:sequenc= e>

-     &= nbsp;  <xs:element ref=3D"rpc-error"

-         &nb= sp;          minOccurs=3D"= ;0" maxOccurs=3D"unbounded"/>

=

         <xs:any names= pace=3D"##any" processContents=3D"lax"

         =         minOccurs=3D"0" maxOcc= urs=3D"unbounded"/>

&nb= sp;      </xs:sequence>

     </xs:group>

 

 

Then gives th= e error:  ‘<xs:element name=3D”ok”>’ mak= es the content model non-deterministic against ‘<xs:any namespace-= “##any”>’.

 

 

Removing the <ok> element as fol= lows:

 

     <xs:complexType name=3D&qu= ot;rpcReplyType">

  =      <xs:choice>

=

-         <xs:element name= =3D"ok"/>

  &nb= sp;      <xs:group ref=3D"rpcResponse"= ;/>

     &= nbsp; </xs:choice>

  &= nbsp;    <xs:attribute name=3D"message-id" type= =3D"messageIdType"

 &nb= sp;       use=3D"optional"/>

       <= !--

     &nbs= p;   Any attributes supplied with <rpc> element must be ret= urned

     &n= bsp;   on <rpc-reply>.

       -->

       <xs:anyAttribute processCont= ents=3D"lax"/>

 &nbs= p;   </xs:complexType>

 

 <= /o:p>

Enables the XSD to be valid. = While this schema will still validate everything from before, it’s n= ot ideal either as it doesn’t explicitly show the <ok> or <r= pc-error> elements anymore, but I don’t see how else to make it va= lid…

 <= /span>

 

<= p class=3DMsoNormal> 

BTW, I be= lieve there is an error in the netconf-monitoring RFC, shouldn’t this= example be updated as follows?

 

    &nb= sp;  <rpc-reply message-id=3D"101"

<= /div>

          = xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0">=

-       <data>

       &nb= sp;   <netconf-state

&nb= sp;            xmlns=3D&q= uot;urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">

        &nbs= p;    <schemas>

&= nbsp;           &nbs= p;  <!-- SNIP -->

 &nb= sp;           </schemas>= =

       =    </netconf-state>

-&= nbsp;      </data>

       </rpc-reply><= span style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>

 

 

Thank= s,

Kent

=

 

 

= --_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABE0HQ1EXCH01corp_-- From wwwrun@rfc-editor.org Thu Dec 2 21:28:45 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED6BF3A6A62 for ; Thu, 2 Dec 2010 21:28:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.341 X-Spam-Level: X-Spam-Status: No, score=-102.341 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dpzAv-1AvKCX for ; Thu, 2 Dec 2010 21:28:45 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 273773A6A61 for ; Thu, 2 Dec 2010 21:28:45 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 0FBC1E06E0; Thu, 2 Dec 2010 21:30:01 -0800 (PST) To: balazs.lengyel@ericsson.com, mbj@tail-f.com, dromasca@avaya.com, rbonica@juniper.net, bertietf@bwijnen.net, mehmet.ersue@nsn.com From: RFC Errata System Message-Id: <20101203053002.0FBC1E06E0@rfc-editor.org> Date: Thu, 2 Dec 2010 21:30:01 -0800 (PST) Cc: rfc-editor@rfc-editor.org, viswanath@huawei.com, netconf@ietf.org Subject: [Netconf] [Technical Errata Reported] RFC5717 (2657) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 05:28:46 -0000 The following errata report has been submitted for RFC5717, "Partial Lock Remote Procedure Call (RPC) for NETCONF". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5717&eid=2657 -------------------------------------- Type: Technical Reported by: B Viswanath Reddy Section: Appendix C Original Text ------------- Step 6 - Lock user Joe The NETCONF server grants the partial lock. The scope of this second lock includes only the node with name Joe. The lock protects all data below this particular node. Step 7 - Receive lock 2 | /usr:top/usr:users/user[usr:name="Joe"]" Corrected Text -------------- Step 6 - Lock user Joe The NETCONF server grants the partial lock. The scope of this second lock includes only the node with name Joe. The lock protects all data below this particular node. Step 7 - Receive lock 2 | /usr:top/usr:users/usr:user[usr:name="Joe"]" Notes ----- The instance identifier /usr:top/usr:users/user[usr:name="Joe"]" must be replaced with /usr:top/usr:users/usr:user[usr:name="Joe"]" Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5717 (draft-ietf-netconf-partial-lock-11) -------------------------------------- Title : Partial Lock Remote Procedure Call (RPC) for NETCONF Publication Date : December 2009 Author(s) : B. Lengyel, M. Bjorklund Category : PROPOSED STANDARD Source : Network Configuration Area : Operations and Management Stream : IETF Verifying Party : IESG From bertietf@bwijnen.net Fri Dec 3 01:25:53 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EABE28C180 for ; Fri, 3 Dec 2010 01:25:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.461 X-Spam-Level: X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXYuE-oBnlDy for ; Fri, 3 Dec 2010 01:25:52 -0800 (PST) Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id F0C073A68C6 for ; Fri, 3 Dec 2010 01:25:51 -0800 (PST) Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1PORv1-0006Ve-4D for netconf@ietf.org; Fri, 03 Dec 2010 10:27:08 +0100 Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from ) id 1PORv0-0008J5-TQ for netconf@ietf.org; Fri, 03 Dec 2010 10:27:07 +0100 Message-ID: <4CF8B7EA.7050708@bwijnen.net> Date: Fri, 03 Dec 2010 10:27:06 +0100 From: "Bert (IETF) Wijnen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Netconf Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4a40c92f6efe55790d64b44015b53c13e X-RIPE-Spam-Level: -- X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4a40c92f6efe55790d64b44015b53c13e Subject: [Netconf] Fwd: [Technical Errata Reported] RFC5717 (2657) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 09:25:53 -0000 FYI, I did not see this reflected on our WG mailing list. Martin, can you have a first look at this, since Balazs is not following thiss as closely anymore as he used to do. Bert -------- Original Message -------- Subject: [Technical Errata Reported] RFC5717 (2657) Date: Thu, 2 Dec 2010 21:30:01 -0800 (PST) From: RFC Errata System To: balazs.lengyel@ericsson.com, mbj@tail-f.com, dromasca@avaya.com, rbonica@juniper.net, bertietf@bwijnen.net, mehmet.ersue@nsn.com CC: viswanath@huawei.com, netconf@ietf.org, rfc-editor@rfc-editor.org The following errata report has been submitted for RFC5717, "Partial Lock Remote Procedure Call (RPC) for NETCONF". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5717&eid=2657 -------------------------------------- Type: Technical Reported by: B Viswanath Reddy Section: Appendix C Original Text ------------- Step 6 - Lock user Joe The NETCONF server grants the partial lock. The scope of this second lock includes only the node with name Joe. The lock protects all data below this particular node. Step 7 - Receive lock 2 | /usr:top/usr:users/user[usr:name="Joe"]" Corrected Text -------------- Step 6 - Lock user Joe The NETCONF server grants the partial lock. The scope of this second lock includes only the node with name Joe. The lock protects all data below this particular node. Step 7 - Receive lock 2 | /usr:top/usr:users/usr:user[usr:name="Joe"]" Notes ----- The instance identifier /usr:top/usr:users/user[usr:name="Joe"]" must be replaced with /usr:top/usr:users/usr:user[usr:name="Joe"]" Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5717 (draft-ietf-netconf-partial-lock-11) -------------------------------------- Title : Partial Lock Remote Procedure Call (RPC) for NETCONF Publication Date : December 2009 Author(s) : B. Lengyel, M. Bjorklund Category : PROPOSED STANDARD Source : Network Configuration Area : Operations and Management Stream : IETF Verifying Party : IESG From mbj@tail-f.com Fri Dec 3 01:40:16 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69A283A6AB8 for ; Fri, 3 Dec 2010 01:40:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTz51Gn+H+bL for ; Fri, 3 Dec 2010 01:40:15 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 276E63A68C6 for ; Fri, 3 Dec 2010 01:40:15 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id D9323616001; Fri, 3 Dec 2010 10:41:30 +0100 (CET) Date: Fri, 03 Dec 2010 10:41:28 +0100 (CET) Message-Id: <20101203.104128.123611252.mbj@tail-f.com> To: rfc-editor@rfc-editor.org From: Martin Bjorklund In-Reply-To: <20101203053002.0FBC1E06E0@rfc-editor.org> References: <20101203053002.0FBC1E06E0@rfc-editor.org> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: rbonica@juniper.net, viswanath@huawei.com, netconf@ietf.org Subject: Re: [Netconf] [Technical Errata Reported] RFC5717 (2657) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 09:40:16 -0000 Hi, The report is correct - the prefix "usr:" is missing in these two cases. However, there is actually another error in these two expressions - there is a trailing " character after each expression. So: OLD: /usr:top/usr:users/user[usr:name="Joe"]" NEW: /usr:top/usr:users/usr:user[usr:name="Joe"] /martin RFC Errata System wrote: > > The following errata report has been submitted for RFC5717, > "Partial Lock Remote Procedure Call (RPC) for NETCONF". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5717&eid=2657 > > -------------------------------------- > Type: Technical > Reported by: B Viswanath Reddy > > Section: Appendix C > > Original Text > ------------- > Step 6 - Lock user Joe > > xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" > xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" > message-id="104"> > > > > > > The NETCONF server grants the partial lock. The scope of this second > lock includes only the node with name Joe. The lock protects > all data below this particular node. > > Step 7 - Receive lock > > xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" > xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" > message-id="104"> > 2 > > | /usr:top/usr:users/user[usr:name="Joe"]" > > > > > Corrected Text > -------------- > Step 6 - Lock user Joe > > xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" > xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" > message-id="104"> > > > > > > The NETCONF server grants the partial lock. The scope of this second > lock includes only the node with name Joe. The lock protects > all data below this particular node. > > Step 7 - Receive lock > > xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" > xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" > message-id="104"> > 2 > > | /usr:top/usr:users/usr:user[usr:name="Joe"]" > > > > > Notes > ----- > The instance identifier /usr:top/usr:users/user[usr:name="Joe"]" must be replaced with /usr:top/usr:users/usr:user[usr:name="Joe"]" > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5717 (draft-ietf-netconf-partial-lock-11) > -------------------------------------- > Title : Partial Lock Remote Procedure Call (RPC) for NETCONF > Publication Date : December 2009 > Author(s) : B. Lengyel, M. Bjorklund > Category : PROPOSED STANDARD > Source : Network Configuration > Area : Operations and Management > Stream : IETF > Verifying Party : IESG > From mbj@tail-f.com Fri Dec 3 03:29:58 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDF6128C0FC for ; Fri, 3 Dec 2010 03:29:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIXZYdZIJjKc for ; Fri, 3 Dec 2010 03:29:57 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id D92CE28C18C for ; Fri, 3 Dec 2010 03:29:56 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 0F0E6616001; Fri, 3 Dec 2010 12:31:13 +0100 (CET) Date: Fri, 03 Dec 2010 12:31:11 +0100 (CET) Message-Id: <20101203.123111.32109474.mbj@tail-f.com> To: kwatsen@juniper.net From: Martin Bjorklund In-Reply-To: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 11:29:58 -0000 Hi, Kent Watsen wrote: > I loaded the schema from 4741bis-04 into XMLSpy (2006) and got the > following error: > > '' makes the content model > non-deterministic against ''. Ugh. I've validated the XSD with libxml, but it doesn't complain :( I agree this is an error though. One option is to change the ##any to ##other: But then we have the problem that the "data" element is not listed here, since it is defined in the Operations Layer as rpc output to get and get-config. This becomes a problem since the XSD and YANG model both provide elements to the same namespace. We could handle this by putting data back: But then we're mixing layers... An alternative would be to use the substitution technique that we already use for the rpc operation: And then if you want to define your own rpc-reply element, e.g. "data" you would do: /martin From bertietf@bwijnen.net Fri Dec 3 03:45:54 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14BB828C0DF for ; Fri, 3 Dec 2010 03:45:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.473 X-Spam-Level: X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMwLbO-Qo5mw for ; Fri, 3 Dec 2010 03:45:53 -0800 (PST) Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id BBFDE28C0D8 for ; Fri, 3 Dec 2010 03:45:52 -0800 (PST) Received: from dodo.ripe.net ([193.0.23.4]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1POU6R-00081I-8A; Fri, 03 Dec 2010 12:47:04 +0100 Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from ) id 1POU6R-00005G-2n; Fri, 03 Dec 2010 12:47:03 +0100 Message-ID: <4CF8D8B6.1080106@bwijnen.net> Date: Fri, 03 Dec 2010 12:47:02 +0100 From: "Bert (IETF) Wijnen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: netconf Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4fa58af7649e5736021f5708a20478c87 X-RIPE-Spam-Level: -- X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4fa58af7649e5736021f5708a20478c87 Cc: viswanath@huawei.com Subject: [Netconf] WG last call to approve [Technical Errata Reported] RFC5717 (2657) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 11:45:54 -0000 This is a WG Last Call to make sure we have consensus on an errata report to RFC 5717. Please respond/comment no later than Dec 17 2010 (any time zone). Based on the errata report, Martin even found another error. Fixing both, Martin has come up with the following text: Type: Technical (but it is in non-normative Appendix C) Section: Appendix C (page 22) In Step 6, Original Text: Corrected Text: In step 7, Original Text: /usr:top/usr:users/user[usr:name="Joe"]" Corrected Text: /usr:top/usr:users/usr:user[usr:name="Joe"] From j.schoenwaelder@jacobs-university.de Fri Dec 3 04:34:37 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 055AD28C0DE for ; Fri, 3 Dec 2010 04:34:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.109 X-Spam-Level: X-Spam-Status: No, score=-103.109 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCwohRXECS8n for ; Fri, 3 Dec 2010 04:34:35 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id E58EC28C0D9 for ; Fri, 3 Dec 2010 04:34:34 -0800 (PST) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id D2231C0003; Fri, 3 Dec 2010 13:35:51 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id hYwuby04Yw+s; Fri, 3 Dec 2010 13:35:51 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 33B5CC0002; Fri, 3 Dec 2010 13:35:45 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id C558815DC683; Fri, 3 Dec 2010 13:35:43 +0100 (CET) Date: Fri, 3 Dec 2010 13:35:43 +0100 From: Juergen Schoenwaelder To: "Bert (IETF) Wijnen" Message-ID: <20101203123543.GB1858@elstar.local> Mail-Followup-To: "Bert (IETF) Wijnen" , netconf , viswanath@huawei.com References: <4CF8D8B6.1080106@bwijnen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CF8D8B6.1080106@bwijnen.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf , viswanath@huawei.com Subject: Re: [Netconf] WG last call to approve [Technical Errata Reported] RFC5717 (2657) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 12:34:37 -0000 On Fri, Dec 03, 2010 at 12:47:02PM +0100, Bert (IETF) Wijnen wrote: > This is a WG Last Call to make sure we have consensus > on an errata report to RFC 5717. > > Please respond/comment no later than Dec 17 2010 (any time zone). > > Based on the errata report, Martin even found another error. > Fixing both, Martin has come up with the following text: [...] I agree with Martin's fix. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From kwatsen@juniper.net Fri Dec 3 09:27:52 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34A8D28C182 for ; Fri, 3 Dec 2010 09:27:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-SCupDrurvB for ; Fri, 3 Dec 2010 09:27:50 -0800 (PST) Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id AD0B628C162 for ; Fri, 3 Dec 2010 09:27:49 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTPko47w39KaFK11olBhFaZXeZz8grUbD@postini.com; Fri, 03 Dec 2010 09:29:07 PST Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Fri, 3 Dec 2010 09:27:26 -0800 From: Kent Watsen To: Andy Bierman , "netconf@ietf.org" Date: Fri, 3 Dec 2010 09:27:24 -0800 Thread-Topic: 4741bis-04 has non-deterministic schema Thread-Index: AcuSoR4T/0jFyft0TaKOVVwvT5veKgAAhBHAABpYvLA= Message-ID: <84600D05C20FF943918238042D7670FD37443616C9@EMBX01-HQ.jnpr.net> References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_84600D05C20FF943918238042D7670FD37443616C9EMBX01HQjnprn_" MIME-Version: 1.0 Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 17:27:52 -0000 --_000_84600D05C20FF943918238042D7670FD37443616C9EMBX01HQjnprn_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > Also, the monitoring example is correct. > The response is for the following . > The operation returns everything within the element . Ah, I see now the YANG schema for and having: output { container data { presence "An empty data container indicates that the request did not produce any results."; description "Copy of the source datastore subset which matched the filter criteria (if any)."; } } Martin, this means that we do not want to define a element in Thanks, Kent --_000_84600D05C20FF943918238042D7670FD37443616C9EMBX01HQjnprn_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

> Also, the monitoring example is correct.

> The response is for the followi= ng <get>.

> The <get> operation returns everything within the element &l= t;data>.

 

Ah, I see now the YANG schema for= <get> and <get-config> having:

 

   &nbs= p; output {

       = container data {

     &n= bsp;   presence

    = ;       "An empty data container indicat= es that the

      &= nbsp;     request did not produce any results.";

         d= escription

      &n= bsp;    "Copy of the source datastore subset which matc= hed

       &nb= sp;    the filter criteria (if any).";

       }

=       }

=  

 <= /o:p>

Martin, this means that we do n= ot want to define a <data> element in <rpcResponse><= /span>

 

Thanks,

Kent

 

 

= = --_000_84600D05C20FF943918238042D7670FD37443616C9EMBX01HQjnprn_-- From biermana@Brocade.com Fri Dec 3 09:37:57 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2FF628C17E for ; Fri, 3 Dec 2010 09:37:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.208 X-Spam-Level: X-Spam-Status: No, score=-2.208 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Re92kR0cwTt for ; Fri, 3 Dec 2010 09:37:55 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id 57F7228C11D for ; Fri, 3 Dec 2010 09:37:53 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oB3HVF8s022960; Fri, 3 Dec 2010 09:39:11 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.140.11]) by mx0b-000f0801.pphosted.com with ESMTP id sy4acg0y9-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 03 Dec 2010 09:39:10 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE01.corp.brocade.com (144.49.140.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 3 Dec 2010 09:40:09 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Fri, 3 Dec 2010 09:39:08 -0800 From: Andy Bierman To: Kent Watsen , "netconf@ietf.org" Date: Fri, 3 Dec 2010 09:39:07 -0800 Thread-Topic: 4741bis-04 has non-deterministic schema Thread-Index: AcuSoR4T/0jFyft0TaKOVVwvT5veKgAAhBHAABpYvLAAANuI0A== Message-ID: References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> <84600D05C20FF943918238042D7670FD37443616C9@EMBX01-HQ.jnpr.net> In-Reply-To: <84600D05C20FF943918238042D7670FD37443616C9@EMBX01-HQ.jnpr.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABEEHQ1EXCH01corp_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-03_11:2010-12-03, 2010-12-03, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012030078 Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 17:37:57 -0000 --_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABEEHQ1EXCH01corp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I think the YANG for and output needs to change to anyxm= l, otherwise a YANG validator will complain that container 'data' has no child= nodes defined. I agree that the element should be left out of the XSD. It is not hardwired in. The WG decided the node was part of the or definition. No other 4741 operation returns d= ata. The XSD should align with the YANG expectations (output/foo --> /rpc-reply/= foo). Andy From: Kent Watsen [mailto:kwatsen@juniper.net] Sent: Friday, December 03, 2010 9:27 AM To: Andy Bierman; netconf@ietf.org Subject: RE: 4741bis-04 has non-deterministic schema > Also, the monitoring example is correct. > The response is for the following . > The operation returns everything within the element . Ah, I see now the YANG schema for and having: output { container data { presence "An empty data container indicates that the request did not produce any results."; description "Copy of the source datastore subset which matched the filter criteria (if any)."; } } Martin, this means that we do not want to define a element in Thanks, Kent --_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABEEHQ1EXCH01corp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,<= /o:p>

 

I think the YANG for <get> and <get-confi= g> output needs to change to anyxml,
otherwise a YANG validator will = complain that container ‘data’ has no child nodes
defined.= =A0

 

I agree that the <data> element sh= ould be left out of the XSD.

It is not hardwired in.=A0 The WG decided the <data> node was part=
of the <get> or <get-config> definition.=A0 No other 4741 o= peration returns data.

The= XSD should align with the YANG expectations (output/foo =E0= /rpc-reply/foo).

&nb= sp;

Andy

<= p class=3DMsoNormal> 

 

<= span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From: = Kent Watsen [mailto:kwatsen@juniper.net]
Sent: Friday, December = 03, 2010 9:27 AM
To: Andy Bierman; netconf@ietf.org
Subject= : RE: 4741bis-04 has non-deterministic schema

 

> Also, the monitoring example is correct.

> The response is for the following <get>.<= o:p>

> The <get> opera= tion returns everything within the element <data>.<= /p>

 

Ah, I see now the YANG schema for <get> and <get-confi= g> having:

 <= /o:p>

     output {

       container data {

         presence

         &= nbsp; "An empty data container indicates that the

            re= quest did not produce any results.";

 &= nbsp;       description

=

           "Cop= y of the source datastore subset which matched

&n= bsp;           the filter= criteria (if any).";

   &nbs= p;   }

      }=

 <= /p>

 

Martin, this means that we do not want to define a <data>= element in <rpcResponse>

<= span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F= 497D'> 

Thanks,<= /o:p>

Kent

 

=  

= --_000_B11AB91666F22D498EEC66410EB3D3C4F412CEABEEHQ1EXCH01corp_-- From kwatsen@juniper.net Fri Dec 3 14:58:35 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CCC83A69B8 for ; Fri, 3 Dec 2010 14:58:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQufTVP0ZuTD for ; Fri, 3 Dec 2010 14:58:34 -0800 (PST) Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by core3.amsl.com (Postfix) with ESMTP id 5BFBB3A659C for ; Fri, 3 Dec 2010 14:58:34 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKTPl2ZnJBOXhzOLBjzyaUD+7EkE4RbbrV@postini.com; Fri, 03 Dec 2010 14:59:53 PST Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Fri, 3 Dec 2010 14:57:49 -0800 From: Kent Watsen To: Martin Bjorklund Date: Fri, 3 Dec 2010 14:57:48 -0800 Thread-Topic: [Netconf] 4741bis-04 has non-deterministic schema Thread-Index: AcuS3a9MFvsxktVfRueN9sptqmVXVgASpjfQ Message-ID: <84600D05C20FF943918238042D7670FD3744361C2E@EMBX01-HQ.jnpr.net> References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> <20101203.123111.32109474.mbj@tail-f.com> In-Reply-To: <20101203.123111.32109474.mbj@tail-f.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "netconf@ietf.org" Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 22:58:35 -0000 > An alternative would be to use the substitution technique that we > already use for the rpc operation: > > > > minOccurs=3D"0" maxOccurs=3D"unbounded"/> > > > > > > type=3D"rpcResponseType" abstract=3D"true"/> XMLSpy 2011 says that the 4741bis-4 schema is valid after this update > And then if you want to define your own rpc-reply element, e.g. "data" > you would do: >=20 > > > > > > namespace=3D"##other" processContents=3D"lax"/> > > > > > Right, saving the 4741bis-4 schema into file called "4741bis-4.xsd", I then= created another file called "my-rpc.xsd" as follows: =20 Which then allowed me to create: token And: token anytype All validating with XMLSpy 2011 BTW: is the NetConf schema post somewhere online? - or will projects always= need to copy/paste it from the spec and distribute it as part of there sch= ema? Thanks, Kent From mbj@tail-f.com Sun Dec 5 05:14:44 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCD8A3A6AB9 for ; Sun, 5 Dec 2010 05:14:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bLygVGs6uMdE for ; Sun, 5 Dec 2010 05:14:43 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id A299F3A6AA8 for ; Sun, 5 Dec 2010 05:14:43 -0800 (PST) Received: from localhost (c213-100-166-57.swipnet.se [213.100.166.57]) by mail.tail-f.com (Postfix) with ESMTPSA id 7C26D616001; Sun, 5 Dec 2010 14:16:03 +0100 (CET) Date: Sun, 05 Dec 2010 14:16:01 +0100 (CET) Message-Id: <20101205.141601.18197811.mbj@tail-f.com> To: kwatsen@juniper.net From: Martin Bjorklund In-Reply-To: <84600D05C20FF943918238042D7670FD3744361C2E@EMBX01-HQ.jnpr.net> References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> <20101203.123111.32109474.mbj@tail-f.com> <84600D05C20FF943918238042D7670FD3744361C2E@EMBX01-HQ.jnpr.net> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2010 13:14:45 -0000 Kent Watsen wrote: > > An alternative would be to use the substitution technique that we > > already use for the rpc operation: > > > XMLSpy 2011 says that the 4741bis-4 schema is valid after this update I validated this schema with libxml as well. So, does anyone object to this change? Since the current schema in draft -06 is broken we need to do something. I believe this is the best fix; it actually makes the XSD a bit more useful, since we get an explicit mechanism for handling custom rpc-replies (just as we already have with custom rpcs). Tools that generate XSD compatible with 4741bis from YANG models (e.g. pyang) should be updated to use this new substitution group mechanism, but this should be ok. > BTW: is the NetConf schema post somewhere online? - or will projects always > need to copy/paste it from the spec and distribute it as part of there schema? IANA keeps it at http://www.iana.org/assignments/xml-registry/schema/netconf. But in general copy & paste from the RFC is done also for other formats; mibs, yang models, abnf grammars etc. /martin From mbj@tail-f.com Sun Dec 5 05:15:13 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7BDF28C0DF for ; Sun, 5 Dec 2010 05:15:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGouukM+ynFK for ; Sun, 5 Dec 2010 05:15:12 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id DB17D3A6AA8 for ; Sun, 5 Dec 2010 05:15:11 -0800 (PST) Received: from localhost (c213-100-166-57.swipnet.se [213.100.166.57]) by mail.tail-f.com (Postfix) with ESMTPSA id E564F616001; Sun, 5 Dec 2010 14:16:32 +0100 (CET) Date: Sun, 05 Dec 2010 14:16:32 +0100 (CET) Message-Id: <20101205.141632.116449110.mbj@tail-f.com> To: biermana@Brocade.com From: Martin Bjorklund In-Reply-To: References: <84600D05C20FF943918238042D7670FD37443616C9@EMBX01-HQ.jnpr.net> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2010 13:15:13 -0000 Andy Bierman wrote: > Hi, > > I think the YANG for and output needs to change to anyxml, > otherwise a YANG validator will complain that container 'data' has no child > nodes > defined. +1 /martin From biermana@Brocade.com Mon Dec 6 10:09:37 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14EB33A686B for ; Mon, 6 Dec 2010 10:09:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.912 X-Spam-Level: X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_34=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HA+u6YaZ1v3h for ; Mon, 6 Dec 2010 10:09:36 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id 365453A682C for ; Mon, 6 Dec 2010 10:09:36 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oB6IAx6O006925; Mon, 6 Dec 2010 10:10:59 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.140.11]) by mx0b-000f0801.pphosted.com with ESMTP id t14f480fy-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 06 Dec 2010 10:10:59 -0800 Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXEDGE01.corp.brocade.com (144.49.140.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 6 Dec 2010 10:11:54 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Mon, 6 Dec 2010 10:10:57 -0800 From: Andy Bierman To: Martin Bjorklund Date: Mon, 6 Dec 2010 10:10:55 -0800 Thread-Topic: [Netconf] 4741bis-04 has non-deterministic schema Thread-Index: AcuUfqR1T8dtraVxQl+ars7HyYi13gA8CviQ Message-ID: References: <84600D05C20FF943918238042D7670FD37443616C9@EMBX01-HQ.jnpr.net> <20101205.141632.116449110.mbj@tail-f.com> In-Reply-To: <20101205.141632.116449110.mbj@tail-f.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-06_12:2010-12-06, 2010-12-06, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012060101 Cc: "netconf@ietf.org" Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 18:09:37 -0000 Hi, The way this is handled in yuma is not perfect YANG, but it allows better auto-validation than anyxml. container config { ncx:root; } The 'root' extension tells the tools that this is a config root, not a container with no children defined. The allowed content is the set of available top-level YANG data nodes (known to the tool). This works for or -- any container tagged as ncx:root. We can't really do something like this in 4741bis. But IMO we need to standardize on YANG as the NETCONF content layer, and stop assuming a NETCONF config can be 'anyxml'. Andy -----Original Message----- From: Martin Bjorklund [mailto:mbj@tail-f.com]=20 Sent: Sunday, December 05, 2010 5:17 AM To: Andy Bierman Cc: kwatsen@juniper.net; netconf@ietf.org Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema Andy Bierman wrote: > Hi, >=20 > I think the YANG for and output needs to change to any= xml, > otherwise a YANG validator will complain that container 'data' has no chi= ld > nodes > defined. +1 /martin From mbj@tail-f.com Mon Dec 6 11:29:36 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37B2B3A6895 for ; Mon, 6 Dec 2010 11:29:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.746 X-Spam-Level: X-Spam-Status: No, score=-1.746 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_34=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ypIexIWiacjw for ; Mon, 6 Dec 2010 11:29:33 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 9A5493A6890 for ; Mon, 6 Dec 2010 11:28:59 -0800 (PST) Received: from localhost (c213-100-166-57.swipnet.se [213.100.166.57]) by mail.tail-f.com (Postfix) with ESMTPSA id 3FDAC616001; Mon, 6 Dec 2010 20:30:22 +0100 (CET) Date: Mon, 06 Dec 2010 20:30:19 +0100 (CET) Message-Id: <20101206.203019.151249595.mbj@tail-f.com> To: biermana@Brocade.com From: Martin Bjorklund In-Reply-To: References: <20101205.141632.116449110.mbj@tail-f.com> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 19:29:36 -0000 Andy Bierman wrote: > Hi, > > The way this is handled in yuma is not perfect YANG, > but it allows better auto-validation than anyxml. > > container config { > ncx:root; > } > > The 'root' extension tells the tools that this is a config root, > not a container with no children defined. The allowed content > is the set of available top-level YANG data nodes (known to the tool). > This works for or -- any container > tagged as ncx:root. But the tool could also do anyxml config { ncx:root; } > We can't really do something like this in 4741bis. > But IMO we need to standardize on YANG as the NETCONF content layer, > and stop assuming a NETCONF config can be 'anyxml'. I would argue that anyxml is the correct construct to use even if all content was described in YANG modules. /martin From ietf@andybierman.com Mon Dec 6 12:13:14 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 967D43A688A for ; Mon, 6 Dec 2010 12:13:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_27=0.6, J_CHICKENPOX_34=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSFsfZUE3W5i for ; Mon, 6 Dec 2010 12:13:13 -0800 (PST) Received: from nm26-vm0.bullet.mail.sp2.yahoo.com (nm26-vm0.bullet.mail.sp2.yahoo.com [98.139.91.230]) by core3.amsl.com (Postfix) with SMTP id 0446B3A6894 for ; Mon, 6 Dec 2010 12:13:12 -0800 (PST) Received: from [98.139.91.67] by nm26.bullet.mail.sp2.yahoo.com with NNFMP; 06 Dec 2010 20:14:34 -0000 Received: from [98.139.91.15] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 06 Dec 2010 20:14:34 -0000 Received: from [127.0.0.1] by omp1015.mail.sp2.yahoo.com with NNFMP; 06 Dec 2010 20:14:34 -0000 X-Yahoo-Newman-Id: 547832.55766.bm@omp1015.mail.sp2.yahoo.com Received: (qmail 55606 invoked from network); 6 Dec 2010 20:14:34 -0000 Received: from [192.168.0.14] (ietf@75.84.164.152 with plain) by smtp105.sbc.mail.gq1.yahoo.com with SMTP; 06 Dec 2010 12:14:30 -0800 PST X-Yahoo-SMTP: Z6xhxCCswBAlhcxjVNwaQtp4EKpLdTUUf5Nx_pGy81o- X-YMail-OSG: zo0e0rAVM1mJExcwjvkh8Zw3ojgD7Y5LhyvoFVbEflIXZk. wCbPUyN8T5iTaMOv6Hhl5Fir3pD4N3XLK4NdIiWiorNsh6gx7YsUI.apVcte Rej3SiTNicekuMwKpSA_hAkuVIq9BDvD9LqS799zf1V5wBnWrfvCV25MgcnL fsdcSu.dionkMkqt.CHZCZSnp8NZd4mO0ferncx5inOY0phJajAnZO9KlM6P DU4JOvpmJ1IXLBbR_x1BEZp5Hx_esf5Z3a_tGrhlnpL.gXRtN2Xd2crUNkbm FgUHN7myvyk9sqKJh3FqsCn0- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4CFD4426.6050903@andybierman.com> Date: Mon, 06 Dec 2010 12:14:30 -0800 From: Andy Bierman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10 MIME-Version: 1.0 To: Martin Bjorklund References: <20101205.141632.116449110.mbj@tail-f.com> <20101206.203019.151249595.mbj@tail-f.com> In-Reply-To: <20101206.203019.151249595.mbj@tail-f.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: biermana@Brocade.com, netconf@ietf.org Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 20:13:14 -0000 On 12/06/2010 11:30 AM, Martin Bjorklund wrote: > Andy Bierman wrote: >> Hi, >> >> The way this is handled in yuma is not perfect YANG, >> but it allows better auto-validation than anyxml. >> >> container config { >> ncx:root; >> } >> >> The 'root' extension tells the tools that this is a config root, >> not a container with no children defined. The allowed content >> is the set of available top-level YANG data nodes (known to the tool). >> This works for or -- any container >> tagged as ncx:root. > > But the tool could also do > > anyxml config { > ncx:root; > } > good point -- I should change ncx:root to use anyxml. >> We can't really do something like this in 4741bis. >> But IMO we need to standardize on YANG as the NETCONF content layer, >> and stop assuming a NETCONF config can be 'anyxml'. > > I would argue that anyxml is the correct construct to use even if all > content was described in YANG modules. > Yes -- an NP container is its own special YANG creation. A real node might have the wd:default attribute in it, or other XML attributes. I would prefer to keep mixed XML content, or a text node, out of the standard. NETCONF is complicated enough with just YANG as the content. > > /martin Andy From mbj@tail-f.com Fri Dec 10 05:38:50 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60E4A28C0D0 for ; Fri, 10 Dec 2010 05:38:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFUhRkmd5ziH for ; Fri, 10 Dec 2010 05:38:49 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 2BE7A3A6AC8 for ; Fri, 10 Dec 2010 05:38:47 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 7D83F616001 for ; Fri, 10 Dec 2010 14:40:17 +0100 (CET) Date: Fri, 10 Dec 2010 14:40:16 +0100 (CET) Message-Id: <20101210.144016.249498658.mbj@tail-f.com> To: netconf@ietf.org From: Martin Bjorklund X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Netconf] list of 4741bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 13:38:51 -0000 Hi, As requested by the chairs, this is a list of proposed edits for 4741bis. There are a few editorial changes, and two technical changes. One is a fix for the XML Schema bug reported by Kent, and one is a fix for the 'data' response element in the YANG module. /martin Section 4.2., paragraph 1: OLD: The message is sent in response to an operation. NEW: The message is sent in response to an message. Section 7.5., paragraph 6: OLD: A lock MUST not be granted if either of the following conditions is true: NEW: A lock MUST NOT be granted if either of the following conditions is true: Appendix B., paragraph 4: OLD: This schema defines the syntax for the NETCONF Message layer NEW: This schema defines the syntax for the NETCONF Messages layer Appendix B., paragraph 6: OLD: NEW: Appendix C., paragraph 46: OLD: output { container data { presence "An empty data container indicates that the request did not produce any results."; description "Copy of the source datastore subset which matched the filter criteria (if any)."; } } } NEW: output { anyxml data { description "Copy of the source datastore subset which matched the filter criteria (if any). An empty data container indicates that the request did not produce any results."; } } } Appendix C., paragraph 84: OLD: output { container data { presence "An empty data container indicates that the filter request did not match any results."; description "Copy of the running datastore subset and/or state data which matched the filter criteria (if any)."; } } } NEW: output { anyxml data { description "Copy of the running datastore subset and/or state data which matched the filter criteria (if any). An empty data container indicates that the request did not produce any results."; } } } From mbj@tail-f.com Fri Dec 10 06:21:40 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D76C828C0E1 for ; Fri, 10 Dec 2010 06:21:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7wWJEvU92o6 for ; Fri, 10 Dec 2010 06:21:38 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id E97FB3A6CA7 for ; Fri, 10 Dec 2010 06:21:34 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 79753616001 for ; Fri, 10 Dec 2010 15:22:56 +0100 (CET) Date: Fri, 10 Dec 2010 15:22:55 +0100 (CET) Message-Id: <20101210.152255.172617871.mbj@tail-f.com> To: netconf@ietf.org From: Martin Bjorklund X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 14:21:41 -0000 Hi, As requested by the chairs, attached is the updated list of proposed edits to 4742bis. Don't forget to send comments before 14 December 2010! /martin OLD (in 3.1): The following example shows a capability exchange. Data sent by the NETCONF client are marked with "C:" and data sent by the NETCONF server are marked with "S:". S: S: S: S: S: urn:ietf:params:xml:ns:netconf:base:1.0 S: S: S: urn:ietf:params:ns:netconf:capability:startup:1.0 S: S: S: 4 S: S: ]]>]]> C: C: C: C: C: urn:ietf:params:xml:ns:netconf:base:1.0 C: C: C: C: ]]>]]> NEW: The following example shows a capability exchange. Data sent by the NETCONF client are marked with "C: " and data sent by the NETCONF server are marked with "S: ". S: S: S: S: S: urn:ietf:params:xml:ns:netconf:base:1.1 S: S: S: urn:ietf:params:ns:netconf:capability:startup:1.0 S: S: S: 4 S: S: ]]>]]> C: C: C: C: C: urn:ietf:params:xml:ns:netconf:base:1.1 C: C: C: C: ]]>]]> Delete this from 3.1: As the previous example illustrates, a special character sequence, ]]>]]>, MUST be sent by both the NETCONF client and the NETCONF server after each XML document in the NETCONF exchange. This character sequence MUST NOT appear in an XML document. NEW (right after the first paragraph in Section 4.): 4.1. Framing protocol The previous version of this document defined the character sequence "]]>]]>" as a message separator, under the assumption that it could not be found in well-formed XML documents. However, this assumption is not correct. It can legally appear in XML attributes, comments, and processing instructions. In order to solve this problem, and at the same time be compatible with existing implementations, this document defines the following framing protocol. The message MUST be followed by the character sequence "]]>]]>". Upon reception of the message, the receiving peer's SSH Transport layer conceptually passes the message to the Messages layer. If the :base:1.1 capability is advertised by both peers, the chunked transfer mechanism (see Section 4.1.1) is used for the remainder of the NETCONF session. Otherwise, the old end-of-message based mechanism (see Section 4.1.2) is used. 4.1.1. Chunked Framing Mechanism This mechanism encodes all NETCONF messages with a chunked framing. Specifically, the message follows the ABNF [RFC 5234] rule Chunked-Message: Chunked-Message = 1*chunk end-of-chunks chunk = LF HASH chunk-size LF chunk-data chunk-size = 1*DIGIT1 0*DIGIT chunk-data = 1*OCTET end-of-chunks = LF HASH HASH LF DIGIT1 = %x31-39 DIGIT = %x30-39 HASH = %x23 LF = %x0A OCTET = %x00-FF The chunk-size field is a string of decimal digits indicating the number of octets in chunk-data. Leading zeros are prohibited, and the maximum allowed chunk-size value is 4294967295. As an example, the message: could be encoded as: #4 ## Conceptually, the SSH Transport layer encodes messages sent by the Messages layer, and decodes messages received on the SSH channel before passing them to the Messages layer. If an error occurs during the decoding process, the peer MUST terminate the NETCONF session by closing the corresponding SSH channel. 4.1.2. End-of-message Framing Mechanism This mechanism exists for backwards compatibility with implementations of previous versions of this document. It is only used when the remote peer does not advertise the :base:1.1 capability. When this mechanism is used, the special character sequence "]]>]]>", MUST be sent by both the NETCONF client and the NETCONF server after each message (XML document) in the NETCONF exchange. Conceptually, the SSH Transport layer passes any data found in between the "]]>]]>" characters to the Messages layer. OLD (section 4): C: C: C: C: C: C: C: C: C: C: ]]>]]> S: S: S: S: S: rootsuperuser S: fredadmin S: barneyadmin S: S: S: S: ]]>]]> NEW: C: C: #271 C: C: C: C: C: C: C: C: C: C: C: ## S: S: #404 S: S: S: S: S: rootsuperuser S: fredadmin S: barneyadmin S: S: S: S: S: ## OLD (Section 5): C: C: C: C: C: ]]>]]> S: S: S: S: S: ]]>]] NEW: C: C: #141 C: C: C: C: C: C: ## S: S: #140 S: S: S: S: S: S: ## OLD (Section 6): RFC 4742 assumes that the EOM sequence cannot appear in any XML document, which turned out to be mistaken. The EOM sequence can cause operational problems and open space for attacks if sent deliberately in an XML document. It is however believed that the associated threat is not very high. This document keeps using the EOM sequence to avoid incompatibility with existing implementations. Implementations of SSH transport must exercise extra care and make sure the EOM sequence is not present in an XML document. NEW: RFC 4742 assumes that the EOM sequence "]]>]]>" cannot appear in any well-formed XML document, which turned out to be mistaken. The EOM sequence can cause operational problems and open space for attacks if sent deliberately in RPC messages. It is however believed that the associated threat is not very high. This document still uses the EOM sequence for the initial message to avoid incompatibility with existing implementations. When both peers implement this specification, a proper framing protocol is used for the rest of the NETCONF session, to avoid injection attacks. From lhotka@cesnet.cz Fri Dec 10 07:40:15 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FBB43A6C98 for ; Fri, 10 Dec 2010 07:40:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.494 X-Spam-Level: X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lnOIKZb54NVy for ; Fri, 10 Dec 2010 07:40:13 -0800 (PST) Received: from office2.cesnet.cz (office2.cesnet.cz [IPv6:2001:718:1:101::144:244]) by core3.amsl.com (Postfix) with ESMTP id 10FDC3A67ED for ; Fri, 10 Dec 2010 07:40:09 -0800 (PST) Received: from [IPv6:2001:718:1a02:7:201:80ff:fe65:dd1e] (unknown [IPv6:2001:718:1a02:7:201:80ff:fe65:dd1e]) by office2.cesnet.cz (Postfix) with ESMTPSA id 342242CDE058 for ; Fri, 10 Dec 2010 16:41:39 +0100 (CET) From: Ladislav Lhotka To: netconf@ietf.org In-Reply-To: <20101210.152255.172617871.mbj@tail-f.com> References: <20101210.152255.172617871.mbj@tail-f.com> Content-Type: text/plain; charset="UTF-8" Organization: CESNET Date: Fri, 10 Dec 2010 16:41:36 +0100 Message-ID: <1291995696.26221.67.camel@behold> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 15:40:15 -0000 Hi, I have reviewed the text with the proposed edits. I fully support the inclusion of the chunked framing protocol because it significantly increases robustness of the SSH transport. I also checked the chunk sizes in all examples. My suggestions for minor improvements of the proposed edits are below. On Pá, 2010-12-10 at 15:22 +0100, Martin Bjorklund wrote: > Hi, > > As requested by the chairs, attached is the updated list of proposed > edits to 4742bis. Don't forget to send comments before 14 December > 2010! > > > /martin > > > OLD (in 3.1): > > The following example shows a capability exchange. Data sent by the > NETCONF client are marked with "C:" and data sent by the NETCONF > server are marked with "S:". > > S: > S: > S: > S: > S: urn:ietf:params:xml:ns:netconf:base:1.0 > S: > S: > S: urn:ietf:params:ns:netconf:capability:startup:1.0 > S: > S: > S: 4 > S: > S: ]]>]]> > > C: > C: > C: > C: > C: urn:ietf:params:xml:ns:netconf:base:1.0 > C: > C: > C: > C: ]]>]]> > > NEW: > > The following example shows a capability exchange. Data sent by the > NETCONF client are marked with "C: " and data sent by the NETCONF > server are marked with "S: ". > > S: > S: > S: > S: > S: urn:ietf:params:xml:ns:netconf:base:1.1 > S: > S: > S: urn:ietf:params:ns:netconf:capability:startup:1.0 > S: > S: > S: 4 > S: > S: ]]>]]> > > C: > C: > C: > C: > C: urn:ietf:params:xml:ns:netconf:base:1.1 > C: > C: > C: > C: ]]>]]> > > > > Delete this from 3.1: > > As the previous example illustrates, a special character sequence, > ]]>]]>, MUST be sent by both the NETCONF client and the NETCONF > server after each XML document in the NETCONF exchange. This > character sequence MUST NOT appear in an XML document. > > > > > > > NEW (right after the first paragraph in Section 4.): > > 4.1. Framing protocol > > The previous version of this document defined the character sequence > "]]>]]>" as a message separator, under the assumption that it could > not be found in well-formed XML documents. However, this assumption s/could not be found/cannot appear/ > is not correct. It can legally appear in XML attributes, comments, > and processing instructions. In order to solve this problem, and at > the same time be compatible with existing implementations, this > document defines the following framing protocol. > > The message MUST be followed by the character sequence > "]]>]]>". Upon reception of the message, the receiving > peer's SSH Transport layer conceptually passes the > message to the Messages layer. If the :base:1.1 capability is > advertised by both peers, the chunked transfer mechanism (see > Section 4.1.1) is used for the remainder of the NETCONF > session. Otherwise, the old end-of-message based mechanism > (see Section 4.1.2) is used. > > 4.1.1. Chunked Framing Mechanism > > This mechanism encodes all NETCONF messages with a chunked > framing. Specifically, the message follows the ABNF [RFC 5234] > rule Chunked-Message: > > Chunked-Message = 1*chunk > end-of-chunks > > chunk = LF HASH chunk-size LF > chunk-data > chunk-size = 1*DIGIT1 0*DIGIT > chunk-data = 1*OCTET > > end-of-chunks = LF HASH HASH LF > > DIGIT1 = %x31-39 > DIGIT = %x30-39 > HASH = %x23 > LF = %x0A > OCTET = %x00-FF > > The chunk-size field is a string of decimal digits indicating the > number of octets in chunk-data. Leading zeros are prohibited, and > the maximum allowed chunk-size value is 4294967295. > > As an example, the message: > > xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > > > > could be encoded as: > > #4 > #18 > message-id="102" > > #79 > xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > > > ## > > Conceptually, the SSH Transport layer encodes messages sent by the > Messages layer, and decodes messages received on the SSH channel > before passing them to the Messages layer. > > If an error occurs during the decoding process, the peer MUST > terminate the NETCONF session by closing the corresponding SSH > channel. > I think the paragraph starting with "To continue the example given above, ..." and the example belongs here and not after 4.1.2. > 4.1.2. End-of-message Framing Mechanism > > This mechanism exists for backwards compatibility with > implementations of previous versions of this document. It is only s/is only/MUST be/ > used when the remote peer does not advertise the :base:1.1 > capability. ... , and MUST NOT be used otherwise. > > When this mechanism is used, the special character sequence > "]]>]]>", MUST be sent by both the NETCONF client and the NETCONF > server after each message (XML document) in the NETCONF exchange. > Conceptually, the SSH Transport layer passes any data found in > between the "]]>]]>" characters to the Messages layer. > > > > OLD (section 4): According to the ABNF, all chunks - including the first one - begin with LF, so I think all examples using the chunk framing should start with the empty line, i.e. either C: or S: to indicate the presence of LF. Lada > > C: > C: C: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > C: > C: > C: > C: > C: > C: > C: > C: ]]>]]> > > S: > S: S: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > S: > S: > S: rootsuperuser > S: fredadmin > S: barneyadmin > S: > S: > S: > S: ]]>]]> > > NEW: > > C: > C: #271 > C: > C: C: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > C: > C: > C: > C: > C: > C: > C: > C: > C: ## > > S: > S: #404 > S: > S: S: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > S: > S: > S: rootsuperuser > S: fredadmin > S: barneyadmin > S: > S: > S: > S: > S: ## > > OLD (Section 5): > > C: > C: C: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > C: > C: > C: ]]>]]> > > S: > S: S: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > S: > S: > S: ]]>]] > > NEW: > > C: > C: #141 > C: > C: C: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > C: > C: > C: > C: ## > > S: > S: #140 > S: > S: S: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > S: > S: > S: > S: ## > > OLD (Section 6): > > RFC 4742 assumes that the EOM sequence cannot appear in any XML > document, which turned out to be mistaken. The EOM sequence can > cause operational problems and open space for attacks if sent > deliberately in an XML document. It is however believed that the > associated threat is not very high. This document keeps using the > EOM sequence to avoid incompatibility with existing implementations. > Implementations of SSH transport must exercise extra care and make > sure the EOM sequence is not present in an XML document. > > NEW: > > RFC 4742 assumes that the EOM sequence "]]>]]>" cannot appear in > any well-formed XML document, which turned out to be mistaken. The > EOM sequence can cause operational problems and open space for > attacks if sent deliberately in RPC messages. It is however > believed that the associated threat is not very high. This > document still uses the EOM sequence for the initial > message to avoid incompatibility with existing implementations. > When both peers implement this specification, a proper framing > protocol is used for the rest of the NETCONF session, to avoid > injection attacks. > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf -- Ladislav Lhotka, CESNET PGP Key ID: E74E8C0C From mbj@tail-f.com Fri Dec 10 07:45:53 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37AD13A6C98 for ; Fri, 10 Dec 2010 07:45:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNK0wHmM9zAc for ; Fri, 10 Dec 2010 07:45:52 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 53C633A6B54 for ; Fri, 10 Dec 2010 07:45:52 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 89C11616001; Fri, 10 Dec 2010 16:47:22 +0100 (CET) Date: Fri, 10 Dec 2010 16:47:20 +0100 (CET) Message-Id: <20101210.164720.61171376.mbj@tail-f.com> To: lhotka@cesnet.cz From: Martin Bjorklund In-Reply-To: <1291995696.26221.67.camel@behold> References: <20101210.152255.172617871.mbj@tail-f.com> <1291995696.26221.67.camel@behold> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 15:45:53 -0000 Hi, Ladislav Lhotka wrote: > According to the ABNF, all chunks - including the first one - begin with > LF, so I think all examples using the chunk framing should start with > the empty line, i.e. either > > C: > > or > > S: > > to indicate the presence of LF. I think they do, don't they? /martin From lhotka@cesnet.cz Fri Dec 10 08:11:09 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FC4D3A6CA9 for ; Fri, 10 Dec 2010 08:11:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.507 X-Spam-Level: X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AQ2baXlwPMn6 for ; Fri, 10 Dec 2010 08:11:08 -0800 (PST) Received: from office2.cesnet.cz (office2.cesnet.cz [IPv6:2001:718:1:101::144:244]) by core3.amsl.com (Postfix) with ESMTP id 5D6913A6B58 for ; Fri, 10 Dec 2010 08:11:06 -0800 (PST) Received: from [IPv6:2001:718:1a02:7:201:80ff:fe65:dd1e] (unknown [IPv6:2001:718:1a02:7:201:80ff:fe65:dd1e]) by office2.cesnet.cz (Postfix) with ESMTPSA id 5AAB22CDE058; Fri, 10 Dec 2010 17:12:37 +0100 (CET) From: Ladislav Lhotka To: Martin Bjorklund In-Reply-To: <20101210.164720.61171376.mbj@tail-f.com> References: <20101210.152255.172617871.mbj@tail-f.com> <1291995696.26221.67.camel@behold> <20101210.164720.61171376.mbj@tail-f.com> Content-Type: text/plain; charset="UTF-8" Organization: CESNET Date: Fri, 10 Dec 2010 17:12:34 +0100 Message-ID: <1291997554.30936.2.camel@behold> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 16:11:09 -0000 On Pá, 2010-12-10 at 16:47 +0100, Martin Bjorklund wrote: > Hi, > > Ladislav Lhotka wrote: > > According to the ABNF, all chunks - including the first one - begin with > > LF, so I think all examples using the chunk framing should start with > > the empty line, i.e. either > > > > C: > > > > or > > > > S: > > > > to indicate the presence of LF. > > I think they do, don't they? Oh yes, sorry, I had the changes you sent on 30 November and didn't notice you had corrected this in the new version. Thanks, Lada > > > /martin -- Ladislav Lhotka, CESNET PGP Key ID: E74E8C0C From j.schoenwaelder@jacobs-university.de Fri Dec 10 12:31:15 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1B353A6BAF for ; Fri, 10 Dec 2010 12:31:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.085 X-Spam-Level: X-Spam-Status: No, score=-103.085 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pSTjiNOrXEQ for ; Fri, 10 Dec 2010 12:31:14 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id A79BA3A6BAD for ; Fri, 10 Dec 2010 12:31:14 -0800 (PST) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 677EDC001B; Fri, 10 Dec 2010 21:32:46 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id cUamhadCyOuB; Fri, 10 Dec 2010 21:32:46 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D223FC0014; Fri, 10 Dec 2010 21:32:45 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id AC51715EAAC2; Fri, 10 Dec 2010 21:32:40 +0100 (CET) Date: Fri, 10 Dec 2010 21:32:40 +0100 From: Juergen Schoenwaelder To: Martin Bjorklund Message-ID: <20101210203240.GB975@elstar.local> Mail-Followup-To: Martin Bjorklund , netconf@ietf.org References: <20101210.152255.172617871.mbj@tail-f.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101210.152255.172617871.mbj@tail-f.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 20:31:15 -0000 On Fri, Dec 10, 2010 at 03:22:55PM +0100, Martin Bjorklund wrote: > C: > C: > C: ## [...] > S: > S: > S: ## [...] > C: > C: > C: ## [...] > S: > S: > S: ## My understanding is that these empty lines are not necessarily needed. If this is correct, then these examples might lead people to believe these empty lines are needed and I would prefer that these empty lines are removed. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From lhotka@cesnet.cz Fri Dec 10 13:51:18 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 363F03A6BC7 for ; Fri, 10 Dec 2010 13:51:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.517 X-Spam-Level: X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kDoHUdlc-+-O for ; Fri, 10 Dec 2010 13:51:16 -0800 (PST) Received: from office2.cesnet.cz (office2.cesnet.cz [IPv6:2001:718:1:101::144:244]) by core3.amsl.com (Postfix) with ESMTP id 37E083A6BB3 for ; Fri, 10 Dec 2010 13:51:13 -0800 (PST) Received: from stardust-w.lhotkovi.cz (unknown [IPv6:2001:718:1a02:7:5ab0:35ff:fe73:8f1d]) by office2.cesnet.cz (Postfix) with ESMTPSA id 338182CDE058; Fri, 10 Dec 2010 22:52:44 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ladislav Lhotka In-Reply-To: <20101210203240.GB975@elstar.local> Date: Fri, 10 Dec 2010 22:52:43 +0100 Content-Transfer-Encoding: 7bit Message-Id: <65137B88-C4BC-462A-804C-50E6A82729B0@cesnet.cz> References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> To: Juergen Schoenwaelder X-Mailer: Apple Mail (2.1082) Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 21:51:18 -0000 On Dec 10, 2010, at 9:32 PM, Juergen Schoenwaelder wrote: > On Fri, Dec 10, 2010 at 03:22:55PM +0100, Martin Bjorklund wrote: > >> C: >> C: >> C: ## > > [...] > >> S: >> S: >> S: ## > > [...] > >> C: >> C: >> C: ## > > [...] > >> S: >> S: >> S: ## > > My understanding is that these empty lines are not necessarily needed. > If this is correct, then these examples might lead people to believe > these empty lines are needed and I would prefer that these empty lines > are removed. I agree. On the other hand, shouldn't the examples end with e.g. C: ## C: to indicate the LF *after* the double hash? Lada > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf -- Ladislav Lhotka, CESNET PGP Key ID: E74E8C0C From j.schoenwaelder@jacobs-university.de Fri Dec 10 13:58:13 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DACC28C158 for ; Fri, 10 Dec 2010 13:58:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.095 X-Spam-Level: X-Spam-Status: No, score=-103.095 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UynRDcFPMftF for ; Fri, 10 Dec 2010 13:58:12 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 212CA28C13B for ; Fri, 10 Dec 2010 13:58:12 -0800 (PST) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id F2717C0021; Fri, 10 Dec 2010 22:59:43 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id PGrNHyKQ5LEN; Fri, 10 Dec 2010 22:59:43 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 305C6C001B; Fri, 10 Dec 2010 22:59:43 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 1B7E315EAF6B; Fri, 10 Dec 2010 22:59:39 +0100 (CET) Date: Fri, 10 Dec 2010 22:59:39 +0100 From: Juergen Schoenwaelder To: Ladislav Lhotka Message-ID: <20101210215939.GA1377@elstar.local> Mail-Followup-To: Ladislav Lhotka , Martin Bjorklund , netconf@ietf.org References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> <65137B88-C4BC-462A-804C-50E6A82729B0@cesnet.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65137B88-C4BC-462A-804C-50E6A82729B0@cesnet.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 21:58:13 -0000 On Fri, Dec 10, 2010 at 10:52:43PM +0100, Ladislav Lhotka wrote: > I agree. On the other hand, shouldn't the examples end with e.g. > > C: ## > C: > > to indicate the LF *after* the double hash? We do not have a good way of visualizing line feeds that are distinct from the word processing line feeds. This again might be read as two line feeds - so its hardly better. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From mbj@tail-f.com Fri Dec 10 14:34:35 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF2B528C0CE for ; Fri, 10 Dec 2010 14:34:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.971 X-Spam-Level: X-Spam-Status: No, score=-1.971 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Or9pS-Ect73B for ; Fri, 10 Dec 2010 14:34:33 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 51DB73A6BD5 for ; Fri, 10 Dec 2010 14:34:33 -0800 (PST) Received: from localhost (c213-100-166-57.swipnet.se [213.100.166.57]) by mail.tail-f.com (Postfix) with ESMTPSA id 12A5F616001; Fri, 10 Dec 2010 23:36:05 +0100 (CET) Date: Fri, 10 Dec 2010 23:36:04 +0100 (CET) Message-Id: <20101210.233604.91186971.mbj@tail-f.com> To: j.schoenwaelder@jacobs-university.de From: Martin Bjorklund In-Reply-To: <20101210203240.GB975@elstar.local> References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 22:34:35 -0000 Juergen Schoenwaelder wrote: > On Fri, Dec 10, 2010 at 03:22:55PM +0100, Martin Bjorklund wrote: > > > C: > > C: > > C: ## > > [...] > > > S: > > S: > > S: ## > > [...] > > > C: > > C: > > C: ## > > [...] > > > S: > > S: > > S: ## > > My understanding is that these empty lines are not necessarily needed. > If this is correct, then these examples might lead people to believe > these empty lines are needed and I would prefer that these empty lines > are removed. Sure, that's an option. If so, we must also decrement each chunk size by 1. If that makes the examples more clear, that's fine with me. /martin From bertietf@bwijnen.net Tue Dec 14 23:53:43 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FBCA3A6E45 for ; Tue, 14 Dec 2010 23:53:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.143 X-Spam-Level: X-Spam-Status: No, score=-100.143 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QgjTg9YOQZb for ; Tue, 14 Dec 2010 23:53:42 -0800 (PST) Received: from relay.versatel.net (relay61.tele2.vuurwerk.nl [62.250.3.61]) by core3.amsl.com (Postfix) with ESMTP id 2BED73A6E7C for ; Tue, 14 Dec 2010 23:53:41 -0800 (PST) Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from ) id 1PSmCo-0005NL-8R; Wed, 15 Dec 2010 08:55:22 +0100 Message-ID: From: "Bert Wijnen \(IETF\)" To: "Netconf" , "Martin Bjorklund" References: <20101210.144016.249498658.mbj@tail-f.com> In-Reply-To: <20101210.144016.249498658.mbj@tail-f.com> Date: Wed, 15 Dec 2010 08:55:15 +0100 Organization: Consultant 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 Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18263 Subject: Re: [Netconf] list of 4741bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2010 07:53:43 -0000 Not having heard any objections to this, we suggest that Martin puts a new revision out for this document later this week. If you DO HAVE objections, PLEASE SPEAK up ASAP. Bert and Mehmet ----- Original Message ----- From: "Martin Bjorklund" To: Sent: Friday, December 10, 2010 2:40 PM Subject: [Netconf] list of 4741bis edits Hi, As requested by the chairs, this is a list of proposed edits for 4741bis. There are a few editorial changes, and two technical changes. One is a fix for the XML Schema bug reported by Kent, and one is a fix for the 'data' response element in the YANG module. /martin Section 4.2., paragraph 1: OLD: The message is sent in response to an operation. NEW: The message is sent in response to an message. Section 7.5., paragraph 6: OLD: A lock MUST not be granted if either of the following conditions is true: NEW: A lock MUST NOT be granted if either of the following conditions is true: Appendix B., paragraph 4: OLD: This schema defines the syntax for the NETCONF Message layer NEW: This schema defines the syntax for the NETCONF Messages layer Appendix B., paragraph 6: OLD: NEW: Appendix C., paragraph 46: OLD: output { container data { presence "An empty data container indicates that the request did not produce any results."; description "Copy of the source datastore subset which matched the filter criteria (if any)."; } } } NEW: output { anyxml data { description "Copy of the source datastore subset which matched the filter criteria (if any). An empty data container indicates that the request did not produce any results."; } } } Appendix C., paragraph 84: OLD: output { container data { presence "An empty data container indicates that the filter request did not match any results."; description "Copy of the running datastore subset and/or state data which matched the filter criteria (if any)."; } } } NEW: output { anyxml data { description "Copy of the running datastore subset and/or state data which matched the filter criteria (if any). An empty data container indicates that the request did not produce any results."; } } } _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From bertietf@bwijnen.net Wed Dec 15 01:15:30 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C4E33A6E52 for ; Wed, 15 Dec 2010 01:15:30 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Improper folded header field made up entirely of whitespace (char 20 hex): X-RIPE-Spam-Report: ...al Points: -2.9 points\n \n pts rule nam[...] X-Spam-Flag: NO X-Spam-Score: -102.507 X-Spam-Level: X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ka9pw7jsvi5S for ; Wed, 15 Dec 2010 01:15:29 -0800 (PST) Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id 675903A6E40 for ; Wed, 15 Dec 2010 01:15:27 -0800 (PST) Received: from dodo.ripe.net ([193.0.23.4]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1PSnTu-0006Fl-PF for netconf@ietf.org; Wed, 15 Dec 2010 10:17:07 +0100 Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from ) id 1PSnTu-0007JT-II for netconf@ietf.org; Wed, 15 Dec 2010 10:17:06 +0100 Message-ID: <4D088792.4050409@bwijnen.net> Date: Wed, 15 Dec 2010 10:17:06 +0100 From: "Bert (IETF) Wijnen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: netconf Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4c76f7ff2876aef8c19fa7787f3eda9b9 X-RIPE-Spam-Level: -- X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4c76f7ff2876aef8c19fa7787f3eda9b9 Subject: Re: [Netconf] list of 4741bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2010 09:15:30 -0000 We have seen (during the rfc4742bis discussion) some remarks about this piece of text in RFC4741bis: All NETCONF messages MUST be well-formed XML, encoded in UTF-8. If a peer receives a message that is not well-formedXML, it MUST reply with an 'operation-failed' error. We (still) believe this is what we have consensus for. This text is stronger now that we have proper framing, since valid messages that contain the ]]>]]> can no longer be chopped and end up as invalid. Does anybody have strong objections to leaving that as is? Thanks, Bert and Mehmet From biermana@Brocade.com Wed Dec 15 08:47:22 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E38128C1AB for ; Wed, 15 Dec 2010 08:47:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjxiVOoWQ-rT for ; Wed, 15 Dec 2010 08:47:21 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id 31F5D28C1AE for ; Wed, 15 Dec 2010 08:47:21 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oBFGfxCk012509; Wed, 15 Dec 2010 08:49:01 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.141.11]) by mx0b-000f0801.pphosted.com with ESMTP id t717ar0bc-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 15 Dec 2010 08:49:01 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE02.corp.brocade.com (144.49.141.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 15 Dec 2010 08:54:31 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Wed, 15 Dec 2010 08:49:00 -0800 From: Andy Bierman To: "Bert (IETF) Wijnen" , netconf Date: Wed, 15 Dec 2010 08:48:59 -0800 Thread-Topic: [Netconf] list of 4741bis edits Thread-Index: AcucONzG8mJsWVEYROOxYhrXVO3LgAAPa2vw Message-ID: References: <4D088792.4050409@bwijnen.net> In-Reply-To: <4D088792.4050409@bwijnen.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-15_09:2010-12-15, 2010-12-15, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012150081 Subject: Re: [Netconf] list of 4741bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2010 16:47:22 -0000 Hi, I object to the 'MUST send an ' text. It needs to be spelled out that: - the server may not have the start tag available so the may not have the original attributes, including message-id - the client is assumed to be expecting an but this is not true if the message was a data injection attack - the client may not be able to do anything useful with an with no message-id - if the malformed XML is due to the client or server dropping the TCP connection, then the server cannot send an - there is no requirement that a server parse XML tags in sequence or that each XML tag be made available to the operations layer. A server may implement a DOM design. In either case, the server will get valid XML or get nothing from the XML parser (e.g., libxml2 EOF) - if the server does not have the message-id available, then MUST send i= s not appropriate, since the client cannot reliably correlate the reply with= a request. Andy -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Bert (IETF) Wijnen Sent: Wednesday, December 15, 2010 1:17 AM To: netconf Subject: Re: [Netconf] list of 4741bis edits We have seen (during the rfc4742bis discussion) some remarks about this piece of text in RFC4741bis: All NETCONF messages MUST be well-formed XML, encoded in UTF-8. If a peer receives a message that is not well-formedXML, it MUST reply with an 'operation-failed' error. We (still) believe this is what we have consensus for. This text is stronge= r now that we have proper framing, since valid messages that contain the ]]>]]> can no longer be chopped and end up as invalid. Does anybody have strong objections to leaving that as is? Thanks, Bert and Mehmet _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From mehmet.ersue@nsn.com Thu Dec 16 09:33:18 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EC843A690D for ; Thu, 16 Dec 2010 09:33:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.452 X-Spam-Level: X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 101Z-xJlmdzK for ; Thu, 16 Dec 2010 09:33:17 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 06DE93A6902 for ; Thu, 16 Dec 2010 09:33:16 -0800 (PST) Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id oBGHZ01K014209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Dec 2010 18:35:00 +0100 Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id oBGHYtVe023542; Thu, 16 Dec 2010 18:34:59 +0100 Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 18:34:59 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 16 Dec 2010 18:34:56 +0100 Message-ID: <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> In-Reply-To: <20101210.233604.91186971.mbj@tail-f.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Submission of 4742bis WAS:RE: [Netconf] list of 4742bis edits Thread-Index: AcuYuqfd5vOQMcsYQ7eg8lMDyNYiSAEi8png References: <20101210.152255.172617871.mbj@tail-f.com><20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> From: "Ersue, Mehmet (NSN - DE/Munich)" To: , "ext Margaret Wasserman" X-OriginalArrivalTime: 16 Dec 2010 17:34:59.0716 (UTC) FILETIME=[902AE440:01CB9D47] Subject: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 17:33:18 -0000 Hi All, AFAICS we don't have any consensus to do a change and can see the original proposal from Martin as the result=20 of the discussion. If there is anybody who sees the discussion differently please state so at the latest by Friday EOB.=20 If no, Margaret is going to submit 4742bis on Monday. Mehmet > -----Original Message----- > From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On > Behalf Of ext Martin Bjorklund > Sent: Friday, December 10, 2010 11:36 PM > To: j.schoenwaelder@jacobs-university.de > Cc: netconf@ietf.org > Subject: Re: [Netconf] list of 4742bis edits >=20 > Juergen Schoenwaelder wrote: > > On Fri, Dec 10, 2010 at 03:22:55PM +0100, Martin Bjorklund wrote: > > > > > C: > > > C: > > > C: ## > > > > [...] > > > > > S: > > > S: > > > S: ## > > > > [...] > > > > > C: > > > C: > > > C: ## > > > > [...] > > > > > S: > > > S: > > > S: ## > > > > My understanding is that these empty lines are not necessarily > needed. > > If this is correct, then these examples might lead people to believe > > these empty lines are needed and I would prefer that these empty > lines > > are removed. >=20 > Sure, that's an option. If so, we must also decrement each chunk > size by 1. If that makes the examples more clear, that's fine with me. >=20 >=20 > /martin > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf From j.schoenwaelder@jacobs-university.de Thu Dec 16 12:27:20 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CEBE3A69A5 for ; Thu, 16 Dec 2010 12:27:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.103 X-Spam-Level: X-Spam-Status: No, score=-103.103 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEGxz6OM0JiB for ; Thu, 16 Dec 2010 12:27:19 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 1346B3A6924 for ; Thu, 16 Dec 2010 12:27:19 -0800 (PST) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id D495CC0048; Thu, 16 Dec 2010 21:29:03 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id a6a3g3NfxRaO; Thu, 16 Dec 2010 21:29:03 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C28B7C004A; Thu, 16 Dec 2010 21:29:02 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 56C7915FC45D; Thu, 16 Dec 2010 21:28:56 +0100 (CET) Date: Thu, 16 Dec 2010 21:28:55 +0100 From: Juergen Schoenwaelder To: "Ersue, Mehmet (NSN - DE/Munich)" Message-ID: <20101216202855.GA22164@elstar.local> Mail-Followup-To: "Ersue, Mehmet (NSN - DE/Munich)" , netconf@ietf.org, ext Margaret Wasserman References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ext Margaret Wasserman , netconf@ietf.org Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 20:27:20 -0000 On Thu, Dec 16, 2010 at 06:34:56PM +0100, Ersue, Mehmet (NSN - DE/Munich) wrote: > Hi All, > > AFAICS we don't have any consensus to do a change and > can see the original proposal from Martin as the result > of the discussion. > > If there is anybody who sees the discussion differently > please state so at the latest by Friday EOB. I have not seen anybody speaking up against the suggested removable of empty lines. Lada was in favour, Martin said the numbers need adjusted, which is correct. Am I missing emails? I also checked the archive to be sure... /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From ietf@andybierman.com Thu Dec 16 13:03:21 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2449F3A6934 for ; Thu, 16 Dec 2010 13:03:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhuB+f8Kyims for ; Thu, 16 Dec 2010 13:03:20 -0800 (PST) Received: from nm10-vm0.bullet.mail.ne1.yahoo.com (nm10-vm0.bullet.mail.ne1.yahoo.com [98.138.91.72]) by core3.amsl.com (Postfix) with SMTP id 6340C3A68E1 for ; Thu, 16 Dec 2010 13:03:20 -0800 (PST) Received: from [98.138.90.53] by nm10.bullet.mail.ne1.yahoo.com with NNFMP; 16 Dec 2010 21:05:05 -0000 Received: from [98.138.87.6] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 16 Dec 2010 21:05:05 -0000 Received: from [127.0.0.1] by omp1006.mail.ne1.yahoo.com with NNFMP; 16 Dec 2010 21:05:05 -0000 X-Yahoo-Newman-Id: 685999.34436.bm@omp1006.mail.ne1.yahoo.com Received: (qmail 92794 invoked from network); 16 Dec 2010 21:05:05 -0000 Received: from [192.168.0.14] (ietf@75.84.164.152 with plain) by smtp105.sbc.mail.ne1.yahoo.com with SMTP; 16 Dec 2010 13:05:02 -0800 PST X-Yahoo-SMTP: Z6xhxCCswBAlhcxjVNwaQtp4EKpLdTUUf5Nx_pGy81o- X-YMail-OSG: jDYVn2IVM1kB60lX52FfvqeE98or5dqmYorOsCwZzGxjMrs C94iLR3Ph6wlA6c5joFBaPdXnwxDXCXoEs2cJ1z0CwUIR8bIg_1rD8oOxXCE yOnHEU7OCxKIHRwZDpDy9j.daUvWBgdUYdb5WwRSW1ppaPPjuuaOh_CSAihi D24umKHuF3s6C7f.KDHMsDJWm9aCR8jizCDVlAIXuSlmdatPb7PRi4W9XoeH b41UoYoMdaAjI0HoPZBsLRoKcMQl59b6xwjeYugDrp5GBOQT26l.h97MsFnT _NVSW_1hzOiHUBpTfrEdl1L_m2CqDzU7TvMuNa.Q- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4D0A7F06.9030204@andybierman.com> Date: Thu, 16 Dec 2010 13:05:10 -0800 From: Andy Bierman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: "Ersue, Mehmet \(NSN - DE/Munich\)" , netconf@ietf.org, ext Margaret Wasserman References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> <20101216202855.GA22164@elstar.local> In-Reply-To: <20101216202855.GA22164@elstar.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 21:03:21 -0000 On 12/16/2010 12:28 PM, Juergen Schoenwaelder wrote: > On Thu, Dec 16, 2010 at 06:34:56PM +0100, Ersue, Mehmet (NSN - DE/Munich) wrote: >> Hi All, >> >> AFAICS we don't have any consensus to do a change and >> can see the original proposal from Martin as the result >> of the discussion. >> >> If there is anybody who sees the discussion differently >> please state so at the latest by Friday EOB. > > I have not seen anybody speaking up against the suggested removable of > empty lines. Lada was in favour, Martin said the numbers need adjusted, > which is correct. Am I missing emails? I also checked the archive to > be sure... > I just want the text to mention whether the example has an EOLN 0xa at the end. It should be explained why 1 example is different than the other 2. I don't care which way it is done (blank line or not). > /js > Andy From mehmet.ersue@nsn.com Thu Dec 16 13:32:16 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DC713A69F3 for ; Thu, 16 Dec 2010 13:32:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.455 X-Spam-Level: X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXbeQtIdiGzi for ; Thu, 16 Dec 2010 13:32:15 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 8D0213A69F1 for ; Thu, 16 Dec 2010 13:32:15 -0800 (PST) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id oBGLXwk7003370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Dec 2010 22:33:58 +0100 Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id oBGLXtmV015385; Thu, 16 Dec 2010 22:33:58 +0100 Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 22:33:56 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 16 Dec 2010 22:33:52 +0100 Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6401604110@DEMUEXC006.nsn-intra.net> In-Reply-To: <4D0A7F06.9030204@andybierman.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits Thread-Index: AcudZOuW52F8mKdLTtSFPNVvZdumiQAA+w7A References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> <20101216202855.GA22164@elstar.local> <4D0A7F06.9030204@andybierman.com> From: "Ersue, Mehmet (NSN - DE/Munich)" To: "ext Andy Bierman" , , "ext Margaret Wasserman" X-OriginalArrivalTime: 16 Dec 2010 21:33:56.0190 (UTC) FILETIME=[F15F37E0:01CB9D68] Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 21:32:16 -0000 Please provide concrete OLD/NEW text. Thank you. Mehmet > -----Original Message----- > From: ext Andy Bierman [mailto:ietf@andybierman.com] > Sent: Thursday, December 16, 2010 10:05 PM > To: Ersue, Mehmet (NSN - DE/Munich); netconf@ietf.org; ext Margaret > Wasserman > Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis > edits >=20 > On 12/16/2010 12:28 PM, Juergen Schoenwaelder wrote: > > On Thu, Dec 16, 2010 at 06:34:56PM +0100, Ersue, Mehmet (NSN - > DE/Munich) wrote: > >> Hi All, > >> > >> AFAICS we don't have any consensus to do a change and > >> can see the original proposal from Martin as the result > >> of the discussion. > >> > >> If there is anybody who sees the discussion differently > >> please state so at the latest by Friday EOB. > > > > I have not seen anybody speaking up against the suggested removable > of > > empty lines. Lada was in favour, Martin said the numbers need > adjusted, > > which is correct. Am I missing emails? I also checked the archive to > > be sure... > > >=20 > I just want the text to mention whether the example has an EOLN 0xa at > the end. > It should be explained why 1 example is different than the other 2. > I don't care which way it is done (blank line or not). >=20 > > /js > > >=20 > Andy From biermana@Brocade.com Thu Dec 16 13:41:41 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E96A3A6A02 for ; Thu, 16 Dec 2010 13:41:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.012 X-Spam-Level: X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNl+x1ZLOD+d for ; Thu, 16 Dec 2010 13:41:40 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id 943353A6A01 for ; Thu, 16 Dec 2010 13:41:40 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oBGLgYKg025313; Thu, 16 Dec 2010 13:43:23 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.141.11]) by mx0b-000f0801.pphosted.com with ESMTP id t7tmar0b1-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 16 Dec 2010 13:43:23 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE02.corp.brocade.com (144.49.141.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 16 Dec 2010 13:48:52 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Thu, 16 Dec 2010 13:43:22 -0800 From: Andy Bierman To: "Ersue, Mehmet (NSN - DE/Munich)" , ext Andy Bierman , "netconf@ietf.org" , "ext Margaret Wasserman" Date: Thu, 16 Dec 2010 13:43:19 -0800 Thread-Topic: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits Thread-Index: AcudZOuW52F8mKdLTtSFPNVvZdumiQAA+w7AAAA+jpA= Message-ID: References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> <20101216202855.GA22164@elstar.local> <4D0A7F06.9030204@andybierman.com> <80A0822C5E9A4440A5117C2F4CD36A6401604110@DEMUEXC006.nsn-intra.net> In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6401604110@DEMUEXC006.nsn-intra.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-16_10:2010-12-16, 2010-12-16, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012160160 Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 21:41:41 -0000 OLD: #79 xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> ## Conceptually, the SSH Transport layer encodes messages sent by the Messages layer, and decodes messages received on the SSH channel before passing them to the Messages layer. NEW: #79 xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> ## Note that there is no newline character after the 'rpc' end tag, so there is no blank line generated before the '##' line. Conceptually, the SSH Transport layer encodes messages sent by the Messages layer, and decodes messages received on the SSH channel before passing them to the Messages layer. -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Ersue, Mehmet (NSN - DE/Munich) Sent: Thursday, December 16, 2010 1:34 PM To: ext Andy Bierman; netconf@ietf.org; ext Margaret Wasserman Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits Please provide concrete OLD/NEW text. Thank you. Mehmet > -----Original Message----- > From: ext Andy Bierman [mailto:ietf@andybierman.com] > Sent: Thursday, December 16, 2010 10:05 PM > To: Ersue, Mehmet (NSN - DE/Munich); netconf@ietf.org; ext Margaret > Wasserman > Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis > edits >=20 > On 12/16/2010 12:28 PM, Juergen Schoenwaelder wrote: > > On Thu, Dec 16, 2010 at 06:34:56PM +0100, Ersue, Mehmet (NSN - > DE/Munich) wrote: > >> Hi All, > >> > >> AFAICS we don't have any consensus to do a change and > >> can see the original proposal from Martin as the result > >> of the discussion. > >> > >> If there is anybody who sees the discussion differently > >> please state so at the latest by Friday EOB. > > > > I have not seen anybody speaking up against the suggested removable > of > > empty lines. Lada was in favour, Martin said the numbers need > adjusted, > > which is correct. Am I missing emails? I also checked the archive to > > be sure... > > >=20 > I just want the text to mention whether the example has an EOLN 0xa at > the end. > It should be explained why 1 example is different than the other 2. > I don't care which way it is done (blank line or not). >=20 > > /js > > >=20 > Andy _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From mehmet.ersue@nsn.com Thu Dec 16 14:01:53 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 180AC3A69EC for ; Thu, 16 Dec 2010 14:01:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.457 X-Spam-Level: X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kc3NbhSqo5p for ; Thu, 16 Dec 2010 14:01:52 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id E48873A69DB for ; Thu, 16 Dec 2010 14:01:51 -0800 (PST) Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id oBGM3Lkd001737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Dec 2010 23:03:21 +0100 Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id oBGM3LBr032615; Thu, 16 Dec 2010 23:03:21 +0100 Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Dec 2010 23:03:21 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 16 Dec 2010 23:03:18 +0100 Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6401604112@DEMUEXC006.nsn-intra.net> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits Thread-Index: AcudZOuW52F8mKdLTtSFPNVvZdumiQAA+w7AAAA+jpAAAMRSkA== References: <20101210.152255.172617871.mbj@tail-f.com><20101210203240.GB975@elstar.local><20101210.233604.91186971.mbj@tail-f.com><80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net><20101216202855.GA22164@elstar.local> <4D0A7F06.9030204@andybierman.com> <80A0822C5E9A4440A5117C2F4CD36A6401604110@DEMUEXC006.nsn-intra.net> From: "Ersue, Mehmet (NSN - DE/Munich)" To: "ext Andy Bierman" , "ext Andy Bierman" , , "ext Margaret Wasserman" X-OriginalArrivalTime: 16 Dec 2010 22:03:21.0426 (UTC) FILETIME=[0D88DB20:01CB9D6D] Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2010 22:01:53 -0000 Sounds good to me. Mehmet > -----Original Message----- > From: ext Andy Bierman [mailto:biermana@Brocade.com] > Sent: Thursday, December 16, 2010 10:43 PM > To: Ersue, Mehmet (NSN - DE/Munich); ext Andy Bierman; > netconf@ietf.org; ext Margaret Wasserman > Subject: RE: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis > edits >=20 >=20 > OLD: >=20 > #79 > xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > > > ## >=20 > Conceptually, the SSH Transport layer encodes messages sent by the > Messages layer, and decodes messages received on the SSH channel > before passing them to the Messages layer. >=20 >=20 > NEW: >=20 > #79 > xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > > > ## >=20 > Note that there is no newline character after the 'rpc' end tag, so > there > is no blank line generated before the '##' line. >=20 > Conceptually, the SSH Transport layer encodes messages sent by the > Messages layer, and decodes messages received on the SSH channel > before passing them to the Messages layer. >=20 >=20 > -----Original Message----- > From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On > Behalf Of Ersue, Mehmet (NSN - DE/Munich) > Sent: Thursday, December 16, 2010 1:34 PM > To: ext Andy Bierman; netconf@ietf.org; ext Margaret Wasserman > Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis > edits >=20 > Please provide concrete OLD/NEW text. > Thank you. >=20 > Mehmet >=20 >=20 > > -----Original Message----- > > From: ext Andy Bierman [mailto:ietf@andybierman.com] > > Sent: Thursday, December 16, 2010 10:05 PM > > To: Ersue, Mehmet (NSN - DE/Munich); netconf@ietf.org; ext Margaret > > Wasserman > > Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis > > edits > > > > On 12/16/2010 12:28 PM, Juergen Schoenwaelder wrote: > > > On Thu, Dec 16, 2010 at 06:34:56PM +0100, Ersue, Mehmet (NSN - > > DE/Munich) wrote: > > >> Hi All, > > >> > > >> AFAICS we don't have any consensus to do a change and > > >> can see the original proposal from Martin as the result > > >> of the discussion. > > >> > > >> If there is anybody who sees the discussion differently > > >> please state so at the latest by Friday EOB. > > > > > > I have not seen anybody speaking up against the suggested removable > > of > > > empty lines. Lada was in favour, Martin said the numbers need > > adjusted, > > > which is correct. Am I missing emails? I also checked the archive > to > > > be sure... > > > > > > > I just want the text to mention whether the example has an EOLN 0xa > at > > the end. > > It should be explained why 1 example is different than the other 2. > > I don't care which way it is done (blank line or not). > > > > > /js > > > > > > > Andy > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf From lhotka@cesnet.cz Fri Dec 17 00:50:40 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90BB3A698C for ; Fri, 17 Dec 2010 00:50:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.53 X-Spam-Level: X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJ7K9cxhSTwP for ; Fri, 17 Dec 2010 00:50:40 -0800 (PST) Received: from office2.cesnet.cz (office2.cesnet.cz [IPv6:2001:718:1:101::144:244]) by core3.amsl.com (Postfix) with ESMTP id 51AB13A6AB4 for ; Fri, 17 Dec 2010 00:50:38 -0800 (PST) Received: from [IPv6:2001:718:1a02:7:201:80ff:fe65:dd1e] (unknown [IPv6:2001:718:1a02:7:201:80ff:fe65:dd1e]) by office2.cesnet.cz (Postfix) with ESMTPSA id F035F2CDE057; Fri, 17 Dec 2010 09:52:23 +0100 (CET) From: Ladislav Lhotka To: Andy Bierman In-Reply-To: References: <20101210.152255.172617871.mbj@tail-f.com> <20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> <80A0822C5E9A4440A5117C2F4CD36A64016040B3@DEMUEXC006.nsn-intra.net> <20101216202855.GA22164@elstar.local> <4D0A7F06.9030204@andybierman.com> <80A0822C5E9A4440A5117C2F4CD36A6401604110@DEMUEXC006.nsn-intra.net> Content-Type: text/plain; charset="UTF-8" Organization: CESNET Date: Fri, 17 Dec 2010 09:52:23 +0100 Message-ID: <1292575943.5152.2.camel@behold> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Cc: ext, Margaret Wasserman , "netconf@ietf.org" Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 08:50:40 -0000 On Čt, 2010-12-16 at 13:43 -0800, Andy Bierman wrote: > OLD: > > #79 > xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > > > ## > > Conceptually, the SSH Transport layer encodes messages sent by the > Messages layer, and decodes messages received on the SSH channel > before passing them to the Messages layer. > > > NEW: > > #79 > xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > > > ## > > Note that there is no newline character after the 'rpc' end tag, so there > is no blank line generated before the '##' line. > > Conceptually, the SSH Transport layer encodes messages sent by the > Messages layer, and decodes messages received on the SSH channel > before passing them to the Messages layer. +1. Lada > > > -----Original Message----- > From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf Of Ersue, Mehmet (NSN - DE/Munich) > Sent: Thursday, December 16, 2010 1:34 PM > To: ext Andy Bierman; netconf@ietf.org; ext Margaret Wasserman > Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits > > Please provide concrete OLD/NEW text. > Thank you. > > Mehmet > > > > -----Original Message----- > > From: ext Andy Bierman [mailto:ietf@andybierman.com] > > Sent: Thursday, December 16, 2010 10:05 PM > > To: Ersue, Mehmet (NSN - DE/Munich); netconf@ietf.org; ext Margaret > > Wasserman > > Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis > > edits > > > > On 12/16/2010 12:28 PM, Juergen Schoenwaelder wrote: > > > On Thu, Dec 16, 2010 at 06:34:56PM +0100, Ersue, Mehmet (NSN - > > DE/Munich) wrote: > > >> Hi All, > > >> > > >> AFAICS we don't have any consensus to do a change and > > >> can see the original proposal from Martin as the result > > >> of the discussion. > > >> > > >> If there is anybody who sees the discussion differently > > >> please state so at the latest by Friday EOB. > > > > > > I have not seen anybody speaking up against the suggested removable > > of > > > empty lines. Lada was in favour, Martin said the numbers need > > adjusted, > > > which is correct. Am I missing emails? I also checked the archive to > > > be sure... > > > > > > > I just want the text to mention whether the example has an EOLN 0xa at > > the end. > > It should be explained why 1 example is different than the other 2. > > I don't care which way it is done (blank line or not). > > > > > /js > > > > > > > Andy > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf -- Ladislav Lhotka, CESNET PGP Key ID: E74E8C0C From mbj@tail-f.com Fri Dec 17 01:09:20 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B8D03A695A for ; Fri, 17 Dec 2010 01:09:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKmlhrMtsqYz for ; Fri, 17 Dec 2010 01:09:19 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id A425D3A6926 for ; Fri, 17 Dec 2010 01:09:19 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id F41AF616001; Fri, 17 Dec 2010 10:11:04 +0100 (CET) Date: Fri, 17 Dec 2010 10:11:03 +0100 (CET) Message-Id: <20101217.101103.38395162.mbj@tail-f.com> To: lhotka@cesnet.cz From: Martin Bjorklund In-Reply-To: <1292575943.5152.2.camel@behold> References: <80A0822C5E9A4440A5117C2F4CD36A6401604110@DEMUEXC006.nsn-intra.net> <1292575943.5152.2.camel@behold> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable Cc: ext@core3.amsl.com, biermana@Brocade.com, netconf@ietf.org, margaretw42@gmail.com Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 09:09:20 -0000 Ladislav Lhotka wrote: > On =C8t, 2010-12-16 at 13:43 -0800, Andy Bierman wrote: > > OLD: > > = > > #79 > > xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > > > > > > ## > > = > > Conceptually, the SSH Transport layer encodes messages sent by th= e > > Messages layer, and decodes messages received on the SSH channel > > before passing them to the Messages layer. > > = > > = > > NEW: > > = > > #79 > > xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > > > > > > ## > > = > > Note that there is no newline character after the 'rpc' end tag, = so there > > is no blank line generated before the '##' line. > > = > > Conceptually, the SSH Transport layer encodes messages sent by th= e > > Messages layer, and decodes messages received on the SSH channel > > before passing them to the Messages layer. > = > +1. +1 /martin From phil@juniper.net Fri Dec 17 10:48:58 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E16C33A6BBA for ; Fri, 17 Dec 2010 10:48:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.589 X-Spam-Level: X-Spam-Status: No, score=-6.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cy5-N3WTTbIw for ; Fri, 17 Dec 2010 10:48:58 -0800 (PST) Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by core3.amsl.com (Postfix) with ESMTP id 82B2B3A6974 for ; Fri, 17 Dec 2010 10:48:56 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTQuxArJnhdo8nWCRakzS+Acerk0ykCbN@postini.com; Fri, 17 Dec 2010 10:50:45 PST Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 17 Dec 2010 10:47:18 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id oBHIlHU06264; Fri, 17 Dec 2010 10:47:17 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id oBHIPO4M099764; Fri, 17 Dec 2010 18:25:24 GMT (envelope-from phil@idle.juniper.net) Message-ID: <201012171825.oBHIPO4M099764@idle.juniper.net> To: Ladislav Lhotka Date: Fri, 17 Dec 2010 13:25:24 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain Cc: ext@core3.amsl.com, Andy Bierman , "netconf@ietf.org" , Margaret Wasserman Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 18:48:59 -0000 Ladislav Lhotka writes: >> Note that there is no newline character after the 'rpc' end tag, so there >> is no blank line generated before the '##' line. How about: Note that in this instance there is no newline .... since there certainly could be a newline there. Thanks, Phil From biermana@Brocade.com Fri Dec 17 11:21:27 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A96F3A6BC9 for ; Fri, 17 Dec 2010 11:21:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.022 X-Spam-Level: X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[AWL=0.243, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxFqK04r2fp3 for ; Fri, 17 Dec 2010 11:21:26 -0800 (PST) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by core3.amsl.com (Postfix) with ESMTP id C5FA63A6BD1 for ; Fri, 17 Dec 2010 11:21:26 -0800 (PST) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.4/8.14.4) with SMTP id oBHJMltr025568; Fri, 17 Dec 2010 11:23:09 -0800 Received: from hq1-exedge.brocade.com (hq1-exedge.brocade.com [144.49.140.11]) by mx0b-000f0801.pphosted.com with ESMTP id t8d4p80yr-3 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 17 Dec 2010 11:23:09 -0800 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXEDGE01.corp.brocade.com (144.49.140.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 17 Dec 2010 11:23:48 -0800 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::6452:4b5c:f595:4894]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Fri, 17 Dec 2010 11:23:06 -0800 From: Andy Bierman To: Phil Shafer , Ladislav Lhotka Date: Fri, 17 Dec 2010 11:23:05 -0800 Thread-Topic: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits Thread-Index: AcueG1ErGfCJEUWiTpmnP4cgnawopQABEoRg Message-ID: References: <201012171825.oBHIPO4M099764@idle.juniper.net> In-Reply-To: <201012171825.oBHIPO4M099764@idle.juniper.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-12-17_07:2010-12-17, 2010-12-17, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1010190000 definitions=main-1012170121 Cc: "ext@core3.amsl.com" , Margaret Wasserman , "netconf@ietf.org" Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 19:21:27 -0000 OK -- how about: Note that in this example, there is no newline ... Andy -----Original Message----- From: Phil Shafer [mailto:phil@juniper.net]=20 Sent: Friday, December 17, 2010 10:25 AM To: Ladislav Lhotka Cc: Andy Bierman; ext@core3.amsl.com; Margaret Wasserman; netconf@ietf.org Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits= =20 Ladislav Lhotka writes: >> Note that there is no newline character after the 'rpc' end tag, so th= ere >> is no blank line generated before the '##' line. How about: Note that in this instance there is no newline .... since there certainly could be a newline there. Thanks, Phil From phil@juniper.net Fri Dec 17 11:48:30 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA4473A6BE2 for ; Fri, 17 Dec 2010 11:48:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.59 X-Spam-Level: X-Spam-Status: No, score=-6.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cK6w2zRUVSXz for ; Fri, 17 Dec 2010 11:48:30 -0800 (PST) Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id 2DF033A6BC1 for ; Fri, 17 Dec 2010 11:48:18 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTQu+7U7ClyM9/bztiGYgFscVSFR/5ojO@postini.com; Fri, 17 Dec 2010 11:50:18 PST Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 17 Dec 2010 11:49:32 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id oBHJnVU36432; Fri, 17 Dec 2010 11:49:31 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id oBHJRdNv000447; Fri, 17 Dec 2010 19:27:39 GMT (envelope-from phil@idle.juniper.net) Message-ID: <201012171927.oBHJRdNv000447@idle.juniper.net> To: Andy Bierman In-Reply-To: Date: Fri, 17 Dec 2010 14:27:39 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain Cc: "ext@core3.amsl.com" , "netconf@ietf.org" , Margaret Wasserman Subject: Re: [Netconf] Submission of 4742bis WAS:RE: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 19:48:31 -0000 Andy Bierman writes: >Note that in this example, there is no newline ... Sounds fine. Merry Christmas, Phil From iesg-secretary@ietf.org Mon Dec 20 10:09:03 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E47763A6AA1; Mon, 20 Dec 2010 10:09:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.532 X-Spam-Level: X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bCO4d9bOmnjx; Mon, 20 Dec 2010 10:09:03 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99F573A6AA5; Mon, 20 Dec 2010 10:09:02 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20101220180902.12485.94797.idtracker@localhost> Date: Mon, 20 Dec 2010 10:09:02 -0800 Cc: Internet Architecture Board , netconf mailing list , netconf chair , RFC Editor Subject: [Netconf] Protocol Action: 'With-defaults capability for NETCONF' to Proposed Standard (draft-ietf-netconf-with-defaults-14.txt) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2010 18:09:04 -0000 The IESG has approved the following document: - 'With-defaults capability for NETCONF' (draft-ietf-netconf-with-defaults-14.txt) as a Proposed Standard This document is the product of the Network Configuration Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-netconf-with-defaults/ Technical Summary The NETCONF protocol defines ways to read and edit configuration data from a NETCONF server. In some cases, part of this data may not be set by the NETCONF client, but rather a default value known to the server is used instead. In many situations the NETCONF client has a priori knowledge about default data, so the NETCONF server does not need to save it in a NETCONF configuration datastore or send it to the client in a retrieval operation reply. In other situations the NETCONF client will need this data from the server. Not all server implementations treat this default data the same way. This document defines a capability-based extension to the NETCONF protocol that allows the NETCONF client to identify how defaults are processed by the server, and also defines new mechanisms for client control of server processing of default data. Working Group Summary The working group went over several versions of the document. The comments and reviews helped improve the document a lot and brought us to consensus on the 9th revision of the document. Document Quality There are preliminary implementations of this protocol and updates to comply with this spec are in plan. Others are planning to implement this spec too. Personnel Bert Wijnen is the Document Shepherd. Dan Romascanu is the Responsible Area Director. RFC Editor Note sec 1, para 1, add missing word OLD: A priori knowledge can be obtained, e.g., a document formally describing the data models supported by the NETCONF server. NEW: A priori knowledge can be obtained, e.g., from a document formally describing the data models supported by the NETCONF server. --------------------------------------------- sec 1.2 point 1: change word OLD: The actual nodes omitted depends on the defaults handling behavior used by the server. NEW: The actual nodes omitted depend on the defaults handling behavior used by the server. --------------------------------------------- sec 2, para 1, new last sentence OLD: Instead of forcing a single implementation strategy, this document allows a server to advertise a particular style of defaults handling, and the client can adjust accordingly. NEW: Instead of forcing a single implementation strategy, this document allows a server to advertise a particular style of defaults handling, and the client can adjust accordingly. Client implementations are expected to be powerful enough to support all three of the server basic defaults handling modes. --------------------------------------------- sec 8, para 2, sentence 2: change word OLD: The security consideration of [I-D.ietf-netconf-4741bis] apply to this document as well. NEW: The security consideration of [I-D.ietf-netconf-4741bis] applies to this document as well. From Internet-Drafts@ietf.org Mon Dec 20 14:00:02 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BAA23A6AE1; Mon, 20 Dec 2010 14:00:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.491 X-Spam-Level: X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lgvb5lFT-FMz; Mon, 20 Dec 2010 14:00:01 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FF603A6903; Mon, 20 Dec 2010 14:00:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20101220220001.7530.51039.idtracker@localhost> Date: Mon, 20 Dec 2010 14:00:01 -0800 Cc: netconf@ietf.org Subject: [Netconf] I-D Action:draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2010 22:00:02 -0000 --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 : Using the NETCONF Configuration Protocol over Secure Shell (SSH) Author(s) : M. Wasserman, T. Goddard Filename : draft-ietf-netconf-rfc4742bis-05.txt Pages : 13 Date : 2010-12-20 This document describes a method for invoking and running the NETCONF protocol within a Secure Shell (SSH) session as an SSH subsystem. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-netconf-rfc4742bis-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ 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: Message/External-body; name="draft-ietf-netconf-rfc4742bis-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-12-20134614.I-D@ietf.org> --NextPart-- From kwatsen@juniper.net Mon Dec 20 14:54:59 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B51EF3A691D for ; Mon, 20 Dec 2010 14:54:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Y2ALgfQJ6FX for ; Mon, 20 Dec 2010 14:54:58 -0800 (PST) Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by core3.amsl.com (Postfix) with ESMTP id BE0273A6900 for ; Mon, 20 Dec 2010 14:54:58 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKTQ/fNanxKlDb3hkAPj+V01FYrePGrQG4@postini.com; Mon, 20 Dec 2010 14:56:53 PST Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Mon, 20 Dec 2010 14:55:33 -0800 From: Kent Watsen To: "netconf@ietf.org" Date: Mon, 20 Dec 2010 14:55:31 -0800 Thread-Topic: [Netconf] 4741bis-04 has non-deterministic schema Thread-Index: AcuS3a9MFvsxktVfRueN9sptqmVXVgASpjfQA1oo+rA= Message-ID: <84600D05C20FF943918238042D7670FD374534F4BC@EMBX01-HQ.jnpr.net> References: <84600D05C20FF943918238042D7670FD374419AF64@EMBX01-HQ.jnpr.net> <20101203.123111.32109474.mbj@tail-f.com> <84600D05C20FF943918238042D7670FD3744361C2E@EMBX01-HQ.jnpr.net> In-Reply-To: <84600D05C20FF943918238042D7670FD3744361C2E@EMBX01-HQ.jnpr.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [Netconf] 4741bis-04 has non-deterministic schema X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2010 22:54:59 -0000 Just a quick update (nothing effecting 4741bis-04) to correct my previous p= osting, in case someone looks at this in the future... Noticing that the NETCONF XML example draft-ietf-netmod-yang-13#section-4.2= .9 doesn't have any namespace prefixes: acmefw-2.3 means that what I posted on Dec 3rd shouldn't have either. To fix this, I = modified the schema attributes in the "my-rpcs.xsd" file as follows: Which then allows (according to `xmllint --schema my-rpc.xsd my-rpc.xml`) t= he rpc to omit the prefixes. Here is the updated rpc sans prefixes: token Notes: - XMLSpy could not validate this anymore since the schema no=20 longer specifies the XSD to validate against - removing the "xmlns:dmi" line wasn't technically required, but I did anyway as it was no longer needed Thanks, Kent From bertietf@bwijnen.net Tue Dec 21 04:17:40 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC7043A69EC for ; Tue, 21 Dec 2010 04:17:40 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Improper folded header field made up entirely of whitespace (char 20 hex): X-RIPE-Spam-Report: ...al Points: -2.9 points\n \n pts rule nam[...] X-Spam-Flag: NO X-Spam-Score: -102.518 X-Spam-Level: X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAiMgysCRy7i for ; Tue, 21 Dec 2010 04:17:39 -0800 (PST) Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 647383A6869 for ; Tue, 21 Dec 2010 04:17:37 -0800 (PST) Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1PV1Bh-0001oQ-JS; Tue, 21 Dec 2010 13:19:31 +0100 Received: from dog.ripe.net ([193.0.1.217] helo=guest184.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from ) id 1PV1Bh-0005pG-FH; Tue, 21 Dec 2010 13:19:29 +0100 Message-ID: <4D109B51.8000000@bwijnen.net> Date: Tue, 21 Dec 2010 13:19:29 +0100 From: "Bert (IETF) Wijnen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Netconf Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd41e19db66ba82d397d1157ac0fc95b7e3 X-RIPE-Spam-Level: -- X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd41e19db66ba82d397d1157ac0fc95b7e3 Subject: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2010 12:17:40 -0000 WG participants, This is a 2,5 week (holiday season) WG Last Call for this draft. The idea is to only check if the agreed upon edits have been made properly/correctly and if they do not have any unforeseen side effects/impacts. The WG LC ends on Jan 7th, 2011. Please carefully check/review and send us any comments you may have BEFORE Jan 7th 2011. Bert and Mehmet (Mehmet is the document shepherd) Background: We have been discussing (on this WG mailing list) a set of changes to the rfc4742bis draft. This to try and get proper/reasonable framing. The WG chairs concluded we do have more or less FULL consensus on the proposed edits. And so we asked Margaret to make those edits to the Internet Draft. She did so and the I-D (revision 05) has been posted. -------- Original Message -------- Subject: [Netconf] I-D Action:draft-ietf-netconf-rfc4742bis-05.txt Date: Mon, 20 Dec 2010 14:00:01 -0800 From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org CC: netconf@ietf.org 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 : Using the NETCONF Configuration Protocol over Secure Shell (SSH) Author(s) : M. Wasserman, T. Goddard Filename : draft-ietf-netconf-rfc4742bis-05.txt Pages : 13 Date : 2010-12-20 This document describes a method for invoking and running the NETCONF protocol within a Secure Shell (SSH) session as an SSH subsystem. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-netconf-rfc4742bis-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. From bertietf@bwijnen.net Tue Dec 21 04:53:38 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17EF03A6873 for ; Tue, 21 Dec 2010 04:53:38 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Improper folded header field made up entirely of whitespace (char 20 hex): X-RIPE-Spam-Report: ...al Points: -2.9 points\n \n pts rule nam[...] X-Spam-Flag: NO X-Spam-Score: -102.522 X-Spam-Level: X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFhy4FR7oWxs for ; Tue, 21 Dec 2010 04:53:37 -0800 (PST) Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 83BBF3A6869 for ; Tue, 21 Dec 2010 04:53:35 -0800 (PST) Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1PV1kU-0002wr-4G; Tue, 21 Dec 2010 13:55:31 +0100 Received: from dog.ripe.net ([193.0.1.217] helo=guest184.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from ) id 1PV1kU-0000EN-0z; Tue, 21 Dec 2010 13:55:26 +0100 Message-ID: <4D10A3BD.2020906@bwijnen.net> Date: Tue, 21 Dec 2010 13:55:25 +0100 From: "Bert (IETF) Wijnen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Netconf References: <4D109B51.8000000@bwijnen.net> In-Reply-To: <4D109B51.8000000@bwijnen.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd42e419019dada2536d25b0c5a7c0a6cd4 X-RIPE-Spam-Level: -- X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd42e419019dada2536d25b0c5a7c0a6cd4 Subject: Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2010 12:53:38 -0000 My review comments: 4.1. Framing protocol The previous version of this document defined the character sequence "]]<]]>" as a message separator, under the assumption that it could ====== I think that < should be a >, so "]]>]]>" not be found in well-formed XML documents. However, this assumption is not correct. It can legally appear in XML attributes, comments, and processing instructions. In order to solve this problem, and at the same time be compatible with existing implementations, this document defines the following framing protocol. The message MUST be followed by the character sequence ]]>]]>. Upon reception of the message, the receiving peer's SSH Transport layer conceptually passes the message to the Messages layer. If the :base:1.1 capability is advertised by both peers, the chunked transfer mechanism (see Section 4.1.1) is used for ======= 4.2? the remainder of the NETCONF session. Otherwise, the old end-of- message based mechanism (see Section 4.1.2) is used. ====== 4.3? The sections are actually 4.2 and 4.3 in the document. So that needs to be synced up Bert On 12/21/10 1:19 PM, Bert (IETF) Wijnen wrote: > > WG participants, > > This is a 2,5 week (holiday season) WG Last Call for this draft. > The idea is to only check if the agreed upon edits have been made > properly/correctly and if they do not have any unforeseen side > effects/impacts. > > The WG LC ends on Jan 7th, 2011. Please carefully check/review and > send us any comments you may have BEFORE Jan 7th 2011. > > Bert and Mehmet > (Mehmet is the document shepherd) > > Background: > > We have been discussing (on this WG mailing list) a set of changes > to the rfc4742bis draft. This to try and get proper/reasonable framing. > > The WG chairs concluded we do have more or less FULL consensus on > the proposed edits. And so we asked Margaret to make those edits > to the Internet Draft. She did so and the I-D (revision 05) has > been posted. > > -------- Original Message -------- > Subject: [Netconf] I-D Action:draft-ietf-netconf-rfc4742bis-05.txt > Date: Mon, 20 Dec 2010 14:00:01 -0800 > From: Internet-Drafts@ietf.org > To: i-d-announce@ietf.org > CC: netconf@ietf.org > > > > 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 : Using the NETCONF Configuration Protocol over Secure Shell (SSH) > Author(s) : M. Wasserman, T. Goddard > Filename : draft-ietf-netconf-rfc4742bis-05.txt > Pages : 13 > Date : 2010-12-20 > > This document describes a method for invoking and running the NETCONF > protocol within a Secure Shell (SSH) session as an SSH subsystem. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-netconf-rfc4742bis-05.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > From bertietf@bwijnen.net Tue Dec 21 04:58:25 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62CF23A6996 for ; Tue, 21 Dec 2010 04:58:25 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Improper folded header field made up entirely of whitespace (char 20 hex): X-RIPE-Spam-Report: ...al Points: -2.9 points\n \n pts rule nam[...] X-Spam-Flag: NO X-Spam-Score: -102.526 X-Spam-Level: X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SFurmzp+UZk3 for ; Tue, 21 Dec 2010 04:58:23 -0800 (PST) Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id A5D1A3A68D2 for ; Tue, 21 Dec 2010 04:58:22 -0800 (PST) Received: from ayeaye.ripe.net ([193.0.23.5]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1PV1p8-0003OS-Oe for netconf@ietf.org; Tue, 21 Dec 2010 14:00:16 +0100 Received: from dog.ripe.net ([193.0.1.217] helo=guest184.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from ) id 1PV1p8-0000cq-Jr for netconf@ietf.org; Tue, 21 Dec 2010 14:00:14 +0100 Message-ID: <4D10A4DE.8090408@bwijnen.net> Date: Tue, 21 Dec 2010 14:00:14 +0100 From: "Bert (IETF) Wijnen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Netconf Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4f2a1a107260f368fc56fc914a816ffee X-RIPE-Spam-Level: -- X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4f2a1a107260f368fc56fc914a816ffee Subject: [Netconf] Fwd: Protocol Action: 'With-defaults capability for NETCONF' to Proposed Standard (draft-ietf-netconf-with-defaults-14.txt) X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2010 12:58:25 -0000 Congratulations to the WG. And special thanks to Andy (and Balazs) for editing of course. Bert -------- Original Message -------- Subject: [Netconf] Protocol Action: 'With-defaults capability for NETCONF' to Proposed Standard (draft-ietf-netconf-with-defaults-14.txt) Date: Mon, 20 Dec 2010 10:09:02 -0800 From: The IESG To: IETF-Announce CC: Internet Architecture Board , netconf mailing list , netconf chair , RFC Editor The IESG has approved the following document: - 'With-defaults capability for NETCONF' (draft-ietf-netconf-with-defaults-14.txt) as a Proposed Standard This document is the product of the Network Configuration Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-netconf-with-defaults/ Technical Summary The NETCONF protocol defines ways to read and edit configuration data from a NETCONF server. In some cases, part of this data may not be set by the NETCONF client, but rather a default value known to the server is used instead. In many situations the NETCONF client has a priori knowledge about default data, so the NETCONF server does not need to save it in a NETCONF configuration datastore or send it to the client in a retrieval operation reply. In other situations the NETCONF client will need this data from the server. Not all server implementations treat this default data the same way. This document defines a capability-based extension to the NETCONF protocol that allows the NETCONF client to identify how defaults are processed by the server, and also defines new mechanisms for client control of server processing of default data. Working Group Summary The working group went over several versions of the document. The comments and reviews helped improve the document a lot and brought us to consensus on the 9th revision of the document. Document Quality There are preliminary implementations of this protocol and updates to comply with this spec are in plan. Others are planning to implement this spec too. Personnel Bert Wijnen is the Document Shepherd. Dan Romascanu is the Responsible Area Director. RFC Editor Note sec 1, para 1, add missing word OLD: A priori knowledge can be obtained, e.g., a document formally describing the data models supported by the NETCONF server. NEW: A priori knowledge can be obtained, e.g., from a document formally describing the data models supported by the NETCONF server. --------------------------------------------- sec 1.2 point 1: change word OLD: The actual nodes omitted depends on the defaults handling behavior used by the server. NEW: The actual nodes omitted depend on the defaults handling behavior used by the server. --------------------------------------------- sec 2, para 1, new last sentence OLD: Instead of forcing a single implementation strategy, this document allows a server to advertise a particular style of defaults handling, and the client can adjust accordingly. NEW: Instead of forcing a single implementation strategy, this document allows a server to advertise a particular style of defaults handling, and the client can adjust accordingly. Client implementations are expected to be powerful enough to support all three of the server basic defaults handling modes. --------------------------------------------- sec 8, para 2, sentence 2: change word OLD: The security consideration of [I-D.ietf-netconf-4741bis] apply to this document as well. NEW: The security consideration of [I-D.ietf-netconf-4741bis] applies to this document as well. _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From mbj@tail-f.com Tue Dec 21 05:23:49 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EBCB3A69E9 for ; Tue, 21 Dec 2010 05:23:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IO7RUE9IxUbj for ; Tue, 21 Dec 2010 05:23:48 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 78C633A688F for ; Tue, 21 Dec 2010 05:23:48 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id EC087616001; Tue, 21 Dec 2010 14:25:42 +0100 (CET) Date: Tue, 21 Dec 2010 14:25:42 +0100 (CET) Message-Id: <20101221.142542.247930377.mbj@tail-f.com> To: bertietf@bwijnen.net From: Martin Bjorklund In-Reply-To: <4D109B51.8000000@bwijnen.net> References: <4D109B51.8000000@bwijnen.net> X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2010 13:23:49 -0000 Hi, I have reviewed the changes in -05 and have some comments: In section 4, the last example seems to belong to the new section 4.3, but it should probably be move to section 4.2, since 4.3. talks about the old EOM, but the example shows the new framing protocol. I.e. the text that starts with: To continue the example given above, a NETCONF over SSH session to retrieve a set of configuration information might look like this: ... should be moved. In section 5, you removed some empty lines as suggested by Juergen, but you forgot to modify the chunk-length number, so: OLD: C: C: #141 C: C: C: C: C: ## S: S: #140 S: S: S: S: S: ## NEW: C: C: #140 C: C: C: C: C: ## S: S: #139 S: S: S: S: S: ## /martin From ietfc@btconnect.com Wed Dec 22 07:24:45 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A40153A6A4C for ; Wed, 22 Dec 2010 07:24:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.74 X-Spam-Level: X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0xWuPNRihz3 for ; Wed, 22 Dec 2010 07:24:44 -0800 (PST) Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id 4E14E3A68C2 for ; Wed, 22 Dec 2010 07:24:43 -0800 (PST) Received: from host86-134-205-48.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.48]) by c2beaomr08.btconnect.com with SMTP id BCM26183; Wed, 22 Dec 2010 15:26:40 +0000 (GMT) Message-ID: <00ab01cba1e3$db9f7620$4001a8c0@gateway.2wire.net> From: "t.petch" To: "Juergen Schoenwaelder" , "Martin Bjorklund" References: <20101210.152255.172617871.mbj@tail-f.com><20101210203240.GB975@elstar.local> <20101210.233604.91186971.mbj@tail-f.com> Date: Wed, 22 Dec 2010 15:23:41 +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 X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0301.4D1218AF.00B1, actions=tag X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4D1218B0.0076,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Cc: netconf@ietf.org Subject: Re: [Netconf] list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2010 15:24:45 -0000 ----- Original Message ----- From: "Martin Bjorklund" To: Cc: Sent: Friday, December 10, 2010 11:36 PM Subject: Re: [Netconf] list of 4742bis edit > Juergen Schoenwaelder wrote: > > On Fri, Dec 10, 2010 at 03:22:55PM +0100, Martin Bjorklund wrote: > > > > > C: > > > C: > > > C: ## > > > > [...] > > > > > S: > > > S: > > > S: ## > > > > [...] > > > > > C: > > > C: > > > C: ## > > > > [...] > > > > > S: > > > S: > > > S: ## > > > > My understanding is that these empty lines are not necessarily needed. > > If this is correct, then these examples might lead people to believe > > these empty lines are needed and I would prefer that these empty lines > > are removed. > > Sure, that's an option. If so, we must also decrement each chunk > size by 1. If that makes the examples more clear, that's fine with me. Well the empty lines were removed but the counts were not decremented so I think the result unclear:-( Second, the ABNF for the chunking says LF for the separating character so I think the reference later to 'newline' confusing - replace 'newline' by 'Line Feed' to match the ABNF. (Some would regard newline as CR LF not just LF) Third, more subtle, "Note that there is no newline character after the 'rpc' end tag" well there is a Line Feed there just as there is after message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> The difference is that in these last three cases the Line Feed is counted as part of the chunk-data whereas in the first case it is counted as part of the end-of-chunks. This needs stating. Clearest would be a visible Line Feed character plus an explanation - anything not used in the I-D would do - or has that approach been rejected? And yes, I comment as quickly as I am able to, but that is not as quickly as yourselves:-( Tom Petch > /martin > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf From mbj@tail-f.com Wed Dec 22 07:45:38 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A8653A6B0E for ; Wed, 22 Dec 2010 07:45:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXPweg2c+qLl for ; Wed, 22 Dec 2010 07:45:37 -0800 (PST) Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id C29583A69EC for ; Wed, 22 Dec 2010 07:45:37 -0800 (PST) Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 10474616001 for ; Wed, 22 Dec 2010 16:47:35 +0100 (CET) Date: Wed, 22 Dec 2010 16:47:34 +0100 (CET) Message-Id: <20101222.164734.72163277.mbj@tail-f.com> To: netconf@ietf.org From: Martin Bjorklund X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Netconf] comments on draft-ietf-netconf-system-notifications-02.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2010 15:45:38 -0000 Hi, Here are my comments on this draft. Most are pretty minor, except maybe for the first one, which is a result of the renaming of the draft and module since -01. General The title of this draft is pretty generic: NETCONF Notification Events and it is too similar to RFC 5277: NETCONF Event Notifications Maybe the old "netconf system notifications" is better, but with an explanation that it refers to the netconf system. grouping common-session-parms Why is user-name optional? It is not optional in netconf monitoring. I suggest it is made mandatory. For consistency with netconf monitoring I suggest: s/user-name/username/ s/remote-host/source-host/ grouping changed-by-parms Could the 'server-or-user' choice be mandatory? I.e. the events that use this grouping will always indicate which user and session-id was used, but if it is an unknown session (e.g. changed over snmp), session-id is zero. notification netconf-config-change This is described in the text as: Generated when the NETCONF server detects that the or configuration datastore has changed. This text should also be used in the 'description' stmt in the YANG module. notification netconf-config-change s/target-database/target-datastore/ consistent terminology... notification netconf-confirmed-commit Instead of: uses common-session-parms { refine session-id { mandatory false; } } Could we use: uses common-session-parms { when "../confirm-event != 'timeout'"; } I think this achieves the same effect, but in a more clear way. notification netconf-capability-change I think it should be stated that the modified-capability leaf-list lists the new capability strings. /martin From ietfc@btconnect.com Fri Dec 24 06:29:41 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34AB43A695A for ; Fri, 24 Dec 2010 06:29:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.67 X-Spam-Level: X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.930, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SK1WsvQJZyW4 for ; Fri, 24 Dec 2010 06:29:40 -0800 (PST) Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by core3.amsl.com (Postfix) with ESMTP id D22E03A6452 for ; Fri, 24 Dec 2010 06:29:39 -0800 (PST) Received: from host86-134-205-48.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.48]) by c2bthomr13.btconnect.com with SMTP id BDF13252; Fri, 24 Dec 2010 14:31:41 +0000 (GMT) Message-ID: <01bf01cba36e$80756b60$4001a8c0@gateway.2wire.net> From: "t.petch" To: References: <012901cba354$4ef74780$4001a8c0@gateway.2wire.net> Date: Fri, 24 Dec 2010 14:28:45 +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 X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D14AECC.01A5, actions=tag X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4D14AECD.00B1,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Subject: [Netconf] WGLC was Re: list of 4742bis edits X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2010 14:29:41 -0000 Ah - helps to add the mailing list to the addressees, so for completeness (and apologies to everyone else) > ----- Original Message ----- > From: "t.petch" > Sent: Thursday, December 23, 2010 12:25 PM > > ----- Original Message ----- > > From: "Bert Wijnen (IETF)" > > Sent: Wednesday, December 22, 2010 11:57 PM > > Subject: Re: [Netconf] list of 4742bis edits > > > > > Tom, we now have a WGLC out for the updated > > > draft-ietf-netconf-rfc4742bis-05.txt document. It runs till > > > 7 Jan 2011. See my mail to the list on 22 dec 2010. > > > > > > If this discussion below means any change, then > > > can you please cast your comments in terms of comments > > > on that WGLC, that would be good. > > My first e-mail was written after -05 came out but before I had seen your WGLC so sloppily I replied to Martin's message. Ignore that message and see below > > > Bert > > > > > > ----- Original Message ----- > > > From: "t.petch" > > > To: "Juergen Schoenwaelder" ; "Martin > > > Bjorklund" > > > Cc: > > > Sent: Wednesday, December 22, 2010 3:23 PM > > > > > > > > > ----- Original Message ----- > > > From: "Martin Bjorklund" > > > To: > > > Cc: > > > Sent: Friday, December 10, 2010 11:36 PM > > > Subject: Re: [Netconf] list of 4742bis edit > > > > Juergen Schoenwaelder wrote: > > > > > On Fri, Dec 10, 2010 at 03:22:55PM +0100, Martin Bjorklund wrote: > > > > > > > > > Sure, that's an option. If so, we must also decrement each chunk > > > > size by 1. If that makes the examples more clear, that's fine with me. > > > a) As Martin has also noticed, the empty lines were removed but the counts were not decremented and need to be so. b) The ABNF for the chunking says LF for the separating character so I think that Line Feed is the term to use and the use of 'newline' confusing - replace 'newline' by 'Line Feed' (in whatever text we end up with). c) "Note that there is no newline character after the 'rpc' end tag" Well there is a Line Feed there just as there is after each of message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> The difference is that in these last three cases the Line Feed is counted as part of the chunk-data whereas in the first case it is counted as part of the end-of-chunks. This needs clarifying. Clearest would be a visible Line Feed character - anything not used in the I-D would do. With or without a visible Line Feed, I think that the sentence quoted above should be replaced by NEW "In the second and third chunks quoted above, each line is terminated by a (invisible:-) Line Feed. For all the XML lines except the last, this example treats the Line Feed as part of the chunk-data and so contributing to the chunk-size. For the last XML line, the 'rpc' end tag, the Line Feed is treated as part of the end-of-chunks." Tom Petch > > > > > > /martin > From mehmet.ersue@nsn.com Mon Dec 27 04:21:42 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BF0C3A6846 for ; Mon, 27 Dec 2010 04:21:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.46 X-Spam-Level: X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id acVAQW6tqDxv for ; Mon, 27 Dec 2010 04:21:41 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 519A33A672F for ; Mon, 27 Dec 2010 04:21:40 -0800 (PST) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id oBRCNX2b001730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Dec 2010 13:23:34 +0100 Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id oBRCNOIl016421; Mon, 27 Dec 2010 13:23:32 +0100 Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Dec 2010 13:23:23 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 27 Dec 2010 13:23:20 +0100 Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6401670713@DEMUEXC006.nsn-intra.net> In-Reply-To: <20101221.142542.247930377.mbj@tail-f.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt Thread-Index: AcuhEpgA5QOLK3OmSxe2Yv+iBzQLFQErTwWA References: <4D109B51.8000000@bwijnen.net> <20101221.142542.247930377.mbj@tail-f.com> From: "Ersue, Mehmet (NSN - DE/Munich)" To: "ext Martin Bjorklund" , X-OriginalArrivalTime: 27 Dec 2010 12:23:23.0661 (UTC) FILETIME=[DAFE8BD0:01CBA5C0] Cc: netconf@ietf.org Subject: Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2010 12:21:42 -0000 Why can't we keep the old example from -04 as it is in section 4.3 and change in 4.3? OLD: To continue the example given above, a NETCONF over SSH session to retrieve a set of configuration information might look like this: NEW: To continue the example from Section 3.1, a NETCONF over SSH session using the EOM=20 framing mechanism to retrieve a set of configuration information might look like this: Cheers, Mehmet > -----Original Message----- > From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On > Behalf Of ext Martin Bjorklund > Sent: Tuesday, December 21, 2010 2:26 PM > To: bertietf@bwijnen.net > Cc: netconf@ietf.org > Subject: Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis- > 05.txt >=20 > Hi, >=20 > I have reviewed the changes in -05 and have some comments: >=20 > In section 4, the last example seems to belong to the new section 4.3, > but it should probably be move to section 4.2, since 4.3. talks about > the old EOM, but the example shows the new framing protocol. I.e. the > text that starts with: >=20 > To continue the example given above, a NETCONF over SSH session to > retrieve a set of configuration information might look like this: > ... >=20 > should be moved. >=20 >=20 > In section 5, you removed some empty lines as suggested by Juergen, > but you forgot to modify the chunk-length number, so: >=20 > OLD: >=20 > C: > C: #141 > C: > C: C: xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > C: > C: > C: ## >=20 >=20 > S: > S: #140 > S: > S: S: xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > S: > S: > S: ## >=20 > NEW: >=20 > C: > C: #140 > C: > C: C: xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > C: > C: > C: ## >=20 >=20 > S: > S: #139 > S: > S: S: xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0"> > S: > S: > S: ## >=20 >=20 >=20 > /martin >=20 >=20 > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf From wjhns1@hardakers.net Tue Dec 28 08:10:35 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0416B3A692E for ; Tue, 28 Dec 2010 08:10:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.12 X-Spam-Level: X-Spam-Status: No, score=-4.12 tagged_above=-999 required=5 tests=[AWL=-0.521, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VCtCZE6gV7ER for ; Tue, 28 Dec 2010 08:10:33 -0800 (PST) Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by core3.amsl.com (Postfix) with ESMTP id C7BBB3A6891 for ; Tue, 28 Dec 2010 08:10:33 -0800 (PST) Received: from localhost (75-101-64-22.dsl.dynamic.omsoft.com [75.101.64.22]) by mail.hardakers.net (Postfix) with ESMTPSA id 49C0D2248C; Tue, 28 Dec 2010 08:12:11 -0800 (PST) From: Wes Hardaker To: "Bert \(IETF\) Wijnen" Organization: Sparta References: <4D109B51.8000000@bwijnen.net> Date: Tue, 28 Dec 2010 08:12:10 -0800 In-Reply-To: <4D109B51.8000000@bwijnen.net> (Bert Wijnen's message of "Tue, 21 Dec 2010 13:19:29 +0100") Message-ID: User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Cc: Netconf Subject: Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 16:10:35 -0000 >>>>> On Tue, 21 Dec 2010 13:19:29 +0100, "Bert (IETF) Wijnen" said: B(W> This is a 2,5 week (holiday season) WG Last Call for this draft. B(W> The idea is to only check if the agreed upon edits have been made B(W> properly/correctly and if they do not have any unforeseen side B(W> effects/impacts. Comments (take and leave what you want): * I noted that the section reference was incorrect as well. Specifically in 4.1: s/4.1.1/4.2/ and s/4.1.2/4.3/ * I'm not sure that deciding on the capability based on "base:1.1" is a good idea. Not because it doesn't work, but because it's not future-proof. Wouldn't it be better to say one of: + ":base:1.1 or later", which has the downside of version comparisons. + "any other base capability besides the ':base:1.0' one", which is probably easier to implement. It would still leave problems in the future if we ever needed to change the framing again, but that's not gonna happen, right? right? right? * I didn't follow the whole line-feed discussion, but it appears that the starting examples don't have a preceding line-feed to match the ABNF that says the chunk must *start* with a LF. Thus I'd expect the example to be: ----- starting ----- #4 #4 + Use the C: markings like everywhere else does, possibly in combination with the above suggestion. (I think this is the easiest and cleanest) + ignore me and assume people get the first chunking implemented correctly without help. (later chunkings are more obvious as the linefeed will always follow a RPC message; it's the first that I think is mildly confusing. * Similarily, I don't understand this sentence: Note that there is no newline character after the 'rpc' end tag, so there is no blank line generated before the '##' line. Who's doing the "generation" in that sentence? I just read it for the 4th time while pasting it and got it. I'd suggest the following is more clear (because there *is* a newline in it and it's sort of "generated" by the rules): Note that there is no newline character after the 'rpc' end tag in this message, so there is no otherwise-empty blank line before the '##' line. The LF required by the start of the end-of-chunks block immediately follows the last '>' character in the message. * for the backwards-compatibility issue, the following paragraph has a similar problem: This mechanism exists for backwards compatibility with implementations of previous versions of this document. It is only used when the remote peer does not advertise the :base:1.1 capability. IE, if :base:1.1 goes away in the future, then this document needs to be rewritten even if no other changes are required. Only if advertising the ":base:1.0" would be a better way of checking: NEW: This mechanism exists for backwards compatibility with implementations of previous versions of this document. It is only used when the remote peer advertises only the :base:1.0 capability. * In section 4.3 the examples were changed away from the "]]>]]>" version to the chunked version, but 4.3 is actually discussing the old version! Thus, the chunking needs to be reverted. Additionally, I wouldn't use the phrase "to continue the example given above" since the above is using the chunked framework. How about " A NETCONF over SSH session, using the backwards-compatible end-of-message framing, to retrieve a set of configuration information might look like this: * In section 5 (similar continuation problems) OLD: To continue the example used in previous sections, an existing NETCONF subsystem session could be closed as follows: NEW: To continue the example used in section 4.2, an existing NETCONF subsystem session could be closed as follows: * This is very late (IE, too late), but one thought that occurred to me is that maybe the framing should have used direct XML comments to store the framing data to keep it "XMLish". IE: #4 could have been (with *VERY* strict encoding): But, as I said, this is late and it doesn't seem like many people actually cared about the #4 itself being "not XMLish". -- Wes Hardaker Cobham Analytic Solutions From ietfc@btconnect.com Tue Dec 28 09:05:39 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AD9E3A6890 for ; Tue, 28 Dec 2010 09:05:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.823 X-Spam-Level: X-Spam-Status: No, score=-2.823 tagged_above=-999 required=5 tests=[AWL=0.776, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyNDagIxJT0s for ; Tue, 28 Dec 2010 09:05:38 -0800 (PST) Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id 344703A681B for ; Tue, 28 Dec 2010 09:05:37 -0800 (PST) Received: from host86-134-205-48.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.48]) by c2beaomr08.btconnect.com with SMTP id BDQ29364; Tue, 28 Dec 2010 17:07:42 +0000 (GMT) Message-ID: <011a01cba6a8$f15b4c40$4001a8c0@gateway.2wire.net> From: "t.petch" To: References: <00b101cb609e$fc77ccc0$4001a8c0@gateway.2wire.net> Date: Tue, 28 Dec 2010 17:04:26 +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 X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D1A195D.013B, actions=tag X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4D1A195E.0066,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Cc: ws6zed@gmail.com Subject: Re: [Netconf] e-mail getting bounced X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 17:05:39 -0000 Wes My e-mail to you gets bounced and I believe the MSA is then refusing to send it to anyone so I have taken you off the addressees. The error is "The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was 'wjhns1@hardakers.net'. Subject 'Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt', Account: 'ietfc', Server: 'smtp.btconnect.com', Protocol: SMTP, Server Response: '550 Recipient domain must exist ', Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79" I am afraid that the UK incumbent ISP still doesn't like you. Tom Petch ----- Original Message ----- From: "Wes Hardaker AKA WS6Z" To: "t.petch" Cc: Sent: Saturday, October 02, 2010 2:14 PM Subject: Re: e-mail getting bounced > >>>>> On Thu, 30 Sep 2010 14:56:58 +0200, "t.petch" said: > > tp> I am not getting a DSN or MDN; rather, at send time, I am getting a message > tp> back, presumable from a border MTA, perhaps as a result of a black list on > tp> btconnect.com (bt does host a number of spammers). > > I don't use btconnect.com, though if you're using them for filtering I > suppose that could be a problem. > > tp> And my e-mail client then refuses to send the e-mail to any of the > tp> other addressees, so I had to remove wjhns1@hardakers.net whereupon > tp> it worked. > > I'm sure that address is used as a forged email address a lot, but not > from any of my sites. I'd hope that no one is filtering solely on From > addresses since those are so easily faked. > > -- > Wes Hardaker > My Pictures: http://capturedonearth.com/ > My Thoughts: http://pontifications.hardakers.net/ From ietfc@btconnect.com Tue Dec 28 09:05:41 2010 Return-Path: X-Original-To: netconf@core3.amsl.com Delivered-To: netconf@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8DFA3A68A2 for ; Tue, 28 Dec 2010 09:05:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.017 X-Spam-Level: X-Spam-Status: No, score=-3.017 tagged_above=-999 required=5 tests=[AWL=0.582, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JP0qcRemqav for ; Tue, 28 Dec 2010 09:05:40 -0800 (PST) Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id 15C413A681B for ; Tue, 28 Dec 2010 09:05:39 -0800 (PST) Received: from host86-134-205-48.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.48]) by c2beaomr08.btconnect.com with SMTP id BDQ29367; Tue, 28 Dec 2010 17:07:42 +0000 (GMT) Message-ID: <011b01cba6a8$f18da6e0$4001a8c0@gateway.2wire.net> From: "t.petch" To: "Bert \(IETF\) Wijnen" References: <4D109B51.8000000@bwijnen.net> Date: Tue, 28 Dec 2010 17:04:38 +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 X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D1A195D.013B, actions=tag X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4D1A195E.01AB,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Cc: Netconf Subject: Re: [Netconf] WG Last Call for draft-ietf-netconf-rfc4742bis-05.txt X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 17:05:42 -0000 Wes I largely agree, but do object to 'newline' since the ABNF uses exclusively LF so OLD newline NEW Line Feed And I think that the only way to make chunking clear is to make the Line Feed visible so I have edited 4.2 to look like (and will keep this whatever the WG decides) " As an example, the message: could be encoded as, using } as a visible representation of the Line Feed character: } #4} } #79} xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">} } } ##} Note that } represents Line Feed, as per the ABNF above, and not Carriage Return Line Feed, even though it is the latter sequence that is used to terminate lines in the generation of this memo. The XML comments are included to make the arithmetic clear and neither they, nor the intervening spaces, appear on the wire. Tom Petch ----- Original Message ----- From: "Wes Hardaker" To: "Bert (IETF) Wijnen" Cc: "Netconf" Sent: Tuesday, December 28, 2010 5:12 PM > >>>>> On Tue, 21 Dec 2010 13:19:29 +0100, "Bert (IETF) Wijnen" said: > > B(W> This is a 2,5 week (holiday season) WG Last Call for this draft. > B(W> The idea is to only check if the agreed upon edits have been made > B(W> properly/correctly and if they do not have any unforeseen side > B(W> effects/impacts. > > Comments (take and leave what you want): > > * I noted that the section reference was incorrect as well. Specifically > in 4.1: s/4.1.1/4.2/ and s/4.1.2/4.3/ > > * I'm not sure that deciding on the capability based on "base:1.1" is a > good idea. Not because it doesn't work, but because it's not > future-proof. Wouldn't it be better to say one of: > > + ":base:1.1 or later", which has the downside of version > comparisons. > > + "any other base capability besides the ':base:1.0' one", which is > probably easier to implement. It would still leave problems in > the future if we ever needed to change the framing again, but > that's not gonna happen, right? right? right? > > * I didn't follow the whole line-feed discussion, but it appears that > the starting examples don't have a preceding line-feed to match the > ABNF that says the chunk must *start* with a LF. Thus I'd expect the > example to be: > > ----- starting ----- > > #4 > #18 > ... > > > Right now the #4 starts with the standard "single line break spacing > above it for document readability purposes". I think the only ways > around this would be to: > > + put in start of message markers (like the "----- starting -----" > line above) > > + put 2 line feeds before the initial start > > + prepend the example hello message suffix > > ... (actually insert these) > > #4 > > + Use the C: markings like everywhere else does, possibly in > combination with the above suggestion. > > (I think this is the easiest and cleanest) > > + ignore me and assume people get the first chunking implemented > correctly without help. (later chunkings are more obvious as the > linefeed will always follow a RPC message; it's the first that I > think is mildly confusing. > > * Similarily, I don't understand this sentence: > > Note that there is no newline character after the 'rpc' end tag, > so there is no blank line generated before the '##' line. > > Who's doing the "generation" in that sentence? I just read it for the > 4th time while pasting it and got it. I'd suggest the following is > more clear (because there *is* a newline in it and it's sort of > "generated" by the rules): > > Note that there is no newline character after the 'rpc' end tag > in this message, so there is no otherwise-empty blank line before > the '##' line. The LF required by the start of the end-of-chunks > block immediately follows the last '>' character in the message. > > * for the backwards-compatibility issue, the following paragraph has a > similar problem: > > This mechanism exists for backwards compatibility with > implementations of previous versions of this document. It is > only used when the remote peer does not advertise the :base:1.1 > capability. > > IE, if :base:1.1 goes away in the future, then this document needs to > be rewritten even if no other changes are required. Only if > advertising the ":base:1.0" would be a better way of checking: > > NEW: > This mechanism exists for backwards compatibility with > implementations of previous versions of this document. It is > only used when the remote peer advertises only the :base:1.0 > capability. > > * In section 4.3 the examples were changed away from the "]]>]]>" > version to the chunked version, but 4.3 is actually discussing the old > version! Thus, the chunking needs to be reverted. > > Additionally, I wouldn't use the phrase "to continue the example given > above" since the above is using the chunked framework. How about " > > A NETCONF over SSH session, using the backwards-compatible > end-of-message framing, to retrieve a set of configuration > information might look like this: > > * In section 5 (similar continuation problems) > > OLD: > > To continue the example used in previous sections, an existing > NETCONF subsystem session could be closed as follows: > > NEW: > > To continue the example used in section 4.2, an existing > NETCONF subsystem session could be closed as follows: > > > * This is very late (IE, too late), but one thought that occurred to me > is that maybe the framing should have used direct XML comments to > store the framing data to keep it "XMLish". IE: > > #4 > > could have been (with *VERY* strict encoding): > > > > But, as I said, this is late and it doesn't seem like many people > actually cared about the #4 itself being "not XMLish". > > -- > Wes Hardaker > Cobham Analytic Solutions > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf