[cabfpub] Public Digest, Vol 69, Issue 118

Ryan Sleevi sleevi at google.com
Thu Feb 1 11:32:15 MST 2018


Hi Kirk,

As mentioned previously, these Review Notices don't comply with Section
2.4(e) of the Bylaws and our IPR Policy, Section 4.1

As per https://cabforum.org/wp-content/uploads/CABF-IPR-Policy-v.1.2.pdf
Prior to the approval of a CAB Forum Draft Guideline as a CAB Forum Final
Guideline or Final
Maintenance Guideline there shall be a review period during which
Participants may exclude
CA/B Forum Intellectual Property Rights Policy, v. 1.2 Page 2
certain Essential Claims from CAB Forum RF Licenses. The CAB Forum Chair
shall initiate the
Review Period by distributing to each CAB Forum Participant **a notice of
review period and a
complete draft of the Draft Guideline that is the subject of such notice
(“Review Notice”)**. Each
Participant on behalf of itself and its Affiliates shall have sixty (60)
days following the date of
the receipt of such Review Notice (“Review Period”) to review such Draft
Guideline and
consider any licensing obligations with respect to any Essential Claims
that may be encompassed
by such Draft Guideline. The approval of a CAB Forum Final Maintenance
Guideline shall
follow the same process except that the Review Period shall be thirty (30)
days.


I think the important part is "a complete draft of the Draft Guideline"

Not a redline, but the complete draft - the fully integrated text.


On Thu, Feb 1, 2018 at 1:28 PM, Kirk Hall via Public <public at cabforum.org>
wrote:

