public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Somewhat OT: Any truth to this mess?
Date: Sun, 19 Feb 2012 02:02:51 +0700	[thread overview]
Message-ID: <CAA2qdGVskmWWEiyemcTNomEWQ1qJ-82yP9314O_4wXPVHdJ9FQ@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiDkgYRFneDPmNEAnfC3VDfHm1+hFMFX4u=-RjLq9V_E=w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Feb 19, 2012 1:15 AM, "Michael Mol" <mikemol@gmail.com> wrote:
>
> (Sorry for the top-post...I'm mobile atm.)
>
> My understanding is that core network operators filter ASs for which they
don't have a contract for transit. I.e, if I were to get my own PI space,
I'd have to pay tier 1 networks (or pay someone to ride on *their*
contract) for a contract to have packets destined for my AS to be able to
reach me across their network.
>

Well, yes, but it's the other way around.

It's an operator saying "I don't want traffic for $AS_LIST" or "I want
traffic only for $AS_LIST". The contents of AS_LIST is set by the operator
on the receiving side statically, based on the transit contract.

The routers, being the workhorse brutes that they are, don't waste time
checking on contracts.

So, if a neighbor router suddenly advertise it has a 1-hop distance to
*any* AS... the router will immediately begin switching packets toward that
neighbor.

Rgds,

[-- Attachment #2: Type: text/html, Size: 1161 bytes --]

  reply	other threads:[~2012-02-18 19:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18 10:26 [gentoo-user] Somewhat OT: Any truth to this mess? Dale
2012-02-18 10:44 ` Alan McKinnon
2012-02-18 12:00   ` Dale
2012-02-18 12:24     ` Volker Armin Hemmann
2012-02-18 12:39       ` Dale
2012-02-18 14:40         ` Alan McKinnon
2012-02-18 15:34           ` Dale
2012-02-18 16:18             ` Michael Mol
2012-02-18 17:48               ` Dale
2012-02-18 18:01               ` Pandu Poluan
2012-02-18 18:10                 ` Michael Mol
2012-02-18 19:02                   ` Pandu Poluan [this message]
2012-02-18 16:21         ` Volker Armin Hemmann
2012-02-18 16:31           ` Michael Mol
2012-02-18 12:56       ` Pandu Poluan
2012-02-18 13:18         ` Dale
2012-02-18 13:49           ` Pandu Poluan
2012-02-18 14:38           ` Alan McKinnon
2012-02-19 21:08           ` [gentoo-user] " walt
2012-02-19 21:23             ` Paul Hartman
2012-02-19 22:16               ` Dale
2012-02-20 16:12             ` Todd Goodman
2012-02-20 20:49               ` Grant Edwards
2012-02-20 21:04                 ` Michael Mol
2012-02-20 21:16                   ` Mark Knecht
2012-02-20 21:24                     ` Michael Mol
2012-02-20 21:52                   ` Grant Edwards
2012-02-21  5:30                   ` Paul Hartman
2012-02-18 14:30       ` [gentoo-user] " pk
2012-02-21  3:58         ` Walter Dnes
2012-02-18 14:36     ` Alan McKinnon
2012-02-18 18:11       ` Pandu Poluan
2012-02-18 18:24         ` Michael Mol
2012-02-18 19:10           ` Pandu Poluan
2012-02-18 16:35 ` Mike Edenfield
2012-02-19 21:14   ` [gentoo-user] " walt
2012-02-19 23:29     ` wdk@moriah
2012-02-20 16:37       ` Todd Goodman

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=CAA2qdGVskmWWEiyemcTNomEWQ1qJ-82yP9314O_4wXPVHdJ9FQ@mail.gmail.com \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.org \
    /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