[NETCONF-690] ODL announces RESTCONF capabilities it does not support Created: 25/May/20  Updated: 04/Nov/21  Resolved: 04/Nov/21

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Mahesh Jethanandani Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

RESTCONF announces the following list of capabilities as part of ietf-restconf-monitoring.

 
   

 <capabilities>         <capability>urn:ietf:params:restconf:capability:depth:1.0</capability>         <capability>urn:ietf:params:restconf:capability:fields:1.0</capability>         <capability>urn:ietf:params:restconf:capability:filter:1.0</capability>         <capability>urn:ietf:params:restconf:capability:replay:1.0</capability>         <capability>urn:ietf:params:restconf:capability:with-defaults:1.0</capability>     </capabilities>

 
 
ODL does support fields capability, but it does not support depth, filter. with-defaults and replay does not make sense for RESTCONF (it is not a device). This list should be trimmed to capabilities that are supported.

 Comments   
Comment by Jamo Luhrsen [ 26/May/20 ]

mjethanandani, do you know of anyone that was planning to work on this?

Comment by Robert Varga [ 04/Nov/21 ]

I have just had a pass over these last two weeks as part of NETCONF-773. I do not agree with "it is not a device" assessment. The situation is as follows:

  • depth is supported
  • fields are supported, but might be buggy for the local case
  • filter is supported for notification subscriptions, as per RFC8040
  • replay, specifically start-time and stop-time, are supported for notification subscriptions, as per RFC8040
  • with-defaults is supported to a certain extent, but the logic is rather twisted and under-documented

In any case, for the pass-through case, these are expected to be passed on to the SB handler, which will reject them if the device does not support a capability.

Comment by Robert Varga [ 04/Nov/21 ]

If there are specific cases where parameters do not work, they should be treated as separate bugs.

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