| < draft-ietf-ipsec-skip-udh-00.txt | draft-ietf-ipsec-skip-udh-01.txt > | |||
|---|---|---|---|---|
| - 1 - | ||||
| IPSEC Working Group Ashar Aziz | IPSEC Working Group Ashar Aziz | |||
| INTERNET-DRAFT Tom Markson | INTERNET-DRAFT Tom Markson | |||
| Hemma Prafullchandra | Hemma Prafullchandra | |||
| Sun Microsystems, Inc. | Sun Microsystems, Inc. | |||
| Expires in six months December 21, 1995 | Expires in six months August 1, 1996 | |||
| Encoding of an Unsigned Diffie-Hellman Public Value | Encoding of an Unsigned Diffie-Hellman Public Value | |||
| <draft-ietf-ipsec-skip-udh-00.txt> | <draft-ietf-ipsec-skip-udh-01.txt> | |||
| Status of this Memo | Status of this Memo | |||
| This document is a submission to the IETF Internet Protocol Security | This document is a submission to the IETF Internet Protocol Security | |||
| (IPSEC) Working Group. Comments are solicited and should be addressed to | (IPSEC) Working Group. Comments are solicited and should be addressed to | |||
| to the working group mailing list (ipsec@ans.net) or to the authors. | to the working group mailing list (ipsec@ans.net) or to the authors. | |||
| This document is an Internet-Draft. Internet Drafts are working | This document is an Internet-Draft. Internet Drafts are working | |||
| documents of the Internet Engineering Task Force (IETF), its areas, and | documents of the Internet Engineering Task Force (IETF), its areas, and | |||
| its working Groups. Note that other groups may also distribute working | its working Groups. Note that other groups may also distribute working | |||
| skipping to change at page 3, line 5 ¶ | skipping to change at page 3, line 5 ¶ | |||
| Distribution of this memo is unlimited. | Distribution of this memo is unlimited. | |||
| Abstract | Abstract | |||
| It is useful to be able to communicate public keys in the absence of a | It is useful to be able to communicate public keys in the absence of a | |||
| certificate hierarchy and a signature infrastructure. This document | certificate hierarchy and a signature infrastructure. This document | |||
| describes a method by which certificates which communicate Diffie- | describes a method by which certificates which communicate Diffie- | |||
| Hellman public values and parameters may be encoded and securely named. | Hellman public values and parameters may be encoded and securely named. | |||
| CONTENTS | ||||
| Status of this Memo.................................. 1 | ||||
| Abstract............................................. 2 | ||||
| 1. Unsigned Public Keys................................. 3 | ||||
| 2. Encoding of an Unsigned DH public value.............. 3 | ||||
| 3. Verification of the Unsigned Public Value............ 5 | ||||
| 4. Security Considerations.............................. 5 | ||||
| Acknowledgements..................................... 5 | ||||
| References........................................... 5 | ||||
| Author's Address(es)................................. 6 | ||||
| - i - | ||||
| 1. Unsigned Public Keys | 1. Unsigned Public Keys | |||
| In public key cryptography, certificates provide a binding between an | In public key cryptography, certificates provide a binding between an | |||
| entity's name and their public key. The signature on the certificate | entity's name and their public key. The signature on the certificate | |||
| provides this binding. However, certificates tend to be difficult to | provides this binding. However, certificates tend to be difficult to | |||
| implement and usually require infrastructure to verify signatures. This | implement and usually require infrastructure to verify signatures. This | |||
| infrastructure and certificates, in general, are not in wide use on the | infrastructure and certificates, in general, are not in wide use on the | |||
| Internet. Instead of explicitly binding a name to a public value using | Internet. Instead of explicitly binding a name to a public value using | |||
| a signature, the name may be derived directly from the public key. This | a signature, the name may be derived directly from the public key. This | |||
| can be done by defining the name of the certificate to be the message | can be done by defining the name of the certificate to be the message | |||
| skipping to change at line 207 ¶ | skipping to change at line 188 ¶ | |||
| Alternate email address: markson@eng.sun.com | Alternate email address: markson@eng.sun.com | |||
| Hemma Prafullchandra | Hemma Prafullchandra | |||
| Sun Microsystems, Inc. | Sun Microsystems, Inc. | |||
| M/S PAL1-550 | M/S PAL1-550 | |||
| 2550 Garcia Avenue | 2550 Garcia Avenue | |||
| Mountain View, CA 94043 | Mountain View, CA 94043 | |||
| Email: hemma@eng.sun.com | Email: hemma@eng.sun.com | |||
| Alternate email address: hemma@incog.com | Alternate email address: hemma@incog.com | |||
| CONTENTS | ||||
| Status of this Memo.................................. 1 | ||||
| Abstract............................................. 2 | ||||
| 1. Unsigned Public Keys................................. 3 | ||||
| 2. Encoding of an Unsigned DH public value.............. 3 | ||||
| 3. Verification of the Unsigned Public Value............ 5 | ||||
| 4. Security Considerations.............................. 5 | ||||
| Acknowledgements..................................... 5 | ||||
| References........................................... 5 | ||||
| Author's Address(es)................................. 6 | ||||
| - i - | ||||
| End of changes. 5 change blocks. | ||||
| 23 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||