diff --git a/data/as-set/AS4242420119:AS-TRANSIT b/data/as-set/AS4242420119:AS-TRANSIT
index d987de76a..17aff46bd 100644
--- a/data/as-set/AS4242420119:AS-TRANSIT
+++ b/data/as-set/AS4242420119:AS-TRANSIT
@@ -1,10 +1,6 @@
 as-set:             AS4242420119:AS-TRANSIT
 remarks:            DRATHIR-MNT
 members:            AS4242423759
-remarks:            ALTF4-MNT
-members:            AS4242422935
-remarks:            ELOKO-MNT
-members:            AS4242423298
 remarks:            KRSTN-MNT
 members:            AS4242423723
 remarks:            SKYNET-MNT (IO)
diff --git a/data/aut-num/AS4242420119 b/data/aut-num/AS4242420119
index 26d95c424..53f8b0c59 100644
--- a/data/aut-num/AS4242420119
+++ b/data/aut-num/AS4242420119
@@ -3,6 +3,7 @@ as-name:            JRB0001
 admin-c:            JRB0001-DN42
 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:            - 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.
@@ -12,6 +13,18 @@ remarks:            - The peering must not be down for longer periods of time. F
 remarks:            - The round trip time between the border routers must be reasonable. This is not required for simple downstreams.
 remarks:            - Issues in the peer AS can result in the peering being disabled. If this is the case, the peer has to request the reactivation of the peering after all issues are resolved.
 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:            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.
+remarks:            Custom communities for debugging assistance:
+remarks:            - (4242420119, 1000, n)    Route entered AS on node n.
+remarks:            - (4242420119, 2000, n)    Route left AS on node n.
+remarks:            Other attributes:
+remarks:            - The MED is currently set to the estimated latency of the inbound peering, internal links and the outbound peering plus 1000 * path length. This might change in the future.
+remarks:            
 mp-import:          afi any.unicast from AS4242420119:AS-TRANSIT accept ANY
 mp-export:          afi any.unicast to AS4242420119:AS-TRANSIT announce ANY
 mp-import:          afi any.unicast from AS4242420119:AS-PEER accept PeerAS