[cabfpub] Pre-Ballot 125 - CAA Records

Fri Sep 5 17:31:29 MST 2014

On Sep 5, 2014 5:20 PM, "kirk_hall at trendmicro.com" <kirk_hall at trendmicro.com>
wrote:
>
> Ryan, I just noticed your statement at the bottom of my proposal about a
separate ballot for the amendment I proposed.
>
>
>
> When the Forum has discussed CAA in the past, it was noted that in many
large enterprises (the most likely candidates for CAA), the people who buy
certificates are not the same people who manage the company’s DNS – and in
fact, they may not work on the same continent or know each other.  So it
may be very difficult for CAA records to be updated – a potential
competitive handicap for new CAs, or CAs trying to sell to an organization
that buys its certs from others.
>
>
>
> Several of us tried experiments within our organizations, and found this
was so (no communication between the two groups).  It was also noted that
many enterprises buy certs from multiple CAs, sometimes a development team
needs a cert on very short notice, etc. – CAA could greatly complicate this
with no real benefit if any CA tries to get an exclusive CAA record for
itself and use it as a competitive blocking tool.
>

This proposal does not concern itself with that. It is merely a requirement
to document policies.

Your concerns - and certainly, they have been raised by other CAs - about
the possibility of a CA to abuse its position in a market are only
applicable when CAs are actually required to check CAA, which the Forum has
shown there is significant opposition by CAs to do.

>
>
> I’ll tell you want I’ll do at my next CA, Voracious CA – Section
18(d)(ii) of my Subscriber Agreement will say “You hereby authorize us to
contact your DNS operator and create a CAA record with our name in it.”
Hah!  I’ve just created a potential competitive block for all my
competitors, and the customer never knew.  And I’ll have my sales team
always say “Hey, you know how you can REALLY increase your security?
Create a CAA record and put our name in it.  That prevents rogue hackers
from getting certs in your valuable domain <a totally non-target domain for
hackers>.   I’ll email you instructions containing the name and phone
number of your DNS operator – you’ll get a discount on your next cert if
you do!”  Hah – I just fooled the customer into creating a CAA record that
only contains my name.
>
> Or if I also offer hosting services, I’ll bundle it all, with an
automatic CAA record thrown in.
>
>

And there are plenty of other ways to game the system that the BRs don't
deal with.

Respectfully, Kirk, I would simply ask whether or not you will support a
simple ballot, without your modifications, that simply requires CAs to
document their policies.

CAs that are concerned of such abusive (and, dare I say, unrealistic)
behavior have full liberty to take whatever measures you find suitable in
your CPS. This simply gets your position on record.

I see no reason to stall this ballot, which would inevitably be another 6
months of delay (we have been talking about this since the Mozilla F2F
nearly a year ago), when it makes no such requirements on any CA.

>
> For CAs to impose CAA on other CAs without protective language like what
I propose presents serious competition law issues.  No one yet has said
“it’s a good idea for CAs to tell their customers to create CAA records, or
to do it for them,” so the proposed language is a way to make the CAA
ballot palatable to many CAs (especially smaller or newer CAs).
>

Please reread the ballot. You, and the other CAs who have repeatedly raised
this concern as a way to dismiss CAA, have been listened to, which is why
the ballot is so narrow and focused as it is.

Any CA that shares your view of the unlikely situation occurring can deal
with it in their CPS. If you feel it actually is a problem, or it would
prohibit a ballot that required CAA enforcement (which, again, this does
not), then we can spend another 6 months working on this language and
hearing the same arguments we have heard for the past year+.

To be clear, I'm fully sympathetic to your fear, even though I find it
extremely unlikely, but I think its entirely disconnected and orthogonal to
a simple ballot as this, which simply requires documentation of practices.

Surely you can recognize the value in both such documentation and in the
Forum occasionally reaching consensus and forward progress in real and
pressing issues, rather than be stalled by years of debate and uncertainty
while trying to boil the ocean of CA practices.

