Re: Question about RFC6724

Philip Homburg <pch-ipv6-ietf-8@u-1.phicoh.com> Tue, 03 May 2022 06:42 UTC

Return-Path: <pch-b28DE43C2@u-1.phicoh.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 2A7E1C14F734 for <ipv6@ietfa.amsl.com>; Mon, 2 May 2022 23:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 3MX4IDP8OqlJ for <ipv6@ietfa.amsl.com>; Mon, 2 May 2022 23:42:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93AC1C14F72F for <ipv6@ietf.org>; Mon, 2 May 2022 23:42:50 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1nlmFC-0000JkC; Tue, 3 May 2022 08:42:46 +0200
Message-Id: <m1nlmFC-0000JkC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Question about RFC6724
From: Philip Homburg <pch-ipv6-ietf-8@u-1.phicoh.com>
Sender: pch-b28DE43C2@u-1.phicoh.com
References: <m1nlQqC-0000IEC@stereo.hq.phicoh.net> <efffe452-cbcb-e546-972b-e2bb22a98b62@gmail.com>
In-reply-to: Your message of "Tue, 3 May 2022 08:49:25 +1200 ." <efffe452-cbcb-e546-972b-e2bb22a98b62@gmail.com>
Date: Tue, 03 May 2022 08:42:45 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/VgSg3fRwOr6JxrT-p6Jen4tf2xY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 03 May 2022 06:42:53 -0000

>> In the context of RFC 6724, can you give an example where limiting the
>> CommonPrefixLen to 64 gives the wrong result?
>
>If read that way, it means that all IPv4-mapped addresses match each other
>at /64. I'm sure that isn't the intention and I very much doubt that any
>implementation does that. See my reply to Fred Templin.

If it is obviously wrong, then it should be possible to give an example
where RFC 6724 gives the wrong results. 

Any material change in RFC 6724, would basically be us (6man) trying to define
address selection for IPv4. 

There is a reason the common prefix len is now limited to 64. The same
reasoning applies to IPv4 (i.e., just comparing all address bits is as wrong
for IPv4 as it is for IPv6).