Internet DRAFT - draft-liu-sidrops-rtr-yang
draft-liu-sidrops-rtr-yang
SIDROPS Working Group Y. Liu
Internet Draft China Mobile
Intended status: Standards Track C. Lin
Expires: May 6, 2023 New H3C
H. Wang
Huawei
H. Liu
ZTE
November 6, 2022
YANG Data Model for RPKI to Router Protocol and BGP Origin AS
Validation
draft-liu-sidrops-rtr-yang-01
Abstract
This document defines YANG data models for configuring and managing
Resource Public Key Infrastructure (RPKI) to Router Protocol and BGP
Origin AS Validation.
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 May 6, 2023.
Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
Liu, et al. Expire May 6, 2023 [Page 1]
Internet-Draft YANG Data Model for RPKI to Router November 2022
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...................................................2
1.1. Terminology...............................................2
2. Model Overview.................................................3
3. RPKI to Router YANG Module.....................................3
3.1. Tree View.................................................3
3.2. Yang Module...............................................6
4. BGP Origin AS Validation YANG Module..........................16
4.1. Tree View................................................16
4.2. Yang Module..............................................19
5. Security Considerations.......................................25
6. IANA Considerations...........................................26
7. References....................................................26
7.1. Normative References.....................................26
7.2. Informative References...................................26
Authors' Addresses...............................................27
1. Introduction
[RFC6810] and [RFC8210] describes 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 RPKI-Router
protocol.
[RFC6811] validate the origination Autonomous System (AS) of BGP
routes based on the Validated ROA Payload (VRP) received from the
RPKI cache server.
This document defines YANG [RFC7950] data models for configuring and
managing RPKI-Router Protocol and BGP origin AS validation.
1.1. Terminology
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.
Liu, et al. Expires May 6, 2023 [Page 2]
Internet-Draft YANG Data Model for RPKI to Router November 2022
2. Model Overview
Two YANG data models are defined in this document.
The ietf-rpki-rtr.yang data model provides the methods for
configuring and managing RPKI-Router Protocol. It includes:
o Connectivity parameters, such as RPKI cache server IP address and
destination port.
o Session parameters, such as purge time, refresh time, response
time, and the maximum number of received ROAs.
o Session status and statistics, such as session ID, serial number,
number of received and transmitted messages, and number of ROA
records.
o ROA records.
The ietf-bgp-origin-as-validation.yang data model provides the
methods for configuring BGP origin AS validation.
o Origin AS validation parameters for BGP routes.
o Validity states of BGP routes.
3. RPKI to Router YANG Module
3.1. Tree View
The complete tree of the ietf-rpki-rtr.yang data model is
represented as following. See [RFC8340] for an explanation of the
symbols used.
Liu, et al. Expires May 6, 2023 [Page 3]
Internet-Draft YANG Data Model for RPKI to Router November 2022
module: ietf-rpki-rtr
+--rw rpki-rtr
+--ro roa-table
| +--ro ipv4
| | +--ro roas
| | +--ro roa* [prefix max-len asn server-address]
| | +--ro prefix inet:ipv4-prefix
| | +--ro max-len ipv4-pfx-len
| | +--ro asn inet:as-number
| | +--ro server-address inet:ip-address
| +--ro ipv6
| +--ro roas
| +--ro roa* [prefix max-len asn server-address]
| +--ro prefix inet:ipv6-prefix
| +--ro max-len ipv6-pfx-len
| +--ro asn inet:as-number
| +--ro server-address inet:ip-address
+--rw cache-servers
+--rw cache-server* [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 protocol-version? uint32
+--rw preference? uint32
+--rw enabled? boolean
+--rw description? string
+--rw secure-session-enable? boolean
+--rw secure-session
| +--rw (option)?
| +--:(md5)
| | +--rw enable-md5?
| | | boolean
| | +--rw md5-password?
| | ianach:crypt-hash
| +--:(ssh)
| | +--rw enable-ssh?
| | | boolean
| | +--rw ssh-client-grouping?
| | identityref
| +--:(keychain)
| +--rw enable-keychain?
| | boolean
| +--rw keychain-name?
| key-chain:key-chain-ref
+--rw purge-time? uint32
+--rw refresh-time? uint32
Liu, et al. Expires May 6, 2023 [Page 4]
Internet-Draft YANG Data Model for RPKI to Router November 2022
+--rw response-time? uint32
+--rw roa-limit
| +--rw max-number? uint64
| +--rw threshold-percentage? uint8
| +--rw over-threshold-action? enumeration
| +--rw reconnect-interval? uint32
+--ro session-state? enumeration
+--ro session-id? uint16
+--ro serial-number? uint32
+--ro statistics
| +--ro in-total-messages? yang:zero-based-counter64
| +--ro out-total-messages? yang:zero-based-counter64
| +--ro ipv4-roa-records? yang:zero-based-counter64
| +--ro ipv6-roa-records? yang:zero-based-counter64
+--ro roa-table
+--ro ipv4
| +--ro roas
| +--ro roa* [prefix max-len asn]
| +--ro prefix inet:ipv4-prefix
| +--ro max-len ipv4-pfx-len
| +--ro asn inet:as-number
+--ro ipv6
+--ro roas
+--ro roa* [prefix max-len asn]
+--ro prefix inet:ipv6-prefix
+--ro max-len ipv6-pfx-len
+--ro asn inet:as-number
Liu, et al. Expires May 6, 2023 [Page 5]
Internet-Draft YANG Data Model for RPKI to Router November 2022
3.2. Yang Module
<CODE BEGINS> file "ietf-rpki-rtr@2022-10-18.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 6991: Common YANG Data Types.";
}
import ietf-inet-types {
prefix "inet";
reference
"RFC 6991: Common YANG Data Types";
}
import iana-crypt-hash {
prefix "ianach";
reference
"RFC 7317: A YANG Data Model for System Management";
}
import ietf-ssh-client {
prefix "ssh";
reference
"RFC XXXX: 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 {
prefix "key-chain";
reference
"RFC 8177: YANG Key Chain.";
}
organization
"IETF SIDROPS Working Group";
Liu, et al. Expires May 6, 2023 [Page 6]
Internet-Draft YANG Data Model for RPKI to Router November 2022
contact
"TBD";
description
"This module describes a YANG model for the Resource Public
Key Infrastructure (RPKI) to Router Protocol configuration.
This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.
Copyright (c) 2022 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).
This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices.
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.";
reference "RFC XXXX";
revision 2022-10-18 {
description
"Initial Version";
reference
"RFC XXXX, YANG Data Model for RPKI to Router Protocol
and BGP Origin AS Validation";
}
typedef ipv4-pfx-len {
type uint8 {
range "0 .. 32";
}
description
"IPv4 Prefix Length.";
}
typedef ipv6-pfx-len {
Liu, et al. Expires May 6, 2023 [Page 7]
Internet-Draft YANG Data Model for RPKI to Router November 2022
type uint8 {
range "0 .. 128";
}
description
"IPv6 Prefix Length.";
}
container rpki-rtr {
description
"Configuration parameters for the RPKI to Router Protocol.";
container roa-table {
config false;
description
"Table of ROAs received from all RPKI cache servers.";
container ipv4 {
config false;
description
"Container for IPv4 ROAs table.";
container roas {
config false;
description
"ROAs received from the RPKI cache server.";
list roa {
key "prefix max-len asn server-address";
description
"An entry of ROA.";
leaf prefix {
type inet:ipv4-prefix;
description
"The IPv4 prefix of the ROA.";
}
leaf max-len {
type ipv4-pfx-len;
description
"Denotes the longest prefix allowed. This
MUST NOT be less than the prefix length.";
}
leaf asn {
type inet:as-number;
description
"The origin AS number of the ROA.";
}
leaf server-address {
type inet:ip-address;
description
"IP address of the RPKI cache server.";
}
}
Liu, et al. Expires May 6, 2023 [Page 8]
Internet-Draft YANG Data Model for RPKI to Router November 2022
}
}
container ipv6 {
config false;
description
"Container for IPv6 ROAs table.";
container roas {
config false;
description
"ROAs received from the RPKI cache server.";
list roa {
key "prefix max-len asn server-address";
description
"An entry of ROA.";
leaf prefix {
type inet:ipv6-prefix;
description
"The IPv6 prefix of the ROA.";
}
leaf max-len {
type ipv6-pfx-len;
description
"Denotes the longest prefix allowed. This
MUST NOT be less than the prefix length.";
}
leaf asn {
type inet:as-number;
description
"The origin AS number of the ROA.";
}
leaf server-address {
type inet:ip-address;
description
"IP address of the RPKI cache server.";
}
}
}
}
}
container cache-servers {
description
"Parameters of RPKI cache servers.";
list cache-server {
key "server-address";
description
"Each entry contains parameters for a RPKI cache server
identified by the 'server-address' key.";
leaf server-address {
Liu, et al. Expires May 6, 2023 [Page 9]
Internet-Draft YANG Data Model for RPKI to Router November 2022
type inet:ip-address;
mandatory true;
description
"The IP address of the RPKI cache server";
}
leaf server-port {
type inet:port-number;
description
"The remote port for the connection
to the RPKI cache server";
}
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 protocol-version {
type uint32;
description
"The version number of the RPKI to Router Protocol.";
}
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
Liu, et al. Expires May 6, 2023 [Page 10]
Internet-Draft YANG Data Model for RPKI to Router November 2022
"Textual description of the RPKI cache server";
}
leaf secure-session-enable {
type boolean;
default "false";
description
"Whether the session is secured.";
}
container secure-session {
when "../secure-session-enable = 'true'";
description
"Container for describing how a particular session
is to be secured.";
choice option {
description
"Choice for session secruring 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 ssh:ssh-client-grouping {
reference
"RFC XXXX: YANG Groupings for SSH Clients and
SSH Servers";
}
description
"Uses SSH to secure the session.";
}
case keychain {
leaf keychain-name {
type key-chain:key-chain-ref;
description
"Name of key chain.";
reference
"RFC 8177: YANG Key Chain.";
}
description
"Uses key-chain to secure the session.";
}
}
}
leaf purge-time {
Liu, et al. Expires May 6, 2023 [Page 11]
Internet-Draft YANG Data Model for RPKI to Router November 2022
type uint32;
description
"Configures the time a router waits to keep data from
the RPKI cache server after the session drops.";
}
leaf refresh-time {
type uint32;
description
"Configures the time a router waits in between sending
periodic serial queries to the RPKI cache server.";
}
leaf response-time {
type uint32;
description
"Configures the time a router waits for a response
after sending a serial or reset query to the RPKI
cache server.";
}
container roa-limit {
leaf max-number {
type uint64;
description
"Configures the maximum number of ROAs that can be
received from the RPKI cache server.";
}
leaf threshold-percentage {
type uint8 {
range "0..100";
}
units "percent";
description
"Configures the threshold percentage for ROA maximum
number.";
}
leaf over-threshold-action {
type enumeration {
enum alert-only {
description
"Generates alert messages.";
}
enum discard {
description
"Discards excess ROAs.";
}
enum reconnect {
description
"Diconncets with the RPKI cache server,
and tries to reconnect after reconnection
Liu, et al. Expires May 6, 2023 [Page 12]
Internet-Draft YANG Data Model for RPKI to Router November 2022
timer expires.";
}
enum idle-forever {
description
"Diconncets with the RPKI cache server
forever.";
}
}
description
"The action to taken when ROA number exceeds
threshold.";
}
leaf reconnect-interval {
type uint32 {
range "1..30000";
}
units "minutes";
description
"Time interval for the reconnection timer.";
}
description
"Limit of ROAs that can be received from the RPKI
cache server.";
}
leaf session-state {
type enumeration {
enum idle {
description
"The session is down.";
}
enum connect {
description
"The session is waiting for the underlying
transport session to be established.";
}
enum establish {
description
"The session is up.";
}
}
config false;
description
"The session state.";
}
leaf session-id {
type uint16;
config false;
description
Liu, et al. Expires May 6, 2023 [Page 13]
Internet-Draft YANG Data Model for RPKI to Router November 2022
"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-number {
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.";
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 statistics {
config false;
description
"Statistics of 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.";
}
leaf ipv4-roa-records {
type yang:zero-based-counter64;
description
"The number of ROAs for IPv4 prefixes received
from the RPKI cache server.";
}
leaf ipv6-roa-records {
type yang:zero-based-counter64;
description
Liu, et al. Expires May 6, 2023 [Page 14]
Internet-Draft YANG Data Model for RPKI to Router November 2022
"The number of ROAs for IPv6 prefixes received
from the RPKI cache server.";
}
}
container roa-table {
config false;
description
"Table of ROAs received from the RPKI cache server.";
container ipv4 {
config false;
description
"Container for IPv4 ROAs table.";
container roas {
config false;
description
"ROAs received from the RPKI cache server.";
list roa {
key "prefix max-len asn";
description
"An entry of ROA.";
leaf prefix {
type inet:ipv4-prefix;
description
"The IPv4 prefix of the ROA.";
}
leaf max-len {
type ipv4-pfx-len;
description
"Denotes the longest prefix allowed. This
MUST NOT be less than the prefix length.";
}
leaf asn {
type inet:as-number;
description
"The origin AS number of the ROA.";
}
}
}
}
container ipv6 {
config false;
description
"Container for IPv6 ROAs table.";
container roas {
config false;
description
"ROAs received from the RPKI cache server.";
list roa {
Liu, et al. Expires May 6, 2023 [Page 15]
Internet-Draft YANG Data Model for RPKI to Router November 2022
key "prefix max-len asn";
description
"An entry of ROA.";
leaf prefix {
type inet:ipv6-prefix;
description
"The IPv6 prefix of the ROA.";
}
leaf max-len {
type ipv6-pfx-len;
description
"Denotes the longest prefix allowed. This
MUST NOT be less than the prefix length.";
}
leaf asn {
type inet:as-number;
description
"The origin AS number of the ROA.";
}
}
}
}
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";
}
}
}
}
}
<CODE ENDS>
4. BGP Origin AS Validation YANG Module
4.1. Tree View
The complete tree of the ietf-bgp-origin-as-validation.yang data
model is represented as following. See [RFC8340] for an explanation
of the symbols used.
Liu, et al. Expires May 6, 2023 [Page 16]
Internet-Draft YANG Data Model for RPKI to Router November 2022
module: ietf-bgp-origin-as-validation
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:global
/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast:
+--rw origin-as-validation
+--rw enabled? boolean
+--rw source-protocol? identityref
+--rw redistribution-as? inet:as-number
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:global
/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast:
+--rw origin-as-validation
+--rw enabled? boolean
+--rw source-protocol? identityref
+--rw redistribution-as? inet:as-number
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:rib
/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast
/bgp:loc-rib/bgp:routes/bgp:route:
+--ro origin-as-validity? origin-as-validity-state
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:rib
/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast
/bgp:loc-rib/bgp:routes/bgp:route:
+--ro origin-as-validity? origin-as-validity-state
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:global
/bgp:afi-safis/bgp:afi-safi/bgp:route-selection-options:
+--rw origin-as
+--rw enabled? boolean
+--rw allow-invalid? boolean
+--rw allow-not-found? boolean
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:neighbors
/bgp:neighbor/bgp:afi-safis/bgp:afi-safi
/bgp:ipv4-unicast:
+--rw send-origin-as-validity? boolean
+--rw export-origin-as-validation
+--rw enabled? boolean
+--rw allow-not-found? boolean
augment /rt:routing/rt:control-plane-protocols
Liu, et al. Expires May 6, 2023 [Page 17]
Internet-Draft YANG Data Model for RPKI to Router November 2022
/rt:control-plane-protocol/bgp:bgp/bgp:neighbors
/bgp:neighbor/bgp:afi-safis/bgp:afi-safi
/bgp:ipv6-unicast:
+--rw send-origin-as-validity? boolean
+--rw export-origin-as-validation
+--rw enabled? boolean
+--rw allow-not-found? boolean
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:peer-groups
/bgp:peer-group/bgp:afi-safis/bgp:afi-safi
/bgp:ipv4-unicast:
+--rw send-origin-as-validity? boolean
+--rw export-origin-as-validation
+--rw enabled? boolean
+--rw allow-not-found? boolean
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bgp:bgp/bgp:peer-groups
/bgp:peer-group/bgp:afi-safis/bgp:afi-safi
/bgp:ipv6-unicast:
+--rw send-origin-as-validity? boolean
+--rw export-origin-as-validation
+--rw enabled? boolean
+--rw allow-not-found? boolean
Liu, et al. Expires May 6, 2023 [Page 18]
Internet-Draft YANG Data Model for RPKI to Router November 2022
4.2. Yang Module
<CODE BEGINS> file "ietf-bgp-origin-as-validation@2022-10-18.yang"
module ietf-bgp-origin-as-validation {
yang-version "1.1";
namespace "urn:ietf:params:xml:ns:yang:"
+ "ietf-bgp-origin-as-validation";
prefix "oav";
import ietf-inet-types {
prefix "inet";
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-routing {
prefix "rt";
reference
"RFC 8349, A YANG Data Model for Routing Management
(NMDA Version).";
}
import ietf-bgp {
prefix "bgp";
reference
"RFC XXXX: BGP YANG Model for Service Provider Networks";
}
import iana-bgp-types {
prefix "bt";
reference
"RFC XXXX: BGP YANG Model for Service Provider Networks";
}
organization
"IETF SIDROPS Working Group";
contact
"TBD";
description
"This module describes configuration of the BGP origin AS
validation based on the Validated ROA Payload (VRP).
This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.
Liu, et al. Expires May 6, 2023 [Page 19]
Internet-Draft YANG Data Model for RPKI to Router November 2022
Copyright (c) 2022 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).
This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices.
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.";
reference "RFC XXXX";
revision 2022-10-18 {
description
"Initial Version";
reference
"RFC XXXX, YANG Data Model for RPKI to Router Protocol
and BGP Origin AS Validation";
}
identity vrp-protocol {
description
"Base identity from which VRP source protocol identities
are derived.";
}
identity rpki-rtr {
base vrp-protocol;
description
"RPKI to Router Protocol";
}
identity ineligible-orgin-as {
base bgp:ineligible-route-reason;
description
"Route was ineligible due to origin as validation";
}
typedef origin-as-validity-state {
Liu, et al. Expires May 6, 2023 [Page 20]
Internet-Draft YANG Data Model for RPKI to Router November 2022
type enumeration {
enum not-found {
description
"No VRP Covers the Route Prefix.";
}
enum valid {
description
"At least one VRP Matches the Route Prefix.";
}
enum invalid {
description
"At least one VRP Covers the Route Prefix, but no VRP
Matches it.";
}
enum disabled {
description
"BGP origin AS validation is not enabled.";
}
}
description
"Origin AS validation state of BGP routes.";
reference
"RFC 6811, BGP Prefix Origin Validation.";
}
grouping origin-as-validation-config {
description
"Origin AS validation of BGP prefix.";
container origin-as-validation {
leaf enabled {
type boolean;
default "false";
description
"Whether origin-AS validation of BGP prefix is enabled.";
}
leaf source-protocol {
type identityref {
base vrp-protocol;
}
description
"Type of the protocol from which the VRP originated.";
}
leaf redistribution-as {
type inet:as-number;
description
"Uses this AS number in the origin-AS validation for
redistributed routes since they have no AS-PATH.";
reference
Liu, et al. Expires May 6, 2023 [Page 21]
Internet-Draft YANG Data Model for RPKI to Router November 2022
"RFC 8481, Clarifications to BGP Origin Validation Based
on Resource Public Key Infrastructure (RPKI).";
}
description
"Origin AS validation of BGP prefix.";
}
}
grouping origin-as-selection-option {
description
"Origin AS option for BGP route selection.";
container origin-as {
leaf enabled {
type boolean;
default "false";
description
"When enabled allows the origin AS validity states to be
taken into consideration in the best-path calculation.";
}
leaf allow-invalid {
type boolean;
default "false";
description
"When enabled allows the route with 'invalid' origin AS
to be taken into consideration in the best-path
calculation.";
}
leaf allow-not-found {
type boolean;
default "true";
description
"When enabled allows the route with 'not-found' origin
AS to be taken into consideration in the best-path
calculation.";
}
description
"Origin AS option for BGP route selection.";
}
}
grouping origin-as-validity-advertisement {
description
"Advertisement of Origin Validation State Extended
Community to neighbor(s).";
leaf send-origin-as-validity {
type boolean;
default "false";
description
Liu, et al. Expires May 6, 2023 [Page 22]
Internet-Draft YANG Data Model for RPKI to Router November 2022
"If set to true, send the origin AS validity to the
neighbor(s) using Origin Validation State Extended
Community";
reference
"RFC 8097, BGP Prefix Origin Validation State Extended
Community.";
}
}
grouping export-origin-as-validation-config {
description
"Export Origin AS validation of BGP prefix.";
container export-origin-as-validation {
leaf enabled {
type boolean;
default "false";
description
"When enabled allows the origin AS validity states to be
taken into consideration in BGP export.";
}
leaf allow-not-found {
type boolean;
default "false";
description
"When enabled allows the route with 'not-found' origin
AS to be sent to the neighbor.";
}
description
"Export Origin AS validation of BGP prefix.";
reference
"RFC 8893, Resource Public Key Infrastructure (RPKI) Origin
Validation for BGP Export.";
}
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:global"
+ "/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast" {
description
"Origin AS validation augmentation of BGP IPv4 Unicast
Address Family.";
uses origin-as-validation-config;
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:global"
+ "/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast" {
description
Liu, et al. Expires May 6, 2023 [Page 23]
Internet-Draft YANG Data Model for RPKI to Router November 2022
"Origin AS validation augmentation of BGP IPv6 Unicast
Address Family.";
uses origin-as-validation-config;
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:rib"
+ "/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast"
+ "/bgp:loc-rib/bgp:routes/bgp:route" {
description
"Origin AS validity augmentation of BGP IPv4 Unicast
route.";
leaf origin-as-validity {
type origin-as-validity-state;
description
"Origin AS validity of BGP IPv4 Unicast prefix";
}
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:rib"
+ "/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast"
+ "/bgp:loc-rib/bgp:routes/bgp:route" {
description
"Origin AS validity augmentation of BGP IPv6 Unicast
route.";
leaf origin-as-validity {
type origin-as-validity-state;
description
"Origin AS validity of BGP IPv6 Unicast prefix";
}
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:global"
+ "/bgp:afi-safis/bgp:afi-safi"
+ "/bgp:route-selection-options" {
when "derived-from-or-self(../bgp:name, 'bt:ipv4-unicast') or "
+ "derived-from-or-self(../bgp:name, 'bt:ipv6-unicast')" {
description
"This augmentation is valid for IPv4 and IPv6 Unicast.";
}
description
"augmentation of BGP route selection options";
uses origin-as-selection-option;
}
augment "/rt:routing/rt:control-plane-protocols"
Liu, et al. Expires May 6, 2023 [Page 24]
Internet-Draft YANG Data Model for RPKI to Router November 2022
+ "/rt:control-plane-protocol/bgp:bgp/bgp:neighbors"
+ "/bgp:neighbor/bgp:afi-safis/bgp:afi-safi"
+ "/bgp:ipv4-unicast" {
description
"augmentation of Origin Validation State Extended
Community advertisement for IPv4 Unicast neighbor";
uses origin-as-validity-advertisement;
uses export-origin-as-validation-config;
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:neighbors"
+ "/bgp:neighbor/bgp:afi-safis/bgp:afi-safi"
+ "/bgp:ipv6-unicast" {
description
"augmentation of Origin Validation State Extended
Community advertisement for IPv6 Unicast neighbor";
uses origin-as-validity-advertisement;
uses export-origin-as-validation-config;
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:peer-groups"
+ "/bgp:peer-group/bgp:afi-safis/bgp:afi-safi"
+ "/bgp:ipv4-unicast" {
description
"augmentation of Origin Validation State Extended
Community advertisement for IPv4 Unicast peer group";
uses origin-as-validity-advertisement;
uses export-origin-as-validation-config;
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/bgp:bgp/bgp:peer-groups"
+ "/bgp:peer-group/bgp:afi-safis/bgp:afi-safi"
+ "/bgp:ipv6-unicast" {
description
"augmentation of Origin Validation State Extended
Community advertisement for IPv6 Unicast peer group";
uses origin-as-validity-advertisement;
uses export-origin-as-validation-config;
}
}
<CODE ENDS>
5. Security Considerations
Liu, et al. Expires May 6, 2023 [Page 25]
Internet-Draft YANG Data Model for RPKI to Router November 2022
TBD
6. IANA Considerations
TBD
7. References
7.1. Normative References
[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>.
[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>.
[RFC6811] Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R.
Austein, "BGP Prefix Origin Validation", RFC 6811, DOI
10.17487/RFC6811, January 2013, <https://www.rfc-
editor.org/info/rfc6811>.
[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>.
[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>.
7.2. Informative References
[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>.
Liu, et al. Expires May 6, 2023 [Page 26]
Internet-Draft YANG Data Model for RPKI to Router November 2022
Authors' Addresses
Yisong Liu
China Mobile
China
Email: liuyisong@chinamobile.com
Changwang Lin
New H3C Technologies
China
Email: linchangwang.04414@h3c.com
Haibo Wang
Huawei Technologies
China
Email: rainsword.wang@huawei.com
Hongwei Liu
ZTE Corporation
China
Email: liu.hongwei3@zte.com.cn
Liu, et al. Expires May 6, 2023 [Page 27]
