dn42/registry
1
0
Fork 0
mirror of https://git.dn42.dev/dn42/registry.git synced 2025-07-18 16:37:01 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update peering policy of AS4242420119

Browse source
This commit is contained in:
jrb0001 2018-06-03 21:40:46 +02:00
parent eda42279d7
commit 31d8f82f2e
No known key found for this signature in database
GPG key ID: F67487D78E3BEB1F
3 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

6
data/aut-num/AS4242420119
View file

@ -5,9 +5,9 @@ tech-c: JRB0001-DN42
mnt-by: JRB0001-MNT
remarks:
remarks: This AS is open for new peerings provided that the following requirements are met:
remarks: - At least two IPv6 BGP sessions are required, IPv4 BGP sessions are optional. Multiprotocol sessions are also possible.
remarks: - At least two IPv6 or multiprotocol BGP sessions are required, IPv4 BGP sessions are optional.
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 routing policy should 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.
remarks: - The peering must not be down for longer periods of time. Foreseeable downtime of more than one day should be coordinated.
remarks: - The round trip time between the border routers must be reasonable. This is not required for simple downstreams.
@ -15,7 +15,7 @@ remarks: - Issues in the peer AS can result in the peering being disa
remarks: Please contact the admin-c for peering requests and the tech-c for technical issues.
remarks:
remarks: Well-known communities:
remarks: RFC1997, RFC3765, RFC7999 and RFC8356 are implemented as described in the RFC. Routes with the BLACKHOLE community are redistributed to peers only if they implement the RFC as well.
remarks: RFC1997, RFC3765, RFC7999 and RFC8356 are implemented as described in the RFC. Routes with the BLACKHOLE community are redistributed to peers only if they implement the RFC7999 as well.
remarks: Custom communities for traffic engineering:
remarks: - (4242420119, 0, p) Do not announce to ASp.
remarks: - (4242420119, 1..16, p) Prepend x times before announcing to ASp.