[netmod] RFC 6244 on An Architecture for Network Management Using NETCONF and YANG

rfc-editor@rfc-editor.org Thu, 30 June 2011 19:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E0111E80D6; Thu, 30 Jun 2011 12:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.815
X-Spam-Level:
X-Spam-Status: No, score=-105.815 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4iLATE-llJDP; Thu, 30 Jun 2011 12:46:21 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [64.170.98.47]) by ietfa.amsl.com (Postfix) with ESMTP id 35D5C11E8079; Thu, 30 Jun 2011 12:46:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 262A798C530; Thu, 30 Jun 2011 12:46:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110630194621.262A798C530@rfc-editor.org>
Date: Thu, 30 Jun 2011 12:46:21 -0700
Cc: netmod@ietf.org, rfc-editor@rfc-editor.org
Subject: [netmod] RFC 6244 on An Architecture for Network Management Using NETCONF and YANG
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 19:46:22 -0000

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

        
        RFC 6244

        Title:      An Architecture for Network Management 
                    Using NETCONF and YANG 
        Author:     P. Shafer
        Status:     Informational
        Stream:     IETF
        Date:       June 2011
        Mailbox:    phil@juniper.net
        Pages:      30
        Characters: 63276
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netmod-arch-10.txt

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

The Network Configuration Protocol (NETCONF) gives access to native
capabilities of the devices within a network, defining methods for
manipulating configuration databases, retrieving operational data,
and invoking specific operations.  YANG provides the means to define
the content carried via NETCONF, both data and operations.  Using
both technologies, standard modules can be defined to give
interoperability and commonality to devices, while still allowing
devices to express their unique capabilities.

This document describes how NETCONF and YANG help build network
management applications that meet the needs of network operators.
This document is not an Internet Standards Track specification; it is
published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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