> Virginia – yes, we have been posting Review Notices for every ballot that
> changes the Guidelines since Ballot 190 to the Public list – just search on
> “Review Notice” and you should see them.  Here is an example.
>
>
>
> *From:* Public [mailto:public-bounces at cabforum.org] *On Behalf Of *Virginia
> Fournier via Public
> *Sent:* Wednesday, January 31, 2018 8:09 PM
> *To:* public at cabforum.org
> *Subject:* [EXTERNAL]Re: [cabfpub] Public Digest, Vol 69, Issue 118
>
>
>
> Hi - I don’t recall seeing any Review Notices sent out pursuant to Section
> 2.4(e) of the Bylaws.  What is happening with those?
>
>
>
>
>
> Best regards,
>
>
>
> Virginia Fournier
>
> Senior Standards Counsel
>
>  Apple Inc.
>
> ☏ 669-227-9595 <(669)%20227-9595>
>
> ✉︎ vmf at apple.com
>
>
>
>
>
>
>
>
>
>
>
> On Jan 27, 2018, at 4:20 PM, public-request at cabforum.org wrote:
>
>
>
> Send Public mailing list submissions to
>             public at cabforum.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>             https://cabforum.org/mailman/listinfo/public
> or, via email, send a message with subject or body 'help' to
>             public-request at cabforum.org
>
> You can reach the person managing the list at
>             public-owner at cabforum.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Public digest..."
>
>
> Today's Topics:
>
>   1. Updated CABF documents - Record of Review Notices (Kirk Hall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 28 Jan 2018 00:20:52 +0000
> From: Kirk Hall <Kirk.Hall at entrustdatacard.com>
> To: CA/Browser Forum Public Discussion List <public at cabforum.org>
> Subject: [cabfpub] Updated CABF documents - Record of Review Notices
> Message-ID:
>             <db5933c86e0a4825a58723cc548c3a67 at PMSPEX04.corporate.
> datacard.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I attached updated copies of the BRs, EVGL, and Bylaws in "show changes"
> mode, in both Word and pdf format.  Please review.  If there are no edits,
> we can finalize and post to the CABF website at the end of next week.
>
> A note on timing.  The changes to the BRs and EVGL all come from a single
> ballot, Ballot 217, which only became effective on Jan. 20, 2018 (a week
> ago).  Under our Bylaws, updated BRs and EVGLs should have been circulated
> by last Wednesday, so I am 3 days late - I apologize for any inconvenience.
>
> Our Bylaws do not specify any time limit on when updated copies of the
> Bylaws must be created and circulated, and these revised Bylaws include
> only the changes from Ballot 216, which became effective Dec. 21, 2017 -
> about five weeks ago.  Again, I apologize if anyone was inconvenienced by
> not receiving an updated copy of the Bylaws before today.
>
> I also attach a document "Record of Review Notices Since Ballot 190 (27
> Jan 2018)" which indicates there have been no Exclusion Notices filed on
> Guidelines ballots since Ballot 190.  Members were already aware of this,
> as anyone claiming an Exclusion Notice must post it to the Public list (and
> none have been posted since Ballot 190), but we will maintain and update
> this new document and send it out in the future on the Public list after
> the Review Period for each Guidelines ballot expires.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://cabforum.org/pipermail/public/attachments/
> 20180128/bffb6a85/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Record of Review Notices Since Ballot 190 (27 Jan 2018).pdf
> Type: application/pdf
> Size: 117077 bytes
> Desc: Record of Review Notices Since Ballot 190 (27 Jan 2018).pdf
> URL: <http://cabforum.org/pipermail/public/attachments/
> 20180128/bffb6a85/attachment.pdf>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Record of Review Notices Since Ballot 190 (27 Jan 2018).docx
> Type: application/vnd.openxmlformats-officedocument.
> wordprocessingml.document
> Size: 18341 bytes
> Desc: Record of Review Notices Since Ballot 190 (27 Jan 2018).docx
> URL: <http://cabforum.org/pipermail/public/attachments/
> 20180128/bffb6a85/attachment.docx>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public
>
>
> ------------------------------
>
> End of Public Digest, Vol 69, Issue 118
> ***************************************
>
>
>
>
> ---------- Forwarded message ----------
> From: Kirk Hall <Kirk.Hall at entrustdatacard.com>
> To: "CA/Browser Forum Public Discussion List" <public at cabforum.org>
> Cc:
> Bcc:
> Date: Thu, 21 Dec 2017 22:22:35 +0000
> Subject: Notice of Review Period – Ballot 217
>
> *NOTICE OF REVIEW PERIOD – BALLOT 217*
>
>
>
> This Review Notice is sent pursuant to Section 4.1 of the CA/Browser
> Forum’s Intellectual Property Rights Policy (v1.2).  This Review Period is
> for Final Maintenance Guidelines (30 day Review Period).  A complete draft
> of the Draft Guideline that is the subject of this Review Notice is
> attached.
>
>
>
> Date Review Notice Sent: December 21, 2017
>
>
>
> Ballot for Review:                          Ballot 217 – Sunset RFC 2527
>
>
>
> Start of Review Period:                 December 21, 2017 at 23:00 UTC
>
>
>
> End of Review Period:                  January 20, 2018 at 23:00 UTC
>
>
>
> Please forward any Exclusion Notice relating to Essential Claims to the
> Chair by email to kirk.hall at entrustdatacard.com before the end of the
> Review Period.  See current version of CA/Browser Forum Intellectual
> Property Rights Policy for details.
>
>
>
> *(Optional form of Exclusion Notice is attached)*
>
>
>
> *Ballot 217: Sunset RFC 2527*
>
>
>
> *-- MOTION BEGINS --*
>
>
>
> This ballot modifies the "Baseline Requirements for the Issuance and
> Management of Publicly-Trusted Certificates" as follows, based upon Version
> 1.5.1:
>
>
>
> In Section 2.2, replace the text:
>
>
>
> "The CA SHALL publicly disclose its Certificate Policy and/or
> Certification Practice Statement through an appropriate and readily
> accessible online means that is available on a 24x7 basis. The CA SHALL
> publicly disclose its CA business practices to the extent required by the
> CA's selected audit scheme (see Section 8.1). The disclosures MUST include
> all the material required by RFC 2527 or RFC 3647, and MUST be structured
> in accordance with either RFC 2527 or RFC 3647. "
>
>
>
> with the following:
>
>
>
> "The CA SHALL publicly disclose its Certificate Policy and/or
> Certification Practice Statement through an appropriate and readily
> accessible online means that is available on a 24x7 basis. The CA SHALL
> publicly disclose its CA business practices to the extent required by the
> CA's selected audit scheme (see Section 8.1).
>
>
>
> Effective as of 31 May 2018, the Certificate Policy and/or Certification
> Practice Statement MUST be structured in accordance with RFC 3647. Prior to
> 31 May 2018, the Certificate Policy and/or Certification Practice Statement
> MUST be structured in accordance with either RFC 2527 or RFC 3647. The
> Certificate Policy and/or Certification Practice Statement MUST include all
> material required by RFC 3647 or, if structured as such, RFC 2527."
>
>
>
>
>
> This ballot modifies the "Guidelines for the Issuance and Management of
> Extended Validation Certificates" as follows, based on Version 1.6.6:
>
>
>
> In Section 8.2.2, replace the text:
>
>
>
> "Each CA MUST publicly disclose their EV Policies through an appropriate
> and readily accessible online means that is available on a 24x7 basis.  The
> CA is also REQUIRED to publicly disclose its CA business practices as
> required by WebTrust for CAs and ETSI TS 102 042 and ETSI EN 319 411-1.
> The disclosures MUST be structured in accordance with either RFC 2527 or
> RFC 3647."
>
>
>
> With the following:
>
>
>
> "Each CA MUST publicly disclose its Certificate Policy and/or
> Certification Practice Statement through an appropriate and readily
> accessible online means that is available on a 24x7 basis. The CA SHALL
> publicly disclose its CA business practices to the extent required by the
> CA's selected audit scheme (see Section 17.1).
>
>
>
> Effective as of 31 May 2018, the CA's Certificate Policy and/or
> Certification Practice Statement MUST be structured in accordance with RFC
> 3647. Prior to 31 May 2018, the CA's Certificate Policy and/or
> Certification Practice Statement MUST be structured in accordance with
> either RFC 2527 or RFC 3647. The Certificate Policy and/or Certification
> Practice Statement MUST include all material required by RFC 3647 or, if
> structured as such, RFC 2527."
>
>
>
> *-- MOTION ENDS --*
>
>
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/public/attachments/20180201/d5b63453/attachment-0001.html>


More information about the Public mailing list