Some of the reasons why Universal Plug and Play (UPnP) did not adopt Service Location Protocol V2 (SLP a.k.a Rendezvous) as its discovery protocol. Continue reading Service Location Protocol V2 – An Analysis
Category: Internet Protocols
Articles relating to Internet Protocols, protocol design issues, etc.
OpenNic
This web page is available via http://www.goland.geek. IANA's incompetence and bad faith has reached legendary status in the Internet community and we desperately need an alternative. I don't claim that OpenNic has the solution but we have to do something. I now point my PC's DNS resolution to http://www.opennic.unrated.net/personal.html. Yes, this has obvious privacy ramifications but I'm willing to live with it. Thanks to Simkin for hosting my .geek DNS record.
Royalty Free/Reciprocal
How can something be a de jure standard and still not be open and freely available? When it's license isn't Royalty Free/Reciprocal.
Continue reading Royalty Free/Reciprocal
The Difference between RPCs and Protocols
So what's the difference between RPCs and Protocols and why does it matter? Continue reading The Difference between RPCs and Protocols
Jim Whitehead's Comments
Jim Whitehead's Comments on my article comparing protocols and RPCs. Continue reading Jim Whitehead's Comments
Yaron's WebDAV Agenda
The purpose of this document is to provide a quick introduction to the full power of the WebDAV (http://www.webdav.org) data model.
UPnP Security Flaws
Why TLS doesn't replace VPN for Enterprise customers
If you can establish a TLS connection to your enterprise remotely. then why do you need VPN/IPSEC? Given that any TCP based protocol can be run over TLS it would seem that the ubiquitous support for TLS has solved our remote access end-to-end security problems.
Continue reading Why TLS doesn't replace VPN for Enterprise customers
Limitations of IP Multicasting
For a long time there has been the distant promise that someday we would all just use IP multicasting for distributing content through the Internet. The idea that one could send a packet to one address and have it magically appear at multiple destinations was a compelling one. However IP Multicast has never taken off outside of Intranets. I believe that the fundamental reason for IP Multicast's failure to reach its promised potential is that IP Multicast does not scale very well. Specifically, each router on the distribution path of an IP Multicast must allocate memory to remember that multicast for the length of the multicast session. This means that as the number of multicast sessions that cross that router grow so will the amount of memory the router has to allocate. While the rate of increase of multicast sessions is exponential the rate of increase of memory required is linear.
Multi-Protocol Support – or – Yes, there is more than just HTTP
There will not be one protocol to rule them all.
Continue reading Multi-Protocol Support – or – Yes, there is more than just
HTTP