<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: When Sockets Attack: DNS &#038; DHCP</title>
	<atom:link href="http://hostilefork.com/2008/02/20/when-sockets-attack/feed/" rel="self" type="application/rss+xml" />
	<link>http://hostilefork.com/2008/02/20/when-sockets-attack/</link>
	<description>a disgruntled developer taking a stand in the information multiverse</description>
	<pubDate>Fri, 21 Nov 2008 02:38:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Joseph</title>
		<link>http://hostilefork.com/2008/02/20/when-sockets-attack/#comment-504</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Mon, 19 May 2008 20:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://hostilefork.com/2008/02/20/when-sockets-attack/#comment-504</guid>
		<description>Some history... For baby money, back when Skye was incubating, I used to teach a course on Microsoft's implementation of DHCP and DNS service (how they work and ways they are broken). DHCP is an evolution of improvement from the BOOTP protocol we used to use that handed out addresses from a MAC address look-up table.
Today...
Many of the limitations introduced into the protocol by poor implementation of TCP/IP are being resolved these days by the protocol run on backbone networks. It allows us to run multiple (conflicting) TCP/IP networks over the same equipment by tagging or labeling (the L in MPLS) the networks as distinct. Quality of Service ( QoS ) elements are commercially available to companies that want it in their private networks.  (Net Neutrality)
The feature to support tags is a nice piece of future-proofing, that may serve it well into the future...</description>
		<content:encoded><![CDATA[<p>Some history&#8230; For baby money, back when Skye was incubating, I used to teach a course on Microsoft&#8217;s implementation of DHCP and DNS service (how they work and ways they are broken). DHCP is an evolution of improvement from the BOOTP protocol we used to use that handed out addresses from a MAC address look-up table.<br />
Today&#8230;<br />
Many of the limitations introduced into the protocol by poor implementation of TCP/IP are being resolved these days by the protocol run on backbone networks. It allows us to run multiple (conflicting) TCP/IP networks over the same equipment by tagging or labeling (the L in MPLS) the networks as distinct. Quality of Service ( QoS ) elements are commercially available to companies that want it in their private networks.  (Net Neutrality)<br />
The feature to support tags is a nice piece of future-proofing, that may serve it well into the future&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
