Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

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.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on December 27, 2006.

Copyright Notice

Copyright © The Internet Society (2006).

Abstract

This is the media type specification for the playlist format XSPF ("spiff").

Table of Contents

1.  Requirements notation
2.  Registration
3.  Security considerations
4.  References
§  Author's Address
§  Intellectual Property and Copyright Statements

1. Requirements notation

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 [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

2. Registration

Type name:

application

Type name:

application

Subtype name:

xspf+xml

Required parameters:

none

Optional parameters:

charset. Same as charset parameter of application/xml as specified in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).

Encoding considerations:

Same as encoding considerations of application/xml as specified in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).

Interoperability considerations:

Versions 0 and 1 are compatible except for some playlist publication dates which precede the first publication of either specification.

Published specification:

http://xspf.org/xspf-v1 (version 1)

http://xspf.org/xspf-v0 (version 0)

Applications that use this media type:

Gnomoradio, Webjay.org, Musicplayer, Playr, Jinzora, Yahoo Music Engine, Serpentine, Plurn, ultraPh0nZ FMP256, Spiffy, Plext, BMPx, I/ON, Drupal playlist module, Wordpress playlist module, Ning, Music For Dozens, Musicmobs/Mobster, VLC media player, AmaroK, Pear::Package::File_XSPF, CPAN XML::XSPF, Odeo, Jamendo, ArtistServer, Project Opus, (others)

Additional information:

Magic number(s):

none, but see section 3.1 of [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).

File extension(s):

.xspf

Macintosh file type code(s):

"TEXT"

Fragment/anchor identifiers:

see [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).

Person & email address to contact for further information:

Lucas Gonze <lucas@gonze.com>

Intended usage:

COMMON

Restrictions on usage:

none

Author/change controller:

The XSPF specification is a work product of the Xiph.org Foundation's Playlist Ad Hoc Group. The working group's home on the web is http://xspf.org. The specifications were edited by Lucas Gonze <lucas@gonze.com>, Matthias Friedrich <matt@mafr.de>, and Robert Kaye <rob@eorbit.net>.

XML namespace:

http://xspf.org/ns/0

Base URIs:

see [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).

BOM:

see [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).

3. Security considerations

The XML-based media type being registered has all of the security considerations described in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.) plus additional considerations.

Playlist authors who publish documents containing local filesystem paths should take care to not reveal confidential information contained in those strings.

The registration does not employ active content.

4. References

Author's Address

Intellectual Property Statement

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

Disclaimer of Validity

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Copyright Statement

Copyright © The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

Acknowledgment

Funding for the RFC Editor function is currently provided by the Internet Society.