[YANG] FW: Request for a YANG BOF at IETF70, Vancouver
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 24 October 2007 13:26 UTC
Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkgFI-0002Cx-8T; Wed, 24 Oct 2007 09:26:04 -0400
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1IkgFE-0002CI-R9 for yang-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 09:26:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkgF9-0002Ay-Rz for yang@ietf.org; Wed, 24 Oct 2007 09:25:55 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkgEg-0005QY-0L for yang@ietf.org; Wed, 24 Oct 2007 09:25:55 -0400
X-IronPort-AV: E=Sophos;i="4.21,324,1188792000"; d="txt'?scan'208";a="73077032"
Received: from 14.140.8.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-outbound.avaya.com with ESMTP; 24 Oct 2007 09:25:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C81641.4E8DA8C5"
Date: Wed, 24 Oct 2007 15:25:08 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A045268CD@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Request for a YANG BOF at IETF70, Vancouver
Thread-Index: AcgEDX5PuyiB6YLlTZGFtYr1GbTatgSM2gqA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: yang@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0d2c648c04c631088df6dc3c3125d9df
Subject: [YANG] FW: Request for a YANG BOF at IETF70, Vancouver
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org
-----Original Message----- From: David Partain [mailto:david.partain@ericsson.com] Sent: Monday, October 01, 2007 12:28 PM To: Romascanu, Dan (Dan); Ron Bonica Subject: Request for a YANG BOF at IETF70, Vancouver BOF proposal - YANG modeling Language for NETCONF IETF 70, Vancouver Chairs: David Partain and TBD The NETCONF Working Group has completed a base protocol to be used for configuration management. However, the NETCONF protocol needs a standard content layer. The specifications do not include a modeling language or accompanying rules for how to model the management information that is to be configured using NETCONF. A data modeling framework is needed which supports ongoing development of IETF and vendor-defined modules, within an integrated and seamless conceptual configuration database. This BOF proposes the YANG modeling framework as the standardized modeling framework for NETCONF. Existing languages have been analyzed and deemed insufficient. Input Document: draft-bjorklund-yang-00.txt (not yet published, snapshot attached) Send comments on this BoF proposal to the YANG list list: mailto:yang@ietf.org (tentative - needs to be set up, can be on NGO list until then) Tentative agenda: 1. YANG Overview - Features of the language and examples 2. YANG Details - go into the nitty gritty 3. Q&A 4. Charter discussion and next steps Proposed charter for the YANG Working Group: The Working Group will define a modeling language and associated modeling rules to be used when defining management information to be used specifically with NETCONF. The Working Group is NOT chartered to define a protocol-independent modeling language. The working group will use YANG as its starting point. All Working Group documents will be standards track. The Working Group will produce document(s) covering the following. 1. The language and rules for the new language ("YANG"). 2. A one-to-one reversible translated format ("YIN") to/from XML without loss of semantic data information. 3. The rules for translation into XSD but not necessarily back into the native format. 4. Derived types for YANG. Constraints on the Working Group: 1. The language will have a C-like syntax. 2. The language will not be backwards-compatible with SMIv2. 3. The language cannot be used to model generic XML. 4. Conformance issues will be handled later. Milestones: (ALL of these dates are very loose at this point) 1. Feb 2008: Working Group chartered, -00 draft published based upon draft-bjorklund-yang-00.txt 2. Early April 2008: -01 of base spec after first IETF 3. Late Apr 2008: Interim meeting 4. Jun 2008: -02 of base specification in advance of July IETF, -00 of mapping to XML and -00 of mapping to XSD etc... Finishing spring/summer 2009?
_______________________________________________ YANG mailing list YANG@ietf.org https://www1.ietf.org/mailman/listinfo/yang
- [YANG] FW: Request for a YANG BOF at IETF70, Vanc… Romascanu, Dan (Dan)
- RE: [YANG] FW: Request for a YANG BOF at IETF70, … Romascanu, Dan (Dan)