Notation data format: "user" name space rejected

[Michael Young]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The latest draft of RFC2440 describes two name spaces for notation
data, one of which GnuPG rejects as invalid.  Specifically, the
RFC describes the "user" name space:

>    Names in the user name space consist of a UTF-8 string tag followed
>    by "@" followed by a DNS domain name. Note that the tag MUST NOT
>    contain an "@" character. For example, the "sample" tag used by
>    Example Corporation could be "sample at example.com".

When I try to generate such a notation, I get this error:
    log_error(_("a notation name must have only letters, "
  "digits, dots or underscores and end with an '='\n") );

(My test used 1.0.6, but it doesn't appear to have changed in the
latest source.)

At first glance, it would appear that adding the "@" character
to the check on the line before the log_error() would be sufficient.
But neither the "tag" nor the DNS domain name should need to meet
these tight restrictions (alphanumeric/dot/underscore).  So, I
would suggest looking for a "@" first, at which point almost
anything goes.  Does that seem reasonable?

-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.3

iQA/AwUBPNrFJFMkvpTT8vCGEQKhpgCg2dVswZWsaKwSZGkvQh7Cg3UYDjoAoMCz
tgIKnXkM0nKFPmSe2YWZRWXQ
=U8xW
-----END PGP SIGNATURE-----