Re: [Sidrops] Reason for Outage report (was: Re: ARIN RPKI Service Impact - 12 August 2020 - manifest issue - resolved)

Martin Hoffmann <> Wed, 26 August 2020 18:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 963CC3A003F for <>; Wed, 26 Aug 2020 11:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qo-GAclgsOAO for <>; Wed, 26 Aug 2020 11:24:46 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E55633A0044 for <>; Wed, 26 Aug 2020 11:24:45 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTPSA id 17CA01933F; Wed, 26 Aug 2020 20:24:43 +0200 (CEST)
Authentication-Results:; dmarc=none (p=none dis=none)
Authentication-Results:; spf=none
Date: Wed, 26 Aug 2020 20:24:42 +0200
From: Martin Hoffmann <>
To: Job Snijders <>
Cc: John Curran <>, "" <>
Message-ID: <>
In-Reply-To: <>
References: <> <> <>
Organization: Open Netlabs
X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Sidrops] Reason for Outage report (was: Re: ARIN RPKI Service Impact - 12 August 2020 - manifest issue - resolved)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Aug 2020 18:24:48 -0000

Job Snijders wrote:
> The current versions of routinator and ripe ncc's validator have weak
> (lacking) support for manifest handling, there are other issues in
> both softwares that don't yield errors where they should yield errors
> related to manifest handling. Neither implementation handles
> manifests correctly at the moment, so neither software currently can
> be used to confirm the correct publication of manifest related
> data. :-(

To the best of my knowledge, Routinator and the RIPE NCC RPKI Validator
handle manifests according to the specifications laid out in the
relevant standards track IETF documents. I assume that you are referring
to your assessment that all objects published by a CA should be
discarded if any inconsistencies are discovered. While such behaviour
is certainly acceptable under the current specification, not doing so
does not constitute incorrect handling of manifests.

Given that this topic is currently discussed in this very working
group and there wasn’t outright consensus on how software should behave
in these cases, it seems only prudent to delay modifications until
after such consensus has been achieved.

If you have information about other issues these software packages
have with regards to manifest handling -- as you seem to imply there
are multiple issues --, I am sure the maintainers would like to hear
about them.