Re: Privacy IPv6 addresses (RFC 4941) and the SNMP IP address table in RFC 4293

Brian Haberman <brian@innovationslab.net> Wed, 25 June 2008 20:53 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C93EB28C15D; Wed, 25 Jun 2008 13:53:10 -0700 (PDT)
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 4F4523A6A32 for <ipv6@core3.amsl.com>; Wed, 25 Jun 2008 12:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599]
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 MKvgCqNsH01y for <ipv6@core3.amsl.com>; Wed, 25 Jun 2008 12:10:52 -0700 (PDT)
Received: from jhuapl.edu (piper.jhuapl.edu [128.244.26.33]) by core3.amsl.com (Postfix) with ESMTP id 978A03A68CC for <ipv6@ietf.org>; Wed, 25 Jun 2008 12:10:52 -0700 (PDT)
Received: from ([128.244.206.192]) by piper.jhuapl.edu with ESMTP id 5503081.18889604; Wed, 25 Jun 2008 15:10:37 -0400
Message-ID: <4862982D.1050206@innovationslab.net>
Date: Wed, 25 Jun 2008 15:10:37 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Kristine Adamson <adamson@us.ibm.com>
Subject: Re: Privacy IPv6 addresses (RFC 4941) and the SNMP IP address table in RFC 4293
References: <OF642D7DA0.5F773E86-ON87257472.0048C129-85257472.004A347D@us.ibm.com> <48628930.2030605@ericsson.com>
In-Reply-To: <48628930.2030605@ericsson.com>
X-Mailman-Approved-At: Wed, 25 Jun 2008 13:53:08 -0700
Cc: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>
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: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Hi Kristine,

Suresh Krishnan wrote:
> Hi Kristine,
> 
> Kristine Adamson wrote:
>>
>> Hello,
>>    I have a question about the SNMP IP address table in RFC 4293.  For 
>> privacy IPv6 addresses (as described in RFC 3041), it appears that the 
>> ipAddressOrigin MIB object is supposed to be set to a value of 
>> random(6).  Is this true also for these addresses as defined by RFC 4941
> 
> Yes. The ipAddressOrigin will be set to random for addresses generated 
> using RFC4941 as well.
> 
>> where sites can selectively enable or disable the use of privacy 
>> addresses for some prefixes?
> 
> I am not sure how this plays a role in picking the ipAddressOrigin 
> value. Maybe I misunderstood the scope of your question.

The ipAddressOrigin TC supports 4293 the same way it does 3041.  The 
commentary in the RFC was written prior to the elevation of privacy 
addresses to draft standard.

My understanding of 4293 is that it is not meant as a mechanism to 
control the generation of privacy addresses in any way.  I am not aware 
of any *standardized* method for doing this.  Though section 3.6 of 491 
encourages vendors to provide such a knob.

Regards,
Brian
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------