Ethan,
Maybe you would find the below document useful...
http://www.cisco.com/public/cons/isp/documents/ISP_Design_Fundelmentals-1up.pdf
-- elijah
On Wed, 18 Apr 2001, Ethan wrote:
> well, to correct the statement, of course public addressing as the subnets for
> Internet access, private addresses for backend....isn't that common or am i
> mistaken in my belief ??
>
> but back to the main point, i'd appreciate any comments on routing used in SP
> environments or is this not the right forum...
>
> thanks,
>
> Brian wrote:
>
> > Hmm private addressing at the core? let the guessing begin, I'll say @home.
> >
> > Brian
> >
> > ----- Original Message -----
> > From: "Adam Rothschild" <asr@latency.net>
> > To: "Ethan" <ethan@sun.com>
> > Cc: "Cisco Mailing List (NSP)" <cisco-nsp@puck.nether.net>
> > Sent: Tuesday, April 17, 2001 11:26 PM
> > Subject: Re: [nsp] Routing Architecture
> >
> > > On Tue, Apr 17, 2001 at 12:50:47PM -0400, Ethan wrote:
> > > > In a typical service provider environment say one that provides
> > > > co-location services, how would one propose the routing architecture ?
> > > > The last one I saw divided their networks into subnets VLSM etc.. and
> > > > mixture of private and public addressing with *static routing* at the
> > > > core [...] ^^^^^^^^^^^^^^
> > >
> > > Out of curiosity, which provider was this?
> > >
> > > -adam
> > >
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:35 EDT