Large BGP Community draft-heitz-idr-large-community-00 Jakob Heitz - - PowerPoint PPT Presentation

large bgp community draft heitz idr large community 00
SMART_READER_LITE
LIVE PREVIEW

Large BGP Community draft-heitz-idr-large-community-00 Jakob Heitz - - PowerPoint PPT Presentation

Large BGP Community draft-heitz-idr-large-community-00 Jakob Heitz (Cisco) Keyur Patel (Cisco) Job Snijders (NTT) Ignas Bagodnas (Equinix) IETF 96, July 2016 Berlin 1 draft-heitz-idr-large-community-01 Benefits Todays RFC1997


slide-1
SLIDE 1

Large BGP Community draft-heitz-idr-large-community-00

Jakob Heitz (Cisco) Keyur Patel (Cisco) Job Snijders (NTT) Ignas Bagodnas (Equinix) IETF 96, July 2016 Berlin

draft-heitz-idr-large-community-01

1

slide-2
SLIDE 2

Benefits

  • Today’s RFC1997 communities are 4 octets each. 2 for ASN and 2 to

indicate the action.

  • With 4 octets for the ASN, it is mapped one to one to your actual globally

unique assigned ASN. Clean name space! No more 23456.

  • With 8 octets for the action, you can easily create opaque action code

points: you have room for a “target” and an “action” Examples:

  • “2914:199036:303” (In NTT: prepend 3 times to 32-bit AS 199036)
  • (currently not possible with NTT’s standard BGP Communities)
  • ”2914:65535:3000” (In NTT: lower local preference in region X)
  • Currently done by putting private ASNs in the Global Administrator Field

(65530:3000) – potential for clashes

draft-heitz-idr-large-community-01

2

slide-3
SLIDE 3

Format

  • Each community is 8 octets long.
  • They are grouped by context ASN under a header inside a wide

community BGP attribute.

draft-heitz-idr-large-community-01

3

slide-4
SLIDE 4

Encoding

1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type, Length | : Context ASN : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opaque 1 | | Opaque 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opaque 1 | | Opaque 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : more Opaque, as determined by Length : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

draft-heitz-idr-large-community-01

4

This header from Wide Communities Length determines how many communities

slide-5
SLIDE 5

Textual Representation

  • Each community is represented as a:b:c
  • a, b and c are each a non-negative decimal integer
  • a – ASN
  • b – Opaque 1
  • c – Opaque 2

draft-heitz-idr-large-community-01

5

slide-6
SLIDE 6

Example

  • (2914:1:2), (2914:3:4), (2914:5:6), (3356:7:8)

draft-heitz-idr-large-community-01

6

.. 48 2914 1 2 3 4 5 6 7 8 .. 32 3356 Type and

  • ther

fields 24 + (3*8) Context ASN Communities 24 + (1*8)

slide-7
SLIDE 7

Thanks

  • Jeff Haas, Juniper
  • Jared Mauch, NTT
  • Igor Gashinsky, Yahoo!

draft-heitz-idr-large-community-01

7