[netmod] RFC 8344 on A YANG Data Model for IP Management

rfc-editor@rfc-editor.org Fri, 16 March 2018 21:38 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 55883126BF0; Fri, 16 Mar 2018 14:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dehPmuiEkNHI; Fri, 16 Mar 2018 14:38:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 132AF126C26; Fri, 16 Mar 2018 14:30:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B4F89B80CE7; Fri, 16 Mar 2018 14:30:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netmod@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180316213017.B4F89B80CE7@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:30:17 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/qmGdg1ZPDqTDz1C6LePWJ4hbKJE>
Subject: [netmod] =?utf-8?q?RFC_8344_on_A_YANG_Data_Model_for_IP_Managemen?= =?utf-8?q?t?=
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 16 Mar 2018 21:38:46 -0000

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

        
        RFC 8344

        Title:      A YANG Data Model for IP Management 
        Author:     M. Bjorklund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mbj@tail-f.com
        Pages:      34
        Characters: 59931
        Obsoletes:  RFC 7277

        I-D Tag:    draft-ietf-netmod-rfc7277bis-03.txt

        URL:        https://www.rfc-editor.org/info/rfc8344

        DOI:        10.17487/RFC8344

This document defines a YANG data model for management of IP
implementations.  The data model includes configuration and system
state.

The YANG data model in this document conforms to the Network
Management Datastore Architecture defined in RFC 8342.

This document obsoletes RFC 7277.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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