https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-690 netconf <p>RESTCONF announces the following list of capabilities as part of ietf-restconf-monitoring.</p> <p> <br/>    </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">  &lt;capabilities&gt;         &lt;capability&gt;urn:ietf:params:restconf:capability:depth:1.0&lt;/capability&gt;         &lt;capability&gt;urn:ietf:params:restconf:capability:fields:1.0&lt;/capability&gt;         &lt;capability&gt;urn:ietf:params:restconf:capability:filter:1.0&lt;/capability&gt;         &lt;capability&gt;urn:ietf:params:restconf:capability:replay:1.0&lt;/capability&gt;         &lt;capability&gt;urn:ietf:params:restconf:capability:with-defaults:1.0&lt;/capability&gt;     &lt;/capabilities&gt;</pre> </div></div> <p> <br/>  <br/> 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.</p> NETCONF-690

ODL announces RESTCONF capabilities it does not support

Bug Medium Resolved Won't Do Unassigned Mahesh Jethanandani Mon, 25 May 2020 06:28:08 +0000 Thu, 4 Nov 2021 19:30:31 +0000 Thu, 4 Nov 2021 19:30:31 +0000 restconf-nb 0 3 <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=mjethanandani" class="user-hover" rel="mjethanandani">mjethanandani</a>, do you know of anyone that was planning to work on this?</p> <p>I have just had a pass over these last two weeks as part of <a href="https://jira.opendaylight.org/browse/NETCONF-773" title="Refactor restconf-nb wiring" class="issue-link" data-issue-key="NETCONF-773">NETCONF-773</a>. I do not agree with "it is not a device" assessment. The situation is as follows:</p> <ul> <li>depth is supported</li> <li>fields are supported, but might be buggy for the local case</li> <li>filter is supported for notification subscriptions, as per RFC8040</li> <li>replay, specifically start-time and stop-time, are supported for notification subscriptions, as per RFC8040</li> <li>with-defaults is supported to a certain extent, but the logic is rather twisted and under-documented</li> </ul> <p>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.</p> <p>If there are specific cases where parameters do not work, they should be treated as separate bugs.</p> Development Rank 0|i03sk7: