Versions Compared

Key

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

...

  • They are looking to operationalize the Baseline Expectations for Trust in Federation. The Baseline expectations of Identity Providers, Service Providers and Federation Operators, was approved by Incommon Assurance Advisory Committee and they are now working on the implementation plan. Final Version: https://spaces.internet2.edu/display/InCAssurance/Baseline+Expectations+for+Trust+in+Federation
  • Multifactor profile. Incommon has approved a profile for that and now has shared it with REFEDS, which will ratify it as one of their standards, so name space will be an international name space, profile will be able to be asserted internationally.
  • Open ID Connect for Federation. Implications on Assurance. There are several mobile use cases. Federation with OpenIdConnect specification (sent to the mailing list during the call): https://github.com/rohe/pyoidc/blob/master/oidc_fed/oidcfed.txt

 

 

IAWG Update

...

  • Working on alignment across the TFPs.
  • ICAM Day is scheduled for next March, probably will be a 2-day session. They stressed Peter Alterman good suggestions to include additional partners, to talk about digital signatures and encryption.
  • They had a meeting with Australian Access Federation, where they addressed several issues related to research and education area, OpenId Connect and attributes. They also reviewed some of their tools.
  • They have made progress on the Draft standard operating procedures and hope to share it by the end of October.
  • Planning the 800-63-3 update implementation.