Re: [Sidrops] About the use of manifests (follow-up from Apr Interim meeting)
Job Snijders <job@ntt.net> Sun, 03 May 2020 20:01 UTC
Return-Path: <job@instituut.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 60FE63A11BF for <sidrops@ietfa.amsl.com>; Sun, 3 May 2020 13:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 F-642V292CEM for <sidrops@ietfa.amsl.com>; Sun, 3 May 2020 13:01:16 -0700 (PDT)
Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) (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 0EE513A040B for <sidrops@ietf.org>; Sun, 3 May 2020 13:01:15 -0700 (PDT)
Received: by mail-wr1-f47.google.com with SMTP id d17so18388821wrg.11 for <sidrops@ietf.org>; Sun, 03 May 2020 13:01:15 -0700 (PDT)
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=rD/IBqI8TL3NJrjBhCPhazMd/6Fbry4q6pOUzSY2RHY=; b=h2G49AKh3BUsOz6XdY6z0P/jwfZ74RQyFy+1hKoeHA+suYWNv15x1c8OCRW05dhree QOovYTsZSt5gNH9PJun3bpk4VoZ5jeeIL7FtZQshvf7Bq8GPDcB+9y01/oIM5AjCNEA2 5KghT6IxMbfRCVhvZ/+pm422wVGJl0hiuSHeyHbqPALLu47adUuoeGC+TYfy6+HBQ7N/ fBqfM1QO/Mqy4SWxahjMGhrQiLHPAAmhhWkn5aDm6Pl8t0jBG+UiUkfamvUKhue+QbYu mVjgpHRSOJt/td1scBLcXoVkktZIab73GmQRT7nvRl1qqE7/iB4zPKQdtoVVmY1KH85B K4Ww==
X-Gm-Message-State: AGi0PuYl9sgjSiqe51nTbvBXhqeCar/sDP8zJIb2n3DU0rjLoraix7uW HmqpXKLuoZmrPK0rwD1YU6eytMYom8M=
X-Google-Smtp-Source: APiQypK8CdYKN9/P4T4FXrHoNwqHj4CeVa6bEqDvtrxrDzO7T3S4yXiEl7Ds95Pl4k7AAo2imAFPXg==
X-Received: by 2002:adf:82ac:: with SMTP id 41mr13053861wrc.110.1588536073899; Sun, 03 May 2020 13:01:13 -0700 (PDT)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id m188sm10254963wme.47.2020.05.03.13.01.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 03 May 2020 13:01:13 -0700 (PDT)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id b1f3eeec; Sun, 3 May 2020 20:01:12 +0000 (UTC)
Date: Sun, 03 May 2020 20:01:12 +0000
From: Job Snijders <job@ntt.net>
To: Stephen Kent <stkent=40verizon.net@dmarc.ietf.org>
Cc: sidrops@ietf.org
Message-ID: <20200503200112.GI57581@vurt.meerval.net>
References: <20200503190202.GD57581@vurt.meerval.net> <60c43db2-030e-723e-177c-13cc14758c64@verizon.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <60c43db2-030e-723e-177c-13cc14758c64@verizon.net>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/txBApByUQd8t0l3PBcKeml4_arA>
Subject: Re: [Sidrops] About the use of manifests (follow-up from Apr Interim meeting)
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: Sun, 03 May 2020 20:01:17 -0000
On Sun, May 03, 2020 at 03:56:22PM -0400, Stephen Kent wrote: > Yes, Section 6 of RFC 6486. > > I believe that most of the changes will arise in 6.2, 6.3, 6.4, 6.5, and > 6.6. The current draft (draft-spaghetti-sidrops-rpki-manifest-validation-00) replaces Section 6 entirely. I don't know if that aligns with IETF etiquette and it has to be done paragraph by paragraph, but I hope this helps clarify our thinking. > I'll submit some proposed edits next week. Thank you! Edits welcome in unix patch format, in natural language in email, whatever is easiest. Kind regards, Job
- [Sidrops] About the use of manifests (follow-up f… Job Snijders
- Re: [Sidrops] About the use of manifests (follow-… Stephen Kent
- Re: [Sidrops] About the use of manifests (follow-… Job Snijders
- Re: [Sidrops] About the use of manifests (follow-… Stephen Kent
- Re: [Sidrops] About the use of manifests (follow-… Christopher Morrow
- Re: [Sidrops] About the use of manifests (follow-… Randy Bush
- Re: [Sidrops] About the use of manifests (follow-… Christopher Morrow
- Re: [Sidrops] About the use of manifests (follow-… Stephen Kent
- Re: [Sidrops] About the use of manifests (follow-… Christopher Morrow
- Re: [Sidrops] About the use of manifests (follow-… Stephen Kent
- Re: [Sidrops] About the use of manifests (follow-… Christopher Morrow