| IP Netzwerk - AS12883 |
| Adressbereich: |
AS12883 |
| Netzwerkname: |
UCOMLINE |
| Veranstaltungen: |
Anmeldungzuletzt geändert |
| Klassenname: |
autnum |
| Bemerkungen: |
| Nicht definiert: |
PRIVATE JOINT-STOCK COMPANY "FARLEP-INVEST"
********************************************************************
=> Transits
=> Peers
=> Customer peerings are not described in this object
Abuse reports to abuse@vegatele.com
Operational issues to noc@vegatele.com
Note that the import/export designations above are a simplification
of our actual policies which cannot be properly described given the
limitations of RPSL.
Note that the BGP community filtering scheme also conforms to
Internet-Draft . Only
non-standart communities that are not covered by this document are
shown below.
The following import actions are common to every FARLEP-INVEST
customer BGP session:
+ Advertisements tagged with our own "internal use only" communities
(ie the city/country/region/etc communities outlined below) will
have all of their communities stripped from them at ingress, and any
communities meant to affect suppression, prepending, etc are thus
ignored.
+ Prefixes not matching the per-peer import policy as documented
above are not permitted.
+ LocalPref for specific customers (community 12883:5) will be set
to 405 by default, subject to modification based on received
communities as outlined below.
+ LocalPref for the other customers will be set to 400 by default,
subject to modification based on received communities as outlined
below.
non-customer peering session:
+ RFC1918 and other reserved networks and subnets are
not permited.
+ Prefixes shorter than /3 or longer than /24 are
====================================================================
Communities applied at ingress
--------------------------------------------------------------------
error type communities
12883:999 - "internal use" communities received
prefix type communities
12883:1NN - Internal and Customer routes
12883:2NN - Peer routes
12883:5NN -
12883:3NN - Transit routes
12883:4NN - Transit routes (European distributed)
there NN is a POP number (see below)
internal and customer communities, received in the given POP
12883:101 - ods - Odessa
12883:102 - iev - Kiev
12883:103 - lwo - Lviv
12883:105 - dnk - Dnepropetrovsk
12883:106 - khr - Kharkov
12883:107 - ozh - Zaporozhye
12883:109 - nlv - Nikolaev
12883:110 - mpw - Mariupol
12883:111 - khe - Kherson
12883:112 - ifo - Ivano-Frankovsk
12883:113 - fra - Frankfurt
12883:114 - kwg - Krivoy Rog
12883:117 - vin - Vinnitsa
12883:118 - hmj - Khmelnitskiy
12883:119 - cej - Chernigov
12883:120 - cwc - Chernovtsy
12883:121 - tnl - Ternopil
12883:122 - kbp - Borispol
12883:129 - iev-bts - Belaya Tserkov
12883:130 - rwn - Rovno
12883:131 - ztr - Zhitomir
12883:132 - plv - Poltava
12883:133 - udj - Uzhgorod
12883:134 - kgo - Kirovograd
12883:137 - umy - Sumy
12883:138 - ckc - Cherkassy
12883:139 - uck - Lutsk
auxiliary POP/branch communities
12883:602 - routes received from customers at CORE-0.kiev
12883:702 - routes received from customers at EDGE-3.kiev
regional communities
12883:100 - Europe
Communities accepted from customers
1. Customer traffic engineering communities - LocalPref
2. Blackhole implementation.
The customer will need to ask for the "blackhole" feature
to be enabled on their BGP session.
This will enable two sets of prefix filters on the routes
learnt from the customer:
+ the normal filter will match exactly the routes registered
in the IRRs,
+ the "blackhole" filter will match any host (/32 network),
that is contained within the normal set of routes.
customer traffic engineering communities - LocalPref
65200:70 - set local preference to 70
65200:80 - set local preference to 80
65200:90 - set local preference to 90
customer traffic engineering communities - Blackhole
65534:RRRRR - blackhole traffic at specific border router
65534:0 - blackhole traffic at any border router
Traffic destined for any prefixes tagged with this community will be
discarded at ingress to the FARLEP-INVEST network. The prefix must
be one permitted by the customer's existing ingress BGP filter.
Please contact noc@vegatele.com with any questions regarding this
functionality.
|
|
| Hinweise: |
| Gefiltert: |
This output has been filtered.
|
| Whois-Ungenauigkeitsberichte: |
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 ( Ungenauigkeits-Bericht ) |
| Quelle: |
This output has been filtered.
If you see inaccuracies in the results, please visit:
Objects returned came from source
RIPE
|
| Geschäftsbedingungen: |
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 ( Nutzungsbedingungen ) |
|
| Status: |
Aktiv |
| Links: |
https://rdap.db.ripe.net/autnum/12883 ( Selbst )
http://www.ripe.net/data-tools/support/documentation/terms ( Copyright )
|
| Whois-Server: |
whois.ripe.net |
| Konformität: | nro_rdap_profile_asn_flat_0, cidr0, rdap_level_0, nro_rdap_profile_0, redacted |
IP
