Document: draft-ietf-webdav-bind-23 Reviewer: Pete McCann Review Date: 29 May 2009 IETF LC End Date: 28 May 2009 IESG Telechat date: 04 June 2009 Summary: Ready for publication as Experimental. I had a few minor questions that might just be a result of my own lack of understanding. Major issues: Minor issues: Section 2.3: If because of multiple bindings to a resource, more than one source resource updates a single destination resource, the order of the updates is server defined. Are you trying to say that a Request-URI can map to more than one resource? I didn't think this was possible. If a COPY request would cause a new resource to be created as a copy of an existing resource, and that COPY request has already created a copy of that existing resource, the COPY request instead creates another binding to the previous copy, instead of creating a new resource. This confused me a bit, but after reading the examples in the next section I think I understand what is intended here: do you mean that if the resource graph pointed at by the Request-URI itself has multiple bindings to the same resouce, that resource is only copied once by the COPY operation? Nits/editorial comments: Abstract: s/insure/ensure/