Re: [v6ops] Fwd: New Version Notification for draft-collink-v6ops-ent64pd-01.txt

Fernando Gont <fernando@gont.com.ar> Thu, 12 January 2023 10:03 UTC

Return-Path: <fernando@gont.com.ar>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 809DFC14EB1C; Thu, 12 Jan 2023 02:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4zwK0D28xEp; Thu, 12 Jan 2023 02:03:53 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1B8CC151532; Thu, 12 Jan 2023 02:03:48 -0800 (PST)
Received: from [192.168.100.19] (unknown [190.183.21.160]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 6D1D8282DBC; Wed, 21 Dec 2022 22:26:35 -0300 (-03)
Message-ID: <691e5624-ee62-fd43-8f45-9a2b05200653@gont.com.ar>
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
To: Gert Doering <gert@space.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: V6 Ops List <v6ops@ietf.org>, Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, draft-collink-v6ops-ent64pd@ietf.org, xiaom@google.com
References: <167107554671.48477.568330207202509840@ietfa.amsl.com> <CAFU7BATp=gEB3S8AzhCYDMN3fzLQrYY9pzcWJ=LQnrjC9bRKEA@mail.gmail.com> <Y5sy2ikgQEWSnCsM@Space.Net> <CAKD1Yr0EchmQ11eKCB4AfEJaG7_aFDDv_bavYJY4Zb3iDmhALg@mail.gmail.com> <4277d4e5a962400f8438e8f01c884654@huawei.com> <CAO42Z2y_SWybfLQE3g5a-kVieY05XSxaKTv-UG8kvfbYzJLH6w@mail.gmail.com> <12d95e0b-7264-2fcc-d131-1eca2a72d4e1@gmail.com> <Y6K6QtzrEnvqRfd4@Space.Net>
Content-Language: en-US
From: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <Y6K6QtzrEnvqRfd4@Space.Net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hIJfZLq_VSNKCbAFiVa_VSkTDRM>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-collink-v6ops-ent64pd-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
Date: Thu, 12 Jan 2023 10:03:57 -0000
X-Original-Date: Wed, 21 Dec 2022 22:26:30 -0300
X-List-Received-Date: Thu, 12 Jan 2023 10:03:57 -0000

On 21/12/22 04:48, Gert Doering wrote:
> Hi,
> 
> On Wed, Dec 21, 2022 at 08:50:10AM +1300, Brian E Carpenter wrote:
>> There's a reason that
>> https://www.rfc-editor.org/rfc/rfc7421.html#section-4.5 suggests
>> /80 as the reasonable limit for privacy purposes. The issue is
>> making it highly unlikely (and therefore prohibitively expensive)
>> to find an IID by a scanning attack. At /96, the search space is
>> about 4 billion. Given the number of Internet users in the world,
>> and possible applicability of the birthday paradox, that isn't a
>> safe value. (I can't expect to find *your* IID, but I can hope to
>> find *somebody's* IID.) At /80, the search space is about 281
>> trillion.
> 
> What would the benefit be of finding someone's IID, if that IID is only
> valid for a specific prefix?

Well, thatś normally a prerequisite for performing other attacks  -- you 
kind of cannot attack what you cannot find.

That's why IPv6 pentests can be challenging at times....

-- 
Fernando Gont
e-mail: fernando@gont.com.ar
PGP Fingerprint: 7F7F 686D 8AC9 3319 EEAD C1C8 D1D5 4B94 E301 6F01