Protocol Action: 'The Atom Syndication Format' to Proposed Standard

The IESG <> Wed, 17 August 2005 17:14 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1E5RV2-0000AV-HD; Wed, 17 Aug 2005 13:14:48 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1E5RUz-000087-H5; Wed, 17 Aug 2005 13:14:46 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id NAA12246; Wed, 17 Aug 2005 13:14:42 -0400 (EDT)
Received: from [] ( by with esmtp (Exim 4.43) id 1E5S4Z-0005ks-Ti; Wed, 17 Aug 2005 13:51:32 -0400
Received: from apache by with local (Exim 4.43) id 1E5RUy-0001WJ-57; Wed, 17 Aug 2005 13:14:44 -0400
X-test-idtracker: no
From: The IESG <>
To: IETF-Announce <>
Message-Id: <>
Date: Wed, 17 Aug 2005 13:14:44 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: atompub mailing list <>, Internet Architecture Board <>, atompub chair <>, atompub chair <>, RFC Editor <>
Subject: Protocol Action: 'The Atom Syndication Format' to Proposed Standard
X-Mailman-Version: 2.1.5
Precedence: list
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

The IESG has approved the following document:

- 'The Atom Syndication Format '
   <draft-ietf-atompub-format-11.txt> as a Proposed Standard

This document is the product of the Atom Publishing Format and Protocol 
Working Group. 

The IESG contact persons are Scott Hollenbeck and Ted Hardie.

A URL of this Internet-Draft is:

Technical Summary:

This document describes the Atom format for syndication. It is 
XML-based and is considered to be the successor to the earlier RSS 
formats. Its primary use is for web-based content, but is expected to 
be used for non-web content as well, such as personal news feeds.

Working Group Summary:

Some members of the working group remain unenthusiastic about some
sections of the document, but the chairs strongly believe that there
is rough (or better) consensus in support of the document as a whole.
For some of the parts with the most contention, there cannot be more
than very rough consensus due to basic differences in the way people
would design parts of the format, particularly given that we have many
models in existence with the different flavors of RSS. For some parts
of the document, there is contention about whether or not a
particular item should or should not be in the Atom core versus being
an extension. For some parts, there is contention whether there
should be MUST/SHOULD/MAY leeway for content creators in the presence
or absence of an element, or the semantic content of an element; the
group really pushed RFC 2119 around during the past few months.
Protocol Quality
Scott Hollenbeck and the XML Directorate have reviewed the specification
for the IESG.  Test implementations have confirmed basic protocol

IETF-Announce mailing list