Skip to content

Editorial clean-up for the 'route-object-exclude-always' description #313

@italobusi

Description

@italobusi

The description of the 'route-object-exclude-always' is quite hard to read since it results in a too long statement

I would propose the following updated md code to improve the readability of the text:

>>>>
- 'route-object-exclude-always':
: a list of route entries that are always excluded from the path computation. The exclusion of a route entry in this list
during path computation is not order sensitive.
- 'route-object-include-exclude':
: a list of route entries to include or exclude route entry constraints for the path computation.
: The constraint type (include or exclude)
is specified with each route entry. The path computation considers route entry constraints in the order they appear in this list. Once a route entry
constraint is consumed from this list, it is not considered any further in the computation of the TE path.
: The 'route-object-include-exclude' is used to configure constraints on which
route objects (e.g., nodes, links) are included or excluded in the path
computation.
: The interpretation of an empty 'route-object-include-exclude'
list depends on the TE Tunnel (end-to-end or Tunnel Segment) and on the
specific path, according to the following rules:
>>>>>>>>
1. An empty 'route-object-include-exclude' list for the primary path of an end-to-end TE Tunnel indicates that there are no route objects to be included or excluded in the path computation.
2. An empty 'route-object-include-exclude' list for the primary path of a TE Tunnel Segment indicates that no primary LSP is required for that TE Tunnel.
3. An empty 'route-object-include-exclude' list for a reverse path means it always follows the forward path (i.e., the TE Tunnel is co-routed). When the 'route-object-include-exclude' list is not empty, the reverse path is routed independently of the forward path.
4. An empty 'route-object-include-exclude' list for the secondary (forward) path of a TE Tunnel segment indicates that the secondary path has the same endpoints as the primary path.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions