Research Group - Revision history

Woody at 06:56, 31 March 2022

2022-03-31T06:56:20Z

Woody: /* Beacon */

2022-03-30T13:28:27Z

Beacon

Woody: /* Domain Beacon */

2022-03-28T01:56:27Z

Domain Beacon

Woody: /* Beacon */

2022-03-28T01:54:56Z

Beacon

Wadmin at 13:30, 19 March 2022

2022-03-19T13:30:12Z

Wadmin: Created page with "The '''research group''' is responsible for designing and implementing the metrics and monitoring of the system and its effectiveness, and for liaison with the academic commun..."

2022-03-19T13:28:36Z

Created page with "The '''research group''' is responsible for designing and implementing the metrics and monitoring of the system and its effectiveness, and for liaison with the academic commun..."

New page

The '''research group''' is responsible for designing and implementing the metrics and monitoring of the system and its effectiveness, and for liaison with the academic community who use those metrics.

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

----

=== Beacon ===
The design of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus.

← Older revision		Revision as of 06:56, 31 March 2022
Line 6:		Line 6:

	=== Beacon ===		=== Beacon ===
−	~~The design~~ of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus. It is intended to allow independent verification of IPv4 and IPv6 routing and domain name resolution, and to be robust against orthogonal DNSSEC validation errors.	+	Documentation of [[Research:Beacon\|the beacon can be found here]].
−
−	~~Generally, our goal is to use two of each type of beacon, on independent and unrelated infrastructure, with one strobing on a one-hour period.~~
−
−	~~==== Domain Beacon ====~~
−	~~We have registered two domain names for this purpose:~~ [~~http://sanctions-beacon.net sanctions-beacon.net] and~~ [~~http~~:~~//sanctions-beacon.com sanctions-beacon.com]. Each will be set up to host~~ the ~~necessary responders, on two different independent network connections, using IP addresses not in any of our~~ beacon ~~IP address blocks. We will presumably need to get TLS certs for them as well.~~
−
−	~~==== IPv4 Beacon ====~~
−	~~As of March 30, we have secured a donor for two independent IPv4 /24s, and are awaiting the linking of our new ARIN OrgID, SANCT-7, with the role accounts, so that we~~ can ~~get the transfer initiated.~~
−
−	~~==== IPv6 Beacon ====~~
−	~~As of March 30, we're waiting for the completion of the ARIN account setup, but have an informal confirmation that we'll~~ be ~~approved for two IPv6 /48s.~~
−
−	~~==== ASN Beacon ====~~
−	~~As of March 30, we're waiting for the completion of the ARIN account setup, but have an informal confirmation that we'll be approved for two independent ASNs, one 16-bit, the other 32-bit~~.

@@ Line 7: / Line 7: @@
 === Beacon ===
 The design of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus. It is intended to allow independent verification of IPv4 and IPv6 routing and domain name resolution, and to be robust against orthogonal DNSSEC validation errors.
 ==== Domain Beacon ====
@@ Line 12: / Line 14: @@
 ==== IPv4 Beacon ====
-As of March 28, we're in process of getting two independent IPv4 /24s.
+As of March 30, we have secured a donor for two independent IPv4 /24s, and are awaiting the linking of our new ARIN OrgID, SANCT-7, with the role accounts, so that we can get the transfer initiated.
 ==== IPv6 Beacon ====
-As of March 28, we're in process of getting two independent IPv6 /48s.
+As of March 30, we're waiting for the completion of the ARIN account setup, but have an informal confirmation that we'll be approved for two IPv6 /48s.
 ==== ASN Beacon ====
-As of March 28, we're in process of getting two independent ASNs, one 16-bit, the other 32-bit.
+As of March 30, we're waiting for the completion of the ARIN account setup, but have an informal confirmation that we'll be approved for two independent ASNs, one 16-bit, the other 32-bit.

@@ Line 9: / Line 9: @@
 ==== Domain Beacon ====
-We have registered two domain names for this purpose: sanctions-beacon.net and sanctions-beacon.com. Each will be set up to host the necessary responders, on two different independent network connections, using IP addresses not in any of our beacon IP address blocks.
+We have registered two domain names for this purpose: [http://sanctions-beacon.net sanctions-beacon.net] and [http://sanctions-beacon.com sanctions-beacon.com]. Each will be set up to host the necessary responders, on two different independent network connections, using IP addresses not in any of our beacon IP address blocks. We will presumably need to get TLS certs for them as well.
 ==== IPv4 Beacon ====

← Older revision		Revision as of 01:54, 28 March 2022
Line 7:		Line 7:
	=== Beacon ===		=== Beacon ===
	The design of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus. It is intended to allow independent verification of IPv4 and IPv6 routing and domain name resolution, and to be robust against orthogonal DNSSEC validation errors.		The design of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus. It is intended to allow independent verification of IPv4 and IPv6 routing and domain name resolution, and to be robust against orthogonal DNSSEC validation errors.
		+
		+	==== Domain Beacon ====
		+	We have registered two domain names for this purpose: sanctions-beacon.net and sanctions-beacon.com. Each will be set up to host the necessary responders, on two different independent network connections, using IP addresses not in any of our beacon IP address blocks.
		+
		+	==== IPv4 Beacon ====
		+	As of March 28, we're in process of getting two independent IPv4 /24s.
		+
		+	==== IPv6 Beacon ====
		+	As of March 28, we're in process of getting two independent IPv6 /48s.
		+
		+	==== ASN Beacon ====
		+	As of March 28, we're in process of getting two independent ASNs, one 16-bit, the other 32-bit.

← Older revision		Revision as of 13:30, 19 March 2022
Line 6:		Line 6:

	=== Beacon ===		=== Beacon ===
−	The design of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus.	+	The design of the beacon which will be used to verify operation and reach of the program is currently underway on the mailing list, and will be described here when it reaches stable consensus. It is intended to allow independent verification of IPv4 and IPv6 routing and domain name resolution, and to be robust against orthogonal DNSSEC validation errors.