Re: RFC 9226 on Bioctal: Hexadecimal 2.0
John Levine <johnl@taugh.com> Sun, 03 April 2022 16:15 UTC
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id AFCF43A1CAD
for <ietf@ietfa.amsl.com>; Sun, 3 Apr 2022 09:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.862
X-Spam-Level:
X-Spam-Status: No, score=-1.862 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001,
T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=iecc.com header.b=uxFcJDZa;
dkim=pass (2048-bit key)
header.d=taugh.com header.b=YoFIoV4p
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 et9026qEM_x8 for <ietf@ietfa.amsl.com>;
Sun, 3 Apr 2022 09:15:21 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com
[IPv6:2001:470:1f07:1126:0:43:6f73:7461])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 5433C3A1CAC
for <ietf@ietf.org>; Sun, 3 Apr 2022 09:15:21 -0700 (PDT)
Received: (qmail 44409 invoked from network); 3 Apr 2022 16:15:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com;
h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness;
s=ad76.6249c817.k2204; bh=sfKIMJTJTuTNrysIFjc5QsZO2IXPQzyMMuZmakVnP4c=;
b=uxFcJDZatVXzcXIP898V+t1gCWdRaeB8Mo4NwnZ1LGoPi0JoTz5fTmW5k3q5R8njq9xgleb8jeyWVzBFj2rgbvQV5ztzAwx5vhdIQu+PpPRvkm8CMVWUHozdjh5D8Tdjq53cxR70OAljT+xfxPuNDqJ3KUeeCz49vhPELkcVfDY3w3CpzWvChRl+0SXEFxjfGH1d7D6EHuUpiIzMEB544a11RWOIvyU1wQ2vcFW83jROZzx/G/V0gYMgJL4rmU/Zgq0E9/p1am5cU4c20iNleopP7m/kKq8IOd4A5XVV98v96xWYjUvuD5pGVmoanbRQZzLf+Fk/Oykmas3IlnO4Fg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com;
h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness;
s=ad76.6249c817.k2204; bh=sfKIMJTJTuTNrysIFjc5QsZO2IXPQzyMMuZmakVnP4c=;
b=YoFIoV4p7V9VW0Db8wsIjjewonrhxgGMwqY+3yiybfcLdcdnkAYyP2q7e/ddifFrYXr4PXOz/aalQhiubT7h5DewHO64UEFZk9pdzbG0ab1hyPcYeJUTVOH1nyCq7oZXzwXO2iBGuAWwalBM+eTjtzYPDJKWPz77Di059BaEdgWrI781boMWb8Fh5ghoGy27twYEIa/1w8yX58WAVkLfWr21l/o1CZ9C9AXuXQswJYLGDmFkBW93PESg+9GUtDyVdZebJmsRpbEwrHK//iDnw8OdLd2lRZB6Oyx+MykDYrEOe3/Kavf3qWCgBUHkzLVMLybE7auF9uSzEx/jmb3waw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170])
by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170])
with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6;
03 Apr 2022 16:15:18 -0000
Received: by ary.qy (Postfix, from userid 501)
id 4E2D13A4B44D; Sun, 3 Apr 2022 12:15:17 -0400 (EDT)
Date: 3 Apr 2022 12:15:17 -0400
Message-Id: <20220403161518.4E2D13A4B44D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RFC 9226 on Bioctal: Hexadecimal 2.0
In-Reply-To: <24f08b06-8767-587d-6327-21706da044a9@gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uQmDiHdVS9QEjs6MVNadlyQFHdU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
<mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Apr 2022 16:15:30 -0000
It appears that Brian E Carpenter <brian.e.carpenter@gmail.com> said: >On 03-Apr-22 12:21, Michael Richardson wrote: >> >> I wish that more RFCs had such well thought out Security Considerations. > >They are incomplete. There is a whole world of hurt if one considers >IPv6 addresses. What are we to make of a prefix like 2cf2::/16 ? >If we assume it's bioctal, it is really 28c2::/16 in hex. But if >we assume it's hexadecimal, it's really 2cf2::/16. > >That sort of confusion between IP prefixes could be quite an >operational problem and lead to all kinds of exposures. It means >that auto-detection of bioctal vs hex is generally impossible. Calm down, nobody uses IPv6 so it isn't a problem worth worrying about. Helpfully, John -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
- Re: RFC 9226 on Bioctal: Hexadecimal 2.0 Michael Richardson
- Re: RFC 9226 on Bioctal: Hexadecimal 2.0 Brian E Carpenter
- Re: RFC 9226 on Bioctal: Hexadecimal 2.0 John Levine