RFC 8343 on A YANG Data Model for Interface Management
rfc-editor@rfc-editor.org Fri, 16 March 2018 21:30 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DDA112D874; Fri, 16 Mar 2018 14:30:26 -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=ham 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 hha4yTwoNCs1; Fri, 16 Mar 2018 14:30:08 -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 3AF2512D969; Fri, 16 Mar 2018 14:30:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CFF94B80CD5; Fri, 16 Mar 2018 14:29:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8343 on A YANG Data Model for Interface Management
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: <20180316212956.CFF94B80CD5@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:29:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ScmJwBz-JLrcpkShv9UaqXhBByQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 16 Mar 2018 21:30:29 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8343
Title: A YANG Data Model for Interface Management
Author: M. Bjorklund
Status: Standards Track
Stream: IETF
Date: March 2018
Mailbox: mbj@tail-f.com
Pages: 49
Characters: 91573
Obsoletes: RFC 7223
I-D Tag: draft-ietf-netmod-rfc7223bis-03.txt
URL: https://www.rfc-editor.org/info/rfc8343
DOI: 10.17487/RFC8343
This document defines a YANG data model for the management of network
interfaces. It is expected that interface-type-specific data models
augment the generic interfaces data model defined in this document.
The data model includes definitions for configuration and system
state (status information and counters for the collection of
statistics).
The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) defined in RFC 8342.
This document obsoletes RFC 7223.
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