FYI
Begin forwarded message:
> From: internet-dra...@ietf.org
> Subject: New Version Notification for
> draft-cooper-6man-ipv6-address-generation-privacy-00.txt
> Date: July 15, 2013 6:20:21 PM EDT
> To: Fernando Gont , Alissa Cooper ,
> Dave Thaler
>
>
> A new v
Hi Fernando,
On Jun 5, 2013, at 9:19 PM, Fernando Gont wrote:
> On 06/06/2013 12:24 AM, Alissa Cooper wrote:
>> I'll try to re-state one of my questions more simply, based on the
>> -09:
>>
>> How is the attack explained in C.4 mitigated by the mechanism
>&g
I'll try to re-state one of my questions more simply, based on the -09:
How is the attack explained in C.4 mitigated by the mechanism specified in
draft-ietf-6man-stable-privacy-addresses-09?
One more comment below:
On May 31, 2013, at 8:23 PM, Fernando Gont wrote:
>> Another point for clarifi
Hi Fernando,
Comments inline.
On May 26, 2013, at 9:01 AM, Fernando Gont wrote:
> HI Alissa,
>
> Thanks for posting this. Please find my comments inline...
>
> On 05/24/2013 11:33 PM, Alissa Cooper wrote:
>>
>> The rows of the table are the address generatio
I made updates in response to this email and Dave's emails and made the table
publicly viewable and editable if folks want to make further changes
themselves:
https://docs.google.com/spreadsheet/ccc?key=0Au4OS7RZgZwHdHozNzNHdUNtVEJSNlo3N3NFMG5Wa1E&usp=sharing
On May 24, 2013, at 6:28 PM, Brian
This discussion got me thinking about how to be rigorous in articulating the
specific threats that different kinds of addresses do and do not mitigate. I
put together a little table to try to sum this up:
http://www.alissacooper.com/files/IPv6-address-threats.pdf
The table assumes, for simplici
Hi Ammar,
On Nov 22, 2012, at 2:43 AM, Ammar Salih wrote:
> I can see almost everyone agrees to that the RIR info is not accurate and in
> many cases is incorrect, so why the hassle of assigning wrong locations? And
> why developers are building their applications based on incorrect
> information.
