Re: addrsel: privacy addresses within/out of a site

Pekka Savola <pekkas@netcore.fi> Tue, 04 January 2011 06:31 UTC

Return-Path: <pekkas@netcore.fi>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D8E03A6B43 for <ipv6@core3.amsl.com>; Mon, 3 Jan 2011 22:31:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level:
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, 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 RHoQCZsZ7Qgy for <ipv6@core3.amsl.com>; Mon, 3 Jan 2011 22:31:16 -0800 (PST)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 5B1453A6B42 for <ipv6@ietf.org>; Mon, 3 Jan 2011 22:31:16 -0800 (PST)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id p046XDCk012785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jan 2011 08:33:13 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id p046XDPA012782; Tue, 4 Jan 2011 08:33:13 +0200
Date: Tue, 04 Jan 2011 08:33:13 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: addrsel: privacy addresses within/out of a site
In-Reply-To: <4D2223DB.1000708@gmail.com>
Message-ID: <alpine.LRH.2.02.1101040831240.12735@netcore.fi>
References: <alpine.LRH.2.02.1101031151250.23654@netcore.fi> <20110103204031.0c3589b7@opy.nosense.org> <alpine.LRH.2.02.1101031213060.23654@netcore.fi> <4D2223DB.1000708@gmail.com>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: clamav-milter 0.96.5 at otso.netcore.fi
X-Virus-Status: Clean
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 06:31:18 -0000

On Tue, 4 Jan 2011, Brian E Carpenter wrote:
> Wouldn't the rule "Use ULA prefix inside the site and PA prefix (with
> privacy addresses if desired) otherwise" be simpler? And, by default,
> it would prevent the "inside" address being exported by mistake.

Two prefixes in access lists doesn't seem simpler, though I see it 
could be an option in some other contexts. In our case, we have 20+ 
subnets which are not behind a single big firewall, so there is no 
"inside" and "outside". Also for that reason, using only globals would 
be preferable.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings