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

Chris Morrow <morrowc@ops-netman.net> Fri, 17 July 2020 02:23 UTC

Return-Path: <morrowc@ops-netman.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 44EB83A0F69; Thu, 16 Jul 2020 19:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 VtriYvK8hrsE; Thu, 16 Jul 2020 19:23:57 -0700 (PDT)
Received: from relay.ops-netman.net (relay.ops-netman.net [192.110.255.59]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86E8D3A0F6B; Thu, 16 Jul 2020 19:23:57 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net [199.168.90.119]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by relay.ops-netman.net (Postfix) with ESMTPS id 74C6C3C2035; Fri, 17 Jul 2020 02:23:56 +0000 (UTC)
Received: from mailserver.ops-netman.net.ops-netman.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id 40C1A22F; Fri, 17 Jul 2020 02:23:56 +0000 (UTC)
Date: Fri, 17 Jul 2020 02:23:56 +0000
Message-ID: <87y2nix4jn.wl-morrowc@ops-netman.net>
From: Chris Morrow <morrowc@ops-netman.net>
To: George Michaelson <ggm@algebras.org>
Cc: Christopher Morrow <christopher.morrow@gmail.com>, SIDROps Chairs <sidrops-chairs@ietf.org>, SIDR Operations WG <sidrops@ietf.org>, sidrops-ads@ietf.org
In-Reply-To: <CAKr6gn0_iV62kMuzSpdsiFJ-LJyNsqbU2zLvDqy8rd1zFtHbLw@mail.gmail.com>
References: <CAL9jLaZLYJYkSZneO6mWizF3bY1KAb9-JKaj7FKhZE4dhAGLrA@mail.gmail.com> <CAL9jLaZGwPr8fBrNMfX-jo8=rU1YaWt45T6EvuEkg5ekxk1dCw@mail.gmail.com> <CAKr6gn0_iV62kMuzSpdsiFJ-LJyNsqbU2zLvDqy8rd1zFtHbLw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 Mule/6.0 (HANACHIRUSATO)
Organization: Operations Network Management, Ltd.
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/blFxR1_dBMT1nbapByh8TVBNkVk>
Subject: Re: [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: Fri, 17 Jul 2020 02:23:59 -0000

On Thu, 16 Jul 2020 23:40:47 +0000,
George Michaelson <ggm@algebras.org> wrote:
> 
> I will discuss this with the other authors and expect to re-issue
> shortly subject to their agreement.
> 
> It would be logistically kinder to do this next week, given timezones.

"in your own time" is perfectl fine! :) I wasn't trying to push you
along, just to set status on something that's late getting it (my
fault) and which was in queue for action.

thanks!

> 
> There isn't much more to be said at this point.
> 
> -G
> 
> On Fri, Jul 17, 2020 at 3:27 AM Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
> >
> > 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
> > weeks.
> >
> > -chris
> > still frogsmasking.
> >
> > On Thu, Jun 4, 2020 at 4:22 PM Christopher Morrow
> > <christopher.morrow@gmail.com> 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
> >
> > _______________________________________________
> > Sidrops mailing list
> > Sidrops@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidrops