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

Merge pull request 'AS4242420119 peering maintenance' (#1911) from jrb0001/registry:maintenance into master

Browse source 
Reviewed-on: https://git.dn42.dev/dn42/registry/pulls/1911
Reviewed-by: schema-checker <schema-checker@noreply.dn42.us>
This commit is contained in:
Simon Marsh 2022-06-26 22:25:23 +01:00
commit 646e59c665
4 changed files with 12 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
data/as-set/AS4242420119:AS-PEER
View file

@ -1,5 +1,4 @@
as-set: AS4242420119:AS-PEER
members: AS4242420144
members: AS4242423905
admin-c: JRB0001-DN42
tech-c: JRB0001-DN42

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

@ -1,26 +1,21 @@
as-set: AS4242420119:AS-TRANSIT
members: AS64719
members: AS64737
members: AS64828
members: AS65043
members: AS4242420123
members: AS4242420138
members: AS4242420181
members: AS4242420207
members: AS4242420281
members: AS4242420656
members: AS4242420904
members: AS4242421191
members: AS4242421475
members: AS4242420197
members: AS4242420604
members: AS4242421080
members: AS4242421722
members: AS4242421926
members: AS4242421876
members: AS4242421955
members: AS4242422225
members: AS4242422237
members: AS4242422601
members: AS4242423360
members: AS4242423692
members: AS4242423723
members: AS4242423934
members: AS4242423966
members: AS4242423088
members: AS4242423618
members: AS4242423905
members: AS4242423914
admin-c: JRB0001-DN42
tech-c: JRB0001-DN42
mnt-by: JRB0001-MNT

2
data/as-set/AS4242421191:AS-TRANSIT
View file

@ -11,8 +11,6 @@ remarks: JOSENG-MNT
members: AS4242420789
remarks: WEITI-MNT
members: AS4242423905
remarks: JRB0001-MNT
members: AS4242420119
remarks: DTNET-MNT
members: AS4242421707
remarks: PF-MNT

4
data/aut-num/AS4242420119
View file

@ -5,7 +5,7 @@ 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 or multiprotocol BGP sessions are required, IPv4 BGP sessions are optional.
remarks: - All peerings must have a BGP session over IPv6. For new peerings, IPv4 is only supported via RFC4760 (multiprotocol extensions) and RFC5549 (extended next hop).
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 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.
@ -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 RFC8326 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: RFC1997, RFC3765, RFC7999 and RFC8326 are implemented as described in the RFC. Routes with the BLACKHOLE community are redistributed to other peers 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.