[Acme] Fwd: New Version Notification for draft-biggs-acme-sso-00.txt

Richard Barnes <rlb@ipv.sx> Wed, 09 December 2020 17:00 UTC

Return-Path: <rlb@ipv.sx>
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 7447C3A0FC4 for <acme@ietfa.amsl.com>; Wed, 9 Dec 2020 09:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=ipv-sx.20150623.gappssmtp.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 sY6utPbPXVER for <acme@ietfa.amsl.com>; Wed, 9 Dec 2020 09:00:33 -0800 (PST)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 6A4C93A0F2E for <acme@ietf.org>; Wed, 9 Dec 2020 09:00:32 -0800 (PST)
Received: by mail-qv1-xf2b.google.com with SMTP id dm12so908016qvb.3 for <acme@ietf.org>; Wed, 09 Dec 2020 09:00:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=c9QSeIDpf9TpN9QCxp0twWMhpEjCQhmUd3H7ekNm09A=; b=O5U7HTtBfMeRVvDN8IfJvhTVJ90pD5/EFYlZyRHn7MrGGwQ6cOvxjtABvMUt+6jQcB hgMm7OybsUIJx7WSk10frfpfiVPNlsZhvxQR/Fx3I1XGQEhXozWe1HgNTUa9U+uniVc+ UsddHdv51UYoETC3nhQWSIJ8/pyX1fUwa8Cr3WxPmR6bxNl9riA+5BmrlEOMToALemMG hrmVkmHQF1mygJFWlCt3AQ9RBxcUsjwfsB+m8zD2tXdxq51b3DU6j0dsjgW3oy7S5bQt mi4Dxm4xk4T4pnQgD1FKh3Ur+ReFeF114OyhRbLvrNaQaaW+t5ROyat/lYJIVKFKrHsU s5ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=c9QSeIDpf9TpN9QCxp0twWMhpEjCQhmUd3H7ekNm09A=; b=oQCYFl9UCORmcjOCwNL62TVgac3j4jbrNK6P2RxAu6ZYl8wpt9DFSpeFoY4fvNw0te 3lLLAalwMMQMxpe03/lHYtw8nWbnAU3rDXtwcKR/FLt9yAvTqpv9QlZ0UMJsNBR+gG6d rlGfQYytEiS251IRzBdg2eEsPSDaZIpbsBJ2ybbNBgu/GgwzYNdI4Hrr2NizD/PIA/qa ScPHSVjLYX2R78V+2fZWBjtB/pN2nT+n7q2BJ9czWc1VOy9UhQpMwWVd+rpWuMlgcM5N cuzOZC3z1xfOGTzQ7kL245kwxzxB303mcm++cZqQCaR/nyiQAGBBPpDt+9bai48+KZZa NbIA==
X-Gm-Message-State: AOAM533y3ZiNxedndsGFWcHjOOdoFSgZk4yPrIVPRaPCOZnFmEbVE+Zr XISE3H3CEzAaaNKCPlAw83I1KWdzJde1sMNcmL1DUtHvAjE=
X-Google-Smtp-Source: ABdhPJz313vlHLbriTzUC8zAyv6YS8XhrYjG3e+qgnsKUlWP/xmx66wMWSOYYZQodk/GxbNSX3eETAWrIeD84wlBz8Y=
X-Received: by 2002:a0c:b415:: with SMTP id u21mr3981510qve.0.1607533230321; Wed, 09 Dec 2020 09:00:30 -0800 (PST)
MIME-Version: 1.0
References: <160744016926.7556.727252086744891540@ietfa.amsl.com>
In-Reply-To: <160744016926.7556.727252086744891540@ietfa.amsl.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 09 Dec 2020 12:00:08 -0500
Message-ID: <CAL02cgSti9SQ7Z6mq9oD-4GeNU+ver7MZCueff2A3SmZn=4gOw@mail.gmail.com>
To: IETF ACME <acme@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000028d93605b60aff83"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/q1ONYCJ-SJZWe1wa-yr5OCceyjU>
Subject: [Acme] Fwd: New Version Notification for draft-biggs-acme-sso-00.txt
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: Wed, 09 Dec 2020 17:00:36 -0000

Hi ACME folks,

I'd like to bring this proposed extension to ACME to the attention of the
working group.  This work builds on Alexei's document defining the "email"
identifier type, and defines (1) a mechanism for validating email addresses
using SSO, and (2) some CAA mechanisms to manage issuance of certificates
with email addresses.

I would like for the ACME WG to take this on as a work item, as a logical
next step following on draft-ietf-acme-email-smime.  Any feedback on the
draft would be very welcome.

Thanks,
--Richard


---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, Dec 8, 2020 at 10:09 AM
Subject: New Version Notification for draft-biggs-acme-sso-00.txt
To: Andrew Biggs <adb@cisco.com>, Richard L. Barnes <rlb@ipv.sx>



A new version of I-D, draft-biggs-acme-sso-00.txt
has been successfully submitted by Richard Barnes and posted to the
IETF repository.

Name:           draft-biggs-acme-sso
Revision:       00
Title:          Automated Certificate Management Environment (ACME)
Extension for Single Sign On Challenges
Document date:  2020-12-08
Group:          Individual Submission
Pages:          12
URL:            https://www.ietf.org/archive/id/draft-biggs-acme-sso-00.txt
Status:         https://datatracker.ietf.org/doc/draft-biggs-acme-sso/
Html:           https://www.ietf.org/archive/id/draft-biggs-acme-sso-00.html
Htmlized:       https://tools.ietf.org/html/draft-biggs-acme-sso-00


Abstract:
   This document specifies an extension to the ACME protocol [RFC8555]
   to enable ACME servers to validate a client's control of an email
   identifier using single sign-on (SSO) technologies.  An extension to
   the CAA [RFC8659] resource record specification is also defined to
   provide domain owners a means to declare a set of SSO providers that
   ACME servers may rely upon when employing SSO for identifier
   validation on their domain.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat