RE: Replacing the Label header with a DAV:labeled-version report

"Clemm, Geoff" <[email protected]>
Newsgroups gmane.ietf.deltav
Message-ID <3906C56A7BD1F54593344C05BD1374B1078391BF@SUS-MA1IT01>
   From: Julian Reschke [mailto:[email protected]]

   > From: Clemm, Geoff [mailto:[email protected]]
   > So it looks like the main remaining issue in this thread is
   > 3.6_CLARIFY_DEPTH_MARSHALLING, i.e. whether to keep the marshalling
   > defined in 3253 (i.e. in a DAV:prop) or define a new element for it
   > (i.e. in a DAV:report).  My main concern with making a change is
   > that until we get RFC 3253 updated, any other spec that wants to
   > re-use the REPORT method from 3253 would have to know about the
   > proposed marshalling change, and specify it in their spec (e.g. the
   > ACL spec).  I'm concerned that this is likely to be a more
   > significant source of interoperability problems, than is having
   > DAV:prop be used both for properties and for reports.

   Well, it seems that I'm the only one who feels strongly about this --
   so probably RFC3253 should stay as it is (with clarifications, not
   changes).

OK, I'll mark it resolved, with that as the resolution.  The issue
will remain in the issues list though, so if anyone would like to
reopen it, just let me know.

Cheers,
Geoff
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.