Re: [babel] HMAC Key rotation key format (was ripemd)

Markus Stenberg <> Tue, 04 December 2018 18:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0EEAF130F29 for <>; Tue, 4 Dec 2018 10:33:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vMJUQIMZIBNd for <>; Tue, 4 Dec 2018 10:33:47 -0800 (PST)
Received: from ( [IPv6:2001:67c:1be8::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A35C7130ED9 for <>; Tue, 4 Dec 2018 10:33:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=20161220; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=HnrSqaSPSuRlh1bSlA/uEZy5Nl6wJIlNOiJK8vVUIvc=; b=szU7tDUjQpXC0nmZYJeOg84Pqk fWD/uTFBL8P4wnJOCKIIpbmb47CbD5PkKJ1JktdnSwAKUTGyaw6D+9aDNX0IjcXqs1Ibd1ucJpxF+ MshpLMvBRjl097+a8S5LrNxJeVXkBA0BZahlZBjSGPcr2XmVv7sa3a35dLp8y76sX1yQCl0/lvo1e fIVTl8fsPS6fTR+hF4SIZyvhvhUmw545kb81Naq0OC/UGxmKqlWlV1TqNg5H8Z5FqnNwEs6CoqaPW 9HekGdMJ8nco5TdmTIAS/KAHkAohA963mnOIf5sfL/3zUij9vB1N8nXDubXqnEmpJzlBtaU8DSf3t /yVGx36w==;
Received: from ([] helo=[]) by with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <>) id 1gUFVs-0004Zu-AW; Tue, 04 Dec 2018 20:33:40 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Markus Stenberg <>
In-Reply-To: <>
Date: Tue, 4 Dec 2018 20:33:39 +0200
Cc: Juliusz Chroboczek <>, =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <>, babel-users <>, Babel at IETF <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <>
To: Dave Taht <>
X-Mailer: Apple Mail (2.3445.101.1)
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Subject: Re: [babel] HMAC Key rotation key format (was ripemd)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Dec 2018 18:33:50 -0000

For interconnected domains and whatever, I would rather just use DTLS with relatively shortlived and auto-renewed certs (real-time revocation is hard to do if you are authenticating routing - chicken 'n' egg problem; one alternative is of course some sort of manual blacklisting if you want to go with long-lived certs).  

If HNCP is in picture, DNCP trust based consensus model is also an option - with it, (self-signed) certificates can have long lifetime as their usefulness is determined by consensus of nodes -> as long as there's only few compromised nodes, you can blacklist them in real time if you control the rest of the nodes.