[NGO] BOF Proposal: Comparing Approaches to NETCONF Modeling (CANMOD)
David Partain <david.partain@ericsson.com> Mon, 28 January 2008 15:20 UTC
Return-path: <ngo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJVmY-0003AT-QN; Mon, 28 Jan 2008 10:20:22 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1JJVmX-00037i-SZ for ngo-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 10:20:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJVmX-000370-IB for ngo@ietf.org; Mon, 28 Jan 2008 10:20:21 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJVmV-0001eK-Gg for ngo@ietf.org; Mon, 28 Jan 2008 10:20:21 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id D749D20C2D for <ngo@ietf.org>; Mon, 28 Jan 2008 16:20:18 +0100 (CET)
X-AuditID: c1b4fb3c-aaaedbb0000007e0-a3-479df2b20c4a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id BEC98209AD for <ngo@ietf.org>; Mon, 28 Jan 2008 16:20:18 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jan 2008 16:20:18 +0100
Received: from pcp112127pcs.ki.sw.ericsson.se ([147.214.32.125]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jan 2008 16:20:18 +0100
From: David Partain <david.partain@ericsson.com>
Organization: Ericsson AB
To: ngo@ietf.org
Date: Mon, 28 Jan 2008 16:20:29 +0100
User-Agent: KMail/1.9.8
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200801281620.29527.david.partain@ericsson.com>
X-OriginalArrivalTime: 28 Jan 2008 15:20:18.0322 (UTC) FILETIME=[4A4D4720:01C861C1]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Subject: [NGO] BOF Proposal: Comparing Approaches to NETCONF Modeling (CANMOD)
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Errors-To: ngo-bounces@ietf.org
Hi All, For your information, I've submitted the following proposal for a BOF during the upcoming IETF in March. Cheers, David ------------------------------------------------------------------------------------------------------------------ BOF proposal - Comparing Approaches to NETCONF Modeling (CANMOD) BOF length: 2.5 hours Chairs: 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 current specifications do not include a modeling language or accompanying rules for how to model the management information that is to be configured and monitor 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 datastore and supporting infrastructure. The goal of the BOF is to determine if there is sufficient interest and cohesion to form a working group to standardize a data modeling language for NETCONF. If so, the target is for the BOF to recommend one of the proposals as the starting point as a modeling language for NETCONF. A design team collected, clarified and categorized requirements for a data modeling language from a broad group of IETF participants. Many of these requirements had broad agreement. All of these requirements, and a collection of use-cases motivating the requirements where broad agreement was not reached, are documented in an Internet Draft. The design team will also prepare an example annotated instance document which incorporates many of the requirements. All BOF participants are expected to read this document and to understand the basic concepts of the NETCONF protocol. In order to ensure productive discussion, the BOF chairs will only grant agenda time to discuss these concrete proposals. Discussion should focus on the unique features and approaches of each proposal, use cases that are explicitly supported or not supported, and how important these use cases are to the community. The community is invited to propose (as an Internet Draft) specific concrete data modeling proposals that substantially address the requirements gathered by the design team. These proposals should explain any additional requirements or features which motivated the specific design, which requirements are not met, why, and to what extent the approach has been implemented or modeled. Each proposal should also include a data model definition for the example annotated instance document. The BOF will only spend a short time on the requirements gathering work and will not debate the validity of the requirements. A case for or against specific requirements may, however, be made during presentations of specific solutions. Send comments on this BoF proposal to the NGO (NETCONF Goes On) list: ngo@ietf.org Input Documents: Requirements for a Configuration Data Modeling Language http://www.ietf.org/internet-drafts/draft-presuhn-rcdml-00.txt Drafts where teams write up how they deal with the requirements (not yet published since the requirements draft has to come out first) An Evaluation Framework for Data Modeling Languages in Network Management Domain http://www.ietf.org/internet-drafts/draft-xiao-evaluate-dml-01.txt NETCONF Data Modeling Language Requirements http://www.ersue.de/I-D/draft-linowski-netconf-DML-requirements-00.txt YANG - A data modeling language for NETCONF: http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-00.txt Using XML Schema to define NETCONF Content: http://tools.ietf.org/id/draft-chisholm-netconf-model-07.txt Other as-yet unpublished drafts Agenda (preliminary since we don't know which proposals there will be): (times may have to be adjusted depending on how many proposals there are.) 1. Introduction (one of the chairs): 5 minutes 2. Report from the requirements design team: 15 minutes 3. "Using XML Schema to define NETCONF Content": how it meets the agreed requirements, which additional requirements it meets and chooses not to. (Sharon: 25 minutes) Clarifying questions only. Discussion of proposal (10 minutes) 4. "something relaxng-ish": how it meets the agreed requirements, which additional requirements it meets and chooses not to. (Presenter not yet known: 25 minutes) Clarifying questions only. Discussion of proposal (10 minutes) 5. "YANG - A data modeling language for NETCONF": how it meets the agreed requirements, which additional requirements it meets and chooses not to. (YANG: 25 minutes) Clarifying questions only. Discussion of proposal (10 minutes) 6. Other? 7. General discussion and Way forward (rest of the time) Proposed charter for the NETCONF Modeling Working Group, to be formed after this BOF: The Working Group will standardize a modeling language and associated modeling rules to be used when defining management information to be used specifically with NETCONF. The Working Group is specifically NOT chartered to standardize a protocol-independent modeling language, but broader applicability of the language should not be needlessly hindered. The Working Group will use XX as the starting point for standardization. (where XX is the output of this BOF) Deliverables, etc. to be decided later. _______________________________________________ NGO mailing list NGO@ietf.org https://www1.ietf.org/mailman/listinfo/ngo
- [NGO] BOF Proposal: Comparing Approaches to NETCO… David Partain
- Re: [NGO] BOF Proposal: Comparing Approaches to N… Ladislav Lhotka
- Re: [NGO] BOF Proposal: Comparing Approaches to N… Balazs Lengyel
- Re: [NGO] BOF Proposal: Comparing Approaches to N… Ladislav Lhotka
- RE: [NGO] BOF Proposal: Comparing Approaches to N… Bert Wijnen
- RE: [NGO] BOF Proposal: Comparing Approaches to N… Mehmet Ersue
- Re: [NGO] BOF Proposal: Comparing Approaches to N… David Partain