<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/search/ietf">
<title>Public marks with search ietf</title>
<description>Public marks with search ietf</description>
<link>http://blogmarks.net/marks/search/ietf</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058223093"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058223071"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058223054"/>
<rdf:li resource="http://blogmarks.net/api/user/znarf/mark/1058219501"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058169640"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058157611"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058057359"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058206105"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057992787"/>
<rdf:li resource="http://blogmarks.net/api/user/benoit/mark/1057929060"/>
<rdf:li resource="http://blogmarks.net/api/user/jey/mark/1058545442"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1057788133"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057755073"/>
<rdf:li resource="http://blogmarks.net/api/user/effraie/mark/1057749688"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1057698553"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057579240"/>
<rdf:li resource="http://blogmarks.net/api/user/keusta/mark/1057488099"/>
<rdf:li resource="http://blogmarks.net/api/user/greut/mark/1057487989"/>
<rdf:li resource="http://blogmarks.net/api/user/rodo/mark/1057449689"/>
<rdf:li resource="http://blogmarks.net/api/user/camel/mark/1057422964"/>
<rdf:li resource="http://blogmarks.net/api/user/CharlesNepote/mark/1057339842"/>
<rdf:li resource="http://blogmarks.net/api/user/benoit/mark/1057229142"/>
<rdf:li resource="http://blogmarks.net/api/user/omarvillota/mark/2506574"/>
<rdf:li resource="http://blogmarks.net/api/user/omarvillota/mark/2506515"/>
<rdf:li resource="http://blogmarks.net/api/user/pyxosledisciple/mark/2054169"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058223093">
<title>Statistics on reusing request headers in persistent connections from Koen Holtman on 1995-10-30 (ietf-http-wg-old@w3.org from September to December 1995)</title>
<link>http://lists.w3.org/Archives/Public/ietf-http-wg-old/1995SepDec/0415.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;To make the statistics below, I took a set of proxy&amp;lt;-&gt;server HTTP transactions between the www.win.tue.nl proxy and off-campus servers (18 days worth of traffic, approximately 150Mb in 14501 HTTP transactions)&lt;/p&gt;&lt;/blockquote&gt;

Old survey</description>
<dc:date>2009-02-27T02:07:10Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, survey, html</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lists.w3.org/Archives/Public/ietf-http-wg-old/1995SepDec/0415.html"><img border="0" src="http://blogmarks.net/screenshots/2009/02/27/fcfa155f3ba9881636bf8a12ce01aacb.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lists.w3.org/Archives/Public/ietf-http-wg-old/1995SepDec/0415.html">Statistics on reusing request headers in persistent connections from Koen Holtman on 1995-10-30 (ietf-http-wg-old@w3.org from September to December 1995)</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>To make the statistics below, I took a set of proxy&lt;->server HTTP transactions between the www.win.tue.nl proxy and off-campus servers (18 days worth of traffic, approximately 150Mb in 14501 HTTP transactions)</p></blockquote>

Old survey</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/survey">survey</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058223093">Copy</a> | 
<a href="http://blogmarks.net/link/3111625">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058223071">
<title>W3C WD: HTML Dialects: Internet Media Types and SGML Document Types</title>
<link>http://www.w3.org/MarkUp/WD-doctypes</link>
<description>&lt;blockquote&gt;&lt;p&gt;The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the &quot;-//IETF//DTD HTML 2.0//EN&quot; document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-02-27T00:46:02Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>w3c, html, specification</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.w3.org/MarkUp/WD-doctypes"><img border="0" src="http://blogmarks.net/screenshots/2009/02/27/80154ad8da06abfdfe4d186f2616d76e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.w3.org/MarkUp/WD-doctypes">W3C WD: HTML Dialects: Internet Media Types and SGML Document Types</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the "-//IETF//DTD HTML 2.0//EN" document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/w3c">w3c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/specification">specification</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058223071">Copy</a> | 
<a href="http://blogmarks.net/link/3111603">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058223054">
<title>W3C WD: HTML Dialects: Internet Media Types and SGML Document Types</title>
<link>http://www.w3.org/TR/WD-doctypes</link>
<description>&lt;blockquote&gt;&lt;p&gt;The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the &quot;-//IETF//DTD HTML 2.0//EN&quot; document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-02-27T00:01:14Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>w3c, html, w3cnote</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.w3.org/TR/WD-doctypes"><img border="0" src="http://blogmarks.net/screenshots/2009/02/27/43ddbff9c7c0af0604a6d2e4c3411426.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.w3.org/TR/WD-doctypes">W3C WD: HTML Dialects: Internet Media Types and SGML Document Types</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the "-//IETF//DTD HTML 2.0//EN" document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/w3c">w3c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/w3cnote">w3cnote</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058223054">Copy</a> | 
<a href="http://blogmarks.net/link/3111580">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/znarf/mark/1058219501">
<title>Joe Gregorio | BitWorking | OAuth IETF Charter</title>
<link>http://bitworking.org/news/411/oauth-ietf-charter</link>
<description></description>
<dc:date>2009-02-23T21:20:11Z</dc:date>
<dc:author>François Hodierne</dc:author>
<dc:subject>oAuth, ietf</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://bitworking.org/news/411/oauth-ietf-charter"><img border="0" src="http://blogmarks.net/screenshots/2009/02/23/7ecd4f4dca0686c64f1d38d168be70a2.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://bitworking.org/news/411/oauth-ietf-charter">Joe Gregorio | BitWorking | OAuth IETF Charter</a></h4>
 
