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

Kristine Adamson <adamson@us.ibm.com> Thu, 26 June 2008 09: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 A86C628C106; Thu, 26 Jun 2008 02:53:48 -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 4275B28C101 for <ipv6@core3.amsl.com>; Thu, 26 Jun 2008 02:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 T-7maXYwFYA0 for <ipv6@core3.amsl.com>; Thu, 26 Jun 2008 02:53:46 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by core3.amsl.com (Postfix) with ESMTP id 42C6A3A686D for <ipv6@ietf.org>; Thu, 26 Jun 2008 02:53:46 -0700 (PDT)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e32.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m5Q9n0eE002443 for <ipv6@ietf.org>; Thu, 26 Jun 2008 05:49:00 -0400
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m5Q9rlCQ179442 for <ipv6@ietf.org>; Thu, 26 Jun 2008 03:53:47 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m5Q9rlLW031940 for <ipv6@ietf.org>; Thu, 26 Jun 2008 03:53:47 -0600
Received: from d03nm118.boulder.ibm.com (d03nm118.boulder.ibm.com [9.17.195.144]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m5Q9rlHo031926 for <ipv6@ietf.org>; Thu, 26 Jun 2008 03:53:47 -0600
In-Reply-To: <4862982D.1050206@innovationslab.net>
To: ipv6@ietf.org
MIME-Version: 1.0
Subject: Re: Privacy IPv6 addresses (RFC 4941) and the SNMP IP address table in RFC 4293
X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006
Message-ID: <OFEDAF6F86.3C130B87-ON87257474.00360466-85257474.003664DC@us.ibm.com>
From: Kristine Adamson <adamson@us.ibm.com>
Date: Thu, 26 Jun 2008 03:53:46 -0600
X-MIMETrack: S/MIME Sign by Notes Client on Kristine Adamson/Raleigh/IBM(Release 7.0 HF144|February 01, 2006) at 06/26/2008 05:54:07 AM, Serialize by Notes Client on Kristine Adamson/Raleigh/IBM(Release 7.0 HF144|February 01, 2006) at 06/26/2008 05:54:07 AM, Serialize complete at 06/26/2008 05:54:07 AM, S/MIME Sign failed at 06/26/2008 05:54:07 AM: The cryptographic key was not found, Serialize by Router on D03NM118/03/M/IBM(Release 8.0.1|February 07, 2008) at 06/26/2008 03:53:47, Serialize complete at 06/26/2008 03:53:47
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-Type: multipart/mixed; boundary="===============0697906020=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Suresh/Brian,
   Thanks for your quick replies.  I just wanted to verify that the 
ipAddressOrigin MIB object would still be set to random(6) for the privacy 
addresses defined by RFC 4941. 


Kristine Adamson
IBM z/OS Communications Server: TCP/IP Development
Internet e-mail:adamson@us.ibm.com


Brian Haberman <brian@innovationslab.net>; wrote on 06/25/2008 03:10:37 PM:

> 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
--------------------------------------------------------------------