Authentication Scheme for Public ENUM Applications
draft-chenh-enum-app-auth-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chen Hui | ||
| Last updated | 2006-10-09 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
ENUM possesses the feature of E.164 number authenticity, therefore by being carried with initiation signal of application services, ENUM number can be used to identify originer. The service initiation signal includes sender's (originer's) un- encrypted ENUM number and encrypted ENUM number, or some other information needed by specific applications, then receiver decrypts encrypted ENUM number and compares decrypted result with the un- encrypted ENUM number to authenticate the originer's identity.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)