IETF Logo Mail Archive

Re: [v6ops] Thoughts about wider operational input

Joe Maimon <jmaimon@jmaimon.com> Wed, 23 March 2022 20:32 UTC

Return-Path: <jmaimon@jmaimon.com>
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 596093A0CBD for <v6ops@ietfa.amsl.com>; Wed, 23 Mar 2022 13:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 jr5kXWF_clAV for <v6ops@ietfa.amsl.com>; Wed, 23 Mar 2022 13:32:14 -0700 (PDT)
Received: from smtp.chl.com (smtp.ttec.chl.com [216.222.148.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C1DF3A0CB3 for <v6ops@ietf.org>; Wed, 23 Mar 2022 13:32:14 -0700 (PDT)
Received: from [216.222.150.100] (joe.ttec.chl.com [216.222.150.100]) by smtp.chl.com (8.13.6/8.13.6) with ESMTP id 22NKVsno010191; Wed, 23 Mar 2022 15:31:54 -0500
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, buraglio@es.net, Vasilenko Eduard <vasilenko.eduard@huawei.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <A72CDDDB-CDCE-4EAF-B95E-997C764DB2C4@gmail.com> <9175dc32-45c1-e948-c20a-3bcc958b77b9@gmail.com> <YjmJQMNgnJoSInUw@Space.Net> <fd17a91f-68dc-92b5-0544-51aefa1b7f08@gmail.com> <CAM5+tA-Wq5O4pjQ++VZQi-FTKZGMRAW-LFc6O5dPOyox4QZDEw@mail.gmail.com> <CAPt1N1mK=Xgtt+aYa4ga8YqK2XYhCdQUPrwgVU8xstH+F_RAfQ@mail.gmail.com> <CAM5+tA9zhMpJ1s8keoL8eoEMej5tOM=-imXypHEreUa3wOrt5Q@mail.gmail.com> <2959747f-7b2e-ba95-64ae-95794fa8c4eb@gmail.com> <1854df9952924635afe5ac183421a046@huawei.com> <CAM5+tA95XJEEmz3jBNgNyHVdSDTPqE+A1nXogKEvnQHKTG=Mrg@mail.gmail.com> <8f918356-89ce-e2a1-a807-7d382568db0a@gmail.com>
From: Joe Maimon <jmaimon@jmaimon.com>
Message-ID: <623B83BA.7020100@jmaimon.com>
Date: Wed, 23 Mar 2022 16:31:54 -0400
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version: 1.0
In-Reply-To: <8f918356-89ce-e2a1-a807-7d382568db0a@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ze3d0Ake84446ghljXeNtZa1sNo>
Subject: Re: [v6ops] Thoughts about wider operational input
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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>
X-List-Received-Date: Wed, 23 Mar 2022 20:32:18 -0000


Brian E Carpenter wrote:
> Eduard, you wrote:
>
>> I am puzzled why ::ffff:0:0/96 has been treated as IPv4? Strange 
>> interpretation.
>
> Not at all strange. By definition (see RFC4291, section 2.5.5.2) that 
> is the entire
> IPv4 address space, respresented as an IPv6 prefix.
>
There is 2 thing at play. IPv6 packets with IPv4 embedded addresses as 
either or both source and destination.

And IPv4 packets with IPv4 addresses for both source and destination.

Perhaps they should be ranked individually.

Joe

v2.23.0 | Report a Bug | By Email