Skip to main content

YANG Data Model for RPKI to Router Protocol
draft-ietf-sidrops-rtr-yang-13

Document Type Active Internet-Draft (sidrops WG)
Authors Yisong Liu , Changwang Lin , Jishnu Roy , Haibo Wang , Jeff Haas , Hongwei Liu , Di Ma
Last updated 2026-10-28 (Latest revision 2026-10-21)
Replaces draft-liu-sidrops-rtr-yang
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Yang Validation 0 errors, 0 warnings
Reviews
Additional resources Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Russ Housley
Shepherd write-up Show Last changed 2026-10-21
IESG IESG state AD Evaluation::Revised I-D Needed
Action Holders
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Mohamed Boucadair
Send notices to ggx@gigix.net, housley@vigilsec.com
draft-ietf-sidrops-rtr-yang-13
SIDROPS Working Group                                             Y. Liu
Internet-Draft                                              China Mobile
Intended status: Standards Track                                  C. Lin
Expires: 24 April 2027                              New H3C Technologies
                                                                  J. Roy
                                                                     HPE
                                                                 H. Wang
                                                     Huawei Technologies
                                                                 J. Haas
                                                                     HPE
                                                                  H. Liu
                                                         ZTE Corporation
                                                                   D. Ma
                                                                    ZDNS
                                                         21 October 2026

              YANG Data Model for RPKI to Router Protocol
                     draft-ietf-sidrops-rtr-yang-13

Abstract

   This document defines YANG data models for managing Resource Public
   Key Infrastructure (RPKI) to Router Protocol (RFC6810 and RFC8210).

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 https://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 24 April 2027.

Copyright Notice

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

Liu, et al.               Expires 24 April 2027                 [Page 1]
Internet-Draft           YANG Data Model for RTR            October 2026

   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 Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology and Notation Conventions  . . . . . . . . . . . .   3
     2.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Data Model Overview . . . . . . . . . . . . . . . . . . . . .   4
   4.  RPKI to Router YANG Module  . . . . . . . . . . . . . . . . .   4
     4.1.  Tree View . . . . . . . . . . . . . . . . . . . . . . . .   4
       4.1.1.  Overall Structure . . . . . . . . . . . . . . . . . .   4
       4.1.2.  RTR Session Configuration . . . . . . . . . . . . . .   5
       4.1.3.  RTR Session State . . . . . . . . . . . . . . . . . .   9
     4.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .  14
   5.  RPKI Table YANG Module  . . . . . . . . . . . . . . . . . . .  30
     5.1.  Tree View . . . . . . . . . . . . . . . . . . . . . . . .  30
       5.1.1.  Overall Structure . . . . . . . . . . . . . . . . . .  30
       5.1.2.  VRP Table . . . . . . . . . . . . . . . . . . . . . .  31
       5.1.3.  Router Key Table  . . . . . . . . . . . . . . . . . .  33
       5.1.4.  ASPA Table  . . . . . . . . . . . . . . . . . . . . .  34
     5.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .  35
   6.  Implementation Status . . . . . . . . . . . . . . . . . . . .  44
     6.1.  Juniper Networks (HPE)  . . . . . . . . . . . . . . . . .  44
     6.2.  New H3C Technologies  . . . . . . . . . . . . . . . . . .  45
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  46
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  48
     8.1.  RPKI to Router YANG Module Registry . . . . . . . . . . .  48
     8.2.  RPKI Table YANG Module Registry . . . . . . . . . . . . .  49
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  49
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  49
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  49
     10.2.  Informative References . . . . . . . . . . . . . . . . .  51
   Appendix A.  Full Tree of RPKI to Router YANG Module  . . . . . .  52
   Appendix B.  Full Tree of RPKI Table YANG Module  . . . . . . . .  55
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  56
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  56

Liu, et al.               Expires 24 April 2027                 [Page 2]
Internet-Draft           YANG Data Model for RTR            October 2026

1.  Introduction

   [RFC6810] and [RFC8210] describe a protocol to deliver Resource
   Public Key Infrastructure (RPKI) prefix origin data and router keys
   from a trusted cache server to a router, referred to as the RPKI to
   Router (RTR) protocol.

   [I-D.ietf-sidrops-8210bis] describes version 2 of the RTR protocol,
   which adds a new Autonomous System Provider Authorization (ASPA) PDU
   type.

   This document defines YANG [RFC7950] data models for managing RTR
   protocol ([RFC6810], [RFC8210], and [I-D.ietf-sidrops-8210bis]).

2.  Terminology and Notation Conventions

2.1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "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.

2.2.  Terminology

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

   *  augment

   *  data model

   *  data node

   *  module

   *  namespace

   *  YANG

2.3.  Tree Diagrams

   Tree diagrams used in this document follow the notation defined in
   [RFC8340].

Liu, et al.               Expires 24 April 2027                 [Page 3]
Internet-Draft           YANG Data Model for RTR            October 2026

3.  Data Model Overview

   This document defines two YANG modules: "ietf-rpki-rtr" and "ietf-
   rpki-table".

   The "ietf-rpki-rtr" YANG module provides the methods for managing RTR
   protocol.  It includes:

   *  Connectivity parameters, such as RPKI cache server IP address and
      destination port.

   *  Session parameters, such as refresh interval, retry interval,
      expire interval, and hold interval.

   *  Session status and statistics, such as session ID, serial number,
      number of received and transmitted messages.

   The "ietf-rpki-table" YANG module provides the methods for managing
   records of RTR protocol and the corresponding state hash which is a
   hash value used in the Canonical Cache Representation (CCR) content
   [I-D.ietf-sidrops-rpki-ccr].  It includes:

   *  Validated ROA Payload (VRP) records.

   *  Router Key records.

   *  ASPA records.

   *  CCR state hash, which is optional and is used to verify the
      integrity and consistency of RPKI data originating from the RPKI
      cache.

4.  RPKI to Router YANG Module

4.1.  Tree View

   The full tree of the "ietf-rpki-rtr" YANG module is provided in
   Appendix A.  The following subsections list the subtree structures.

4.1.1.  Overall Structure

   The overall tree structure of the "ietf-rpki-rtr" YANG module is
   shown in Figure 1.

   The "ietf-rpki-rtr" YANG module augments the core routing YANG module
   "ietf-routing" specified in [RFC8349] for managing RTR protocol
   sessions.  Specifically, this YANG module augments "/rt:routing/
   rt:control-plane-protocols/rt:control-plane-protocol".

Liu, et al.               Expires 24 April 2027                 [Page 4]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                +--rw server-address           inet:ip-address
                +--rw server-port?             inet:port-number
                +--rw local-address?           union
                +--rw local-port?              inet:port-number
                +--rw enabled?                 boolean
                +--rw preference?              uint32
                +--rw description?             string
                +--rw reconnect-interval?      uint32
                +--ro session-state?           enumeration
                +--rw enable-authentication?   boolean
                +--rw authentication
                |  ...
                +--rw vrp-limit
                |  ...
                +--rw aspa-limit
                |  ...
                +--ro statistics
                |  ...
                +--ro connection-data
                |  ...
                +--rw protocol-data
                |  ...
                +--ro pdu-counters
                |  ...
                +--ro error-pdu-counters
                   ...

              Figure 1: Overall RPKI to Router Tree Structure

   The "ietf-rpki-rtr" YANG module has a root container 'rpki-rtr',
   which has a subcontainer 'sessions'.  The container 'sessions'
   contains a list 'session', where each entry represents a session
   configuration and state to a specific RPKI cache server.

4.1.2.  RTR Session Configuration

   The RTR session configuration structure for the list 'session' is
   shown in Figure 2.

Liu, et al.               Expires 24 April 2027                 [Page 5]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                +--rw server-address           inet:ip-address
                +--rw server-port?             inet:port-number
                +--rw local-address?           union
                +--rw local-port?              inet:port-number
                +--rw enabled?                 boolean
                +--rw preference?              uint32
                +--rw description?             string
                +--rw reconnect-interval?      uint32
                +--rw enable-authentication?   boolean
                +--rw authentication
                |  ...
                +--rw vrp-limit
                |  ...
                +--rw aspa-limit
                |  ...
                +--rw protocol-data
                |  ...

           Figure 2: RTR Session Configuration Subtree Structure

   The configuration data nodes for the list 'session' are described as
   follows:

   'server-address': Indicates the IP address of the RPKI cache server.

   'server-port': Indicates the port number the server listens on.

   'local-address': Indicates the source IP address used when initiating
   a RTR session connection locally.

   'local-port': Indicates the source port number used when initiating a
   RTR session connection locally.

   'enabled': Indicates the management switch for the RTR session.

   'preference': Indicates the priority for connecting to the RPKI cache
   server.

   'description': Indicates the description information for the RTR
   session.

Liu, et al.               Expires 24 April 2027                 [Page 6]
Internet-Draft           YANG Data Model for RTR            October 2026

   'reconnect-interval': Indicates the reconnection interval after
   session disconnection.

   'enable-authentication': Indicates the switch to enable connection
   authentication for the RTR session.

   'authentication': Indicates the configuration information of
   connection authentication for the RTR session, as shown in Figure 3.

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--rw authentication
                |  +--rw (option)?
                |     +--:(md5)
                |     |  +--rw md5-password?   ianach:crypt-hash
                |     +--:(ssh)
                |     |  +--rw client-identity
                |     |  |  +--rw username?  string
                |     |  |  +--rw public-key!
                |     |  |                   {client-ident-publickey}?
                |     |  |  +--rw password!
                |     |  |                   {client-ident-password}?
                |     |  |  +--rw hostbased!
                |     |  |                   {client-ident-hostbased}?
                |     |  |  +--rw none?      empty {client-ident-none}?
                |     |  |  +--rw certificate!
                |     |  |                   {sshcmn:ssh-x509-certs}?
                |     |  +--rw server-authentication
                |     |  |  +--rw ssh-host-keys!
                |     |  |  +--rw ca-certs!  {sshcmn:ssh-x509-certs}?
                |     |  |  +--rw ee-certs!  {sshcmn:ssh-x509-certs}?
                |     |  +--rw transport-params
                |     |  |                 {sshcmn:transport-params}?
                |     |  +--rw keepalives!   {ssh-client-keepalives}?
                |     |     +--rw max-wait?       uint16
                |     |     +--rw max-attempts?   uint8
                |     +--:(tcp-ao-keychain)
                |        +--rw keychain-name?  key-chain:key-chain-ref
                +--rw vrp-limit
                |  ...
                +--rw aspa-limit
                |  ...

