aut-num | AS268047 |
as-name | MASTERINFO |
descr | MASTERINFO INTERNET |
import | from AS268829 accept ANY |
import | from AS28343 accept ANY |
import | from AS263998 accept ANY |
mp-import | afi ipv6.unicast from AS268829 accept ANY |
mp-import | afi ipv6.unicast from AS28343 accept ANY |
mp-import | afi ipv6.unicast from AS263998 accept ANY |
export | to AS268829 announce AS268047:AS-MASTERINFO-ALL |
export | to AS28343 announce AS268047:AS-MASTERINFO-ALL |
export | to AS263998 announce AS268047:AS-MASTERINFO-ALL |
mp-export | afi ipv6.unicast to AS268829 announce AS268047:AS-MASTERINFO-ALL |
mp-export | afi ipv6.unicast to AS28343 announce AS268047:AS-MASTERINFO-ALL |
mp-export | afi ipv6.unicast to AS263998 announce AS268047:AS-MASTERINFO-ALL |
admin-c | Philipe Alves |
tech-c | Rudson Costa |
remarks | =============================================== |
remarks | 24 x 7 technical support regarding our BGP routing |
remarks | policies or any inquiries concerning AS268047's |
remarks | security and routing policies please reach out to us |
remarks | at the following channels: |
remarks | ============================================================ |
remarks | AS268047 Basic Interconnection Requirements |
remarks | ============================================================ |
remarks | ============================================================ |
remarks | The following is required from your organization in order to |
remarks | establish a BGP session with MASTERINFO at ASN 268047: |
remarks | - The customer must use a RIR assigned ASN. |
remarks | - The customer must have a route/route6 object for each prefix |
remarks | it intends to announce to us, which might include its own |
remarks | prefixes and, if desired, its customers' prefixes as well (customer cone). |
remarks | - Each route/route6 object corresponding to a customer prefix |
remarks | (yours or a prefix from your customer cone) must inform the |
remarks | correct ASN in its 'origin' field. |
remarks | - The ASN mentioned in the 'origin' field of each route and route6 |
remarks | object must have its proper and corresponding aut-num object. |
remarks | - The aforementioned aut-num objects must have a clear routing |
remarks | policy stating what as-sets are to be announced to us. |
remarks | - This as-set MUST be informed on PeeringDB ("IRR as-set/route-set") |
remarks | MASTERINFO strongly encourages you to use two simultaneous methods to |
remarks | validate the origin of the prefixes you announce to us: IRR and ROA |
remarks | (published in your RPKI regime). This is highly recommended because |
remarks | some of our direct upstreams and also indirect upstreams may reject |
remarks | any routes where there is a failure in the origin validation process. |
remarks | You can start this process by "cleaning up your own house first", then |
remarks | working directly with your customers so they can do their homework too, |
remarks | and, by doing that, we can all prevent route leaks and prefix hijacking |
remarks | from happening. :-) |
remarks | Last but not least, please feel free to contact us if you have any questions |
remarks | or need our assistance in working these best practices with you! |
remarks | We will definitely make ourselves available to increase the security of the |
remarks | Internet, your experience as our customer/partner, and in the best |
remarks | interest of our mutual agreement! |
remarks | ============================================================ |
mnt-by | MAINT-AS268829 |
changed | rudsoncosta@3rsolution.com.br 20231102 |
source | RADB |
last-modified | 2023-11-13T16:19:25Z |