From netmod-bounces@ietf.org Tue Apr 29 23:40:03 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D84A3A6800; Tue, 29 Apr 2008 23:40:03 -0700 (PDT) X-Original-To: netmod@ietf.org Delivered-To: netmod@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 117783A6D95; Tue, 29 Apr 2008 19:43:40 -0700 (PDT) Mime-Version: 1.0 To: IETF Announcement list From: The IESG Message-Id: <20080430024340.117783A6D95@core3.amsl.com> Date: Tue, 29 Apr 2008 19:43:40 -0700 (PDT) X-Mailman-Approved-At: Tue, 29 Apr 2008 23:40:02 -0700 Cc: dbharrington@comcast.net, david.partain@ericsson.com, netmod@ietf.org Subject: [netmod] WG Action: NETCONF Data Modeling Language (netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org A new IETF working group has been formed in the Operations and Management Area. For additional information, please contact the Area Directors or the WG Chairs. NETCONF Data Modeling Language (netmod) --------------------------------------------- Chair(s): David Harrington David Partain Operations and Management Area Director(s): Dan Romascanu Ronald Bonica >rbonica@juniper.net> Operations and Management Area Advisor: Dan Romascanu Mailing Lists: General Discussion: netmod@ietf.org To Subscribe: netmod-request@ietf.org In Body: in msg body: subscribe Archive: http://www.ietf.org/mail-archive/web/netmod/ Description: The NETCONF Working Group has completed a base protocol to be used for configuration management. However, the NETCONF protocol does not include a standard content layer. The specifications do not include a modeling language or accompanying rules that can be used to model the management information that is to be configured using NETCONF. This has resulted in inconsistent syntax and interoperability problems. The purpose of NETMOD is to support the ongoing development of IETF and vendor-defined data models for NETCONF. NETMOD's requirements are drawn from the RCDML requirements draft (draft-presuhn-rcdml) and documents referenced therein. The WG will define a "human-friendly" modeling language defining the semantics of operational data, configuration data, notifications, and operations. This language will focus on readability and ease of use. This language must be able to serve as the normative description of NETCONF data models. The WG will use YANG (draft-bjorklund-yang) as its starting point for this language. Language abstractions that facilitate model extensibility and reuse have been identified as a work area and will be considered as a work item or may be integrated into the YANG document based on WG consensus. The WG will define a canonical mapping of this language to NETCONF XML instance documents, the on-the-wire format of YANG-defined XML content. Only data models defined in YANG will have to adhere to this on-the-wire format. In order to leverage existing XML tools for validating NETCONF data in various contexts and also facilitate exchange of data models and schemas with other IETF working groups, the WG will define standard mapping rules from YANG to the DSDL data modeling framework (ISO/IEC 19757) with additional annotations to preserve semantics. The initial YANG mapping rules specifications are expressly defined for NETCONF modeling. However, there may be future areas of applicability beyond NETCONF, and the WG must provide suitable language extensibility mechanisms to allow for such future work. The NETMOD WG will only address modeling NETCONF devices and the language extensibility mechanisms. Any application of YANG to other protocols is future work. The WG will consult with the NETCONF WG to ensure that NETMOD's decision do not conflict with planned work in NETCONF (e.g., locking, notifications). While it is desirable to provide a migration path from existing MIB modules to YANG data models (modules), it is not a requirement to provide full compatibility between SMIv2 and YANG. The Working Group will determine which constructs (e.g., conformance statements) are not relevant for translation from SMIv2 to YANG. YANG is also permitted to introduce constructs that cannot be expressed in SMIv2. However, all basic types that can be represented in SMIv2 must be expressible in YANG. Initial deliverables are below. The working group may choose to combine multiple deliverables into a single document where deemed appropriate. 1. An architecture document explaining the relationship between YANG and its inputs and outputs. (informational) 2. The YANG data modeling language and semantics (proposed standard) 3. Mapping rules of YANG to XML instance data in NETCONF (proposed standard) 4. YIN, a semantically equivalent fully reversible mapping to an XML-based syntax for YANG. YIN is simply the data model in an XML syntax that can be manipulated using existing XML tools (e.g., XSLT) (proposed standard) 5. Mapping rules of YANG to DSDL data modeling framework (ISO/IEC 19757), including annotations for DSDL to preserve top-level semantics during translation (proposed standard). 6. A standard type library for use by YANG (proposed standard) Goals and Milestones: Jun 2008 - All _individual_ drafts available that will be used as input into the WG documents (draft-bjorklund-yang, architecture draft, YIN draft, YANG standard library draft, DSDL mapping rules draft) Aug 2008 - Initial set of WG drafts: architecture, YANG, YIN, YANG standard library, DSDL mapping rules (if there is one/more individual draft), based on WG decisions in Dublin Sep 2008 - Initial DSDL mapping rules document Oct 2008 - 01 of YANG, DSDL, architecture, YIN, and standard library draft. If split out, -00 of on-the-wire XML draft. Feb 2009 - WGLC for architecture doc Mar 2009 - Submit the architecture doc to the IESG for publication as an Informational RFC Aug 2009 - WGLC for YANG, YIN, XML on-the-wire (if split out), YANG standard library, DSDL mapping rules Sep 2009 - Submit YANG, YIN, XML on-the-wire (if split out), YANG standard library, DSDL mapping rules to the IESG for publication as a Proposed Standard _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod From netmod-bounces@ietf.org Tue Apr 29 23:40:03 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 687483A69E3; Tue, 29 Apr 2008 23:40:03 -0700 (PDT) X-Original-To: netmod@core3.amsl.com Delivered-To: netmod@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B1F83A6A54 for ; Tue, 29 Apr 2008 22:05:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.534 X-Spam-Level: X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNrFFZsemAnT for ; Tue, 29 Apr 2008 22:05:49 -0700 (PDT) Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by core3.amsl.com (Postfix) with ESMTP id A497F3A6A6F for ; Tue, 29 Apr 2008 22:05:48 -0700 (PDT) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA03.westchester.pa.mail.comcast.net with comcast id Kh2z1Z0010mv7h05300F00; Wed, 30 Apr 2008 05:03:57 +0000 Received: from Harrington73653 ([24.128.66.199]) by OMTA11.westchester.pa.mail.comcast.net with comcast id Kh5q1Z00D4HwxpC3X00000; Wed, 30 Apr 2008 05:05:51 +0000 X-Authority-Analysis: v=1.0 c=1 a=rqiit6U69JwA:10 a=G2oZPUsET2AA:10 a=48vgC7mUAAAA:8 a=e_iVOOC0sT6YZ8mWE9MA:9 a=LL-lspTwcimJ8k6j1y4A:7 a=OVb3bCGzcWEb54c5TzUVP5KZMB4A:4 a=si9q_4b84H0A:10 a=hPjdaMEvmhQA:10 a=lZB815dzVvQA:10 a=f7GxY0FH8QIA:10 a=4dyfk4FV-b8A:10 a=peF9eE_zjQwA:10 a=AcZQ66N1Z8sA:10 From: "David Harrington" To: References: <20080430024340.117783A6D95@core3.amsl.com> Date: Wed, 30 Apr 2008 01:05:50 -0400 Message-ID: <011401c8aa7f$dc10dbc0$0600a8c0@china.huawei.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20080430024340.117783A6D95@core3.amsl.com> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: AciqbA2DP8IT82S2RqyV5cVE/k94xAAEqxpg X-Mailman-Approved-At: Tue, 29 Apr 2008 23:40:02 -0700 Subject: Re: [netmod] WG Action: NETCONF Data Modeling Language (netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org Congratulations on finally getting a working group. David Harrington dbharrington@comcast.net ietfdbh@comcast.net dharrington@huawei.com > -----Original Message----- > From: ietf-announce-bounces@ietf.org > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG > Sent: Tuesday, April 29, 2008 10:44 PM > To: IETF Announcement list > Cc: dbharrington@comcast.net; david.partain@ericsson.com; > netmod@ietf.org > Subject: WG Action: NETCONF Data Modeling Language (netmod) > > A new IETF working group has been formed in the Operations > and Management > Area. For additional information, please contact the Area > Directors or > the WG Chairs. > > NETCONF Data Modeling Language (netmod) > --------------------------------------------- > > Chair(s): > > David Harrington > David Partain > > Operations and Management Area Director(s): > > Dan Romascanu > Ronald Bonica >rbonica@juniper.net> > > Operations and Management Area Advisor: > Dan Romascanu > > Mailing Lists: > > General Discussion: netmod@ietf.org > To Subscribe: netmod-request@ietf.org > In Body: in msg body: subscribe > Archive: http://www.ietf.org/mail-archive/web/netmod/ > > Description: > > The NETCONF Working Group has completed a base protocol to be > used for configuration management. However, the NETCONF protocol > does not include a standard content layer. The specifications do > not include a modeling language or accompanying rules that can be > used to model the management information that is to be configured > using NETCONF. This has resulted in inconsistent syntax and > interoperability problems. The purpose of NETMOD is to support > the ongoing development of IETF and vendor-defined data models > for NETCONF. > > NETMOD's requirements are drawn from the RCDML requirements draft > (draft-presuhn-rcdml) and documents referenced therein. > > The WG will define a "human-friendly" modeling language defining > the semantics of operational data, configuration data, > notifications, and operations. This language will focus on > readability and ease of use. This language must be able to serve > as the normative description of NETCONF data models. The WG will > use YANG (draft-bjorklund-yang) as its starting point for this > language. > > Language abstractions that facilitate model extensibility and > reuse have been identified as a work area and will be considered > as a work item or may be integrated into the YANG document based > on WG consensus. > > The WG will define a canonical mapping of this language to > NETCONF XML instance documents, the on-the-wire format of > YANG-defined XML content. Only data models defined in YANG will > have to adhere to this on-the-wire format. > > In order to leverage existing XML tools for validating NETCONF > data in various contexts and also facilitate exchange of data > models and schemas with other IETF working groups, the WG will > define standard mapping rules from YANG to the DSDL data modeling > framework (ISO/IEC 19757) with additional annotations to preserve > semantics. > > The initial YANG mapping rules specifications are expressly > defined for > NETCONF modeling. However, there may be future areas of > applicability beyond NETCONF, and the WG must provide suitable > language extensibility mechanisms to allow for such future work. > The NETMOD WG will only address modeling NETCONF devices and the > language extensibility mechanisms. Any application of YANG to > other protocols is future work. > > The WG will consult with the NETCONF WG to ensure that NETMOD's > decision do not conflict with planned work in NETCONF (e.g., > locking, notifications). > > While it is desirable to provide a migration path from existing > MIB modules to YANG data models (modules), it is not a > requirement to provide full compatibility between SMIv2 and YANG. > The Working Group will determine which constructs (e.g., conformance > statements) are not relevant for translation from SMIv2 to > YANG. YANG is > also permitted to introduce constructs that cannot be > expressed in SMIv2. > However, all basic types that can be represented in SMIv2 must be > expressible in YANG. > > Initial deliverables are below. The working group may choose to > combine multiple deliverables into a single document where deemed > appropriate. > > 1. An architecture document explaining the relationship > between YANG and its inputs and outputs. (informational) > > 2. The YANG data modeling language and semantics (proposed > standard) > > 3. Mapping rules of YANG to XML instance data in NETCONF > (proposed standard) > > 4. YIN, a semantically equivalent fully reversible mapping to an > XML-based syntax for YANG. YIN is simply the data model in > an XML syntax > that can be manipulated using existing XML tools (e.g., XSLT) > (proposed > standard) > > 5. Mapping rules of YANG to DSDL data modeling framework (ISO/IEC > 19757), including annotations for DSDL to preserve top-level > semantics during translation (proposed standard). > > 6. A standard type library for use by YANG (proposed standard) > > Goals and Milestones: > > Jun 2008 - All _individual_ drafts available that will be used as > input into the WG documents (draft-bjorklund-yang, architecture > draft, YIN draft, YANG standard library draft, DSDL mapping rules > draft) > > Aug 2008 - Initial set of WG drafts: architecture, YANG, YIN, > YANG standard library, DSDL mapping rules (if there is one/more > individual draft), based on WG decisions in Dublin > > Sep 2008 - Initial DSDL mapping rules document > > Oct 2008 - 01 of YANG, DSDL, architecture, YIN, and standard > library draft. If split out, -00 of on-the-wire XML draft. > > Feb 2009 - WGLC for architecture doc > > Mar 2009 - Submit the architecture doc to the IESG for > publication as an Informational RFC > > Aug 2009 - WGLC for YANG, YIN, XML on-the-wire (if split out), > YANG standard library, DSDL mapping rules > > Sep 2009 - Submit YANG, YIN, XML on-the-wire (if split out), YANG > standard library, DSDL mapping rules to the IESG for publication as a > Proposed Standard > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce > _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod From netmod-bounces@ietf.org Tue Apr 29 23:40:03 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 733D83A6BCA; Tue, 29 Apr 2008 23:40:03 -0700 (PDT) X-Original-To: netmod@core3.amsl.com Delivered-To: netmod@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5F433A6AED for ; Tue, 29 Apr 2008 22:13:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pkb-HldG2LCX for ; Tue, 29 Apr 2008 22:13:02 -0700 (PDT) Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by core3.amsl.com (Postfix) with ESMTP id 725943A691D for ; Tue, 29 Apr 2008 22:13:00 -0700 (PDT) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA05.westchester.pa.mail.comcast.net with comcast id Kh5M1Z0010EZKEL5500m00; Wed, 30 Apr 2008 05:12:44 +0000 Received: from Harrington73653 ([24.128.66.199]) by OMTA01.westchester.pa.mail.comcast.net with comcast id KhD21Z0074HwxpC3M00000; Wed, 30 Apr 2008 05:13:03 +0000 X-Authority-Analysis: v=1.0 c=1 a=AH3vrOh2S_8A:10 a=_s51KALZ46YA:10 a=48vgC7mUAAAA:8 a=e_iVOOC0sT6YZ8mWE9MA:9 a=LL-lspTwcimJ8k6j1y4A:7 a=ysMzmY2dgxJc9f1MpVqIAJ8J_mIA:4 a=si9q_4b84H0A:10 a=hPjdaMEvmhQA:10 a=lZB815dzVvQA:10 a=f7GxY0FH8QIA:10 a=4dyfk4FV-b8A:10 a=peF9eE_zjQwA:10 a=50e4U0PicR4A:10 From: "David B Harrington" To: Date: Wed, 30 Apr 2008 01:13:02 -0400 Message-ID: <011701c8aa80$dda93990$0600a8c0@china.huawei.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: AciqbA2DP8IT82S2RqyV5cVE/k94xAAEqxpgAACERjA= X-Mailman-Approved-At: Tue, 29 Apr 2008 23:40:02 -0700 Subject: [netmod] WG Action: NETCONF Data Modeling Language (netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org Hi Congratulations on finally getting a working group. David Harrington dbharrington@comcast.net ietfdbh@comcast.net dharrington@huawei.com > -----Original Message----- > From: ietf-announce-bounces@ietf.org > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG > Sent: Tuesday, April 29, 2008 10:44 PM > To: IETF Announcement list > Cc: dbharrington@comcast.net; david.partain@ericsson.com; > netmod@ietf.org > Subject: WG Action: NETCONF Data Modeling Language (netmod) > > A new IETF working group has been formed in the Operations > and Management > Area. For additional information, please contact the Area > Directors or > the WG Chairs. > > NETCONF Data Modeling Language (netmod) > --------------------------------------------- > > Chair(s): > > David Harrington > David Partain > > Operations and Management Area Director(s): > > Dan Romascanu > Ronald Bonica >rbonica@juniper.net> > > Operations and Management Area Advisor: > Dan Romascanu > > Mailing Lists: > > General Discussion: netmod@ietf.org > To Subscribe: netmod-request@ietf.org > In Body: in msg body: subscribe > Archive: http://www.ietf.org/mail-archive/web/netmod/ > > Description: > > The NETCONF Working Group has completed a base protocol to be > used for configuration management. However, the NETCONF protocol > does not include a standard content layer. The specifications do > not include a modeling language or accompanying rules that can be > used to model the management information that is to be configured > using NETCONF. This has resulted in inconsistent syntax and > interoperability problems. The purpose of NETMOD is to support > the ongoing development of IETF and vendor-defined data models > for NETCONF. > > NETMOD's requirements are drawn from the RCDML requirements draft > (draft-presuhn-rcdml) and documents referenced therein. > > The WG will define a "human-friendly" modeling language defining > the semantics of operational data, configuration data, > notifications, and operations. This language will focus on > readability and ease of use. This language must be able to serve > as the normative description of NETCONF data models. The WG will > use YANG (draft-bjorklund-yang) as its starting point for this > language. > > Language abstractions that facilitate model extensibility and > reuse have been identified as a work area and will be considered > as a work item or may be integrated into the YANG document based > on WG consensus. > > The WG will define a canonical mapping of this language to > NETCONF XML instance documents, the on-the-wire format of > YANG-defined XML content. Only data models defined in YANG will > have to adhere to this on-the-wire format. > > In order to leverage existing XML tools for validating NETCONF > data in various contexts and also facilitate exchange of data > models and schemas with other IETF working groups, the WG will > define standard mapping rules from YANG to the DSDL data modeling > framework (ISO/IEC 19757) with additional annotations to preserve > semantics. > > The initial YANG mapping rules specifications are expressly > defined for > NETCONF modeling. However, there may be future areas of > applicability beyond NETCONF, and the WG must provide suitable > language extensibility mechanisms to allow for such future work. > The NETMOD WG will only address modeling NETCONF devices and the > language extensibility mechanisms. Any application of YANG to > other protocols is future work. > > The WG will consult with the NETCONF WG to ensure that NETMOD's > decision do not conflict with planned work in NETCONF (e.g., > locking, notifications). > > While it is desirable to provide a migration path from existing > MIB modules to YANG data models (modules), it is not a > requirement to provide full compatibility between SMIv2 and YANG. > The Working Group will determine which constructs (e.g., conformance > statements) are not relevant for translation from SMIv2 to > YANG. YANG is > also permitted to introduce constructs that cannot be > expressed in SMIv2. > However, all basic types that can be represented in SMIv2 must be > expressible in YANG. > > Initial deliverables are below. The working group may choose to > combine multiple deliverables into a single document where deemed > appropriate. > > 1. An architecture document explaining the relationship > between YANG and its inputs and outputs. (informational) > > 2. The YANG data modeling language and semantics (proposed > standard) > > 3. Mapping rules of YANG to XML instance data in NETCONF > (proposed standard) > > 4. YIN, a semantically equivalent fully reversible mapping to an > XML-based syntax for YANG. YIN is simply the data model in > an XML syntax > that can be manipulated using existing XML tools (e.g., XSLT) > (proposed > standard) > > 5. Mapping rules of YANG to DSDL data modeling framework (ISO/IEC > 19757), including annotations for DSDL to preserve top-level > semantics during translation (proposed standard). > > 6. A standard type library for use by YANG (proposed standard) > > Goals and Milestones: > > Jun 2008 - All _individual_ drafts available that will be used as > input into the WG documents (draft-bjorklund-yang, architecture > draft, YIN draft, YANG standard library draft, DSDL mapping rules > draft) > > Aug 2008 - Initial set of WG drafts: architecture, YANG, YIN, > YANG standard library, DSDL mapping rules (if there is one/more > individual draft), based on WG decisions in Dublin > > Sep 2008 - Initial DSDL mapping rules document > > Oct 2008 - 01 of YANG, DSDL, architecture, YIN, and standard > library draft. If split out, -00 of on-the-wire XML draft. > > Feb 2009 - WGLC for architecture doc > > Mar 2009 - Submit the architecture doc to the IESG for > publication as an Informational RFC > > Aug 2009 - WGLC for YANG, YIN, XML on-the-wire (if split out), > YANG standard library, DSDL mapping rules > > Sep 2009 - Submit YANG, YIN, XML on-the-wire (if split out), YANG > standard library, DSDL mapping rules to the IESG for publication as a > Proposed Standard > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce > _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod From netmod-bounces@ietf.org Tue Apr 29 23:40:03 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9104528C20D; Tue, 29 Apr 2008 23:40:03 -0700 (PDT) X-Original-To: netmod@core3.amsl.com Delivered-To: netmod@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 257D93A69E3; Tue, 29 Apr 2008 23:33:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.584 X-Spam-Level: X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEbJZRYXWbGH; Tue, 29 Apr 2008 23:33:50 -0700 (PDT) Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 836503A685A; Tue, 29 Apr 2008 23:33:50 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.25,726,1199682000"; d="scan'208";a="124194023" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 30 Apr 2008 02:33:52 -0400 X-IronPort-AV: E=Sophos;i="4.25,726,1199682000"; d="scan'208";a="195252973" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Apr 2008 02:33:51 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 30 Apr 2008 08:33:49 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Action: NETCONF Data Modeling Language (netmod) Thread-Index: AciqbCHbEpEMLNvIQ4ab2dxmTV6NJQAHlgAg From: "Romascanu, Dan (Dan)" To: X-Mailman-Approved-At: Tue, 29 Apr 2008 23:40:02 -0700 Cc: NETCONF Goes On , netconf@ietf.org, ops-area@ietf.org Subject: [netmod] FW: WG Action: NETCONF Data Modeling Language (netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org Please see below the announcement of the formation of the NETMOD Working Group. Congratulations and thanks to all the folks who worked hard and contributed to the formation of the Working Group. David Harrington and David Partain are the co-chairs of the WG, let us congratulate them and help them in their ambitious task. This team and this community has now the challenge of proving that the development of a data modeling language for management is possible in the IETF and that lessons of the past were well learned for the benefit of the network operators and of the devices and management applications developers. We have created the netmod@ietf.org list. Please subscribe to this list and move all discussions from the ngo and yang lists that fall under the scope of netmod to the new list. I suggest that we keep ngo@ietf.org for future not-chartered NETCONF discussions and that we shut down the yang list in the next few weeks. Regards, Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: Wednesday, April 30, 2008 5:44 AM To: IETF Announcement list Cc: dbharrington@comcast.net; david.partain@ericsson.com; netmod@ietf.org Subject: WG Action: NETCONF Data Modeling Language (netmod) A new IETF working group has been formed in the Operations and Management Area. For additional information, please contact the Area Directors or the WG Chairs. NETCONF Data Modeling Language (netmod) --------------------------------------------- Chair(s): David Harrington David Partain Operations and Management Area Director(s): Dan Romascanu Ronald Bonica >rbonica@juniper.net> Operations and Management Area Advisor: Dan Romascanu Mailing Lists: General Discussion: netmod@ietf.org To Subscribe: netmod-request@ietf.org In Body: in msg body: subscribe Archive: http://www.ietf.org/mail-archive/web/netmod/ Description: The NETCONF Working Group has completed a base protocol to be used for configuration management. However, the NETCONF protocol does not include a standard content layer. The specifications do not include a modeling language or accompanying rules that can be used to model the management information that is to be configured using NETCONF. This has resulted in inconsistent syntax and interoperability problems. The purpose of NETMOD is to support the ongoing development of IETF and vendor-defined data models for NETCONF. NETMOD's requirements are drawn from the RCDML requirements draft (draft-presuhn-rcdml) and documents referenced therein. The WG will define a "human-friendly" modeling language defining the semantics of operational data, configuration data, notifications, and operations. This language will focus on readability and ease of use. This language must be able to serve as the normative description of NETCONF data models. The WG will use YANG (draft-bjorklund-yang) as its starting point for this language. Language abstractions that facilitate model extensibility and reuse have been identified as a work area and will be considered as a work item or may be integrated into the YANG document based on WG consensus. The WG will define a canonical mapping of this language to NETCONF XML instance documents, the on-the-wire format of YANG-defined XML content. Only data models defined in YANG will have to adhere to this on-the-wire format. In order to leverage existing XML tools for validating NETCONF data in various contexts and also facilitate exchange of data models and schemas with other IETF working groups, the WG will define standard mapping rules from YANG to the DSDL data modeling framework (ISO/IEC 19757) with additional annotations to preserve semantics. The initial YANG mapping rules specifications are expressly defined for NETCONF modeling. However, there may be future areas of applicability beyond NETCONF, and the WG must provide suitable language extensibility mechanisms to allow for such future work. The NETMOD WG will only address modeling NETCONF devices and the language extensibility mechanisms. Any application of YANG to other protocols is future work. The WG will consult with the NETCONF WG to ensure that NETMOD's decision do not conflict with planned work in NETCONF (e.g., locking, notifications). While it is desirable to provide a migration path from existing MIB modules to YANG data models (modules), it is not a requirement to provide full compatibility between SMIv2 and YANG. The Working Group will determine which constructs (e.g., conformance statements) are not relevant for translation from SMIv2 to YANG. YANG is also permitted to introduce constructs that cannot be expressed in SMIv2. However, all basic types that can be represented in SMIv2 must be expressible in YANG. Initial deliverables are below. The working group may choose to combine multiple deliverables into a single document where deemed appropriate. 1. An architecture document explaining the relationship between YANG and its inputs and outputs. (informational) 2. The YANG data modeling language and semantics (proposed standard) 3. Mapping rules of YANG to XML instance data in NETCONF (proposed standard) 4. YIN, a semantically equivalent fully reversible mapping to an XML-based syntax for YANG. YIN is simply the data model in an XML syntax that can be manipulated using existing XML tools (e.g., XSLT) (proposed standard) 5. Mapping rules of YANG to DSDL data modeling framework (ISO/IEC 19757), including annotations for DSDL to preserve top-level semantics during translation (proposed standard). 6. A standard type library for use by YANG (proposed standard) Goals and Milestones: Jun 2008 - All _individual_ drafts available that will be used as input into the WG documents (draft-bjorklund-yang, architecture draft, YIN draft, YANG standard library draft, DSDL mapping rules draft) Aug 2008 - Initial set of WG drafts: architecture, YANG, YIN, YANG standard library, DSDL mapping rules (if there is one/more individual draft), based on WG decisions in Dublin Sep 2008 - Initial DSDL mapping rules document Oct 2008 - 01 of YANG, DSDL, architecture, YIN, and standard library draft. If split out, -00 of on-the-wire XML draft. Feb 2009 - WGLC for architecture doc Mar 2009 - Submit the architecture doc to the IESG for publication as an Informational RFC Aug 2009 - WGLC for YANG, YIN, XML on-the-wire (if split out), YANG standard library, DSDL mapping rules Sep 2009 - Submit YANG, YIN, XML on-the-wire (if split out), YANG standard library, DSDL mapping rules to the IESG for publication as a Proposed Standard _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod From netmod-bounces@ietf.org Wed Apr 30 08:47:32 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E77C28C3F5; Wed, 30 Apr 2008 08:47:32 -0700 (PDT) X-Original-To: netmod@core3.amsl.com Delivered-To: netmod@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B37A3A6C41 for ; Wed, 30 Apr 2008 08:35:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.199 X-Spam-Level: X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEGlcWVDAdRZ for ; Wed, 30 Apr 2008 08:35:35 -0700 (PDT) Received: from smtp117.sbc.mail.sp1.yahoo.com (smtp117.sbc.mail.sp1.yahoo.com [69.147.64.90]) by core3.amsl.com (Postfix) with SMTP id 587DE3A698A for ; Wed, 30 Apr 2008 08:35:34 -0700 (PDT) Received: (qmail 12500 invoked from network); 30 Apr 2008 15:35:37 -0000 Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.126.241.42 with plain) by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 30 Apr 2008 15:35:35 -0000 X-YMail-OSG: GnDIEqcVM1mTt0aFmfW8woMc69usHmPYsW5u.uxQizuofQQIlHBYmh.VpLPdWCza.EcQ0rpO2hCEkmgp1YkmfJAhguTGWptggcKmAKKV2WFFNCtABKdzJANa3peEgl4Swuc- X-Yahoo-Newman-Property: ymail-3 Message-ID: <481891C6.5090303@andybierman.com> Date: Wed, 30 Apr 2008 08:35:34 -0700 From: Andy Bierman User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: In-Reply-To: X-Mailman-Approved-At: Wed, 30 Apr 2008 08:47:30 -0700 Cc: NETCONF Goes On , netmod@ietf.org Subject: Re: [netmod] [Netconf] FW: WG Action: NETCONF Data Modeling Language (netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org Romascanu, Dan (Dan) wrote: > Please see below the announcement of the formation of the NETMOD Working > Group. Congratulations and thanks to all the folks who worked hard and > contributed to the formation of the Working Group. David Harrington and > David Partain are the co-chairs of the WG, let us congratulate them and > help them in their ambitious task. This team and this community has now > the challenge of proving that the development of a data modeling > language for management is possible in the IETF and that lessons of the > past were well learned for the benefit of the network operators and of > the devices and management applications developers. > > We have created the netmod@ietf.org list. Please subscribe to this list > and move all discussions from the ngo and yang lists that fall under the > scope of netmod to the new list. I suggest that we keep ngo@ietf.org for > future not-chartered NETCONF discussions and that we shut down the yang > list in the next few weeks. > Would it be possible to auto-subscribe the members of the NGO list to the NETMOD list? I prefer to have both the YANG and NGO lists go away. Discussions on unchartered work have mostly been about NETMOD. Now that the NETMOD WG exists, there will not be enough email on NGO to warrant a separate list. > Regards, > > Dan > Andy _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod From netmod-bounces@ietf.org Wed Apr 30 08:48:52 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C813828C3D4; Wed, 30 Apr 2008 08:48:52 -0700 (PDT) X-Original-To: netmod@core3.amsl.com Delivered-To: netmod@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2B9C28C3CE; Wed, 30 Apr 2008 08:48:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.404 X-Spam-Level: X-Spam-Status: No, score=-2.404 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08quGHSBSzmz; Wed, 30 Apr 2008 08:48:47 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 930BD28C3FA; Wed, 30 Apr 2008 08:47:42 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.25,729,1199682000"; d="scan'208";a="105330843" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Apr 2008 11:47:43 -0400 X-IronPort-AV: E=Sophos;i="4.25,729,1199682000"; d="scan'208";a="195473466" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Apr 2008 11:47:42 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 30 Apr 2008 17:47:01 +0200 Message-ID: In-reply-to: <481891C6.5090303@andybierman.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Netconf] FW: WG Action: NETCONF Data Modeling Language (netmod) Thread-Index: Aciq198+RdXkypwqTWuFZzAwWkNYhAAAKivg References: <481891C6.5090303@andybierman.com> From: "Romascanu, Dan (Dan)" To: "Andy Bierman" Cc: NETCONF Goes On , netmod@ietf.org Subject: Re: [netmod] [Netconf] FW: WG Action: NETCONF Data Modeling Language (netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org > -----Original Message----- > From: Andy Bierman [mailto:ietf@andybierman.com] > > > > Would it be possible to auto-subscribe the members of the NGO > list to the NETMOD list? Well, people started to subscribe five minutes after the announcement was out. I guess that by this time one third of the ngo subscribers may already be on netmod. I prefer people subscribing individually, it's the IETF way if you want especially taking into account that ngo was not only about netmod. > > I prefer to have both the YANG and NGO lists go away. > Discussions on unchartered work have mostly been about NETMOD. > Now that the NETMOD WG exists, there will not be enough email > on NGO to warrant a separate list. I agree about YANG as YANG is now a netmod component. I am somehow hesitating about ngo, as this was historically used for non chartered NETCONF issues, and now it can be used also for not chartered NETMOD issues. This was kind of successful in letting people to focus on chartered items if they want to. However, if more people insist on shutting down ngo as well I will not fight this fiercely. Dan > > > Regards, > > > > Dan > > > > Andy > > > > _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod From netmod-bounces@ietf.org Wed Apr 30 10:58:26 2008 Return-Path: X-Original-To: netmod-archive@ietf.org Delivered-To: ietfarch-netmod-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB5043A6892; Wed, 30 Apr 2008 10:58:26 -0700 (PDT) X-Original-To: netmod@core3.amsl.com Delivered-To: netmod@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAD8F3A6C90 for ; Wed, 30 Apr 2008 10:52:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.545 X-Spam-Level: X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rbof9JmRCnf9 for ; Wed, 30 Apr 2008 10:52:02 -0700 (PDT) Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by core3.amsl.com (Postfix) with ESMTP id 927623A6B91 for ; Wed, 30 Apr 2008 10:52:02 -0700 (PDT) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA02.westchester.pa.mail.comcast.net with comcast id KreT1Z0020mv7h0520DC00; Wed, 30 Apr 2008 17:51:42 +0000 Received: from Harrington73653 ([24.128.66.199]) by OMTA11.westchester.pa.mail.comcast.net with comcast id Kts41Z0084HwxpC3X00000; Wed, 30 Apr 2008 17:52:05 +0000 X-Authority-Analysis: v=1.0 c=1 a=UfEG-boNnzIA:10 a=NOy0HNGcBHsA:10 a=48vgC7mUAAAA:8 a=u7gjMENukCDBUx-m9k4A:9 a=wL6e8l09fnSt89i3lTAA:7 a=irN9lasf_7ELn00K5C3r7158xlMA:4 a=lZB815dzVvQA:10 a=ucw2XimmUOMA:10 a=50e4U0PicR4A:10 From: "David Harrington" To: "'Romascanu, Dan \(Dan\)'" , "'Andy Bierman'" References: <481891C6.5090303@andybierman.com> Date: Wed, 30 Apr 2008 13:52:04 -0400 Message-ID: <018001c8aaea$e6b8d080$0600a8c0@china.huawei.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: Aciq198+RdXkypwqTWuFZzAwWkNYhAAAKivgAASUhSA= X-Mailman-Approved-At: Wed, 30 Apr 2008 10:58:21 -0700 Cc: 'NETCONF Goes On' , netmod@ietf.org Subject: Re: [netmod] [NGO] [Netconf] FW: WG Action: NETCONF Data Modeling Language(netmod) X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: netmod-bounces@ietf.org Errors-To: netmod-bounces@ietf.org Hi, There are still unchertered items to discuss, so I would prefer to keep NGO active. dbh > -----Original Message----- > From: ngo-bounces@ietf.org [mailto:ngo-bounces@ietf.org] On > Behalf Of Romascanu, Dan (Dan) > Sent: Wednesday, April 30, 2008 11:47 AM > To: Andy Bierman > Cc: NETCONF Goes On; netmod@ietf.org > Subject: Re: [NGO] [Netconf] FW: WG Action: NETCONF Data > Modeling Language(netmod) > > > > > -----Original Message----- > > From: Andy Bierman [mailto:ietf@andybierman.com] > > > > > > > > Would it be possible to auto-subscribe the members of the NGO > > list to the NETMOD list? > > Well, people started to subscribe five minutes after the announcement > was out. I guess that by this time one third of the ngo > subscribers may > already be on netmod. I prefer people subscribing > individually, it's the > IETF way if you want especially taking into account that ngo was not > only about netmod. > > > > > I prefer to have both the YANG and NGO lists go away. > > Discussions on unchartered work have mostly been about NETMOD. > > Now that the NETMOD WG exists, there will not be enough email > > on NGO to warrant a separate list. > > I agree about YANG as YANG is now a netmod component. I am somehow > hesitating about ngo, as this was historically used for non chartered > NETCONF issues, and now it can be used also for not chartered NETMOD > issues. This was kind of successful in letting people to focus on > chartered items if they want to. > > However, if more people insist on shutting down ngo as well I will not > fight this fiercely. > > Dan > > > > > > Regards, > > > > > > Dan > > > > > > > Andy > > > > > > > > > _______________________________________________ > NGO mailing list > NGO@ietf.org > https://www.ietf.org/mailman/listinfo/ngo > _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod