RE: Fw: Welcome to the InterNAT...

"Tony Hain" <alh-ietf@tndh.net> Thu, 27 March 2003 17:32 UTC

Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09113; Thu, 27 Mar 2003 12:32:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18ybMj-0000VW-00 for ietf-list@ran.ietf.org; Thu, 27 Mar 2003 12:40:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18ybMG-0000Rd-00 for ietf@ran.ietf.org; Thu, 27 Mar 2003 12:40:08 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08745 for <ietf@ietf.org>; Thu, 27 Mar 2003 12:24:45 -0500 (EST)
Received: from eagleswings (127.0.0.1) by library with [XMail 1.10 (Win32/Ix86) ESMTP Server] id <S232C7> for <ietf@ietf.org> from <alh-ietf@tndh.net>; Thu, 27 Mar 2003 09:27:06 -0800
Reply-To: alh-ietf@tndh.net
From: Tony Hain <alh-ietf@tndh.net>
To: 'Pekka Savola' <pekkas@netcore.fi>
Cc: 'Eliot Lear' <lear@cisco.com>, 'The IETF' <ietf@ietf.org>
Subject: RE: Fw: Welcome to the InterNAT...
Date: Thu, 27 Mar 2003 09:27:01 -0800
Message-ID: <053a01c2f486$13d36010$ee1a4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <Pine.LNX.4.44.0303271832160.19060-100000@netcore.fi>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA09113

Pekka Savola wrote:
> Not so.  (If you build your system in an optimal fashion -- 
> which really 
> does need a bit fleshing out, though.)

So the intent is to dictate to everyone how they build their networks?

> 
> Such prefixes would then reach valid lifetime=x, preferred 
> lifetime=0, be set "deprecated" and not be used for new 
> connections anymore.  Nothing requires connections be killed 
> using such deprecated addresses.

Get real! If the prefix is not imediately invalidated, it will be
impossible to connect to nodes that now have a valid right to use that
prefix. If the router does not have a current prefix allocation, it must
set valid lifetime to 0. It is not reasonable to expect an automated
process to figure out when you want it to keep a prefix around and when
you want it to go away. Even if it could do that, one set of machines on
the local network may want the opposite state from another set of
machines. 

Tony