Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]

james woodyatt <jhw@apple.com> Wed, 19 November 2008 00:33 UTC

Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC6953A6B2F for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 16:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.234
X-Spam-Level:
X-Spam-Status: No, score=-105.234 tagged_above=-999 required=5 tests=[AWL=-0.739, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 bDiOTE8KOZqA for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 16:33:54 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C9A2B3A6947 for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 16:33:53 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1L2axF-00054F-Nr for v6ops-data@psg.com; Wed, 19 Nov 2008 00:30:01 +0000
Received: from [17.254.13.23] (helo=mail-out4.apple.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <jhw@apple.com>) id 1L2axA-00053N-Px for v6ops@ops.ietf.org; Wed, 19 Nov 2008 00:29:59 +0000
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id 4631B4762E6C; Tue, 18 Nov 2008 16:29:56 -0800 (PST)
Received: from relay14.apple.com (unknown [127.0.0.1]) by relay14.apple.com (Symantec Brightmail Gateway) with ESMTP id 2D8C328090; Tue, 18 Nov 2008 16:29:56 -0800 (PST)
X-AuditID: 11807134-a6bbcbb000000f08-1a-49235e033dd1
Received: from [17.151.119.116] (unknown [17.151.119.116]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay14.apple.com (Apple SCV relay) with ESMTP id CBAFD28043; Tue, 18 Nov 2008 16:29:55 -0800 (PST)
Cc: IPv6 Operations <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Message-Id: <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com>
From: james woodyatt <jhw@apple.com>
To: Gert Doering <gert@space.net>
In-Reply-To: <20081118220136.GE89033@Space.Net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
Date: Tue, 18 Nov 2008 18:29:54 -0600
References: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com> <60FD682C-1436-493F-995D-4B2A7241D398@apple.com> <20081118220136.GE89033@Space.Net>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 18, 2008, at 16:01, Gert Doering wrote:
> On Mon, Nov 17, 2008 at 11:22:14PM -0600, james woodyatt wrote:
>> I am so *so* tired of making excuses for bad code.  Just once, I'd
>> like to be able to say, "I see your coders thought it would be a good
>> idea to store IP addresses in a persistent store without any cache
>> coherency protocol, and now you can't renumber your network without
>> eating the time and expense of qualifying a radical new  
>> implementation
>> of your hugely business-critical software application.  You know
>> what?  That's your own fault.  Not ours.  p.s. I bet you'll read that
>> tech-note next time, right?"
>
> OK, I bite.  What answer do you give to folks that need to renumber
> things like site-to-site VPN endpoints, which affects lots of  
> configuration
> to be changed by *other* folks (their VPN peers)?

Please, help me understand why solving this problem requires storing  
IP addresses in persistent storage without a coherent caching  
protocol.  I'm not seeing it-- probably because I'm not sure I  
understand the nature and scope of the problem very well.

For the sake of argument, I'll accept that reasonable people currently  
perceive it to be necessary.  My hunch is that those folks should  
probably be using DNS-SD instead of the fragile cruftiness they're  
struggling against now.  Maybe if I understood the problem better, I  
could suggest a more detailed alternative to their current solution.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering