[NETCONF-372] Define and implement a 'session-candidate' NETCONF extension Created: 14/Mar/17  Updated: 15/Mar/19

Status: Confirmed
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: New Feature
Reporter: Robert Varga Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
blocks NETCONF-370 Milestone: Implement DataBroker API f... Confirmed

 Description   

Base RFC6241 does not provide enough discovery services to understand how the candidate data store works with respect to other sessions and recommends locking the candidate.

This does not align well with how the ODL data store works, specifically ODL does not have a shared candidate store, but rather implements it using MVCC, where each session can have a candidate and conflicts are resolved on commit.

Unfortunately this capability is not discoverable, which means that ODL NETCONF SB plugin cannot take advantage of it when connecting to and ODL-based device.

Define a new NETCONF capability, which indicates that the candidate store is not shared and exists only as long as the session does.

Implement this capability on the NB and make the SB plugin recognize it, so it does not lock the candidate store.



 Comments   
Comment by Robert Varga [ 14/Mar/17 ]

The capability definition should be a draft RFC document.

Generated at Wed Feb 07 20:14:51 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.