AS21949 — Beanfield Technologies Beanfield

aut-num: AS21949
as-name: BEANFIELD-AS
descr: Beanfield Metroconnect
mnt-by: MNT-BNFD
source: ARIN
changed: jlixfeld@beanfield.com 20201021
import: from AS-ANY accept any
export: to AS-ANY announce AS-BEANFIELD
remarks:
remarks: +------------------------------------------------+
remarks: | bgp communities supported by beanfield/as21949 |
remarks: +------------------------------------------------+
remarks: |
remarks: +
remarks: | table 1
remarks: +---------------------------------------------+
remarks: | local-pref traffic engineering communities |
remarks: +------------+------------+-------------------+
remarks: | community | local-pref | description |
remarks: +------------+------------+-------------------+
remarks: | 21949:1001 | n/a | origin: internal |
remarks: | 21949:9000 | n/a | origin: customer |
remarks: | empty | 990 | customer default |
remarks: | 21949:9001 | 990 | customer default |
remarks: | 21949:9002 | 10 | customer fallback |
remarks: | 21949:9010 | 390 | eq peer |
remarks: | 21949:9011 | 380 | lt peer |
remarks: | 21949:9020 | 190 | eq transit |
remarks: | 21949:666 | 990 | blackhole |
remarks: +------------+------------+-------------------+
remarks: |
remarks: +
remarks: | table 2
remarks: +------------------------------------------------------+
remarks: | as21949 <> upstream supported bgp community mappings |
remarks: +------------+-----------------------------------------+
remarks: | | equivalent supported by upstream asn |
remarks: +------------+------+------+------+------+------+------+
remarks: | action | 577 | 852 | 174 | 3356 | 1299 | 2914 |
remarks: +------------+------+------+------+------+------+------+
remarks: | eq peer | | * | | | * | * |
remarks: | lt peer | | | * | * | | * |
remarks: | eq transit | | | | | | |
remarks: | fallback | * | * | * | * | * | * |
remarks: | blackhole | * | * | | * | * | * |
remarks: +------------+------+------+------+------+------+------+
remarks: |
remarks: +
remarks: | table 3
remarks: +--------------------------------------------------------+
remarks: | as21949 <> ixp rs supported blackhole mapping |
remarks: +-------+-------+-------+--------+------+-----+----------+
remarks: | torix | qix | nyiix | de-cix | drix | six | equinix |
remarks: +-------+-------+-------+--------+------+-----+----------+
remarks: | | | * | * | | * | * |
remarks: +-------+-------+-------+--------+------+-----+----------+
remarks: |
remarks: +
remarks: | table 4
remarks: +--------------------------------------------------+
remarks: | ixp action communities |
remarks: +----------------+------------+--------------------+
remarks: | ixp | community | action description |
remarks: +----------------+------------+--------------------+
remarks: | all ixps | 21949:2000 | do not announce |
remarks: | torix | 21949:2010 | do not announce |
remarks: | qix | 21949:2020 | do not announce |
remarks: | nyiix | 21949:2030 | do not announce |
remarks: | de-cix nyc | 21949:2040 | do not announce |
remarks: | drix nyc | 21949:2050 | do not announce |
remarks: | six | 21949:2060 | do not announce |
remarks: | equinix sea | 21949:2070 | do not announce |
remarks: | equinix ash | 21949:2080 | do not announce |
remarks: | equinix chi | 21949:2090 | do not announce |
remarks: +----------------+------------+--------------------+
remarks: |
remarks: +
remarks: | table 5
remarks: +---------------------------------------------------------------+
remarks: | upstream action communities |
remarks: +------------------+----------+------------+--------------------+
remarks: | upstream | metro | community | action description |
remarks: +------------------+----------+------------+--------------------+
remarks: | all upstreams | all | 21949:3000 | do not announce |
remarks: + + + + +
remarks: | cogent | all | 21949:3010 | do not announce |
remarks: | | toronto | 21949:3011 | do not announce |
remarks: | | montreal | 21949:3012 | do not announce |
remarks: + + + + +
remarks: | bell | all | 21949:3020 | do not announce |
remarks: | | toronto | 21949:3021 | do not announce |
remarks: | | montreal | 21949:3022 | do not announce |
remarks: + + + + +
remarks: | telus | all | 21949:3030 | do not announce |
remarks: | | toronto | 21949:3031 | do not announce |
remarks: + + + + +
remarks: | centurylink | all | 21949:3040 | do not announce |
remarks: | | toronto | 21949:3041 | do not announce |
remarks: | | montreal | 21949:3042 | do not announce |
remarks: + + + + +
remarks: | ntt | all | 21949:3050 | do not announce |
remarks: | | toronto | 21949:3051 | do not announce |
remarks: | | new york | 21949:3052 | do not announce |
remarks: | | seattle | 21949:3053 | do not announce |
remarks: + + + + +
remarks: | telia | all | 21949:3060 | do not announce |
remarks: | | toronto | 21949:3061 | do not announce |
remarks: | | montreal | 21949:3062 | do not announce |
remarks: +------------------+----------+------------+--------------------+
remarks: |
remarks: +--------------------------------------------------------------------+
remarks: | notes regarding bgp community use & support |
remarks: +--------------------------------------------------------------------+
remarks: | 1. bgp customers wishing to send and/or receive communities must |
remarks: | first have the feature enabled on their session(s). please |
remarks: | contact support-at-beanfield.com for this change. |
remarks: | |
remarks: | 2. communities defined in table 1 are evaluated until first match. |
remarks: | |
remarks: | 3. meds are accepted, regardless of bgp session configuration |
remarks: | for community support. |
remarks: | |
remarks: | 4. table 2 describes whether a beanfield upstream asn has support |
remarks: | for the equivalent traffic engineering community action that we |
remarks: | implement. where an upstream asn supports the equivalent, we |
remarks: | re-write their equivalent community on our announcements to |
remarks: | that upstream. |
remarks: | |
remarks: | example: 2914 supports the equivalent of 21949:9011. that is, |
remarks: | when a prefix tagged with 21949:9011 is announced to 2914, we |
remarks: | map to the 2914 equivalent of 21949:9011. |
remarks: | |
remarks: | 5. action communities defined in tables 4 and 5 are evaluated on |
remarks: | any match(es). |
remarks: | |
remarks: | 6. in addition to the communities defined as "origin:" in table 1, |
remarks: | received communities as defined in tables 4 and 5 denote the |
remarks: | prefix origin. |
remarks: | |
remarks: | 7. cogent/174 > 21949: only local and customer prefixes accepted |
remarks: | 21949 > cogent/174: prefixes are tagged with 174:991 by default |
remarks: | refer to the Cogent Customer User Guide for details. |
remarks: | |
remarks: | 8. remote triggered black hole notes: |
remarks: | |
remarks: | only ipv4 host prefixes (eq /32) are accepted. |
remarks: | |
remarks: | only ipv6 host prefixes (eq /128) are accepted. |
remarks: | |
remarks: | traffic to rtbh community tagged host prefix(es) is discarded |
remarks: | at as21949 northbound borders. |
remarks: | |
remarks: | rtbh community will override any other community applied to |
remarks: | the announced host prefix. |
remarks: | |
remarks: | rtbh community is re-written towards all upstreams and ixp |
remarks: | route servers where rtbh is supported per tables 2 & 3. |
remarks: | |
remarks: +--------------------------------------------------------------------+
remarks: