Subject: Fwd: RFC 5005 on Feed Paging and Archiving

From: Mark Nottingham <[email-masked]>
Date: Sat, 8 Sep 2007 10:51:36 +1000

FYI. Thanks again to everyone who reviewed, suggested, helped and  
gave feedback.

Begin forwarded message:

> From: [email-masked]
> Date: 8 September 2007 10:41:00 AM
> To: [email-masked], [email-masked]
> Cc: [email-masked]
> Subject: RFC 5005 on Feed Paging and Archiving
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 5005
>
>         Title:      Feed Paging and Archiving
>         Author:     M. Nottingham
>         Status:     Standards Track
>         Date:       September 2007
>         Mailbox:    [email-masked]
>         Pages:      15
>         Characters: 28937
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-nottingham-atompub-feed-history-11.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc5005.txt
>
> This specification defines three types of syndicated Web feeds that
> enable publication of entries across one or more feed documents.
> This includes "paged" feeds for piecemeal access, "archived" feeds
> that allow reconstruction of the feed's contents, and feeds that are
> explicitly "complete".  [STANDARDS TRACK]
>
> This is now a Proposed Standard Protocol.
>
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and  
> suggestions
> for improvements.Please refer to the current edition of the Internet
>  Official Protocol Standards (STD 1) for the standardization state and
>  status of this protocol.  Distribution of this memo is unlimited.
>
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to [email-masked].  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to [email-masked].
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to [email-masked] with the message body
>
> help: ways_to_get_rfcs. For example:
>
>         To: [email-masked]
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [email-masked].   
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> [email-masked].  Please consult RFC 2223, Instructions  
> to RFC
> Authors, for further information.
>
>
> The RFC Editor Team
> USC/Information Sciences Institute
>
> ...
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/ietf-announce

--
Mark Nottingham     http://www.mnot.net/