Skip to main content

Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)
draft-ietf-webdav-bind-27

Yes

(Alexey Melnikov)

No Objection

(Dan Romascanu)
(Jari Arkko)
(Lars Eggert)
(Pasi Eronen)
(Ron Bonica)
(Ross Callon)
(Russ Housley)

Abstain

(Lisa Dusseault)

Note: This ballot was opened for revision 27 and is now closed.

Alexey Melnikov Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
(was Discuss, No Objection, Discuss) No Objection
No Objection (2009-08-13) Unknown
Comment fixed
Teenie nit...
Section 14
    and other members of the WebDAV working group.
But there is no WG.
Say...
    and other subscribers to the WebDAV mailing list.
Cullen Jennings Former IESG member
(was Discuss) No Objection
No Objection (2009-06-04) Unknown
The WG LC was not correct in that it was done as a LC for a WG doc not an individual doc.
Dan Romascanu Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
No Objection
No Objection () Unknown

                            
Pasi Eronen Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection (2009-06-03) Unknown
Comment has been resolved...

-----
I don't understand the example in section 2.3.2.  How would the COPY operation update any bindings and affect the contents of R3?  If I understand the semantics as described in section 9.8.4 of RFC 4918, the result of the copy would result in deletion of the bindings in C2 to Resource C3, the deletion of C2, creation of a new C1 in CollY containing bindings x.gif and y.gif to new resources R1' and R2'.
Robert Sparks Former IESG member
(was Discuss) No Objection
No Objection (2009-06-03) Unknown
The document provides some discussion of the ramifications of simple loops, but its not immediately obvious that the recommendations for handling them are sufficient for dealing with more complex loops. Are there additional issues introduced when each added level of depth adds an exponentially growing number of elements? 

(view in fixed width)
        +---------+
        | root    |
        |         |
        |  start  |
        +---------+ 
             |
             v
        +---------+          +---------+ 
  +---->| C1      |          | C2      |<---+
  |  +->|         |          |         |<-+ |
  |  |  | a    b  |          | a    b  |  | |
  |  |  +---------+          +---------+  | |
  |  |    |    |               |    |     | |
  |  |    |    |          +----+    |     | |
  |  |    |    |          |         |     | |
  |  |    |    +----------c---+     |     | |
  |  |    |               |   |     |     | |
  |  |    |    +----------+   |     |     | |
  |  |    v    v              v     v     | |
  |  |  +---------+          +---------+  | |
  |  |  | C3      |          | C4      |  | |
  |  |  |         |          |         |  | |
  |  |  | a    b  |          | a    b  |  | |
  |  |  +---------+          +---------+  | |
  |  |    |    |               |    |     | |
  |  +----+    |          +----+    +-----+ |
  |            |          |                 |
  |            +----------c-----------------+
  |                       |
  +-----------------------+
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection () Unknown

                            
Tim Polk Former IESG member
No Objection
No Objection (2009-06-04) Unknown
The Security Considerations section has a textual reference to the considerations for
HTTP/1.1 and WebDAV, but does not indicate which RFCs contain those considerations.
It would be helpful to readers if there were explicit references added for 2616, 3744 
and 4918 at that point in the text.
Lisa Dusseault Former IESG member
Abstain
Abstain () Unknown