<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:11 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-497] Json restconf responses does not prepend module name at top level</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-497</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;RFC 8040 refers &lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; to RFC 7951 which states:&lt;br/&gt;
 &#160; &quot;A namespace-qualified member name MUST be used for all members of a top-level JSON object&quot;&lt;/p&gt;

&lt;p&gt;Note that ODL already requires the module name in input (PUT, POST, input part of RPC) but this bug is about ODL not prefixing the module name in output (GET, output part of RPC). But examples in RFCs clearly show the MUST also applies on output.&lt;/p&gt;

&lt;p&gt;To reproduce (on Nitrogen snapshot), start ODL, install odl-restconf and odl-netconf-topology, then:&lt;/p&gt;

&lt;p&gt;Current:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
$ curl -u admin:admin http:&lt;span class=&quot;code-comment&quot;&gt;//127.0.0.1:8181/restconf/config/network-topology:network-topology ;echo
&lt;/span&gt;&#160; {&lt;span class=&quot;code-quote&quot;&gt;&quot;network-topology&quot;&lt;/span&gt;:{&lt;span class=&quot;code-quote&quot;&gt;&quot;topology&quot;&lt;/span&gt;:[{&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-id&quot;&lt;/span&gt;:&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-netconf&quot;&lt;/span&gt;}]}}
$ curl -u admin:admin http:&lt;span class=&quot;code-comment&quot;&gt;//127.0.0.1:8181/restconf/operational/network-topology:network-topology/topology/topology-netconf ;echo
&lt;/span&gt;&#160; {&lt;span class=&quot;code-quote&quot;&gt;&quot;topology&quot;&lt;/span&gt;:[{&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-id&quot;&lt;/span&gt;:&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-netconf&quot;&lt;/span&gt;}]}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Expected: &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
$ curl -u admin:admin http:&lt;span class=&quot;code-comment&quot;&gt;//127.0.0.1:8181/restconf/config/network-topology:network-topology ;echo
&lt;/span&gt;&#160; {&lt;span class=&quot;code-quote&quot;&gt;&quot;network-topology:network-topology&quot;&lt;/span&gt;:{&lt;span class=&quot;code-quote&quot;&gt;&quot;topology&quot;&lt;/span&gt;:[{&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-id&quot;&lt;/span&gt;:&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-netconf&quot;&lt;/span&gt;}]}}
$ curl -u admin:admin http:&lt;span class=&quot;code-comment&quot;&gt;//127.0.0.1:8181/restconf/operational/network-topology:network-topology/topology/topology-netconf ;echo
&lt;/span&gt; &#160;{&lt;span class=&quot;code-quote&quot;&gt;&quot;network-topology:topology&quot;&lt;/span&gt;:[{&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-id&quot;&lt;/span&gt;:&lt;span class=&quot;code-quote&quot;&gt;&quot;topology-netconf&quot;&lt;/span&gt;}]}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The same behavior is present both on draft02 and draft18 (URLs are different) and on Oxygen snapshots.&lt;/p&gt;

&lt;p&gt;This seems to be an old bug, as Draft 02 &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; examples also do contain the prefix, but even old ODL test data &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; do not expect the prefix.&lt;br/&gt;
 It is too late to change draft02 behavior as many tests are expecting that, but draft18 (and&#160;odl-restconf-nb-rfc8040 in Oxygen) should be fixed before users start to rely on this non-standard behavior.&lt;br/&gt;
 It is possible that some users would prefer shorter responses, but the standard behavior should be the default.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://tools.ietf.org/html/rfc8040#section-11.3.2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc8040#section-11.3.2&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://tools.ietf.org/html/draft-bierman-netconf-restconf-02&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/draft-bierman-netconf-restconf-02&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://github.com/opendaylight/integration-test/blob/release/lithium/test/csit/variables/bgpuser/empty.json&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/opendaylight/integration-test/blob/release/lithium/test/csit/variables/bgpuser/empty.json&lt;/a&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;manual testing&lt;/p&gt;</environment>
        <key id="29075">NETCONF-497</key>
            <summary>Json restconf responses does not prepend module name at top level</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</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="tcere">Tomas Cere</assignee>
                                    <reporter username="vrpolak">Vratko Polak</reporter>
                        <labels>
                    </labels>
                <created>Tue, 16 Jan 2018 13:11:52 +0000</created>
                <updated>Wed, 16 Jan 2019 10:54:00 +0000</updated>
                            <resolved>Wed, 16 Jan 2019 10:54:00 +0000</resolved>
                                    <version>Fluorine</version>
                    <version>Neon</version>
                    <version>Fluorine SR1</version>
                                    <fixVersion>Neon</fixVersion>
                    <fixVersion>Fluorine SR2</fixVersion>
                                    <component>restconf-nb</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="62746" author="opendaylight.release" created="Thu, 3 May 2018 09:35:38 +0000"  >&lt;p&gt;Since the bug is unassigned I&apos;m currently assigning it to you.&lt;/p&gt;

&lt;p&gt;Please assign to the relevant person.&#160;&lt;/p&gt;</comment>
                            <comment id="64818" author="rovarga" created="Tue, 28 Aug 2018 00:30:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=JakubToth&quot; class=&quot;user-hover&quot; rel=&quot;JakubToth&quot;&gt;JakubToth&lt;/a&gt; any update on this?&lt;/p&gt;</comment>
                            <comment id="66114" author="franky01hu" created="Thu, 3 Jan 2019 15:32:11 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=JakubToth&quot; class=&quot;user-hover&quot; rel=&quot;JakubToth&quot;&gt;JakubToth&lt;/a&gt;, &lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga&quot; class=&quot;user-hover&quot; rel=&quot;rovarga&quot;&gt;rovarga&lt;/a&gt; - I am also interested to know the progress on this, it is clearly a problem that ODL does not compy with RFC7951.&lt;/p&gt;

&lt;p&gt;Are there any commits available to be tested?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="31287">NETCONF-592</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|i039iv:</customfieldvalue>

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