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

Christopher Morrow <> Thu, 16 July 2020 17:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3F7003A07F0; Thu, 16 Jul 2020 10:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R1ylZ_xqqqCE; Thu, 16 Jul 2020 10:27:49 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D7D6B3A05E2; Thu, 16 Jul 2020 10:27:35 -0700 (PDT)
Received: by with SMTP id e3so3052573qvo.10; Thu, 16 Jul 2020 10:27:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=r1iz3yJ42BVX1n4nHzdpo3IHvp7yyJ8sjXkaFj7j0yc=; b=jwUWi9fpq8/GAOtRxHOK6c9okJFg8Lesej90BZmbfQmefhX8eilU+5RqOjbxJSp9i7 nUY9R3lcZbNEnkZUbIAly1h+reiKt13Fuml/BhH3Al02ylCZK2WVZllE4XVNzL6M1cwS CaXIZXOF0rvXMRlB1G9zzWCHlgAYt2HbkAA/0jl02LptSuOouTT3TRxxYfp1+i7NO1Ns PfRjUdrn852FEklZ0OmYju8R5Ylmt3AfXuJ1999fWMdOSVs2wnNSbGt2bK4ktKsG8DgB Jcay/5KmffR3RV5fmcJzxyuJP59CdVxgXO97yQnaD9KD7xC5jFCjaY5g1sifKjZpcNsp hBuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=r1iz3yJ42BVX1n4nHzdpo3IHvp7yyJ8sjXkaFj7j0yc=; b=Z73/s/wj/qFEFYsgJ6f/nMTysBKKSrc75rK0uafcBAr6NAE4SDpLzZqLBK+VReu023 kizVaBMjdntb8M2KDS1X4snFJuSqCD6PDybewvuzdrTp+CwEwziOhylHcro2ziIjFzxk CFgljX15VOpLYkw62a/iC2c+XENCEhBBCZLVGhyBPEg8/yfXrYIhXRLDBvAqrysAwefj Vj9As9q2cwZ8E+b/EQSGhDnHDUSuRaAveKUnwGGpCuOTNYFd3XDDWMMdZZ/QNLbFfWXc H2hYrFTAUzu/PXsCfKSj0nBzJrAU0xpbZqQ2MYQOl3nl5v9V+5Ff52Epnk2lK56C5h1N E7EQ==
X-Gm-Message-State: AOAM533qfj3jrkasEo2n60WcYKiPWt3c4EZevi8fuwoRiK6+HzchsCYm 371fOg7mJMgWDGPXkNuHKhxMK1W+uLSVAkPOhz5To0xK
X-Google-Smtp-Source: ABdhPJzwMeB9Brk4tCWjjMUqB3rCHhB6lmVc+myTSq6+H3LRo/C1gSswCLFhvH4ht4OhFhJwA98hTCydi4wcG7kvDWk=
X-Received: by 2002:ad4:458a:: with SMTP id x10mr5276070qvu.223.1594920454576; Thu, 16 Jul 2020 10:27:34 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Christopher Morrow <>
Date: Thu, 16 Jul 2020 13:27:23 -0400
Message-ID: <>
To: SIDROps Chairs <>, SIDR Operations WG <>,
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Sidrops] [WGLC] draft-ietf-sidrops-signed-tal - ends 18/Jun/2020
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 Jul 2020 17:27:51 -0000

Howdy! this .. got lost :(
and I think the Authors are planning to meet 'shortly' and chat
through next steps for this document.

For now I think a refresh is inflight to keep it alive in the system,
but we're pending a refresh of the document in the next couple of

still frogsmasking.

On Thu, Jun 4, 2020 at 4:22 PM Christopher Morrow
<> wrote:
> 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