Asymetric API on DataChannels creation

When you call to createDataChannel() you get a "connecting" DataChannel,
and when connection gets stablished you get an "open" event over it. On the
other hand, on the receiver side you only get a "datachannel" event with
the new DataChannel, thats already open. Doesn't it makes more sense that
the "datachannel" event raise a "connecting" DataChannel to be able to do
pre-open initializations and later raise the "open" event instead of do
both things at the same time? This would also easy to reuse code on
applications when both end are symetric.

If it's done this way just to ear a data flight, it would be mimic just
setting on the specification the "datachannel" event before
setting/changing the status to "open" and adding afterthat an "open" event.