Re: [apops] Re: [Oz-ISP] Telstra Community support

  • To: Phillip Grasso-Nguyen <grasso at magna dot com dot au>
  • Subject: Re: [apops] Re: [Oz-ISP] Telstra Community support
  • From: Joe Abley <jabley at automagic dot org>
  • Date: Sat, 14 Apr 2001 09:32:13 -0400
  • Cc: apops at lists dot apnic dot net
  • In-reply-to: <006101c0c436$8af00e00$6500a8c0@PGLAPTOP>; from grasso at magna dot com dot au on Sat, Apr 14, 2001 at 02:26:50AM +1000
  • References: <002e01c0c313$6897aee0$b4646fcb@PGLAPTOP> <v04220803b6fb25cbad63@[192.83.231.95]> <002501c0c42b$ccbc1550$6500a8c0@PGLAPTOP> <20010413113729.L19984@buddha.home.automagic.org> <006101c0c436$8af00e00$6500a8c0@PGLAPTOP>
  • Sender: owner-apops@lists.apnic.net
  • User-agent: Mutt/1.2.5i
    • On Sat, Apr 14, 2001 at 02:26:50AM +1000, Phillip Grasso-Nguyen wrote:
      > > What are you trying to achieve?
      > by providers being able to pass communites, remote policy can be changed,
      > e.g
      > check out open transits policies,
      > Extract from whois -h whois.ra.bet AS5511
      >                Community Definition
      >                ------------------------------------------------------
      >                5511:1000  Do not announce to US peers
      >                5511:1001  Prepend 5511 when announcing to US peers
      >                5511:1002  Prepend 5511 5511 when announcing to US peers
      >                5511:1101  Do not announce to Sprintlink/AS1239
      >                5511:1102  Do not announce to ICM/AS1800
      >                5511:1201  Prepend 5511 when announcing to Sprintlink
      >                5511:1202  Prepend 5511 when announcing to ICM
      >                5511:1301  Prepend 5511 5511 when announcing to Sprintlink
      >                5511:1302  Prepend 5511 5511 when announcing to ICM
      >                5511:1401 Do not announce to Sprint on Relay
      >                5511:2000  Do not announce to european peers
      >                5511:2001  Prepend 5511 when announcing to european peers
      >                5511:2002  Prepend 5511 5511 to european peers
      >                5511:2101  Do not announce to Global One/AS4000
      >                5511:2102  Do not announce to Ebone/AS1755
      >                5511:2201  Prepend 5511 when announcing to Global One
      >                5511:2202  Prepend 5511 when announcing to Ebone
      >                5511:2301  Prepend 5511 5511 when announcing to Global One
      >                5511:2302  Prepend 5511 5511 when announcing to Ebone
      >                5511:3000 Do not announce to asia/pacific peers
      >                5511:4000  Do not announce to other peers
      
      5511 is not passing these communities through to peers, though, which is
      what you said you were asking for, wasn't it?
      
      You seem to want a mechanism that will allow you to influence the way
      your prefixes are propagated to the rest of the world; however, by asking
      Telstra to leave whatever communities you set intact, you are presupposing
      a solution.
      
      > endless possiblities.
      
      Endless is a little over-enthusiastic :)
      
      > means that service providers don't have to break cidr to control their
      > inbound policies, also gives end providers a choice how their networks get
      > routed, specially if some providers want to route around bottleneaks etc.
      
      The normal approach to routing around bottlenecks is to call your provider
      and say "hey! there's a bottleneck there. you should fix your export policy
      to avoid that."
      
      You are asking Telstra to offload the job of fixing their transit issues
      onto their customers. To some extent, this is similar to them just providing
      you with telnet access to their routers, and saying "if you need to make
      changes, go ahead" :)
      
      
      Joe
      *             APOPS: Asia Pacific Operations Forum              *
      * To unsubscribe: send "unsubscribe" to apops-request at apnic dot net *