RFC 8542 on A YANG Data Model for Fabric Topology in Data-Center Networks
rfc-editor@rfc-editor.org Mon, 25 March 2019 18:42 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 92B3012078E; Mon, 25 Mar 2019 11:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 xExJmcuKzLgr; Mon, 25 Mar 2019 11:42:37 -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 22910120790; Mon, 25 Mar 2019 11:42:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2A2C5B80E06; Mon, 25 Mar 2019 11:42:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8542 on A YANG Data Model for Fabric Topology in Data-Center Networks
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, i2rs@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190325184223.2A2C5B80E06@rfc-editor.org>
Date: Mon, 25 Mar 2019 11:42:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GhiN_mFAYUuTmyEM03IDzNYyKlg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 Mar 2019 18:42:40 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8542
Title: A YANG Data Model for
Fabric Topology in Data-Center Networks
Author: Y. Zhuang,
D. Shi,
R. Gu,
H. Ananthakrishnan
Status: Standards Track
Stream: IETF
Date: March 2019
Mailbox: zhuangyan.zhuang@huawei.com,
shidanian@huawei.com,
gurong_cmcc@outlook.com,
hari@netflix.com
Pages: 32
Characters: 53064
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-i2rs-yang-dc-fabric-network-topology-12.txt
URL: https://www.rfc-editor.org/info/rfc8542
DOI: 10.17487/RFC8542
This document defines a YANG data model for fabric topology in data-
center networks and represents one possible view of the data-center
fabric. This document focuses on the data model only and does not
endorse any kind of network design that could be based on the
abovementioned model.
This document is a product of the Interface to the Routing System 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