Network Working Group W. Norris
Internet-Draft April 6, 2011
Updates: 4287 (if approved)
Intended status: Informational
Expires: October 8, 2011
The Atom Audience Extension
draft-norris-atompub-audience-01.txt
Abstract
TBD
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 8, 2011.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Norris Expires October 8, 2011 [Page 1]
Internet-Draft Atom audience April 2011
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3
3. The 'atom:to' element . . . . . . . . . . . . . . . . . . . . . 3
4. The 'atom:cc' element . . . . . . . . . . . . . . . . . . . . . 4
5. The 'atom:bcc' element . . . . . . . . . . . . . . . . . . . . 5
6. IRI's and the 'xml:base' Attribute . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
10. Normative References . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Norris Expires October 8, 2011 [Page 2]
Internet-Draft Atom audience April 2011
1. Introduction
TBD
2. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, [RFC2119]
This specification uses XML Namespaces [W3C.REC-xml-names-19990114]
to uniquely identify XML element names. It uses the following
namespace prefix for the indicated namespace URI;
"atom": "http://www.w3.org/2005/Atom"
3. The 'atom:to' element
The atom:to element MAY be used as the child of an atom:entry element
to identify an intended redistribution target for the atom:entry.
The value of the atom:to element MUST be an IRI. Processors that are
redistributing copies of an atom:entry, SHOULD NOT remove any
contained atom:to elements from the redistributed copy.
to = element atom:to {
atomCommonAttributes,
(atomUri | "*")
}
An atom:entry element MAY contain any number of atom:to elements, but
MUST NOT contain more than one with the same IRI value as sibling
atom:to, atom:cc and atom:bcc elements.
The value "*" MAY be used to indicate that the entry is intended to
be redistributed to everyone.
Processors that encounter IRI values in atom:to elements that cannot
be resolved to a entity to which the atom:entry can be redistributed
MUST NOT stop processing the entry. However, such processors MAY
signal an error or a warning to the client indicating that the IRI is
being ignored.
Norris Expires October 8, 2011 [Page 3]
Internet-Draft Atom audience April 2011
...
...
*
acct:john.doe@example.org
acct:jane.doe@example.org
...
...
4. The 'atom:cc' element
The atom:cc element MAY be used as the child of an atom:entry element
to identify an intended redistribution target for the atom:entry.
The value of the atom:cc element MUST be an IRI. Processors that are
redistributing copies of an atom:entry, SHOULD NOT remove any
contained atom:cc elements from the redistributed copy.
cc = element atom:cc {
atomCommonAttributes,
(atomUri | "*")
}
An atom:entry element MAY contain any number of atom:cc elements, but
MUST NOT contain more than one with the same IRI value as sibling
atom:to, atom:cc and atom:bcc elements.
The value "*" MAY be used to indicate that the entry is intended to
be redistributed to everyone.
Processors that encounter IRI values in atom:cc elements that cannot
be resolved to a entity to which the atom:entry can be redistributed
MUST NOT stop processing the entry. However, such processors MAY
signal an error or a warning to the client indicating that the IRI is
being ignored.
Norris Expires October 8, 2011 [Page 4]
Internet-Draft Atom audience April 2011
...
...
*
acct:john.doe@example.org
acct:jane.doe@example.org
...
...
5. The 'atom:bcc' element
The atom:bcc element MAY be used as the child of an atom:entry
element to identify an intended redistribution target for the atom:
entry. The value of the atom:to element MUST be an IRI. Processors
that are redistributing copies of an atom:entry, MUST remove all
contained atom:bcc elements from the redistributed copy. When
redistributing an atom:entry containing atom:bcc elements, the
processor MAY include an empty atom:bcc element within the
redistributed copy as an indication to recipients that copies have
been sent to an undisclosed set of recipients.
bcc = element atom:bcc {
atomCommonAttributes,
(atomUri)
}
An atom:entry element MAY contain any number of atom:bcc elements,
but MUST NOT contain more than one with the same IRI value as sibling
atom:to, atom:cc or atom:bcc elements.
Processors MUST ignore atom:bcc elements that use the reserved "*"
value.
Processors that encounter IRI values in atom:bcc elements that cannot
be resolved to a entity to which the atom:entry can be redistributed
MUST NOT stop processing the entry. However, such processors MAY
signal an error or a warning to the client indicating that the IRI is
being ignored.
Norris Expires October 8, 2011 [Page 5]
Internet-Draft Atom audience April 2011
...
...
acct:john.doe@example.org
acct:jane.doe@example.org
...
...
6. IRI's and the 'xml:base' Attribute
The atom:to and atom:bcc elements use IRIs [RFC3987]. Every URI
[RFC3986] is also an IRI, so a URI may be used as the value of these
elements. When an IRI that is not also a URI is given for
dereferencing, it MUST be mapped to a URI using the steps in Section
3.1 of [RFC3987].
The atom:to and atom:bcc elements MAY have an xml:base attribute
[W3C.REC-xmlbase-20010627]. When xml:base is used, it serves the
function described in section 5.1.1 of [RFC3986], establishing the
base URI (or IRI) for resolving any relative references found within
the effective scope of the xml:base attribute.
7. Security Considerations
TBD
8. IANA Considerations
TBD
9. Acknowledgements
The author gratefully acknowledges the feedback from the members of
the Atom Publishing Format and Protocol working group during the
development of this specification.
10. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Norris Expires October 8, 2011 [Page 6]
Internet-Draft Atom audience April 2011
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001.
[RFC3548] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 3548, July 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", RFC 3987, January 2005.
[RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
Syndication Format", RFC 4287, December 2005.
[W3C.REC-xml-20040204]
Yergeau, F., Maler, E., Sperberg-McQueen, C., Paoli, J.,
and T. Bray, "Extensible Markup Language (XML) 1.0 (Third
Edition)", World Wide Web Consortium FirstEdition REC-xml-
20040204, February 2004,
.
[W3C.REC-xml-names-19990114]
Hollander, D., Layman, A., and T. Bray, "Namespaces in
XML", World Wide Web Consortium FirstEdition REC-xml-
names-19990114, January 1999,
.
[W3C.REC-xmlbase-20010627]
Marsh, J., "XML Base", World Wide Web Consortium
FirstEdition REC-xmlbase-20010627, June 2001,
.
Author's Address
Will Norris
Phone:
Email: willnorris@google.com
URI: http://google.com
Norris Expires October 8, 2011 [Page 7]