Re: [Sidrops] proposed, revised text for Section 6

Job Snijders <job@ntt.net> Tue, 05 May 2020 21:58 UTC

Return-Path: <job@ntt.net>
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 3C5BD3A0BCF for <sidrops@ietfa.amsl.com>; Tue, 5 May 2020 14:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSOiBcoYpRkM for <sidrops@ietfa.amsl.com>; Tue, 5 May 2020 14:58:44 -0700 (PDT)
Received: from mail4.dllstx09.us.to.gin.ntt.net (mail4.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::192:26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB3463A0BD1 for <sidrops@ietf.org>; Tue, 5 May 2020 14:58:44 -0700 (PDT)
Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) by mail4.dllstx09.us.to.gin.ntt.net (Postfix) with ESMTPSA id A6A2FEE0117 for <sidrops@ietf.org>; Tue, 5 May 2020 21:58:43 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailauth.nyi.internal (Postfix) with ESMTP id E18F127C0054 for <sidrops@ietf.org>; Tue, 5 May 2020 17:58:42 -0400 (EDT)
Received: from imap1 ([10.202.2.51]) by compute3.internal (MEProxy); Tue, 05 May 2020 17:58:42 -0400
X-ME-Sender: <xms:kuGxXiCvQyUD6huUDsqO0jiE2_qVlkxjtOgXrBRDJa5KWaq9Fe9YzQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrjeejgdefudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedflfhosgcuufhnihhjuggvrhhsfdcuoehjohgssehnthht rdhnvghtqeenucggtffrrghtthgvrhhnpeegjeehtdeltdfgjeetjeegiedvfeevgfehff duteejheevuefgffeigeethfehgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehjohgsodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhith ihqddutdegjeeludehkeegqddvfeeffeekfedvtddqjhhosgeppehnthhtrdhnvghtsehs ohgsohhrnhhoshhtrdhnvght
X-ME-Proxy: <xmx:kuGxXjqCx1Gsqo-sUe1eq-g2RRUjlp9xGjW-oAap-N3E00v_HDb_gA> <xmx:kuGxXn8LRVqheGMpckWPvBt8WD-cjfwfEc1xBysHrmz_7FmxrDIfUA> <xmx:kuGxXqfpLfCUtgXO5ujF2de19gmBzNUB-a8hqvWdEH1KV6RlIlHfyQ> <xmx:kuGxXrGobEXA7xhQqgFluorVxfOaO6gAaKGBAn_8odWFAoaIJc5onQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6E7A6C200A6; Tue, 5 May 2020 17:58:42 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-351-g9981f4f-fmstable-20200421v1
Mime-Version: 1.0
Message-Id: <c1f51d28-e19d-41b2-ad23-f96973fb7598@www.fastmail.com>
In-Reply-To: <7355e27e-ee58-f84b-4fed-9674ae542d94@verizon.net>
References: <557f0928-c7b1-4b8d-b3b6-078733f7ef8a.ref@verizon.net> <557f0928-c7b1-4b8d-b3b6-078733f7ef8a@verizon.net> <CAKr6gn29namLq5qq6WhhveT+6r7vC8W9SmwPcNP_un93GWmP9A@mail.gmail.com> <7355e27e-ee58-f84b-4fed-9674ae542d94@verizon.net>
Date: Tue, 05 May 2020 23:58:21 +0200
From: "Job Snijders" <job@ntt.net>
To: sidrops@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Oq82CQXXHeCAtQTUPcNLEFauyC8>
Subject: Re: [Sidrops] proposed, revised text for Section 6
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 05 May 2020 21:58:46 -0000

Dear Group,,

On Tue, May 5, 2020, at 21:52, Stephen Kent wrote:
> > I just want to note that while I think you made a logically consistent
> > choice, I do not agree with its intent, in as much as I believe cached
> > state could be used to construct the valid state which the manifest
> > and CRL declare.
> >
> > So, I think you drove to a harder place than I intended. But, I accept
> > this is a choice, and a strong choice.
> >
> > I suspect I am in a minority of one on this. I would not seek to
> > impede a group decision driving to a more narrow constrained
> > definition.
> 
> I believe Job made a good argument supporting your observation, and we 
> can revise the text to take advantage of the cached state. I will note, 
> in passing, that this can introduce variances in local processing based 
> on local cache loss and/or differences in cache refresh timing by 
> different RPs. But, if everyone is comfortable accepting the potential 
> variance, I'm happy to proceed.

About the next period of time: yes, Stephen, please proceed to write down your thoughts. I would like to read your messages (through this mailinglist). I can't compensate you for your efforts with a monetary currency, but I can commit my attention to what you write.

For what it is worth - as member (and dependent) of the community around OpenBSD rpki-client, I observe people are holding the various pieces of the puzzle up against the light in various direction and positions, trying to see how how to align (if possible) the implementation of our RPKI cache software with the spirit of George's observation. Test balloons in the form of POSIX.1 patch(1) files are shared within that community. And it appears it'll be a multi-week effort to resolve the puzzle in a way that all people involved would want to run in production on their EBGP routers.

As SIDROPS are not in an easy working space: the timezones differences are really hard, emails might not arrive, reliable distribution of audio from interim meetings seems challenging, and we all speak an approximation of a common language. Receiving messages in simple English helps improve my participation in this process.

Stephen, my request to you: share directly with the working group what you perceive as the space and "variances", and make strong strong suggestions about the specific single path/vector you perceive as most optimal through the space, and I look forward to comparing notes and observations.

Kind regards,

Job