[sidr] slight whoops

Stephen Kent <kent@bbn.com> Sun, 24 July 2011 13:25 UTC

Return-Path: <kent@bbn.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4337521F8880 for <sidr@ietfa.amsl.com>; Sun, 24 Jul 2011 06:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.538
X-Spam-Level:
X-Spam-Status: No, score=-106.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHL3mqvjrsxz for <sidr@ietfa.amsl.com>; Sun, 24 Jul 2011 06:25:52 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEA821F8663 for <sidr@ietf.org>; Sun, 24 Jul 2011 06:25:52 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:52166 helo=[130.129.71.153]) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Qkygp-0004Hj-II for sidr@ietf.org; Sun, 24 Jul 2011 09:25:51 -0400
Mime-Version: 1.0
Message-Id: <p06240808ca50e4106010@[130.129.18.170]>
Date: Sun, 24 Jul 2011 09:25:49 -0400
To: sidr@ietf.org
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [sidr] slight whoops
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 13:25:53 -0000

I was reminded that not all objects in the RPKI repository are
CMS objects, e.g., certs and CRLs.

These are binary objects that do not start with an OID.

Nonetheless, since we have adopted rsync as the access protocol
for the RPKI repository, and since it deals with files and filenames,
using the filename to identify an object yype at the top level seems
appropriate.

Steve