IETF Logo Mail Archive

Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))

Keith Moore <moore@cs.utk.edu> Mon, 31 March 2003 22:06 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 RAA27422; Mon, 31 Mar 2003 17:06:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 1907a1-00036Y-00 for ietf-list@ran.ietf.org; Mon, 31 Mar 2003 17:16:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 1907ZR-00033P-00 for ietf@ran.ietf.org; Mon, 31 Mar 2003 17:16:01 -0500
Received: from astro.cs.utk.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27033 for <ietf@ietf.org>; Mon, 31 Mar 2003 16:59:35 -0500 (EST)
Received: from astro.cs.utk.edu (localhost [127.0.0.1]) by astro.cs.utk.edu (cf 8.9.3) with SMTP id h2VM1vA06318; Mon, 31 Mar 2003 17:01:57 -0500 (EST)
Date: Mon, 31 Mar 2003 17:01:57 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Matt Crawford <crawdad@fnal.gov>
Cc: moore@cs.utk.edu, mansaxel@besserwisser.org, ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030331170157.1678c623.moore@cs.utk.edu>
In-Reply-To: <200303312143.h2VLhc2Y001999@gungnir.fnal.gov>
References: <43450000.1049144401@localhost.besserwisser.org> <200303312143.h2VLhc2Y001999@gungnir.fnal.gov>
X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 31 Mar 2003 15:43:38 -0600
"Matt Crawford" <crawdad@fnal.gov> wrote:

> > All things SL is claimed to solve are solveable with unique
> > addresses too, as long as you've got enough of them. The rest is
> > just simple (perhaps tedious) work that every operations-aware
> > person I know of would prefer to madness.
> 
> All right, how do you make internal site communications completely
> oblivious to a change in your externally-visible routing prefix?

You declare that any app that keeps connections around for more than
some time period T (say for 30 days) have a mechanism for
detecting and recovering from prefix changes. That solves the
problem for all apps, not just for local apps.

v2.23.0 | Report a Bug | By Email