OpenId Foundation Activites - Revision history

Antoniok at 18:52, 28 October 2015

2015-10-28T18:52:05Z

← Older revision		Revision as of 20:52, 28 October 2015
Line 59:		Line 59:
	\|-		\|-
	\| Web pages		\| Web pages
	\|		\| [http://openid.net/wg/risc/ http://openid.net/wg/risc/]
	\|-		\|-
	\| Documentation		\| Documentation

Antoniok at 18:50, 28 October 2015

2015-10-28T18:50:46Z

← Older revision		Revision as of 20:50, 28 October 2015
Line 7:		Line 7:
	<span style="line-height: 1.6;">"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. </span><span style="line-height: 1.6;">The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."</span>		<span style="line-height: 1.6;">"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. </span><span style="line-height: 1.6;">The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."</span>

	== <span style="font-size: larger; line-height: 1.2;">Current ~~Working~~ groups and projects</span> ==		== <span style="font-size: larger; line-height: 1.2;">Current working groups and projects related to privacy standards</span> ==

	=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===		=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===

Antoniok at 18:50, 28 October 2015

2015-10-28T18:50:16Z

← Older revision		Revision as of 20:50, 28 October 2015
Line 8:		Line 8:

	== <span style="font-size: larger; line-height: 1.2;">Current Working groups and projects</span> ==		== <span style="font-size: larger; line-height: 1.2;">Current Working groups and projects</span> ==



	=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===		=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===
Line 41:		Line 39:
	\|}		\|}

	=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">~~Risk~~ WG</span> ===		=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Risc WG</span> ===

	{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"		{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
Line 71:		Line 69:

	\|}		\|}
	~~<br/>~~

Antoniok at 18:49, 28 October 2015

2015-10-28T18:49:55Z

← Older revision		Revision as of 20:49, 28 October 2015
Line 30:		Line 30:
	\|-		\|-
	\| Web pages		\| Web pages
	\|		\| [http://openid.net/wg/heart/ http://openid.net/wg/heart/]
	\|-		\|-
	\| Documentation		\| Documentation
Line 40:		Line 40:

	\|}		\|}



	=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Risk WG</span> ===		=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Risk WG</span> ===

Antoniok at 18:48, 28 October 2015

2015-10-28T18:48:49Z

← Older revision		Revision as of 20:48, 28 October 2015
Line 3:		Line 3:
	== <span style="font-size: larger;">Introduction</span> ==		== <span style="font-size: larger;">Introduction</span> ==

	<span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 22.3999996185303px;">The objective of this page is to provide a high-level view of activities related to privacy standards in the OpenId foundation.</span>		<span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 22.3999996185303px;">The objective of this page is to provide a high-level view of activities related to privacy standards in the OpenId foundation.[http://openid.net/ http://openid.net/]</span>

	<span style="line-height: 1.6;">"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. </span><span style="line-height: 1.6;">The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."</span>		<span style="line-height: 1.6;">"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. </span><span style="line-height: 1.6;">The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."</span>

Antoniok at 18:47, 28 October 2015

2015-10-28T18:47:12Z

@@ Line 9: / Line 9: @@
 == <span style="font-size: larger; line-height: 1.2;">Current Working groups and projects</span> ==
-<span style="font-size: larger; line-height: 1.2;"></span>
 === <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===
@@ Line 40: / Line 40: @@
 |}
-|-
+=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Risk&nbsp;WG</span> ===
 {| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
@@ Line 80: / Line 52: @@
 | Overview
+|
-The HEART Working Group intends to harmonize and develop a set of privacy and security specifications that would enable an individual to manage the authorization, consent and release of their health related data via RESTful data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others<br/>List of current working documents / projects are as follows:
+The goal of RISC is to provide data sharing schemas, privacy recommendations and protocols to:
-|}
+Internet accounts that use email addresses or phone numbers as the primary identifier for the account will be the initial focus.
-{| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
+The working group is currently gathering the requirements and fit and gaps. One of the topics that the WG appreciate is the privacy aspect of the sharing of the account data.<br/>In essence, the specification will be describing how to notify the relevant parties when higher account compromise risk were observed. For example, an email provider may provide that the email account now has elevated risk state that the service provider that uses the address as the account reset address may stop using it for the time being. This will prevent the account compromise chain among the service providers and will help maintain the user’s privacy.<br/>If the relationship between the email provider above and the service provider is explicit and the user has opted in, then it should not be a problem. However, in most cases, they are implicit. It is conceivable to guide the user to opt-in to this kind of relationship at the next login, but the people who did not opted in will not be protected. If the opt-out was allowed, the first thing the attacker would do after compromising the account is to opt-out from the account risk information sharing so that he can take over the related accounts as well. From our evaluation, one of the best way is for the service provider to share the password reset etc. email address with the email provider in bulk and set up the information sharing path without opt-out option. This will give the greatest privacy protection / privacy risk ratio.
 |-
@@ Line 130: / Line 73: @@
 |}

