[Smcwg-public] [EXTERNAL] Re: CAA and S/MIME

[Stephen Davidson]

Thanks for raising this Rob as it will come up in some detail later in our
discussions relating to control of an email address.

 

https://tools.ietf.org/html/draft-biggs-acme-sso-00#section-6 ACME Extension
for Single Sign On Challenges

 

Note that this not only defines an issueemail property for CAA, but also a
validationmethods parameter which is squarely within the interest of this
WG.  Options defined in the RFC include an SSO option (including the ability
to specify SSOproviders) as well as email verification (see other doc at
https://www.ietf.org/id/draft-ietf-acme-email-smime-13.txt Extensions to
ACME for end-user S/MIME certificates) mentioned previously.

 

Regards, Stephen

 

 

 

From: Smcwg-public <smcwg-public-bounces at cabforum.org> On Behalf Of Rob
Stradling via Smcwg-public
Sent: Monday, February 1, 2021 6:41 PM
To: Paul van Brouwershaven <Paul.vanBrouwershaven at entrust.com>; SMIME
Certificate Working Group <smcwg-public at cabforum.org>; Tim Hollebeek
<tim.hollebeek at digicert.com>; Neil Dunbar <ndunbar at trustcorsystems.com>;
Dimitris Zacharopoulos (HARICA) <dzacharo at harica.gr>
Cc: Kirk Hall <Kirk.Hall at entrust.com>
Subject: Re: [Smcwg-public] [EXTERNAL] Re: CAA and S/MIME

 

FYI, https://tools.ietf.org/html/draft-biggs-acme-sso-00#section-6 seeks to
"extend CAA to allow control over issuance of certificates for email
addresses within that domain".

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20210201/2e4c22bd/attachment.html>