[Date Prev][Date Next]
On May 1, 2010, at 12:31 PM, email@example.com wrote:
> just some changes and cleanups according the still ongoing discussion =
I recommend consideration of this patch be deferred until the =
specification is less of a work-in-a-progress.
> The patch can be downloaded here:=20
> - removed extensible matching rules strictly associated with=20
> dedicated syntaxes
> - added two universal matching rules instead:
> - nowMach (equality matching rule)
> - nowOrdering (ordering matching rule)
> - these two rules also support extensible match filters
Your comments imply these rules could be used as attribute type equality =
and ordering rules. I don't believe the met the requirements (see =
X.501) to be used in that manner. That is, they only make sense as =
extensible matching rules.
> To publish a correct server current time time-stamp value within =
> - apply the bugfix from ITS#6541
> - and use -DCTM_G_DIFFERENTIAL_SERVERTIME
#ifdef's should, IMO, be generally avoided.
> To extend generalizedTime attribute types to also support "NOW" as=20
> assertion value:
> - use -DCTM_RFC4517_MR_AV_SYNTAX_VIOLATION
The generalized time syntax is not ours to alter. Introduction of such =
a change would, it seem, lead to interoperability problems.
> Beware of patching conflicts in schema_init.c:
> This patch contains small redundant parts from my parallel =
> in ITS#6532