|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Wed, 28 Apr 2004 12:22:03 -0700 From: Owen DeLong <owen@delong.com> To: Pekka Savola <pekkas@netcore.fi>, Kevin Oberman <oberman@es.net> Cc: Steve Conte <conte@iana.org>, nanog@merit.edu In-Reply-To: <Pine.LNX.4.44.0404282041530.11021-100000@netcore.fi> Errors-To: owner-nanog-outgoing@merit.edu --==========3BCDB6A6C1F059E7ED65========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline That would be one possible solution. Other solutions would be: Each registry could have a well-known well signed PGP key and use that to sign these announcement postings. IANA could make these announcements using a well-known well signed PGP key. Of course, all of those options are not mutually exclusive, either. Owen --==========3BCDB6A6C1F059E7ED65========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (Darwin) iD8DBQFAkARbn5zKWQ/iqj0RAqyCAJ0QjYvA6wzpX3/U6eifiUAQ4/FdMwCfbTQs oeR16yHnyiwpLLTm5HyylhI= =yTZG -----END PGP SIGNATURE----- --==========3BCDB6A6C1F059E7ED65==========--
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |