A YANG Data Model for Routing Information Protocol (RIP)
draft-ietf-rtgwg-yang-rip-06

Document Type Active Internet-Draft (rtgwg WG)
Last updated 2017-10-26
Replaces draft-liu-rtgwg-yang-rip
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Yang Validation 13 errors, 0 warnings.
Reviews
Additional URLs
- Yang catalog entry for ietf-rip@2017-10-25.yang
- Yang impact analysis for draft-ietf-rtgwg-yang-rip
Stream WG state Submitted to IESG for Publication
Document shepherd Yingzhen Qu
Shepherd write-up Show (last changed 2017-06-27)
IESG IESG state AD Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to Yingzhen Qu <yingzhen.qu@huawei.com>
Network Working Group                                             X. Liu
Internet-Draft                                                     Jabil
Intended status: Standards Track                                P. Sarda
Expires: April 29, 2018                                         Ericsson
                                                            V. Choudhary
                                                              Individual
                                                        October 26, 2017

        A YANG Data Model for Routing Information Protocol (RIP)
                      draft-ietf-rtgwg-yang-rip-06

Abstract

   This document describes a data model for the Routing Information
   Protocol (RIP).  Both RIP version 2 and RIPng are covered.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 29, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Liu, et al.              Expires April 29, 2018                 [Page 1]
Internet-Draft                  YANG RIP                    October 2017

Table of Contents

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

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 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",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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

   o  augment

   o  data model

Liu, et al.              Expires April 29, 2018                 [Page 2]
Show full document text