From owner-netconf@ops.ietf.org Thu Nov 01 15:40:39 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InfuB-0006Je-Pz for netconf-archive@lists.ietf.org; Thu, 01 Nov 2007 15:40:39 -0400 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Infu0-0007VZ-Kb for netconf-archive@lists.ietf.org; Thu, 01 Nov 2007 15:40:34 -0400 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Infjg-000Hv8-Tp for netconf-data@psg.com; Thu, 01 Nov 2007 19:29:48 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [198.152.71.100] (helo=de307622-de-outbound.net.avaya.com) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1InfjP-000HtI-0w for netconf@ops.ietf.org; Thu, 01 Nov 2007 19:29:43 +0000 X-IronPort-AV: E=Sophos;i="4.21,359,1188792000"; d="scan'208";a="70346737" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Nov 2007 15:29:28 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: NETCONF rechartering goes to external review Date: Thu, 1 Nov 2007 20:28:42 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NETCONF rechartering goes to external review Thread-Index: AcgcvWmKnqb33p0rRdKR7EMW5MF3SA== From: "Romascanu, Dan (Dan)" To: "Netconf WG" , Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f The IESG discussed in the telechat today the proposal for the re-chartering of the NETCONF WG and sent it to IETF review. You should see the announcement in the next few days. The discussion for the approval of the new charter is scheduled for the IESG telechat on 11/15. Thanks for the effort until now and please be ready to participate and support the upcoming discussions.=20 Dan =20 -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Nov 07 17:19:26 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IptF8-0005ro-AL for netconf-archive@lists.ietf.org; Wed, 07 Nov 2007 17:19:26 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IptF4-0004yU-W9 for netconf-archive@lists.ietf.org; Wed, 07 Nov 2007 17:19:26 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Ipt8X-0002W8-IT for netconf-data@psg.com; Wed, 07 Nov 2007 22:12:37 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [198.152.13.100] (helo=co300216-co-outbound.avaya.com) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Ipt7y-0002Tr-3s for netconf@ops.ietf.org; Wed, 07 Nov 2007 22:12:21 +0000 X-IronPort-AV: E=Sophos;i="4.21,386,1188792000"; d="scan'208";a="81693178" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 07 Nov 2007 17:11:55 -0500 X-IronPort-AV: E=Sophos;i="4.21,386,1188792000"; d="scan'208";a="122966047" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 07 Nov 2007 17:11:25 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: FW: [YANG] YANG draft Date: Wed, 7 Nov 2007 23:11:23 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [YANG] YANG draft Thread-Index: AcghgWTiLe/FvXcgTCG62Q1CX9RSkAACXLow From: "Romascanu, Dan (Dan)" To: "Netconf WG" , , Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f =20 I apologize for cross-posting.=20 Dan =20 -----Original Message----- From: Martin Bjorklund [mailto:mbj@tail-f.com]=20 Sent: Wednesday, November 07, 2007 11:05 PM To: yang@ietf.org Subject: [YANG] YANG draft A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : YANG - A data modeling language for NETCONF Author(s) : M. Bjorklund Filename : draft-bjorklund-netconf-yang-00.txt Pages : 147 Date : 2007-11-07 YANG is a data modeling language used to model configuration and state data manipulated by the NETCONF protocol, NETCONF remote procedure calls, and NETCONF notifications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-00.txt /martin -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Nov 08 04:56:46 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iq47y-0005ug-QB for netconf-archive@lists.ietf.org; Thu, 08 Nov 2007 04:56:46 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iq47u-0007ek-JF for netconf-archive@lists.ietf.org; Thu, 08 Nov 2007 04:56:46 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iq40G-000Kks-Rv for netconf-data@psg.com; Thu, 08 Nov 2007 09:48:48 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [198.152.13.100] (helo=co300216-co-outbound.avaya.com) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iq405-000KkD-Md for netconf@ops.ietf.org; Thu, 08 Nov 2007 09:48:43 +0000 X-IronPort-AV: E=Sophos;i="4.21,388,1188792000"; d="scan'208";a="81803331" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 08 Nov 2007 04:48:31 -0500 X-IronPort-AV: E=Sophos;i="4.21,388,1188792000"; d="scan'208";a="123061300" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 08 Nov 2007 04:47:49 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Call for Candidates - NETCONF WG chairs Date: Thu, 8 Nov 2007 10:47:41 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for Candidates - NETCONF WG chairs Thread-Index: Acgh7GeEK+PXzx1HSYCbZXmfNI4T5A== From: "Romascanu, Dan (Dan)" To: "Netconf WG" Cc: , , , "Ron Bonica" Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -3.0 (---) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 A new charter for the NETCONF Working Group is right now in review. We expect it to be approved before the Vancouver meeting.=20 As you may know Andy Bierman and Simon Linen who chaired the working group from its start express the desire to step down from their positions of co-chairs by the time the Working Group engages in the new phase of NETCONF.=20 The ADs have decided to write down a brief profile for the WG chair(s) and issue an open call for candidates.=20 We would like you to consider this profile and either nominate yourself or other people that you think that would fit well in this role by sending mail to the OPS ADs. (dromasca@avaya.com and rbonica@juniper.net) We do not intend to disclose the names of the nominees in public, but we will probably solicit for feedback with various other people. If you have a problem with your name being mentioned in this context, pls let us know. Note that this profile is written for a somewhat ideal candidate. We fully realize that such people are probably non-existent, so don't hesitate to nominate somebody who in your opinion would fit this role quite well but doesn't fit this profile 100%. And the intend is to select two co-chairs that can complement each other and work together. As for the profile: =20 - Good management and process skills, including but not limited to choosing and supervising editors, commitment and follow-through on the charter, active management of the working group discussions, and handling IETF process steps in prompt fashion. - Good basic knowledge of the NETCONF protocols - Understanding of the requirements/needs/applications of management protocols. - Operational background/experience is very desirable. - Enough available time. For example, preferable not more than one other working chair role in IETF. - There is no requirement that the candidate has been an IETF working group chair before, but it helps if there is some evidence that the candidate can fulfill such a role (e.g.. other management role in other places than IETF etc.) We would like to receive your comments & nominations by November 16, 2007 and we plan to make a decision as soon as possible thereafter. It will be helpful if you indicate in your nomination mail how you or the nominated candidate fits this profile as best as possible. =20 And last but not least, we would like to thank Andy and Simon for leading and guiding the work to develop NETCONF. Their contribution was tremendous and we hope that they will continue to contribute to the NETCONF WG and other related activities in the area.=20 Ron and Dan -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Nov 08 13:32:57 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqCBV-0007QG-Ce for netconf-archive@lists.ietf.org; Thu, 08 Nov 2007 13:32:57 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqCBS-0007GT-96 for netconf-archive@lists.ietf.org; Thu, 08 Nov 2007 13:32:57 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IqC0T-0003Za-72 for netconf-data@psg.com; Thu, 08 Nov 2007 18:21:33 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-202.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO,USER_IN_WHITELIST autolearn=no version=3.2.3 Received: from [156.154.16.138] (helo=ns1.neustar.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iq8ti-000GVE-GV for netconf@ops.ietf.org; Thu, 08 Nov 2007 15:02:46 +0000 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id 98DF126E4D; Thu, 8 Nov 2007 15:02:21 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Iq8th-0006Q2-HE; Thu, 08 Nov 2007 10:02:21 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: netconf@ops.ietf.org From: The IESG Subject: WG Review: Recharter of Network Configuration (netconf) Reply-To: iesg@ietf.org Message-Id: Date: Thu, 08 Nov 2007 10:02:21 -0500 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0 A modified charter has been submitted for the Network Configuration (netconf) working group in the Operations and Management Area of the IETF. The IESG has not made any determination as yet. The modified charter is provided below for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by November 15, 2007. Network Configuration (netconf) ================================ Current Status: Active Working Group Chair(s): TBD Operations and Management Area Director(s): Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Technical Advisor(s): Wesley Hardaker Mailing Lists: General Discussion: netconf@ops.ietf.org To Subscribe: netconf-request@ops.ietf.org In Body: in msg body: subscribe Archive: https://ops.ietf.org/lists/netconf Description of Working Group: Wes Hardaker is Technical Advisor for Security Matters Configuration of networks of devices has become a critical requirement for operators in today's highly interoperable networks. Operators from large to small have developed their own mechanisms or used vendor specific mechanisms to transfer configuration data to and from a device, and for examining device state information which may impact the configuration. Each of these mechanisms may be different in various aspects, such as session establishment, user authentication, configuration data exchange, and error responses. The NETCONF Working Group is chartered to produce a protocol suitable for network configuration, with the following characteristics: - Provides retrieval mechanisms which can differentiate between configuration data and non-configuration data - Is extensible enough that vendors will provide access to all configuration data on the device using a single protocol - Has a programmatic interface (avoids screen scraping and formatting-related changes between releases) - Uses a textual data representation, that can be easily manipulated using non-specialized text manipulation tools. - Supports integration with existing user authentication methods - Supports integration with existing configuration database systems - Supports network wide configuration transactions (with features such as locking and rollback capability) - Is as transport-independent as possible - Provides the following support for asynchronous notifications: - Specify the message (capability exchange) details to support notifications. - Specify the application mapping details to support notifications. - Specify the protocol syntax and semantics of a notification message. - Specify or select a notification content information model. - Specify a mechanism for controlling the delivery (turn on/off) of notifications during a session. - Specify a mechanism for selectively receiving a configurable subset of all possible notification types. The NETCONF protocol will use XML for data encoding purposes, because XML is a widely deployed standard which is supported by a large number of applications. XML also supports hierarchical data structures. The NETCONF protocol should be independent of the data definition language and data models used to describe configuration and state data. However, the authorization model used in the protocol is dependent on the data model. Although these issues must be fully addressed to develop standard data models, only a small part of this work will be initially addressed. This group will specify requirements for standard data models in order to fully support the NETCONF protocol, such as: - identification of principals, such as user names or distinguished names - mechanism to distinguish configuration from non-configuration data - XML namespace conventions - XML usage guidelines It should be possible to transport the NETCONF protocol using several different protocols. The group will select at least one suitable transport mechanism, and define a mapping for the selected protocol(s). The initial work (has completed) and was restricted to the following items: - NETCONF Protocol Specification, which defines the operational model, protocol operations, transaction model, data model requirements, security requirements, and transport layer requirements. - NETCONF over SSH Specification: Implementation Mandatory; NETCONF over BEEP Specification: Implementation Optional; NETCONF over SOAP Specification: Implementation Optional; These documents define how the NETCONF protocol is used with each transport protocol selected by the working group, and how it meets the security and transport layer requirements of the NETCONF Protocol Specification. Additional Notification work (as described above) will now be addressed since the initial work has been completed. An individual submission Internet Draft has been proposed to the WG as the starting point for the Notification work. The WG shall adopt the document identified as 'draft-chisholm-NETCONF-event-01.txt' as the starting point for this work. A second phase of incremental development of NETCONF will include the following items: 1. Fine-grain locking: The base NETCONF protocol only provides a lock for the entire configuration datastore, which is not deemed to meet important operational and security requirements. The NETCONF working group will produce a standards-track RFC specifying a mechanism for fine-grain locking of the NETCONF configuration datastore. (The initial draft will be based on draft-lengyel-ngo-partial-lock-00.txt barring additional contributions from the community.) 2. NETCONF monitoring: It is considered best practice for IETF working groups to include management of their protocols within the scope of the solution they are providing. NETCONF does not provide this capability. The NETCONF working group will produce a standards-track RFC with mechanisms allowing NETCONF itself to be used to monitor some aspects of NETCONF operation. (The initial draft will be based on draft-chisholm-netconf-monitoring-00.txt barring additional contributions from the community.) 3. Schema advertisement: Currently the NETCONF protocol is able to advertise which protocol features are supported on a particular netconf-capable device. However, there is currently no way to discover which XML Schema are supported on the device. The NETCONF working group will produce a standards-track RFC with mechanisms making this discovery possible. This item may be merged with "NETCONF monitoring" into a single document. (The initial draft will be based on draft-scott-netconf-schema-query-00.txt barring additional contributions from the community.) 4. NETCONF over TLS - based on implementation experience there is a need for a standards track document to define NETCONF over TLS as an optional transport for NETCONF (The initial draft will be based on draft-badra-tls-netconf-04.txt barring additional contributions from the community.) The following are currently not considered in scope for re-chartering at this time, but may be candidates for work when there is community consensus to take them on. Individual submissions are being encouraged. o Access Control requirements o General improvements to the base protocol o NETCONF access to SMI-based MIB data o The Bill Fenner problem: Address real or perceived issue that "giving SSH for NETCONF gives full SSH access to the box" Goals and Milestones: Done Working Group formed Done Submit initial NETCONF Protocol draft Done Submit initial NETCONF over (transport-TBD) draft Done Begin Working Group Last Call for the NETCONF Protocol draft Done Begin Working Group Last Call for the NETCONF over (transport-TBD) draft Done Submit final version of the NETCONF Protocol draft to the IESG Done Submit final version of the NETCONF over SOAP draft to the IESG Done Submit final version of the NETCONF over BEEP draft to the IESG Done Submit final version of the NETCONF over SSH draft to the IESG Done Update charter Done Submit first version of NETCONF Notifications document Done Begin WGLC of NETCONF Notifications document Dec 2006 Submit final version of NETCONF Notifications document to IESG for consideration as Proposed Standard December 2007 -00 draft for NETCONF Monitoring December 2007 -00 draft for Schema Advertisement December 2007 -00 draft for Fine Grain Locking December 2007 -00 draft for NETCONF over TLS March 2008 - Early Review of client authentication approach (for NETCONF over TLS) with the security community at IETF 71 August 2008 - WG Last Call on NETCONF Monitoring after IETF72 August 2008 - WG Last Call on Schema Advertisement after IETF72 August 2008 - WG Last Call on Fine Grain Locking after IETF72 August 2008 - WG Last Call on NETCONF over TLS after IETF72 October 2008 Send four documents to the IESG for consideration as proposed standards -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Nov 08 15:57:35 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqERS-0006hf-WD for netconf-archive@lists.ietf.org; Thu, 08 Nov 2007 15:57:35 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqERP-0003HI-GV for netconf-archive@lists.ietf.org; Thu, 08 Nov 2007 15:57:34 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IqEHO-000DfB-AR for netconf-data@psg.com; Thu, 08 Nov 2007 20:47:10 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [69.147.64.89] (helo=smtp116.sbc.mail.sp1.yahoo.com) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IqEHD-000De0-2G for netconf@ops.ietf.org; Thu, 08 Nov 2007 20:47:04 +0000 Received: (qmail 30729 invoked from network); 8 Nov 2007 20:46:58 -0000 Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221 with plain) by smtp116.sbc.mail.sp1.yahoo.com with SMTP; 8 Nov 2007 20:46:57 -0000 X-YMail-OSG: dCqt7AcVM1lbHzKSKhCuNd5xQJuGRgvVxay_OKQGVrcVF_CR Message-ID: <473375C4.1040100@andybierman.com> Date: Thu, 08 Nov 2007 12:47:00 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "Netconf (E-mail)" Subject: END WGLC for draft-ietf-netconf-notification-10.txt Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Hi, The WG Last Call for the NETCONF Notifications draft is now completed. There were a few minor bugfixes and clarifications that were noted on the WG mailing list. A new version (-11) will be created with these minor corrections, and forwarded to the IESG for publication consideration. There will not be another WGLC for the this document. Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Sat Nov 10 01:23:34 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iqjkk-0003wB-3k for netconf-archive@lists.ietf.org; Sat, 10 Nov 2007 01:23:34 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iqjkg-00052d-Oo for netconf-archive@lists.ietf.org; Sat, 10 Nov 2007 01:23:34 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iqjea-000CC8-HJ for netconf-data@psg.com; Sat, 10 Nov 2007 06:17:12 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [206.190.49.175] (helo=web54605.mail.re2.yahoo.com) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IqjeP-000CBX-MD for netconf@ops.ietf.org; Sat, 10 Nov 2007 06:17:07 +0000 Received: (qmail 78747 invoked by uid 60001); 10 Nov 2007 06:17:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=4jEL/LXYFlvOfi3/86iuadqbUosqlKSR/3PM29eFWCMb9RWrE8KJTIswkDwQRafwdME4IzgvCzX+txQ58L7Z5hCzl6shRSLJ0hcxy0rx0T0B58wKvOBbPbPU/sPQMN/SsBrPjQZ2/wsCsQJFy3h8FrIH/FTZQ8Fi8IYFHbuqBbs=; X-YMail-OSG: ZzErLoIVM1kyNofH0a.RtMuufj62BCUFmhr_XXnzMPMgqieKjOBGW40a4jP6aPBa.7BvURAr.io327HqqEpY7Zew4p.5ax3IdHLvN10RCxwhI4cQYVrKyO3kn4HFHw-- Received: from [198.206.187.100] by web54605.mail.re2.yahoo.com via HTTP; Fri, 09 Nov 2007 22:17:00 PST Date: Fri, 9 Nov 2007 22:17:00 -0800 (PST) From: Bharadwaj Kalahasti Subject: Question on To: netconf@ops.ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <855937.77999.qm@web54605.mail.re2.yahoo.com> Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Andy, On page 8 of section 1.2, you have written: " Although it is possible to arbitrarily extend the element, this XSD mechanism is by definition non-standard, and 'off-the-shelf' XSD-based applications will not be able to do anything useful with information encoded in this manner. " The stated flaws in XSD such as lack of conditional presence test for referential integrity could be fixed with changes to the XSD language by creating new elements that are test-only or such. Has there been effort in seeking such a solution from W3C forum so far? Reason being an attempt to create a modeling language that is compliant with both SMIv2 and XSD seems to be an overkill. Please enlighten me if I have missed any concepts here. Thanks, Kalahasti __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Sat Nov 10 02:10:38 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqkUI-0004Z3-N0 for netconf-archive@lists.ietf.org; Sat, 10 Nov 2007 02:10:38 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqkUF-0006Al-90 for netconf-archive@lists.ietf.org; Sat, 10 Nov 2007 02:10:38 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IqkOy-000F95-DU for netconf-data@psg.com; Sat, 10 Nov 2007 07:05:08 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [69.147.64.91] (helo=smtp118.sbc.mail.sp1.yahoo.com) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IqkOn-000F6k-Ep for netconf@ops.ietf.org; Sat, 10 Nov 2007 07:05:02 +0000 Received: (qmail 95414 invoked from network); 10 Nov 2007 07:04:56 -0000 Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221 with plain) by smtp118.sbc.mail.sp1.yahoo.com with SMTP; 10 Nov 2007 07:04:56 -0000 X-YMail-OSG: B2osccQVM1kAByiing3h4CVTT.ilqM2J5GSFcTVm.EachNPW Message-ID: <47355815.7090903@andybierman.com> Date: Fri, 09 Nov 2007 23:04:53 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Bharadwaj Kalahasti CC: netconf@ops.ietf.org Subject: Re: Question on References: <855937.77999.qm@web54605.mail.re2.yahoo.com> In-Reply-To: <855937.77999.qm@web54605.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Bharadwaj Kalahasti wrote: > Andy, > On page 8 of section 1.2, you have written: > " > Although it is possible to arbitrarily extend the element, > this XSD mechanism is by definition non-standard, and 'off-the-shelf' > XSD-based applications will not be able to do anything useful with > information encoded in this manner. > " > The stated flaws in XSD such as lack of conditional presence test for referential > integrity could be fixed with changes to the XSD language by creating new elements > that are test-only or such. Has there been effort in seeking such a solution from > W3C forum so far? Reason being an attempt to create a modeling language that is > compliant with both SMIv2 and XSD seems to be an overkill. I think the 'must' and 'when' clauses in the YANG language address the needs of NETCONF very well in this area. They leverage Xpath in the simplest possible way. I don't know about a NETCONF DML that is backwards-compatible with SMIv2. I think YANG can represent just about any SMIv2 data model. The reverse is obviously never going to be true. > Please enlighten me if I have missed any concepts here. > Thanks, > Kalahasti Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 12 13:14:47 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irdo7-0006ec-Gh for netconf-archive@lists.ietf.org; Mon, 12 Nov 2007 13:14:47 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Irdo5-00078t-0h for netconf-archive@lists.ietf.org; Mon, 12 Nov 2007 13:14:47 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IrdaQ-000EH4-TN for netconf-data@psg.com; Mon, 12 Nov 2007 18:00:38 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-201.9 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO,USER_IN_WHITELIST autolearn=no version=3.2.3 Received: from [156.154.16.138] (helo=ns1.neustar.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IrdZr-000ECl-AQ for netconf@ops.ietf.org; Mon, 12 Nov 2007 18:00:22 +0000 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 743D726E71; Mon, 12 Nov 2007 18:00:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IrdZq-0000cU-Bv; Mon, 12 Nov 2007 13:00:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: netconf@ops.ietf.org From: Internet-Drafts@ietf.org Subject: I-D Action:draft-ietf-netconf-notification-11.txt Message-Id: Date: Mon, 12 Nov 2007 13:00:02 -0500 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Configuration Working Group of the IETF. Title : NETCONF Event Notifications Author(s) : S. Chisholm, H. Trevino Filename : draft-ietf-netconf-notification-11.txt Pages : 46 Date : 2007-11-11 This document defines mechanisms that provide an asynchronous message notification delivery service for the NETCONF protocol. This is an optional capability built on top of the base NETCONF definition. This document defines the capabilities and operations necessary to support this service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-11.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-netconf-notification-11.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-netconf-notification-11.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-11-12125042.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-netconf-notification-11.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-netconf-notification-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-12125042.I-D\@ietf.org> --OtherAccess-- --NextPart-- -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 12 15:29:44 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irfui-0002d8-2t for netconf-archive@lists.ietf.org; Mon, 12 Nov 2007 15:29:44 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Irfud-0003WN-8l for netconf-archive@lists.ietf.org; Mon, 12 Nov 2007 15:29:44 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Irfhf-0003l3-HF for netconf-data@psg.com; Mon, 12 Nov 2007 20:16:15 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [69.147.64.91] (helo=smtp118.sbc.mail.sp1.yahoo.com) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Irfh5-0003el-RJ for netconf@ops.ietf.org; Mon, 12 Nov 2007 20:15:59 +0000 Received: (qmail 40594 invoked from network); 12 Nov 2007 20:15:39 -0000 Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221 with plain) by smtp118.sbc.mail.sp1.yahoo.com with SMTP; 12 Nov 2007 20:15:38 -0000 X-YMail-OSG: X4vApRwVM1kcQk_wN.1l53jrdCqvK0SqY.sWvybUZsKMrJ7v8hwVe26TtFs5agsa0dat8HPvStLeHi3BeMkLFeAd Message-ID: <4738B469.8060208@andybierman.com> Date: Mon, 12 Nov 2007 12:15:37 -0800 From: Andy Bierman User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "Netconf (E-mail)" Subject: quick check of notification-11 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Hi, The new Notifications draft is out: http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-11.txt Could the people who made comments on -10 check that their bugs/issues were properly addressed? Unless there are no objections, the 1 hour NETCONF meeting in Vancouver dedicated to Notification issues will be canceled, because we are done. (!) Many thanks to Sharon and Hector for all their hard work, and to all the people who reviewed and improved it along the way. thanks, Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 12 16:54:17 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrhEX-0004y0-Pf for netconf-archive@lists.ietf.org; Mon, 12 Nov 2007 16:54:17 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrhEV-0007EA-Fx for netconf-archive@lists.ietf.org; Mon, 12 Nov 2007 16:54:17 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Irh4A-000B8Y-Vt for netconf-data@psg.com; Mon, 12 Nov 2007 21:43:34 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_WHITELIST autolearn=no version=3.2.3 Received: from [156.154.24.138] (helo=ns3.neustar.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IrdQr-000D6q-VX for netconf@ops.ietf.org; Mon, 12 Nov 2007 17:50:51 +0000 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id EBF52175BD; Mon, 12 Nov 2007 17:50:44 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IrdQq-0006ti-G6; Mon, 12 Nov 2007 12:50:44 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: schishol@nortel.com Cc: netconf@ops.ietf.org, htrevino@cisco.com From: IETF I-D Submission Tool Subject: New Version Notification for draft-ietf-netconf-notification-11 Message-Id: Date: Mon, 12 Nov 2007 12:50:44 -0500 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a A new version of I-D, draft-ietf-netconf-notification-11.txt has been successfuly submitted by Sharon Chisholm and posted to the IETF repository. Filename: draft-ietf-netconf-notification Revision: 11 Title: NETCONF Event Notifications Creation_date: 2007-11-11 WG ID: netconf Number_of_pages: 46 Abstract: This document defines mechanisms that provide an asynchronous message notification delivery service for the NETCONF protocol. This is an optional capability built on top of the base NETCONF definition. This document defines the capabilities and operations necessary to support this service. The IETF Secretariat. -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 13 03:48:39 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrrRn-0003TS-K1 for netconf-archive@lists.ietf.org; Tue, 13 Nov 2007 03:48:39 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrrRj-00010A-4A for netconf-archive@lists.ietf.org; Tue, 13 Nov 2007 03:48:39 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IrrJj-000H67-Tx for netconf-data@psg.com; Tue, 13 Nov 2007 08:40:19 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [193.180.251.62] (helo=mailgw4.ericsson.se) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IrrJA-000H0j-Br for netconf@ops.ietf.org; Tue, 13 Nov 2007 08:40:03 +0000 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 6F60620448; Tue, 13 Nov 2007 09:39:40 +0100 (CET) X-AuditID: c1b4fb3e-b0835bb0000007e1-4d-473962cc8fe0 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 535332051D; Tue, 13 Nov 2007 09:39:40 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 09:39:40 +0100 Received: from [159.107.198.61] ([159.107.198.61]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 09:39:39 +0100 Message-ID: <473962C9.8020805@ericsson.com> Date: Tue, 13 Nov 2007 09:39:37 +0100 From: Balazs Lengyel User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: Andy Bierman CC: "Netconf (E-mail)" Subject: Re: quick check of notification-11 References: <4738B469.8060208@andybierman.com> In-Reply-To: <4738B469.8060208@andybierman.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 13 Nov 2007 08:39:40.0144 (UTC) FILETIME=[BB096700:01C825D0] X-Brightmail-Tracker: AAAAAA== Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Hello Andy, My comments got in OK. Congratulations to all that we finally succeeded in completing Notifications. regards Balazs Andy Bierman wrote: > Hi, > > The new Notifications draft is out: > http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-11.txt > > Could the people who made comments on -10 check that their bugs/issues > were properly addressed? > > Unless there are no objections, the 1 hour NETCONF meeting in Vancouver > dedicated to Notification issues will be canceled, because we are done. (!) > > Many thanks to Sharon and Hector for all their hard work, > and to all the people who reviewed and improved it along the way. > > > thanks, > Andy > > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with > the word 'unsubscribe' in a single line as the message text body. > archive: -- Balazs Lengyel Ericsson Hungary Ltd. TSP System Manager ECN: 831 7320 Fax: +36 1 4377792 Tel: +36-1-437-7320 email: Balazs.Lengyel@ericsson.com -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 20 13:18:15 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuXfr-0001UZ-LZ for netconf-archive@lists.ietf.org; Tue, 20 Nov 2007 13:18:15 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuXfg-0002pq-FD for netconf-archive@lists.ietf.org; Tue, 20 Nov 2007 13:18:15 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IuXU8-00064A-SP for netconf-data@psg.com; Tue, 20 Nov 2007 18:06:08 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [62.241.162.32] (helo=ranger.systems.pipex.net) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IuXTZ-0005zW-AP for netconf@ops.ietf.org; Tue, 20 Nov 2007 18:05:52 +0000 Received: from pc6 (1Cust138.tnt1.lnd4.gbr.da.uu.net [62.188.130.138]) by ranger.systems.pipex.net (Postfix) with SMTP id 0FA84E0003E6; Tue, 20 Nov 2007 18:05:23 +0000 (GMT) Message-ID: <021d01c82b97$85b13b60$0601a8c0@pc6> Reply-To: "tom.petch" From: "tom.petch" To: "Romascanu, Dan (Dan)" , References: Subject: Re: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC Date: Tue, 20 Nov 2007 17:40:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -104.0 (---------------------------------------------------) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab ----- Original Message ----- From: "Romascanu, Dan (Dan)" To: ; Sent: Monday, October 08, 2007 2:50 PM Subject: FW: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC I think that folks in the OPS Area and NECONF may want to have a look at this proposal and comment if necessary. Dan OK, I'll bite. Why do you think that this might be of interest to NETCONF? It looks quite straightforward (apart from a few typos). I note that there is now -12 which has altered the substance of the XML and in doing so made it invalid (as has already been pointed out). Tom Petch -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org] Sent: Monday, October 08, 2007 3:30 PM To: IETF-Announce Subject: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC The IESG has received a request from an individual submitter to consider the following document: - 'XML Schema for Media Control ' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-11-05. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-levin-mmusic-xml-media-control -11.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag= 9391&rfc_flag=0 -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 20 17:40:43 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iublr-0004pi-58 for netconf-archive@lists.ietf.org; Tue, 20 Nov 2007 17:40:43 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iublm-000652-EM for netconf-archive@lists.ietf.org; Tue, 20 Nov 2007 17:40:43 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iubc0-0003Zw-GI for netconf-data@psg.com; Tue, 20 Nov 2007 22:30:32 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [198.152.71.100] (helo=de307622-de-outbound.net.avaya.com) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IubbQ-0003Tg-Sx for netconf@ops.ietf.org; Tue, 20 Nov 2007 22:30:16 +0000 X-IronPort-AV: E=Sophos;i="4.21,443,1188792000"; d="scan'208";a="74897187" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Nov 2007 17:29:48 -0500 X-IronPort-AV: E=Sophos;i="4.21,443,1188792000"; d="scan'208";a="126749773" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 20 Nov 2007 17:29:08 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC Date: Tue, 20 Nov 2007 23:29:07 +0100 Message-ID: In-Reply-To: <021d01c82b97$85b13b60$0601a8c0@pc6> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC Thread-Index: Acgrn/YUGazXLryOQ6mv41H1IgariAAI+5Pw References: <021d01c82b97$85b13b60$0601a8c0@pc6> From: "Romascanu, Dan (Dan)" To: "tom.petch" , Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Hi Tom, The original call for comments was for draft-11, which was in IETF LC a while ago. Right now draft-12 is in LC, and in case you have any consistent comments you may want to forward them to the ietf list or to the authors.=20 To answer your question besides the fact that cross-area reviews are a good thing, I believe that it's useful for the NETCONF community to see how other protocols are using XML for management operations in different environments.=20 Dan =20 =20 > -----Original Message----- > From: tom.petch [mailto:cfinss@dial.pipex.com]=20 > Sent: Tuesday, November 20, 2007 6:40 PM > To: Romascanu, Dan (Dan); netconf@ops.ietf.org > Subject: Re: Last Call: draft-levin-mmusic-xml-media-control=20 > (XML Schema for Media Control) to Informational RFC=20 >=20 > ----- Original Message ----- > From: "Romascanu, Dan (Dan)" > To: ; > Sent: Monday, October 08, 2007 2:50 PM > Subject: FW: Last Call: draft-levin-mmusic-xml-media-control=20 > (XML Schema for Media Control) to Informational RFC >=20 > I think that folks in the OPS Area and NECONF may want to=20 > have a look at this proposal and comment if necessary. >=20 > Dan >=20 > OK, I'll bite. >=20 > Why do you think that this might be of interest to NETCONF? =20 > It looks quite straightforward (apart from a few typos). I=20 > note that there is now -12 which has altered the substance of=20 > the XML and in doing so made it invalid (as has already been=20 > pointed out). >=20 > Tom Petch >=20 > -----Original Message----- > From: The IESG [mailto:iesg-secretary@ietf.org] > Sent: Monday, October 08, 2007 3:30 PM > To: IETF-Announce > Subject: Last Call: draft-levin-mmusic-xml-media-control (XML=20 > Schema for Media Control) to Informational RFC >=20 > The IESG has received a request from an individual submitter=20 > to consider the following document: >=20 > - 'XML Schema for Media Control ' > as an=20 > Informational RFC >=20 > The IESG plans to make a decision in the next few weeks, and=20 > solicits final comments on this action. Please send=20 > substantive comments to the ietf@ietf.org mailing lists by=20 > 2007-11-05. Exceptionally, comments may be sent to=20 > iesg@ietf.org instead. In either case, please retain the=20 > beginning of the Subject line to allow automated sorting. >=20 > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-levin-mmusic-xml-med ia-control -11.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag= =3D 9391&rfc_flag=3D0 -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 20 18:34:08 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IucbY-00083a-4d for netconf-archive@lists.ietf.org; Tue, 20 Nov 2007 18:34:08 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IucbW-0008HP-8m for netconf-archive@lists.ietf.org; Tue, 20 Nov 2007 18:34:08 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IucR4-0007td-Us for netconf-data@psg.com; Tue, 20 Nov 2007 23:23:18 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [212.201.44.23] (helo=hermes.jacobs-university.de) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IucQZ-0007qs-LA for netconf@ops.ietf.org; Tue, 20 Nov 2007 23:23:03 +0000 Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 242C2865A0; Wed, 21 Nov 2007 00:22:46 +0100 (CET) Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 09782-09; Wed, 21 Nov 2007 00:22:41 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9C079863E7; Wed, 21 Nov 2007 00:22:41 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id A172F3ED49A; Wed, 21 Nov 2007 00:22:40 +0100 (CET) Date: Wed, 21 Nov 2007 00:22:40 +0100 From: Juergen Schoenwaelder To: "Romascanu, Dan (Dan)" Cc: "tom.petch" , netconf@ops.ietf.org Subject: Re: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC Message-ID: <20071120232240.GA4679@elstar.local> Reply-To: j.schoenwaelder@jacobs-university.de Mail-Followup-To: "Romascanu, Dan (Dan)" , "tom.petch" , netconf@ops.ietf.org References: <021d01c82b97$85b13b60$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 On Tue, Nov 20, 2007 at 11:29:07PM +0100, Romascanu, Dan (Dan) wrote: > To answer your question besides the fact that cross-area reviews are a > good thing, I believe that it's useful for the NETCONF community to see > how other protocols are using XML for management operations in different > environments. Not sure this is such a great example (for whatever it is meant to be an example). Let me quote from the abstract: [...] New implementations are discouraged from using the described method described except for backward compatibility purposes. [...] I understand the problem here does not seem to be the XML fragment but the usage of the signaling path - but then I am again not sure what particular NETCONF lesson I am supposed to learn from this. And since you specifically point to this document (and not at other IDs that contain XML fragments where they sometimes also talk about configuration), I am seriously concerned that people looking at examples of the following instance XML document complexity (yes that is all there is!) may draw wrong conclusions. My understanding is that NETCONF is intended to deal with things as complex as whole router configurations, different data stores, locking semantics, commit mechanisms, failure handling mechanisms, validation features, ... and from that perspective, I guess I should not have looked at this document (and clearly not spent time writing this email). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Wed Nov 21 03:10:13 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iukez-0007Pg-Rk for netconf-archive@lists.ietf.org; Wed, 21 Nov 2007 03:10:13 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iukev-0004Dz-1e for netconf-archive@lists.ietf.org; Wed, 21 Nov 2007 03:10:13 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IukTW-000Hhd-31 for netconf-data@psg.com; Wed, 21 Nov 2007 07:58:22 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [133.145.228.44] (helo=mail9.hitachi.co.jp) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IukSw-000Hfm-CQ for netconf@ops.ietf.org; Wed, 21 Nov 2007 07:58:06 +0000 Received: from mlsv13.hitachi.co.jp (unknown [133.144.234.166]) by mail9.hitachi.co.jp (Postfix) with ESMTP id BE0CB37C86 for ; Wed, 21 Nov 2007 16:57:44 +0900 (JST) Received: from MFILTER-S4.hitachi.co.jp by mlsv13.hitachi.co.jp (8.13.1/8.13.1) id lAL7vihs005885; Wed, 21 Nov 2007 16:57:44 +0900 Received: from vshuts3.hitachi.co.jp (unverified) by MFILTER-S4.hitachi.co.jp (Content Technologies SMTPRS 4.3.17) with SMTP id ; Wed, 21 Nov 2007 16:57:43 +0900 Received: from gmml28.itg.hitachi.co.jp ([158.213.165.131]) by vshuts3.hitachi.co.jp with SMTP id M2007112116574315861; Wed, 21 Nov 2007 16:57:43 +0900 Received: from localhost by gmml28.itg.hitachi.co.jp (AIX5.2/8.11.6p2/8.11.0) id lAL7vhe12079350; Wed, 21 Nov 2007 16:57:43 +0900 Date: Wed, 21 Nov 2007 16:57:42 +0900 (JST) Message-Id: <20071121.165742.233425847.hideki.okita.pf@hitachi.com> To: ngo@ietf.org, netconf@ops.ietf.org Subject: draft-okita-netconf-advertisement-00 From: OKITA Hideki In-Reply-To: <20071107.224343.197593066.hideki.okita.pf@hitachi.com> References: <20071011.171321.160611072.hideki.okita.pf@hitachi.com> <47141616.3010705@iijlab.net> <20071107.224343.197593066.hideki.okita.pf@hitachi.com> Organization: Central Research Lab., Hitachi Ltd., Japan X-Mailer: Mew version 5.2 on Emacs 22.0.90 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Dear all, I have submitted a new I-D about the NETCONF Schema advertisement requirement taken into the updated netconf WG charter. > Filename: draft-okita-netconf-advertisement > Title: NETCONF Configuration Interface Advertisement with WSDL and XSD I'd like to make the requirement and available solutions clear by this I-D before we discuss a particular solution. In the schema-query-00 draft, a new NETCONF operation is proposed to take Schema location and access method for the Schema on a NETCONF device. IMO, the requirement for this solution is "NMS developers can know Schema location and access method to the Schema" For this requirement, we can take up following several solutions. - fixed access method and URL (this I-D) - URL described in user's guide - inband dynamic retrieval (schema-query-00) - UDDI (broker model in Web-Service) We should compare the pros/cons of these solutinos. I'd like to discuss this point in Vancouver. Regards, Hideki Okita Central Research Laboratory, Hitachi, Ltd. From: IETF I-D Submission Tool Subject: Manual Post Requested for draft-okita-netconf-advertisement Date: Mon, 12 Nov 2007 09:04:00 -0500 > Filename: draft-okita-netconf-advertisement > Version: 00 > URL: http://www.ietf.org/internet-drafts/draft-okita-netconf-advertisement-00.txt > Title: NETCONF Configuration Interface Advertisement with WSDL and XSD > Creation_date: 2007-11-12 > WG ID: Indvidual Submission > Number_of_pages: 19 > Abstract: > This memo describes a configuration interface advertisement method > for NETCONF device developers. In the proposal, the developers take > a configuration interface definition information of target NETCONF > devices. On their development environment, they generate stab > classes to control the devices. The NETCONF device advertises their > configuration interface by a WSDL file. The WSDL file describes > message type of each NETCONF operation of the device. The WSDL file > contains XML Schema in its types element and describes definition of > the types definition used to configuration data. By this > configuration interface advertisement, Network management System > (NMS) developers can improve their development efficiency of the NMS. > > Author(s): > Hideki Okita, hideki.okita.pf@hitachi.com > Tomoyuki Iijima, tomoyuki.iijima@alaxala.com > Yoshifumi Atarashi, atarashi@alaxala.net From: "Romascanu, Dan (Dan)" Subject: [NGO] FW: Internal WG Review: Recharter of Network Configuration WG(netconf) Date: Sun, 28 Oct 2007 17:35:24 +0100 > 3. Schema advertisement: Currently the NETCONF protocol is able to > advertise which protocol features are supported on a particular > NETCONF-capable device. However, there is currently no way to discover > which XML Schema are supported on the device. The NETCONF working group > will produce a standards-track RFC with mechanisms making this discovery > possible. > > This item may be merged with "Netconf monitoring" into a single > document. > > (The initial draft will be based on > draft-scott-netconf-schema-query-00.txt barring additional contributions > from the community.) -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Nov 22 17:37:16 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvKfc-0001I7-9K for netconf-archive@lists.ietf.org; Thu, 22 Nov 2007 17:37:16 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvKfZ-00021m-Tl for netconf-archive@lists.ietf.org; Thu, 22 Nov 2007 17:37:16 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvKY2-0001QL-O9 for netconf-data@psg.com; Thu, 22 Nov 2007 22:29:26 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [130.59.4.87] (helo=diotima.switch.ch) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvKXS-0001OM-U2 for netconf@ops.ietf.org; Thu, 22 Nov 2007 22:29:10 +0000 Received: from diotima (localhost [IPv6:::1]) by diotima.switch.ch (8.14.1+Sun/8.14.1) with ESMTP id lAMMSkwY004830; Thu, 22 Nov 2007 23:28:46 +0100 (CET) From: Simon Leinen MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18246.670.185842.424015@switch.ch> Date: Thu, 22 Nov 2007 23:28:46 +0100 To: netconf@ops.ietf.org, ngo@ietf.org Subject: DRAFT agenda for NETCONF meeting at IETF 70 in Vancouver X-Mailer: VM 8.0.5-504 under Emacs 22.1.1 (sparc-sun-solaris2.11) X-Face:1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR` Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a I heard that the new NETCONF charter was approved by the IESG on 11/15. (official announcements are a little slow to come out at the moment, due to the secretariat transition) Andy and myself are stepping down as chairs with the conclusion of the old charter. Pending the appointment of new chairs, I'll chair the meeting in Vancouver. This is the DRAFT meeting agenda - sorry for the late submission! Please send any change suggestions to the NETCONF list, CC'ing the NGO list if you wish. [VOLUNTEERS FOR NOTETAKER/JABBER SCRIBE WELCOME - PLEASE SEND ME MAIL!] http://www3.ietf.org/proceedings/07dec/agenda/netconf.txt NETCONF WG IETF 70, Vancouver, BC, Canada TUESDAY, December 4, 2007 1850-1950 "Wrapping up work under the old charter" We will probably cancel this slot. WEDNESDAY, December 5, 2007 1300-1500 (Salon 1) "Bootstrapping work under the new charter" Scribes (1-5 minutes) Agenda bashing (5 minutes) WG status (10 minutes) call for WG chair volunteers New charter items 1. Fine-grained locking (15 minutes) draft-lengyel-ngo-partial-lock-01.txt 2. Netconf monitoring (10 minutes) draft-scott-netconf-monitoring-00.txt 3. Schema advertisement (30 minutes) draft-okita-netconf-advertisement-00.txt draft-scott-netconf-schema-query-00.txt 4. NETCONF over TLS (10 minutes) draft-badra-tls-netconf-04.txt AOB (35 minutes) -- Simon. -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Nov 23 06:21:07 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvWan-0008GQ-Ud for netconf-archive@lists.ietf.org; Fri, 23 Nov 2007 06:21:07 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvWai-0004sH-DI for netconf-archive@lists.ietf.org; Fri, 23 Nov 2007 06:21:05 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvWSS-000OyP-85 for netconf-data@psg.com; Fri, 23 Nov 2007 11:12:28 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3 Received: from [62.241.162.31] (helo=galaxy.systems.pipex.net) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvWSH-000Oxi-Bs for netconf@ops.ietf.org; Fri, 23 Nov 2007 11:12:22 +0000 Received: from pc6 (1Cust167.tnt4.lnd4.gbr.da.uu.net [62.188.133.167]) by galaxy.systems.pipex.net (Postfix) with SMTP id EC6B8E000310; Fri, 23 Nov 2007 11:12:11 +0000 (GMT) Message-ID: <048301c82db9$4683c6a0$0601a8c0@pc6> Reply-To: "tom.petch" From: "tom.petch" To: "Romascanu, Dan (Dan)" , References: <021d01c82b97$85b13b60$0601a8c0@pc6> Subject: Re: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC Date: Fri, 23 Nov 2007 10:45: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 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -104.0 (---------------------------------------------------) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 ---- Original Message ----- From: "Romascanu, Dan (Dan)" To: "tom.petch" ; Sent: Tuesday, November 20, 2007 11:29 PM Subject: RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC Hi Tom, The original call for comments was for draft-11, which was in IETF LC a while ago. Right now draft-12 is in LC, and in case you have any consistent comments you may want to forward them to the ietf list or to the authors. To answer your question besides the fact that cross-area reviews are a good thing, I believe that it's useful for the NETCONF community to see how other protocols are using XML for management operations in different environments. Dan Dan, Understand. I do now keep an eye on XML arising from other working groups but did not see this one as particularly insightful. I do see the simple ones - eg draft-ietf-simple-xml-patch-ops-03 - and ippm - eg draft-ietf-ippm-storetraceroutes-05 with its definition of inetAddressType:-) - as more thought provoking Tom Petch -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Nov 23 07:03:38 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvXFy-00086v-H6 for netconf-archive@lists.ietf.org; Fri, 23 Nov 2007 07:03:38 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvXFw-0005wm-7e for netconf-archive@lists.ietf.org; Fri, 23 Nov 2007 07:03:38 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvX8h-0002m7-R3 for netconf-data@psg.com; Fri, 23 Nov 2007 11:56:07 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [130.59.4.87] (helo=diotima.switch.ch) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvX88-0002i7-5d for netconf@ops.ietf.org; Fri, 23 Nov 2007 11:55:51 +0000 Received: (from leinen@localhost) by diotima.switch.ch (8.14.1+Sun/8.14.1) id lANBtQG2007927; Fri, 23 Nov 2007 12:55:26 +0100 (CET) X-Authentication-Warning: diotima.switch.ch: leinen set sender to simon.leinen@switch.ch using -f From: Simon Leinen To: netconf@ops.ietf.org Cc: ngo@ietf.org Subject: NETCONF-related sessions at IETF 70 In-Reply-To: <18246.670.185842.424015@switch.ch> (Simon Leinen's message of "Thu, 22 Nov 2007 23:28:46 +0100") References: <18246.670.185842.424015@switch.ch> X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR` Date: Fri, 23 Nov 2007 12:55:26 +0100 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (usg-unix-v) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: d6b246023072368de71562c0ab503126 Since there are a few other sessions with NETCONF content (haha, pun intended), I collected those on: http://www.ops.ietf.org/netconf/#ietf70 Complain if I have overlooked anything. Mon 0900-1130: APPAREA (Discussion on XML schemas and modeling, e.g. YANG) Mon 1740-1950: OPSAREA Open Meeting (MIB2RDML, XML Schema for NETCONF, YANG) Tue 1850-1950: NETCONF - will be CANCELED unless something comes up Tue 1520-1720: OPSAWG (Datatypes for NETCONF, smidump MIB->XSD conversion) Wed 1300-1500: NETCONF (New charter items) -- Simon. -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Nov 23 08:01:36 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvYA3-00053U-Q0 for netconf-archive@lists.ietf.org; Fri, 23 Nov 2007 08:01:35 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvYA0-0007VD-Ce for netconf-archive@lists.ietf.org; Fri, 23 Nov 2007 08:01:35 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvXze-0007aV-8w for netconf-data@psg.com; Fri, 23 Nov 2007 12:50:50 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [47.140.192.55] (helo=zrtps0kn.nortel.com) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IvXz4-0007Wt-Ka for netconf@ops.ietf.org; Fri, 23 Nov 2007 12:50:34 +0000 Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lANCo5027278; Fri, 23 Nov 2007 12:50:06 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [NGO] NETCONF-related sessions at IETF 70 Date: Fri, 23 Nov 2007 07:50:02 -0500 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B411F6C98B@zcarhxm2.corp.nortel.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [NGO] NETCONF-related sessions at IETF 70 Thread-Index: Acgtx8UBaCGovoUjQemohtkbMUzLyAABU3AA References: <18246.670.185842.424015@switch.ch> From: "Sharon Chisholm" To: "Simon Leinen" , Cc: Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Hi It would be good to reserve the timeslot and the room for an informal meeting. Now that the protocol extensions and the content specification discussions seem to have homes, what I think would be interesting is to try to identify a working group interesting in being a guinea pig for defining some NETCONF content for their work. This session could work out the plan to make that happen. Either that or for more detailed discussion of the items in the updated NETCONF charter. Sharon -----Original Message----- From: Simon Leinen [mailto:simon.leinen@switch.ch]=20 Sent: Friday, November 23, 2007 6:55 AM To: netconf@ops.ietf.org Cc: ngo@ietf.org Subject: [NGO] NETCONF-related sessions at IETF 70 Since there are a few other sessions with NETCONF content (haha, pun intended), I collected those on: http://www.ops.ietf.org/netconf/#ietf70 Complain if I have overlooked anything. Mon 0900-1130: APPAREA (Discussion on XML schemas and modeling, e.g. YANG)=20 Mon 1740-1950: OPSAREA Open Meeting (MIB2RDML, XML Schema for NETCONF, YANG)=20 Tue 1850-1950: NETCONF - will be CANCELED unless something comes up=20 Tue 1520-1720: OPSAWG (Datatypes for NETCONF, smidump MIB->XSD conversion)=20 Wed 1300-1500: NETCONF (New charter items) -- Simon. _______________________________________________ NGO mailing list NGO@ietf.org https://www1.ietf.org/mailman/listinfo/ngo -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 26 01:35:16 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwXYq-0000Ap-Gs for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 01:35:16 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwXYn-00045W-6N for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 01:35:16 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwXMa-0003tx-JF for netconf-data@psg.com; Mon, 26 Nov 2007 06:22:36 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [64.18.2.169] (helo=exprod7og108.obsmtp.com) by psg.com with smtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwXMN-0003re-2K for netconf@ops.ietf.org; Mon, 26 Nov 2007 06:22:31 +0000 Received: from source ([66.129.224.36]) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP; Sun, 25 Nov 2007 22:22:08 PST Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 25 Nov 2007 22:17:00 -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 lAQ5OrE24722; Sun, 25 Nov 2007 21:24:53 -0800 (PST) (envelope-from phil@idle.juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id lAQ5LWaq008411; Mon, 26 Nov 2007 05:21:36 GMT (envelope-from phil@idle.juniper.net) Message-Id: <200711260521.lAQ5LWaq008411@idle.juniper.net> To: "Sharon Chisholm" cc: "Simon Leinen" , netconf@ops.ietf.org, ngo@ietf.org Subject: Re: [NGO] NETCONF-related sessions at IETF 70 In-reply-to: <713043CE8B8E1348AF3C546DBE02C1B411F6C98B@zcarhxm2.corp.nortel.com> Date: Mon, 26 Nov 2007 00:21:32 -0500 From: Phil Shafer X-OriginalArrivalTime: 26 Nov 2007 06:17:00.0983 (UTC) FILETIME=[F4BFD470:01C82FF3] Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 "Sharon Chisholm" writes: >Either that or for more detailed discussion of the items in the updated >NETCONF charter. Another thought is to come up with a list of the five biggest impediments to NETCONF's complete domination of the configuration space. Do we know the answers to questions like: - Why aren't/won't device folks shipping netconf implementations? - Why aren't/won't application writers moving to NETCONF? - Why isn't NETCONF becoming the answer to configuration problems? - What's stopping it? - Where's the chicken? - What's the egg? - What's the key to moving forward from here? - Where should we be concentrating our (precious and few) resources? - Will any of the new charter items be on this list? Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 26 13:09:39 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwiOp-00040P-EB for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 13:09:39 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwiOk-00077c-US for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 13:09:39 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iwi8A-0006Ky-Fh for netconf-data@psg.com; Mon, 26 Nov 2007 17:52:26 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [206.190.49.172] (helo=web54602.mail.re2.yahoo.com) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iwi7c-0006Hj-OI for netconf@ops.ietf.org; Mon, 26 Nov 2007 17:52:12 +0000 Received: (qmail 24048 invoked by uid 60001); 26 Nov 2007 17:51:51 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=xMwbr4raHk25mJ0mvKInw/Y7c/QEz2S2OVjekslfXDlLI+1aHtIW2M1Ymtf1edK8yNvXkZv3XlNbtusfDdse7StHqxpRBKpE/TqMhMmwTaTFqvExwy7505143eXRqJkjuKIr+YZHlnxr33CsjJgrkK1jXovZoNcb1/LHt9EYbbA=; X-YMail-OSG: j6glQ4cVM1koVvw4HgB9c5lWETF6cZaDOzn8ybfo3NaIldLALBXW_3cViYtCg3MLTn6P7yhd7n8kE24dFi05p_eG3OSekQFGPndajKJbC.WPgcPlvAZ8d04fP4dOwkLvfWRMaKGX_hQJl5M- Received: from [198.206.187.100] by web54602.mail.re2.yahoo.com via HTTP; Mon, 26 Nov 2007 09:51:51 PST Date: Mon, 26 Nov 2007 09:51:51 -0800 (PST) From: Bharadwaj Kalahasti Subject: Re: [NGO] NETCONF-related sessions at IETF 70 To: Phil Shafer , Sharon Chisholm Cc: Simon Leinen , netconf@ops.ietf.org, ngo@ietf.org In-Reply-To: <200711260521.lAQ5LWaq008411@idle.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <267105.23677.qm@web54602.mail.re2.yahoo.com> Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Phil, As an implementor, I can think of one obstacle I face with movement of MIBs from use with SNMP to Netconf protocol: -- Separation of configuration and state data. -- Non-definition of a state datastore. -- Difficulty in converting existing MIB stata data into Netconf state data. My 2 cents. Kalahasti --- Phil Shafer wrote: > "Sharon Chisholm" writes: > >Either that or for more detailed discussion of the items in the updated > >NETCONF charter. > > Another thought is to come up with a list of the five biggest > impediments to NETCONF's complete domination of the configuration > space. Do we know the answers to questions like: > > - Why aren't/won't device folks shipping netconf implementations? > - Why aren't/won't application writers moving to NETCONF? > - Why isn't NETCONF becoming the answer to configuration problems? > - What's stopping it? > - Where's the chicken? > - What's the egg? > - What's the key to moving forward from here? > - Where should we be concentrating our (precious and few) resources? > - Will any of the new charter items be on this list? > > Thanks, > Phil > > -- > to unsubscribe send a message to netconf-request@ops.ietf.org with > the word 'unsubscribe' in a single line as the message text body. > archive: > ____________________________________________________________________________________ Get easy, one-click access to your favorites. Make Yahoo! your homepage. http://www.yahoo.com/r/hs -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 26 13:40:32 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwisi-0002T9-OI for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 13:40:32 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iwise-00087P-Gj for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 13:40:32 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iwij4-0009A6-BV for netconf-data@psg.com; Mon, 26 Nov 2007 18:30:34 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [64.18.2.157] (helo=exprod7og102.obsmtp.com) by psg.com with smtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwiiU-000955-NY for netconf@ops.ietf.org; Mon, 26 Nov 2007 18:30:18 +0000 Received: from source ([66.129.224.36]) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP; Mon, 26 Nov 2007 10:29:52 PST Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Nov 2007 10:29:06 -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 lAQIT5E02105; Mon, 26 Nov 2007 10:29:05 -0800 (PST) (envelope-from phil@idle.juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id lAQIPeLl012623; Mon, 26 Nov 2007 18:25:40 GMT (envelope-from phil@idle.juniper.net) Message-Id: <200711261825.lAQIPeLl012623@idle.juniper.net> To: Bharadwaj Kalahasti cc: Sharon Chisholm , Simon Leinen , netconf@ops.ietf.org, ngo@ietf.org Subject: Re: [NGO] NETCONF-related sessions at IETF 70 In-reply-to: <267105.23677.qm@web54602.mail.re2.yahoo.com> Date: Mon, 26 Nov 2007 13:25:40 -0500 From: Phil Shafer X-OriginalArrivalTime: 26 Nov 2007 18:29:06.0006 (UTC) FILETIME=[3A1A6F60:01C8305A] Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Bharadwaj Kalahasti writes: >-- Separation of configuration and state data. >-- Non-definition of a state datastore. >-- Difficulty in converting existing MIB stata data into Netconf state data. My hope is that the YANG work will address these points. Juergen Schoenwaelder has a backend to libsmi that emits YANG for MIBs, which goes a long way toward helping carry existing MIB data in NETCONF. Have you had a chance to read the YANG draft? It's available at: http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-00.txt Thanks, Phil -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Mon Nov 26 14:22:10 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwjX0-00061T-3a for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 14:22:10 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwjWw-0000tG-PA for netconf-archive@lists.ietf.org; Mon, 26 Nov 2007 14:22:10 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwjQH-000CN7-NM for netconf-data@psg.com; Mon, 26 Nov 2007 19:15:13 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [206.190.49.173] (helo=web54603.mail.re2.yahoo.com) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwjPi-000CJW-1C for netconf@ops.ietf.org; Mon, 26 Nov 2007 19:14:57 +0000 Received: (qmail 46017 invoked by uid 60001); 26 Nov 2007 19:14:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=QL8GQw4NtaFRvmjZ2C6lNw8SB+yuGrr/cGfj+xU+vQVYWs3ClTtMoergcKNlWwBpvuOeUxGNaUe723BCpAHDnbmJytiUOcsjXUb8VSw6sdQ8x20ogHicKEGwV/xzNwTDGLwscyVAGPlpma6vVY5A9JujXP2RWfJE4SzVJmOnejQ=; X-YMail-OSG: 7ch844IVM1kXrWfEfyFu7UJxKXJVqisbC9RnjrmqdqxAA59aMd.iKu2yVZ3ayO4j8mC5vn5k7dnHAmzPoAmxYjkNvufaSUH3P0NteOvLafhRIECp2NiLhisNs23qVsvLvF3EjowiEP59FWFM6arm4aSwew-- Received: from [198.206.187.100] by web54603.mail.re2.yahoo.com via HTTP; Mon, 26 Nov 2007 11:14:32 PST Date: Mon, 26 Nov 2007 11:14:32 -0800 (PST) From: Bharadwaj Kalahasti Subject: Re: [NGO] NETCONF-related sessions at IETF 70 To: Phil Shafer Cc: Sharon Chisholm , Simon Leinen , netconf@ops.ietf.org, ngo@ietf.org In-Reply-To: <200711261825.lAQIPeLl012623@idle.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <169906.29955.qm@web54603.mail.re2.yahoo.com> Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Phil, Thanks for the answer. I will review the YANG draft. Regards, Kalahasti --- Phil Shafer wrote: > Bharadwaj Kalahasti writes: > >-- Separation of configuration and state data. > >-- Non-definition of a state datastore. > >-- Difficulty in converting existing MIB stata data into Netconf state data. > > My hope is that the YANG work will address these points. Juergen > Schoenwaelder has a backend to libsmi that emits YANG for MIBs, > which goes a long way toward helping carry existing MIB data in > NETCONF. Have you had a chance to read the YANG draft? > It's available at: > > http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-00.txt > > Thanks, > Phil > ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 27 04:54:49 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwx9V-0007wn-Iz for netconf-archive@lists.ietf.org; Tue, 27 Nov 2007 04:54:49 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iwx9S-0001ns-1M for netconf-archive@lists.ietf.org; Tue, 27 Nov 2007 04:54:49 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwwuJ-000EUK-Tl for netconf-data@psg.com; Tue, 27 Nov 2007 09:39:07 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [66.249.92.172] (helo=ug-out-1314.google.com) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iwwtc-000ERl-HI for netconf@ops.ietf.org; Tue, 27 Nov 2007 09:38:41 +0000 Received: by ug-out-1314.google.com with SMTP id k3so168714ugf for ; Tue, 27 Nov 2007 01:38:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; bh=brBqAVNpRRgGVHVVzM3tZC7UaaYeA3sxTeQhDx/T7ug=; b=mXpb26AUu9XtUo/QlyuQB2zghJtEH3cytPpWJrplENl4jPuz8GOrtqu9rPhqqoHF+XvqWeLXi3sEDcYPLYQRK0jvR4PCaSDxV6V0vP2uy4URi97S10MB9CXCQW+8K3CEqxlgdBt+RHpgAfFodgZCAjnsIEw5UYdVrWLE5nijG58= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; b=Go9r/cFIPXFam/PZQJ8edWnXMG0Y8bd7LonSdFsDdFd8T9RQQueQYSbzHeU6UeyiY9nK0+XKHWGsmK4KJ2eMs7rQpHnDEgDNzM2qiEg76DFN2UgeOKvdzLOS7y829HLq7mRo+1n+iGI72kNpizQzyDouRZN6qFzzWiBhFVQhogs= Received: by 10.67.19.11 with SMTP id w11mr558344ugi.1196156300147; Tue, 27 Nov 2007 01:38:20 -0800 (PST) Received: from ?192.168.1.75? ( [195.72.179.98]) by mx.google.com with ESMTPS id b35sm252149ugd.2007.11.27.01.38.18 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 27 Nov 2007 01:38:18 -0800 (PST) Cc: ngo@ietf.org Message-Id: <8C1259C3-737F-4E9C-8585-1D10E0162368@jadickinson.co.uk> From: John Dickinson To: netconf@ops.ietf.org In-Reply-To: <200711260521.lAQ5LWaq008411@idle.juniper.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Subject: Re: [NGO] NETCONF-related sessions at IETF 70 Date: Tue, 27 Nov 2007 09:38:16 +0000 References: <200711260521.lAQ5LWaq008411@idle.juniper.net> X-Mailer: Apple Mail (2.915) Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 On 26 Nov 2007, at 05:21, Phil Shafer wrote: > "Sharon Chisholm" writes: >> Either that or for more detailed discussion of the items in the >> updated >> NETCONF charter. > > Another thought is to come up with a list of the five biggest > impediments to NETCONF's complete domination of the configuration > space. Do we know the answers to questions like: > > - Why aren't/won't device folks shipping netconf implementations? > - Why aren't/won't application writers moving to NETCONF? > - Why isn't NETCONF becoming the answer to configuration problems? > - What's stopping it? > - Where's the chicken? > - What's the egg? > - What's the key to moving forward from here? > - Where should we be concentrating our (precious and few) resources? > - Will any of the new charter items be on this list? I think that such a discussion would be very useful in getting the word out about NETCONF and helping people understand how it could be used. There has, for example, been some discussion in the dnsop WG about developing a protocol for configuring and controlling nameservers (http://tools.ietf.org/wg/dnsop/minutes?item=minutes69.html ) and I am one of the authors of a draft (http://www.ietf.org/internet-drafts/draft-arends-nscp-00.txt ) that suggests using NETCONF. The biggest issue for me in choosing NETCONF was and is to be sure I am using NETCONF appropriately and that it really is the correct solution to my problem. I am currently looking at such things as, what would be an appropriate data model, how to correctly use capabilities and how to engineer things that are not strictly configuration, such as control commands, monitoring and statistics gathering. Thanks, John --- John Dickinson jad@jadickinson.co.uk -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 27 05:36:43 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwxo3-0004Tv-6K for netconf-archive@lists.ietf.org; Tue, 27 Nov 2007 05:36:43 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iwxo0-0005qU-41 for netconf-archive@lists.ietf.org; Tue, 27 Nov 2007 05:36:43 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iwxf6-000HRV-Lp for netconf-data@psg.com; Tue, 27 Nov 2007 10:27:28 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-202.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO,USER_IN_WHITELIST autolearn=no version=3.2.3 Received: from [156.154.16.138] (helo=ns1.neustar.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwhY0-0003Mn-O1 for netconf@ops.ietf.org; Mon, 26 Nov 2007 17:15:18 +0000 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 7072F26E80; Mon, 26 Nov 2007 17:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IwhXx-0007q9-BX; Mon, 26 Nov 2007 12:15:01 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: ietf-announce@ietf.org Cc: netconf@ops.ietf.org, Andy Bierman , Simon Linen From: IESG Secretary Subject: WG Action: RECHARTER: Network Configuration WG (netconf) Message-Id: Date: Mon, 26 Nov 2007 12:15:01 -0500 Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: bcd240e64c427d3d3617cfc704e7fd7f The Network Configuration (netconf) working group in the Operations and Management Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. +++ Network Configuration (netconf) ================================ Current Status: Active Working Group Chair(s): Andy Bierman Simon Linen Operations and Management Area Director(s): Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Technical Advisor(s): Wesley Hardaker Mailing Lists: General Discussion: netconf@ops.ietf.org To Subscribe: netconf-request@ops.ietf.org In Body: in msg body: subscribe Archive: https://ops.ietf.org/lists/netconf Description of Working Group: Wes Hardaker is Technical Advisor for Security Matters Configuration of networks of devices has become a critical requirement for operators in today's highly interoperable networks. Operators from large to small have developed their own mechanisms or used vendor specific mechanisms to transfer configuration data to and from a device, and for examining device state information which may impact the configuration. Each of these mechanisms may be different in various aspects, such as session establishment, user authentication, configuration data exchange, and error responses. The NETCONF Working Group is chartered to produce a protocol suitable for network configuration, with the following characteristics: - Provides retrieval mechanisms which can differentiate between configuration data and non-configuration data - Is extensible enough that vendors will provide access to all configuration data on the device using a single protocol - Has a programmatic interface (avoids screen scraping and formatting-related changes between releases) - Uses a textual data representation, that can be easily manipulated using non-specialized text manipulation tools. - Supports integration with existing user authentication methods - Supports integration with existing configuration database systems - Supports network wide configuration transactions (with features such as locking and rollback capability) - Is as transport-independent as possible - Provides the following support for asynchronous notifications: - Specify the message (capability exchange) details to support notifications. - Specify the application mapping details to support notifications. - Specify the protocol syntax and semantics of a notification message. - Specify or select a notification content information model. - Specify a mechanism for controlling the delivery (turn on/off) of notifications during a session. - Specify a mechanism for selectively receiving a configurable subset of all possible notification types. The NETCONF protocol will use XML for data encoding purposes, because XML is a widely deployed standard which is supported by a large number of applications. XML also supports hierarchical data structures. The NETCONF protocol should be independent of the data definition language and data models used to describe configuration and state data. However, the authorization model used in the protocol is dependent on the data model. Although these issues must be fully addressed to develop standard data models, only a small part of this work will be initially addressed. This group will specify requirements for standard data models in order to fully support the NETCONF protocol, such as: - identification of principals, such as user names or distinguished names - mechanism to distinguish configuration from non-configuration data - XML namespace conventions - XML usage guidelines It should be possible to transport the NETCONF protocol using several different protocols. The group will select at least one suitable transport mechanism, and define a mapping for the selected protocol(s). The initial work (has completed) and was restricted to the following items: - NETCONF Protocol Specification, which defines the operational model, protocol operations, transaction model, data model requirements, security requirements, and transport layer requirements. - NETCONF over SSH Specification: Implementation Mandatory; NETCONF over BEEP Specification: Implementation Optional; NETCONF over SOAP Specification: Implementation Optional; These documents define how the NETCONF protocol is used with each transport protocol selected by the working group, and how it meets the security and transport layer requirements of the NETCONF Protocol Specification. Additional Notification work (as described above) will now be addressed since the initial work has been completed. An individual submission Internet Draft has been proposed to the WG as the starting point for the Notification work. The WG shall adopt the document identified as 'draft-chisholm-NETCONF-event-01.txt' as the starting point for this work. A second phase of incremental development of NETCONF will include the following items: 1. Fine-grain locking: The base NETCONF protocol only provides a lock for the entire configuration datastore, which is not deemed to meet important operational and security requirements. The NETCONF working group will produce a standards-track RFC specifying a mechanism for fine-grain locking of the NETCONF configuration datastore. (The initial draft will be based on draft-lengyel-ngo-partial-lock-00.txt barring additional contributions from the community.) 2. NETCONF monitoring: It is considered best practice for IETF working groups to include management of their protocols within the scope of the solution they are providing. NETCONF does not provide this capability. The NETCONF working group will produce a standards-track RFC with mechanisms allowing NETCONF itself to be used to monitor some aspects of NETCONF operation. (The initial draft will be based on draft-chisholm-netconf-monitoring-00.txt barring additional contributions from the community.) 3. Schema advertisement: Currently the NETCONF protocol is able to advertise which protocol features are supported on a particular netconf-capable device. However, there is currently no way to discover which XML Schema are supported on the device. The NETCONF working group will produce a standards-track RFC with mechanisms making this discovery possible. This item may be merged with "NETCONF monitoring" into a single document. (The initial draft will be based on draft-scott-netconf-schema-query-00.txt barring additional contributions from the community.) 4. NETCONF over TLS - based on implementation experience there is a need for a standards track document to define NETCONF over TLS as an optional transport for NETCONF (The initial draft will be based on draft-badra-tls-netconf-04.txt barring additional contributions from the community.) The following are currently not considered in scope for re-chartering at this time, but may be candidates for work when there is community consensus to take them on. Individual submissions are being encouraged. o Access Control requirements o General improvements to the base protocol o NETCONF access to SMI-based MIB data o The Bill Fenner problem: Address real or perceived issue that "giving SSH for NETCONF gives full SSH access to the box" Goals and Milestones: Done Working Group formed Done Submit initial NETCONF Protocol draft Done Submit initial NETCONF over (transport-TBD) draft Done Begin Working Group Last Call for the NETCONF Protocol draft Done Begin Working Group Last Call for the NETCONF over (transport-TBD) draft Done Submit final version of the NETCONF Protocol draft to the IESG Done Submit final version of the NETCONF over SOAP draft to the IESG Done Submit final version of the NETCONF over BEEP draft to the IESG Done Submit final version of the NETCONF over SSH draft to the IESG Done Update charter Done Submit first version of NETCONF Notifications document Done Begin WGLC of NETCONF Notifications document Dec 2006 Submit final version of NETCONF Notifications document to IESG for consideration as Proposed Standard December 2007 -00 draft for NETCONF Monitoring December 2007 -00 draft for Schema Advertisement December 2007 -00 draft for Fine Grain Locking December 2007 -00 draft for NETCONF over TLS March 2008 - Early Review of client authentication approach (for NETCONF over TLS) with the security community at IETF 71 August 2008 - WG Last Call on NETCONF Monitoring after IETF72 August 2008 - WG Last Call on Schema Advertisement after IETF72 August 2008 - WG Last Call on Fine Grain Locking after IETF72 August 2008 - WG Last Call on NETCONF over TLS after IETF72 October 2008 Send four documents to the IESG for consideration as proposed standards -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Tue Nov 27 05:43:57 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwxv3-00016d-J9 for netconf-archive@lists.ietf.org; Tue, 27 Nov 2007 05:43:57 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iwxv0-0006Yf-52 for netconf-archive@lists.ietf.org; Tue, 27 Nov 2007 05:43:57 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iwxnk-000I0v-7V for netconf-data@psg.com; Tue, 27 Nov 2007 10:36:24 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [213.180.94.162] (helo=mail.tail-f.com) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IwxnA-000Hxq-Ev for netconf@ops.ietf.org; Tue, 27 Nov 2007 10:36:08 +0000 Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTP id 416861B80C3; Tue, 27 Nov 2007 11:35:47 +0100 (CET) Date: Tue, 27 Nov 2007 11:36:51 +0100 (CET) Message-Id: <20071127.113651.89794928.mbj@tail-f.com> To: jad@jadickinson.co.uk Cc: netconf@ops.ietf.org, ngo@ietf.org Subject: Re: [NGO] NETCONF-related sessions at IETF 70 From: Martin Bjorklund In-Reply-To: <8C1259C3-737F-4E9C-8585-1D10E0162368@jadickinson.co.uk> References: <200711260521.lAQ5LWaq008411@idle.juniper.net> <8C1259C3-737F-4E9C-8585-1D10E0162368@jadickinson.co.uk> X-Mailer: Mew version 5.1.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Hi John, John Dickinson wrote: > There has, for example, been some discussion in the dnsop WG about > developing a protocol for configuring and controlling nameservers (http://tools.ietf.org/wg/dnsop/minutes?item=minutes69.html > ) and I am one of the authors of a draft (http://www.ietf.org/internet-drafts/draft-arends-nscp-00.txt > ) that suggests using NETCONF. > > The biggest issue for me in choosing NETCONF was and is to be sure I > am using NETCONF appropriately and that it really is the correct > solution to my problem. I have read your draft and I do believe (and hope!) that NETCONF is a good solution to this problem. > I am currently looking at such things as, what > would be an appropriate data model, how to correctly use capabilities > and how to engineer things that are not strictly configuration, such > as control commands, monitoring and statistics gathering. In your draft you also listed: Be extensible to allow implementors to extend to cover new objects and methods. Maybe not suprising, but these are exactly the problems that YANG is designed to help you with. To be more specific, with YANG, you can write a standard data model with the the (most) common configuration parameters. Vendors can then augment this standard data model with vendor-specific config params. As an example (NOTE: I don't know what parameters actually would make sense, this is just an example): container server { container panorama { list view { key view-name; leaf-list match-client { type inet:ip-prefix; } leaf recursion { type boolean; } ... } } } Then vendor X can add its own proprietary stuff: augment /dns:server/dns:panorama/dns:view { leaf funky-cache-option { ... } ... } And in the NETCONF XML you might see: mybiew 192.168.23.0/24 172.16.30.0/16 true magic The same goes for commands (rpcs). You can define standard rpc, and vendors can e.g. add new rpcs, or augment the standard rpcs. /martin -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Nov 29 17:40:47 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ixs3r-0006sH-QZ for netconf-archive@lists.ietf.org; Thu, 29 Nov 2007 17:40:47 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ixs3r-0000Mn-EX for netconf-archive@lists.ietf.org; Thu, 29 Nov 2007 17:40:47 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Ixrvv-0000A6-BX for netconf-data@psg.com; Thu, 29 Nov 2007 22:32:35 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [130.59.4.87] (helo=diotima.switch.ch) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Ixqoc-000KGT-H6 for netconf@ops.ietf.org; Thu, 29 Nov 2007 21:21:05 +0000 Received: (from leinen@localhost) by diotima.switch.ch (8.14.1+Sun/8.14.1) id lATLKmp2003758; Thu, 29 Nov 2007 22:20:48 +0100 (CET) X-Authentication-Warning: diotima.switch.ch: leinen set sender to simon.leinen@switch.ch using -f From: Simon Leinen To: "Sharon Chisholm" Cc: , Subject: Re: [NGO] NETCONF-related sessions at IETF 70 In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B411F6C98B@zcarhxm2.corp.nortel.com> (Sharon Chisholm's message of "Fri, 23 Nov 2007 07:50:02 -0500") References: <18246.670.185842.424015@switch.ch> <713043CE8B8E1348AF3C546DBE02C1B411F6C98B@zcarhxm2.corp.nortel.com> X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR` Date: Thu, 29 Nov 2007 22:20:48 +0100 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (usg-unix-v) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Sharon Chisholm writes: > It would be good to reserve the timeslot and the room for an > informal meeting. OK, so let's go ahead like this: As I suggested, we cancel the short NETCONF slot (TUESDAY, December 4, 2007 1850-1950), and try to keep the room for informal discussions. > Now that the protocol extensions and the content specification > discussions seem to have homes, what I think would be interesting is > to try to identify a working group interesting in being a guinea pig > for defining some NETCONF content for their work. This session could > work out the plan to make that happen. IPFIX seems to be a good candidate, because they have development of "an XML-based configuration data model that can be used for configuring IPFIX devices and for storing, modifying and managing IPFIX configurations parameter sets" on their brand-new charter, which also notes that "This work will be performed in close collaboration with the NETCONF WG". IPFIX meets on Tuesday 1300-1500, and I'll be chairing the meeting (since the real IPFIX chairs won't be in Vancouver), so I can invite interested participants to our informal meeting on Tuesday evening. OK? > Either that or for more detailed discussion of the items in the > updated NETCONF charter. I hope two hours are sufficient for that. -- Simon. -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Thu Nov 29 17:56:40 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxsJE-0006II-P8 for netconf-archive@lists.ietf.org; Thu, 29 Nov 2007 17:56:40 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxsJC-0006Je-SQ for netconf-archive@lists.ietf.org; Thu, 29 Nov 2007 17:56:40 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IxsBc-0001Un-50 for netconf-data@psg.com; Thu, 29 Nov 2007 22:48:48 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [130.59.4.87] (helo=diotima.switch.ch) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IxsAx-0001RU-BU for netconf@ops.ietf.org; Thu, 29 Nov 2007 22:48:27 +0000 Received: from diotima (localhost [IPv6:::1]) by diotima.switch.ch (8.14.1+Sun/8.14.1) with ESMTP id lATMm3U8004511; Thu, 29 Nov 2007 23:48:03 +0100 (CET) From: Simon Leinen MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18255.16803.842234.805741@switch.ch> Date: Thu, 29 Nov 2007 23:48:03 +0100 To: netconf@ops.ietf.org, ngo@ietf.org Subject: Preparation for the NETCONF meeting next Wednesday X-Mailer: VM 8.1.0-devo-484 under Emacs 22.1.1 (sparc-sun-solaris2.11) X-Face:1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR` Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Dear NETCONF WG participants, here are a few things I'd like you to consider before the NETCONF WG meeting in Vancouver (Wednesday 1300-1500, Salon 1): 1.) We need a notetaker and Jabber scribe (ideally two different persons). If you are willing to volunteer, send me mail. Thanks! 2.) At the meeting next Wednesday, we'll go through the new charter items and discuss whether individual Internet-Drafts should be adopted by the Working Group. Therefore it is especially important that you have READ THE DRAFTS. Pointers can be found in the agenda on the IETF tools site: http://tools.ietf.org/wg/netconf/agenda 3.) Remember that Andy and I are stepping back at chairs of the WG; our ADs have issued a call for volunteers. This call is still open. In particular, the ADs would like to hear from candidates with an operator background. If interested, please contact Dan Romascanu and Ron Bonica . Have a good trip, and see you in Vancouver or on the 'net, -- Simon. -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Nov 30 02:21:23 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iy0Bf-0006jn-UJ for netconf-archive@lists.ietf.org; Fri, 30 Nov 2007 02:21:23 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iy0Bf-0002FN-7I for netconf-archive@lists.ietf.org; Fri, 30 Nov 2007 02:21:23 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iy02w-000BQI-7a for netconf-data@psg.com; Fri, 30 Nov 2007 07:12:22 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-102.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, USER_IN_ALL_SPAM_TO autolearn=no version=3.2.3 Received: from [193.180.251.60] (helo=mailgw3.ericsson.se) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iy02M-000BOi-9y for netconf@ops.ietf.org; Fri, 30 Nov 2007 07:12:06 +0000 Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 39E4720ECD; Fri, 30 Nov 2007 08:11:42 +0100 (CET) X-AuditID: c1b4fb3c-aff97bb0000030cf-cb-474fb7ae4bbf Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0FFDF20410; Fri, 30 Nov 2007 08:11:42 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 08:11:41 +0100 Received: from [159.107.198.61] ([159.107.198.61]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 08:11:40 +0100 Message-ID: <474FB7A3.9000903@ericsson.com> Date: Fri, 30 Nov 2007 08:11:31 +0100 From: Balazs Lengyel User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: Simon Leinen CC: Sharon Chisholm , netconf@ops.ietf.org, ngo@ietf.org Subject: Re: [NGO] NETCONF-related sessions at IETF 70 References: <18246.670.185842.424015@switch.ch> <713043CE8B8E1348AF3C546DBE02C1B411F6C98B@zcarhxm2.corp.nortel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Nov 2007 07:11:40.0895 (UTC) FILETIME=[4161AEF0:01C83320] X-Brightmail-Tracker: AAAAAA== Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: -4.0 (----) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Hello Simon, Sharon, We also have John Dickinson from DNSOP. He seems a very promising candidate. Balazs John Dickinson wrote: > > There has, for example, been some discussion in the dnsop WG about > > developing a protocol for configuring and controlling nameservers (http://tools.ietf.org/wg/dnsop/minutes?item=minutes69.html > > ) and I am one of the authors of a draft (http://www.ietf.org/internet-drafts/draft-arends-nscp-00.txt > > ) that suggests using NETCONF. > > > > The biggest issue for me in choosing NETCONF was and is to be sure I > > am using NETCONF appropriately and that it really is the correct > > solution to my problem. I have read your draft and I do believe (and hope!) that NETCONF is a good solution to this problem. > > I am currently looking at such things as, what > > would be an appropriate data model, how to correctly use capabilities > > and how to engineer things that are not strictly configuration, such > > as control commands, monitoring and statistics gathering. In your draft you also listed: Be extensible to allow implementors to extend to cover new objects and methods. Maybe not suprising, but these are exactly the problems that YANG is designed to help you with. To be more specific, with YANG, you can write a standard data model with the the (most) common configuration parameters. Vendors can then augment this standard data model with vendor-specific config params. As an example (NOTE: I don't know what parameters actually would make sense, this is just an example): container server { container panorama { list view { key view-name; leaf-list match-client { type inet:ip-prefix; } leaf recursion { type boolean; } ... } } } Then vendor X can add its own proprietary stuff: augment /dns:server/dns:panorama/dns:view { leaf funky-cache-option { ... } ... } And in the NETCONF XML you might see: mybiew 192.168.23.0/24 172.16.30.0/16 true magic The same goes for commands (rpcs). You can define standard rpc, and vendors can e.g. add new rpcs, or augment the standard rpcs. /martin _______________________________________________ NGO mailing list NGO@ietf.org http --------------------------------------------------------------------------------------- Simon Leinen wrote: > Sharon Chisholm writes: >> It would be good to reserve the timeslot and the room for an >> informal meeting. > > OK, so let's go ahead like this: As I suggested, we cancel the short > NETCONF slot (TUESDAY, December 4, 2007 1850-1950), and try to keep > the room for informal discussions. > >> Now that the protocol extensions and the content specification >> discussions seem to have homes, what I think would be interesting is >> to try to identify a working group interesting in being a guinea pig >> for defining some NETCONF content for their work. This session could >> work out the plan to make that happen. > > IPFIX seems to be a good candidate, because they have development of > "an XML-based configuration data model that can be used for > configuring IPFIX devices and for storing, modifying and managing > IPFIX configurations parameter sets" on their brand-new charter, which > also notes that "This work will be performed in close collaboration > with the NETCONF WG". > > IPFIX meets on Tuesday 1300-1500, and I'll be chairing the meeting > (since the real IPFIX chairs won't be in Vancouver), so I can invite > interested participants to our informal meeting on Tuesday evening. > > OK? > >> Either that or for more detailed discussion of the items in the >> updated NETCONF charter. > > I hope two hours are sufficient for that. -- Balazs Lengyel Ericsson Hungary Ltd. TSP System Manager ECN: 831 7320 Fax: +36 1 4377792 Tel: +36-1-437-7320 email: Balazs.Lengyel@ericsson.com -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: From owner-netconf@ops.ietf.org Fri Nov 30 08:53:29 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iy6J7-0008Tg-PX for netconf-archive@lists.ietf.org; Fri, 30 Nov 2007 08:53:29 -0500 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iy6J5-0001tm-To for netconf-archive@lists.ietf.org; Fri, 30 Nov 2007 08:53:29 -0500 Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iy5u8-000CiT-Hu for netconf-data@psg.com; Fri, 30 Nov 2007 13:27:40 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com X-Spam-Level: X-Spam-Status: No, score=-201.1 required=5.0 tests=AWL,BAYES_00,FH_HAS_XAIMC, RDNS_NONE,USER_IN_ALL_SPAM_TO,USER_IN_WHITELIST autolearn=no version=3.2.3 Received: from [202.99.23.227] (helo=people.com.cn) by psg.com with smtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iy3vA-0002FM-9Z for netconf@ops.ietf.org; Fri, 30 Nov 2007 11:20:58 +0000 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm54750512a; Fri, 30 Nov 2007 19:33:37 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm178474b1b76; Tue, 27 Nov 2007 01:33:10 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Tue, 27 Nov 2007 01:33:10 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwhY6-0004fj-CP; Mon, 26 Nov 2007 12:15:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwhY3-0004dz-T3 for ietf-announce@ietf.org; Mon, 26 Nov 2007 12:15:07 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwhXx-0004NY-HZ for ietf-announce@ietf.org; Mon, 26 Nov 2007 12:15:07 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 7072F26E80; Mon, 26 Nov 2007 17:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IwhXx-0007q9-BX; Mon, 26 Nov 2007 12:15:01 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: ietf-announce@ietf.org From: IESG Secretary Message-Id: Date: Mon, 26 Nov 2007 12:15:01 -0500 X-Scan-Signature: e367d58950869b6582535ddf5a673488 Cc: Simon Linen , netconf@ops.ietf.org Subject: WG Action: RECHARTER: Network Configuration WG (netconf) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , X-AIMC-AUTH: (null) X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: iesg-secretary@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn Sender: owner-netconf@ops.ietf.org Precedence: bulk X-Spam-Score: 0.9 (/) X-Scan-Signature: 325b777e1a3a618c889460b612a65510 The Network Configuration (netconf) working group in the Operations and Management Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. +++ Network Configuration (netconf) ================================ Current Status: Active Working Group Chair(s): Andy Bierman Simon Linen Operations and Management Area Director(s): Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Technical Advisor(s): Wesley Hardaker Mailing Lists: General Discussion: netconf@ops.ietf.org To Subscribe: netconf-request@ops.ietf.org In Body: in msg body: subscribe Archive: https://ops.ietf.org/lists/netconf Description of Working Group: Wes Hardaker is Technical Advisor for Security Matters Configuration of networks of devices has become a critical requirement for operators in today's highly interoperable networks. Operators from large to small have developed their own mechanisms or used vendor specific mechanisms to transfer configuration data to and from a device, and for examining device state information which may impact the configuration. Each of these mechanisms may be different in various aspects, such as session establishment, user authentication, configuration data exchange, and error responses. The NETCONF Working Group is chartered to produce a protocol suitable for network configuration, with the following characteristics: - Provides retrieval mechanisms which can differentiate between configuration data and non-configuration data - Is extensible enough that vendors will provide access to all configuration data on the device using a single protocol - Has a programmatic interface (avoids screen scraping and formatting-related changes between releases) - Uses a textual data representation, that can be easily manipulated using non-specialized text manipulation tools. - Supports integration with existing user authentication methods - Supports integration with existing configuration database systems - Supports network wide configuration transactions (with features such as locking and rollback capability) - Is as transport-independent as possible - Provides the following support for asynchronous notifications: - Specify the message (capability exchange) details to support notifications. - Specify the application mapping details to support notifications. - Specify the protocol syntax and semantics of a notification message. - Specify or select a notification content information model. - Specify a mechanism for controlling the delivery (turn on/off) of notifications during a session. - Specify a mechanism for selectively receiving a configurable subset of all possible notification types. The NETCONF protocol will use XML for data encoding purposes, because XML is a widely deployed standard which is supported by a large number of applications. XML also supports hierarchical data structures. The NETCONF protocol should be independent of the data definition language and data models used to describe configuration and state data. However, the authorization model used in the protocol is dependent on the data model. Although these issues must be fully addressed to develop standard data models, only a small part of this work will be initially addressed. This group will specify requirements for standard data models in order to fully support the NETCONF protocol, such as: - identification of principals, such as user names or distinguished names - mechanism to distinguish configuration from non-configuration data - XML namespace conventions - XML usage guidelines It should be possible to transport the NETCONF protocol using several different protocols. The group will select at least one suitable transport mechanism, and define a mapping for the selected protocol(s). The initial work (has completed) and was restricted to the following items: - NETCONF Protocol Specification, which defines the operational model, protocol operations, transaction model, data model requirements, security requirements, and transport layer requirements. - NETCONF over SSH Specification: Implementation Mandatory; NETCONF over BEEP Specification: Implementation Optional; NETCONF over SOAP Specification: Implementation Optional; These documents define how the NETCONF protocol is used with each transport protocol selected by the working group, and how it meets the security and transport layer requirements of the NETCONF Protocol Specification. Additional Notification work (as described above) will now be addressed since the initial work has been completed. An individual submission Internet Draft has been proposed to the WG as the starting point for the Notification work. The WG shall adopt the document identified as 'draft-chisholm-NETCONF-event-01.txt' as the starting point for this work. A second phase of incremental development of NETCONF will include the following items: 1. Fine-grain locking: The base NETCONF protocol only provides a lock for the entire configuration datastore, which is not deemed to meet important operational and security requirements. The NETCONF working group will produce a standards-track RFC specifying a mechanism for fine-grain locking of the NETCONF configuration datastore. (The initial draft will be based on draft-lengyel-ngo-partial-lock-00.txt barring additional contributions from the community.) 2. NETCONF monitoring: It is considered best practice for IETF working groups to include management of their protocols within the scope of the solution they are providing. NETCONF does not provide this capability. The NETCONF working group will produce a standards-track RFC with mechanisms allowing NETCONF itself to be used to monitor some aspects of NETCONF operation. (The initial draft will be based on draft-chisholm-netconf-monitoring-00.txt barring additional contributions from the community.) 3. Schema advertisement: Currently the NETCONF protocol is able to advertise which protocol features are supported on a particular netconf-capable device. However, there is currently no way to discover which XML Schema are supported on the device. The NETCONF working group will produce a standards-track RFC with mechanisms making this discovery possible. This item may be merged with "NETCONF monitoring" into a single document. (The initial draft will be based on draft-scott-netconf-schema-query-00.txt barring additional contributions from the community.) 4. NETCONF over TLS - based on implementation experience there is a need for a standards track document to define NETCONF over TLS as an optional transport for NETCONF (The initial draft will be based on draft-badra-tls-netconf-04.txt barring additional contributions from the community.) The following are currently not considered in scope for re-chartering at this time, but may be candidates for work when there is community consensus to take them on. Individual submissions are being encouraged. o Access Control requirements o General improvements to the base protocol o NETCONF access to SMI-based MIB data o The Bill Fenner problem: Address real or perceived issue that "giving SSH for NETCONF gives full SSH access to the box" Goals and Milestones: Done Working Group formed Done Submit initial NETCONF Protocol draft Done Submit initial NETCONF over (transport-TBD) draft Done Begin Working Group Last Call for the NETCONF Protocol draft Done Begin Working Group Last Call for the NETCONF over (transport-TBD) draft Done Submit final version of the NETCONF Protocol draft to the IESG Done Submit final version of the NETCONF over SOAP draft to the IESG Done Submit final version of the NETCONF over BEEP draft to the IESG Done Submit final version of the NETCONF over SSH draft to the IESG Done Update charter Done Submit first version of NETCONF Notifications document Done Begin WGLC of NETCONF Notifications document Dec 2006 Submit final version of NETCONF Notifications document to IESG for consideration as Proposed Standard December 2007 -00 draft for NETCONF Monitoring December 2007 -00 draft for Schema Advertisement December 2007 -00 draft for Fine Grain Locking December 2007 -00 draft for NETCONF over TLS March 2008 - Early Review of client authentication approach (for NETCONF over TLS) with the security community at IETF 71 August 2008 - WG Last Call on NETCONF Monitoring after IETF72 August 2008 - WG Last Call on Schema Advertisement after IETF72 August 2008 - WG Last Call on Fine Grain Locking after IETF72 August 2008 - WG Last Call on NETCONF over TLS after IETF72 October 2008 Send four documents to the IESG for consideration as proposed standards _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: