Difference between revisions of "Research:Beacon"
| Line 11: | Line 11: | ||
==== IPv6 Beacon ==== | ==== IPv6 Beacon ==== | ||
| − | As of | + | As of April 1, we've submitted requests to ARIN for two independent /48s of IPv6 space. |
==== ASN Beacon ==== | ==== ASN Beacon ==== | ||
As of March 31, we've been approved for both a 16-bit and a 32-bit ASN, and we're waiting to receive the invoices for them before they can be issued. | As of March 31, we've been approved for both a 16-bit and a 32-bit ASN, and we're waiting to receive the invoices for them before they can be issued. | ||
Revision as of 07:09, 1 April 2022
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.
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: 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 will presumably need to get TLS certs for them as well.
IPv4 Beacon
As of March 31, we have secured a donor for two independent IPv4 /24s, our new ARIN OrgID, SANCT-7, is active, the transfer has been initiated, and we're waiting for RIPE to contact ARIN's 8.4 transfer group.
IPv6 Beacon
As of April 1, we've submitted requests to ARIN for two independent /48s of IPv6 space.
ASN Beacon
As of March 31, we've been approved for both a 16-bit and a 32-bit ASN, and we're waiting to receive the invoices for them before they can be issued.
