Should requireParentForOutgoingSpans also suppress further child spans?

[evantorrie]

In @opentelemetry/instrumentation-http, the requireParentSpanForOutgoingSpans operates as the documentation specifies, which is to prevent an http span from being created if there is no parent span currently active.

However, it doesn't say anything about further child spans of the HTTP request.

For example

• @opentelemetry/instrumentation-dns will still generate a span for any required DNS lookup such as the hostname specified in the HTTP url
• @opentelemetry/instrumentation-net tcp.connect and tls.connect spans will both be generated by the net instrumentation.

These spans appear without the http parent span, but in doing so, can be confusing to the user who may not understand why a dns lookup and a tcp.connect is happening when they turned requireParentForOutgoingSpans: true on for HTTP instrumentation.

Would it make more sense that requireParentForOutgoingSpans: true have its semantics changed, or another option provided, that not only omits the HTTP span, but also sets a suppressInstrumentation on the current context such that no further spans will be created by other instrumentation until the HTTP call completes?