Re: Brian Haberman's Discuss on draft-ietf-6man-stable-privacy-addresses-16: (with DISCUSS)

Fernando Gont <fgont@si6networks.com> Thu, 23 January 2014 11:50 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD701A042B; Thu, 23 Jan 2014 03:50:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aF96dBJ7ln-k; Thu, 23 Jan 2014 03:50:42 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3941D1A03E5; Thu, 23 Jan 2014 03:50:42 -0800 (PST)
Received: from 75-138-17-190.fibertel.com.ar ([190.17.138.75] helo=[192.168.3.102]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1W6InZ-0008GX-FY; Thu, 23 Jan 2014 12:50:17 +0100
Message-ID: <52E10153.8070001@si6networks.com>
Date: Thu, 23 Jan 2014 08:47:31 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>, Fernando Gont <fernando@gont.com.ar>, The IESG <iesg@ietf.org>
Subject: Re: Brian Haberman's Discuss on draft-ietf-6man-stable-privacy-addresses-16: (with DISCUSS)
References: <20140122202434.30069.4084.idtracker@ietfa.amsl.com> <52E02EAD.1050009@si6networks.com> <52E03BAD.5050306@innovationslab.net> <52E04278.1000401@gont.com.ar> <52E0FF5C.8050906@innovationslab.net>
In-Reply-To: <52E0FF5C.8050906@innovationslab.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, ipv6@ietf.org, draft-ietf-6man-stable-privacy-addresses@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 23 Jan 2014 11:50:44 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/23/2014 08:39 AM, Brian Haberman wrote:
> 
> On 1/22/14 5:13 PM, Fernando Gont wrote:
>>> All this point is making is that there are a variety of ways
>>> of getting this behavior and DNA provided guidance on one way
>>> to do that.  The simple solution is to refer to those RFCs 
>>> (informatively) and point out that they describe one way to
>>> track which addresses are associated with particular networks.
>>> This has the benefit of not forcing re-calculation of the hash
>>> on every (re-)connect.
>> 
>> I have no issues with that (I misinterpreted where you were
>> going, it seems).
>> 
>> So I guess one could add something along the lines of: "A node
>> may use Simple DNA [RFC6059] to reuse a previously-configured 
>> address for this network without the need to recompute the 
>> Interface-ID with the scheme specified in this document."
>> 
>> ?
>> 
> 
> That would work for me.  We can wait to see if any of AD has an
> issue with this text.

My understanding of the discussion with Thomas is that one could
rather use the SDNA stuff as a possible source for the Network_ID
parameter. That' be great. (I proposed some text to Thomas, and I'm
waiting for his response).

Regarding use of DNA as proposed in the suggested paragraph above, I
have no issues with it, although it seems orthogonal and out of scope
*here*. -- i.e., such note might make more sense for the other
document that has just been adopted. This one is about what to do when
you have already "decided" that you cannot reuse the
previously-assigned address.

Thoughts?

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




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJS4QE0AAoJEK4lDVUdTnSS6mwP/jtMdUHmCIUPfQ1jea3VWVta
ViGtQJs3zIyODuuK0gq+nzg16HNdBtQnct0K1VXdo3ZZhLVuJsJQUBTCzJKbMFvF
+dYwdYDCIRcTjEwLt7+EzQ/my+jhjBsKw0RpFS2xj2pzvk7ZWBChn8SEtxMrU419
aGvpRyh3cFXU7Zmnk6g/eFXm/HUvgUoYxSCbw480XxseuRgA3NyxHchvoLkTt0VF
67Kp3pw75LDU04rCo3zY18l1U2acnv4LzQ4auvpzF4jjuUyQEPvVJde8SB9XVUUn
CxZ5bb2YvcHOdWeRB05IrJnBij/Bb1NXHIGtYEnmN4L2pRicVSjeRj/B1gftQ/tl
QT1GMaAvak9hB2Qjf78QZn7Atl3Pz1ev1MwfEiODz1GHFoCf4OiBlFsnDWd3gCvG
RuMEZ/Jak6RR8zqjwEIVQRiXmmJR+R6LjGsjia1K6r5gxpsWseBsPhRk8QKU9Nze
EcbE16pMs645O0H5o3EKoPUzGKTV7d1z9aYjLodCDMS3+LTdF1JlMyVzzgrcZbna
DaLU/aPbn+y/IrdfhZrfLl/a8ERCJ6Sv4LMkJzIi8wtSZYEAfJGKDdT9uCJUMyNw
FAdmkzmO5BFbSpFjszvTTMM/Y2XxNVF5ysPFurmxOb489DRAJugLh7iBRYARWDuM
Uao28y7jpo5VgPCHYHmf
=wsjs
-----END PGP SIGNATURE-----