AS4242420119 peering maintenance

### DN42 Signature
### method: ssh
### mntner: JRB0001-MNT
### text: 56404ffbb809240ecb892aedec7482b4f103d5dc
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAAhcAAAAHc3NoLXJzYQAAAAMBAAEAAAIBAOifnnBQf7Zorgs8rYijGi
cmJMr4AD1vDe+INyq+RPw7ipeh2v0hNEa8Eg7fosCtpRv+5vDqOL1R8C3mHiLCGiIwGsa4
pHKrek39yrJwVWSp1bmZKdeUvNsxWwyi2VM8TtRbOqi0YV4vmQvQerhqb7UsiS2nXg52+4
C/AOYwB8DMUERxjtKpzZC6roQbKKAGj2E1zcrYOlTGBvghnWrsULDsUez5sAw5uiVEbUL0
QxdC/C4xH00mt7OMFh+7prPBzryh3lcSy7SOGdJk1I8RVHJqkQci6upSn5y9rF1dDbb3rb
4BbrJ74tKGDju/3N5N2dwJr0MxGMNmg4+39byFs7RSkcBSsTRq//wBQHcUsVuVsu8M10Yc
flX8/BSC2/jluV/05gAGD+6nmXDUrgO6HBoD+msEi4iOiJP94LyR02sshrtaqEALu2iVzo
TipEJChJOUJlUg3VjdWxv5wm9zVgza4Kq43G6ZP2lifIDi1M2G942z5ZGk/cn4lEpl2lLK
1eofB5zI1XVefKbg+EJONCbgE6nQ92GOlLJmO29pMUQEiFqYqzpgHtDm0PgV6qN5b3imma
1kw3MIDYjzvQzuW0u6ioXjFwZPaEM+PQk1U9w7H/gbm2kS3QCKX+UBv2I6NNEIXWxwS6ln
mT9XdXXh9XAWkPthUf/2kysMG653zH1nAAAABGRuNDIAAAAAAAAABnNoYTUxMgAAAhQAAA
AMcnNhLXNoYTItNTEyAAACAFZ2SUBIg6rRhD4B729Xd3iaPlOT/DBYR2RkqE/EJEqS1fKE
LSOMGegXYgaUNQUhUHO6jathsYwscKgmghANEzzwIsk/B3XClMfk4upMJYf7kAgO4aCpKs
ImXBw2ueWS1CpIt/ByFatMlywuMzRwyzIJFSCusIOIqN2LiClC78VRE6YUQkwszS+ar4//
msEEOVtnec1bXijzIF3u/bDA5O/cOUJc/SNQr9xlxIQlrLMgn4C0s9wYVvZyqlGzv2ykpp
su85l+zvl8XjOBdfZvkQ+Kn/qPnr3l7XdshE3U1yE2FSzNkvAqjlnDyhgkSzPQDLDRtKh0
5ry39awQpqdkFlUHQKU5BBe8eIvG315ztS4qMogq/hJLlkFoUwnBZnKUDjMxL1tMuomUnA
9yxXWrAL+oQhLt9zW22F+L/d+v4JlChDCjvK9vH4qk+46AqVPbMRT0F/OkwD/d2/RZHBF4
XUG4mx/GOXAU8lMBjWG8hetdG5d56tQ8KChp3+OfGbTDZCDCc6U8Rx6RPTABc9uhy2sh1A
Ib1H98U9ujPdfYzYvC9ktNtjRkBpriRalclj6l4+ojrynX0lWErS37t5MXCv2LrfS4sDv8
3oM66r4ZPlT3OQnDsXYN+ZTBKSngw3ksAqIfc1Xg4fArJeuzQ6pQ5jM/sXXIvk7bJEGder
FbPiKo
-----END SSH SIGNATURE-----
This commit is contained in:
jrb0001 2022-06-26 22:07:02 +02:00
parent 150affa099
commit a3a5939bf1
4 changed files with 12 additions and 20 deletions

View file

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

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

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

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.