SR Policy dynamic candidate path

[alex4871095]

Hello,
I'm trying to configure SR Policy on FRR 8.5 and wondering if dynamic candidate path can be computed by headend router itself or it can only be computed by some external entity and announced to headend by protocols such as PCEP or BGP.
Explicit path is ok, while dynamic path segment list is marked as undefined.

!
router isis myisis
net 49.0000.0000.0000.0001.00
mpls-te on
segment-routing on
segment-routing global-block 10000 50000 local-block 60000 100000
segment-routing node-msd 16
segment-routing prefix fd00:100::1/128 index 101
exit
!
segment-routing
traffic-eng
mpls-te on
mpls-te import isis
segment-list SL1
index 10 mpls label 10104
index 20 mpls label 10103
exit
policy color 1 endpoint fd00:100::3
name SRPolicy1
binding-sid 40001
candidate-path preference 100 name CP1 explicit segment-list SL1
candidate-path preference 200 name CP2 dynamic
affinity exclude-any 0x00000001
exit
exit
exit
!

R1# show sr-te policy detail

Endpoint: fd00:100::3 Color: 1 Name: SRPolicy1 BSID: 40001 Status: Active

• Preference: 100 Name: CP1 Type: explicit Segment-List: SL1 Protocol-Origin: Local
  Preference: 200 Name: CP2 Type: dynamic Segment-List: (undefined) Protocol-Origin: Local

R1#