OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [NETCONF-5] Update call home to RFC8071 https://jira.opendaylight.org/browse/NETCONF-5 netconf <p><a href="http://tools.ietf.org/html/draft-ietf-netconf-reverse-ssh" class="external-link" target="_blank" rel="nofollow noopener">http://tools.ietf.org/html/draft-ietf-netconf-reverse-ssh</a> is a very useful feature for controller deployments, where we do not need to pre-configure the device locations. Implement it such that a sal-netconf-connector instance can be configured to accept Call Home connections.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-5 Update call home to RFC8071 Improvement Resolved Done Oleksii Mozghovyi Robert Varga Thu, 24 Jul 2014 22:48:37 +0000 Tue, 23 Feb 2021 18:43:57 +0000 Tue, 23 Feb 2021 18:43:57 +0000 1.13.0 netconf 0 11 <p>Postponing for berylium.</p> <p>Also effort needs to be aligned with USC project. The USC opendaylight project is aiming for call home support for all the protocols.</p> <p>Move to NETCONFI project.</p> <p>Postponing for Boron. As Maros said, find out how we could align this with USC.</p> <p>Call home will be RFC8071 soon: <a href="https://www.rfc-editor.org/auth48/C279" class="external-link" target="_blank" rel="nofollow noopener">https://www.rfc-editor.org/auth48/C279</a><br/> Configuration support is part of <a href="https://tools.ietf.org/html/draft-ietf-netconf-netconf-client-server-01" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/draft-ietf-netconf-netconf-client-server-01</a></p> <p>This will be initially an experimental feature. <br/> The first implementation will not be cluster-aware.</p> <p>Added <a href="https://jira.opendaylight.org/browse/NETCONF-377" title="make netconf call home feature be cluster-aware" class="issue-link" data-issue-key="NETCONF-377">NETCONF-377</a> to add cluster-aware feature to call home.</p> Duplicate CONTROLLER-989 NETCONF-375 Development External issue ID 1422 External issue URL Issue Type Priority Rank 0|i01vvb: