<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:14:47 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>[BGPCEP-1014] as-path prepending with multiple instances of own AS number missing</title>
                <link>https://jira.opendaylight.org/browse/BGPCEP-1014</link>
                <project id="10108" key="BGPCEP">bgpcep</project>
                    <description>&lt;p&gt;The as-path prepending functionality implemented in bgpcep is missing the feature to add more than one instance of own AS number defined in section section 5.1.2&#160; of RFC4271:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;   Whenever the modification of the AS_PATH attribute calls for
   including or prepending the AS number of the local system, the local
   system MAY include/prepend more than one instance of its own AS
   number in the AS_PATH attribute.  This is controlled via local
   configuration.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Currently it is possible to prepend only one instance of own AS to the path.&#160;&#160;&lt;/p&gt;
</description>
                <environment></environment>
        <key id="36124">BGPCEP-1014</key>
            <summary>as-path prepending with multiple instances of own AS number missing</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</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="GregSu">Grzegorz Sulek</reporter>
                        <labels>
                            <label>pick-next</label>
                            <label>pt</label>
                    </labels>
                <created>Sat, 20 Aug 2022 10:55:16 +0000</created>
                <updated>Wed, 24 Jan 2024 15:54:31 +0000</updated>
                                                            <fixVersion>0.21.0</fixVersion>
                    <fixVersion>0.19.9</fixVersion>
                    <fixVersion>0.20.7</fixVersion>
                                    <component>BGP</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="71418" author="rovarga" created="Sat, 20 Aug 2022 21:27:42 +0000"  >&lt;p&gt;This has a tie-in with policies, as expressed in openconfig-rp-statement. That bit of code seems to do the right thing, assuming there are multiple actions are present.&lt;/p&gt;

&lt;p&gt;As a first step, I think we need some upfront design as to how this should work &amp;#8211; either an explicit feature, or a policy thing.&lt;/p&gt;

&lt;p&gt;The other consequence of this is that path selection needs to treat the same ASN appearing consecutively in an AS_SEQUENCE is a single AS, not as an AS loop &amp;#8211; otherwise we would end up disqualifying it rather than proceeding to check the AS distance.&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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i042w7:</customfieldvalue>

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