|
The only thing I can think of that
might be different is that a naive
implementation
might parse a Terminate message on the assumption that it
is validly formatted.
It is concievable that certain implementations might be
vulnerable to specific
incorrect formattings causing internal buffer
overflows/etc. It sounds crazy,
but look at some of the web/email related attacks that have
been diagnosed.
But even that isn't a *new* attack, since deliberate
mal-formatting of headers
is a known attack, and the mitigation strategy is already
known (don't make
assumptions about anything that shows up on a
wire).
So I'd agree that an extra example might be nice, but there
are always things
that would be "nice" to add to a draft. If you keep
adding them forever then
it stays a draft forever. I'd rather have an RFC that was
missing some examples.
-- |
_______________________________________________ rddp mailing list rddp at ietf.org https://www1.ietf.org/mailman/listinfo/rddp