Skip to main content

On the Generation of Transient Numeric Identifiers
draft-irtf-pearg-numeric-ids-generation-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Fernando Gont , Ivan Arce
Last updated 2020-02-24 (Latest revision 2019-08-23)
Replaces draft-gont-numeric-ids-generation, draft-gont-predictable-protocol-ids
RFC stream Internet Research Task Force (IRTF)
Formats
Reviews
IETF conflict review conflict-review-irtf-pearg-numeric-ids-generation, conflict-review-irtf-pearg-numeric-ids-generation, conflict-review-irtf-pearg-numeric-ids-generation, conflict-review-irtf-pearg-numeric-ids-generation, conflict-review-irtf-pearg-numeric-ids-generation, conflict-review-irtf-pearg-numeric-ids-generation
Additional resources Mailing list discussion
Stream IRTF state (None)
Consensus boilerplate Unknown
Document shepherd (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

This document performs an analysis of the security and privacy implications of different types of "numeric identifiers" used in IETF protocols, and tries to categorize them based on their interoperability requirements and the associated failure severity when such requirements are not met. Subsequently, it provides advice on possible algorithms that could be employed to satisfy the interoperability requirements of each identifier type, while minimizing the security and privacy implications, thus providing guidance to protocol designers and protocol implementers. Finally, this describes a number of algorithms that have been employed in real implementations to generate transient numeric identifiers and analyzes their security and privacy properties.

Authors

Fernando Gont
Ivan Arce

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)