* Netconf message-id attribute changed from optional to mandatory
* Made NETCONF message handling more strict according to RFC 6241 * Set `CLICON_NETCONF_MESSAGE_ID_OPTIONAL` to true to accept omission of message-id attribute * Fixed: [need make sure message-id exist in rpc validate #240](https://github.com/clicon/clixon/issues/240)
This commit is contained in:
parent
96c9296056
commit
85e2945ec9
22 changed files with 196 additions and 89 deletions
|
|
@ -50,6 +50,7 @@ module clixon-config {
|
|||
CLICON_RESTCONF_PRIVILEGES
|
||||
CLICON_RESTCONF_INSTALLDIR
|
||||
CLICON_RESTCONF_STARTUP_DONTUPDATE
|
||||
CLICON_NETCONF_MESSAGE_ID_OPTIONAL
|
||||
Released in Clixon 5.2";
|
||||
}
|
||||
revision 2021-03-08 {
|
||||
|
|
@ -465,6 +466,16 @@ module clixon-config {
|
|||
is returned, which conforms to the RFC.
|
||||
Note this applies only to external NETCONF, not the internal (IPC) netconf";
|
||||
}
|
||||
leaf CLICON_NETCONF_MESSAGE_ID_OPTIONAL {
|
||||
type boolean;
|
||||
default false;
|
||||
description
|
||||
"This option relates to RFC 6241 Sec 4.1 <rpc> Element
|
||||
The <rpc> element has a mandatory attribute 'message-id', which is a
|
||||
string chosen by the sender of the RPC.
|
||||
If true, an RPC can be sent without a message-id.
|
||||
This applies to both external NETCONF and internal (IPC) netconf";
|
||||
}
|
||||
leaf CLICON_RESTCONF_DIR {
|
||||
type string;
|
||||
description
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue