draft-ietf-webdav-bind-16.txt   draft-ietf-webdav-bind-17.txt 
Network Working Group G. Clemm Network Working Group G. Clemm
Internet-Draft IBM Internet-Draft IBM
Updates: J. Crawford Updates: J. Crawford
draft-ietf-webdav-rfc2518bis IBM Research draft-ietf-webdav-rfc2518bis IBM Research
(if approved) J. Reschke, Ed. (if approved) J. Reschke, Ed.
Intended status: Standards Track greenbytes Intended status: Standards Track greenbytes
Expires: July 9, 2007 J. Whitehead Expires: August 12, 2007 J. Whitehead
U.C. Santa Cruz U.C. Santa Cruz
January 5, 2007 February 8, 2007
Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)
draft-ietf-webdav-bind-16 draft-ietf-webdav-bind-17
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 39 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 9, 2007. This Internet-Draft will expire on August 12, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This specification defines bindings, and the BIND method for creating This specification defines bindings, and the BIND method for creating
multiple bindings to the same resource. Creating a new binding to a multiple bindings to the same resource. Creating a new binding to a
resource causes at least one new URI to be mapped to that resource. resource causes at least one new URI to be mapped to that resource.
skipping to change at page 3, line 42 skipping to change at page 3, line 42
B.5. Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 36 B.5. Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 36
B.6. Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 36 B.6. Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 36
B.7. Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 36 B.7. Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 36
B.8. Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 36 B.8. Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 36
B.9. Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 36 B.9. Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 36
B.10. Since draft-ietf-webdav-bind-11 . . . . . . . . . . . . . 37 B.10. Since draft-ietf-webdav-bind-11 . . . . . . . . . . . . . 37
B.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 37 B.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 37
B.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 37 B.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 37
B.13. Since draft-ietf-webdav-bind-14 . . . . . . . . . . . . . 37 B.13. Since draft-ietf-webdav-bind-14 . . . . . . . . . . . . . 37
B.14. Since draft-ietf-webdav-bind-15 . . . . . . . . . . . . . 38 B.14. Since draft-ietf-webdav-bind-15 . . . . . . . . . . . . . 38
B.15. Since draft-ietf-webdav-bind-16 . . . . . . . . . . . . . 38
Appendix C. Resolved issues (to be removed by RFC Editor Appendix C. Resolved issues (to be removed by RFC Editor
before publication) . . . . . . . . . . . . . . . . . 38 before publication) . . . . . . . . . . . . . . . . . 38
C.1. rfc2518bis-lock-root . . . . . . . . . . . . . . . . . . . 38 C.1. iana-vs-http-status . . . . . . . . . . . . . . . . . . . 38
Appendix D. Open issues (to be removed by RFC Editor prior to Appendix D. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 38 publication) . . . . . . . . . . . . . . . . . . . . 38
D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40
Intellectual Property and Copyright Statements . . . . . . . . . . 42 Intellectual Property and Copyright Statements . . . . . . . . . . 42
1. Introduction 1. Introduction
This specification extends the WebDAV Distributed Authoring Protocol This specification extends the WebDAV Distributed Authoring Protocol
skipping to change at page 33, line 28 skipping to change at page 33, line 28
hostile attempts to make it devote resources to adding bindings to hostile attempts to make it devote resources to adding bindings to
the list. the list.
11. Internationalization Considerations 11. Internationalization Considerations
All internationalization considerations mentioned in All internationalization considerations mentioned in
[draft-ietf-webdav-rfc2518bis] also apply to this document. [draft-ietf-webdav-rfc2518bis] also apply to this document.
12. IANA Considerations 12. IANA Considerations
There are no IANA considerations related to this specification. Section 7 defines the HTTP status codes 208 (Already Reported) and
506 (Loop Detected), to be added to the registry at
<http://www.iana.org/assignments/http-status-codes>.
13. Acknowledgements 13. Acknowledgements
This document is the collaborative product of the authors and Tyson This document is the collaborative product of the authors and Tyson
Chihaya, Jim Davis, Chuck Fay and Judith Slein. This draft has Chihaya, Jim Davis, Chuck Fay and Judith Slein. This draft has
benefited from thoughtful discussion by Jim Amsden, Peter Carlson, benefited from thoughtful discussion by Jim Amsden, Peter Carlson,
Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun,
Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa
Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe
Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris
skipping to change at page 38, line 13 skipping to change at page 38, line 13
Identify Julian Reschke as Editor. Identify Julian Reschke as Editor.
B.14. Since draft-ietf-webdav-bind-15 B.14. Since draft-ietf-webdav-bind-15
Fix typo in RFC2119 keywords section (sorry!). Fix typo in RFC2119 keywords section (sorry!).
Update [draft-ietf-webdav-rfc2518-bis] to draft 17. Update [draft-ietf-webdav-rfc2518-bis] to draft 17.
Add and resolve issue "rfc2518bis-lock-root". Add and resolve issue "rfc2518bis-lock-root".
B.15. Since draft-ietf-webdav-bind-16
Add and resolve issue "iana-vs-http-status".
Appendix C. Resolved issues (to be removed by RFC Editor before Appendix C. Resolved issues (to be removed by RFC Editor before
publication) publication)
Issues that were either rejected or resolved in this version of this Issues that were either rejected or resolved in this version of this
document. document.
C.1. rfc2518bis-lock-root C.1. iana-vs-http-status
Type: change Type: change
julian.reschke@greenbytes.de (2007-01-04): <http://ietf.osafoundation.org:8080/bugzilla/show_bug.cgi?id=266>
draft-ietf-webdav-rfc2518bis-17 uses the term "lock root"
inconsistently. Add an appendix explaining the problem and
suggesting a clarification.
Resolution (2007-01-04): Add appendix explaining the issue and julian.reschke@greenbytes.de (2007-02-08): Need to register new HTTP
recommending a fix to rfc2518bis. status codes according to RFC2817 and
<http://www.iana.org/assignments/http-status-codes>).
Resolution (2007-02-07): Done.
Appendix D. Open issues (to be removed by RFC Editor prior to Appendix D. Open issues (to be removed by RFC Editor prior to
publication) publication)
D.1. edit D.1. edit
Type: edit Type: edit
julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for
editorial fixes/enhancements. editorial fixes/enhancements.
skipping to change at page 42, line 15 skipping to change at page 42, line 15
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST, OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 42, line 48 skipping to change at page 42, line 47
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 13 change blocks. 
19 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/