RFC 6110 on Mapping YANG to Document Schema Definition Languages and Validating NETCONF Content

rfc-editor@rfc-editor.org Sat, 12 February 2011 00:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 809E73A6A7B; Fri, 11 Feb 2011 16:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.029
X-Spam-Status: No, score=-102.029 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id vjSto95urEq4; Fri, 11 Feb 2011 16:03:52 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id BFF623A6A7A; Fri, 11 Feb 2011 16:03:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1F255E0745; Fri, 11 Feb 2011 16:04:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6110 on Mapping YANG to Document Schema Definition Languages and Validating NETCONF Content
From: rfc-editor@rfc-editor.org
Message-Id: <20110212000409.1F255E0745@rfc-editor.org>
Date: Fri, 11 Feb 2011 16:04:09 -0800 (PST)
Cc: netmod@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Feb 2011 00:03:53 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6110

        Title:      Mapping YANG to Document Schema 
                    Definition Languages and Validating NETCONF Content 
        Author:     L. Lhotka, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2011
        Mailbox:    lhotka@cesnet.cz
        Pages:      100
        Characters: 192547
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netmod-dsdl-map-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6110.txt

This document specifies the mapping rules for translating YANG data
models into Document Schema Definition Languages (DSDL), a
coordinated set of XML schema languages standardized as ISO/IEC
19757.  The following DSDL schema languages are addressed by the
mapping: Regular Language for XML Next Generation (RELAX NG),
Schematron, and Schematron and Document Schema Renaming Language
(DSRL).  The mapping takes one or more YANG modules and produces a
set of DSDL schemas for a selected target document type -- datastore
content, Network Configuration Protocol (NETCONF) messages, etc.
Procedures for schema-based validation of such documents are also
discussed.  [STANDARDS-TRACK]

This document is a product of the NETCONF Data Modeling Language Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC