[cabfcert_policy] Proposed edits to Section 5.1 of BRs

Fri May 6 03:08:19 MST 2016

Dear Ben,

       Chunghwa Telecom will endorse.

Sincerely Yours,

               Li-Chun CHEN

From: policyreview-bounces at cabforum.org [mailto:policyreview-bounces at cabforum.org] On Behalf Of Ben Wilson
Sent: Thursday, May 05, 2016 11:25 PM
To: Robin Alden; 'Dimitris Zacharopoulos'; policyreview at cabforum.org
Subject: Re: [cabfcert_policy] Proposed edits to Section 5.1 of BRs

Thanks, Robin.  The  draft ballot is posted here:

https://cabforum.org/wiki/170%20-%20Amend%20Section%205.1%20of%20Baseline%20Requirements 

From: Robin Alden [mailto:robin at comodo.com] 
Sent: Thursday, May 5, 2016 8:18 AM
To: Ben Wilson <ben.wilson at digicert.com>; 'Dimitris Zacharopoulos' <jimmy at it.auth.gr>; policyreview at cabforum.org
Subject: RE: [cabfcert_policy] Proposed edits to Section 5.1 of BRs

Hi Ben,

                Comodo will endorse.

Regards
Robin

From: policyreview-bounces at cabforum.org [mailto:policyreview-bounces at cabforum.org] On Behalf Of Ben Wilson
Sent: 04 May 2016 16:13
To: Ben Wilson <ben.wilson at digicert.com>; Dimitris Zacharopoulos <jimmy at it.auth.gr>; policyreview at cabforum.org
Subject: Re: [cabfcert_policy] Proposed edits to Section 5.1 of BRs

Here it is with that  recent change.  https://github.com/cabforum/documents/compare/PolicyRevWG-%233-BR-Section-5.1 

I will need two endorsers.

From: policyreview-bounces at cabforum.org [mailto:policyreview-bounces at cabforum.org] On Behalf Of Ben Wilson
Sent: Wednesday, May 4, 2016 9:09 AM
To: Dimitris Zacharopoulos <jimmy at it.auth.gr>; policyreview at cabforum.org
Subject: Re: [cabfcert_policy] Proposed edits to Section 5.1 of BRs

Thanks.  We can just delete that cross-reference. 

From: policyreview-bounces at cabforum.org [mailto:policyreview-bounces at cabforum.org] On Behalf Of Dimitris Zacharopoulos
Sent: Wednesday, May 4, 2016 4:20 AM
To: policyreview at cabforum.org
Subject: Re: [cabfcert_policy] Proposed edits to Section 5.1 of BRs

Hello Ben,

Section 5.1.8 (Off-site backup) refers to 6.2.4 (Private Key Backup) which currently only states "See Section 5.2.2.", which refers to "number of individuals required per task". 
Is Section 5.2.2 planned to be updated along with the proposed changes of your latest commit <https://github.com/cabforum/documents/commit/84bbe5607dc96f330d3830578454741c2ea61fcd> ? 

It seems that we are making too many hops and perhaps could somehow reduce them.

Best regards,
Dimitris.

On 3/5/2016 11:29 μμ, Ben Wilson wrote:

Content-Type: multipart/alternative;

  boundary="----=_NextPart_001_0038_01D1A548.30B658A0"

------=_NextPart_001_0038_01D1A548.30B658A0

Content-Type: text/plain;

  charset="us-ascii"

Content-Transfer-Encoding: 7bit

I've uploaded proposed language for additions to section 5.1 of the

Baseline Requirements into GitHub.  Available for review here:

https://github.com/cabforum/documents/commit/84bbe5607dc96f330d3830578454741

c2ea61fcd 

------=_NextPart_001_0038_01D1A548.30B658A0

Content-Type: text/html;

  charset="us-ascii"

Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =

xmlns:o=3D"urn:schemas-microsoft-com:office:office" =

xmlns:w=3D"urn:schemas-microsoft-com:office:word" =

xmlns:m=3D <http://schemas.microsoft.com/office/2004/12/omml> "http://schemas.microsoft.com/office/2004/12/omml" =

xmlns=3D <http://www.w3.org/TR/REC-html40> "http://www.w3.org/TR/REC-html40"><head><META =

HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =

charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =

(filtered medium)"><style><!--

/* Font Definitions */

@font-face

  {font-family:"Cambria Math";

  panose-1:2 4 5 3 5 4 6 3 2 4;}

@font-face

  {font-family:Calibri;

  panose-1:2 15 5 2 2 2 4 3 2 4;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

  {margin:0in;

  margin-bottom:.0001pt;

  font-size:11.0pt;

  font-family:"Calibri",sans-serif;}

a:link, span.MsoHyperlink

  {mso-style-priority:99;

  color:#0563C1;

  text-decoration:underline;}

a:visited, span.MsoHyperlinkFollowed

  {mso-style-priority:99;

  color:#954F72;

  text-decoration:underline;}

span.EmailStyle17

  {mso-style-type:personal-compose;

  font-family:"Calibri",sans-serif;

  color:windowtext;}

.MsoChpDefault

  {mso-style-type:export-only;

  font-family:"Calibri",sans-serif;}

@page WordSection1

  {size:8.5in 11.0in;

  margin:1.0in 1.0in 1.0in 1.0in;}

div.WordSection1

  {page:WordSection1;}

--></style><!--[if gte mso 9]><xml>

<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />

</xml><![endif]--><!--[if gte mso 9]><xml>

<o:shapelayout v:ext=3D"edit">

<o:idmap v:ext=3D"edit" data=3D"1" />

</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US =

link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =

class=3DMsoNormal>I&#8217;ve uploaded proposed language for additions to =

section 5.1 of the&nbsp; Baseline Requirements into GitHub.&nbsp; =

Available for review here:<o:p></o:p></p><p =

class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =

href=3D <https://github.com/cabforum/documents/commit/84bbe5607dc96f330d38=30578454741c2ea61fcd> "https://github.com/cabforum/documents/commit/84bbe5607dc96f330d38=
30578454741c2ea61fcd <https://github.com/cabforum/documents/commit/84bbe5607dc96f330d38=30578454741c2ea61fcd> ">https://github.com/cabforum/documents/commit/84bbe5=

607dc96f330d3830578454741c2ea61fcd</a> =

<o:p></o:p></p></div></body></html>

------=_NextPart_001_0038_01D1A548.30B658A0--

_______________________________________________
Policyreview mailing list
Policyreview at cabforum.org
https://cabforum.org/mailman/listinfo/policyreview

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 
Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/policyreview/attachments/20160506/54c95a66/attachment-0001.html 