Re: [Acme] [EXTERNAL] agenda items for IETF 118 and important dates

Deb Cooley <debcooley1@gmail.com> Thu, 02 November 2023 14:29 UTC

Return-Path: <debcooley1@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 E3391C15152F; Thu, 2 Nov 2023 07:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.853
X-Spam-Level:
X-Spam-Status: No, score=-1.853 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXeLCkV9mpjZ; Thu, 2 Nov 2023 07:29:01 -0700 (PDT)
Received: from mail-oo1-xc32.google.com (mail-oo1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EC72C15109A; Thu, 2 Nov 2023 07:29:01 -0700 (PDT)
Received: by mail-oo1-xc32.google.com with SMTP id 006d021491bc7-5820299b99cso997573eaf.1; Thu, 02 Nov 2023 07:29:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698935340; x=1699540140; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=knUcX0v7oPbDiJQr815ariil8vOxif4iMFTfrendR/c=; b=lDQR8BLvirShsdGpGRjSXyMQaH/ZoPdgd83Yn6oo+Ybhy2kYmpqnrp0yx4Wirl6JO4 E9R5GVvmVNQwYvMUGGp5eMrV5pmJDYfNRYcCeSfc/0Xz2Qn7duV0n8ebRYgIFzenPSaJ Ll8ZHjDM6Xn5mtBeZyvT06XMKFKrfPIuRCjZz/wvFJ6XIxgnvsuUTE4VUZid8O2nmxeP pQDyN9KycOeJUvKPwsydPPo49c7RGotDTNgtMbE9ZpqlTVLHNy8v/FUPMqeECzbehlmz dhqdciPnS0WvaUbVE+UexFoLiUzdLLKmAjWR6MENAMfYIRcNBlbJBZMwAMB9iUOfC1L/ NzSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698935340; x=1699540140; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=knUcX0v7oPbDiJQr815ariil8vOxif4iMFTfrendR/c=; b=Xg9YumRmljrJp0w2xUuJ720dwZUtJ2EhFLYIZYciF8Np4swv+55Icb7d3wazWO1BYr +KU/B/RcaxlIhAEghChwkDYXP1YCAkSIhsNnUo453DwIan1tDXvP937LUm3Yp7t8+iMV Cn3czzi7jr1KB8C347j1NnRkEPpHhCm3VF/VOeeFGtfVqmYsr2zdMBfjMUOklGEmhWVU 7MzdSHGvHDl+4yodV0s/rMjN7Jmn7evsAhgQqLqYcSDBelt7KH4wqvlpBRRqidBogeip XlXF7EwSqYRgxZTn5D+1tXkWuaalQrRsjtAdk8yhW/3+xg617c9Ov/ALfRRNRoCdzqNs bJqg==
X-Gm-Message-State: AOJu0YwNgve8Bp3KG+nTj3VuvzxiNtF34nviOUcewyX/qEijhrWC4R2V WRawivhz5dX3N4eRGh19uCjRbqFzJC6dyMT3KCXLYTE=
X-Google-Smtp-Source: AGHT+IGi02745MprtIzDANzQ/FhgEbiX/0BU0y8zrS1f5bi9mpJcJcHa22oDwKQLsm31fYjSG2M5vOQVx8lQMO+DZz4=
X-Received: by 2002:a05:6870:1699:b0:1e9:d3bd:3ec with SMTP id j25-20020a056870169900b001e9d3bd03ecmr3208229oae.22.1698935340044; Thu, 02 Nov 2023 07:29:00 -0700 (PDT)
MIME-Version: 1.0
References: <CAGgd1OdbbuZme9-XrAN9oNhxv_8aE5cwSONiO-6Vrcxk2k2+BQ@mail.gmail.com> <CH0PR11MB57398136296EF61F5115F0B59FD3A@CH0PR11MB5739.namprd11.prod.outlook.com>
In-Reply-To: <CH0PR11MB57398136296EF61F5115F0B59FD3A@CH0PR11MB5739.namprd11.prod.outlook.com>
From: Deb Cooley <debcooley1@gmail.com>
Date: Thu, 02 Nov 2023 10:28:48 -0400
Message-ID: <CAGgd1OfASr+pM7dPDYcNTuYzpVMsNK5XQ1_od3x4JgXGEXOs8A@mail.gmail.com>
To: IETF ACME <acme@ietf.org>
Cc: "acme-ads@ietf.org" <acme-ads@ietf.org>, "<acme-chairs@ietf.org>" <acme-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007098f506092c35a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/GQrINTXgVA_-WTmqidnr1sU2nys>
Subject: Re: [Acme] [EXTERNAL] agenda items for IETF 118 and important dates
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
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, 02 Nov 2023 14:29:06 -0000

I'm getting ready to put the acme agenda together.  I have only two
briefing that have been requested...  Obviously we can add people late, but
it is nicer to know in advance.

Also the Meetecho interface has changed.  There are videos and resources
available.  I was going to request a test session so I can see what the
chair features look like.  If any of the speakers (especially remote
speakers) want to tag along, I'd be good with that.  If you have times you
prefer, just email the chair alias.  My thought was maybe on Friday late
afternoon (US East Coast time), Monday before the sessions (Prague time),
or Monday lunch (Prague time).

Deb

On Thu, Oct 12, 2023 at 12:01 PM Mike Ounsworth <Mike.Ounsworth@entrust.com>
wrote:

> Hi Deb,
>
>
>
> We have just pushed draft-vanbrouwershaven-acme-auto-discovery-02: we
> have just pushed a -02 [1]. Since 117 there have been some great offline
> discussions making progress on the technical issues, so we can give a short
> presentation to update the community.
>
>
>
> The main technical issue we’re working through is “account
> disambiguation”; consider a large enterprise subscriber that has multiple
> departments which are all authorized to issue for *.company.com, but
> let’s say that only DepartmentA is authorized to issue S/MIME, and only
> DepartmentB is authorized to issue EV. The acme-auto-discovery mechanism
> will result in an issuance request from the ACME protocol account
> controlled by the cloud provider, so we need a robust way to tie that back
> to the pre-existing substcriber Org/Department account in the CA. This is
> turning out to be tricky, but we’ll be happy to present progress at 118.
>
>
>
>
>
> [1]:
> https://datatracker.ietf.org/doc/draft-vanbrouwershaven-acme-auto-discovery/
>
> ---
>
> *Mike* Ounsworth
>
>
>
> *From:* Acme <acme-bounces@ietf.org> *On Behalf Of * Deb Cooley
> *Sent:* Monday, October 9, 2023 9:22 AM
> *To:* IETF ACME <acme@ietf.org>
> *Cc:* acme-ads@ietf.org; <acme-chairs@ietf.org> <acme-chairs@ietf.org>
> *Subject:* [EXTERNAL] [Acme] agenda items for IETF 118 and important dates
>
>
>
> All, The preliminary agenda has acme scheduled to meet on Wednesday from
> 1300-1400 (Prague time).   The agenda will be final on Friday (13 Oct).
> If you would like to present during that time slot, please contact the
> chairs ( acme-chairs@ ietf. org
>
> All,
>
>
>
> The preliminary agenda has acme scheduled to meet on Wednesday from
> 1300-1400 (Prague time).  The agenda will be final on Friday (13 Oct).  If
> you would like to present during that time slot, please contact the chairs
> ( acme-chairs@ietf.org ).
>
>
>
> Also the Internet Draft submission cut-off is 23 Oct 2023 midnight (UTC),
> so if you want your draft updated prior to the workshop, now is the time.
> Obviously new work falls into this timeline as well.
>
>
>
> A couple of notes:
>
> 1.  draft-ietf-acme-dtnnodeid-11 - the chairs will coordinate w/ the AD.
> mea culpa.
>
> 2.  draft-vanbrouwershaven-acme-auto-discovery-01 - we would like to see
> this draft updated before the call for adoption.
>
>
> Deb (and Yoav)
> acme chairs
>
>
> *Any email and files/attachments transmitted with it are intended solely
> for the use of the individual or entity to whom they are addressed. If this
> message has been sent to you in error, you must not copy, distribute or
> disclose of the information it contains. Please notify Entrust immediately
> and delete the message from your system.*
>