IETF Logo Mail Archive

Re: [v6ops] Operational guidelines for a company/organization IPv6 address scheme supplemental to RFC5157

Fernando Gont <fgont@si6networks.com> Thu, 27 September 2012 18:43 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054A921F84C5 for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2012 11:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyglSY7TcivC for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2012 11:43:14 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 63EB121F84FE for <v6ops@ietf.org>; Thu, 27 Sep 2012 11:43:14 -0700 (PDT)
Received: from 217.64.252.202.mactelecom.net ([217.64.252.202] helo=[10.4.2.187]) by web01.jbserver.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <fgont@si6networks.com>) id 1THJ3G-0005X1-Ny; Thu, 27 Sep 2012 20:43:10 +0200
Message-ID: <50649E3D.6090402@si6networks.com>
Date: Thu, 27 Sep 2012 20:43:09 +0200
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: "Marksteiner, Stefan" <stefan.marksteiner@joanneum.at>
References: <8A317FD8C00FEE448E52D4EE5B56BB3E0232A086D8FF@RZJC1EX.jr1.local>, <1348519034.47465.YahooMailNeo@web32503.mail.mud.yahoo.com> <8A317FD8C00FEE448E52D4EE5B56BB3E0232A086D902@RZJC1EX.jr1.local>, <5061B157.1090106@gmail.com> <8A317FD8C00FEE448E52D4EE5B56BB3E0232A086D90A@RZJC1EX.jr1.local> <1348602134.63605.YahooMailNeo@web32505.mail.mud.yahoo.com> <8A317FD8C00FEE448E52D4EE5B56BB3E0232A08499BB@RZJC1EX.jr1.local>
In-Reply-To: <8A317FD8C00FEE448E52D4EE5B56BB3E0232A08499BB@RZJC1EX.jr1.local>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 'IPv6 Ops WG' <v6ops@ietf.org>
Subject: Re: [v6ops] Operational guidelines for a company/organization IPv6 address scheme supplemental to RFC5157
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Sep 2012 18:43:17 -0000

On 09/26/2012 09:16 AM, Marksteiner, Stefan wrote:
> There's a variety of reasons to keep track of addresses from usage
> and statistics to forensic purposes in security incidents (also those
> which are perpetrated from inside sources to outside targets). 

You might want to use ipv6mon for that:
<http://www.si6networks.com/tools/ipv6mon>


> Privacy extensions would perhaps be too unpredictable to manage, but
> stateful DHCPv6 combined with a suitable IPAM-solution would probably
> do the trick. Maybe I have been stuck  in my mindset a little, as we
> use only static addresses in our productive IPv4 network. 

Either the above, and/or implement draft-ietf-6man-stable-privacy-addresses

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email