IETF Logo Mail Archive

Re: [Sidrops] WG Adoption call for draft-madi-sidrops-rp-adoption

George Michaelson <ggm@algebras.org> Wed, 11 October 2017 06:28 UTC

Return-Path: <ggm@algebras.org>
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 0F9D9133064 for <sidrops@ietfa.amsl.com>; Tue, 10 Oct 2017 23:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.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 SnsgSuiA9Mle for <sidrops@ietfa.amsl.com>; Tue, 10 Oct 2017 23:27:57 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 A6CAF133052 for <sidrops@ietf.org>; Tue, 10 Oct 2017 23:27:57 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id w45so472156uac.3 for <sidrops@ietf.org>; Tue, 10 Oct 2017 23:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=koVcSMppGJZ1HSio347514F8YInlqcyU2czA7UbYwr8=; b=WQD/m7p7NPdgnk1y6NJrRDOos6qxX60VtEDfA/+RY7pebPoLA6mhjtiRyMmIiVWFpU d3CZEyfU8bhT/6KrXW+etB2aI4csyvHs3kOZIU87HTTo7hai8dHmTkg4Z8zrf93u2TT4 UpY600FCojIIhTzdRZB4lI8mR2UpNlYJw2mT+OzyO4KK4W3VafOgvJ30FqHbdgmEnZfr EL8NWd2zpStMs0+z+jS+lv65iE7sKgbYR4Pwh66zV9wxwbSJIdjHVyKTpyV9prok1zvZ lhAIzLkShZyz95VejjU5C3k4oLlRV9EvSh/gsk/OoRqXTBqEbHl8QgU4G6OCWd/UrIdy 4Elw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=koVcSMppGJZ1HSio347514F8YInlqcyU2czA7UbYwr8=; b=BoN4nxPMCCIpIHWL7IkKnzSR19BCCssAGf3faLr2PT3xNM0v023zjM3StY1fhPRHHG 1UDxEjdysWWETHo/cG3h3TrJQN1f8cECmtJIrYStQhYKprcKQOF49IXjL+C2SvOIp90h tGci1ZZgcidHw2nfkUd5P4sCttlstQ/tnvNoI2wraepS9dNMBDvD+Bof7wGv0tXSEGQR Gh3UsbwSSGdbI9+LvCaUVOSnZBrtwJZBrI5QwoHron0OAbd1wMeYlXSmP4O+GChU+hbI MttipZ9tQJNbyQdmGomNDA42UpRmb61XL5bQFxjAl4b/llSs+bfbUY2ewXf1uEmOUdBE lO2w==
X-Gm-Message-State: AMCzsaWhnRg+C1NIGrEbxKFozoaC+LBJJ51dPnsmLXulHNG9UrSWQe85 HP0aMS1TsCaOTdOpTkUIrFRr592PPZxKfRK6whKgLEb2
X-Google-Smtp-Source: AOwi7QDcvz5YYPXUx6zDJDWXu5nOQ3xcaq9YJmSQEma5uz8pkRoE8WSlMLfGbsKC9DgjbyZ4LzJN35GA7SLft1mny4w=
X-Received: by 10.159.63.15 with SMTP id h15mr5481665uaj.156.1507703276143; Tue, 10 Oct 2017 23:27:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.91.93 with HTTP; Tue, 10 Oct 2017 23:27:55 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:e847:5919:d977:cadd]
In-Reply-To: <CB3C3CD7-AE5E-4267-9E56-C55229D8BADA@arrcus.com>
References: <CB3C3CD7-AE5E-4267-9E56-C55229D8BADA@arrcus.com>
From: George Michaelson <ggm@algebras.org>
Date: Tue, 10 Oct 2017 23:27:55 -0700
Message-ID: <CAKr6gn2unMCXn+3nOHOtv39XYCEbj=c3MoqBhZXAkVDYL20uLA@mail.gmail.com>
To: "sidrops@ietf.org" <sidrops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/IPOVdszzdzFMmIzFyJVU339ncAU>
Subject: Re: [Sidrops] WG Adoption call for draft-madi-sidrops-rp-adoption
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 11 Oct 2017 06:28:00 -0000

We have a tradition in the IETF (as I understand it) of writing
clarifying documents to bring together the normative from the
discrete, different places it lies in, and therefore clarify what
must, must not, and may be done and the implications in each case.
It's been done in other contexts. Why not here?

So I have no problem with the WG taking on that kind of work. I don't
"do" routing and I've never written relying-party code, I don't think
my review is going to add much because I lack the critical eye in that
regard.

Life is confusing enough without having open questions about the
canonical reading of a bunch of disparate documents written by
different authors at different times.

-George

On Tue, Oct 10, 2017 at 10:05 AM, Keyur Patel <keyur@arrcus.com> wrote:
> Hi Folks,
>
>
>
> The authors have requested SIDROPS working group adoption call of
> draft-madi-sidrops-rp-adoption, “Requirements for Resource Public Key
> Infrastructure (RPKI) Relying Parties”. Please send your comments to the
> list.
>
>
>
> This adoption call will conclude on Oct 25 2017.
>
>
>
> Regards,
>
> Chris & Keyur
>
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>

v2.23.0 | Report a Bug | By Email