[cabfpub] Associate Member status and meeting participation by related entities

Sat May 26 01:25:32 UTC 2018

Hi Kirk,

I'm not sure what/if/how this solves any challenges we'd discussed. Is the
assumption that if such an organization requested of the Chair to be an AM,
that the chair would decline, and suggest they could only be an IP?

I'm mostly trying to understand the problem, as you see it, that this seeks
to solve. I think there was some confusion around that on the call, and I
don't quite see that articulated here.

On Fri, May 25, 2018 at 8:39 PM, Kirk Hall via Public <public at cabforum.org>
wrote:

> On our May 17 teleconference, we discussed the application of TUV-Austria
> (an ETSI auditing firm) for Associate Membership in the Forum.  There was
> unanimous agreement that TUV-Austria should participate in some way, but
> there was not consensus on what formal status the organization should have.
>
>
>
> The Forum’s past practice on admitting individual audit firms as Associate
> Members in their own name or as representatives of the audit scheme they
> follow (e.g., ETSI / ACABc) has not been consistent.  I’d like to discuss a
> possible Bylaws change to clarify this on our May 31 teleconference.
>
>
>
> *1.  Current Bylaw Provisions*
>
>
>
> Here are current Bylaws provisions.
>
>
>
> *3.1         Associate Members*
>
> The Forum may enter into associate member relationships with other
> organizations when the CA/Browser Forum determines that maintaining such a
> relationship will be of benefit to the work of the Forum.  *In the past,
> entities qualifying as Associate Members have included the AICPA/CICA
> WebTrust Task Force, the European Telecommunications Standards Institute,
> Paypal, the Internet Corporation for Assigned Names and Numbers, tScheme,
> the U.S. Federal PKI*, and CAs applying for membership but awaiting full
> qualification under Section 2.1.  Participation as an Associate Member is
> by invitation only.  In order to become an Associate Member, an
> organization must sign a mutual letter of intent, understanding, or other
> agreement and the Forum’s IPR Agreement, unless this latter requirement is
> waived in writing by the Forum based on overriding policies of the
> Associate Member’s own organization IPR rules.  *Associate Members may
> attend face-to-face meetings, communicate with Forum Members on member
> lists, and access Forum wiki content*.  Associate Members are not
> entitled to vote except on special straw polls of the Forum (e.g. when
> selecting meeting dates, locations, etc.)
>
>
>
> *3.2  Interested Parties*
>
>
>
> Any person or entity that wishes to participate in the Forum as an
> Interested Party may do so by providing their name, affiliation (optional),
> and contact information, and by agreeing to the IPR Agreement attached as
> Exhibit A (indicating agreement by manual signing or digitally signing the
> agreement).
>
>
>
> Interested Parties may participate in Forum activities in the following
> ways:
>
> (a)  By becoming involved in Working Groups,
>
> (b)  By posting to the Public Mail List, and
>
> (c)   By participating in those portions of Forum Teleconferences and
> Forum Meetings to which they are invited by the Forum Chair relating to
> their areas of special expertise or the subject of their Working Group
> participation.
>
> Interested Parties are required to comply with the provisions of the IPR
> Agreement and these Bylaws.  Interested Parties may lose their status as
> Interested Parties by vote of the Members, in the Members’ sole discretion.
>
>
>
> The biggest differences between Associate Member (AM) and Interested Party
> (IP) status are that AMs can participate on all Forum teleconferences,
> attend all meetings, and receive mailings on the Management@ list (which
> is generally limited to meeting logistics and review of draft Minutes).
> The Chair can invite IPs to participate in specific portions of
> teleconferences and meetings as warranted.
>
>
>
> *2.  Associate Members and their related entities*
>
>
>
> There are three main Associate Members who often have their own members or
> related entities participate in teleconferences and meetings, and not
> always at the specific invitation of the Chair: (1) WebTrust, (2)
> ETSI/ACABc, and (3) Federal PKI.  Some of the related entities of these AMs
> have been individual audit firms for WebTrust and ETSI/ACABc, and various
> government agencies and outside contractors for FPKI.
>
>
>
> Clearly the actual officers or representatives of an AM (like Jeff Ward
> and Don Sheehy for WebTrust, and Arno Fiedler and Nick Pope for ETSI)
> should be allowed to participate for those organizations without invitation
> by the Chair.  The situation has sometimes been less clear for FPKI, as the
> exact governing structure for that name appears to be a “network” and not
> an entity:
>
>
>
> *What is the Federal PKI?  *https://fpki.idmanagement.gov/
> #what-is-the-federal-pki
>
> The Federal PKI is a network of hundreds of certification authorities
> (CAs) that issue:
>
> ·       PIV credentials and person identity certificates
>
> ·       PIV-Interoperable credentials and person identity certificates
>
> ·       Other person identity certificates
>
> ·       Enterprise device identity certificates
>
> The participating Certification Authorities and the Policies, Processes,
> and Auditing of all the participants is referred to as the Federal Public
> Key Infrastructure (FPKI).
>
> The FPKI includes US federal, State, Local, Tribal, Territorial,
> international governments, and commercial organizations who work together
> to provide services for the benefit of the federal government.
>
>
>
> Deborah Gallagher signed our IPR Agreement in 2013 as “Chair, Federal PKI
> Policy Authority”.
>
>
>
> How should other audit firms like TUV-Austria or WebTrust qualified
> auditors who want to attend meetings or calls be classified?  Clearly they
> must first sign our current IPR Agreement, but do they attend as “Associate
> Members” under the status of their supervising organization, or do they
> attend only as Interested Parties who need the invitation of the Chair each
> time?  And how do we treat the various related entities who work on the
> FPKI network?
>
>
>
> *3.  Suggested Approach*
>
>
>
> The situation has not been abuses in the past, but we should create a
> clearer set of rules.  In my opinion, we should delegate to the existing
> Associate Members which related entities can participate on a regular
> basis, without the specific invitation of the Chair in each case.
>
>
>
> I suggest we add a sentence to Bylaw 3.1 – Associate Members that allows
> Associate Members themselves to designate representatives of related
> entities to participate in teleconferences and attend meetings under the
> status of the designating Associate Member (but in their own name, not the
> name of the Associate Member), and only after signing the current IPR
> Agreement.  This would allow, for example, WebTrust to authorize
> participation by individual auditors who are not actual WebTrust officers,
> the same for ETSI/ACABc, and possibly the same for FPKI.  We would first
> have to determine who actually speaks for FPKI as a “network” and would
> have the authority to designate representatives of related entities who
> could participate under FPKI’s Associate Member status.
>
>
>
> To do this, we could add the following new paragraph at the end of Bylaw
> 3.1 – Associate Members:
>
>
>
> Associate Members may designate representatives of their related entities
> (including their members or network members) to participate in Forum
> teleconferences and meetings on an ongoing or on a limited basis with the
> same rights as an Associate Member, and may remove such designations at any
> time.  The related entities must sign the Forum’s applicable IPR Agreements
> and must participate in their own names and not as representatives of the
> Associate Members who designated them.  In the event that too many related
> entities are designated by an Associate Member in the Chair’s opinion, the
> Chair may limit the number of related entities that an Associate Member may
> designate under this provision.
>
>
>
> We will discuss this on our May 31 teleconference.  I welcome other ideas.
>
>
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20180525/ee7175ac/attachment-0003.html>