BGP Prefix SID is not announced to iBGP peer

On my machine I have two karaf instances running iBGP peers.

I create application peer on Node2 and program following route:

PUT

http://localhost:8182/restconf/config/bgp-rib:application-rib/192.168.1.10/tables/bgp-types:ipv4-address-family/bgp-labeled-unicast:labeled-unicast-subsequent-address-family/bgp-labeled-unicast:labeled-unicast-routes/labeled-unicast-route/route/1

 

{

  "bgp-labeled-unicast:labeled-unicast-route": [

    {

      "path-id": 1,

      "route-key": "route",

      "attributes": {

        "local-pref":

{           "pref": 100         }

,

        "bgp-prefix-sid": {

          "bgp-prefix-sid-tlvs": [

           

{               "label-index-tlv": 4             }

,

            {

              "srgb-value": [

               

{                   "range": 8000,                   "base": 16000                 }

              ]

            }

          ]

        },

        "ipv4-next-hop":

{           "global": "10.23.1.3"         }

,

        "as-path": {},

        "origin":

{           "value": "igp"         }

      },

      "label-stack": [

       

{           "label-value": 16002         }

      ],

      "prefix": "10.100.1.4/24"

    }

  ]

}

 

It is written to LocRib on Node2:

GET http://localhost:8182/restconf/operational/bgp-rib:bgp-rib/rib/bgp-example/loc-rib

 

Same route is visible in adj-rib-out:

GET http://localhost:8182/restconf/operational/bgp-rib:bgp-rib/rib/bgp-example/peer/bgp:%2F%2F192.168.1.1/adj-rib-out

 

But adj-rib-in on Node1 is missing bgp-refix-sid attribute:

GET http://localhost:8181/restconf/operational/bgp-rib:bgp-rib/rib/bgp-example/peer/bgp:%2F%2F192.168.1.2/adj-rib-in

(…)

      {

        "afi": "bgp-types:ipv4-address-family",

        "safi": "bgp-labeled-unicast:labeled-unicast-subsequent-address-family",

        "bgp-labeled-unicast:labeled-unicast-routes": {

          "labeled-unicast-route": [

            {

              "path-id": 1,

              "route-key": "AAAAATAD6CEKZAE=",

              "attributes": {

                "local-pref":

{                   "pref": 100                 }

,

                "ipv4-next-hop":

{                   "global": "10.23.1.3"                 }

,

                "as-path": {},

                "origin":

{                   "value": "igp"                 }

              },

              "label-stack": [

                

{                   "label-value": 16002                 }

              ],

              "prefix": "10.100.1.0/24"

            }

          ]

        },

        "attributes":

{           "uptodate": true         }

      }

(…)

 

Also it is not written to loc-rib on Node1.

After lookig at the logs (attached), it looks like

both BGPMessageToByteEncoder on Node2

and BGPByteToMessageDecoder on Node1

report the same binary representation of BGP update that was sent.

 

But while BGPMessageToByteEncoder on Node2 logs bgp-prefix-sid attributes,

BGPUpdateMessageParser on Node1 does not.

 

Is it a bug or my configuration is invalid?