<?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>Persistent notes &#187; protocols</title>
	<atom:link href="http://alexkr.com/tag/protocols/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexkr.com</link>
	<description>Alexander Krivutsenko&#039;s online journal</description>
	<lastBuildDate>Fri, 01 Oct 2010 08:16:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Sample SCTP code for Linux</title>
		<link>http://alexkr.com/source-code/339/sample-sctp-code-for-linux/</link>
		<comments>http://alexkr.com/source-code/339/sample-sctp-code-for-linux/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 08:37:28 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[protocols]]></category>

		<guid isPermaLink="false">http://alexkr.com/?p=339</guid>
		<description><![CDATA[Instruction about compiling SCTP code on Linux]]></description>
		<wfw:commentRss>http://alexkr.com/source-code/339/sample-sctp-code-for-linux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Current state of SCTP</title>
		<link>http://alexkr.com/memos/156/sctp-on-windows/</link>
		<comments>http://alexkr.com/memos/156/sctp-on-windows/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 14:13:48 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[big]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[protocols]]></category>

		<guid isPermaLink="false">http://alexkr.com/memos/156/using-sctp-for-better-reliability/</guid>
		<description><![CDATA[SCTP is a relatively new protocol which may replace TCP for some applications which require more reliability. ]]></description>
		<wfw:commentRss>http://alexkr.com/memos/156/sctp-on-windows/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Detecting TCP connection problems</title>
		<link>http://alexkr.com/posts/150/tcp-keep-alives/</link>
		<comments>http://alexkr.com/posts/150/tcp-keep-alives/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 11:39:33 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[protocols]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/150/tcp-keep-alives/</guid>
		<description><![CDATA[The common task for any TCP networking application is to observe connection problems.

Some devepers prefer to implement their own application level &#8220;heartbeat&#8221; protocol which makes sure that TCP connection is alive.
Not all know that TCP implementations indeed have built-in way to detect and signalize connection failure.
The built-in way is called TCP &#8220;keep alives&#8221; mechanism for [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/150/tcp-keep-alives/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Short memo about RFC 3455 SIP P-Header extensions</title>
		<link>http://alexkr.com/posts/141/short-memo-about-rfc-3455-sip-p-header-extensions/</link>
		<comments>http://alexkr.com/posts/141/short-memo-about-rfc-3455-sip-p-header-extensions/#comments</comments>
		<pubDate>Sun, 03 Aug 2008 16:16:52 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[protocols]]></category>
		<category><![CDATA[sip]]></category>
		<category><![CDATA[voip]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/141/short-memo-about-rfc-3455-sip-p-header-extensions/</guid>
		<description><![CDATA[P-Associated-URI

This header is included by registrar in the 200 response to the REGISTER request.
Contains list of associated URIs. Mandatory for registrars which support this RFC.
P-Called-Party-ID

This header is included in INVITE request from proxy to user agent.
Contains destination SIP URI to which initial call was planned.
Used to provided transparent URI to the end user agent in
multiple [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/141/short-memo-about-rfc-3455-sip-p-header-extensions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Session establishment in MRCP v.2</title>
		<link>http://alexkr.com/memos/126/session-establishment-in-mrcp-v2/</link>
		<comments>http://alexkr.com/memos/126/session-establishment-in-mrcp-v2/#comments</comments>
		<pubDate>Sat, 17 Nov 2007 12:22:07 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[big]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[protocols]]></category>

		<guid isPermaLink="false">http://alexkr.com/memos/126/session-establishment-in-mrcp-v2/</guid>
		<description><![CDATA[There are no MRCP communications before SIP session is established. In order to create SIP session a client must send SIP INVITE and assign at least one control stream. The following example shows SDP parameters for SIP INVITE which is send by a client to establish MRCP control media session and audio stream to the [...]]]></description>
		<wfw:commentRss>http://alexkr.com/memos/126/session-establishment-in-mrcp-v2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mandatory DHCP options</title>
		<link>http://alexkr.com/posts/4/mandatory-dhcp-options/</link>
		<comments>http://alexkr.com/posts/4/mandatory-dhcp-options/#comments</comments>
		<pubDate>Mon, 02 May 2005 08:04:28 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[protocols]]></category>

		<guid isPermaLink="false">http://alexkr.com/uncategorized/4/mandatory-dhcp-options/</guid>
		<description><![CDATA[When implementing DHCP server it is necessary to send Server Identifier option field in the DHCPOFFER message otherwise Windows XP DHCP client will not work fine.
As RFC states you must use



  Subnet mask (DHCP option code 1)
  Router address (DHCP option code 3)
  DNS servers (DHCP option code 6)
  Server Identifier [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/4/mandatory-dhcp-options/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

