|
|||||||||||
|
Re: linux-ipsec: syntax conventions, part 1
From: Hugh Redelmeier <hugh(at)trends.net>
Date: Fri Mar 20 1998 - 23:32:26 EST
| Flags fields with more than one bit set are written with the flag names
Comma "feels" not quite right to me. If it were using set notation
{cat, dog}
| White space after commas is ignored on input;
Since this syntax is meant for shell-parsed command arguments and for files, spaces are funny things. I'd like to see some example uses. It seems to me that a sequence of tokens is naturally a tupple. Some form of delimiter might be required, but I don't know the syntactic context you imagine for these. "*" is easier to see than "any". Perhaps it should be allowed as a synonym. | The IPSEC drafts use "opaque" in some places to refer to values that are
Let's change the drafts :-)
| From: John Gilmore <gnu@toad.com>
| And in particular, the conventions we use should match traditional
Remember that an important use will be in non-script files. The - --keyword notation isn't pretty in that context. | > Codes (enumerations selecting, e.g., encryption algorithms) and flags
Matching the names in the standards would seem best.
| From: Todd Graham Lewis <tlewis@mindspring.net>
| The only thing which full, dotted-quad syntax for
I suspect that this is mandated.
Hugh Redelmeier
-----BEGIN PGP SIGNATURE-----
iQCVAwUBNRNCrMFAuQPManGZAQHXygQAv1cm16F4ChwaL14ULz/MFUXa0ZCAwfFy
htZVWYIygyhcx7V51rFWQ7qhvZnPipHghc0dgVoGDEwKv7S0VYZopbBXn7whhP1z
wqWDmIUE4XeeWwCxt3ZRvMZuaLgtvRbZci0eJcaT2bpW9xPiAHacNKa4HpEghPvL
c3sOuQHq2/U=
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 12:59:28 EDT |
||||||||||
|
|||||||||||