Privacy and Security Considerations in ENUM
draft-shockey-enum-privacy-security-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard D. Shockey | ||
| Last updated | 2010-04-26 (Latest revision 2002-10-30) | ||
| Replaced by | draft-ietf-enum-privacy-security | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-enum-privacy-security | |
| 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
Many individuals and groups have expressed concerns about the privacy and security of personal information to be established in implementations of RFC 2916. This document discusses some of the technical as well as security and privacy considerations national implementations of ENUM should consider. This is a work in progress. Input from security and privacy experts is welcome.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)