Liu, et al.               Expires 24 April 2027                 [Page 7]
Internet-Draft           YANG Data Model for RTR            October 2026

           Figure 3: RTR Session Authentication Subtree Structure

   'vrp-limit' (Figure 4): Indicates the limit configuration on the
   number of VRP record received from the RTR session.

   'aspa-limit' (Figure 4): Indicates the limit configuration on the
   number of ASPA record received from the RTR session.

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--rw authentication
                |  ...
                +--rw vrp-limit
                |  +--rw max-number?              uint64
                |  +--rw threshold-percentage?    rt-types:percentage
                |  +--rw over-threshold-action?   enumeration
                +--rw aspa-limit
                |  +--rw max-number?              uint64
                |  +--rw threshold-percentage?    rt-types:percentage
                |  +--rw over-threshold-action?   enumeration

       Figure 4: RTR Session Received Record Limit Subtree Structure

   In Figure 4, 'vrp-limit' and 'aspa-limit' have the same structure,
   both having the maximum number of records allowed to be received from
   the RTR session ('max-number'), the threshold percentage for record
   maximum number ('threshold-percentage'), and handling strategy when
   exceeding the record threshold ('over-threshold-action').

   'protocol-data': Indicates the protocol parameters of the RTR
   session.  The configurable parameters include the preferred protocol
   version ('preferred-protocol-version') and the intervals for refresh
   ('refresh-interval'), retry ('retry-interval'), expire ('expire-
   interval'), and hold ('hold-interval') timers, as shown in Figure 5.

Liu, et al.               Expires 24 April 2027                 [Page 8]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--rw protocol-data
                |  +--rw preferred-protocol-version?   uint8
                |  +--rw refresh-interval?             uint32
                |  +--rw retry-interval?               uint32
                |  +--rw expire-interval?              uint32
                |  +--rw hold-interval?                uint32
                |  ...
                ...

    Figure 5: RTR Session Protocol Data Configuration Subtree Structure

4.1.3.  RTR Session State

   The RTR session state structure for the list 'session' is shown in
   Figure 6.

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                +--ro session-state?           enumeration
                +--ro statistics
                |  ...
                +--ro connection-data
                |  ...
                +--rw protocol-data
                |  ...
                +--ro pdu-counters
                |  ...
                +--ro error-pdu-counters
                   ...

               Figure 6: RTR Session State Subtree Structure

   The state data nodes for the list 'session' are described as follows:

   'session-state': Indicates the connection status of the RTR session.

Liu, et al.               Expires 24 April 2027                 [Page 9]
Internet-Draft           YANG Data Model for RTR            October 2026

   'statistics': Indicates the statistics of RPKI records or messages
   received from the server of the RTR session, as shown in Figure 7.

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--ro statistics
                |  +--ro total-vrp-records?  yang:zero-based-counter64
                |  +--ro ipv4-vrp-records?   yang:zero-based-counter64
                |  +--ro ipv6-vrp-records?   yang:zero-based-counter64
                |  +--ro router-key-records? yang:zero-based-counter64
                |  +--ro aspa-records?       yang:zero-based-counter64
                |  +--ro in-total-messages?  yang:zero-based-counter64
                |  +--ro out-total-messages? yang:zero-based-counter64
                +--ro connection-data
                |  ...
                +--rw protocol-data
                |  ...
                +--ro pdu-counters
                |  ...
                +--ro error-pdu-counters
                   ...

             Figure 7: RTR Session Statistics Subtree Structure

   'connection-data': Indicates the state information relating to the
   session connection with the RPKI cache server, as shown in Figure 8.

Liu, et al.               Expires 24 April 2027                [Page 10]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--ro statistics
                |  ...
                +--ro connection-data
                |  +--ro flaps?                       uint32
                |  +--ro last-session-up-down?        yang:date-and-time
                |  +--ro last-update-sync?            yang:date-and-time
                |  +--ro last-full-sync?              yang:date-and-time
                |  +--ro last-serial-query?           yang:date-and-time
                |  +--ro last-reset-query?            yang:date-and-time
                |  +--ro last-eod-received?           yang:date-and-time
                |  +--ro last-config-change?          yang:date-and-time
                |  +--ro last-error?                  yang:date-and-time
                |  +--ro last-connection-error?       yang:date-and-time
                |  +--ro last-connection?             yang:date-and-time
                |  +--ro error-reason?                string
                +--rw protocol-data
                |  ...
                +--ro pdu-counters
                |  ...
                +--ro error-pdu-counters
                   ...

          Figure 8: RTR Session Connection Data Subtree Structure

   'protocol-data': Indicates the state parameters of the RTR protocol
   of the session.  The state parameters include the negotiated protocol
   version ('protocol-version'), the scheduled time points for refresh
   ('refresh-time'), response ('response-time'), record lifetime
   ('record-lifetime'), and hold ('hold-time'), as well as the session
   identifier ('session-id') and serial numbers ('serial-full' and
   'serial-incremental'), as shown in Figure 9.  The configurable
   protocol parameters in 'protocol-data' are described in
   Section 4.1.2.

Liu, et al.               Expires 24 April 2027                [Page 11]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--ro statistics
                |  ...
                +--ro connection-data
                |  ...
                +--rw protocol-data
                |  ...
                |  +--ro protocol-version?   uint8
                |  +--ro refresh-time?       yang:date-and-time
                |  +--ro response-time?      yang:date-and-time
                |  +--ro record-lifetime?    yang:date-and-time
                |  +--ro hold-time?          yang:date-and-time
                |  +--ro session-id?         uint16
                |  +--ro serial-full?        uint32
                |  +--ro serial-incremental? uint32
                +--ro pdu-counters
                |  ...
                +--ro error-pdu-counters
                   ...

        Figure 9: RTR Session Protocol Data State Subtree Structure

   'pdu-counters': Indicates the send and receive statistics of various
   types of RTR PDUs, as shown in Figure 10.

Liu, et al.               Expires 24 April 2027                [Page 12]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--ro statistics
                |  ...
                +--ro connection-data
                |  ...
                +--rw protocol-data
                |  ...
                +--ro pdu-counters
                |  +--ro serial-notify?    yang:zero-based-counter64
                |  +--ro serial-query?     yang:zero-based-counter64
                |  +--ro reset-query?      yang:zero-based-counter64
                |  +--ro cache-response?   yang:zero-based-counter64
                |  +--ro ipv4-prefix?      yang:zero-based-counter64
                |  +--ro ipv6-prefix?      yang:zero-based-counter64
                |  +--ro end-of-data?      yang:zero-based-counter64
                |  +--ro cache-reset?      yang:zero-based-counter64
                |  +--ro router-key?       yang:zero-based-counter64
                |  +--ro aspa?             yang:zero-based-counter64
                +--ro error-pdu-counters
                   ...

           Figure 10: RTR Session PDU Counters Subtree Structure

   'error-pdu-counters': Indicates counters of Error Report PDUs
   exchanged with the RPKI cache server, by error code, as shown in
   Figure 11.

Liu, et al.               Expires 24 April 2027                [Page 13]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                ...
                +--ro statistics
                |  ...
                +--ro connection-data
                |  ...
                +--rw protocol-data
                |  ...
                +--ro pdu-counters
                |  ...
                +--ro error-pdu-counters
                   +--ro corrupt-data?      yang:zero-based-counter64
                   +--ro internal-error?    yang:zero-based-counter64
                   +--ro no-data-available? yang:zero-based-counter64
                   +--ro invalid-request?   yang:zero-based-counter64
                   +--ro unsupported-protocol-version?
                   |                        yang:zero-based-counter64
                   +--ro unsupported-pdu-type?
                   |                        yang:zero-based-counter64
                   +--ro withdrawal-unknown-record?
                   |                        yang:zero-based-counter64
                   +--ro duplicate-announcement-received?
                   |                        yang:zero-based-counter64
                   +--ro unexpected-protocol-version?
                   |                        yang:zero-based-counter64
                   +--ro aspa-provider-list-error?
                   |                        yang:zero-based-counter64
                   +--ro transport-failure?  yang:zero-based-counter64
                   +--ro ordering-error?      yang:zero-based-counter64
                   +--ro cache-restart?       yang:zero-based-counter64
                   +--ro cache-shutdown?      yang:zero-based-counter64

        Figure 11: RTR Session Error PDU Counters Subtree Structure

4.2.  YANG Module

   This YANG module has normative references to [RFC6810], [RFC7317],
   [RFC8177], [RFC8210], [RFC8294], [RFC8343], [RFC8349], [RFC9644],
   [RFC9911], and [I-D.ietf-sidrops-8210bis].

Liu, et al.               Expires 24 April 2027                [Page 14]
Internet-Draft           YANG Data Model for RTR            October 2026

     Note that the "RFC ZZZZ" in this YANG module must be replaced by
     the publication version of [I-D.ietf-sidrops-8210bis] and this
     note is to be removed after the publication of
     [I-D.ietf-sidrops-8210bis].

   <CODE BEGINS> file "ietf-rpki-rtr@2026-10-15.yang"
   module ietf-rpki-rtr {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-rpki-rtr";
     prefix rpki-rtr;

     import ietf-yang-types {
       prefix yang;
       reference
         "RFC 9911: Common YANG Data Types";
     }
     import ietf-inet-types {
       prefix inet;
       reference
         "RFC 9911: Common YANG Data Types";
     }
     import ietf-routing {
       prefix rt;
       reference
         "RFC 8349: A YANG Data Model for Routing Management
                    (NMDA Version)";
     }
     import ietf-routing-types {
       prefix rt-types;
       reference
         "RFC 8294: Common YANG Data Types for the Routing Area";
     }
     import iana-crypt-hash {
       prefix ianach;
       reference
         "RFC 7317: A YANG Data Model for System Management";
     }
     import ietf-ssh-client {
       prefix sshc;
       reference
         "RFC 9644: YANG Groupings for SSH Clients and SSH Servers";
     }
     import ietf-interfaces {
       prefix if;
       reference
         "RFC 8343: A YANG Data Model for Interface Management";
     }
     import ietf-key-chain {

Liu, et al.               Expires 24 April 2027                [Page 15]
Internet-Draft           YANG Data Model for RTR            October 2026

       prefix key-chain;
       reference
         "RFC 8177: YANG Data Model for Key Chains";
     }

     organization
       "IETF Secure Inter-Domain Routing Operations (SIDROPS)
        Working Group";
     contact
       "WG Web:   <https://datatracker.ietf.org/wg/sidrops/>
        WG List:  SIDROPS <mailto:sidrops@ietf.org>

        Editor:   Yisong Liu
                  <mailto:liuyisong@chinamobile.com>
        Editor:   Changwang Lin
                  <mailto:linchangwang.04414@h3c.com>
        Editor:   Haibo Wang
                  <mailto:rainsword.wang@huawei.com>
        Editor:   Jishnu Roy
                  <mailto:jishnu.roy@hpe.com>
        Editor:   Jeffrey Haas
                  <mailto:jeffrey.haas@hpe.com>
        Editor:   Hongwei Liu
                  <mailto:liu.hongwei3@zte.com.cn>
        Editor:   Di Ma
                  <mailto:madi@zdns.cn>";
     description
       "This module describes a YANG model for the Resource Public
        Key Infrastructure (RPKI) to Router (RTR) protocol management.

        The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
        NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
        'MAY', and 'OPTIONAL' in this document are to be interpreted as
        described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
        they appear in all capitals, as shown here.

        Copyright (c) 2026 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 Revised BSD License set
        forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (https://trustee.ietf.org/license-info).

        All revisions of IETF and IANA published modules can be found
        at the YANG Parameters registry group

Liu, et al.               Expires 24 April 2027                [Page 16]
Internet-Draft           YANG Data Model for RTR            October 2026

        (https://www.iana.org/assignments/yang-parameters).

        This version of this YANG module is part of RFC XXXX; see the
        RFC itself for full legal notices.";

     revision 2026-10-15 {
       description
         "Initial Version";
       reference
         "RFC XXXX: YANG Data Model for RPKI to Router Protocol";
     }

     identity rpki-rtr {
       base rt:routing-protocol;
       description
         "RTR protocol.";
     }

     grouping records-limit {
       description
         "Limit of records that can be received from the RPKI
          cache server.";
       leaf max-number {
         type uint64;
         description
           "Configures the maximum number of records that can be
            received from the RPKI cache server.";
       }
       leaf threshold-percentage {
         type rt-types:percentage;
         units "percent";
         description
           "Configures the threshold percentage for record maximum
            number.";
       }
       leaf over-threshold-action {
         type enumeration {
           enum alert-only {
             description
               "Generates alert messages.";
           }
           enum discard {
             description
               "Discards excess records.";
           }
           enum reconnect {
             description
               "Disconnects with the RPKI cache server,

Liu, et al.               Expires 24 April 2027                [Page 17]
Internet-Draft           YANG Data Model for RTR            October 2026

                and tries to reconnect after reconnection
                timer expires.";
           }
           enum idle-forever {
             description
               "Disconnects with the RPKI cache server
                forever.";
           }
         }
         description
           "The action to taken when record number exceeds
            threshold.";
       }
     }

     augment "/rt:routing/rt:control-plane-protocols/"
           + "rt:control-plane-protocol" {
       when "derived-from-or-self(rt:type, 'rpki-rtr')" {
         description
           "This augmentation is valid for a routing protocol
            instance of RTR.";
       }
       description
         "RTR protocol augmentation of ietf-routing module
          control-plane-protocol.";
       container rpki-rtr {
         description
           "Configuration parameters for the RTR protocol.";
         container sessions {
           description
             "Parameters of RPKI sessions to cache servers.";
           list session {
             key "server-address";
             description
               "Each entry contains parameters for a RPKI session
                identified by the 'server-address' key.";
             leaf server-address {
               type inet:ip-address;
               mandatory true;
               description
                 "The IP address of the RPKI cache server resembling
                  a session.";
             }
             leaf server-port {
               type inet:port-number;
               description
                 "The remote port for the connection
                  to the RPKI cache server.";

Liu, et al.               Expires 24 April 2027                [Page 18]
Internet-Draft           YANG Data Model for RTR            October 2026

             }
             leaf local-address {
               type union {
                 type inet:ip-address;
                 type if:interface-ref;
               }
               description
                 "The local IP (either IPv4 or IPv6) address to use for
                  the connection to the RPKI cache server. This may be
                  expressed as either an IP address or reference to the
                  name of an interface.";
             }
             leaf local-port {
               type inet:port-number;
               description
                 "The local port for the connection
                  to the RPKI cache server.";
             }
             leaf enabled {
               type boolean;
               default "true";
               description
                 "Whether the RPKI cache server is enabled.";
             }
             leaf preference {
               type uint32;
               description
                 "The router's preference to connect to that cache.
                  The lower the value, the more preferred.";
             }
             leaf description {
               type string;
               description
                 "Textual description of the RPKI cache server.";
             }
             leaf reconnect-interval {
               type uint32 {
                 range "1..30000";
               }
               units "minutes";
               description
                 "Time interval for the reconnection timer.";
             }
             leaf session-state {
               type enumeration {
                 enum idle {
                   description
                     "The session is down.";

Liu, et al.               Expires 24 April 2027                [Page 19]
Internet-Draft           YANG Data Model for RTR            October 2026

                 }
                 enum connect {
                   description
                     "The session is waiting for the underlying
                      transport session to be established.";
                 }
                 enum establish {
                   description
                     "The session is up.";
                 }
                 enum ex-incr {
                   description
                     "Incremental update of records in progress.";
                 }
                 enum ex-full {
                   description
                     "Full update of records in progress.";
                 }
               }
               config false;
               description
                 "The session state.";
             }
             leaf enable-authentication {
               type boolean;
               default "false";
               description
                 "Whether the session is secured.";
             }
             container authentication {
               when "../enable-authentication = 'true'";
               description
                 "Container for describing how a particular session
                  is to be secured.";
               choice option {
                 description
                   "Choice for session securing methods.";
                 case md5 {
                   leaf md5-password {
                     type ianach:crypt-hash;
                     description
                       "The password for md5 authentication.";
                   }
                   description
                     "Uses TCP-MD5 to secure the session.";
                 }
                 case ssh {
                   uses sshc:ssh-client-grouping {

Liu, et al.               Expires 24 April 2027                [Page 20]
Internet-Draft           YANG Data Model for RTR            October 2026

                     reference
                       "RFC 9644: YANG Groupings for SSH Clients and
                                  SSH Servers";
                   }
                   description
                     "Uses SSH to secure the session.";
                 }
                 case tcp-ao-keychain {
                   leaf keychain-name {
                     type key-chain:key-chain-ref;
                     description
                       "Name of key chain.";
                     reference
                       "RFC 8177: YANG Data Model for Key Chains";
                   }
                   description
                     "Uses key-chain to secure the session.";
                 }
               }
             }
             container vrp-limit {
               description
                 "Limit of Validated ROA Payload records that can be
                  received from the RPKI cache server.";
               uses records-limit;
             }
             container aspa-limit {
               description
                 "Limit of Autonomous System Provider Authorization
                  (ASPA) records that can be received from the RPKI
                  cache server.";
               uses records-limit;
             }
             container statistics {
               config false;
               description
                 "Statistics of the RPKI cache server.";
               leaf total-vrp-records {
                 type yang:zero-based-counter64;
                 description
                   "The total number of Validated ROA Payloads
                    received from the RPKI cache server.";
               }
               leaf ipv4-vrp-records {
                 type yang:zero-based-counter64;
                 description
                   "The number of Validated ROA Payloads for IPv4
                    prefixes received from the RPKI cache server.";

Liu, et al.               Expires 24 April 2027                [Page 21]
Internet-Draft           YANG Data Model for RTR            October 2026

               }
               leaf ipv6-vrp-records {
                 type yang:zero-based-counter64;
                 description
                   "The number of Validated ROA Payloads for IPv6
                    prefixes received from the RPKI cache server.";
               }
               leaf router-key-records {
                 type yang:zero-based-counter64;
                 description
                   "The number of Router Keys received from the RPKI
                    cache server.";
               }
               leaf aspa-records {
                 type yang:zero-based-counter64;
                 description
                   "The number of ASPAs received from the RPKI
                    cache server.";
               }
               leaf in-total-messages {
                 type yang:zero-based-counter64;
                 description
                   "The total number of messages received from the
                    RPKI cache server.";
               }
               leaf out-total-messages {
                 type yang:zero-based-counter64;
                 description
                   "The total number of messages transmitted to the
                    RPKI cache server.";
               }
             }
             container connection-data {
               config false;
               description
                 "State information relating to the connection
                  with the RPKI cache server.";
               leaf flaps {
                 type uint32;
                 description
                   "Count for number of flaps observed on the
                    session.";
               }
               leaf last-session-up-down {
                 type yang:date-and-time;
                 description
                   "The date and time the RPKI-RTR session last
                    transitioned in or out of the UP state.";

Liu, et al.               Expires 24 April 2027                [Page 22]
Internet-Draft           YANG Data Model for RTR            October 2026

                 reference
                   "RFC 6810: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol";
               }
               leaf last-update-sync {
                 type yang:date-and-time;
                 description
                   "The date and time of the last serial sync with the
                    cache server.";
               }
               leaf last-full-sync {
                 type yang:date-and-time;
                 description
                   "The date and time of the last reset sync with the
                    cache server.";
               }
               leaf last-serial-query {
                 type yang:date-and-time;
                 description
                   "The date and time the last serial query was sent to
                    the cache server.";
               }
               leaf last-reset-query {
                 type yang:date-and-time;
                 description
                   "The date and time the last reset query was sent to
                    the cache server.";
               }
               leaf last-eod-received {
                 type yang:date-and-time;
                 description
                   "The date and time the last EOD was received.";
               }
               leaf last-config-change {
                 type yang:date-and-time;
                 description
                   "The date and time of the last host, port, VRF or
                    local interface change.";
               }
               leaf last-error {
                 type yang:date-and-time;
                 description
                   "The date and time of the last protocol error sent to
                    or received from the cache server.";
               }
               leaf last-connection-error {
                 type yang:date-and-time;
                 description

Liu, et al.               Expires 24 April 2027                [Page 23]
Internet-Draft           YANG Data Model for RTR            October 2026

                   "The date and time of the last connection error to
                    the cache server.";
               }
               leaf last-connection {
                 type yang:date-and-time;
                 description
                   "The date and time of the last connection to the
                    cache server.";
               }
               leaf error-reason {
                 type string;
                 description
                   "Reason for error in connection.";
               }
             }
             container protocol-data {
               description
                 "Parameters related to the RTR protocol.";
               leaf preferred-protocol-version {
                 type uint8;
                 description
                   "The preferred version number of the RTR protocol
                    to be used when establishing the session. If not
                    configured, the router will use its default
                    protocol version.";
               }
               leaf refresh-interval {
                 type uint32 {
                   range "1..86400";
                 }
                 default 3600;
                 description
                   "Number of seconds a router waits in between
                    sending periodic serial queries to the RPKI
                    cache server. If configured, this value
                    overrides the value announced by the cache
                    server in the End of Data PDU.";
                 reference
                   "RFC ZZZZ: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol, Version 2,
                              Section 6";
               }
               leaf retry-interval {
                 type uint32 {
                   range "1..7200";
                 }
                 default 600;
                 description

Liu, et al.               Expires 24 April 2027                [Page 24]
Internet-Draft           YANG Data Model for RTR            October 2026

                   "Number of seconds between poll error and cache
                    server poll. If configured, this value
                    overrides the value announced by the cache
                    server in the End of Data PDU.";
                 reference
                   "RFC ZZZZ: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol, Version 2,
                              Section 6";
               }
               leaf expire-interval {
                 type uint32 {
                   range "600..172800";
                 }
                 default 7200;
                 description
                   "Number of seconds to retain data synced from
                    cache server. If configured, this value
                    overrides the value announced by the cache
                    server in the End of Data PDU.";
                 reference
                   "RFC ZZZZ: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol, Version 2,
                              Section 6";
               }
               leaf hold-interval {
                 type uint32;
                 description
                   "Maximum number of seconds to wait without receiving
                    any RTR PDUs from the cache server before tearing
                    down the RTR session. Any incoming PDU resets this
                    timer. The hold-interval value must be at least
                    twice the configured refresh-interval. If not
                    configured, implementations should choose a value
                    that is at least twice the configured
                    refresh-interval.";
               }
               leaf protocol-version {
                 type uint8;
                 config false;
                 description
                   "The negotiated version number of the RTR protocol
                    currently in use for this session.";
               }
               leaf refresh-time {
                 type yang:date-and-time;
                 config false;
                 description
                   "The date and time when the next refresh of RPKI

Liu, et al.               Expires 24 April 2027                [Page 25]
Internet-Draft           YANG Data Model for RTR            October 2026

                    data from the RPKI cache server will occur.";
               }
               leaf response-time {
                 type yang:date-and-time;
                 config false;
                 description
                   "The date and time when a response to a serial or
                    reset query to the RPKI cache server is expected.";
               }
               leaf record-lifetime {
                 type yang:date-and-time;
                 config false;
                 description
                   "The date and time when the records received from
                    the RPKI cache server will expire.";
               }
               leaf hold-time {
                 type yang:date-and-time;
                 config false;
                 description
                   "The date and time when the RTR session will be torn
                    down if no RTR PDUs are received from the cache
                    server.";
               }
               leaf session-id {
                 type uint16;
                 config false;
                 description
                   "When a cache server is started, it generates a
                    Session ID to identify the instance of the cache
                    and to bind it to the sequence of Serial Numbers
                    that cache instance will generate.";
                 reference
                   "RFC 6810: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol
                    RFC 8210: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol, Version 1";
               }
               leaf serial-full {
                 type uint32;
                 config false;
                 description
                   "A 32-bit strictly increasing unsigned integer which
                    wraps from 2^32-1 to 0. It denotes the logical
                    version of a cache. It resembles the latest full
                    query.";
                 reference
                   "RFC 6810: The Resource Public Key Infrastructure

Liu, et al.               Expires 24 April 2027                [Page 26]
Internet-Draft           YANG Data Model for RTR            October 2026

                              (RPKI) to Router Protocol
                    RFC 8210: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol, Version 1";
               }
               leaf serial-incremental {
                 type uint32;
                 config false;
                 description
                   "A 32-bit strictly increasing unsigned integer which
                    wraps from 2^32-1 to 0. It denotes the logical
                    version of a cache. It resembles the latest
                    incremental query.";
                 reference
                   "RFC 6810: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol
                    RFC 8210: The Resource Public Key Infrastructure
                              (RPKI) to Router Protocol, Version 1";
               }
             }
             container pdu-counters {
               config false;
               description
                 "Counters of RTR PDUs exchanged with the RPKI cache
                  server, by PDU type.";
               leaf serial-notify {
                 type yang:zero-based-counter64;
                 description
                   "Serial Notify (PDU Type 0) count.";
               }
               leaf serial-query {
                 type yang:zero-based-counter64;
                 description
                   "Serial Query (PDU Type 1) count.";
               }
               leaf reset-query {
                 type yang:zero-based-counter64;
                 description
                   "Reset Query (PDU Type 2) count.";
               }
               leaf cache-response {
                 type yang:zero-based-counter64;
                 description
                   "Cache Response (PDU Type 3) count.";
               }
               leaf ipv4-prefix {
                 type yang:zero-based-counter64;
                 description
                   "IPv4 Prefix (PDU Type 4) count.";

Liu, et al.               Expires 24 April 2027                [Page 27]
Internet-Draft           YANG Data Model for RTR            October 2026

               }
               leaf ipv6-prefix {
                 type yang:zero-based-counter64;
                 description
                   "IPv6 Prefix (PDU Type 6) count.";
               }
               leaf end-of-data {
                 type yang:zero-based-counter64;
                 description
                   "End of Data (PDU Type 7) count.";
               }
               leaf cache-reset {
                 type yang:zero-based-counter64;
                 description
                   "Cache Reset (PDU Type 8) count.";
               }
               leaf router-key {
                 type yang:zero-based-counter64;
                 description
                   "Router Key (PDU Type 9) count.";
               }
               leaf aspa {
                 type yang:zero-based-counter64;
                 description
                   "ASPA (PDU Type 11) count.";
               }
             }
             container error-pdu-counters {
               config false;
               description
                 "Counters of Error Report PDUs exchanged with the
                  RPKI cache server, by error code.";
               leaf corrupt-data {
                 type yang:zero-based-counter64;
                 description
                   "Corrupt Data (Error Code 0) Error Report PDU
                    count.";
               }
               leaf internal-error {
                 type yang:zero-based-counter64;
                 description
                   "Internal Error (Error Code 1) Error Report PDU
                    count.";
               }
               leaf no-data-available {
                 type yang:zero-based-counter64;
                 description
                   "No Data Available (Error Code 2) Error Report PDU

Liu, et al.               Expires 24 April 2027                [Page 28]
Internet-Draft           YANG Data Model for RTR            October 2026

                    count.";
               }
               leaf invalid-request {
                 type yang:zero-based-counter64;
                 description
                   "Invalid Request (Error Code 3) Error Report PDU
                    count.";
               }
               leaf unsupported-protocol-version {
                 type yang:zero-based-counter64;
                 description
                   "Unsupported Protocol Version (Error Code 4) Error
                    Report PDU count.";
               }
               leaf unsupported-pdu-type {
                 type yang:zero-based-counter64;
                 description
                   "Unsupported PDU Type (Error Code 5) Error Report
                    PDU count.";
               }
               leaf withdrawal-unknown-record {
                 type yang:zero-based-counter64;
                 description
                   "Withdrawal of Unknown Record (Error Code 6) Error
                    Report PDU count.";
               }
               leaf duplicate-announcement-received {
                 type yang:zero-based-counter64;
                 description
                   "Duplicate Announcement Received (Error Code 7)
                    Error Report PDU count.";
               }
               leaf unexpected-protocol-version {
                 type yang:zero-based-counter64;
                 description
                   "Unexpected Protocol Version (Error Code 8) Error
                    Report PDU count.";
               }
               leaf aspa-provider-list-error {
                 type yang:zero-based-counter64;
                 description
                   "ASPA Provider List Error (Error Code 9) Error
                    Report PDU count.";
               }
               leaf transport-failure {
                 type yang:zero-based-counter64;
                 description
                   "Transport Failure (Error Code 10) Error Report

Liu, et al.               Expires 24 April 2027                [Page 29]
Internet-Draft           YANG Data Model for RTR            October 2026

                    PDU count.";
               }
               leaf ordering-error {
                 type yang:zero-based-counter64;
                 description
                   "Ordering Error (Error Code 11) Error Report PDU
                    count.";
               }
               leaf cache-restart {
                 type yang:zero-based-counter64;
                 description
                   "Cache Restart (Error Code 12) Error Report PDU
                    count.";
               }
               leaf cache-shutdown {
                 type yang:zero-based-counter64;
                 description
                   "Cache Shutdown (Error Code 13) Error Report PDU
                    count.";
               }
             }
           }
         }
       }
     }
   }
   <CODE ENDS>

5.  RPKI Table YANG Module

5.1.  Tree View

   The full tree of the "ietf-rpki-table" YANG module is provided in
   Appendix B.  The following subsections list the subtree structures.

5.1.1.  Overall Structure

   The overall tree structure of the "ietf-rpki-table" YANG module is
   shown in Figure 12.

   The "ietf-rpki-table" YANG module also augments the core routing YANG
   module "ietf-routing" specified in [RFC8349].  Specifically, this
   YANG module augments "/rt:routing".

Liu, et al.               Expires 24 April 2027                [Page 30]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-table
     augment /rt:routing:
       +--ro vrp-tables
       |  +--ro vrp-table* [name]
       |     ...
       +--ro router-key-tables
       |  +--ro router-key-table* [name]
       |     ...
       +--ro aspa-tables
          +--ro aspa-table* [name]
             ...

                Figure 12: Overall RPKI Table Tree Structure

   The "ietf-rpki-table" YANG module has three containers: 'vrp-tables',
   'router-key-tables', and 'aspa-tables'.

   The 'vrp-tables' container lists the VRP records received from all
   RPKI cache servers, and each list 'vrp-table' identifies a VRP record
   table received from a RPKI cache server.

   The 'router-key-tables' container lists the Router Key records
   received from all RPKI cache servers, and each list 'router-key-
   table' identifies a Router Key record table received from a RPKI
   cache server.

   The 'aspa-tables' container lists the ASPA records received from all
   RPKI cache servers, and each list 'aspa-table' identifies an ASPA
   record table received from a RPKI cache server.

5.1.2.  VRP Table

   The structure of the list 'vrp-table' is shown in Figure 13.

Liu, et al.               Expires 24 April 2027                [Page 31]
Internet-Draft           YANG Data Model for RTR            October 2026

   module: ietf-rpki-table
     augment /rt:routing:
       +--ro vrp-tables
       |  +--ro vrp-table* [name]
       |     +--ro name                      string
       |     +--ro ccr-roapayloadstate-hash? ccr-hash
       |     +--ro ipv4
       |     |  +--ro vrps
       |     |  |  +--ro vrp* [prefix max-len asn source]
       |     |  |     +--ro prefix       inet:ipv4-prefix
       |     |  |     +--ro max-len      ipv4-prefix-length
       |     |  |     +--ro asn          inet:as-number
       |     |  |     +--ro source       union
       |     |  +--ro total-records?     yang:gauge32
       |     |  +--ro records-added?     yang:counter64
       |     |  +--ro records-deleted?   yang:counter64
       |     +--ro ipv6
       |        +--ro vrps
       |        |  +--ro vrp* [prefix max-len asn source]
       |        |     +--ro prefix       inet:ipv6-prefix
       |        |     +--ro max-len      ipv6-prefix-length
       |        |     +--ro asn          inet:as-number
       |        |     +--ro source       union
       |        +--ro total-records?     yang:gauge32
       |        +--ro records-added?     yang:counter64
       |        +--ro records-deleted?   yang:counter64
       +--ro router-key-tables
       |  +--ro router-key-table* [name]
       |     ...
       +--ro aspa-tables
          +--ro aspa-table* [name]
             ...

                Figure 13: RPKI VRP Table Subtree Structure

   The 'vrp-table' data nodes are described as follows:

   'name': Indicates the name of the VRP table.

   'ccr-roapayloadstate-hash': Indicates the CCR state hash for the ROA
   payload.

   'ipv4': Indicates detailed information and statistics of IPv4 VRP
   records in the VRP table.

Liu, et al.               Expires 24 April 2027                [Page 32]
Internet-Draft           YANG Data Model for RTR            October 2026

     This data node includes 'vrps', 'total-records', 'records-added',
     and 'records-deleted'. The 'vrps' indicates all IPv4 VRP records
     in the VRP table, and each list 'vrp' indicates an IPv4 VRP
     record, which includes the IPv4 prefix ('prefix'), the maximum
     IPv4 prefix length ('max-len'), the origin AS number of the IPv4
     prefix ('asn'), and the source of the IPv4 VRP record ('source').
     The 'total-records' indicates the total number of IPv4 VRP
     records. The 'records-added' indicates the number of IPv4 VRP
     records cumulatively added. The 'records-deleted' indicates the
     number of IPv4 VRP records cumulatively deleted.

   'ipv6': Indicates detailed information and statistics of IPv6 VRP
   records in the VRP table.

     This data node has the same structure as the data node 'ipv4'.
     The 'vrps' indicates all IPv6 VRP records in the VRP table, and
     each list 'vrp' indicates an IPv6 VRP record, which includes the
     IPv6 prefix ('prefix'), the maximum IPv6 prefix length
     ('max-len'), the origin AS number of the IPv6 prefix ('asn'), and
     the source of the IPv6 VRP record ('source'). The 'total-records'
     indicates the total number of IPv6 VRP records. The
     'records-added' indicates the number of IPv6 VRP records
     cumulatively added. The 'records-deleted' indicates the number of
     IPv6 VRP records cumulatively deleted.

5.1.3.  Router Key Table

   The structure of the list 'router-key-table' is shown in Figure 14.

   module: ietf-rpki-table
     augment /rt:routing:
       +--ro vrp-tables
       |  +--ro vrp-table* [name]
       |     ...
       +--ro router-key-tables
       |  +--ro router-key-table* [name]
       |     +--ro name                     string
       |     +--ro ccr-routerkeystate-hash? ccr-hash
       |     +--ro router-keys
       |        +--ro router-key* [ski asn key server-address]
       |           +--ro ski            subject-key-id
       |           +--ro asn            inet:as-number
       |           +--ro key            binary
       |           +--ro server-address inet:ip-address
       +--ro aspa-tables
          +--ro aspa-table* [name]
             ...

Liu, et al.               Expires 24 April 2027                [Page 33]
Internet-Draft           YANG Data Model for RTR            October 2026

             Figure 14: RPKI Router Key Table Subtree Structure

   The 'router-key-table' data nodes are described as follows:

   'name': Indicates the name of the Router Key table.

   'ccr-routerkeystate-hash': Indicates the CCR state hash for the
   Router Key payload.

   'router-keys': Indicates detailed information of Router Key records
   in the Router Key table.

     This data node only includes a list 'router-key', which contains
     the Subject Key Identifier (SKI) of the Router Key ('ski'), the
     AS number of the router which the Router Key belongs to ('asn'),
     the subjectPublicKeyInfo value of the Router Key (see [RFC8608])
     ('key'), and the IP address of the RPKI cache server
     ('server-address').

5.1.4.  ASPA Table

   The structure of the list 'aspa-table' is shown in Figure 15.

   module: ietf-rpki-table
     augment /rt:routing:
       +--ro vrp-tables
       |  +--ro vrp-table* [name]
       |     ...
       +--ro router-key-tables
       |  +--ro router-key-table* [name]
       |     ...
       +--ro aspa-tables
          +--ro aspa-table* [name]
             +--ro name                       string
             +--ro ccr-aspapayloadstate-hash? ccr-hash
             +--ro aspas* [customer-asn]
                +--ro customer-asn        inet:as-number
                +--ro server-address?     inet:ip-address
                +--ro provider-asns* [provider-asn]
                   +--ro provider-asn     inet:as-number

                Figure 15: RPKI ASPA Table Subtree Structure

   The 'aspa-table' data nodes are described as follows:

   'name': Indicates the name of the ASPA table.

Liu, et al.               Expires 24 April 2027                [Page 34]
Internet-Draft           YANG Data Model for RTR            October 2026

   'ccr-aspapayloadstate-hash': Indicates the CCR state hash for the
   ASPA payload.

   'aspas': Indicates detailed information of ASPA records in the ASPA
   table.

     This data node includes a leaf 'customer-asn', a leaf
     'server-address', and a list 'provider-asns'. The 'customer-asn'
     indicates the AS number of a customer. The 'server-address'
     indicates the IP address of the RPKI cache server from which ASPA
     records are received. The list 'provider-asns' contains a leaf
     'provider-asn' which indicates the AS number of a provider of the
     customer.

5.2.  YANG Module

   This YANG module has normative references to [RFC6487], [RFC8349],
   [RFC8608], [RFC9911], [I-D.ietf-sidrops-8210bis], and
   [I-D.ietf-sidrops-rpki-ccr].

     Note that the "RFC YYYY" in this YANG module must be replaced by
     the publication version of [I-D.ietf-sidrops-rpki-ccr], and the
     "RFC ZZZZ" must be replaced by the publication version of
     [I-D.ietf-sidrops-8210bis]. This note is to be removed after the
     publication of [I-D.ietf-sidrops-rpki-ccr] and
     [I-D.ietf-sidrops-8210bis].

   <CODE BEGINS> file "ietf-rpki-table@2026-10-15.yang"
   module ietf-rpki-table {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-rpki-table";
     prefix rpki-table;

     import ietf-yang-types {
       prefix yang;
       reference
         "RFC 9911: Common YANG Data Types";
     }
     import ietf-inet-types {
       prefix inet;
       reference
         "RFC 9911: Common YANG Data Types";
     }
     import ietf-routing {
       prefix rt;
       reference
         "RFC 8349: A YANG Data Model for Routing Management
                    (NMDA Version)";

Liu, et al.               Expires 24 April 2027                [Page 35]
Internet-Draft           YANG Data Model for RTR            October 2026

     }

     organization
       "IETF Secure Inter-Domain Routing Operations (SIDROPS)
        Working Group";
     contact
       "WG Web:   <https://datatracker.ietf.org/wg/sidrops/>
        WG List:  SIDROPS <mailto:sidrops@ietf.org>

        Editor:   Yisong Liu
                  <mailto:liuyisong@chinamobile.com>
        Editor:   Changwang Lin
                  <mailto:linchangwang.04414@h3c.com>
        Editor:   Haibo Wang
                  <mailto:rainsword.wang@huawei.com>
        Editor:   Jishnu Roy
                  <mailto:jishnu.roy@hpe.com>
        Editor:   Jeffrey Haas
                  <mailto:jeffrey.haas@hpe.com>
        Editor:   Hongwei Liu
                  <mailto:liu.hongwei3@zte.com.cn>
        Editor:   Di Ma
                  <mailto:madi@zdns.cn>";
     description
       "This module describes a YANG model for the Resource Public
        Key Infrastructure (RPKI) to Router (RTR) protocol data
        management.

        The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
        NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
        'MAY', and 'OPTIONAL' in this document are to be interpreted as
        described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
        they appear in all capitals, as shown here.

        Copyright (c) 2026 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 Revised BSD License set
        forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (https://trustee.ietf.org/license-info).

        All revisions of IETF and IANA published modules can be found
        at the YANG Parameters registry group
        (https://www.iana.org/assignments/yang-parameters).

Liu, et al.               Expires 24 April 2027                [Page 36]
Internet-Draft           YANG Data Model for RTR            October 2026

        This version of this YANG module is part of RFC XXXX; see the
        RFC itself for full legal notices.";

     revision 2026-10-15 {
       description
         "Initial Version";
       reference
         "RFC XXXX: YANG Data Model for RPKI to Router Protocol";
     }

     typedef ipv4-prefix-length {
       type uint8 {
         range "0 .. 32";
       }
       description
         "IPv4 Prefix Length.";
     }

     typedef ipv6-prefix-length {
       type uint8 {
         range "0 .. 128";
       }
       description
         "IPv6 Prefix Length.";
     }

     typedef subject-key-id {
       type binary {
         length "20";
       }
       description
         "Subject Key Identifier.";
     }

     typedef ccr-hash {
       type binary {
         length "32";
       }
       description
         "Canonical Cache Representation (CCR) state hash.

          This represents a 256-bit SHA-256 hash of the canonical
          representation of RPKI data as defined in RFC YYYY.

          The hash provides a compact, verifiable representation
          of the complete state of RPKI validation data, enabling
          efficient synchronization and consistency verification
          between caches.";

Liu, et al.               Expires 24 April 2027                [Page 37]
Internet-Draft           YANG Data Model for RTR            October 2026

       reference
         "RFC YYYY: A Profile for Resource Public Key Infrastructure
                    (RPKI) Canonical Cache Representation (CCR)";
     }

     grouping aspa-overall-records {
       description
         "Autonomous System Provider Authorization (ASPA) records
          received from all RPKI cache servers.";
       reference
         "RFC ZZZZ: The Resource Public Key Infrastructure (RPKI) to
                    Router Protocol, Version 2";
       list aspas {
         key "customer-asn";
         description
           "An entry for ASPA.";
         leaf customer-asn {
           type inet:as-number;
           description
             "The AS number of a customer.";
         }
         leaf server-address {
           type inet:ip-address;
           description
             "IP address of the RPKI cache server.";
         }
         list provider-asns {
           key "provider-asn";
           description
             "Providers of the customer.";
           leaf provider-asn {
             type inet:as-number;
             description
               "The AS number of a provider.";
           }
         }
       }
     }

     augment "/rt:routing" {
       description
         "RPKI tables augmentation of ietf-routing module.";
       container vrp-tables {
         config false;
         description
           "List of tables containing Validated ROA Payloads
            received from all RPKI cache servers.";
         list vrp-table {

Liu, et al.               Expires 24 April 2027                [Page 38]
Internet-Draft           YANG Data Model for RTR            October 2026

           key "name";
           description
             "Table of Validated ROA Payloads received from
              a RPKI cache server.";
           leaf name {
             type string;
             description
               "Name of the Validated ROA Payload table.";
           }
           leaf ccr-roapayloadstate-hash {
             type ccr-hash;
             description
               "CCR state hash for the ROA payload.

                This hash represents the canonical state of this
                specific ROA entry as defined in the CCR specification.
                It is optional and can be used to verify the integrity
                and consistency of ROA data originating from the RPKI
                cache.";
             reference
               "RFC YYYY: A Profile for Resource Public Key
                          Infrastructure (RPKI) Canonical Cache
                          Representation (CCR)";
           }
           container ipv4 {
             config false;
             description
               "Container for IPv4 Validated ROA Payloads table.";
             container vrps {
               config false;
               description
                 "IPv4 Validated ROA Payloads received from the RPKI
                  cache server.";
               list vrp {
                 key "prefix max-len asn source";
                 description
                   "An entry of IPv4 Validated ROA Payload.";
                 leaf prefix {
                   type inet:ipv4-prefix;
                   description
                     "The IPv4 prefix of the IPv4 Validated ROA
                      Payload.";
                 }
                 leaf max-len {
                   type ipv4-prefix-length;
                   description
                     "Denotes the longest IPv4 prefix allowed. This
                      MUST NOT be less than the IPv4 prefix length.";

Liu, et al.               Expires 24 April 2027                [Page 39]
Internet-Draft           YANG Data Model for RTR            October 2026

                 }
                 leaf asn {
                   type inet:as-number;
                   description
                     "The origin AS number of the IPv4 Validated ROA
                      Payload.";
                 }
                 leaf source {
                   type union {
                     type inet:ip-address;
                     type string;
                   }
                   description
                     "String representing the source of the record
                      in this record-set.";
                 }
               }
             }
             leaf total-records {
               type yang:gauge32;
               description
                 "Total number of IPv4 Validated ROA Payload records.";
             }
             leaf records-added {
               type yang:counter64;
               description
                 "Number of IPv4 Validated ROA Payload records
                  cumulatively added.";
             }
             leaf records-deleted {
               type yang:counter64;
               description
                 "Number of IPv4 Validated ROA Payload records
                  cumulatively deleted.";
             }
           }
           container ipv6 {
             config false;
             description
               "Container for IPv6 Validated ROA Payloads table.";
             container vrps {
               config false;
               description
                 "IPv6 Validated ROA Payloads received from the RPKI
                  cache server.";
               list vrp {
                 key "prefix max-len asn source";
                 description

Liu, et al.               Expires 24 April 2027                [Page 40]
Internet-Draft           YANG Data Model for RTR            October 2026

                   "An entry for IPv6 Validated ROA Payload.";
                 leaf prefix {
                   type inet:ipv6-prefix;
                   description
                     "The IPv6 prefix of the IPv6 Validated ROA
                      Payload.";
                 }
                 leaf max-len {
                   type ipv6-prefix-length;
                   description
                     "Denotes the longest IPv6 prefix allowed. This
                      MUST NOT be less than the prefix length.";
                 }
                 leaf asn {
                   type inet:as-number;
                   description
                     "The origin AS number of the IPv6 Validated ROA
                      Payload.";
                 }
                 leaf source {
                   type union {
                     type inet:ip-address;
                     type string;
                   }
                   description
                     "Representing the source of the record in this
                      record-set. Either a server IP or a source file
                      of static records.";
                 }
               }
             }
             leaf total-records {
               type yang:gauge32;
               description
                 "Total number of IPv6 Validated ROA Payload records.";
             }
             leaf records-added {
               type yang:counter64;
               description
                 "Number of IPv6 Validated ROA Payload records
                  cumulatively added.";
             }
             leaf records-deleted {
               type yang:counter64;
               description
                 "Number of IPv6 Validated ROA Payload records
                  cumulatively deleted.";
             }

Liu, et al.               Expires 24 April 2027                [Page 41]
Internet-Draft           YANG Data Model for RTR            October 2026

           }
         }
       }
       container router-key-tables {
         config false;
         description
           "List of Router Key table received from all RPKI cache
            servers.";
         list router-key-table {
           key "name";
           description
             "Table of Router Keys received from a RPKI cache
              server.";
           leaf name {
             type string;
             description
               "Name of the Router Key table.";
           }
           leaf ccr-routerkeystate-hash {
             type ccr-hash;
             description
               "CCR state hash for the Router Key payload.

                This hash represents the canonical state of this
                specific Router Key entry as defined in the CCR
                specification. It is optional and can effectively
                verify the consistency of BGPsec Router Key data
                derived from the RPKI cache.";
             reference
               "RFC YYYY: A Profile for Resource Public Key
                          Infrastructure (RPKI) Canonical Cache
                          Representation (CCR)";
           }
           container router-keys {
             config false;
             description
               "Router Keys received from the RPKI cache server.";
             list router-key {
               key "ski asn key server-address";
               description
                 "An entry for Router Key.";
               leaf ski {
                 type subject-key-id;
                 description
                   "A Router Key's Subject Key Identifier (SKI).";
                 reference
                   "RFC 6487: A Profile for X.509 PKIX Resource
                              Certificates";

Liu, et al.               Expires 24 April 2027                [Page 42]
Internet-Draft           YANG Data Model for RTR            October 2026

               }
               leaf asn {
                 type inet:as-number;
                 description
                   "The AS number of the router which the key
                    belongs to.";
               }
               leaf key {
                 type binary;
                 description
                   "A Router Key's subjectPublicKeyInfo value, as
                    described in Section 3.1.1 of RFC 8608, encoded
                    using ASN.1 Distinguished Encoding Rules (DER).";
                 reference
                   "RFC 8608: BGPsec Algorithms, Key Formats, and
                              Signature Formats";
               }
               leaf server-address {
                 type inet:ip-address;
                 description
                   "IP address of the RPKI cache server.";
               }
             }
           }
         }
       }
       container aspa-tables {
         config false;
         description
           "List of tables of ASPAs received from all RPKI cache
            servers.";
         list aspa-table {
           key "name";
           description
             "Table of ASPAs received from a RPKI cache server.";
           leaf name {
             type string;
             description
               "Name of the ASPA table.";
           }
           leaf ccr-aspapayloadstate-hash {
             type ccr-hash;
             description
               "CCR state hash for the ASPA payload.

                This hash represents the canonical state of this
                specific ASPA entry as defined in the CCR
                specification. It is optional and facilitates

Liu, et al.               Expires 24 April 2027                [Page 43]
Internet-Draft           YANG Data Model for RTR            October 2026

                consistency checking for AS path validation data
                originating from the RPKI cache.";
             reference
               "RFC YYYY: A Profile for Resource Public Key
                          Infrastructure (RPKI) Canonical Cache
                          Representation (CCR)";
           }
           uses aspa-overall-records;
         }
       }
     }
   }
   <CODE ENDS>

6.  Implementation Status

   Note to the RFC Editor - remove this section before publication, as
   well as remove the reference to [RFC7942].

   This section records the status of known implementations of the
   protocol defined by this specification at the time of posting of this
   Internet-Draft, and is based on a proposal described in [RFC7942].
   The description of implementations in this section is intended to
   assist the IETF in its decision processes in progressing drafts to
   RFCs.  Please note that the listing of any individual implementation
   here does not imply endorsement by the IETF.  Furthermore, no effort
   has been spent to verify the information presented here that was
   supplied by IETF contributors.  This is not intended as, and must not
   be construed to be, a catalog of available implementations or their
   features.  Readers are advised to note that other implementations may
   exist.

   According to [RFC7942], "this will allow reviewers and working groups
   to assign due consideration to documents that have the benefit of
   running code, which may serve as evidence of valuable experimentation
   and feedback that have made the implemented protocols more mature.
   It is up to the individual working groups to use this information as
   they see fit".

6.1.  Juniper Networks (HPE)

   *  Organization: Juniper Networks (HPE).

   *  Implementation: The following leaves/parameters in description are
      implemented.

   *  Description: YANG model leaves that are supported:

Liu, et al.               Expires 24 April 2027                [Page 44]
Internet-Draft           YANG Data Model for RTR            October 2026

      -  Ietf-rpki-rtr.yang

           Server-address
           Session-state
           Total-vrp-records
           Ipv4-vrp-records
           Ipv6-vrp-records
           Refresh-time
           Hold-time
           Serial-incremental
           Serial-full
           Last-session-up-down
           Last-update-sync
           Last-eod-received
           Last-serial-query
           Last-reset-query
           Flaps

      -  Ietf-rpki-table.yang

           Ipv4 | ipv6:
             Total-records
             Records-added
             Records-deleted.

   *  Maturity Level: Ready-for-deployment

   *  Coverage:

   *  Version: Draft-03

   *  Licensing: N/A

   *  Implementation experience: Nothing specific.

   *  Contact: jishnu.roy@hpe.com

   *  Last updated: March 30, 2026

6.2.  New H3C Technologies

   *  Organization: New H3C Technologies.

   *  Implementation: The following leaves/parameters in description are
      implemented.

   *  Description: "ietf-rpki-rtr" and "ietf-rpki-table" YANG modules
      have been implemented in New H3C Products.

Liu, et al.               Expires 24 April 2027                [Page 45]
Internet-Draft           YANG Data Model for RTR            October 2026

   *  Maturity Level: Ready-for-deployment

   *  Coverage: All data nodes of "ietf-rpki-rtr" and "ietf-rpki-table"
      YANG modules.

   *  Version: Draft-03

   *  Licensing: N/A

   *  Implementation experience: Nothing specific.

   *  Contact: li_meng_limeng@h3c.com

   *  Last updated: March 30, 2026

7.  Security Considerations

   This section is modeled after the template described in Section 3.7.1
   of [RFC9907].

   The "ietf-rpki-rtr" YANG module and "ietf-rpki-table" YANG module
   define data models that are designed to be accessed via YANG-based
   management protocols, such as Network Configuration Protocol
   (NETCONF) [RFC6241] and RESTCONF [RFC8040].  These YANG-based
   management protocols (1) have to use a secure transport layer (e.g.,
   Secure Shell (SSH) [RFC4252], TLS [RFC9846], and QUIC [RFC9000]) and
   (2) have to use mutual authentication.

   The Network Configuration Access Control Model (NACM) [RFC8341]
   provides the means to restrict access for particular NETCONF or
   RESTCONF users to a preconfigured subset of all available NETCONF or
   RESTCONF protocol operations and content.

   There are a number of data nodes defined in these YANG modules that
   are writable/creatable/deletable (i.e., config true, which is the
   default).  All writable data nodes are likely to be sensitive or
   vulnerable in some network environments.  Write operations (e.g.,
   edit-config) and delete operations to these data nodes without proper
   protection or authentication can have a negative effect on network
   operations.  The following subtrees and data nodes have particular
   sensitivities/vulnerabilities:

Liu, et al.               Expires 24 April 2027                [Page 46]
Internet-Draft           YANG Data Model for RTR            October 2026

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:server-address

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:server-port

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:local-address

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:local-port

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:enabled

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:preference

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:description

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:enable-authentication

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:authentication

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:vrp-limit

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:aspa-limit

   Some of the readable data nodes in these YANG modules may be
   considered sensitive or vulnerable in some network environments.  It
   is thus important to control read access (e.g., via get, get-config,
   or notification) to these data nodes.  Specifically, the following
   subtrees and data nodes have particular sensitivities/
   vulnerabilities:

Liu, et al.               Expires 24 April 2027                [Page 47]
Internet-Draft           YANG Data Model for RTR            October 2026

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:session-state

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:statistics

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:connection-data

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:protocol-data

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:pdu-counters

     rpki-rtr:rpki-rtr/rpki-rtr:sessions/rpki-rtr:session/rpki-
     rtr:error-pdu-counters

     rt:routing/rpki-table:vrp-tables/rpki-table:vrp-table

     rt:routing/rpki-table:router-key-tables/rpki-table:router-key-
     table

     rt:routing/rpki-table:aspa-tables/rpki-table:aspa-table

   There are no particularly sensitive RPC or action operations.

8.  IANA Considerations

8.1.  RPKI to Router YANG Module Registry

   IANA is requested to register the following URI in the "ns" registry
   within the "IETF XML Registry" group ([RFC3688]):

      URI: urn:ietf:params:xml:ns:yang:ietf-rpki-rtr
      Registrant Contact: The IESG.
      XML: N/A; the requested URI is an XML namespace

   IANA is requested to register the following YANG modules in the "YANG
   Module Names" registry ([RFC6020]) within the "YANG Parameters"
   registry group.

      Name: ietf-rpki-rtr
      Maintained by IANA? N
      Namespace: urn:ietf:params:xml:ns:yang:ietf-rpki-rtr
      Prefix: rpki-rtr
      Reference: RFC XXXX

Liu, et al.               Expires 24 April 2027                [Page 48]
Internet-Draft           YANG Data Model for RTR            October 2026

8.2.  RPKI Table YANG Module Registry

   IANA is requested to register the following URI in the "ns" registry
   within the "IETF XML Registry" group ([RFC3688]):

      URI: urn:ietf:params:xml:ns:yang:ietf-rpki-table
      Registrant Contact: The IESG.
      XML: N/A; the requested URI is an XML namespace

   IANA is requested to register the following YANG module in the "YANG
   Module Names" registry ([RFC6020]) within the "YANG Parameters"
   registry group.

      Name: ietf-rpki-table
      Maintained by IANA? N
      Namespace: urn:ietf:params:xml:ns:yang:ietf-rpki-table
      Prefix: rpki-table
      Reference: RFC XXXX

9.  Acknowledgments

   The authors would like to thank Job Snijders, Santosh Kolenchery,
   Ebben Xavier Aries, Tapasee Ratna Goutam and Haiyang Zhang for their
   review and discussion of this document.

   Thanks to Per Andersson for the Yangdoctors Early review.

10.  References

10.1.  Normative References

   [I-D.ietf-sidrops-8210bis]
              Bush, R., Austein, R., and T. Harrison, "The Resource
              Public Key Infrastructure (RPKI) to Router Protocol,
              Version 2", Work in Progress, Internet-Draft, draft-ietf-
              sidrops-8210bis-27, 13 August 2026,
              <https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-
              8210bis-27>.

   [I-D.ietf-sidrops-rpki-ccr]
              Snijders, J., Bakker, B., Bruijnzeels, T., and T. Buehler,
              "A Profile for Resource Public Key Infrastructure (RPKI)
              Canonical Cache Representation (CCR)", Work in Progress,
              Internet-Draft, draft-ietf-sidrops-rpki-ccr-11, 1 July
              2026, <https://datatracker.ietf.org/doc/html/draft-ietf-
              sidrops-rpki-ccr-11>.

Liu, et al.               Expires 24 April 2027                [Page 49]
Internet-Draft           YANG Data Model for RTR            October 2026

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <https://www.rfc-editor.org/info/rfc6020>.

   [RFC6487]  Huston, G., Michaelson, G., and R. Loomans, "A Profile for
              X.509 PKIX Resource Certificates", RFC 6487,
              DOI 10.17487/RFC6487, February 2012,
              <https://www.rfc-editor.org/info/rfc6487>.

   [RFC6810]  Bush, R. and R. Austein, "The Resource Public Key
              Infrastructure (RPKI) to Router Protocol", RFC 6810,
              DOI 10.17487/RFC6810, January 2013,
              <https://www.rfc-editor.org/info/rfc6810>.

   [RFC7317]  Bierman, A. and M. Bjorklund, "A YANG Data Model for
              System Management", RFC 7317, DOI 10.17487/RFC7317, August
              2014, <https://www.rfc-editor.org/info/rfc7317>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8177]  Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
              Zhang, "YANG Data Model for Key Chains", RFC 8177,
              DOI 10.17487/RFC8177, June 2017,
              <https://www.rfc-editor.org/info/rfc8177>.

   [RFC8210]  Bush, R. and R. Austein, "The Resource Public Key
              Infrastructure (RPKI) to Router Protocol, Version 1",
              RFC 8210, DOI 10.17487/RFC8210, September 2017,
              <https://www.rfc-editor.org/info/rfc8210>.

Liu, et al.               Expires 24 April 2027                [Page 50]
Internet-Draft           YANG Data Model for RTR            October 2026

   [RFC8294]  Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
              "Common YANG Data Types for the Routing Area", RFC 8294,
              DOI 10.17487/RFC8294, December 2017,
              <https://www.rfc-editor.org/info/rfc8294>.

   [RFC8341]  Bierman, A. and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, RFC 8341,
              DOI 10.17487/RFC8341, March 2018,
              <https://www.rfc-editor.org/info/rfc8341>.

   [RFC8343]  Bjorklund, M., "A YANG Data Model for Interface
              Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
              <https://www.rfc-editor.org/info/rfc8343>.

   [RFC8349]  Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
              Routing Management (NMDA Version)", RFC 8349,
              DOI 10.17487/RFC8349, March 2018,
              <https://www.rfc-editor.org/info/rfc8349>.

   [RFC8608]  Turner, S. and O. Borchert, "BGPsec Algorithms, Key
              Formats, and Signature Formats", RFC 8608,
              DOI 10.17487/RFC8608, June 2019,
              <https://www.rfc-editor.org/info/rfc8608>.

   [RFC9644]  Watsen, K., "YANG Groupings for SSH Clients and SSH
              Servers", RFC 9644, DOI 10.17487/RFC9644, October 2024,
              <https://www.rfc-editor.org/info/rfc9644>.

   [RFC9911]  Schowalder, J., Ed., "Common YANG Data Types", RFC 9911,
              DOI 10.17487/RFC9911, December 2025,
              <https://www.rfc-editor.org/info/rfc9911>.

10.2.  Informative References

   [RFC4252]  Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
              Authentication Protocol", RFC 4252, DOI 10.17487/RFC4252,
              January 2006, <https://www.rfc-editor.org/info/rfc4252>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.

   [RFC7942]  Sheffer, Y. and A. Farrel, "Improving Awareness of Running
              Code: The Implementation Status Section", BCP 205,
              RFC 7942, DOI 10.17487/RFC7942, July 2016,
              <https://www.rfc-editor.org/info/rfc7942>.

Liu, et al.               Expires 24 April 2027                [Page 51]
Internet-Draft           YANG Data Model for RTR            October 2026

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8340]  Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
              BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
              <https://www.rfc-editor.org/info/rfc8340>.

   [RFC9000]  Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
              Multiplexed and Secure Transport", RFC 9000,
              DOI 10.17487/RFC9000, May 2021,
              <https://www.rfc-editor.org/info/rfc9000>.

   [RFC9846]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 9846, DOI 10.17487/RFC9846, July 2026,
              <https://www.rfc-editor.org/info/rfc9846>.

   [RFC9907]  Bierman, A., Boucadair, M., Ed., and Q. Wu, "Guidelines
              for Authors and Reviewers of Documents Containing YANG
              Data Models", BCP 216, RFC 9907, DOI 10.17487/RFC9907,
              March 2026, <https://www.rfc-editor.org/info/rfc9907>.

Appendix A.  Full Tree of RPKI to Router YANG Module

   module: ietf-rpki-rtr
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
       +--rw rpki-rtr
          +--rw sessions
             +--rw session* [server-address]
                +--rw server-address           inet:ip-address
                +--rw server-port?             inet:port-number
                +--rw local-address?           union
                +--rw local-port?              inet:port-number
                +--rw enabled?                 boolean
                +--rw preference?              uint32
                +--rw description?             string
                +--rw reconnect-interval?      uint32
                +--ro session-state?           enumeration
                +--rw enable-authentication?   boolean
                +--rw authentication
                |  +--rw (option)?
                |     +--:(md5)
                |     |  +--rw md5-password?   ianach:crypt-hash
                |     +--:(ssh)
                |     |  +--rw client-identity
                |     |  |  +--rw username?  string
                |     |  |  +--rw public-key!

Liu, et al.               Expires 24 April 2027                [Page 52]
Internet-Draft           YANG Data Model for RTR            October 2026

                |     |  |                   {client-ident-publickey}?
                |     |  |  +--rw password!
                |     |  |                   {client-ident-password}?
                |     |  |  +--rw hostbased!
                |     |  |                   {client-ident-hostbased}?
                |     |  |  +--rw none?      empty {client-ident-none}?
                |     |  |  +--rw certificate!
                |     |  |                   {sshcmn:ssh-x509-certs}?
                |     |  +--rw server-authentication
                |     |  |  +--rw ssh-host-keys!
                |     |  |  +--rw ca-certs!  {sshcmn:ssh-x509-certs}?
                |     |  |  +--rw ee-certs!  {sshcmn:ssh-x509-certs}?
                |     |  +--rw transport-params
                |     |  |                 {sshcmn:transport-params}?
                |     |  +--rw keepalives!   {ssh-client-keepalives}?
                |     |     +--rw max-wait?       uint16
                |     |     +--rw max-attempts?   uint8
                |     +--:(tcp-ao-keychain)
                |        +--rw keychain-name?  key-chain:key-chain-ref
                +--rw vrp-limit
                |  +--rw max-number?              uint64
                |  +--rw threshold-percentage?    rt-types:percentage
                |  +--rw over-threshold-action?   enumeration
                +--rw aspa-limit
                |  +--rw max-number?              uint64
                |  +--rw threshold-percentage?    rt-types:percentage
                |  +--rw over-threshold-action?   enumeration
                +--ro statistics
                |  +--ro total-vrp-records?  yang:zero-based-counter64
                |  +--ro ipv4-vrp-records?   yang:zero-based-counter64
                |  +--ro ipv6-vrp-records?   yang:zero-based-counter64
                |  +--ro router-key-records? yang:zero-based-counter64
                |  +--ro aspa-records?       yang:zero-based-counter64
                |  +--ro in-total-messages?  yang:zero-based-counter64
                |  +--ro out-total-messages? yang:zero-based-counter64
                +--ro connection-data
                |  +--ro flaps?                       uint32
                |  +--ro last-session-up-down?        yang:date-and-time
                |  +--ro last-update-sync?            yang:date-and-time
                |  +--ro last-full-sync?              yang:date-and-time
                |  +--ro last-serial-query?           yang:date-and-time
                |  +--ro last-reset-query?            yang:date-and-time
                |  +--ro last-eod-received?           yang:date-and-time
                |  +--ro last-config-change?          yang:date-and-time
                |  +--ro last-error?                  yang:date-and-time
                |  +--ro last-connection-error?       yang:date-and-time
                |  +--ro last-connection?             yang:date-and-time
                |  +--ro error-reason?                string

Liu, et al.               Expires 24 April 2027                [Page 53]
Internet-Draft           YANG Data Model for RTR            October 2026

                +--rw protocol-data
                |  +--rw preferred-protocol-version?  uint8
                |  +--rw refresh-interval?            uint32
                |  +--rw retry-interval?              uint32
                |  +--rw expire-interval?             uint32
                |  +--rw hold-interval?               uint32
                |  +--ro protocol-version?            uint8
                |  +--ro refresh-time?                yang:date-and-time
                |  +--ro response-time?               yang:date-and-time
                |  +--ro record-lifetime?             yang:date-and-time
                |  +--ro hold-time?                   yang:date-and-time
                |  +--ro session-id?                  uint16
                |  +--ro serial-full?                 uint32
                |  +--ro serial-incremental?          uint32
                +--ro pdu-counters
                |  +--ro serial-notify?    yang:zero-based-counter64
                |  +--ro serial-query?     yang:zero-based-counter64
                |  +--ro reset-query?      yang:zero-based-counter64
                |  +--ro cache-response?   yang:zero-based-counter64
                |  +--ro ipv4-prefix?      yang:zero-based-counter64
                |  +--ro ipv6-prefix?      yang:zero-based-counter64
                |  +--ro end-of-data?      yang:zero-based-counter64
                |  +--ro cache-reset?      yang:zero-based-counter64
                |  +--ro router-key?       yang:zero-based-counter64
                |  +--ro aspa?             yang:zero-based-counter64
                +--ro error-pdu-counters
                   +--ro corrupt-data?      yang:zero-based-counter64
                   +--ro internal-error?    yang:zero-based-counter64
                   +--ro no-data-available? yang:zero-based-counter64
                   +--ro invalid-request?   yang:zero-based-counter64
                   +--ro unsupported-protocol-version?
                   |                        yang:zero-based-counter64
                   +--ro unsupported-pdu-type?
                   |                        yang:zero-based-counter64
                   +--ro withdrawal-unknown-record?
                   |                        yang:zero-based-counter64
                   +--ro duplicate-announcement-received?
                   |                        yang:zero-based-counter64
                   +--ro unexpected-protocol-version?
                   |                        yang:zero-based-counter64
                   +--ro aspa-provider-list-error?
                   |                        yang:zero-based-counter64
                   +--ro transport-failure?  yang:zero-based-counter64
                   +--ro ordering-error?      yang:zero-based-counter64
                   +--ro cache-restart?       yang:zero-based-counter64
                   +--ro cache-shutdown?      yang:zero-based-counter64

Liu, et al.               Expires 24 April 2027                [Page 54]
Internet-Draft           YANG Data Model for RTR            October 2026

Appendix B.  Full Tree of RPKI Table YANG Module

   module: ietf-rpki-table
     augment /rt:routing:
       +--ro vrp-tables
       |  +--ro vrp-table* [name]
       |     +--ro name                      string
       |     +--ro ccr-roapayloadstate-hash? ccr-hash
       |     +--ro ipv4
       |     |  +--ro vrps
       |     |  |  +--ro vrp* [prefix max-len asn source]
       |     |  |     +--ro prefix       inet:ipv4-prefix
       |     |  |     +--ro max-len      ipv4-prefix-length
       |     |  |     +--ro asn          inet:as-number
       |     |  |     +--ro source       union
       |     |  +--ro total-records?     yang:gauge32
       |     |  +--ro records-added?     yang:counter64
       |     |  +--ro records-deleted?   yang:counter64
       |     +--ro ipv6
       |        +--ro vrps
       |        |  +--ro vrp* [prefix max-len asn source]
       |        |     +--ro prefix       inet:ipv6-prefix
       |        |     +--ro max-len      ipv6-prefix-length
       |        |     +--ro asn          inet:as-number
       |        |     +--ro source       union
       |        +--ro total-records?     yang:gauge32
       |        +--ro records-added?     yang:counter64
       |        +--ro records-deleted?   yang:counter64
       +--ro router-key-tables
       |  +--ro router-key-table* [name]
       |     +--ro name                     string
       |     +--ro ccr-routerkeystate-hash? ccr-hash
       |     +--ro router-keys
       |        +--ro router-key* [ski asn key server-address]
       |           +--ro ski            subject-key-id
       |           +--ro asn            inet:as-number
       |           +--ro key            binary
       |           +--ro server-address inet:ip-address
       +--ro aspa-tables
          +--ro aspa-table* [name]
             +--ro name                       string
             +--ro ccr-aspapayloadstate-hash? ccr-hash
             +--ro aspas* [customer-asn]
                +--ro customer-asn        inet:as-number
                +--ro server-address?     inet:ip-address
                +--ro provider-asns* [provider-asn]
                   +--ro provider-asn     inet:as-number

Liu, et al.               Expires 24 April 2027                [Page 55]
Internet-Draft           YANG Data Model for RTR            October 2026

Contributors

   Mengxiao Chen
   H3C
   China
   Email: chen.mengxiao@h3c.com

   Santosh Kolenchery
   HPE
   Email: santosh.kolenchery@hpe.com

   Haiyang Zhang
   H3C
   China
   Email: zhang.haiyanga@h3c.com

Authors' Addresses

   Yisong Liu
   China Mobile
   32 Xuanwumen West Street
   Beijing
   Xicheng District, 100053
   China
   Email: liuyisong@chinamobile.com

   Changwang Lin
   New H3C Technologies
   8 Yongjia North Road
   Beijing
   Haidian District, 100094
   China
   Email: linchangwang.04414@h3c.com

   Jishnu Roy
   HPE
   192, Whitefield Road
   Bengaluru, Karnataka 560048
   B Narayanapura, Mahadevapura
   India
   Email: jishnu.roy@hpe.com

Liu, et al.               Expires 24 April 2027                [Page 56]
Internet-Draft           YANG Data Model for RTR            October 2026

   Haibo Wang
   Huawei Technologies
   China
   Email: rainsword.wang@huawei.com

   Jeffrey Haas
   HPE
   1133 Innovation Way
   Sunnyvale, CA 94089
   United States of America
   Email: jeffrey.haas@hpe.com

   Hongwei Liu
   ZTE Corporation
   China
   Email: liu.hongwei3@zte.com.cn

   Di Ma
   ZDNS
   Floor 21, Block B, Greenland Center
   Chaoyang Beijing, 100102
   China
   Email: madi@zdns.cn

Liu, et al.               Expires 24 April 2027                [Page 57]