[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BGP offloading (fixing legacy router BGP scalability issues)

Subject: BGP offloading (fixing legacy router BGP scalability issues)
From: johnl at iecc.com (John R. Levine)
Date: 6 Apr 2015 18:30:57 -0400
In-reply-to: <CAP-guGVgRv6nex2-A8Mks7zrdN+TwD3-gzh5y953Mba42yAHhw@mail.gmail.com>
References: <[email protected]> <[email protected]> <CAP-guGVgRv6nex2-A8Mks7zrdN+TwD3-gzh5y953Mba42yAHhw@mail.gmail.com>

> http://www.americanbar.org/newsletter/publications/gp_solo_magazine_home/gp_solo_magazine_index/civilliability.html

Nothing there about ISP liability other than noting the third-party 
immunity from the CDA.

> https://www.ftc.gov/news-events/press-releases/2009/06/ftc-shuts-down-notorious-rogue-internet-service-provider-3fn

Well, yeah, they were actively running a crimeware service.  "Don't do 
that."

References:
- BGP offloading (fixing legacy router BGP scalability issues)
  - From: goemon at anime.net (goemon at anime.net)
- BGP offloading (fixing legacy router BGP scalability issues)
  - From: johnl at iecc.com (John Levine)
- BGP offloading (fixing legacy router BGP scalability issues)
  - From: bill at herrin.us (William Herrin)

Prev by Date: BGP offloading (fixing legacy router BGP scalability issues)
Next by Date: BGP offloading (fixing legacy router BGP scalability issues)
Previous by thread: BGP offloading (fixing legacy router BGP scalability issues)
Next by thread: BGP offloading (fixing legacy router BGP scalability issues)
Index(es):
- Date
- Thread