[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: requirements draft revision
On Fri, Jun 29, 2001 at 07:13:15PM -0500, Jon (Taz) Mischo wrote:
> On Fri, 29 Jun 2001, Joe Abley wrote:
> > I don't understand the question. It's the fact that C is providing
> > connectivity to the internet beyond C that makes it a transit provider.
> > I don't understand what addressing and/or the presence of NAT has to
> > do with it in the general case.
> No, it's the fact that C will route _any_ of its customers' traffic to
We were avoiding the use of "customer", I think, in the interests of finding
a technical description as opposed to a commercial one.
> either its destination or to an egress point nearer (usually) its
> destination that makes it a transit provider. The word any is the key. A
> peer will route any traffic you send it that is destined for its own
> network, and sometimes to other agreed upon networks. A transit provider
> routes you to EVERYTHING.
Right. Isn't this encapsulated in Randy's use of "global"?