<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:46 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[NETCONF-735] Support NETCONF get/get-config with multiple selected subtrees</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-735</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;According to RFC 6241, NETCONF should support reading of multiple subtrees using single get/get-config RPC request. See following examples:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Reading just specific elements under all list items:&lt;br/&gt;
 &lt;a href=&quot;https://tools.ietf.org/html/rfc6241#section-6.4.6&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc6241#section-6.4.6&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Selection of multiple composite subtrees:&lt;br/&gt;
 &lt;a href=&quot;https://tools.ietf.org/html/rfc6241#section-6.4.7&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc6241#section-6.4.7&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Current implementation of NETCONF in ODL supports only construction of simple subtree filter based on one YangInstanceIdentifier path.&lt;/p&gt;

&lt;p&gt;On RESTCONF side, there is &apos;fields&apos; query parameter that can be used for testing of this feature - most, if not all patterns that can be built using fields query parameter can be emulated using subtree filtering; see details:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://tools.ietf.org/html/rfc8040#section-4.8.3&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc8040#section-4.8.3&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;What should be done:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;construction of more complex NETCONF subtree filters based on one parent path and list of subpaths that select specific fields that must be read&lt;/li&gt;
	&lt;li&gt;exposing a new read method to NETCONF DOM API (DOMDataBroker extension and raw NETCONF service); for example: read(datastore, yiid, list&amp;lt;yiid&amp;gt;)&lt;/li&gt;
	&lt;li&gt;creation of &apos;fields&apos; query parameter parser that would return List&amp;lt;YangInstanceIdentifier&amp;gt; collection&lt;/li&gt;
	&lt;li&gt;connection of RESTCONF and NETCONF sides&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Use case:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;we need to read just selected leaves under all list items&lt;/li&gt;
	&lt;li&gt;in NETCONF device, there are nearly 5000 list items an each of this list item has next containers; however we don&apos;t need all data&lt;/li&gt;
	&lt;li&gt;because of the efficiency we would like to use just single RPC and minimize the network traffic&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;em&gt;Note: similar ticket on ONAP JIRA:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;em&gt;&lt;a href=&quot;https://jira.onap.org/browse/SDNC-1367&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jira.onap.org/browse/SDNC-1367&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="33445">NETCONF-735</key>
            <summary>Support NETCONF get/get-config with multiple selected subtrees</summary>
                <type id="10103" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10311&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="jaro0149odl">Jaroslav T&#243;th</assignee>
                                    <reporter username="jaro0149odl">Jaroslav T&#243;th</reporter>
                        <labels>
                    </labels>
                <created>Wed, 21 Oct 2020 05:50:45 +0000</created>
                <updated>Wed, 12 May 2021 15:57:58 +0000</updated>
                            <resolved>Wed, 12 May 2021 15:57:58 +0000</resolved>
                                                    <fixVersion>Aluminium SR4</fixVersion>
                    <fixVersion>1.13.2</fixVersion>
                                    <component>netconf</component>
                    <component>restconf-nb</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                    <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="21092">NETCONF-79</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03vi7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>