Natively, DRCP supports connection tagging, which is a single label without weights. So, labeling with single label works transparently if you use UCP with DRCP. Multiple label UCP connections work, but they have the following behavior changes:

• The cost method in the ConnectionLabelingCallback API is not invoked if you use UCP with DRCP using connection labeling

• UCP can invoke the configure method in the ConnectionLabelingCallback API more with DRCP configuration than without DRCP configuration.