Re: [Acme] IETF 107; agenda

Yaron Sheffer <yaronf.ietf@gmail.com> Mon, 09 March 2020 20:55 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049623A170A for <acme@ietfa.amsl.com>; Mon, 9 Mar 2020 13:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.384
X-Spam-Level:
X-Spam-Status: No, score=-0.384 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, MALFORMED_FREEMAIL=1.713, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 9g0BbjVvB-1v for <acme@ietfa.amsl.com>; Mon, 9 Mar 2020 13:55:28 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 E720A3A1709 for <acme@ietf.org>; Mon, 9 Mar 2020 13:55:27 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id a141so97063wme.2 for <acme@ietf.org>; Mon, 09 Mar 2020 13:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=3aItI1iIx4pt0k2EgamuQx14C4og/LpixZEvGT6Qc3c=; b=q88N848zuBNaeYzKBY5uwDLz23l6wFJZvrF6b5J0yT2SwiFwDYx0mMDbvogcFYSnFO fEyC69kQT96Eu8KRIRNETO2Chg+m7k1h5lsIb/su/CXqVOXkEc9cAoVuUR+9xfEtwQen Mtx696xaLcULje8F7HKVRrJzkeVWSq0gyqYV4rQzHuiX4Jx8ubghEKWcon2FQ2rwAcV1 RpQWzYFzwqUx8kw8rrDvxYpvqEOQ7xnlR45lHZHUJArWr+HouYlxjrFQiVgFj4SEkdB9 K8u0D6XclXAWygEFVuNNgBSrD7FwvXJAjmT1mnBipF7BJ4rE7AjOpwPXQ/gwhw5dTWay XkRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=3aItI1iIx4pt0k2EgamuQx14C4og/LpixZEvGT6Qc3c=; b=lcSTC9mCbigce5iVjSfAL/5hgSASAIUb8ovxyIIpDQq9IjeKzRxIzXj/G0lYb9Zojg 7fIbB1gHtwHfAwPJv5N+QoYjd4UpTLmkyAd7ZOTkLrPVx6dYOsuXpXSYCW359IM0D4to kjEJotVmvTT4iCDxel6Hf99W6B8jkAfdh1BTZVcfTZJLCj+I7F/Ju+5Lj6WYYXT2txuz zc0JqGwjGtvtUm/cMHg6keeyRB+nKrgQUA9slLcHJhf9b3tHtB0SdkTHTsocBrQcRmVC goUCoQ3Evq6fEUaeeqSao4H0OB+w/SIwnUHlL8kr+WzkR+D/MTg2WHF0z0Yg/HeYus2m p+tw==
X-Gm-Message-State: ANhLgQ3KN07hd14tE6HS2IoDYlBiAQlz8+muZ+Toqj4LX4HS7zCvtvyI BBqqILjd7b71reRVIa0ZAwU=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vuzRbBseD/nGHrTL7GibAm0LtQPrxm6NbGO6TmN?= =?utf-8?q?2cO57EhhLQ15fvTfAxTzCPNCIHpqcfMvuA=3D=3D?=
X-Received: by 2002:a05:600c:54f:: with SMTP id k15mr1019723wmc.96.1583787326108; Mon, 09 Mar 2020 13:55:26 -0700 (PDT)
Received: from [10.0.0.144] (bzq-79-178-61-110.red.bezeqint.net. [79.178.61.110]) by smtp.gmail.com with ESMTPSA id o26sm892298wmc.33.2020.03.09.13.55.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Mar 2020 13:55:25 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.22.0.200209
Date: Mon, 09 Mar 2020 22:55:23 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>, Yoav Nir <ynir.ietf@gmail.com>
CC: "acme@ietf.org" <acme@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Message-ID: <9932DDF4-5DAD-47FE-BD57-C45A5CB58E02@corp.intuit.net>
Thread-Topic: [Acme] IETF 107; agenda
References: <2737DD9A-53F6-4F03-AD30-0FC582E32501@akamai.com> <E00DF68C-7AE7-4C04-9D42-A902C2736C57@gmail.com> <9DC70110-40BA-45DB-8316-DF145561657F@akamai.com>
In-Reply-To: <9DC70110-40BA-45DB-8316-DF145561657F@akamai.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/AFvvhPBsUfbIOqcnLn1SbMGl6t0>
Subject: Re: [Acme] IETF 107; agenda
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 20:55:31 -0000

It would not be the first time people confused Yoav and myself. I am honored...

Yaron (me) is not planning to be there, I am banned by both my company and my government.

Re: STAR, Rich didn't get it completely right: the base STAR is in AUTH48 and might actually get published in the next day or two. STAR Delegation has made lots of progress since the last meeting, but personally (I have not consulted with my coauthors) I think is not ready for LC yet. I'll be happy to present the progress remotely, if the meeting does happen.

Thanks,
	Yaron



On 3/9/20, 19:42, "Salz, Rich" <rsalz@akamai.com> wrote:

    That is what I get for looking at the "new draft" email from Yaron while writing mail to ACME.  Ooops.
    
    
    On 3/9/20, 1:34 PM, "Yoav Nir" <ynir.ietf@gmail.com> wrote:
    
        …and Yoav won’t be there either. No idea about Yaron.
        
        > On 9 Mar 2020, at 17:11, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
        > 
        > Yaron and I cannot attend and will be remote.  We have volunteers to act as chairs for us (on CC).  Looking at the list below, it seems reasonable to cancel our session.  PLEASE POST IF YOU DISAGREE.  Of course "they" may decide to cancel anyway, but please post your opinion here.
        > 
        > Let’s look at the documents in our queue and see which need time at IETF 107.  See https://datatracker.ietf.org/wg/acme/documents/ to link to the document.
        > 
        > draft-ietf-acme-authority-token-04, ACME Challenges Using an Authority Token -and-
        > draft-ietf-acme-authority-token-tnauthlist-05,  TNAuthList profile of ACME Authority Token
        > 	Any update from the authors?  Is this ready for WGLC?
        > 	This has never had much in-person discussion, and the domain expertise is in STIR
        > 
        > draft-ietf-acme-client-00, ACME End User Client and Code Signing Certificates
        > 	Any updates?  This was recently adopted by the WG.
        > 
        > draft-ietf-acme-integrations-00, ACME Integrations
        > 	Michael Richardson can present.
        > 
        > draft-friel-acme-subdomains-02
        > 	Michael Richardson can present; this is a topic for WG adoption
        > 
        > draft-ietf-acme-email-smime-06, Extensions to Automatic Certificate Management Environment for end user S/MIME certificates
        > 	Any updates?  Ready for WGLC?
        > 
        > draft-ietf-acme-star-delegation-03, An ACME Profile for Generating Delegated STAR Certificates
        > 	Yaron just pushed a new update.  Does this need F2F time?  The main document (draft-ietf-acme-star-11,  Support for Short-Term, Automatically-Renewed (STAR) Certificates in Automated Certificate Management Environment (ACME) is already in IESG review and probably wants this one to be in the same bundle.)
        > 
        > 
        > _______________________________________________
        > Acme mailing list
        > Acme@ietf.org
        > https://www.ietf.org/mailman/listinfo/acme