Note: a later version of this document has been published as RFC 5791.
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), 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”.¶
This Internet-Draft will expire in August 2010.¶
Copyright (c) 2010 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 BSD License.¶
Distribution of this document is unlimited.
Please send feedback to either the DC-Architecture mailing list (<http://www.jiscmail.ac.uk/lists/dc-architecture.html>) or the IETF Apps Area mailing list (<https://www.ietf.org/mailman/listinfo/apps-discuss>).
XML versions and latest edits for this document are available from <http://greenbytes.de/tech/webdav/#draft-reschke-rfc2731bis>.
|I auth48 (type: edit, status: closed)|
|email@example.com||2010-02-19||Umbrella issue for changes made during the RFC Editor's AUTH48 period.|
|Associated changes in this document: <#rfc.change.auth48.1>, <#rfc.change.auth48.2>, <#rfc.change.auth48.3>, <#rfc.change.auth48.4>, 1, <#rfc.change.auth48.6>, <#rfc.change.auth48.7>, del-6.|
This document is of administrative nature only and therefore there are no security relations related to it.¶
There are no IANA considerations related to this document.
This proposal has been discussed and approved on the DC-ARCHITECTURE mailing list (<DC-ARCHITECTURE@JISCMAIL.AC.UK>, <https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=DC-ARCHITECTURE;XwVOng;20090818152516%2B0200>).
Added John Kunze as Co-Author. Expand Security Considerations to say why there aren't any. Include title of RFC 2731 into this document's title. Mention that Dublin Core has maintained its version of the spec for the last decade. Add open issue "historic", which is waiting for community feedback.
Close issue "historic".
Add and resolve issues "ref2731norm" and "dcrefnorm".