<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blog.anta.net &#187; protocols</title>
	<atom:link href="http://blog.anta.net/tag/protocols/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.anta.net</link>
	<description>Internetworking, security, safety and more</description>
	<lastBuildDate>Mon, 06 Feb 2012 11:24:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Recommendations for transport-protocol port randomisation published as RFC and BCP</title>
		<link>http://blog.anta.net/2011/01/19/recommendations-for-transport-protocol-port-randomisation-published-as-rfc-and-bcp/</link>
		<comments>http://blog.anta.net/2011/01/19/recommendations-for-transport-protocol-port-randomisation-published-as-rfc-and-bcp/#comments</comments>
		<pubDate>Wed, 19 Jan 2011 06:40:48 +0000</pubDate>
		<dc:creator>Thor Kottelin</dc:creator>
				<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[algorithms]]></category>
		<category><![CDATA[Argentina]]></category>
		<category><![CDATA[attacks]]></category>
		<category><![CDATA[BCP]]></category>
		<category><![CDATA[Fernando Gont]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[IETF]]></category>
		<category><![CDATA[Michael Vittrup Larsen]]></category>
		<category><![CDATA[NAPT]]></category>
		<category><![CDATA[NetBSD]]></category>
		<category><![CDATA[ports]]></category>
		<category><![CDATA[protocols]]></category>
		<category><![CDATA[randomisation]]></category>
		<category><![CDATA[RFC]]></category>
		<category><![CDATA[TCP]]></category>
		<category><![CDATA[Tieto]]></category>
		<category><![CDATA[transport]]></category>
		<category><![CDATA[UDP]]></category>
		<category><![CDATA[Universidad Tecnológica Nacional]]></category>

		<guid isPermaLink="false">http://blog.anta.net/?p=1499</guid>
		<description><![CDATA[The IETF has published RFC&#160;6056, “Recommendations for Transport-Protocol Port Randomization”, which is also BCP&#160;156. The document is authored by Michael Vittrup Larsen of Tieto and Fernando Gont of Argentina’s Universidad Tecnológica Nacional. A third party who knows, or succeeds in guessing, the ephemeral port numbers in use by transport protocols such as TCP and UDP [...]<script type="text/javascript">SHARETHIS.addEntry({ title: "Recommendations for transport-protocol port randomisation published as RFC and BCP", url: "http://blog.anta.net/2011/01/19/recommendations-for-transport-protocol-port-randomisation-published-as-rfc-and-bcp/" });</script>]]></description>
		<wfw:commentRss>http://blog.anta.net/2011/01/19/recommendations-for-transport-protocol-port-randomisation-published-as-rfc-and-bcp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looking for Ethernet segment peers</title>
		<link>http://blog.anta.net/2008/08/19/looking-for-ethernet-segment-peers/</link>
		<comments>http://blog.anta.net/2008/08/19/looking-for-ethernet-segment-peers/#comments</comments>
		<pubDate>Tue, 19 Aug 2008 10:55:19 +0000</pubDate>
		<dc:creator>Thor Kottelin</dc:creator>
				<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[addresses]]></category>
		<category><![CDATA[ARP]]></category>
		<category><![CDATA[broadcasts]]></category>
		<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[firewalls]]></category>
		<category><![CDATA[hosts]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[masks]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[ping]]></category>
		<category><![CDATA[protocols]]></category>
		<category><![CDATA[segments]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.anta.net/?p=310</guid>
		<description><![CDATA[As I recently wrote a brief set of instructions for checking whether there are any other Ethernet hosts on the same segment as you, I might as well post it here. Assumptions a Microsoft® Windows® workstation or server an Ethernet IPv4 network nothing prevents you from sending ping requests nothing prevents any other hosts on [...]<script type="text/javascript">SHARETHIS.addEntry({ title: "Looking for Ethernet segment peers", url: "http://blog.anta.net/2008/08/19/looking-for-ethernet-segment-peers/" });</script>]]></description>
		<wfw:commentRss>http://blog.anta.net/2008/08/19/looking-for-ethernet-segment-peers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protocol fields as advertising space</title>
		<link>http://blog.anta.net/2008/04/01/protocol-fields-as-advertising-space/</link>
		<comments>http://blog.anta.net/2008/04/01/protocol-fields-as-advertising-space/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 18:29:20 +0000</pubDate>
		<dc:creator>Thor Kottelin</dc:creator>
				<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[Aaron Falk]]></category>
		<category><![CDATA[advertising]]></category>
		<category><![CDATA[April]]></category>
		<category><![CDATA[fields]]></category>
		<category><![CDATA[IETF]]></category>
		<category><![CDATA[protocols]]></category>
		<category><![CDATA[rental]]></category>
		<category><![CDATA[revenue]]></category>
		<category><![CDATA[RFC]]></category>
		<category><![CDATA[Scott Bradner]]></category>

		<guid isPermaLink="false">http://blog.anta.net/2008/04/01/protocol-fields-as-advertising-space/</guid>
		<description><![CDATA[Today, 1&#160;April 2008, the IETF published RFC&#160;5241, “Naming Rights in IETF Protocols”. Authored by Aaron Falk and Scott Bradner, of BBN Technologies and Harvard University, respectively, the document proposes protocol field naming rights as a new revenue source for the IETF. The RFC suggests that the rental of naming rights could fetch one&#160;million&#160;USD (approximately 640&#160;kEUR) [...]<script type="text/javascript">SHARETHIS.addEntry({ title: "Protocol fields as advertising space", url: "http://blog.anta.net/2008/04/01/protocol-fields-as-advertising-space/" });</script>]]></description>
		<wfw:commentRss>http://blog.anta.net/2008/04/01/protocol-fields-as-advertising-space/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RFCs prepare for Internet emergency calls</title>
		<link>http://blog.anta.net/2008/01/08/rfcs-prepare-for-internet-emergency-calls/</link>
		<comments>http://blog.anta.net/2008/01/08/rfcs-prepare-for-internet-emergency-calls/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 06:23:14 +0000</pubDate>
		<dc:creator>Thor Kottelin</dc:creator>
				<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[Safety]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[answering]]></category>
		<category><![CDATA[calls]]></category>
		<category><![CDATA[context resolution]]></category>
		<category><![CDATA[directory assistance]]></category>
		<category><![CDATA[emergency]]></category>
		<category><![CDATA[hot lines]]></category>
		<category><![CDATA[IETF]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[locations]]></category>
		<category><![CDATA[mapping]]></category>
		<category><![CDATA[marking]]></category>
		<category><![CDATA[multimedia]]></category>
		<category><![CDATA[protocols]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[RFC]]></category>
		<category><![CDATA[routing]]></category>
		<category><![CDATA[service]]></category>
		<category><![CDATA[threats]]></category>
		<category><![CDATA[URN]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://blog.anta.net/2008/01/08/rfcs-prepare-for-internet-emergency-calls/</guid>
		<description><![CDATA[The Emergency Context Resolution with Internet Technologies Working Group of the IETF has released three RFC documents pertaining to emergency calls in IP networks. RFC 5012 &#8211; Requirements for Emergency Context Resolution with Internet Technologies Abstract This document defines terminology and enumerates requirements for the context resolution of emergency calls placed by the public using [...]<script type="text/javascript">SHARETHIS.addEntry({ title: "RFCs prepare for Internet emergency calls", url: "http://blog.anta.net/2008/01/08/rfcs-prepare-for-internet-emergency-calls/" });</script>]]></description>
		<wfw:commentRss>http://blog.anta.net/2008/01/08/rfcs-prepare-for-internet-emergency-calls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

