RFC 8695 on A YANG Data Model for the Routing Information Protocol (RIP)

rfc-editor@rfc-editor.org Fri, 21 February 2020 22:33 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 755181200F3; Fri, 21 Feb 2020 14:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 CjRxCHV0U9K6; Fri, 21 Feb 2020 14:33:43 -0800 (PST)
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 103401200DB; Fri, 21 Feb 2020 14:33:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 507A5F40719; Fri, 21 Feb 2020 14:33:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2OTUgb24gQSBZQU5HIERhdGEgTW9kZWwgZm9yIHRoZSBSb3V0aW5nIEluZm9ybWF0aW9uIFByb3RvY29sIChSSVAp?=
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, rtgwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200221223336.507A5F40719@rfc-editor.org>
Date: Fri, 21 Feb 2020 14:33:36 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kN6-x3jjV-mY-PfwDex_pS0_xy4>
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: Fri, 21 Feb 2020 22:33:46 -0000

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

        
        RFC 8695

        Title:      A YANG Data Model for 
                    the Routing Information Protocol (RIP) 
        Author:     X. Liu,
                    P. Sarda,
                    V. Choudhary
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    xufeng.liu.ietf@gmail.com, 
                    prateek.sarda@ericsson.com, 
                    vikschw@gmail.com
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-yang-rip-11.txt

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

        DOI:        10.17487/RFC8695

This document describes a data model for the management of the
Routing Information Protocol (RIP).  Both RIP version 2 and RIPng are
covered.  The data model includes definitions for configuration,
operational state, and Remote Procedure Calls (RPCs).

The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA).

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