[Sidrops] [WGLC] draft-ietf-sidrops-signed-tal - ends 18/Jun/2020

Christopher Morrow <christopher.morrow@gmail.com> Thu, 04 June 2020 20:22 UTC

Return-Path: <christopher.morrow@gmail.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 5A9F63A0F29; Thu, 4 Jun 2020 13:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5YHs_fLjb0Xy; Thu, 4 Jun 2020 13:22:42 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 02F763A0F26; Thu, 4 Jun 2020 13:22:42 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id w3so7534778qkb.6; Thu, 04 Jun 2020 13:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=YzSd+1vWbUVl2tC0wjxH2VwL+FetJ38XP1R59kQPPSE=; b=Ar8q1ZO1fSl3n4YH4ctP4p43IKbScEPfQRe5vX1NITudAKd/9KHogtZg0wLhl6fOnX 3UBu7VoBBfstukDhHsiRlhHqmWQgOP4++MsKmERPFISVcCha1sAEe4Ld7qcagauahhvX VwFhcfW0o4QqUwBKfBki6tFEPArzw9Hs/9lO7d8rIOu9YFecbdDlJFETFIhOcGuMJA/A XuqH7hoSkBoHPURvAz4McldlH4NtQqwVat4gmvI7km8klVoIKsbpV6rhGcN7Zn6+drTZ cq/z0F9aPG0LkLMSttxp8Yp+YUijBrlmJ1zdNp3PpUnTGYH/P4R1qR12dVSsd4CMC/CR caXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=YzSd+1vWbUVl2tC0wjxH2VwL+FetJ38XP1R59kQPPSE=; b=IUtioPyp6hFbPlDflzRvzMMM2izQ2HJEqHVoU+Mt/UIREqOw6u46IfEdH8yapKu1Zb 6H3BC9HbcbAIykKGjYZvmHfPGrewa4wgnfGd5Z2aIeMeSOiaMqkpqyYfkvofnTlQj/ES jDwdeNkRL3BrFM64CLAWd8GdH0aCZiUZdc2Ai1ReQmEanc1Chnz/kihsutMs8+E5U7CM uK3wmqlKwW1MRiDl0mupG4bINiQjEwfhw0BLNUAI8Mk6Qio6mctsKo+87PIvHFomCw4/ QvrNoCx6hHPLTACb0VZMTDGlqsmGJUosCjYe3zpIkBW76nO+faSAk5x2gc714ShyfkD3 J1qA==
X-Gm-Message-State: AOAM533cYYg+auYMVg1WTk07tQh+2cudNhw+bJXiijpUVHVoAyztHBaX lF6HpHTOPrvQe8mAyuyxB644tHZjNBaG1wKAfCG1rvC+bIU=
X-Google-Smtp-Source: ABdhPJxqDkNx7szeA2S1T0ln6nfp7rgaDxm4NvJO2SZ4vNC4aw30qszPy1dFj9N2hYpAEjS3TSOtYRQFelE3AXeLU4Y=
X-Received: by 2002:a37:48c8:: with SMTP id v191mr6878056qka.268.1591302160848; Thu, 04 Jun 2020 13:22:40 -0700 (PDT)
MIME-Version: 1.0
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Thu, 4 Jun 2020 16:22:30 -0400
Message-ID: <CAL9jLaZLYJYkSZneO6mWizF3bY1KAb9-JKaj7FKhZE4dhAGLrA@mail.gmail.com>
To: SIDROps Chairs <sidrops-chairs@ietf.org>, SIDR Operations WG <sidrops@ietf.org>, sidrops-ads@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/rxHIDXUYXM4o_4NhlqvxWuchPhc>
Subject: [Sidrops] [WGLC] draft-ietf-sidrops-signed-tal - ends 18/Jun/2020
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: Thu, 04 Jun 2020 20:22:44 -0000

Howdy WG folks!

we have had a few discussions and starter-steps for:
  WGLC - draft-ietf-sidrops-signed-tal

I think we never officially WGLC'd this document.
I think it'd be terrific if we could get folk to re-read, and
comment/assent/dissent (politely!:) ) on this topic now.

Please have a read, the Abstract is thusly presented:
  "A Trust Anchor Locator (TAL) [I-D.ietf-sidrops-https-tal] is used by
   Relying Parties (RP) in the RPKI to locate and validate a Trust
   Anchor (TA) CA certificate used in RPKI validation.  This document
   defines an RPKI signed object for a set of Trust Anchor Keys (TAK),
   that can be used by TA creators and publishers to signal their set of
   current keys and the location(s) of the accompanying CA certificates
   to RPs, as well as changes to this set in the form of revoked keys
   and new keys, in order to support both planned and unplanned key
   rolls without impacting RPKI validation."

and I'd like to conclude Jun 18 2020 if t all possible :)
Of course, if the authors are: "Yo! this is not ready! back to the
easy-bake please!" that's also cool, just trying to force conversation
and forward momentum I am! :)

-chris
co-chair-frog-smasher