<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:53:53 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>[CONTROLLER-793] Yang capabilities without revision should be supported in ODL</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-793</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;One more query related to revision of schema sources&lt;br/&gt;
#1 right now ODL does not support scheam sources without revision.&lt;br/&gt;
which leads to Bug in Yang specification and ODL&lt;/p&gt;

&lt;p&gt;already commented on &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-641&quot; title=&quot;Read Yang files from Local if device reported capabilities don&amp;#39;t have the revision&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-641&quot;&gt;&lt;del&gt;CONTROLLER-641&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Regarding this bug, there is plenty of evidence in RFC 6020 that the first revision of a YANG module does not need to have a &quot;revision&quot; statement, and hence not needed in the &amp;lt;hello&amp;gt; message, but section 5.6.4.1 says:&lt;/p&gt;

&lt;p&gt;   &quot;A server MUST advertise all revisions of all modules it implements.&quot;&lt;/p&gt;

&lt;p&gt;Which seems contradictory.  Discussing with the NETMOD WG, it is agreed that the sentence should have been written:&lt;/p&gt;

&lt;p&gt;   &quot;A server MUST advertise all known revisions of all modules it implements.&quot;&lt;/p&gt;

&lt;p&gt;Thus providing the necessary leeway.&lt;/p&gt;

&lt;p&gt;FWIW, the only time it is envisioned a YANG module not wanting to have an initial revision date is when the module itself is already version-specific (e.g., &lt;a href=&quot;http://xml.juniper.net/netconf/junos/14.2R2.4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://xml.juniper.net/netconf/junos/14.2R2.4&lt;/a&gt;), which clearly will have one and only one revision.  In all other cases, it seems the module is expected to be versioned over time and therefore SHOULD have a revision statement.  For this reason, the NETMOD WG may also add a clarifying statement into section 7.1.9.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Linux&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="25347">CONTROLLER-793</key>
            <summary>Yang capabilities without revision should be supported in ODL</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <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="10002">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ankit21.a@tcs.com">Ankit agarwal</reporter>
                        <labels>
                    </labels>
                <created>Tue, 9 Sep 2014 06:54:20 +0000</created>
                <updated>Thu, 19 Oct 2017 22:13:18 +0000</updated>
                            <resolved>Tue, 9 Sep 2014 06:56:02 +0000</resolved>
                                    <version>Helium</version>
                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="49090" author="ankit21.a@tcs.com" created="Tue, 9 Sep 2014 06:56:02 +0000"  >&lt;p&gt;Is same as &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-641&quot; title=&quot;Read Yang files from Local if device reported capabilities don&amp;#39;t have the revision&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-641&quot;&gt;&lt;del&gt;CONTROLLER-641&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="25195">CONTROLLER-641</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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1762</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=1762]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02mlb:</customfieldvalue>

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