Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify policy-forwarding and routing-policy if no rules are present #1223

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -62,11 +62,14 @@ module openconfig-policy-forwarding {

A forwarding-policy specifies the match criteria that it intends
to use to determine the packets that it reroutes - this may
consist of a number of criteria, such as DSCP. The action of the
policy results in a forwarding action being applied to matching
packets. For example, decapsulating the packet from a GRE header.
In order to enact the policy based on particular interfaces - the
forwarding-policy is applied to an interface via referencing it
consist of a number of criteria, such as DSCP. The match criteria
is specified as rules. If no rules are specified, then the policy
will match all packets.

The action of the policy results in a forwarding action being applied
to matching packets. For example, decapsulating the packet from a GRE
header. In order to enact the policy based on particular interfaces -
the forwarding-policy is applied to an interface via referencing it
within an 'apply-forwarding-policy' statement associated with an
interface.

Expand All @@ -81,7 +84,13 @@ module openconfig-policy-forwarding {
The forwarding action of the corresponding policy is set to
PATH_GROUP and references the configured group of LSPs.";

oc-ext:openconfig-version "0.6.1";
oc-ext:openconfig-version "0.7.0";

revision "2024-11-14" {
description
"Clarify that if no rules are present, all packets will be matched.";
reference "0.7.0";
}

revision "2023-04-25" {
description
Expand Down Expand Up @@ -159,3 +168,4 @@ module openconfig-policy-forwarding {
}
}
}

20 changes: 14 additions & 6 deletions release/models/policy/openconfig-routing-policy.yang
Original file line number Diff line number Diff line change
Expand Up @@ -51,11 +51,13 @@ module openconfig-routing-policy {
Evaluation of each policy definition proceeds by evaluating its
corresponding individual policy statements in order. When a
condition statement in a policy statement is satisfied, the
corresponding action statement is executed. If the action
statement has a final disposition configured as policy result, either
accept-route or reject-route, evaluation of the current policy definition
stops, and no further policy statements are evaluated. In case there is a
policy chain, no further policy definitions in the chain are evaluated.
corresponding action statement is executed. A policy statement with no
conditions defined is evaluated as statisfied, meaning all routes are
matched. If the action statement has a final disposition configured as
policy result, either accept-route or reject-route, evaluation of the
current policy definition stops, and no further policy statements are
evaluated. In case there is a policy chain, no further policy definitions
in the chain are evaluated.

If the action statement has the NEXT_STATEMENT policy result, all the
defined actions are executed and policy evaluation proceeds to the next
Expand Down Expand Up @@ -87,8 +89,14 @@ module openconfig-routing-policy {
default value for the default-(import|export)-policy leaf must be
applied. See RFC6020 7.6.1 which applies to this model.";

oc-ext:openconfig-version "3.4.2";
oc-ext:openconfig-version "3.5.0";

revision "2024-11-26" {
description
"Clarify that a policy statement with no conditions defined is evaluated
as statisfied.";
reference "3.5.0";
}
revision "2023-11-01" {
description
"Refactor apply policy to separate default policy in it's own common
Expand Down
Loading