Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Agreed to  move forward  with Monday July 19, 2021 for adoption of Baseline Expectation V2
    • InCommon staff will Update the InCommon Website
    • Replace with new Baseline Expectations text
    • InCommon Federation will switch to enforcement mode
    • Entities will need to meet BEv2 to be submitted
      • Does not impact existing entities that are not “touched”
    •  InCommon Federation Manager will get updated with greater clarity around encryption
  • NIH Requirements 
  • Next Phase for BEv2
    • After July 16 we begin next phase  
    • Assemble list of non adhering entities (list already exists)
    • Need to schedule and conduct office hours, this will help organizations not in compliance
    • Office hours suggested for August, September, October  and November
    • Suggestion to hold office hours on the alternate weeks from CTAB meetings (Tuesdays at 1pm ET)
    • Albert: Internet2 Marcomm group is ready to help CTAB publicize BEv2 and funnel those with issues to office hours 
    • August 2021 - begin publishing list of non adhering entities
      •  may want to revisit this if list continues to be very large
    • Perhaps publish list of organization that are adhering, at least to Site Admins and Execs
    • August 2021 - resume bi weekly notifications with a new message, more targeted
    • September 2021 - start tracking using ? pages, once the list is down to 100 or fewer
    • Last time, for BEV1, we created wiki pages and assigned them to CTAB members to contact non adhering organizations
    • Do not want to begin that with a list over 100
    • October 2021 - engagement begins

  •  Extensions for BEv2
    • For BEv1, we posted a web form where orgs could request an extension, for after Dec 2021 
    • Albert has received emails stating that organizations can’t adhere to BEv2 by July 19 but do plan to adhere to BEv2 by end of summer 2021
      • Extension Request Form will be available when CTAB starts nudging outreach
    • Concern about hard deadline right before the winter break
    • For BEv1, there was a December 2018 deadline, but  CTAB did not suggest to InCommon Steering to remove any entities until February 2019

  • SIRTFI and BEv2
    • It was noted that SIRTFI is fuzzier than the other new BEv2 requirements
    • TomB: From the point of view of the SIRTFI working group, the degree to which SIRTFI requirements are met is a business decision.  It is rare for everything to be perfectly implemented at all times.  It’s about due diligence

  • Wiki Updates and other communication
    • Albert : we will continue to refine the wiki
    • Albert will publish the next steps on a wiki page for the community
    • Albert is working with Internet2 Marcomm on case studies, showing solutions to issues in fulfilling BEv2
    • There will be a communication on July 17, stating we have transitioned to BEv2

  • More on Next Steps for BEv2 
    • Generally follow processes/flow from BEv1 closing
    • Revive community dispute docket described here: https://www.incommon.org/federation/dispute-resolution/
    • Develop next round of notification email templates
    • Get ready to publish non-adhering entities/orgs
    • Ready extension request submission/tracking
    • Schedule office hours (for Fall and Winter, monthly?)
    • On July 19 - officially publish BE2 text on web site
    • TBD: how will we actually measure “Encryption” when it comes to entity removal time, what are the operational implications of each option?

...