Re: Question about RFC6724
Philip Homburg <pch-ipv6-ietf-8@u-1.phicoh.com> Wed, 04 May 2022 07:27 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 28BE6C157B4F for <ipv6@ietfa.amsl.com>; Wed, 4 May 2022 00:27:11 -0700 (PDT)
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, RCVD_IN_DNSWL_HI=-5, 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 wjb_ebi4_Jdq for <ipv6@ietfa.amsl.com>; Wed, 4 May 2022 00:27:10 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [45.83.6.19]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65957C157B47 for <ipv6@ietf.org>; Wed, 4 May 2022 00:27:07 -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 m1nm9Pc-0000KeC; Wed, 4 May 2022 09:27:04 +0200
Message-Id: <m1nm9Pc-0000KeC@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> <m1nlmFC-0000JkC@stereo.hq.phicoh.net> <f22f0aed-f3aa-7016-844f-89e5f576440d@gmail.com>
In-reply-to: Your message of "Wed, 4 May 2022 09:03:08 +1200 ." <f22f0aed-f3aa-7016-844f-89e5f576440d@gmail.com>
Date: Wed, 04 May 2022 09:27:02 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0-VFaeMxbix74VLtzFi0iXc6QOc>
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: Wed, 04 May 2022 07:27:11 -0000
>10.1.0.10 printer.mynet.example.com >192.168.178.99 printer.mynet.example.com > >then getaddrinfo() returns this, on a Windows host whose IPv4 >address is 192.168.178.20: > >(<AddressFamily.AF_INET: 2>, 0, 0, '', ('10.1.0.10', 0)) >(<AddressFamily.AF_INET: 2>, 0, 0, '', ('192.168.178.99', 0)) Thanks for the example. After careful reading of RFC 6724, I think you are right. We should update the description of CommonPrefixLen, such that for IPv4-mapped it considers the length of IPv4 prefix. I thought the reason it mentions 64, is that it is hard to use the real prefix length. For example, in a system that receives addresses using IA_NA and where there are no onlink prefixes, how does one determine "the portion of the address not including the interface ID". However, that is an IPv6 problem. For IPv4 it should be clear what the prefix length is.
- Question about RFC6724 Brian E Carpenter
- Re: Question about RFC6724 Erik Kline
- Re: Question about RFC6724 Philip Homburg
- RE: Question about RFC6724 Templin (US), Fred L
- Re: Question about RFC6724 Brian E Carpenter
- Re: Question about RFC6724 Brian E Carpenter
- Re: Question about RFC6724 JINMEI Tatuya / 神明達哉
- Re: Question about RFC6724 Brian E Carpenter
- Re: Question about RFC6724 JINMEI Tatuya / 神明達哉
- Re: Question about RFC6724 Philip Homburg
- Re: Question about RFC6724 Brian E Carpenter
- Re: Question about RFC6724 Philip Homburg
- RE: Question about RFC6724 Vasilenko Eduard