Operations Group - Revision history

Woody: /* Goals */

2022-04-18T08:19:36Z

Goals

Woody at 20:00, 9 April 2022

2022-04-09T20:00:51Z

Wadmin: Created page with "The '''operations group''' is responsible for the functioning of this web site (which is MediaWiki, reskinned by [https://opentechstrategies.com Open Tech Strategies]) and mai..."

2022-03-19T13:25:56Z

Created page with "The '''operations group''' is responsible for the functioning of this web site (which is MediaWiki, reskinned by [https://opentechstrategies.com Open Tech Strategies]) and mai..."

New page

The '''operations group''' is responsible for the functioning of this web site (which is MediaWiki, reskinned by [https://opentechstrategies.com Open Tech Strategies]) and mailing lists, the operational mechanism of the BGP and RPZ data feeds, and liaison with the Internet network operators who use them.

The work of the operations group is done on the operations mailing list (which you're [https://lists.sanctions.net/mailman/listinfo/operations welcome to join], or you can consult its [https://lists.sanctions.net/pipermail/operations/ archives of past discussion]) and documentation will be published here.

← Older revision		Revision as of 08:19, 18 April 2022
Line 5:		Line 5:
	== Goals ==		== Goals ==
	The long-term goal of the operations group is to provide a two-factor authenticated interface for each subscribing network operator, allowing them to select the specific jurisdictions in which they need to ensure sanctions compliance, such that the BGP and RPZ feeds they receive will contain exactly what's needed, and nothing more. The goal is to ensure compliance, without falling into ''over''compliance.		The long-term goal of the operations group is to provide a two-factor authenticated interface for each subscribing network operator, allowing them to select the specific jurisdictions in which they need to ensure sanctions compliance, such that the BGP and RPZ feeds they receive will contain exactly what's needed, and nothing more. The goal is to ensure compliance, without falling into ''over''compliance.
		+
		+	Because some jurisdictions issue partial exemptions, we currently imagine that the user interface will allow, for each jurisdiction, compliance selections of "full," "minimum," or "none."

← Older revision		Revision as of 20:00, 9 April 2022
Line 2:		Line 2:

	The work of the operations group is done on the operations mailing list (which you're [https://lists.sanctions.net/mailman/listinfo/operations welcome to join], or you can consult its [https://lists.sanctions.net/pipermail/operations/ archives of past discussion]) and documentation will be published here.		The work of the operations group is done on the operations mailing list (which you're [https://lists.sanctions.net/mailman/listinfo/operations welcome to join], or you can consult its [https://lists.sanctions.net/pipermail/operations/ archives of past discussion]) and documentation will be published here.
		+
		+	== Goals ==
		+	The long-term goal of the operations group is to provide a two-factor authenticated interface for each subscribing network operator, allowing them to select the specific jurisdictions in which they need to ensure sanctions compliance, such that the BGP and RPZ feeds they receive will contain exactly what's needed, and nothing more. The goal is to ensure compliance, without falling into ''over''compliance.