There are several plausible scenarios where you could have the same contact URI appear twice. For example, limitations in the capabilities description may not allow you to express "this URI can do A1,A2,A3 OR it can do B1,B2,B3" (but not random combinations of sub-capabilities such as A1,B1).Out of curiosity, is there anything that says that the contact uri must be unique within the composed document? With the service tuples being identified by tuple-id:s, is there anything preventing to such tuples having the same contact uri:s?
_______________________________________________ Simple mailing list Simple at ietf.org https://www1.ietf.org/mailman/listinfo/simple