by <a href="http://blogmarks.net/user/znarf">François Hodierne</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/oAuth">oAuth</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ietf">ietf</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058219501">Copy</a> | 
<a href="http://blogmarks.net/link/3108459">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058169640">
<title>&quot;IETF is a black hole.&quot; Sam Ruby 18 May 2004</title>
<link>http://www.w3.org/2004/05/18-atom-nyc</link>
<description>&lt;blockquote&gt;&lt;p&gt;sr - sam ruby, IBM
: IETF is a black hole. I'm not thrilled with them. But it has an external perception of being open.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-01-24T22:09:03Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>atom, ietf</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.w3.org/2004/05/18-atom-nyc"><img border="0" src="http://blogmarks.net/screenshots/2009/01/24/54d332f98a52a361ac234c828a4b2e7a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.w3.org/2004/05/18-atom-nyc">&quot;IETF is a black hole.&quot; Sam Ruby 18 May 2004</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/442">2 other(s)</a> 
<div class="description"><blockquote><p>sr - sam ruby, IBM
: IETF is a black hole. I'm not thrilled with them. But it has an external perception of being open.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ietf">ietf</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058169640">Copy</a> | 
<a href="http://blogmarks.net/link/442">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1058157611">
<title>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) </title>
<link>http://www.ietf.org/rfc/rfc2324.txt</link>
<description>Sure the most funny IETF RFC that I have been given to read. This document specifies a Hyper Text Coffee Pot Control Protocol (HTCPCP), based on HTTP, which permits the full request and responses necessary to control all devices capable of making the popular caffeinated hot beverages.
</description>
<dc:date>2009-01-12T11:04:13Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>http, httcpcp, joke, coffee, geeeeeeeeeek, protocol, rfc, standard</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ietf.org/rfc/rfc2324.txt"><img border="0" src="http://blogmarks.net/screenshots/2009/01/12/4dbb8f7c9b0cb4bd0bd14d439112d963.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ietf.org/rfc/rfc2324.txt">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) </a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/706445">1 other(s)</a> 
<p class="description">Sure the most funny IETF RFC that I have been given to read. This document specifies a Hyper Text Coffee Pot Control Protocol (HTCPCP), based on HTTP, which permits the full request and responses necessary to control all devices capable of making the popular caffeinated hot beverages.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/httcpcp">httcpcp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/joke">joke</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/coffee">coffee</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geeeeeeeeeek">geeeeeeeeeek</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/protocol">protocol</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rfc">rfc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standard">standard</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058157611">Copy</a> | 
<a href="http://blogmarks.net/link/706445">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058057359">
<title>HTTPmail ietf draft</title>
<link>http://www.ietf.org/internet-drafts/draft-dusseault-httpmail-00.txt</link>
<description>&lt;blockquote&gt;&lt;p&gt;This document proposes a standard format and a standard navigation mechanism so that mail stores can provide interoperable access to mailboxes and messages over HTTP. Mailbox contents and listings of mailboxes are exposed as Atom Feeds, while messages themselves are downloaded as a document of type message/822. Each mailbox and each message is assigned an HTTP URL, and if permissions checks are satisfied, each message may be downloaded independently. &lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2008-11-13T06:05:21Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, atom, email, rest</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ietf.org/internet-drafts/draft-dusseault-httpmail-00.txt"><img border="0" src="http://blogmarks.net/screenshots/2008/11/13/87aeca9d66976940ae2c4ea7d9334ada.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ietf.org/internet-drafts/draft-dusseault-httpmail-00.txt">HTTPmail ietf draft</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This document proposes a standard format and a standard navigation mechanism so that mail stores can provide interoperable access to mailboxes and messages over HTTP. Mailbox contents and listings of mailboxes are exposed as Atom Feeds, while messages themselves are downloaded as a document of type message/822. Each mailbox and each message is assigned an HTTP URL, and if permissions checks are satisfied, each message may be downloaded independently. </p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rest">rest</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058057359">Copy</a> | 
<a href="http://blogmarks.net/link/2966091">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058206105">
<title>hcalendar-fr - Microformats</title>
<link>http://microformats.org/wiki/hcalendar-fr</link>
<description>hCalendar est un format simple, ouvert, distribué pour le calendrier et les événements, fondé sur le standard iCalendar (RFC2445 (http://www.ietf.org/rfc/rfc2445.txt)), adaptable pour l'embarquement dans HTML ou XHTML, Atom, RSS et le XML arbitraire. hCalendar est l'un des nombreux standards ouverts microformat.  Vous voulez démarrer par écrire un événement hCalendar ? Utilisez le hCalendar creator (http://microformats.org/code/hcalendar/creator) pour écrire un événement et le publier, ou suivez les trucs de publication hCalendar pour ajouter de la syntaxe hCalendar à votre page d'évènements à venir ou des événements que vous mentionnez dans vos billets de blogs, wikis, etc.</description>
<dc:date>2008-11-04T11:47:15Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>reference, event, evenement, calendar, xml, calendrier, documentation, microformat</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://microformats.org/wiki/hcalendar-fr"><img border="0" src="http://blogmarks.net/screenshots/2007/02/19/b3d4c713ac0b9cc3d8fe16985f981f46.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://microformats.org/wiki/hcalendar-fr">hcalendar-fr - Microformats</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1116349">2 other(s)</a> 
<p class="description">hCalendar est un format simple, ouvert, distribué pour le calendrier et les événements, fondé sur le standard iCalendar (RFC2445 (http://www.ietf.org/rfc/rfc2445.txt)), adaptable pour l'embarquement dans HTML ou XHTML, Atom, RSS et le XML arbitraire. hCalendar est l'un des nombreux standards ouverts microformat.  Vous voulez démarrer par écrire un événement hCalendar ? Utilisez le hCalendar creator (http://microformats.org/code/hcalendar/creator) pour écrire un événement et le publier, ou suivez les trucs de publication hCalendar pour ajouter de la syntaxe hCalendar à votre page d'évènements à venir ou des événements que vous mentionnez dans vos billets de blogs, wikis, etc.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reference">reference</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/event">event</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/evenement">evenement</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/calendar">calendar</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/calendrier">calendrier</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/documentation">documentation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformat">microformat</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058206105">Copy</a> | 
<a href="http://blogmarks.net/link/1116349">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057992787">
<title>Not a standard debate</title>
<link>http://www.business-standard.com/india/storypage.php?autono=335446</link>
<description>&lt;blockquote&gt;&lt;p&gt;Second, according to sources close to the development, the Bureau of Indian Standards (BIS) — which met in New Delhi on the 22nd of this month — is reviewing the ISO transparency issue while simultaneously exploring alternate standards which emerge from bodies like the W3C and the Internet Engineering Task Force (IETF).&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2008-09-25T07:07:49Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>w3c, standards</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.business-standard.com/india/storypage.php?autono=335446"><img border="0" src="http://blogmarks.net/screenshots/2008/09/25/14fbf6dbc44276e080e4550dbeafb7e6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.business-standard.com/india/storypage.php?autono=335446">Not a standard debate</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Second, according to sources close to the development, the Bureau of Indian Standards (BIS) — which met in New Delhi on the 22nd of this month — is reviewing the ISO transparency issue while simultaneously exploring alternate standards which emerge from bodies like the W3C and the Internet Engineering Task Force (IETF).</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/w3c">w3c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057992787">Copy</a> | 
<a href="http://blogmarks.net/link/2908597">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/benoit/mark/1057929060">
<title>IETF Tools</title>
<link>http://wiki.tools.ietf.org/</link>
<description></description>
<dc:date>2008-07-28T04:57:19Z</dc:date>
<dc:author>benoit</dc:author>
<dc:subject>ietf, tools, wiki, trac</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wiki.tools.ietf.org/"><img border="0" src="http://blogmarks.net/screenshots/2008/07/28/04dec4416f11914adcac40544c8e54bd.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wiki.tools.ietf.org/">IETF Tools</a></h4>
 
by <a href="http://blogmarks.net/user/benoit">benoit</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ietf">ietf</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wiki">wiki</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/trac">trac</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057929060">Copy</a> | 
<a href="http://blogmarks.net/link/2850788">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jey/mark/1058545442">
<title>http://www.ietf.org/rfc/rfc4949.txt</title>
<link>http://www.ietf.org/rfc/rfc4949.txt</link>
<description></description>
<dc:date>2008-07-23T22:17:12Z</dc:date>
<dc:author>jey</dc:author>
<dc:subject>IET, glossary, security, internet</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ietf.org/rfc/rfc4949.txt"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ietf.org/rfc/rfc4949.txt">http://www.ietf.org/rfc/rfc4949.txt</a></h4>
 
by <a href="http://blogmarks.net/user/jey">jey</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/IET">IET</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/glossary">glossary</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/security">security</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/internet">internet</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058545442">Copy</a> | 
<a href="http://blogmarks.net/link/3379576">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1057788133">
<title>Quel format de syndication choisir? RSS, RDF, Atom?</title>
<link>http://www.scriptol.fr/rss/choisir-format.php</link>
<description>Bien que d'autres solutions aient été proposées dans le passé, trois formats de syndication ont émergé:
- RSS 2.0, ou Really Simple Syndication, par Harvard
- RSS 1.0, ou Rich Site Summary, par le groupe RSS-DEV, et
- Atom par IETF, format largement utilisé mais toujours en cours de définition.</description>
<dc:date>2008-04-11T14:13:48Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>rss, atom, syndication, DocumentationTools, faq</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.scriptol.fr/rss/choisir-format.php"><img border="0" src="http://blogmarks.net/screenshots/2008/04/11/e87c69cc90ce52db9703469dc2e5011a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.scriptol.fr/rss/choisir-format.php">Quel format de syndication choisir? RSS, RDF, Atom?</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Bien que d'autres solutions aient été proposées dans le passé, trois formats de syndication ont émergé:
- RSS 2.0, ou Really Simple Syndication, par Harvard
- RSS 1.0, ou Rich Site Summary, par le groupe RSS-DEV, et
- Atom par IETF, format largement utilisé mais toujours en cours de définition.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rss">rss</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/syndication">syndication</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/DocumentationTools">DocumentationTools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/faq">faq</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057788133">Copy</a> | 
<a href="http://blogmarks.net/link/2741010">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057755073">
<title>Comment etendre en HTML</title>
<link>https://listserv.heanet.ie/cgi-bin/wa?A2=ind9510&amp;L=html-wg&amp;T=0&amp;F=&amp;S=&amp;P=11212</link>
<description>&lt;blockquote&gt;&lt;p&gt;The HTML WG has several times expressed a strong preference that HTML be officially extended only by standards-track &quot;versions&quot;, not by registered extensions. This is the reason why proposed individual feature extensions are being handled with experimental RFCs, rather than as standards-track ones. The responsible Applications Area Director would prefer that IANA start a registry of this type only in coordination with that WG, lest the registration mechanism become an alternative to normal IETF processing.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2008-03-27T14:19:04Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>html5</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://listserv.heanet.ie/cgi-bin/wa?A2=ind9510&amp;L=html-wg&amp;T=0&amp;F=&amp;S=&amp;P=11212"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://listserv.heanet.ie/cgi-bin/wa?A2=ind9510&amp;L=html-wg&amp;T=0&amp;F=&amp;S=&amp;P=11212">Comment etendre en HTML</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>The HTML WG has several times expressed a strong preference that HTML be officially extended only by standards-track "versions", not by registered extensions. This is the reason why proposed individual feature extensions are being handled with experimental RFCs, rather than as standards-track ones. The responsible Applications Area Director would prefer that IANA start a registry of this type only in coordination with that WG, lest the registration mechanism become an alternative to normal IETF processing.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057755073">Copy</a> | 
<a href="http://blogmarks.net/link/2718565">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/effraie/mark/1057749688">
<title>IETF Documents</title>
<link>http://tools.ietf.org/html/</link>
<description></description>
<dc:date>2008-02-18T09:12:41Z</dc:date>
<dc:author>effraie</dc:author>
<dc:subject>specifications, rfc, web, standard, recherche, internet, html, geek, documentation, standards, documents, reference</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://tools.ietf.org/html/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://tools.ietf.org/html/">IETF Documents</a></h4>
 
by <a href="http://blogmarks.net/user/effraie">effraie</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/specifications">specifications</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rfc">rfc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standard">standard</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/recherche">recherche</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/internet">internet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geek">geek</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/documentation">documentation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/documents">documents</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reference">reference</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057749688">Copy</a> | 
<a href="http://blogmarks.net/link/2714022">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1057698553">
<title>Apache Abdera</title>
<link>http://incubator.apache.org/abdera/</link>
<description>The goal of the Apache Abdera project is to build a functionally-complete, high-performance implementation of the IETF Atom Syndication Format (RFC 4287) and Atom Publishing Protocol (RFC# Pending) specifications.</description>
<dc:date>2008-02-13T18:38:15Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>apache, atom, server</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://incubator.apache.org/abdera/"><img border="0" src="http://blogmarks.net/screenshots/2006/08/29/e3144266a95820e386e15099fbda0502.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://incubator.apache.org/abdera/">Apache Abdera</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1043563">1 other(s)</a> 
<p class="description">The goal of the Apache Abdera project is to build a functionally-complete, high-performance implementation of the IETF Atom Syndication Format (RFC 4287) and Atom Publishing Protocol (RFC# Pending) specifications.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057698553">Copy</a> | 
<a href="http://blogmarks.net/link/1043563">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057579240">
<title>Dare Obasanjo aka Carnage4Life - Google OpenSocial: Technical Overview and Critique</title>
<link>http://www.25hoursaday.com/weblog/2007/11/03/GoogleOpenSocialTechnicalOverviewAndCritique.aspx</link>
<description>&lt;blockquote&gt;&lt;p&gt;There are all sorts of forums for proposing and discussing open Web technologies including the IETF, W3C, OASIS and even ECMA. Until all of the underlying technologies in OpenSocial have been handed over to one or more of these standards bodies, this is a case of the proprietary pot calling the proprietary kettle black.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2007-11-27T00:13:40Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>standards, google, opacité</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.25hoursaday.com/weblog/2007/11/03/GoogleOpenSocialTechnicalOverviewAndCritique.aspx"><img border="0" src="http://blogmarks.net/screenshots/2007/11/27/88d60a83144f1d112f79618846bb1d6a.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.25hoursaday.com/weblog/2007/11/03/GoogleOpenSocialTechnicalOverviewAndCritique.aspx">Dare Obasanjo aka Carnage4Life - Google OpenSocial: Technical Overview and Critique</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2510850">1 other(s)</a> 
<div class="description"><blockquote><p>There are all sorts of forums for proposing and discussing open Web technologies including the IETF, W3C, OASIS and even ECMA. Until all of the underlying technologies in OpenSocial have been handed over to one or more of these standards bodies, this is a case of the proprietary pot calling the proprietary kettle black.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacit%25C3%25A9">opacité</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057579240">Copy</a> | 
<a href="http://blogmarks.net/link/2510850">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/keusta/mark/1057488099">
<title>RSS Tag Soup parser (name rss-tag-soup)</title>
<link>http://librdf.org/raptor/api/parser-rss-tag-soup.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;A parser for the multiple XML RSS formats. […] This includes support for the Atom 1.0 syndication format defined in IETF RFC 4287&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;One single way to grab differents RSS or Atom feed whitout worrying that much.&lt;/p&gt;</description>
<dc:date>2007-10-16T08:37:54Z</dc:date>
<dc:author>keusta</dc:author>
<dc:subject>rss, xml</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://librdf.org/raptor/api/parser-rss-tag-soup.html"><img border="0" src="http://blogmarks.net/screenshots/2007/10/16/9fcdea974e30c79c63e61782fa19b329.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://librdf.org/raptor/api/parser-rss-tag-soup.html">RSS Tag Soup parser (name rss-tag-soup)</a></h4>
 
by <a href="http://blogmarks.net/user/keusta">keusta</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2479969">1 other(s)</a> 
<div class="description"><blockquote><p>A parser for the multiple XML RSS formats. […] This includes support for the Atom 1.0 syndication format defined in IETF RFC 4287</p></blockquote>
<p>One single way to grab differents RSS or Atom feed whitout worrying that much.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rss">rss</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057488099">Copy</a> | 
<a href="http://blogmarks.net/link/2479969">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/greut/mark/1057487989">
<title>RSS Tag Soup parser (name rss-tag-soup)</title>
<link>http://librdf.org/raptor/api/parser-rss-tag-soup.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;A parser for the multiple XML RSS formats. […] This includes support for the Atom 1.0 syndication format defined in IETF RFC 4287&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;One single way to grab differents RSS or Atom feed whitout worrying that much.&lt;/p&gt;</description>
<dc:date>2007-10-16T07:15:26Z</dc:date>
<dc:author>greut</dc:author>
<dc:subject>xml, rss, atom, websemantic, raptor, rapper, librdf</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://librdf.org/raptor/api/parser-rss-tag-soup.html"><img border="0" src="http://blogmarks.net/screenshots/2007/10/16/9fcdea974e30c79c63e61782fa19b329.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://librdf.org/raptor/api/parser-rss-tag-soup.html">RSS Tag Soup parser (name rss-tag-soup)</a></h4>
 
by <a href="http://blogmarks.net/user/greut">greut</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2479969">1 other(s)</a> 
<div class="description"><blockquote><p>A parser for the multiple XML RSS formats. […] This includes support for the Atom 1.0 syndication format defined in IETF RFC 4287</p></blockquote>
<p>One single way to grab differents RSS or Atom feed whitout worrying that much.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rss">rss</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/websemantic">websemantic</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/raptor">raptor</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rapper">rapper</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/librdf">librdf</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057487989">Copy</a> | 
<a href="http://blogmarks.net/link/2479969">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/rodo/mark/1057449689">
<title>Setting Up An iSCSI Environment On Linux | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://howtoforge.com/iscsi_on_linux</link>
<description>Setting Up An iSCSI Environment On Linux

Nowadays, the iSCSI technology is quite popular in the storage world. This article shows an iSCSI demo environment which consists of one Debian Linux host and one Netapp Filer.We try to show the most important features of this protocol.

 
1. What is iSCSI?

It is a network storage protocol above TCP/IP. This protocol encapsulates SCSI data into TCP packets. iSCSI allows us to connect a host to a storage array via a simple Ethernet connection (tape drive). This solution is cheaper than the Fibre Channel SAN (Fibre channel HBAs and switches are expensive). From the host view the user sees the storage array LUNs like a local disks. iSCSI devices should not be confused with the NAS devices (for example NFS). The most important difference is that NFS volumes can be accessed by multiple hosts, but one iSCSI volume can by accessed by one host. It is similar to SCSIi protocol: usually only one host has access to one SCSI disk (the difference is the cluster enviroment). The iSCSI protocol is defined in the RFC3720 document by the IETF (Internet Engineering Task Force).</description>
<dc:date>2007-09-20T14:31:13Z</dc:date>
<dc:author>rodo</dc:author>
<dc:subject>storage, iscsi, cluster, debian, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://howtoforge.com/iscsi_on_linux"><img border="0" src="http://blogmarks.net/screenshots/2007/09/20/afa8c6d2e08052bb5ce3c8c0811e6a9b.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://howtoforge.com/iscsi_on_linux">Setting Up An iSCSI Environment On Linux | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/rodo">rodo</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2424468">1 other(s)</a> 
<p class="description">Setting Up An iSCSI Environment On Linux

Nowadays, the iSCSI technology is quite popular in the storage world. This article shows an iSCSI demo environment which consists of one Debian Linux host and one Netapp Filer.We try to show the most important features of this protocol.

 
1. What is iSCSI?

It is a network storage protocol above TCP/IP. This protocol encapsulates SCSI data into TCP packets. iSCSI allows us to connect a host to a storage array via a simple Ethernet connection (tape drive). This solution is cheaper than the Fibre Channel SAN (Fibre channel HBAs and switches are expensive). From the host view the user sees the storage array LUNs like a local disks. iSCSI devices should not be confused with the NAS devices (for example NFS). The most important difference is that NFS volumes can be accessed by multiple hosts, but one iSCSI volume can by accessed by one host. It is similar to SCSIi protocol: usually only one host has access to one SCSI disk (the difference is the cluster enviroment). The iSCSI protocol is defined in the RFC3720 document by the IETF (Internet Engineering Task Force).</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/storage">storage</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/iscsi">iscsi</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cluster">cluster</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057449689">Copy</a> | 
<a href="http://blogmarks.net/link/2424468">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/camel/mark/1057422964">
<title>Setting Up An iSCSI Environment On Linux | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://howtoforge.com/iscsi_on_linux</link>
<description>Setting Up An iSCSI Environment On Linux

Nowadays, the iSCSI technology is quite popular in the storage world. This article shows an iSCSI demo environment which consists of one Debian Linux host and one Netapp Filer.We try to show the most important features of this protocol.

 
1. What is iSCSI?

It is a network storage protocol above TCP/IP. This protocol encapsulates SCSI data into TCP packets. iSCSI allows us to connect a host to a storage array via a simple Ethernet connection (tape drive). This solution is cheaper than the Fibre Channel SAN (Fibre channel HBAs and switches are expensive). From the host view the user sees the storage array LUNs like a local disks. iSCSI devices should not be confused with the NAS devices (for example NFS). The most important difference is that NFS volumes can be accessed by multiple hosts, but one iSCSI volume can by accessed by one host. It is similar to SCSIi protocol: usually only one host has access to one SCSI disk (the difference is the cluster enviroment). The iSCSI protocol is defined in the RFC3720 document by the IETF (Internet Engineering Task Force).</description>
<dc:date>2007-08-30T16:56:42Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>linux, debian, environment, network, cluster, iscsi</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://howtoforge.com/iscsi_on_linux"><img border="0" src="http://blogmarks.net/screenshots/2007/09/20/afa8c6d2e08052bb5ce3c8c0811e6a9b.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://howtoforge.com/iscsi_on_linux">Setting Up An iSCSI Environment On Linux | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2424468">1 other(s)</a> 
<p class="description">Setting Up An iSCSI Environment On Linux

Nowadays, the iSCSI technology is quite popular in the storage world. This article shows an iSCSI demo environment which consists of one Debian Linux host and one Netapp Filer.We try to show the most important features of this protocol.

 
1. What is iSCSI?

It is a network storage protocol above TCP/IP. This protocol encapsulates SCSI data into TCP packets. iSCSI allows us to connect a host to a storage array via a simple Ethernet connection (tape drive). This solution is cheaper than the Fibre Channel SAN (Fibre channel HBAs and switches are expensive). From the host view the user sees the storage array LUNs like a local disks. iSCSI devices should not be confused with the NAS devices (for example NFS). The most important difference is that NFS volumes can be accessed by multiple hosts, but one iSCSI volume can by accessed by one host. It is similar to SCSIi protocol: usually only one host has access to one SCSI disk (the difference is the cluster enviroment). The iSCSI protocol is defined in the RFC3720 document by the IETF (Internet Engineering Task Force).</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/environment">environment</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/network">network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cluster">cluster</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/iscsi">iscsi</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057422964">Copy</a> | 
<a href="http://blogmarks.net/link/2424468">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/CharlesNepote/mark/1057339842">
<title>Enigform :: Firefox Add-ons</title>
<link>https://addons.mozilla.org/en-US/firefox/addon/4531</link>
<description>&quot;

Enhances HTTP security by adding GnuPG Digital Signatures to GET, POST and AJAX-generated POSTs to sites that request this level of security, or to all requests if told to do so.

Enigform is the Reference Implementation of the ideas and methods described in the soon-to-be (I hope!) IETF Draft &quot;OpenPGP based Identity and Data Authentication for HTTP&quot; by Arturo 'Buanzo' Busleiman. For more information, please visit http://enigform.mozdev.org..&quot;</description>
<dc:date>2007-07-12T09:37:04Z</dc:date>
<dc:author>CharlesNepote</dc:author>
<dc:subject>extension, standard, openpgp, pgp, firefox, sécurité, gpg, ietf, norme, web, identification</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://addons.mozilla.org/en-US/firefox/addon/4531"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://addons.mozilla.org/en-US/firefox/addon/4531">Enigform :: Firefox Add-ons</a></h4>
 
by <a href="http://blogmarks.net/user/CharlesNepote">CharlesNepote</a> 
<p class="description">"

Enhances HTTP security by adding GnuPG Digital Signatures to GET, POST and AJAX-generated POSTs to sites that request this level of security, or to all requests if told to do so.

Enigform is the Reference Implementation of the ideas and methods described in the soon-to-be (I hope!) IETF Draft "OpenPGP based Identity and Data Authentication for HTTP" by Arturo 'Buanzo' Busleiman. For more information, please visit http://enigform.mozdev.org.."</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/extension">extension</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standard">standard</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/openpgp">openpgp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pgp">pgp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/s%25C3%25A9curit%25C3%25A9">sécurité</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gpg">gpg</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ietf">ietf</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/norme">norme</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/identification">identification</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057339842">Copy</a> | 
<a href="http://blogmarks.net/link/2352827">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/benoit/mark/1057229142">
<title>draft-ietf-atompub-protocol-15.txt</title>
<link>http://www.ietf.org/internet-drafts/draft-ietf-atompub-protocol-15.txt</link>
<description></description>
<dc:date>2007-05-30T07:02:22Z</dc:date>
<dc:author>benoit</dc:author>
<dc:subject>draft, app</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ietf.org/internet-drafts/draft-ietf-atompub-protocol-15.txt"><img border="0" src="http://blogmarks.net/screenshots/2007/05/30/cd409833df361f74553ee81adc7318d8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ietf.org/internet-drafts/draft-ietf-atompub-protocol-15.txt">draft-ietf-atompub-protocol-15.txt</a></h4>
 
by <a href="http://blogmarks.net/user/benoit">benoit</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/draft">draft</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/app">app</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057229142">Copy</a> | 
<a href="http://blogmarks.net/link/2260372">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/omarvillota/mark/2506574">
<title>Internet Society</title>
<link>http://www.isoc.org/internet/history/brief.shtml</link>
<description>The Internet SOCiety (ISOC) is a professional membership society with more than 100 organization and over 20,000 individual members in over 180 countries. It provides leadership in addressing issues that confront the future of the Internet, and is the organization home for the groups responsible for Internet infrastructure standards, including the Internet Engineering Task Force (IETF) and the Internet Architecture Board (IAB)</description>
<dc:date>2007-04-10T16:14:06Z</dc:date>
<dc:author>omarvillota</dc:author>
<dc:subject>gobernanza web, repositorio web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.isoc.org/internet/history/brief.shtml"><img border="0" src="http://blogmarks.net/screenshots/2007/04/10/292de9c4851fc1c48623d5b0407ccbc4.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.isoc.org/internet/history/brief.shtml">Internet Society</a></h4>
 
by <a href="http://blogmarks.net/user/omarvillota">omarvillota</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/351395">1 other(s)</a> 
<p class="description">The Internet SOCiety (ISOC) is a professional membership society with more than 100 organization and over 20,000 individual members in over 180 countries. It provides leadership in addressing issues that confront the future of the Internet, and is the organization home for the groups responsible for Internet infrastructure standards, including the Internet Engineering Task Force (IETF) and the Internet Architecture Board (IAB)</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gobernanza%2Bweb">gobernanza web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/repositorio%2Bweb">repositorio web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2506574">Copy</a> | 
<a href="http://blogmarks.net/link/351395">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/omarvillota/mark/2506515">
<title>The Internet Engineering Task Force</title>
<link>http://www.ietf.org/</link>
<description>The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual</description>
<dc:date>2007-04-10T16:06:14Z</dc:date>
<dc:author>omarvillota</dc:author>
<dc:subject>gobernanza web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ietf.org/"><img border="0" src="http://blogmarks.net/screenshots/2007/04/10/22640918e183f42b4090397a70fd8786.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ietf.org/">The Internet Engineering Task Force</a></h4>
 
by <a href="http://blogmarks.net/user/omarvillota">omarvillota</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/200130">5 other(s)</a> 
<p class="description">The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gobernanza%2Bweb">gobernanza web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2506515">Copy</a> | 
<a href="http://blogmarks.net/link/200130">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/pyxosledisciple/mark/2054169">
<title>hcalendar-fr - Microformats</title>
<link>http://microformats.org/wiki/hcalendar-fr</link>
<description>hCalendar est un format simple, ouvert, distribué pour le calendrier et les événements, fondé sur le standard iCalendar (RFC2445 (http://www.ietf.org/rfc/rfc2445.txt)), adaptable pour l'embarquement dans (X)HTML, Atom, RSS et le XML arbitraire. hCalendar est l'un des nombreux standards ouverts microformat.</description>
<dc:date>2007-02-19T12:43:18Z</dc:date>
<dc:author>pyxosledisciple</dc:author>
<dc:subject>xml, standards, standard, calendrier, hcalendar, microformat</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://microformats.org/wiki/hcalendar-fr"><img border="0" src="http://blogmarks.net/screenshots/2007/02/19/b3d4c713ac0b9cc3d8fe16985f981f46.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://microformats.org/wiki/hcalendar-fr">hcalendar-fr - Microformats</a></h4>
 
by <a href="http://blogmarks.net/user/pyxosledisciple">pyxosledisciple</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1116349">2 other(s)</a> 
<p class="description">hCalendar est un format simple, ouvert, distribué pour le calendrier et les événements, fondé sur le standard iCalendar (RFC2445 (http://www.ietf.org/rfc/rfc2445.txt)), adaptable pour l'embarquement dans (X)HTML, Atom, RSS et le XML arbitraire. hCalendar est l'un des nombreux standards ouverts microformat.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standard">standard</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/calendrier">calendrier</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hcalendar">hcalendar</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformat">microformat</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2054169">Copy</a> | 
<a href="http://blogmarks.net/link/1116349">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>