[NGO] FW: WG Action: NETCONF Data Modeling Language (netmod)

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 30 April 2008 06:33 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ngo-archive@optimus.ietf.org
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C6AC3A6A3F; Tue, 29 Apr 2008 23:33:54 -0700 (PDT)
X-Original-To: ngo@core3.amsl.com
Delivered-To: ngo@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: <EDC652A26FB23C4EB6384A4584434A04B7B026@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: WG Action: NETCONF Data Modeling Language (netmod)
Thread-Index: AciqbCHbEpEMLNvIQ4ab2dxmTV6NJQAHlgAg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: netmod@ietf.org
Cc: NETCONF Goes On <ngo@ietf.org>, netconf@ietf.org, ops-area@ietf.org
Subject: [NGO] FW: WG Action: NETCONF Data Modeling Language (netmod)
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-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 <dbharrington@comcast.net> David Partain
<david.partain@ericsson.com>

Operations and Management Area Director(s):

Dan Romascanu <dromasca@avaya.com>
Ronald Bonica >rbonica@juniper.net>

Operations and Management Area Advisor:
Dan Romascanu <dromasca@avaya.com>

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
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo