PROPOSED FRAMEWORK ________________________________ Location for "Remailer Description" (actual remailer) -the Help File (obtainable through remailer-help standard query Location for "Remailer Description" (not an actual remailer e.g TURING aka CC) -(some dedicated webpage, in .txt format -possibly with a standard name ( \RemailerDescription.txt ) ________________________________ Section delimination the relevant section could be delimited with: -----BEGIN REMAILER DESCRIPTION -----END REMAILER DESCRIPTION and contain one line per keyword ________________________________ Keyword line I initially thought of a line looking like a record from a comma-delimited file But, because the whole section is immerged in a non-machine-readable file, there is no inconvenient to a more unix-like structure: $RemailerDescription{"RemailerName"}{"RemailerOccurrence"}{"Protocol"}{"Keyword"} = "Value" With RemailerName is the Remailer's name (e.g. "Frog", "CC", "Farout"...) Remailer Occurrence is a number/String (generally "0", but might be "1", "2" in case of mirrored sites) Protocol is the available channel/port (generally "80" for http, but could be finger or mail) Keyword is the name of the data whose value follows (e.g. "Keyring_RSA_asc" or "Keyring_RSA+DSS_pgp") Value is a value (or a list of values, blank-separated) relevant with the keyword (e.g. "http://www.privacyresources.org/frogadmin/Keys/pgpkeys.asc") ________________________________ Example Frog saying: "I offer an ascii-armored version of PGP keyrings, with RSA-only keys and the preferred location to find it is on my website http://www.privacyresources.org/frogadmin/Keys/pgpkeys.asc and I also offer a binary version" would spell: -----BEGIN REMAILER DESCRIPTION $RemailerDescription{"Frog"}{"0"}{"80"}{"Keyring_RSA_asc"} = "http://www.privacyresources.org/frogadmin/Keys/pgpkeys.asc" $RemailerDescription{"Frog"}{"0"}{"80"}{"Keyring_RSA_pgp"} = "http://www.privacyresources.org/frogadmin/Keys/pgpkeys.pgp" -----END REMAILER DESCRIPTION