Re: [Cbor] changes to draft-ietf-cbor-network-addresses-01.txt

Carsten Bormann <> Mon, 08 March 2021 07:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 100CE3A273D for <>; Sun, 7 Mar 2021 23:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4dVedcnQauKM for <>; Sun, 7 Mar 2021 23:53:03 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 229973A2739 for <>; Sun, 7 Mar 2021 23:53:03 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4Dv9Yn0GpzzyTN; Mon, 8 Mar 2021 08:53:01 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
From: Carsten Bormann <>
In-Reply-To: <30430.1615160268@localhost>
Date: Mon, 8 Mar 2021 08:53:00 +0100
Cc:, Brian E Carpenter <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <30430.1615160268@localhost>
To: Michael Richardson <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [Cbor] changes to draft-ietf-cbor-network-addresses-01.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Mar 2021 07:53:06 -0000

I think prefixes and addresses are completely separate use cases.

There is rarely a point in suppressing trailing zeroes in an address.
We shouldn’t burden implementations to cater to this 0.4 % case (probably less in practice).

Prefixes are different, and they should indeed always be tail-cut.
(They are usually /64 or shorter, so there is a real win.)

We could imagine an alternate world where IIDs are carefully chosen so that actual addresses have as many trailing zeroes as possible.
But that’s not what happens today.  If we were to compress inner zero runs (as in “::”), we’d need to give the byte position where that happens (the length would be implied by the length of the remaining byte string).
I’m not proposing we cater to that.

Grüße, Carsten

(The /24 IPv4 example in the draft is wrong.)