|
|
| (One intermediate revision by the same user not shown) |
| 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]]. |
| − | | |
| − | ==== 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 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.
| |
Latest revision as of 06:56, 31 March 2022
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 welcome to join, or you can consult its archives of past discussion) and its findings and documentation will be published here.
Beacon
Documentation of the beacon can be found here.
