[Date Prev][Date Next]
ok, i learned from Kurt and Tony, that the matching rules of CN provide no
chance for significant leading space. so far, so good.
I have no access to X.500 or X.501.
how would You choose an attribute key (within a DN) that allow for
significant leading whitespace?
We need it for FQDNs, since according to RFC 2822, <firstname.lastname@example.org> is not
the same as < email@example.com> and we'd like to distinguish both correctly.
Thank You for hints.