<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:32:48 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>[OPNFLWPLUG-558] Broken protocol handling part 1 - incorrect handshake</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-558</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;Controller disregards switch responses during handshake phase in OpenFlow 1.3&lt;/p&gt;

&lt;p&gt;Example. The switch sends a FEATURE REPLY which says:&lt;/p&gt;

&lt;p&gt;FLOW_STATS: False&lt;br/&gt;
TABLE_STATS: False&lt;br/&gt;
QUEUE_STATS: False&lt;/p&gt;

&lt;p&gt;The controller immediately replies with OFPMP METER FEATURES&lt;/p&gt;

&lt;p&gt;That is broken - you are not supposed to ask the switch for meter features if it has not got any in the first place.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27826">OPNFLWPLUG-558</key>
            <summary>Broken protocol handling part 1 - incorrect handshake</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="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="aivanov@brocade.com">Anton Ivanov</reporter>
                        <labels>
                    </labels>
                <created>Tue, 6 Oct 2015 09:05:38 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:39 +0000</updated>
                            <resolved>Tue, 6 Oct 2015 10:16:32 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="57350" author="mirehak@cisco.com" created="Tue, 6 Oct 2015 09:34:03 +0000"  >&lt;p&gt;Talking about He-codebase, right?&lt;/p&gt;</comment>
                            <comment id="57351" author="aivanov@brocade.com" created="Tue, 6 Oct 2015 10:16:32 +0000"  >&lt;p&gt;Yes. &lt;/p&gt;

&lt;p&gt;I will test the new one shortly with and without the config setting and if it does not behave per spec file that separately.&lt;/p&gt;

&lt;p&gt;I discussed this one with Anil - the spec is actually flawed here and the old behavior is probably the only way to work around the flaw.&lt;/p&gt;

&lt;p&gt;I assumed that you can imply that there are no meter stats if the stat related feature bits are False. However that is not the case as the spec appears to not have a direct FeatureReply feature bit to METER_FEATURES in the first place.&lt;/p&gt;

&lt;p&gt;I am going to close this one and continue going through the FSM (or to be more exact lack of) in the protocol handler and filing bugs for both old and new.&lt;/p&gt;</comment>
                    </comments>
                    <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>4419</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=4419]]></customfieldvalue>

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

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