>
"It would be silly to let your multi-gigabyte file transfer DoS your VoIP call."1. I think it would be silly to assume a reasonable person would propose sending multi-gigabyte files down a VoIP connection. You might want to consider asking people if there was a miscommunication before assuming they're unreasonable or ignorant.
2. I thought the qualifier that it would remove the need to open a second app was sufficient to indicate that I was talking about opening a second app. Ergo "connection" meant the human-process of mapping a VoIP contact to a data-transfer app/credentials, opening second app, sending file, etc.
3. No, a second physical connection for the file stream doesn't necessarily mean "everything would work fine". Anything that requires a new protocol/extension would make classification of the product/feature/service game to be, well, gamed, by the ISP, for profit.
As the VoIP connection itself would need to at least be modified to signal/establish the physical data connection, you'd necessarily have a protocol variant - even if the file transfer itself was, say, ftp.
4. The whole point of the example is just "New product that extends old protocol, thereby giving ISP chance to QoS-round-file new product rather than compete". Focusing on the example itself is just wasting our time.
> "I think Google is aware that any agreement would need more teeth than trusting the goodness of Verizon's heart to comply."
I think Google is doing nothing more than hedging against the possibility that legislation will undercut the FCC's net neutrality kick; particularly given legislative power being likely to tip back to the strongly pro-corporate side.
I sincerely doubt they're negotiating with Verizon over treatment of any traffic that does not come from Google.