| IP Red - AS3320 |
| Rango de direcciones: |
AS3320 |
| Nombre de red: |
DTAG |
| Eventos: |
registroúltimo cambio |
| Nombre de la clase: |
autnum |
| Observaciones: |
| Sin definir: |
Internet service provider operations
peering coordinators for AS3320:
abuse reports should be sent to the contacts listed in the registry entries for the IP address of the offending host system
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.
the most important and helpful use of the IRR is to publish what a network will announce to peers and upstream
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)
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)
in fact we apply route filters based on this for all neighbors - as far as feasible
for data published through the RIPE routing registry we generate filters automatically
we consider the integration of RIR and routing registry data and the application of RPSS authorization a great feature of the RIPE routing registry
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)
this will be sufficient to have our peers accept the routes
in any case peers - and any network in the Internet - is free to apply some selective policy (e.g. prefix length based)
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
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
============================================================== IPv6 we do/publish essentially the same like for IPv4
==============================================================
|
|
| Notas: |
| Filtrado: |
This output has been filtered.
|
| Informes de inexactitud de Whois: |
This output has been filtered.
If you see inaccuracies in the results, please visit:
https://www.ripe.net/contact-form?topic=ripe_dbm&show_form=true ( Informe de inexactitud ) |
| Origen: |
This output has been filtered.
If you see inaccuracies in the results, please visit:
Objects returned came from source
RIPE
|
| Términos y condiciones: |
This output has been filtered.
If you see inaccuracies in the results, please visit:
Objects returned came from source
RIPE
This is the RIPE Database query service. The objects are in RDAP format.
http://www.ripe.net/db/support/db-terms-conditions.pdf ( Términos de servicio ) |
|
| Estado: |
Activo |
| Enlaces: |
https://rdap.db.ripe.net/autnum/3320 ( Uno mismo )
http://www.ripe.net/data-tools/support/documentation/terms ( Copyright )
|
| Servidor Whois: |
whois.ripe.net |
| Conformidad: | nro_rdap_profile_asn_flat_0, cidr0, rdap_level_0, nro_rdap_profile_0, redacted |
IP
