On Tue, 2005-08-09 at 22:58 -0600, The Purple Streak, Hilarie Orman
wrote:
http://www.purplestreak.com/ietf-opes/draft-ietf-opes-rules-language-hopalong-00.txt
1. Applicable to partial messages (packet-by-packet)
I would remove the references to "packets" from the draft. None of the
protocols we think of dealing with (HTTP, OCP, SMTP, IMAP, RTSP) have a
notion of a packet.
Support for partial messages or, more precisely, partial message
payloads (potentially large bodies and such) is a must, of course.
Beyond that, incomplete "parts" should be invisible to the rules
language. The language does not need to deal with a truncated HTTP
header field or a partially received IPv6 address, for example.
If the protocol defines an "element" or "part", the rules should be able
to access that part (usually via protocol-specific modules). Splitting
e;ementary parts into smaller chunks should be out of scope.
Note that if your description promises support for application protocol
elements (headers, bodies, etc.) than it would be possible to support
packets as well, but only for protocols that deal with packets...
Another unrelated comment is that we should not assume that a message is
always headers+body. Even HTTP messages are not like that because they
may have trailers. I think a couple of places in the draft may imply
otherwise.
If there is an error but there are no matching onError rules, what
happens?
Is there arithmetic support? For example, can I count the number of
certain headers in the message?
Please add at least one non-trivial/semi-complete realistic example.
Thank you,
Alex.