> > This of course leaves the way open to get your non-technical HR
> > person to ask bizarre, embarrasing or just plain impossible
> > questions.
> >
> > "So, Mr Berkowitz, could you please explain when a static RIP route
> > would be useful between autonymous systems?"
In reality, I've been researching a lightweight RIP variant simply
for keepalives between private AS and providers. Special application
though. Scott Bradner made unpleasant noises when he heard my initial
thought. Nevertheless, I agree about the silly questions.
Every few weeks, I get a recruiter or HR person calling me to ask if
I'm interested in "being a Cisco engineer." One of the telltale
questions that tells me this is not exactly relevant is "how many
routers have you worked with?"
How many routers are in the Internet? I certainly don't know,
although I could take a crack at the number of AS. There were 2500 or
so in AT&T's internal network when I consulted on it. MCI's frame
service uses about 1000 routers.
A really...sharp...recruiter paused and said "my client needs someone
with hands-on experience in a real network with 50 or so routers. Do
you have such experience?"
> >
> > "Mr Lammle, when you've wired the left-handed wedgie-strap to the
> > Cisco trouter port, what's the next step to getting true voice over
> > avian-carrier signalling?"
> >
>
>I would say that depends on whether the avian carrier is African or
>European. :-)
>
Ummm....you're looking at the problem in an implementation-specific
manner. Do you really think the IETF has stood still since RFC 1149?
RFC 2549 IP over Avian Carriers with Quality of Service. D. Waitzman.
April-01-1999. (Format: TXT=9519 bytes) (Updates 1149)(Status:
INFORMATIONAL)
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
