Subject: Re: Importing kqueue's from FreeBSD...
To: Luke Mewburn <email@example.com>
From: Jason R Thorpe <firstname.lastname@example.org>
Date: 03/20/2001 09:53:47
On Tue, Mar 20, 2001 at 08:58:02AM +1100, Luke Mewburn wrote:
> type = kqueue_filtertype("read");
> I think this solve's eeh's (and thorpej's) concerns about allowing
> arbitrary filters to be defined, without requiring strings to be used
> at all times. There's still a potential for namespace clash (if two
> third party lkm vendors choose the same string), but it's far less
> likely than two vendors choosing the same int.
No, this is a fine solution, and there is a way to deal with the
Here is a quote from draft-ietf-secsh-architecture-08.txt:
o Names that do not contain an at-sign (@) are reserved to be assigned
by IETF consensus (RFCs). Examples include `3des-cbc', `sha-1',
`hmac-sha1', and `zlib' (the quotes are not part of the name). Names
of this format MUST NOT be used without first registering them.
Registered names MUST NOT contain an at-sign (@) or a comma (,).
o Anyone can define additional algorithms by using names in the format
name@domainname, e.g. "email@example.com". The format of the part
preceding the at sign is not specified; it MUST consist of US-ASCII
characters except at-sign and comma. The part following the at-sign
MUST be a valid fully qualified internet domain name [RFC-1034]
controlled by the person or organization defining the name. It is up
to each domain how it manages its local namespace.
-- Jason R. Thorpe <firstname.lastname@example.org>