IETF Logo Mail Archive

Re: Randomness of Message-ID in IMDN

"Frank Ellermann" <nobody@xyzzy.claranet.de> Thu, 15 May 2008 19:29 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F06C3A6912; Thu, 15 May 2008 12:29:30 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C7723A68D6 for <ietf@core3.amsl.com>; Thu, 15 May 2008 12:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FSIWxXNx9loa for <ietf@core3.amsl.com>; Thu, 15 May 2008 12:29:05 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 96C3428C148 for <ietf@ietf.org>; Thu, 15 May 2008 12:27:56 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Jwj7D-0005uK-7k for ietf@ietf.org; Thu, 15 May 2008 19:27:47 +0000
Received: from hmbg-d9b88e26.pool.mediaways.net ([217.184.142.38]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Thu, 15 May 2008 19:27:47 +0000
Received: from nobody by hmbg-d9b88e26.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Thu, 15 May 2008 19:27:47 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: Randomness of Message-ID in IMDN
Date: Thu, 15 May 2008 21:28:30 +0200
Organization: <http://purl.net/xyzzy>
Lines: 27
Message-ID: <g0i2r2$l2f$1@ger.gmane.org>
References: <20080503211234.0377B5081A@romeo.rtfm.com><C5B56A4A-1901-41F6-B47E-C04F51D813E6@standardstrack.com><20080514154217.28E375081A@romeo.rtfm.com><28AB2CB7-DE19-42B0-906C-2D900FEDFB1A@standardstrack.com><20080514172556.2819F5081A@romeo.rtfm.com><g0hor4$frm$2@ger.gmane.org> <20080515185334.6BA8F5081A@romeo.rtfm.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e26.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Cc: simple@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Eric Rescorla wrote:

> looking at the examples in -07, it sure looks to me like
> message ids are not intended to be globally unique forever,
> since, since they're way too short.

Indeed, whatever it is, it is certainly no 2822 Message-ID.

>> a "worldwide unique forever" Message-ID can boil down to
>> timestamp @ domain (plus magic to avoid collisions for
>> various Message-ID generators for a given domain or
>> subdomain).
 
> I'm not sure I get the point you're trying to make here.

Some Message-ID generators I'm aware of use timestamps 
spiced with other ingredients (process number, specific
format per application) for the unique part (left hand
side), and their outcome is predictable to some degree.

Noted in the "security considerations" of corresponding
RFCs as one of several possible issues with Message-IDs.

I'm not sure what this IMDN handle really is, some kind
of magic cookie.

 Frank

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email