Skip to content

state how a NETCONF client could discover if the server supports "with-immutability" parameter #20

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.

Sign up for GitHub

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

Merged
QiufangMa merged 1 commit into from
Mar 31, 2026
Merged

state how a NETCONF client could discover if the server supports "with-immutability" parameter #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 3 additions & 0 deletions draft-ietf-netmod-immutable-flag.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,6 +266,9 @@ module: ietf-immutable-annotation
~~~~
{: #tree title="Augmentations to NETCONF Operations" artwork-align="center}

To discover if the "with-immutability" parameter is supported by the server,
a NETCONF client can query if the server implements "ietf-immutable-annotation" module by reading the YANG library information from the operational state datastore, as per {{?RFC8526}}.

Refer to {{NETCONF-example}} for an example of NETCONF operation with "with-immutability" input parameter.

### RESTCONF Extensions to Support "with-immutability" {#RESTCONF-ext}
Expand Down
Loading