Conversation
Notices
-
everyone that tells me that #SIP is a real alternative to #Skype: #ProveIt #SIP CANNOT operate behind #NAT
-
@coyo i thought there were a bunch of non-Skype VOIPs
-
.. I'm going to find the bastard that submitted SIP to the IETF and strangle him.
-
@coyo Without the experience with SIP, Jingle would not have occurred.
-
@lnxwalt280: they should have KNOWN that NAT would kill SIP before attempting to submit it as a standard! and i'm not saying #Jingle either
-
@coyo Submitting as an RFC allowed them to get enough implementations and users to find out about NAT issue. They thought they'd solved it.
-
@lnxwalt280: still, submitting the #RFC seems really really premature, considering we do NOT have #IPv6 yet.
-
@coyo RFCs are not necessarily standards. They are often experimental or incremental steps on a "standards track" that will lead to standard
-
fair enough. #IPv6 will probably take forever and a day to deploy, so we may as well create a solution that doesnt require IP-layer support
-
i've seen people generally link to #RFCs when referring to a standard to hold written software to, though
-
@coyo That is true. The RFC doc itself usually specifies a status. But before a standard is approved, it should have multiple ...
-
@coyo ... independent and interoperable implementations (including at least one that falls under a FLOSS license).
-
All 280 content and data are available under the