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-91 netconf <p>The ODL Netconf client isn't checking for "interleave" (RFC 5277) capability being in the server offered capabilities, and assumes it to be there. This causes failures when ODL sends RPCs and Notification requests on the same session (the server device rejects these). </p> <p>Issue observed in Lithium SR2.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-91

ODL assumes netconf interleave capability

Bug Confirmed Unresolved Unassigned Wojciech Dec Tue, 27 Oct 2015 16:45:02 +0000 Tue, 10 May 2022 12:22:41 +0000 netconf 0 3 <p>(In reply to Wojciech Dec from comment #0)<br/> &gt; The ODL Netconf client isn't checking for "interleave" (RFC 5277) capability<br/> &gt; being in the server offered capabilities, and assumes it to be there. This<br/> &gt; causes failures when ODL sends RPCs and Notification requests on the same<br/> &gt; session (the server device rejects these). <br/> &gt; <br/> &gt; Issue observed in Lithium SR2.</p> <p>Hi Wojciech,<br/> Does this bug has been solved in the lastest Boron? If not, could you please provide more details or the step you try which how the bug occured.</p> <p>Last tried with Be, where it still wasn't fixed. However a quick search of the latest netconf master shows no relevant hits for the "interleave" keyword, so it does not appear to be solved.</p> <p>To be specific: urn:ietf:params:netconf:capability:interleave:1.0 capability,<br/> allows the client to get send RPCs while a notification subscription is active. The ODL netconf client must not assume that this capability is on the server unless it is advertised by the server, and clearly there is no such check.</p> Relates NETCONF-878 Development External issue ID 4532 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01wef: