[Sidrops] passed nextUpdate in CRL and manifest

Taiji Kimura <taiji-k@nic.ad.jp> Fri, 30 November 2018 07:30 UTC

From: Taiji Kimura <taiji-k@nic.ad.jp>
Openpgp: preference=signencrypt
To: sidrops@ietf.org
Message-ID: <e5053f0a-c6a6-c3a2-aa9c-d10f3084e40e@nic.ad.jp>
Date: Fri, 30 Nov 2018 16:30:26 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/dg7CG-kbBGQkUTgZloC8oGdNSfA>
Subject: [Sidrops] passed nextUpdate in CRL and manifest
Precedence: list

Hello,

CRL and manifest issued with JPNIC's CA had been passed their nextUpdate
in Nov 10.
Sorry for your inconvenience.

# JPNIC is operating RPKI CA (as a testing service) for resources
# allocated from APNIC.

The CA's repository (rpki-repository.nic.ad.jp) has been kept.
Resource certificates had enough time until their expiration. But
the CA (issuing server) located in different building had been affected
from scheduled power outage. CRL and manifest (6 hours as nextUpdate
for both - is the time for recovery.) had not been updated during the
outage. ROV results should had been "Not Found" for 11 hours.

The nextUpdate value was modified already as enough time for our service
recovery. Some monitoring functions on object's validity will be
reconsidered because this issue was notified by a user.

 -- kimura taiji

[Sidrops] passed nextUpdate in CRL and manifest Taiji Kimura