Web Distributed Authoring and Versioning (WebDAV) SEARCH
RFC 5323

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

(Chris Newman) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) (was No Record, No Objection) No Objection

(Pasi Eronen) No Objection

(Russ Housley) No Objection

(Jon Peterson) No Objection

(Tim Polk) (was No Record, Discuss, No Objection) No Objection

(Dan Romascanu) No Objection

(Mark Townsley) No Objection

(David Ward) No Objection

Magnus Westerlund (was Discuss) No Objection

Comment (2008-09-10)
No email
send info
Section 3.2:

   DASLHeader = "DASL" ":" 1#Coded-URL
   Coded-URL  = <defined in Section 10.1 of [RFC4918]>

   (This grammar uses the augmented BNF format defined in Section 2.1 of
   [RFC2616])

I find it a bit confusing that one uses two different ABNFs in this document. I understand the issue with importing an element defined by RFC 2616 syntax and the difference in implicit LWS rules. However, I take the opportunity to point out that RFC 4918 has managed to use RFC 2616 ABNF which imports a RFC 2234 ABNF element. Which I thinks has some potential for confusion when moving this or the HTTP spec to new versions. 

The # operator is quite easy to explicitly define. 

   DASLHeader = "DASL" ":" *LWSP Coded-URL *(*LWSP "," *LWSP Coded-URL)
   Coded-URL  = "<" absolute-URI ">"
                       ; No linear whitespace (LWS) allowed in Coded-URL
                       ; absolute-URI defined in RFC 3986, Section 4.3
   LWSP       = <defined in RFC 5234>
   absolute-URI = <defined in RFC 3986>

So the above is the equivalent all in RFC 5234 ABNF with the possible question if it is allowed to have a LWSP element between "DASL" and ":".