NetworkTalk & BGP

A.2.b) Peering agreement between the upstream/transit providers

  1. ISP-B is a Tier1 operator; ISP-C and ISP-D are Tier2 operators and buy IP transit to ISP-B.
    1. The question is how ISP-B tags the routes received from its peers, in our case from ISP-C and ISP-D? Same question for ISP-C and ISP-D?
    2. Which attribute do they use in order to control the receiving routes from its peers and customers buying IP transit?
  2. ISP-B, ISP-C and ISP-D propose the following communities rules on which we can focus our attention:
    1. ISP-B proposes the following communities which allow customers to set local preference about their advertised network, within ISP-B’s AS:
      1. 300:70 set local preference 70
      2. 300:80 set local preference 80
      3. 300:90 set local preference 90
      4. local pref for routes learned from peers : 86
    2. ISP-C proposes the following communities which allow customers to set local preference about their advertised network, within ISP-C’s AS:
      1. 400:70 set local preference 70
      2. local pref for routes learned from peers : 90
    3.  ISP-D proposes the following communities which allow customers to set local preference about their advertised network, within ISP-D’s AS:
      1. 500:70 set local preference 70
      2. 500:80 set local preference 80
      3. 500:90 set local preference 90
      4. local pref for routes learned from peers set to 85

Plz check also “RFC 1998” on the Internet.
See below Figure A.1: PEERING AGREEMENT WITH LOCAL PREFERENCE

top

Come back to Tutorial Index”