Whois

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to 'AS8192 - AS8523'

as-block:       AS8192 - AS8523
descr:          RIPE NCC ASN block
remarks:        These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by:         RIPE-NCC-HM-MNT
created:        2018-11-22T15:27:23Z
last-modified:  2018-11-22T15:27:23Z
source:         RIPE

% Information related to 'AS8315'

% Abuse contact for 'AS8315' is '[email protected]'

aut-num:        AS8315
as-name:        ACNBB
remarks:        Accenture Backbone
remarks:        https://www.accenture.com
remarks:        ==============================================================
remarks:        Please find our peering details at
remarks:        http://as8315.peeringdb.com/
remarks:        ==============================================================
remarks:        We have an open peering policy and would like to peer with
remarks:        you. Please send requests to [email protected].
remarks:        ==============================================================
remarks:        NOC: [email protected]
remarks:        Abuse: [email protected]
remarks:        ==============================================================
remarks:        We share the view that for many networks ( including ours:-) )
remarks:        only some abstraction of the actual routing policy should/can
remarks:        be published in the IRR.
remarks:        Right now we are abstracting to a very essential minimum.
remarks:        the most important and helpful use of the IRR is
remarks:        to publish what a network will announce to peers and upstream
remarks:        we are providing that by means of the AS-set AS8315:AS-SENTIA
remarks:        which we have been keeping up to date all the time
remarks:        we encourage all our neighbors to define and maintain an
remarks:        AS-set to describe their announcements, and to register
remarks:        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
remarks:        about their announcements towards AS8315 - in terms of
remarks:        AS-set (preferred), AS number, route-set
remarks:        (and the IRR database used to publish)
remarks:        in fact we apply route filters based on this
remarks:        for all neighbors - as far as feasible
remarks:        for data published through the RIPE routing registry
remarks:        we generate filters automatically
remarks:        we consider the integration of RIR and routing registry data
remarks:        and the application of RPSS authorization a great feature
remarks:        of the RIPE routing registry
remarks:        unfortunately this benefit is not available with any
remarks:        other IRR database that we know of...
remarks:        and some of the IRR databases allow essentially any garbage
remarks:        to be registered without any control - making those databases
remarks:        quite useless...
export:         to AS8315:AS-ACNBB announce ANY # but don't publish that list; in general - if they ask for less, we can do
export:         to AS-ANY announce AS8315:AS-ACNBB # New AS SET
remarks:        customers are strongly encouraged to define and maintain
remarks:        an AS-set that we will include in the definition
remarks:        of AS8315:AS-ACNBB (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 -
remarks:        is free to apply some selective policy (e.g. prefix
remarks:        length based)
remarks:        but we do not think that any such selective policy
remarks:        will be based on details of our routing policy omitted
remarks:        from this aut-num: object
remarks:        unfortunately some customers do not provide usable IRR data;
remarks:        we will NOT add to the uncontrolled garbage in the IRR by
remarks:        proxy registering in some database that requires no
remarks:        authorization
remarks:        we advise customers that routes without IRR registration
remarks:        and not covered by AS8315:AS-ACNBB may receive less than
remarks:        full support by some of our peer networks and other
remarks:        parts of the Internet
remarks:        ==============================================================
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 AS8315:AS-ACNBB 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 AS8315:AS-ACNBB # for peers and others...
remarks:        ==============================================================
org:            ORG-ABV1-RIPE
admin-c:        ACN1337-RIPE
tech-c:         ACN1337-RIPE
abuse-c:        ABAR3-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         ACNBB-MNT
created:        2006-01-05T09:59:28Z
last-modified:  2023-05-31T11:10:32Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.117 (SHETLAND)

Prefix

Peers