Re: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt

Henning Schulzrinne <hgs@cs.columbia.edu> Sat, 14 June 2003 01:34 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01112 for <nsis-archive@odin.ietf.org>; Fri, 13 Jun 2003 21:34:48 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5E1YKM09354 for nsis-archive@odin.ietf.org; Fri, 13 Jun 2003 21:34:20 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DJ91a30409; Fri, 13 Jun 2003 15:09:01 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DJ8lm30139 for <nsis@optimus.ietf.org>; Fri, 13 Jun 2003 15:08:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19464 for <nsis@ietf.org>; Fri, 13 Jun 2003 15:08:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qtsh-0000aJ-00 for nsis@ietf.org; Fri, 13 Jun 2003 15:06:35 -0400
Received: from opus.cs.columbia.edu ([128.59.20.100]) by ietf-mx with esmtp (Exim 4.12) id 19Qtsg-0000aG-00 for nsis@ietf.org; Fri, 13 Jun 2003 15:06:34 -0400
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191]) by opus.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h5DJ8due029385; Fri, 13 Jun 2003 15:08:39 -0400 (EDT)
Message-ID: <3EEA2056.5020207@cs.columbia.edu>
Date: Fri, 13 Jun 2003 15:04:54 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030603 Thunderbird/0.1a
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Allison Mankin <mankin@psg.com>
CC: Michael Thomas <mat@cisco.com>, brunner@ccrle.nec.de, john.loughney@nokia.com, nsis@ietf.org
Subject: Re: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt
References: <E19QgNO-000IdP-00@psg.com>
In-Reply-To: <E19QgNO-000IdP-00@psg.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Allison Mankin wrote:

> Globally unique means a reasonably quite pseudo-random number
> (because it isn't good to have the resources id'd as someone else's)
> or a value that is sure to be unique.
> 
> I'm not asking the document to take these ramblings in...just raising
> thoughts.

The interim meeting slides have an 'analysis' of the collision 
probability for different random number lengths, which were 
significantly lower than any other reasonable failure probabilities and 
similar to the probability that Earth will be obliterated by a meteor, 
from my recollection.

I also believe that are no reasonable alternatives unless one assumes

1) every originator has a DNS name that is guaranteed to be unique and 
that it has easy access to (this isn't true without a working inverse 
mapping)

or

2) every originator has a globally unique IP address (clearly iffy)

or

3) we posit some global number handout algorithm system (maybe useful, 
but non-trivial; see multicast address assignment problem)

Henning



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis