From: Derek Fawcus <dfawcus@cisco.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] peering
Date: Tue, 27 Jan 2004 23:26:14 +0000 [thread overview]
Message-ID: <20040127232614.D16382@edinburgh.cisco.com> (raw)
In-Reply-To: <000b01c3e40d$e3fb2260$9214598a@mars>; from aletko@iname.com on Mon, Jan 26, 2004 at 08:11:18AM -0500
On Mon, Jan 26, 2004 at 08:11:18AM -0500, Artem Letko wrote:
> AT&T does inbound filtering on the Cisco's.
>
> Art.
Not to mention any specifics... but I believe the above sort of thing is
correct. The routes exchanged are run through a filter to remove crap.
where crap can be invalid routes (bogons), routes for prefixes that
are too long (or short), and routes that violate a given policy.
Then there are all sort of other fudges, like manipulating the path
you receive from, or supply to a given peer (i.e. inserting/removing ASNs).
DF
>
> ----- Original Message -----
> From: "David Presotto" <presotto@closedmind.org>
> To: <9fans@cse.psu.edu>
> Sent: Sunday, January 25, 2004 8:26 PM
> Subject: [9fans] peering
>
>
> > Anyone out there connect to an ISP peering point (exchange, MAE,
> whatever)?
> > I'm interested in what you do to avoid crappy BGP routes. Anyone have
> > experience with rtConfig, either good or bad?
>
prev parent reply other threads:[~2004-01-27 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 1:26 David Presotto
2004-01-26 13:11 ` Artem Letko
2004-01-27 23:26 ` Derek Fawcus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040127232614.D16382@edinburgh.cisco.com \
--to=dfawcus@cisco.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).