RFC 9067 on A YANG Data Model for Routing Policy

rfc-editor@rfc-editor.org Tue, 12 October 2021 05:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE8E3A0D6A; Mon, 11 Oct 2021 22:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 dpgKA25c1-oU; Mon, 11 Oct 2021 22:16:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B2AB3A0D5E; Mon, 11 Oct 2021 22:16:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 499) id 42A34F380E; Mon, 11 Oct 2021 22:16:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9067 on A YANG Data Model for Routing Policy
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtgwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20211012051657.42A34F380E@rfc-editor.org>
Date: Mon, 11 Oct 2021 22:16:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/0CQknPjIxu89fXnmU9bJmoUIQPw>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2021 05:17:03 -0000

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

        
        RFC 9067

        Title:      A YANG Data Model for Routing Policy 
        Author:     Y. Qu,
                    J. Tantsura,
                    A. Lindem,
                    X. Liu
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2021
        Mailbox:    yingzhen.qu@futurewei.com,
                    jefftant.ietf@gmail.com,
                    acee@cisco.com,
                    xufeng.liu.ietf@gmail.com
        Pages:      38
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-policy-model-31.txt

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

        DOI:        10.17487/RFC9067

This document defines a YANG data model for configuring and managing
routing policies in a vendor-neutral way. The model provides a
generic routing policy framework that can be extended for specific
routing protocols using the YANG 'augment' mechanism.

This document is a product of the Routing Area Working Group 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