Re: IPv6 Routing & ND vs. Addressing, (Was: Re: <draft-ietf-6man-rfc4291bis-09.txt>)

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 15 July 2017 21:01 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1D712F27C for <ipv6@ietfa.amsl.com>; Sat, 15 Jul 2017 14:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 bPx1KfwCkUxe for <ipv6@ietfa.amsl.com>; Sat, 15 Jul 2017 14:01:43 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD8FC12EC61 for <ipv6@ietf.org>; Sat, 15 Jul 2017 14:01:43 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id q85so60100454pfq.1 for <ipv6@ietf.org>; Sat, 15 Jul 2017 14:01:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Rb7K63KiFQ/Oh737T9jtdV5dO1BEamOb35ovwH8qClw=; b=axThxe9c6HwAXPRei6obMjnLKgWO0DOVyocOz/x+HPH5kxM5tsNFF0htpTdPO0RLzc a6hn9GhpuF61L6BgM3/uBw4CQcB8tsVj6J/fp01a2pLSPXsv6FnhtpxMo68ibZlOAWiu OKY4R3wtxDohX6aiIjhwmaj6F9x1rCAcSXXrFBev27KEvmq7m9MlCdlaM+GkYjjSuCZK ItLKo+JiJ5QuQKVn0IuLlF4zSvhX912jQaWs1wAvSsfa1Qw6xM7Vb+x/q4qOSozOeJ/e 7eAhsBIlot5Kd7hrUKr15M1HFAHF7Szg0QPJJJ+czfXf4jKVIklNqLdHKlhUGMDyJTNb 9Ggg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Rb7K63KiFQ/Oh737T9jtdV5dO1BEamOb35ovwH8qClw=; b=Y/bsan2LB72kii1ERWtfBNjhCUvJA1pmS8sqz5PG8wFwscnHZExp5V66UGr9fLkm/P twZ/k/oYxrb67PlmUZfHiV/oC7QpuJyl+sV4VQXlJl4PiMbNswKo3HfIYnvgP8ZtyVZM MyOln6MEkppT+JXIy0LMi9VWllfEJ2tPJB3wJW4rvz6+6PsvdLiQTQH1ZQm8H+9aCqWn cU001zHoBAIlmVNNIoxg6ivDOeAV0M+NqWMUGi1xGKP9ZL39INstyEEKKsl7my4gSRqX S+1DYM3NRqsHdZS573cRLvldaeKyCV0wJtS0LmVwoTdCAQ+20W/9TjPgRrJ56me0xM1f TEAg==
X-Gm-Message-State: AIVw111YuhpYuk5l9AOdSxzWXvLEjNPlca+beoBPbl8irv8yc6mUIFdU 5YJMYh4E0vTD1Uku
X-Received: by 10.84.214.143 with SMTP id j15mr22450777pli.40.1500152502731; Sat, 15 Jul 2017 14:01:42 -0700 (PDT)
Received: from [192.168.178.21] (69.21.255.123.dynamic.snap.net.nz. [123.255.21.69]) by smtp.gmail.com with ESMTPSA id o62sm26679370pfg.120.2017.07.15.14.01.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Jul 2017 14:01:42 -0700 (PDT)
Subject: Re: IPv6 Routing & ND vs. Addressing, (Was: Re: <draft-ietf-6man-rfc4291bis-09.txt>)
To: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>, ipv6@ietf.org
References: <CAN-Dau2zgthR2w9e5ZVUdGc-vm+YvK2uTUJ8O=vrcv0jNc58RA@mail.gmail.com> <CAN-Dau03r_CKW53kegaLa=F_R_RG4cWaCT1j6idrqPm9UuN03A@mail.gmail.com> <5963BF27.1050300@foobar.org> <ff09ffcd-df65-4033-8018-fbe7ae98cff8@gmail.com> <6bf7f3d0e9c047b1b86d4bcc220f8705@XCH15-06-11.nw.nos.boeing.com> <CAN-Dau1bxm5y0v_6kUBc_ym39bSSxepjdwrzcS7YHWD=CV9-bw@mail.gmail.com> <3b34d6e9718a45ae80877e36fb55f2b4@XCH15-06-11.nw.nos.boeing.com> <CAO42Z2x+282VK7nMFHjcCz9tBmJ_=d4OhkiRZFZDLcZhakGB1Q@mail.gmail.com> <30cb27b2-007a-2a39-803d-271297862cae@gmail.com> <40d757eb97564bc8bb0511063bd9d3f4@XCH15-06-11.nw.nos.boeing.com> <CAO42Z2x7ER2fUietjT3Ns-jpCqscCmVDVubiM0Dgw1_L0bkw=A@mail.gmail.com> <c7b140bf69104cd3877a7da03fbf17e7@XCH15-06-11.nw.nos.boeing.com> <32924d19-e5ce-7606-77f4-925b682065f5@gmail.com> <745583ab45bb407a9a210020a96773c5@XCH15-06-11.nw.nos.boeing.com> <m1dVbRc-0000GQC@stereo.hq.phicoh.net> <b6da9e67-1f4e-8900-5a3b-575d0c6fd2fd@gmail.com> <m1dWNIL-0000FpC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3d2f1182-ec19-959e-a63f-ad0d316bbacf@gmail.com>
Date: Sun, 16 Jul 2017 09:01:36 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <m1dWNIL-0000FpC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Gj9OEHFTOfCrje_lSLOvGXMtpWk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 15 Jul 2017 21:01:45 -0000

On 16/07/2017 01:39, Philip Homburg wrote:
>> This is backwards. The goals of pseudo-random IIDs are to reduce the
>> probability that scanning attacks find hosts, and to reduce the risk
>> of IIDs being used to breach privacy.
>>
>> If these goals are met, the collision probability will in any case
>> be low, so DAD failure will be exceedingly rare.
> 
> I completely disagree. A collision is fatal. We are nowhere near transparently
> handling all collisions. At best we can hope that DAD can make one node
> continue unaffected.

I'm confused.

Firstly, do we have any experimental evidence that collisions
are a real operational problem? (Obviously, MAC address collisions are
disastrous at layer 2 anyway, so although IPv6+(Modified EUI-64) needs to
detect them, they are irrelevant to the current discussion.)

Secondly, if a collision does occur with IPv6+(pseudo-random IID),
recovery is obvious: after DAD failure, generate a new pseudo-random
IID and try again. This is perfectly compatible with RFC4862 section 5.5
and is specfied in RFC7217 for stable IIDs and in RFC4941 for privacy
addresses.

    Brian

> 
> In contrast, people have been scanning my IPv4 ranges for the past 20 years
> or so. That may be annoying. That may amplify attacks opportunities. But
> in it self it is not fatal.
> 
> 
> .
>