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

Fernando Gont <fernando@gont.com.ar> Thu, 12 January 2023 11:13 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 4CD74C14CF1C for <v6ops@ietfa.amsl.com>; Thu, 12 Jan 2023 03:13:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] autolearn=ham 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 0o6gg1sOW1wD for <v6ops@ietfa.amsl.com>; Thu, 12 Jan 2023 03:13:49 -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 843B8C14EB14 for <v6ops@ietf.org>; Thu, 12 Jan 2023 03:13: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)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 23415282DC7; Wed, 21 Dec 2022 22:50:41 -0300 (-03)
Message-ID: <2aa6b925-f88f-69fc-70ef-926a68fea4af@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
Content-Language: en-US
To: Martin Huněk <martin.hunek@tul.cz>, Brian E Carpenter <brian.e.carpenter@gmail.com>, v6ops@ietf.org
References: <167107554671.48477.568330207202509840@ietfa.amsl.com> <2859685.e9J7NaK4W3@asclepius.adm.tul.cz> <3cac1c98-8cdb-8b5b-4d03-7b03c24f8124@gmail.com> <2148317.C4sosBPzcN@asclepius.adm.tul.cz> <b0799fdf-49af-d5ac-803f-2a838c1537fb@gmail.com> <ac2b11e3-1860-abf9-1f7f-f2f0cae22db3@tul.cz>
From: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <ac2b11e3-1860-abf9-1f7f-f2f0cae22db3@tul.cz>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hLkMths2btpAD00WqA_Yy3x5tsk>
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 11:13:51 -0000
X-Original-Date: Wed, 21 Dec 2022 22:50:39 -0300
X-List-Received-Date: Thu, 12 Jan 2023 11:13:51 -0000

Hi,

On 21/12/22 13:13, Martin Huněk wrote:
> 
> On 21. 12. 22 5:02, Brian E Carpenter wrote:
>> On 21-Dec-22 13:19, Martin Huněk wrote:
>>> Hi Brian,
>>>
>>> Dne pondělí 19. prosince 2022 21:59:12 CET, Brian E Carpenter napsal(a):
>>>> On 19-Dec-22 23:30, Martin Huněk wrote:
>>>>
>>>>> Furthermore, this address has to be predictable for an 
>>>>> ISP/netadmin, so it is possible to make an AAAA record for it
>>>>
>>>> Er, no, the creation of such an AAAA record should be automated 
>>>> (subject to some kind of authorization).
>>>
>>> I would certainly not want arbitrary (BYOD) connected devices to be 
>>> allowed to manipulate DNS records in my domain by the DDNS. There are 
>>> security reasons for that. If I know the DUID of the device providing 
>>> some service to the Internet users and the IID where the device 
>>> listens is known, I can make static prefix delegation, and then I can 
>>> make an AAAA record for it. Without it, I can run only IPv4 services 
>>> there.
>>
>> Completely understood. But the bad old days of using the MAC address 
>> to create the IID are gone, and numbering hosts from 1 upwards would 
>> be extremely helpful for some kinds of attack.
> 
> Again, I do not suggest that it should, by default, number 
> hosts/services from 1 upwards. I'm saying that when (and only when) the 
> device is providing service to the Internet, the IID on which the 
> service is listening should be predictable.

No. It does not need to be predictable -- that's one of the reasons for 
which you have the DNS. If anything, it needs to be stable, to avoid the 
hassle (and glitches) to perform DNS updates regularly.

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