ietf-rip

This YANG module defines a model for managing Routing Information Protocol (RIP), including RIP version 2 and RIPng. Copyright ...

  • Version: 2020-02-20

    ietf-rip@2020-02-20


    
      module ietf-rip {
    
        yang-version 1.1;
    
        namespace
          "urn:ietf:params:xml:ns:yang:ietf-rip";
    
        prefix rip;
    
        import ietf-inet-types {
          prefix inet;
        }
        import ietf-yang-types {
          prefix yang;
        }
        import ietf-interfaces {
          prefix if;
        }
        import ietf-ip {
          prefix ip;
        }
        import ietf-routing {
          prefix rt;
        }
        import ietf-key-chain {
          prefix key-chain;
        }
        import ietf-bfd-types {
          prefix bfd-types;
        }
        import ietf-ospf {
          prefix ospf;
        }
        import ietf-isis {
          prefix isis;
        }
    
        organization
          "IETF Routing Area Working Group (rtgwg)";
    
        contact
          "WG Web:   <https://datatracker.ietf.org/wg/rtgwg/>
         WG List:  <mailto:rgtwg@ietf.org>
    
         Editor:   Xufeng Liu
                   <mailto:xufeng.liu.ietf@gmail.com>
    
         Editor:   Prateek Sarda
                   <mailto:prateek.sarda@ericsson.com>
    
         Editor:   Vikram Choudhary
                   <mailto:vikschw@gmail.com>";
    
        description
          "This YANG module defines a model for managing Routing
         Information Protocol (RIP), including RIP version 2 and RIPng.
    
         Copyright (c) 2020 IETF Trust and the persons identified as
         authors of the code.  All rights reserved.
    
         Redistribution and use in source and binary forms, with or
         without modification, is permitted pursuant to, and subject to
         the license terms contained in, the Simplified BSD License set
         forth in Section 4.c of the IETF Trust's Legal Provisions
         Relating to IETF Documents
         (http://trustee.ietf.org/license-info).
    
         This version of this YANG module is part of RFC 8695; see the
         RFC itself for full legal notices.";
    
        revision "2020-02-20" {
          description "Initial revision.";
          reference
            "RFC 8695: A YANG Data Model for Routing Information Protocol
            (RIP).
             RFC 2453: RIP Version 2.
             RFC 2080: RIPng for IPv6.
             RFC 1724: RIP Version 2 MIB Extension.";
    
        }
    
    
        feature bfd {
          description
            "This feature indicates that the RIP implementation on the
           system supports BFD (Bidirectional Forwarding Detection).";
        }
    
        feature explicit-neighbors {
          description
            "This feature indicates that the system supports explicit
           neighbor configuration on a RIP interface.";
        }
    
        feature global-statistics {
          description
            "This feature indicates that the system supports collecting
           global statistics data related to RIP.";
        }
    
        feature interface-statistics {
          description
            "This feature indicates that the system supports collecting
           per-interface statistics data related to RIP.";
        }
    
        typedef prefix-set-ref {
          type string;
          description
            "A type for a reference to a prefix set.
           The string value is the name identifier for uniquely
           identifying the referenced prefix set, which contains a list
           of prefixes that a routing policy can applied.  The definition
           of such a prefix set is outside the scope of this document.";
        }
    
        typedef route-policy-ref {
          type string;
          description
            "A type for a reference to a route policy.
           The string value is the name identifier for uniquely
           identifying the referenced routing policy, which contains one
           or more policy rules that can be used for a routing decision.
           The definition of such a routing policy is outside the scope
           of this document.";
        }
    
        identity rip {
          base rt:routing-protocol;
          description
            "Identity for the Routing Information Protocol.";
        }
    
        identity ripv2 {
          base rip:rip;
          description
            "Identity for RIPv2 (RIP version 2).";
        }
    
        identity ripng {
          base rip:rip;
          description "Identity for RIPng.";
        }
    
        rpc clear-rip-route {
          description
            "Clears RIP routes from the IP routing table and routes
           redistributed into RIP for the specified RIP instance
           or for all RIP instances in the current context.";
          input {
            leaf rip-instance {
              type leafref {
                path "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/rt:name";
              }
              description
                "Instance name identifying a specific RIP instance.
               This leaf is optional for the RPC.
               If it is specified, the RPC will clear all routes in the
               specified RIP instance;
               if it is not specified, the RPC will clear all routes in
               all RIP instances.";
            }
          }
        }  // rpc clear-rip-route
      }  // module ietf-rip
    

© 2023 YumaWorks, Inc. All rights reserved.