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

Document Type RFC - Proposed Standard (February 2020; No errata)
Authors Xufeng Liu  , Prateek Sarda  , Vikram Choudhary 
Last updated 2020-02-21
Replaces draft-liu-rtgwg-yang-rip
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Yang Validation 5 errors, 0 warnings.
Additional Resources
- Yang catalog entry for ietf-rip@2018-02-03.yang
- Yang impact analysis for draft-ietf-rtgwg-yang-rip
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Yingzhen Qu
Shepherd write-up Show (last changed 2017-06-27)
IESG IESG state RFC 8695 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Vigoureux
Send notices to Yingzhen Qu <yingzhen.qu@huawei.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack

Internet Engineering Task Force (IETF)                            X. Liu
Request for Comments: 8695                                Volta Networks
Category: Standards Track                                       P. Sarda
ISSN: 2070-1721                                                 Ericsson
                                                            V. Choudhary
                                                           February 2020

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


   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).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
     1.1.  Terminology
     1.2.  Tree Diagrams
     1.3.  Prefixes in Data Node Names
   2.  Design of the Data Model
     2.1.  Scope of the Data Model
     2.2.  Relation to the Core Routing Framework
     2.3.  Protocol Configuration
     2.4.  Protocol States
     2.5.  RPC Operations
     2.6.  Notifications
     2.7.  Optional Features
   3.  Tree Structure
   4.  YANG Module
   5.  IANA Considerations
   6.  Security Considerations
   7.  References
     7.1.  Normative References
     7.2.  Informative References
   Appendix A.  Data Tree Example
   Authors' Addresses

1.  Introduction

   This document introduces a YANG [RFC7950] data model for the Routing
   Information Protocol (RIP) [RFC2453][RFC2080].  RIP was designed to
   work as an Interior Gateway Protocol (IGP) in moderate-size
   Autonomous Systems (AS).

   This YANG data model supports both RIP version 2 and RIPng.  RIP
   version 2 (defined in [RFC2453]) supports IPv4.  RIPng (defined in
   [RFC2080]) supports IPv6.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   The following terms are defined in [RFC7950] and are not redefined

   *  augment

   *  data model

   *  data node

1.2.  Tree Diagrams

   A simplified graphical representation of the data model is used in
   this document.  The meaning of the symbols in these diagrams is
   defined in [RFC8340].

1.3.  Prefixes in Data Node Names

   In this document, names of data nodes, actions, and other data model
   objects are often used without a prefix, as long as it is clear from
   the context in which YANG module each name is defined.  Otherwise,
   names are prefixed using the standard prefix associated with the
   corresponding YANG module, as shown in Table 1.

               | Prefix    | YANG module     | Reference   |
               | yang      | ietf-yang-types | [RFC6991]   |
               | inet      | ietf-inet-types | [RFC6991]   |
               | if        | ietf-interfaces | [RFC8343]   |
               | ip        | ietf-ip         | [RFC8344]   |
               | rt        | ietf-routing    | [RFC8349]   |
Show full document text