Antoniok at 18:45, 28 October 2015

2015-10-28T18:45:02Z

← Older revision		Revision as of 20:45, 28 October 2015
Line 9:		Line 9:
	== <span style="font-size: larger; line-height: 1.2;">Current Working groups and projects</span> ==		== <span style="font-size: larger; line-height: 1.2;">Current Working groups and projects</span> ==

			<span style="font-size: larger; line-height: 1.2;"></span>

			=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===

			{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
			\|-
			\| Chair
			\| <br/>
			\|-
			\| Overview
			\|
			The HEART Working Group intends to harmonize and develop a set of privacy and security specifications that would enable an individual to manage the authorization, consent and release of their health related data via RESTful data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others<br/>List of current working documents / projects are as follows:

			* Health Relationship Trust Profile for OpenID Connect 1.0
			* Health Relationship Trust Profile for OAuth 2.0
			* Health Relationship Trust Profile for User Managed Access 1.0
			* Health Relationship Trust Profile for
			* Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 Scopes

			\|-
			\| Web pages
			\|
			\|-
			\| Documentation
			\|
			\|-
			\| Comments
			\|


			\|}
			<span style="font-size: larger; line-height: 1.2;"></span><span style="font-size: larger; line-height: 1.2;"></span>
			=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===

			{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
			\|-
			\| Chair
			\| <br/>
			\|-
			\| Overview
			\|
			The HEART Working Group intends to harmonize and develop a set of privacy and security specifications that would enable an individual to manage the authorization, consent and release of their health related data via RESTful data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others<br/>List of current working documents / projects are as follows:

			* Health Relationship Trust Profile for OpenID Connect 1.0
			* Health Relationship Trust Profile for OAuth 2.0
			* Health Relationship Trust Profile for User Managed Access 1.0
			* Health Relationship Trust Profile for
			* Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 Scopes

			\|-
			\| Web pages
			\|
			\|-
			\| Documentation
			\|
			\|-
			\| Comments
			\|


			\|}

			=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===

			{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
			\|-
			\| Chair
			\| <br/>
			\|-
			\| Overview
			\|
			The HEART Working Group intends to harmonize and develop a set of privacy and security specifications that would enable an individual to manage the authorization, consent and release of their health related data via RESTful data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others<br/>List of current working documents / projects are as follows:

			* Health Relationship Trust Profile for OpenID Connect 1.0
			* Health Relationship Trust Profile for OAuth 2.0
			* Health Relationship Trust Profile for User Managed Access 1.0
			* Health Relationship Trust Profile for
			* Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 Scopes

			\|-
			\| Web pages
			\|
			\|-
			\| Documentation
			\|
			\|-
			\| Comments
			\|


			\|}
			<span style="font-size: larger; line-height: 1.2;"></span>
	=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===		=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===

Antoniok at 18:43, 28 October 2015

2015-10-28T18:43:59Z

← Older revision		Revision as of 20:43, 28 October 2015
Line 38:		Line 38:

	\|}		\|}

	~~dddd~~
	~~=== ===~~

Antoniok at 18:43, 28 October 2015

2015-10-28T18:43:20Z

← Older revision		Revision as of 20:43, 28 October 2015
Line 39:		Line 39:
	\|}		\|}

			dddd
	=== ===		=== ===

Antoniok at 18:42, 28 October 2015

2015-10-28T18:42:55Z

← Older revision		Revision as of 20:42, 28 October 2015
Line 7:		Line 7:
	<span style="line-height: 1.6;">"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. </span><span style="line-height: 1.6;">The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."</span>		<span style="line-height: 1.6;">"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. </span><span style="line-height: 1.6;">The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."</span>

	== <span style="font-size: larger;">~~Some conventions on OpenId standards~~</span> ==		== <span style="font-size: larger; line-height: 1.2;">Current Working groups and projects</span> ==

	== <span style="font-size: ~~larger~~;~~">Technical Committees</span> ==~~		=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Heart WG</span> ===

	~~=== <span style="font~~-~~size~~: ~~larger~~;">AA</span> ===

	{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"		{\| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
	\|-		\|-
	\| Chair		\| Chair
	\| xx		\| <br/>
	\|-		\|-
	\| Overview		\| Overview
	\|		\|
	xx		The HEART Working Group intends to harmonize and develop a set of privacy and security specifications that would enable an individual to manage the authorization, consent and release of their health related data via RESTful data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others<br/>List of current working documents / projects are as follows:

			* Health Relationship Trust Profile for OpenID Connect 1.0
			* Health Relationship Trust Profile for OAuth 2.0
			* Health Relationship Trust Profile for User Managed Access 1.0
			* Health Relationship Trust Profile for
			* Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 Scopes

	\|-		\|-