CRXN
/
dn42_gateways
2
1
Fork 1
Code Issues Pull Requests Activity
Data for the dn42 / CRXN interconnection is stored here.
13 Commits
1 Branch
0 Tags
43 KiB
Ruby 100%
 
Go to file
Marek Küthe bc7ded72dc Merge pull request 'add a few empty lines' (#2) from mark22k/crxn-dn42-gateways:empty_lines into master 
Reviewed-on: #2
 		2023-01-29 13:39:57 +00:00
gateways replace tabs with spaces 2022-12-12 12:00:48 +01:00
scripts initial commit 2022-12-08 11:00:58 +01:00
README.md replace tabs with spaces 2022-12-12 12:00:48 +01:00
crxn_registry.json add a few empty lines 2023-01-29 14:37:51 +01:00
gateways.md initial commit 2022-12-08 11:00:58 +01:00

README.md

DN42 / CRXN interconnection

Data on the DN42 / CRXN interconnection is stored here. This includes the CRXN dummy ASN, the CRXN website and the operators of the gateways.

Gateways: gateways.md

Submit new gateway

If you want to run a gateway yourself, that's no problem. Create a file for it in the gateways folder. Execute (if you can) the generate_markdown_gateways.rb script in the scripts folder.

Specification

Gateway JSON object

{
    "dn42": {
        "asn": ["asn1", "asn2"],
        "contact": ["PERSON-DN42"]
    },
    "permission": "issued"
}
  • dn42
    • asn: Array of AS numbers that the operator will use to operate the gateway.
    • contact: An array of dn42 person or rule objects containing contact information to contact the operator.
  • permission: Every new operator needs the approval of the CRXN community. The following values are possible:
    • issued: The CRXN has agreed and the operator is allowed to operate the gateway.
    • denied: All objects with this status must be removed.