Page tree
Skip to end of metadata
Go to start of metadata

Per-Entity Metadata Working Group - 2016-10-19
Agenda and Notes

[Etherpad used to create these notes: Agenda_and_Notes_-_2016-10-19.etherpad]

Dial in from a Phone:
 Dial one of the following numbers:
  +1.408.740.7256
  +1.888.240.2560
  +1.408.317.9253
 195646158 #
 Meeting URL (for VOIP and video):  https://bluejeans.com/195646158
 Wiki space:  https://spaces.at.internet2.edu/x/T4PmBQ

Attendees

  • David Walker, InCommon / Internet2
  • Ian Young
  • Michael Domingues, University of Iowa
  • Nick Roy, InCommon / Internet2
  • Chris Hubing / Internet2
  • IJ Kim / Internet2
  • Scott Koranda/LIGO
  • Scott Cantor, tOSU
  • Rhys Smith, Jisc
  • Tom Mitchell, GENI
  • Tom Scavo, InCommon/Internet2
  • Ann West, InCommon/Internet2


Agenda and Notes

  1. NOTE WELL: All Internet2 Activities are governed by the Internet2 Intellectual Property Framework. - http://www.internet2.edu/policies/intellectual-property-framework/
  2. NOTE WELL: The call is being recorded.
  3. Agenda bash
  4. Client libraries with multiple DNS A and AAAA records
    1. http://marc.info/?l=shibboleth-dev&m=147639642710536&w=2
    2. Maybe libcurl? https://github.com/curl/curl/blob/master/lib/connect.c#L1156
  5. Finalizing our report - https://docs.google.com/document/d/1MSRAO6FkEltsIM0E9X5y7dnfalephiaIvS1ZE2WTeFM/edit?usp=sharing
    1. Is tone of the report OK for the community, or is it too specific to Ops?
      1. We'll keep it fairly detailed, but we will use the Executive Summary and appendixes to keep the big messages from getting lost.
    2. Post-meeting notes of significant edits
      1. We'll add specific requirements/targets like % availability to the executive summary.
      2. We haven't said much about cache timeoutes.  TomS will query the list for what we want to say.
      3. ScottC will revise section 5.4 (Security Related Risks)
      4. TomS will revise the description of the overall metadata production/publishing/distribution environment and how it changes with MDQ.  Some of this may go into an appendix.
      5. In the discussion of CDN / "traditional" distribution layers, we'll emphasize that the important thing is to have primary and backup services to achieve the availability we need.  Each of the primary and secondary services might be CDN or "traditional," and that mix might change over time.
      6. We will add the "Parking Lot" items to the report, probably in an appendix.
        1. The concept of local/campus distribution is in some of our diagrams, too.
    3. We decided to go out for community review after next week's call.
      1. We'll give two weeks for the review, which will allow us to finish up in November.

 

  • No labels