Re: [Acme] Agenda for IETF 105

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 11 July 2019 23:17 UTC

Return-Path: <kathleen.moriarty.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 014EE120041 for <acme@ietfa.amsl.com>; Thu, 11 Jul 2019 16:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, 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 axSEDn8rDCuN for <acme@ietfa.amsl.com>; Thu, 11 Jul 2019 16:17:38 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 5F3AE120033 for <acme@ietf.org>; Thu, 11 Jul 2019 16:17:38 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id z4so6269814qtc.3 for <acme@ietf.org>; Thu, 11 Jul 2019 16:17:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ySnaSDRChOh/Fr4cNDFczgEWbiJL5N8l4GSidh+8Sr0=; b=GP1i/vNn+QTf3xgeqdEztQ5SzJf4VxwpZ9nuUOoMS2QriRBiH3N8qjpqmue71wIL2O 7ZLHbQTUBHruAET21rQj7JO49lyDj7RTXNfsaVdrmVs1+1cCPxMztEp+1TY5Le7zzVrq XDqPLmwWCzNzTAtmlUx13eD9epkqtMbNXcDJmeD9iXCM8nr171CQGHEdngkWc1OX/7G8 idUTzoLF8Ne/nZN7G0wSs3qr57iO6yAm70ywdZL9ZPT53eCS3+gGYOpnziFLOoXUFIwo KomVUS2M3LpvNXz9TymkILd6CdlHD6jufmdK1rCp7JaVUdI0u+fuPxQsw9CoB6HgxecY KMJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ySnaSDRChOh/Fr4cNDFczgEWbiJL5N8l4GSidh+8Sr0=; b=S/p1X/Uh3lPceEzcNliNkW7aiMfkJ8/xzQd6z5Y9avi8dmMg7KKk+NoAnp5cU1Jc3A 1d8TyEgGDFrcwtjiMXTUioMNWveywFxX2N5dwSE/cuoR+G8tuOljx3UHWUAz9G1avxyw 9+8kV1N+nXUVF0L5ArOtGG32uf+4B1AKLOniQSX5xB7ZJwU1GEEkenCjZqyg+xP4mo9y LsDAhKma82L3UM8ABNTEQQMkLXceCuJ1T3/xsX9J0LWGNrbdT8lMowTW+a5Y2V5yUeP8 0C+wU1hPnJD0jsZ+P5NCRBu/K2yefFNdQqSDwq4pM+sOhn8eLIj/cRaUruVToX8yfc/O I7lw==
X-Gm-Message-State: APjAAAW46jGBW/MVllXjuZrTMZMZApBxEAt9EYzwoeVetJWr5L6zsngp uMwFeKLzVw5JXLXmNqd4R/rRYr5DJWA=
X-Google-Smtp-Source: APXvYqySmBu7q8eTxtsKKpQm1ArfR65H/B29U9/ETGtnfrn3AFcCzfBhJZFx6leUIpuhwsNL1iywUw==
X-Received: by 2002:aed:37e7:: with SMTP id j94mr1180689qtb.75.1562887057338; Thu, 11 Jul 2019 16:17:37 -0700 (PDT)
Received: from [192.168.1.3] (146-115-73-78.s5196.c3-0.arl-cbr1.sbo-arl.ma.cable.rcncustomer.com. [146.115.73.78]) by smtp.gmail.com with ESMTPSA id j22sm2558070qtp.0.2019.07.11.16.17.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jul 2019 16:17:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-E9977C8D-A4C8-4781-9191-C65DDAA889E0"
Mime-Version: 1.0 (1.0)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <DM6PR11MB3385039A752CA0A71B188B2EDBF30@DM6PR11MB3385.namprd11.prod.outlook.com>
Date: Thu, 11 Jul 2019 19:17:35 -0400
Cc: Yoav Nir <ynir.ietf@gmail.com>, IETF ACME <acme@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <89B6CECC-92A7-4949-ADFB-37D789C867C2@gmail.com>
References: <893AF799-FFBF-4120-98F9-AF7F7E985EC9@gmail.com> <DM6PR11MB3385039A752CA0A71B188B2EDBF30@DM6PR11MB3385.namprd11.prod.outlook.com>
To: "Owen Friel (ofriel)" <ofriel@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/-XDM69nqJPG8IRkaeJ7mQeTXs1o>
Subject: Re: [Acme] Agenda for IETF 105
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: Thu, 11 Jul 2019 23:17:40 -0000


Sent from my mobile device

> On Jul 11, 2019, at 4:56 PM, Owen Friel (ofriel) <ofriel@cisco.com> wrote:
> 
> Hi all,
> Could I have 10 mins to cover:
> https://tools.ietf.org/html/draft-friel-acme-integrations-01
>  
> There is some overlap with https://tools.ietf.org/html/draft-yusef-acme-3rd-party-device-attestation-01 and https://datatracker.ietf.org/doc/draft-moriarty-acme-client/ and we are having offline discussion with Kathleen and Rifaat on how to align all 3.

I’d like to present the updated client draft listed above as well.

There’s an overview draft the may fold in with Owen’s, but we need to figure that out according to interest.

https://tools.ietf.org/html/draft-moriarty-acme-overview-00

Best regards,
Kathleen 

>  
> Thanks,
> Owen
>  
> From: Acme <acme-bounces@ietf.org> On Behalf Of Yoav Nir
> Sent: 11 July 2019 20:50
> To: IETF ACME <acme@ietf.org>
> Subject: [Acme] Agenda for IETF 105
>  
> Hi, all
>  
> We are putting together the agenda for IETF 105.
>  
> The current plan is to have presentation and agenda time for email and for telephony.
>  
> There is still time on the agenda to cover more topics, so if you think they should be brought up, please reply either to this thread, or directly to Rich and me:
> ·         draft-ietf-acme-tls-alpn seems to be stalled for months. We’ve had a change of AD and a new AD review ([1]). Can allocating meeting time help with progressing this?
> ·         draft-ietf-acme-star is in IETF LC with no significant issues having come up.  Unless the authors think otherwise, I don’t see a need to allocate agenda time at this point.
> ·         draft-ietf-acme-ip is waiting for an AD write-up and to progress it. Unless Roland feels differently, I don’t think there’s much to spend agenda time on.
> ·         draft-ietf-acme-caa is in the RFC editor’s queue.  So, all good?
>  
> If you have some other business for the WG meeting, please bring it up now.
>  
> Thanks
>  
> Rich & Yoav
>  
>  
> [1] https://mailarchive.ietf.org/arch/msg/acme/YW9rho7i1YjLd32k-MDYX4p2dSU
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme