ipv4-extended-tunnel-id showing backwards when LSP is operational down

Bug exists since Beryllium at least.

Reproduce:

1. Create a PCC-inited LSP
2. Observe the network topology, ipv4 under reported-lsp/path/lsp/tlvs/lsp-identifiers is displayed like this:

<ipv4>
<ipv4-tunnel-endpoint-address>192.168.254.3</ipv4-tunnel-endpoint-address>
<ipv4-tunnel-sender-address>192.168.254.1</ipv4-tunnel-sender-address>
<ipv4-extended-tunnel-id>192.168.254.3</ipv4-extended-tunnel-id>
</ipv4>

3. Make the LSP operational down
4. Check the network topology again, now the ipv4 is showing like this

<ipv4>
<ipv4-tunnel-endpoint-address>192.168.254.6</ipv4-tunnel-endpoint-address>
<ipv4-tunnel-sender-address>192.168.254.1</ipv4-tunnel-sender-address>
<ipv4-extended-tunnel-id>6.254.168.192</ipv4-extended-tunnel-id>
</ipv4>

5. The ipv4-extended-tunnel-id is recovered to correct value when operational is back to UP.

• Tested with Cisco XRV 5.3 as router

Is this behavior expected?