Re: [Sidrops] Some remarks on draft-ietf-sidrops-rpki-rsc-06.txt

Job Snijders <job@fastly.com> Mon, 23 May 2022 19:21 UTC

Return-Path: <job@fastly.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9F5C15AE09 for <sidrops@ietfa.amsl.com>; Mon, 23 May 2022 12:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIAbQFvJoeKB for <sidrops@ietfa.amsl.com>; Mon, 23 May 2022 12:21:41 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98C03C159A24 for <sidrops@ietf.org>; Mon, 23 May 2022 12:21:41 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id p26so20374346eds.5 for <sidrops@ietf.org>; Mon, 23 May 2022 12:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=wBuPrcEhHOafbL5QmjbQ6WqseTVo0idtIuX8hGDlotY=; b=N/UaGHf5g+GIQTcktY3rjryBmIJS4+fc4sRaBklYAuC/cMJhB4qs6p4jIX+4IzNBYt oqVf5akqCn2vQokyVJiG9WY/BDRK608mt5i/losd0ZxdFuamR9sWsmTA1BcbQN+JAi9g CJFZ71j/7xMgClgmo1CxD/tDGmsJo6LLUAiSU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=wBuPrcEhHOafbL5QmjbQ6WqseTVo0idtIuX8hGDlotY=; b=WuUc4Syb2nhQFhCQVG+rg35CFys7SsbbZVNzLEStrJ5Ky5e7pvG/U9CZyolSsIh+VF 3gR5pDlYjKhradT8iZufj2WY9TOBNVA5FIjflwXpD4bA6+2Buz7A9gkvMrRYbjWTtdUN jd49v9YPt4lrbHWY1sQOKAs9754NouiTG8t6zkgiC3LAK8AF3o2FePNIGLiiFCASuWjx QZH1Zg27vhljiEgFDjVxU83xreD0/fGaUigY+psVIFTc73NwVSadAcQEBH2r7bEEkeou Wz1qeP03MtfN9B8WnsxEMFk3H4LR8G6ezz7yRSslhuSDNLSlG27fdkVcXMt6aHBNPopx 77pw==
X-Gm-Message-State: AOAM532DiqHYFOOK5J4hS4xyZJCgQgjyGmV591ITAIR/2GXn2V4XfilV yDNND3KEEspzvaX0tmWkB30Ixn4zXvsD9g==
X-Google-Smtp-Source: ABdhPJwG1ONFHcQg3EJxp8j5Gr7ieUeupZLEQr+M0/3RbfmXLMNVIRrHwvOmY6q6RXuLbbXAHdpOPA==
X-Received: by 2002:a05:6402:2554:b0:42b:703c:513e with SMTP id l20-20020a056402255400b0042b703c513emr5135222edb.58.1653333699740; Mon, 23 May 2022 12:21:39 -0700 (PDT)
Received: from snel ([2a10:3781:276:2:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id kt1-20020a170906aac100b006fecb577060sm2123521ejb.119.2022.05.23.12.21.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 May 2022 12:21:38 -0700 (PDT)
Date: Mon, 23 May 2022 21:21:37 +0200
From: Job Snijders <job@fastly.com>
To: Theo Buehler <tb@theobuehler.org>
Cc: sidrops@ietf.org
Message-ID: <Yovewfu6pSVEH3/U@snel>
References: <Ynn5/yLvmB2LIBR0@theobuehler.org> <YofZkqdtlXb/z3sM@theobuehler.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <YofZkqdtlXb/z3sM@theobuehler.org>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/t5ENnZKnJGtm7YB2MVknBtQtfFA>
Subject: Re: [Sidrops] Some remarks on draft-ietf-sidrops-rpki-rsc-06.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2022 19:21:45 -0000

Dear Theo,

On Fri, May 20, 2022 at 08:10:26PM +0200, Theo Buehler wrote:
> This mail was stuck in the moderation queue for ~10 days. Most of it is
> obsoleted and has been addressed by draft-ietf-sidrops-rpki-rsc-07.txt
> 
> The one remaining point is this. I would still appreciate some
> clarification:
> 
> > 4. FileNameAndHash with optional filename field.
> > 
> > The draft only says that the filename field is optional. This seems
> > strange for a list of files whose hashes are supposed to be checked.
> > No rationale is given. I cannot find any text that explains what an
> > implementer is supposed do with a naked hash without corresponding
> > filename. Example use, a permission to ignore or an instruction to
> > report would all be helpful.

The FileName being optional in FileNameAndHash was done at the request
of some folks who envisioned workflows in which content is directly
addressed and not stored on a filesystem. An example could some kind of
challenge/response where only the RSC file is exchanged without any
additional files.

I think your suggestion to ask implementers to report naked hashes to
the relying party operator is a good one. We can add this in -08.

Kind regards,

Job