Re: [Sidrops] mft version field issue (Was: I-D Action: draft-ietf-sidrops-6486bis-05.txt)
Job Snijders <job@fastly.com> Sat, 10 July 2021 19:57 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 D5B7C3A0772 for <sidrops@ietfa.amsl.com>; Sat, 10 Jul 2021 12:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 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, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.com
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 uHRt304nAFKG for <sidrops@ietfa.amsl.com>; Sat, 10 Jul 2021 12:57:41 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85C803A0809 for <sidrops@ietf.org>; Sat, 10 Jul 2021 12:57:41 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id l24so19695632edr.11 for <sidrops@ietf.org>; Sat, 10 Jul 2021 12:57: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=XlFdaA7B1X2siRWzvp1Exdj6sy3TdxqBSw4qBuBhWpc=; b=OP2ceJKPPSmQWtdSZDiC43+CncoAOsTvw+1E8l2xfiMt7nUpcg2+ZRTylJ9Zjdu7oj k3G7ZYPuAK6ufYU+jlfaS8fjkhjO2pIGiOUEoP52s17fhaLRKFSaUfp80sea48S+u+07 eKYEGzGMvMZU38MQFqQAcqbKCh8KW+FdReuhU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=XlFdaA7B1X2siRWzvp1Exdj6sy3TdxqBSw4qBuBhWpc=; b=f8UbGeMhfH03nzeTlxRbcwF1FksOVBJg7/OZNlaaze5gdOPimIssq9lkQQlRkkW+I6 MmKXNVkr5Bw+YiLYnJZpJOolKBCf8sL0EzS2CdN7DJewTxY2JSv6cyn7+xFIHw87ek1u 9GswnjH9vjWrTuvC6i+f5E7TfavLqmEGHLM0YoyCNlg1yYh629OL5j6rqf9tZAceW99K B8dYVRzSWoHQycaePgq+8pFaK1aqQkHMSQhzsV7k1r1MslmHSolMvI7a3ZHsL8pVvpPN 12sqovY56gwgl0umoOueQExetnUrK2tZ46Eug6Q72E24/ep6mDKXCISMdVNpGQpLz6GT 5+cA==
X-Gm-Message-State: AOAM532PX9Waxy9wO96FucMHIOOpUoKD1pMen/G1ICyFsbiUpXilyI3J o6PZmBHTBSlYmA4k0DFlwXboGdmidhh1Qg==
X-Google-Smtp-Source: ABdhPJwuO0iLyVdWFXuQeLR4J13aknvHpsrwUholH/jq/OpnZrid0gGmt3thVtzdJ9DCwBRZpyDqoQ==
X-Received: by 2002:a05:6402:5212:: with SMTP id s18mr21830016edd.370.1625947054763; Sat, 10 Jul 2021 12:57:34 -0700 (PDT)
Received: from snel (mieli.sobornost.net. [45.138.228.4]) by smtp.gmail.com with ESMTPSA id ch27sm3413004edb.57.2021.07.10.12.57.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 10 Jul 2021 12:57:34 -0700 (PDT)
Date: Sat, 10 Jul 2021 21:57:02 +0200
From: Job Snijders <job@fastly.com>
To: Russ Housley <housley@vigilsec.com>
Cc: Stephen Kent <stkent@verizon.net>, sidrops@ietf.org
Message-ID: <YOn7jt+Vx7oM+cpc@snel>
References: <YOnj0sIs8ecU7uCG@snel> <A848C6DC-C20D-4EFC-9D9B-B7D2A33E96AA@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A848C6DC-C20D-4EFC-9D9B-B7D2A33E96AA@vigilsec.com>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/CDrwMyp3dFyzHHCfNG6iouRYjxQ>
Subject: Re: [Sidrops] mft version field issue (Was: I-D Action: draft-ietf-sidrops-6486bis-05.txt)
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: Sat, 10 Jul 2021 19:57:51 -0000
On Sat, Jul 10, 2021 at 03:43:08PM -0400, Russ Housley wrote: > If you try to decode, and it fails, then the Version should tell you > what ASN.1 module was used by the originator in order to properly > decode it. All of the RPKI-related CMS content types started with a > Version of zero. Yes. So when a RP decodes it and fails, the expectation is that the RP will immediately upgrade to a newer version of their RP software? If a CA jumps to the new version 'too soon', the CA risks losing their ability to inject VRPs into the routing systems of the RPs. At what point can a CA know or expect that sufficient RPs in the field are able to decode their objects if they choose to use the new version? Kind regards, Job
- Re: [Sidrops] mft version field issue (Was: I-D A… Job Snijders
- Re: [Sidrops] mft version field issue (Was: I-D A… Job Snijders
- Re: [Sidrops] mft version field issue (Was: I-D A… Stephen Kent
- Re: [Sidrops] mft version field issue (Was: I-D A… Russ Housley
- Re: [Sidrops] mft version field issue (Was: I-D A… Job Snijders
- Re: [Sidrops] mft version field issue (Was: I-D A… Russ Housley