<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: ietf</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/ietf.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-11-20T18:55:21+00:00</updated><author><name>Simon Willison</name></author><entry><title>OAuth in Minneapolis</title><link href="https://simonwillison.net/2008/Nov/20/mnotus/#atom-tag" rel="alternate"/><published>2008-11-20T18:55:21+00:00</published><updated>2008-11-20T18:55:21+00:00</updated><id>https://simonwillison.net/2008/Nov/20/mnotus/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.mnot.net/blog/2008/11/21/oauth"&gt;OAuth in Minneapolis&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
OAuth looks like it’s on track for an IETF Working Group.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ietf"&gt;ietf&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mark-nottingham"&gt;mark-nottingham&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/standards"&gt;standards&lt;/a&gt;&lt;/p&gt;



</summary><category term="ietf"/><category term="mark-nottingham"/><category term="oauth"/><category term="standards"/></entry><entry><title>First Notes on Django</title><link href="https://simonwillison.net/2007/Dec/3/educated/#atom-tag" rel="alternate"/><published>2007-12-03T11:38:52+00:00</published><updated>2007-12-03T11:38:52+00:00</updated><id>https://simonwillison.net/2007/Dec/3/educated/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.educatedguesswork.org/movabletype/archives/2007/12/first_notes_on.html"&gt;First Notes on Django&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Cool, the IETF are developing internal tools with Django.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ietf"&gt;ietf&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;&lt;/p&gt;



</summary><category term="django"/><category term="ietf"/><category term="python"/></entry><entry><title>Quoting James Snell</title><link href="https://simonwillison.net/2007/Nov/18/snellspace/#atom-tag" rel="alternate"/><published>2007-11-18T00:15:22+00:00</published><updated>2007-11-18T00:15:22+00:00</updated><id>https://simonwillison.net/2007/Nov/18/snellspace/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://snellspace.com/wp/?p=803"&gt;&lt;p&gt;I think it is well established that HTTP Authentication needs a major kick in the ass and OpenID and OAuth may get us most of the way there.  However, until I see RFC#s attached to both I'm hardly going to consider them to be complete. I propose the creation of an IETF WG on Identity and Authentication. The WG would be chartered to produce two RFCs covering each of the two areas. OpenID and OAuth could be used to seed the WG effort.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://snellspace.com/wp/?p=803"&gt;James Snell&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/http"&gt;http&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ietf"&gt;ietf&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/james-snell"&gt;james-snell&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rfc"&gt;rfc&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/standardisation"&gt;standardisation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/standards"&gt;standards&lt;/a&gt;&lt;/p&gt;



</summary><category term="http"/><category term="ietf"/><category term="james-snell"/><category term="oauth"/><category term="openid"/><category term="rfc"/><category term="standardisation"/><category term="standards"/></entry><entry><title>Proposed RFC for application/json</title><link href="https://simonwillison.net/2006/Aug/1/proposed/#atom-tag" rel="alternate"/><published>2006-08-01T21:29:17+00:00</published><updated>2006-08-01T21:29:17+00:00</updated><id>https://simonwillison.net/2006/Aug/1/proposed/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.ietf.org/rfc/rfc4627.txt?number=4627"&gt;Proposed RFC for application/json&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Douglas Crockford is putting JSON through the IETF.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.davidflanagan.com/blog/2006_08.html"&gt;davidflanagan.com&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/douglas-crockford"&gt;douglas-crockford&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ietf"&gt;ietf&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/json"&gt;json&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rfc"&gt;rfc&lt;/a&gt;&lt;/p&gt;



</summary><category term="douglas-crockford"/><category term="ietf"/><category term="json"/><category term="rfc"/></entry></feed>