https://docs.google.com/document/d/1cz8PJQ8IngRNsWPU02YuBQ7MKRdtUtI1lOeB-uh7TWw/edit?usp=sharing 

Attending: Zacharias T, Judith B, Nicole R, Nicole H, Phil S, Mary M, Gary W, Chris H, Meshna K, David H, IJ Kim, Paul C

  1. Agenda bash
  2. Why we’re doing this - very short
  3. Monday 13th meeting of FedCM CG: who can attend?
    1. Gary, Chris P, Judith
  4. Monday 20th meeting of FedCM CG: who can attend for each proposal?
    1. Zacharias, Judith, Phil S
  5. If you are working on proposals 
  6. Discuss a strategy for refining the proposals and the preamble (possible strategy below)
  7. Possible strategy
    1. Divide into three teams: storage API, federation Trust, and preamble
      1. Identify who on each team can attend the FedCM meetings on the 13th and the 20th
    2. Create three breakout rooms for the proposals and the preamble
    3. Preamble team refines the preamble as much as possible by the end of this meeting
      1. The Why was not clear - Heather summarized as “allow the browser to classify an exchange between an RP and an IdP as a legitimate federated login flow without interrupting the protocols and without requiring any one party to a federated authentication flow be fully trusted.”
    4. Proposal teams pick an editor
      1. Team walks through the document looking for places to improve
        1. Advice from Martin Thomas: “ …details of DOM APIs tend not to be helpful,...  better to lay out what information the browser would hold, how it would be protected, who can access it, etc....”
      2. Assign any longer improvements (diagrams, standardizing APIs, etc) to a person who will get the changes in before CET start of work on Mar 13
      3. After meeting ends
        1. Proposal editors take preamble and add to the document
        2. Assignments are completed and the editor notified task is complete
        3. Editors notify Zacharias when complete and Zacharias checks into FedCM proposal github

References


  • No labels