notation data & policy URL

[Atom 'Smasher']

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

> Once you have a @ character in the key, you are explicitly saying that
> the format of the value is defined by you.  You can thus put anything
> you like in there.  Since the IETF has not defined any "official"
> keys, GnuPG requires you to have that @ character.
==========================================

ok... i may be slow, but i'm catching on.... ;)

so, there is an IETF name space and a user name space. any name that
includes "@" is part of the user name space, and any name that does not
include "@" is part of the IETF name space.

how am i doing so far?

now, since the IETF hasn't defined anything to be used in their name
space, that leaves the user name space, which should (must?) be in the
form of an email address (name at domain).

am i still doing ok?

so, what does IETF have planned for their notation data within openPGP
keys? of what practical use is it for user data? are there any examples of
some legitimate uses or planned uses?


        ...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 3EBE 2810 30AE 601D 54B2 4A90 9C28 0BBF 3D7D 41E3
 -------------------------------------------------

	"I don't know anything about music.
	 In my line you don't have to."
		-- Elvis Presley
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iEYEARECAAYFAkB4ZzEACgkQnCgLvz19QeMb4ACdEDkHED+fXw8A/tEpmyd90riJ
Y+AAn3+8HaPSUBHfNPuLeC99mD3KFMgB
=jEpX
-----END PGP SIGNATURE-----