ietf-system-capabilities

Organization:

IETF NETCONF (Network Configuration) Working Group

Module:

ietf-system-capabilities

Version:

2022-02-17

File:

ietf-system-capabilities@2022-02-17.yang

Abstract:

This module specifies a structure to specify system capabilities for a server or a publisher. System capabilities may include c...

Contact:

WG Web: <https://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>

Editor: Balazs Lengyel
<mailto:balazs.lengyel@ericsson.com>

Check for an additional details:

YANG Catalog

Description:

This module specifies a structure to specify system
capabilities for a server or a publisher. System capabilities
may include capabilities of a NETCONF or RESTCONF server or a
notification publisher.

This module does not contain any specific capabilities; it only
provides a structure where containers containing the actual
capabilities are augmented in.

Capability values can be specified at the system level, at the
datastore level (by selecting all nodes in the datastore), or
for specific data nodes of a specific datastore (and their
contained subtrees).
Capability values specified for a specific datastore or
node-set override values specified on the system/publisher
level.

The same grouping MUST be used to define hierarchical
capabilities supported both at the system level and at the
datastore/data-node level.

To find a capability value for a specific data node in a
specific datastore, the user SHALL:

1) search for a datastore-capabilities list entry for
the specific datastore. When stating a specific capability, the
relative path for any specific capability must be the same
under the system-capabilities container and under the
per-node-capabilities list.

2) If the datastore entry is found within that entry, process
all per-node-capabilities entries in the order they appear in
the list. The first entry that specifies the specific
capability and has a node-selector selecting the specific data
node defines the capability value.

3) If the capability value is not found above and the specific
capability is specified under the system-capabilities container
(outside the datastore-capabilities list), this value shall be
used.

4) If no values are found in the previous steps, the
system/publisher is not capable of providing a value. Possible
reasons are that it is unknown, the capability is changing for
some reason, there is no specified limit, etc. In this case,
the system's behavior is unspecified.

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) 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 9196
(https://www.rfc-editor.org/info/rfc9196); see the RFC itself
for full legal notices.