========================================================
 Abuse reports to abuse@ucomline.net
 ========================================================

 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
 ,
 and only non-standart communities that are not covered
 by this document are shown below.

 The following import actions are common to every
 Ucomline customer peering 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 below are not permitted.

 + Localpref will be set to 400 by default, subject
 to modification based on received communities as
 outlined below.

 The following import actions are common to every
 Ucomline non-customer peering session:

 + RFC1918 and other reserved networks and subnets are
 not permited.

 + Prefixes shorter than /3 or longer than /24 are
 not permited.

 ========================================================
 Communities applied at ingress
 ========================================================
 --------------------------------------------------------
 error type communities
 --------------------------------------------------------
 12883:999               - "internal use" communities
                           received from peer.
 --------------------------------------------------------
 prefix type communities
 --------------------------------------------------------
 12883:1NN               - Internal and Customer routes
 12883:2NN               - Peer routes
 12883:5NN               - Peer routes (IXP distributed)
 12883:3NN               - Upstream routes
 12883:4NN               - Upstream routes (FFT destributed)

 there NN is a POP number (see below)
 --------------------------------------------------------
 internal and customer POP communities
 --------------------------------------------------------
 12883:101  - ods        - Odessa
 12883:102  - iev        - Kiev
 12883:103  - lwo        - Lviv
 12883:104  - dok        - Donetsk
 12883:105  - dnk        - Dnepropetrovsk
 12883:106  - khr        - Kharkov
 12883:107  - ozh        - Zaporozhye
 12883:108  - sip        - Simferopol
 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:115  - uks        - Sevastopol
 12883:116  - vsg        - Lugansk
 12883:117  - vin        - Vinnica
 12883:118  - hmj        - Khmelnitskiy
 12883:119  - cej        - Chernigov
 12883:120  - cwc        - Chernovtsy
 12883:126  - sip-yal    - Yalta
 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 customer POP/branch communities
 --------------------------------------------------------
 12883:602               - CORE routers in Kiev
 12883:702               - EDGE routers in Kiev
 --------------------------------------------------------
 peering POP communities
 --------------------------------------------------------
 12883:202               - UAIX
 --------------------------------------------------------
 peering (IXP distributed) POP communities
 --------------------------------------------------------
 12883:502               - Kiev
 --------------------------------------------------------
 upstream POP communities
 --------------------------------------------------------
 12883:313               - BT, Colt, Gblx, Level3, others
 --------------------------------------------------------
 upstream (FFT distributed) POP communities
 --------------------------------------------------------
 12883:401               - FFT Upstream in Odessa
 12883:402               - FFT Upstream in Kiev
 12883:403               - FFT Upstream in Lviv
 12883:406               - FFT Upstream in Kharkov
 12883:413               - FFT Upstream in Frankfurt
 --------------------------------------------------------
 regional communities
 --------------------------------------------------------
 12883:100               - Europe

 ========================================================
 Communities accepted from customers
 ========================================================
 --------------------------------------------------------
 customer traffic engineering (TE) notes
 --------------------------------------------------------
 1. Communities allow suppress or prepend to peer AS, where

 + peer AS has a peering connection to Ucomline,

 + peer AS is not a customer of Ucomline.

 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 - Suppression
 --------------------------------------------------------
 64999:XXX   - announce to AS XXX if 65000:0 is set
 65000:0     - announce to customers but not to peers
 65000:XXX   - do not announce at peerings to AS XXX
 651NN:XXX   - do not announce at peerings to AS XXX
               at NN POP (see above).

 Note:         XXX means AS number
 --------------------------------------------------------
 customer traffic engineering communities - Prepending
 --------------------------------------------------------
 65001:0     - prepend once  to all peers
 65001:XXX   - prepend once  at peerings to AS XXX
 65002:0     - prepend twice to all peers
 65002:XXX   - prepend twice at peerings to AS XXX
 65003:0     - prepend 3x to all peers
 65003:XXX   - prepend 3x    at peerings to AS XXX
 65004:0     - prepend 4x to all peers
 65004:XXX   - prepend 4x    at peerings to AS XXX
 65006:0     - prepend 6x to all peers
 65006:XXX   - prepend 6x    at peerings to AS XXX
 65008:0     - prepend 8x to all peers and take additional
               measures to make these routes the least
               prefered routes (eg decrease LocalPref)
               within peering ASes
 65008:XXX   - prepend 8x    at peerings to AS XXX

 Note:         XXX means AS number
 --------------------------------------------------------
 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 Ucomline
 network.  The prefix must be one permitted by the
 customer's existing ingress BGP filter.
 Please contact network.provisioning@ucomline.net with any
 questions regarding this functionality.
 --------------------------------------------------------