I think we have two endorsers at this point, so I would be thrilled to see
this taken to a vote. If your fears prevent you from voting on such a
simple change, then we can certainly revisit this and discuss how to
assuage them, but I think if you and others who may feel the same read the
proposal, you will realize nothing unreasonable is being requested of you.

>
>
> From: Ryan Sleevi [mailto:sleevi at google.com]
> Sent: Friday, September 05, 2014 4:43 PM
> To: Kirk Hall (RD-US)
> Cc: CABFPub
> Subject: Re: [cabfpub] Pre-Ballot 125 - CAA Records
>
>
>
>
> On Sep 5, 2014 4:35 PM, "kirk_hall at trendmicro.com" <
kirk_hall at trendmicro.com> wrote:
> >
> > Ben, I have an amendment to propose, in the form of the language below
(to be added at the end of your language in Sec. 8.2.2.  A word of
explanation:  every time CAA has come up as a topic of discussion at a CAB
Forum meeting or on a call, one or more CAs and browsers
>
> I have yet to hear a browser express this concern.
>
> > have expressed concern that CAA could be used as a "blocking" strategy
by CAs in order to add hurdles for another CA to sell certificates to the
same customer.  The main way this could happen is if a CA induces a
customer to insert its name to a CAA record when there is no CAA record at
the time for the customer (or even worse, adds its name to a blank CAA
record in the customer's name -- this could happen if the fine print of the
Subscriber Agreement authorizes the CA to insert its name in a CAA record
for the customer and the customer has no idea this is happening).  Another
potential abuse would be if a CA got its name put in blank CAA records for
other domains registered to the customer that are not even part of the
pending certificate order so that other CAs would find it more difficult to
sell certificates for those domains.
> >
> >
> >
> > There seems to be strong sentiment among CAs and browsers for some
language prohibiting this potential practice as anticompetitive.
>
> I have yet to hear a browser express this concern.
>
> > The decision of whether or not to even have a CAA record should be
solely up to the customer, not the CA.
> >
> >
> >
> > With this explanation, here is my suggestion for additional language
for this pre-ballot:
> >
> >
> >
> > In order to make certain that CAA is not used by CAs in an
anticompetitive manner, no CA shall (1) request or suggest that a customer
include the CA’s name in a CAA record for the domain in question if the
customer does not already have a CAA record that includes the name of one
or more other CAs but omits the CA’s name, (2) obtain authorization from
the customer to act on the customer’s behalf (directly or by request to the
customer’s DNS operator) to create a CAA record for the customer that
includes the CA’s name for the domain in question if the customer does not
already have a CAA record that includes the name of one or more other CAs
but omits the CA’s name, or (3) request or suggest that a customer include
the CA’s name in a CAA record for other domains not the subject of the
customer’s certificate order or obtain authorization from the customer to
act on the customer’s behalf (directly or by request to the customer’s DNS
operator) to create a CAA record for the customer for other domains not the
subject of the customer’s certificate order.
> >
> >
> >
> > What do you think?  Does this meet everyone’s stated concerns?
>
> If you feel strongly about this, I feel it is worth a separate ballot. I
do not support burdening this ballot with that language.
> >
> >
> >
> > [Also – typo below – “(section 4.1 for CA’s still conforming to RFC
2527)” should be “(section 4.1 for CAs still conforming to RFC 2527)”]
> >
> >
> >
> > -----Original Message-----
> > From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org]
On Behalf Of Ben Wilson
> > Sent: Friday, August 29, 2014 2:02 PM
> > To: Sigbjørn Vik; Rick Andrews; Geoff Keating; Stephen Davidson; Ryan
Sleevi (sleevi at google.com)
> > Cc: cabfpub
> > Subject: Re: [cabfpub] Pre-Ballot 125 - CAA Records
> >
> >
> >
> > Picking up where we left off .. attached is the redlined version that I
think is closest to where we were on this issue:
> >
> >
> >
> > 1.  In Section 4 of the Baseline Requirements, add a definition for CAA
Record as follows:
> >
> >
> >
> > CAA Record: The Certification Authority Authorization (CAA) DNS
Resource Record of RFC 6844
> >
> > (http:tools.ietf.org/html/rfc6844) that allows a DNS domain name holder
to specify the Certification Authorities
> >
> > (CAs) authorized to issue certificates for that domain. Publication of
a CAA Resource Record allows public Certification Authorities to implement
additional controls to reduce the risk of unintended certificate mis-issue.
> >
> >
> >
> > We might want to abbreviate this definition a bit.
> >
> >
> >
> > 2.  In Section 8.2.2 (instead of editing warranties in section 7.1.2 or
verification practices in section 11, as some have suggested) add the
following to the end of the paragraph on Disclosure:
> >
> >
> >
> > Effective as of [insert date that is six months from Ballot 125
adoption], section 4.2 of a CA's Certificate Policy and/or Certification
Practice Statement (section 4.1 for CA’s still conforming to RFC 2527) shall
> >
> > disclose: (1) whether the CA reviews CAA Records, and if so, (2) the
CA’s policy or practice on processing CAA Records and comparing them with
proposed Domain Names for the Common Name field or Subject Alternative Name
fields of certificates applications, and (3) any actions taken as result of
such comparison.
> >
> >
> >
> > Any comments or suggestions are welcome.
> >
> >
> >
> > -----Original Message-----
> >
> > From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org]
On Behalf Of Sigbjørn Vik
> >
> > Sent: Tuesday, July 22, 2014 12:47 AM
> >
> > To: Rick Andrews; Geoff Keating; Stephen Davidson
> >
> > Cc: cabfpub
> >
> > Subject: Re: [cabfpub] Pre-Ballot 125 - CAA Records
> >
> >
> >
> > On 21-Jul-14 20:11, Rick Andrews wrote:
> >
> > > Siggy, how does the addition of a CAA record make DoS or DNS
> >
> > > amplification
> >
> > attacks more problematic?
> >
> >
> >
> > I am no DNS expert, merely relaying comments from our sysadmin. If
people with more knowledge in the field conclude that this is not an issue,
that is fine with me, but it should be considered.
> >
> >
> >
> > > -----Original Message-----
> >
> > > From: Sigbjørn Vik [mailto:sigbjorn at opera.com]
> >
> > > Sent: Monday, July 21, 2014 12:21 AM
> >
> > > To: Rick Andrews; Geoff Keating; Stephen Davidson
> >
> > > Cc: cabfpub
> >
> > > Subject: Re: [cabfpub] Pre-Ballot 125 - CAA Records
> >
> > >
> >
> > > On 17-Jul-14 23:51, Rick Andrews wrote:> Siggy,
> >
> > >>
> >
> > >> There are a number of Security Considerations in Section 6 of the CAA
> >
> > >> RFC (_http://tools.ietf.org/html/rfc6844#page-13_) which detail
> >
> > >> possible abuse.
> >
> > >
> >
> > > I don't see DoS or DNS amplification listed there.
> >
> > >
> >
> > > --
> >
> > > Sigbjørn Vik
> >
> > > Opera Software
> >
> > >
> >
> >
> >
> >
> >
> > --
> >
> > Sigbjørn Vik
> >
> > Opera Software
> >
> > _______________________________________________
> >
> > Public mailing list
> >
> > Public at cabforum.org
> >
> > https://cabforum.org/mailman/listinfo/public
> >
> > TREND MICRO EMAIL NOTICE
> > The information contained in this email and any attachments is
confidential
> > and may be subject to copyright or other intellectual property
protection.
> > If you are not the intended recipient, you are not authorized to use or
> > disclose this information, and we request that you notify us by reply
mail or
> > telephone and delete the original message from your mail system.
> >
> >
> > _______________________________________________
> > Public mailing list
> > Public at cabforum.org
> > https://cabforum.org/mailman/listinfo/public
> >
>
> TREND MICRO EMAIL NOTICE
> The information contained in this email and any attachments is
confidential
> and may be subject to copyright or other intellectual property
protection.
> If you are not the intended recipient, you are not authorized to use or
> disclose this information, and we request that you notify us by reply
mail or
> telephone and delete the original message from your mail system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/public/attachments/20140905/67ce672c/attachment-0001.html 