Hi:

Our inclusion request has been in public discussion since April 7. 
We have provided all requested information as a first-time root inclusion 
applicant.
Kindly, we would like to move forward with our request and get your final 
feedback.

Regards.
Syrine
On Wednesday, June 23, 2021 at 10:33:41 PM UTC+1 [email protected] wrote:

> I am pretty sure this is the correct link:
>
> https://bugzilla.mozilla.org/attachment.cgi?id=9228562
>
> (Disregard the link to Facebook).
>
> Ben
>
> On Wed, Jun 23, 2021 at 1:01 PM <[email protected]> wrote:
>
>>
>> Hi
>>
>> We added a document with more details on TunTrust CA budget. See 
>>
> https://www.facebook.com/profile.php?id=100057252566463.
>> Regards
>> Syrine
>>
>>
>>
>> Sent from my Galaxy
>>
>
>>
>> -------- Original message --------
>> From: Watson Ladd <[email protected]> 
>> Date: 2021-06-23 6:01 a.m. (GMT+01:00) 
>> To: [email protected] 
>> Cc: "[email protected]" <[email protected]> 
>> Subject: Re: Public Discussion re: Inclusion of the TunTrust Root CA 
>>
>>
>>
>> On Tuesday, June 22, 2021 at 12:10:43 PM UTC-7 [email protected] wrote:
>>
>>> All,
>>> TunTrust has provided an overview of its compliance infrastructure, 
>>> which I have reviewed. See 
>>> https://bugzilla.mozilla.org/attachment.cgi?id=9226817.  I'm now asking 
>>> the community for further comments and responses to TunTrust's inclusion 
>>> request.
>>>
>>
>> I'm not happy with the level of detail in this overview. While some 
>> answers are thorough, others are not detailed enough. For example  the 
>> budget has no hard numbers at all. Obviously prediction is hard, but surely 
>> the past 3 years of spending could be included.
>>
>> Thanks,
>>> Ben
>>>
>>>
>>> On Mon, Jun 14, 2021 at 8:21 AM Syrine Tlili <[email protected]> 
>>> wrote:
>>>
>>>> Hi  All :
>>>>
>>>> We would like to move forward with our inclusion request in public 
>>>> discussion since April 7th 2021. Based on the public discussion thread [1] 
>>>> and on the new section “CA/Quantifying Value” [2], we have submitted a 
>>>> document in our Bugzilla case [3] that provides answers and clarifications 
>>>> on our CA.
>>>>
>>>>  
>>>>
>>>> [1] 
>>>> https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/LT_5efOFsSU
>>>>
>>>> [2] https://m.wiki.mozilla.org/CA/Quantifying_Value
>>>>
>>>> [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1587779
>>>>
>>>>  
>>>>
>>>> On Tuesday, April 20, 2021 at 7:20:45 PM UTC+1 [email protected] 
>>>> wrote:
>>>>
>>>>> All,
>>>>> Kathleen and I discussed iTrusChina's and TunTrust's root inclusion 
>>>>> applications this morning and agreed that we should extend the public 
>>>>> discussion period and leave them open for discussion beyond April 30th. 
>>>>> Meanwhile, I will work on follow-up questions for them regarding their 
>>>>> added value to users vs. added risk.
>>>>> Thanks,
>>>>> Ben
>>>>>
>>>>> On Thu, Apr 15, 2021 at 2:48 AM 'Syrine Tlili' via 
>>>>> [email protected] <[email protected]> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Thursday, April 8, 2021 at 4:36:19 PM UTC+1 Andrew Ayer wrote:
>>>>>>
>>>>>>> On Thu, 8 Apr 2021 08:20:58 -0700 (PDT) 
>>>>>>> Syrine Tlili <[email protected]> wrote: 
>>>>>>>
>>>>>>> > We are automatically checking the CAA records for all the 
>>>>>>> certificate 
>>>>>>> > requests equally. We do not have affiliates and the only DNS 
>>>>>>> operator 
>>>>>>> > in Tunisia is the «Agence Tunisienne 
>>>>>>> > d’Internet» (https://www.ati.tn/ ; https://whois.ati.tn/ ). 
>>>>>>> Exception 
>>>>>>> > on checking CAA records does not apply to us. 
>>>>>>>
>>>>>>> Your CPS currently lists three exceptions where you might skip CAA 
>>>>>>> checking. If this is not accurate, it should be updated. 
>>>>>>>
>>>>>>> Regards, 
>>>>>>> Andrew
>>>>>>
>>>>>>
>>>>>> Hi:
>>>>>>
>>>>>> This section on  CAA checking exceptions is now updated in our CP/CPS.
>>>>>>
>>>>>> Regards,
>>>>>> Syrine Tlili   
>>>>>>
>>>>>> -- 
>>>>>>
>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "[email protected]" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/3b85ce38-7809-49ff-a2a3-1a9c2a936c30n%40mozilla.org
>>>>>>  
>>>>>> <https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/3b85ce38-7809-49ff-a2a3-1a9c2a936c30n%40mozilla.org?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "[email protected]" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/a/mozilla.org/d/topic/dev-security-policy/dTTp4ZfUW34/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/54f7f7c8-0c5f-403f-bfa1-5a82e7718cbdn%40mozilla.org
>>  
>> <https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/54f7f7c8-0c5f-403f-bfa1-5a82e7718cbdn%40mozilla.org?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/5070bef6-b41c-4900-95f0-141debcc0d1cn%40mozilla.org.

Reply via email to