<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:57 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-809] Add support for RFC8639 subscribed notifications</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-809</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;&lt;a href=&quot;https://datatracker.ietf.org/doc/html/rfc8639&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;RFC8639&lt;/a&gt; augments&#160;&#160;&lt;a href=&quot;https://datatracker.ietf.org/doc/html/rfc5277&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;RFC5277&lt;/a&gt; and&#160;&lt;a href=&quot;https://datatracker.ietf.org/doc/html/rfc6241&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;RFC6241&lt;/a&gt; notifications with important protocol mechanics that make them actually usable.&lt;/p&gt;

&lt;p&gt;Add complete support for RFC8639 notifications across all layers.&lt;/p&gt;</description>
                <environment></environment>
        <key id="34325">NETCONF-809</key>
            <summary>Add support for RFC8639 subscribed notifications</summary>
                <type id="10000" iconUrl="https://jira.opendaylight.org/images/icons/issuetypes/epic.svg">Epic</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                            <label>pt</label>
                    </labels>
                <created>Thu, 26 Aug 2021 20:03:03 +0000</created>
                <updated>Tue, 1 Aug 2023 18:10:40 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="69536" author="rovarga" created="Thu, 26 Aug 2021 21:09:11 +0000"  >&lt;p&gt;Unifying exceptions is critical for a sane protocol interconnect&lt;/p&gt;</comment>
                            <comment id="70901" author="JIRAUSER14307" created="Thu, 21 Apr 2022 09:13:09 +0000"  >&lt;p&gt;Hi, does this new feature have planned target release, i.e. is this targeted for Chlorine/Argon?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="71005" author="rovarga" created="Sun, 24 Apr 2022 23:11:06 +0000"  >&lt;p&gt;First of all, this is an Epic covering two protocols as well as two distinct feature sets. That pretty much guarantees this will be delivered across a number of releases.&lt;br/&gt;
The issues in this epic are a very basic decomposition of what needs to happen to cover the basics of the specification. The list is likely to grow as the design/implementation proceeds, when it does.&lt;/p&gt;

&lt;p&gt;There is at least one dependecy for the entire effort on which the design work, much less an actual implementation, has not started yet. There are a number of dependencies in the individual issues that need to be addressed before those issues can reasonably be worked on. &lt;/p&gt;

&lt;p&gt;Given the number and the skillset of current full-time contributors (and delivering this item is a full-time effort), I cannot really estimate delivery times for the bits and pieces, much less for the entire epic.&lt;/p&gt;

&lt;p&gt;The usual open-source mantra applies: &quot;focus follows interest&quot;. It could be as soon as in 3 months, it could well be in 2 years.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="34167">MDSAL-675</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="34112">YANGTOOLS-1297</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="34231">NETCONF-793</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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_10005" key="com.pyxis.greenhopper.jira:gh-epic-color">
                        <customfieldname>Epic Color</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ghx-label-1</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10004" key="com.pyxis.greenhopper.jira:gh-epic-label">
                        <customfieldname>Epic Name</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Subscribed notifications</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10003" key="com.pyxis.greenhopper.jira:gh-epic-status">
                        <customfieldname>Epic Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[To Do]]></customfieldvalue>

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

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