[Teas] RFC 8795 on YANG Data Model for Traffic Engineering (TE) Topologies

rfc-editor@rfc-editor.org Thu, 06 August 2020 22:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124733A0141; Thu, 6 Aug 2020 15:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 irvSSLM8ABTy; Thu, 6 Aug 2020 15:58:09 -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 553103A0114; Thu, 6 Aug 2020 15:58:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0A466F40759; Thu, 6 Aug 2020 15:58:01 -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, teas@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200806225801.0A466F40759@rfc-editor.org>
Date: Thu, 6 Aug 2020 15:58:01 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/7dhv0kWYLmCuEsCtfXrMO_qAtDs>
Subject: [Teas] =?utf-8?q?RFC_8795_on_YANG_Data_Model_for_Traffic_Enginee?= =?utf-8?q?ring_=28TE=29_Topologies?=
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2020 22:58:11 -0000

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

        
        RFC 8795

        Title:      YANG Data Model for Traffic 
                    Engineering (TE) Topologies 
        Author:     X. Liu,
                    I. Bryskin,
                    V. Beeram,
                    T. Saad,
                    H. Shah,
                    O. Gonzalez de Dios
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2020
        Mailbox:    xufeng.liu.ietf@gmail.com, 
                    i_bryskin@yahoo.com, 
                    vbeeram@juniper.net,
                    tsaad@juniper.net, 
                    hshah@ciena.com,
                    oscar.gonzalezdedios@telefonica.com
        Pages:      170
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-yang-te-topo-22.txt

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

        DOI:        10.17487/RFC8795

This document defines a YANG data model for representing, retrieving,
and manipulating Traffic Engineering (TE) Topologies. The model
serves as a base model that other technology-specific TE topology
models can augment.

This document is a product of the Traffic Engineering Architecture and Signaling 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