IETF Logo Mail Archive

Re: [Acme] IETF 104 Agenda

Yoav Nir <ynir.ietf@gmail.com> Thu, 21 March 2019 11:37 UTC

Return-Path: <ynir.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 D321B1310B0 for <acme@ietfa.amsl.com>; Thu, 21 Mar 2019 04:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5smulw-G-29B for <acme@ietfa.amsl.com>; Thu, 21 Mar 2019 04:37:31 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 392B8131095 for <acme@ietf.org>; Thu, 21 Mar 2019 04:37:29 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id d1so4664696edd.13 for <acme@ietf.org>; Thu, 21 Mar 2019 04:37:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=in-reply-to:references:thread-topic:user-agent:mime-version :content-transfer-encoding:subject:from:date:to:cc:message-id; bh=qZS5fVUoOeEOLqgrH5HuODgIRqdh/6ZStH+tM++/aDk=; b=Z0Vs5hBE1bC2lqUU6VIJ+OQ1CieeCxZKE5AnqK/9cxVqxDw1W+r1xG55+vDv5Zh4Dr 5kxbqOTzIRl5uYRaGPwJ3GF7eEzyDsXi2ygtJ6y3fQYM1ymWARGN8TJ/aCdsuHHttheP 6lwL5/Z9ZlU5mgkDa4eSosGY1YojMV0B2FArbS3BTcqbwJ9r4QzIUr7zcfQrC72hIHuq ycmWsZcqGrvYZ0GXDH42MjZdSpbp5ALY85NgxD2Uj62qVHCXcvQGXY59h2BT8bw++Sja /jvIJ10m0UEC+IJohZN/bDkJI2Uwcxy6YoPjx8Kz6/7EmXO7/pYGb43MLBfuqWJ6lpQb wl6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:in-reply-to:references:thread-topic:user-agent :mime-version:content-transfer-encoding:subject:from:date:to:cc :message-id; bh=qZS5fVUoOeEOLqgrH5HuODgIRqdh/6ZStH+tM++/aDk=; b=W1FAu2sAMSD6RUb7vSm212GUCm8tL940m2/FRGr8KWs2d8II3tYVsGKA4cedK+Yjc9 01rnXqyv9v+3Igmq+dwAPOXv7c//xa7GtyVTPtzQRCPszWDPt4Dq3qvMbBGKM8Q/a7e0 UA1wbGnDb54iYPyPbfLAEcR2Nmg1awC/TlJFki36vSlFdSGJz7GuEhTL2H1wNhwGzcpC VOhp3GZ1OFuvhpu/w9bJEd7qOuE7xBZxRad7pJQ5+SPvgmsPx4GQ3jifwXAlvBWThovs TquYTk28ez5oPYi9nv2pHBKUCeatKceg3bkgb6VwYZSe1wNdQOxHKKUO/6Glz5QXM+wy 5Htg==
X-Gm-Message-State: APjAAAWqmT86jrPsitr6SKnSao5ULBj6+dwM5FI7XJkLBud7gzlW3X2J C5C/65qDApC/p5/MP1pbdwH6EJ2YSvo=
X-Google-Smtp-Source: APXvYqy42lnZDYW3oDiZ5Qzcpq4eQ3YL0EbU+sFrvWJ6ttBjSatQnLlj0OCIaKc8NsrQ5PDoKThi9g==
X-Received: by 2002:a17:906:a85a:: with SMTP id dx26mr1990772ejb.206.1553168247785; Thu, 21 Mar 2019 04:37:27 -0700 (PDT)
Received: from [10.41.2.0] ([147.178.6.137]) by smtp.gmail.com with ESMTPSA id 9sm1023176ejg.71.2019.03.21.04.37.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Mar 2019 04:37:26 -0700 (PDT)
In-Reply-To: <CAGL6ep+5M_bf6SNSTzyjTrN9NWFoz0en7zQuq8MJDiaWryyZeQ@mail.gmail.com>
References: <75FF8515-3866-4F1A-8498-8D6BEC351261@akamai.com> <CAGL6ep+5M_bf6SNSTzyjTrN9NWFoz0en7zQuq8MJDiaWryyZeQ@mail.gmail.com>
X-Referenced-Uid: 63270
Thread-Topic: Re: [Acme] IETF 104 Agenda
User-Agent: Android
X-Is-Generated-Message-Id: true
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----NC127H3K5IHUVSGCDFMEJXJ57S96Z0"
Content-Transfer-Encoding: 7bit
X-Local-Message-Id: <8e1a54ee-b143-4e4a-a2a2-46460b01c9b0@gmail.com>
From: Yoav Nir <ynir.ietf@gmail.com>
Date: Thu, 21 Mar 2019 13:37:23 +0200
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
CC: Rich Salz <rsalz@akamai.com>, IETF ACME <acme@ietf.org>
Message-ID: <8e1a54ee-b143-4e4a-a2a2-46460b01c9b0@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/82Ne6nvn3myoq-HLgrMK-oEfe38>
Subject: Re: [Acme] IETF 104 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: Thu, 21 Mar 2019 11:37:45 -0000

Hi Rifaat. 

We only have one hour in total.  It's about 5 minutes for the administrative stuff, another 10 for status and reconfirming STAR, and maybe 5-10 for status of other things. The rest (about 40 minutes) is for device attestation and client certs. 

⁣Sent from my phone ​


-------- Original Message --------
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Sent: Thu Mar 21 13:18:59 GMT+02:00 2019
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] IETF 104 Agenda

Rich,

How much time is allocated to these items?

Regards,
 Rifaat


On Tuesday, March 19, 2019, Salz, Rich <rsalz@akamai.com> wrote:

> The agenda has been posted to https://datatracker.ietf.org/
> meeting/104/session/acme  It is also below.
>
>
>
> If you want to volunteer before the meeting to do Jabber and/or minutes
> (via etherpad if you prefer), please email acme-chairs@ietf.org
>
>
>
> ACME at IETF 104
>
> Weds 11:20-12:20
>
>
>
>
>
> Admin
>
>     Bluesheets, note-taker, jabber
>
>     Status
>
>
>
> STAR
>
>     Reconfirm lastcall (consensus)
>
>
>
> Device Attestation
>
>
>
> Client certificates
>
>
>
> TNAuth (?)
>
>
>
> Other ?
>


------------------------------------------------------------------------

_______________________________________________
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

v2.23.0 | Report a Bug | By Email