Simultaneous Peer Connections

I am running into an issue with simultaneous peer connections between
users. The issue is when pairing WebRTC with a presence service, if user A
sees user B and initiates a connection at the same time that user B sees
user A and initiates a connection back both of them are in offer states.
Since they are both in offer states neither of them can accept the other
offer request without either creating two connections or jumping through
hoops to figure out who is the leader and who is the follower and dropping
one of the requests.

My question would be if the spec would be able to handle such a case and if
not, what is the best way to get around this issue? I am pretty much
building the jumping through hoops part into my JavaScript library to avoid
this issue and it is proving to be a hassle of getting the timing right.

Thanks,

Dan Ristic
PubNub