For further details about AS3320 please navigate through the tabs or check out a more extensive profile at Robtex.
Data downloaded from whois.ripe.net
aut-num: AS3320 as-name: DTAG org: ORG-DTA2-RIPE descr: Internet service provider operations remarks: peering coordinators for AS3320: remarks: abuse reports should be sent to the contacts listed in the registry entries for the IP address of the offending host system remarks: We share the view that for many networks (including ours:-) only some abstraction of the actual routing policy should/can be published in the IRR. Right now we are abstracting to a very essential minimum. remarks: the most important and helpful use of the IRR is to publish what a network will announce to peers and upstream # we are providing that by means of the AS-set AS3320:AS-DTAG which we have been keeping up to date all the time remarks: we encourage all our neighbors to define and maintain an AS-set to describe their announcements, and to register all the routes (and have their customers do so as well) import: from AS-ANY accept ANY # heavy abstraction hits! well, we are ... neither peering promiscuously nor accepting all junk routes offered... remarks: we maintain a list of what our neighbors have told us about their announcements towards AS3320 - in terms of AS-set (preferred), AS number, route-set (and the IRR database used to publish) remarks: in fact we apply route filters based on this for all neighbors - as far as feasible remarks: for data published through the RIPE routing registry we generate filters automatically remarks: we consider the integration of RIR and routing registry data and the application of RPSS authorization a great feature of the RIPE routing registry # unfortunately this benefit is not available with any other IRR database that we know of... and some of the IRR databases allow essentially any garbage to be registered without any control - making those databases quite useless... export: to AS3320:AS-CUSTOMERS announce ANY # but don't publish that list in general - if they ask for less, we can do export: to AS-ANY announce AS3320:AS-DTAG # for peers and others... for backwards compatibility the older AS-DTAG will be kept around for some more time - defined using just members: AS3320:AS-DTAG please convert to AS3320:AS-DTAG if you are still using the old AS-DTAG remarks: customers are strongly encouraged to define and maintain an AS-set that we will include in the definition of AS3320:AS-DTAG (if we are told the name) remarks: this will be sufficient to have our peers accept the routes remarks: in any case peers - and any network in the Internet - is free to apply some selective policy (e.g. prefix length based) # but we do not think that any such selective policy will be based on details of our routing policy omitted from this aut-num: object remarks: unfortunately some customers do not provide usable IRR data we will NOT add to the uncontrolled garbage in the IRR by proxy registering in some database that requires no authorization remarks: we advise customers that routes without IRR registration and not covered by AS3320:AS-DTAG may receive less than full support by some of our peer networks and other parts of the Internet remarks: ============================================================== IPv6 we do/publish essentially the same like for IPv4 mp-import: afi ipv6.unicast from AS-ANY accept ANY # heavy abstraction... neither peering promiscuously nor accepting all junk routes offered... mp-export: afi ipv6.unicast to AS3320:AS-CUSTOMERS-V6 announce ANY # but don't publish that list in general - if they ask for less, we can do mp-export: afi ipv6.unicast to AS-ANY announce AS3320:AS-DTAG-V6 # for peers and others... remarks: ============================================================== admin-c: SB15220-RIPE tech-c: SB15220-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: DTAG-RR created: 1970-01-01T00:00:00Z last-modified: 2020-12-11T15:33:02Z source: RIPE