dn42/registry
1
0
Fork 0
mirror of https://git.dn42.dev/dn42/registry.git synced 2025-05-07 21:25:24 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update peering policy

Browse source
This commit is contained in:
jrb0001 2018-01-25 21:31:00 +01:00
parent 5319904b89
commit 0b8eda62a6
No known key found for this signature in database
GPG key ID: F67487D78E3BEB1F
2 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
data/as-set/AS4242420119:AS-TRANSIT
View file

@ -9,6 +9,12 @@ remarks: KRSTN-MNT
members: AS4242423723
remarks: SKYNET-MNT (IO)
members: AS4242420630
remarks: GRMML-MNT
members: AS4242420123
remarks: LUTOMA-MNT
members: AS64719
remarks: XUU-MNT
members: AS64737
admin-c: JRB0001-DN42
tech-c: JRB0001-DN42
mnt-by: JRB0001-MNT

2
data/aut-num/AS4242420119
View file

@ -6,7 +6,7 @@ mnt-by: JRB0001-MNT
remarks: This AS is used for the new infrastructure and will completely replace AS4242420117 and AS4242420118 in the near future.
remarks:
remarks: This AS is open for new peerings provided that the following requirements are met:
remarks: - At least two IPv6 sessions are required, IPv4 sessions are optional. Multiprotocol sessions are also possible.
remarks: - At least two IPv6 BGP sessions are required, IPv4 BGP sessions are optional. Multiprotocol sessions are also possible.
remarks: - The contact informations in the registry must always be up to date. The tech-c and admin-c must respond within one week and must read the mailing list.
remarks: - The routing policy must be properly documented in the registry within one week after the peering is established.
remarks: - The peer AS must have at least one other transit and/or upstream peer.