From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: POM Xtables???
Date: Tue, 01 Jul 2008 09:27:38 -0500 [thread overview]
Message-ID: <486A3EDA.8030804@riverviewtech.net> (raw)
In-Reply-To: <486A3AD6.7040905@trash.net>
On 07/01/08 09:10, Patrick McHardy wrote:
> In any case, its unreasonable to expect us to never *extend* (not
> change) the output to accomodate buggy parsers. This is by the way
> the same way that is often used to extend binary structures, even
> though someone stupid might use exact size checks.
*nod*
Agreed.
However as I sit here and think about it, it may be worth adding a new
field *as early as possible* (read closes to the start of line) in the
field list that indicates a version, which can be used to determine the
fields and their position there in. This would make it very easy for
people to write strict parsers down the road. A simple three character
hex field (4 bytes including the leading space) would allow for 4k of
strict layouts. (Even more 0-9 and a-z or additionally A-Z.) Just a
thought.
Grant. . . .
next prev parent reply other threads:[~2008-07-01 14:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 17:54 POM Xtables??? Dave
2008-06-27 18:58 ` Jan Engelhardt
2008-06-27 20:08 ` Dave
2008-06-27 21:16 ` Jan Engelhardt
2008-06-29 2:20 ` Grant Taylor
2008-06-30 16:04 ` Dave
2008-06-30 16:20 ` Patrick McHardy
2008-06-30 20:46 ` Jan Engelhardt
2008-06-30 20:52 ` Patrick McHardy
2008-07-01 9:43 ` Jozsef Kadlecsik
2008-07-01 9:46 ` Patrick McHardy
2008-07-01 11:38 ` Jan Engelhardt
2008-07-01 11:43 ` Patrick McHardy
2008-07-01 11:50 ` Jan Engelhardt
2008-07-01 11:57 ` Patrick McHardy
2008-07-01 14:05 ` Grant Taylor
2008-07-01 14:10 ` Patrick McHardy
2008-07-01 14:27 ` Grant Taylor [this message]
2008-07-01 14:34 ` Patrick McHardy
2008-07-01 14:30 ` Jan Engelhardt
2008-07-23 20:19 ` Jan Engelhardt
2008-07-23 23:21 ` Patrick McHardy
2008-07-24 8:31 ` James King
2008-07-24 9:21 ` Pablo Neira Ayuso
2008-07-24 9:43 ` Patrick McHardy
2008-08-15 8:17 ` James King
2008-08-19 11:35 ` Brent Clark
2008-08-15 8:48 ` James King
2008-06-30 21:11 ` Jozsef Kadlecsik
2008-06-30 21:47 ` Jan Engelhardt
2008-07-01 10:00 ` Jozsef Kadlecsik
2008-07-01 11:19 ` Jan Engelhardt
2008-06-30 20:18 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486A3EDA.8030804@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.