Guidelines for the Generation of Message IDs and Similar Unique Identifiers
draft-ietf-usefor-msg-id-alt-00

Document Type Expired Internet-Draft (usefor WG)
Last updated 1998-09-02
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-usefor-msg-id-alt-00.txt

Abstract

[RFC822] and [RFC1036] define so-called 'Message-IDs' that represent a unique identifier for email and netnews messages. A similar identifier is also used by [RFC2045] for the 'Content-ID' label. For each of these protocols, uniqueness of the identifiers generated is more or less essential. Unfortunately, the original Message-ID specification requires that the generator have an own, non-temporary full qualified domain name available, which does not allow hosts that are connected via dialup lines and get dynamically assigned IP addresses (and hostnames) to generate unique IDs offline. This memo provides recommendations for the generation of such IDs without risking non-uniqueness.

Authors

Claus Faerber (cfaerber@muc.de)

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