[i2rs] RFC 8346 on A YANG Data Model for Layer 3 Topologies

rfc-editor@rfc-editor.org Fri, 16 March 2018 21:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A848812D88A; Fri, 16 Mar 2018 14:31:16 -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 NtZwKw-1-XNM; Fri, 16 Mar 2018 14:31:01 -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 CA68412D892; Fri, 16 Mar 2018 14:30:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6FE3EB80CDB; Fri, 16 Mar 2018 14:30:54 -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, i2rs@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180316213054.6FE3EB80CDB@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:30:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/6E4Z_TVWPFE598rurWztvhS0uf8>
Subject: [i2rs] RFC 8346 on A YANG Data Model for Layer 3 Topologies
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 21:31:19 -0000

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

        
        RFC 8346

        Title:      A YANG Data Model for 
                    Layer 3 Topologies 
        Author:     A. Clemm, 
                    J. Medved,
                    R. Varga,
                    X. Liu,
                    H. Ananthakrishnan,
                    N. Bahadur
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ludwig@clemm.org, 
                    jmedved@cisco.com,
                    robert.varga@pantheon.tech, 
                    xufeng.liu.ietf@gmail.com,
                    hari@packetdesign.com, 
                    nitin_bahadur@yahoo.com
        Pages:      35
        Characters: 64661
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-i2rs-yang-l3-topology-16.txt

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

        DOI:        10.17487/RFC8346

This document defines a YANG data model for Layer 3 network
topologies.

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