| IP Netwerk - AS15544 |
| Adresbereik: |
AS15544 |
| Netwerknaam: |
DATAWAYS |
| Evenementen: |
registratielaatst gewijzigd |
| Naam van de klasse: |
autnum |
| Opmerkingen: |
| Onbepaald: |
DATAWAYS S.A.
Thessaloniki, Greece
27, Georgikis Scholis Ave. GR-57001
Tel: +30.2310953953
Fax: +30.2310953963
Web: https://www.dataways.gr
--------------- AS15544 / DATAWAYS S.A. ---------------
--------- PUBLIC IPv4/IPv6 BGP PEERING POLICY ---------
24x7 NOC Phone: +30.2310953966
General Info about DATAWAYS
===========================
DATAWAYS is a multiprotocol internet service provider
founded in 2000 by a team of IT professionals with many
years of technical expertise and knowledge in the area
of information technology and telecommunications.
The company has offices in Athens and Thessaloniki.
We provide IPv4/IPv6 transit with at least two major
carriers in every location. We are also member of Greek
Internet Exchange (GR-IX) and maintain peering agreements
with other Greek major networks and members of GR-IX.
We are ISO/IEC 27001:2013 certified and maintain a
security policy according to Greek/EU laws. We are also
a RIPE member since 2000 and we operate as a LIR.
We use the RIPE database as the primary IRR database
in which we register most of our objects.
The as-set which contains our own AS number and all our
customers' AS numbers is AS-DATAWAYS. Please use this
as-set if you do prefix filtering, unless otherwise noted.
Our PeeringDB record is at http://as15544.peeringdb.com
General Peering Policy Info
- We honor no-export and no-advertise well-known
communities.
- We do *NOT* honor the MED BGP attribute. All routes
received from our upstreams, customers or IX-peers on both
primary/backup routers get a metric of 0. Please see below
about our primary/backup scheme.
- bogon/martian prefixes are rejected on import.
- Prefixes containing a bogon/reserved/private AS number
in their as-path are rejected.
- We reject the default-route prefix (0/0, ::/0) from all
peers (upstreams/customers/IX-peers).
- Prefixes longer than /24 for IPv4 or /48 for IPv6
are rejected.
- We use BOTH prefix access lists and as-path access lists
for prefix filtering. Customers or IX-peers imported
prefixes must be registered with a valid route/route6
object in the RIPE database. The prefix must be originating
from the customer's AS or, in case the peer is an IX-peer,
the peer's AS and their adjacent AS if any.
All other advertisements are rejected.
Our filters are automatically updated every business-day
morning. Contact noc@dataways.gr for an irregular update.
Primary/Backup BGP Routers
==========================
DATAWAYS prefers to connect with other autonomous systems
using a cluster of bgp routers with at least two BGP
sessions for redundancy. Each session originates from a
different router. The first/primary session is maintained
on our primary-designated router while any other secondary
sessions use our backup(s) router(s).
Routes received from our peers on the primary router always
get a higher local preference than the backup router.
Our customers can fine-tune our local-preference values
using the appropriate community tags. See below.
Routes advertised to our peers have their metric set to 0
on primary and 20 on backup. If the remote AS does not
honor the MED attribute we follow the appropriate
technique as instructed by the remote AS import policy.
BGP Communities used by our Customers
=====================================
Our customers can use the following communities to
influence our BGP routers:
as-path prepend:
----------------
15544:5000 Prepend 5 times to all Upstreams
15544:5900 Prepend 5 times to all GR-IX Peers
local-preference override:
--------------------------
15544:7090 Set local-preference of customer's prefix
to very-low local-preference mode.
In normal operations the customer's announcements have
a higher local-preference value than IX-peers and
upstreams announcements.
The order is: [CUSTOMER] > [IX-PEERS] > [UPSTREAMS]
If you tag your advertisements with 15544:7090 then
the order changes to:
[IX-PEERS] > [UPSTREAMS] > [CUSTOMER]
In this mode, prefixes received from IX-peers and/or
from our upstreams are more preferred. A multi-homed
customer can utilize this mode to use us a
backup/last resort path.
Export Prefix Policy for our Customers
======================================
We advertise the following prefix-sets to our customers:
FIRT: advertise the entire global BGP routing table
GRIX: advertise only prefixes learned from our GR-IX peers.
RIPE: advertise only the RIPE-NCC prefix. This is
193.0.0.0/21 for IPv4 and 2001:67c:2e8::/48 for IPv6
and they both originating from AS3333.
default: advertise only the default route (0/0 or ::/0)
Customer can select/change any of the above sets by
e-mailing noc@dataways.gr.
Import/export policy in RPSL now follows. This is a
generic description of our current peering plan. No
strict filtering or local preference actions are
described. Use only for reference.
|
|
| Mededelingen: |
| Gefilterd: |
This output has been filtered.
|
| Whois-onnauwkeurigheidsrapportage: |
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 ( Onnauwkeurigheid-rapport ) |
| Bron: |
This output has been filtered.
If you see inaccuracies in the results, please visit:
Objects returned came from source
RIPE
|
| Voorwaarden: |
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 ( Servicevoorwaarden ) |
|
| Status: |
Actief |
| Links: |
https://rdap.db.ripe.net/autnum/15544 ( Zelf )
http://www.ripe.net/data-tools/support/documentation/terms ( Copyright )
|
| Whois-server: |
whois.ripe.net |
| Conformiteit: | nro_rdap_profile_asn_flat_0, cidr0, rdap_level_0, nro_rdap_profile_0, redacted |
IP
