Customer Portal

BGP Community Structure

WARNING

This page is a work in progress and should be effectively ignored until this message no longer exists.

Please contact peering@oscloud.io for any questions regarding BGP policy.

Large BGP Communities

Omnificent Systems leverages Large BGP Communities to provide extremely granular control capabilities to transit customers, peers, and internally maintained customers.

Unlike the Extended Community format introduced in RFC 4360, which is comprised of one 32 bit field broken up into two 16 bit fields, large communities are comprised of one 96 bit field, delineated into three 32 bit fields.

Common Community Type Differences

Standard Communities (RFC 1997):

NO-EXPORT

NO-ADVERTISE

NO-ADVERTISE-SUBCONFED

Extended Communities (RFC 4360):

0-65535:0-65535

Large Communities (RFC 8092):

0-4294967295:0-4294967295:0-4294967295

Typically, the three fields are structured as Operator ASN:Function:Parameter.

For example:

ASN:Received from POP:osCloud AZ01 logic would be written as:

395077:1:1011

ASN:Prepend 3x:LEVEL 3 Logic would be written as:

395077:2001:3356

Recommendations for deployment can be found in RFC 8195.

Community Allocations

The Omnificent Systems community structure is allocated into the following buckets:

ASN Function Parameter Description
395077 0-999 * Informational
395077 1000-1999 * Internal Actions
395077 2000-2999 * External Actions
395077 3000-3999 * Security Actions
395077 4000-4294967295 * Unassigned

Community Assignments

POP Information
POP Location POP Name POP ID
Phoenix, AZ AZ01 11
Las Vegas, NV NV01 12
Honolulu, HI HI01 13
Dayton, OH OH01 21
Edison, NJ NJ01 22
Atlanta, GA GA01 23

Upstream Peers

Peer Name Peer ASN AZ01 NV01 HI01 OH01 NJ01 GA01
Cogent 174 ✅ ✅ ✅ ✅
CenturyLink/Qwest 209 ✅ ✅
CenturyLink/Level3 3356 ✅
Hawaiian Telcom 36149 ✅
Hurricane Electric 6939 ✅ ✅

Informational Communities

Received from POP

Community Effect
395077:1:1011 Received from AZ01