RE:
This is the most up-to-date list. http://www.isi.edu/in-notes/iana/assignments/port-numbers -Original Message- From: Tim O'Brien [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 07, 2001 10:24 AM To: Heidi white Cc: [EMAIL PROTECTED] Subject: Re: Have a look at RFC 1700 http://www.ietf.org/rfc/rfc1700.txt Tim - Original Message - From: "Heidi white" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 07, 2001 10:53 AM Anyone know of a site that would list all ports? Or a specific link on the cisco site? I've looked through pages upon pages with no luck. Heidi __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: CCIE salary
With that said, I will certainly follow all your suggestions to become better informed. I should let you know that although I am currently a member of IEEE and have several subcriptions, I do not posses tha hands on experience with all the technologies. I have a very good understanding of the theory and practice required to implement certain soluions. Right now, with the direction the Internet is headed, I am interested in gaining a practical roadmap for developing business solutions that require knowledge of distributed computing methods. With that said, what is the best roadmap to find out how some of the popular customer oriented solutions were developed? One solutions in particular is the Napster application. Do you have a roadmap and a source of information for developing that skillset? Additionally, what are some of the other mailing list you guys are a part of? Thanks! -Original Message- From: Howard C. Berkowitz [mailto:[EMAIL PROTECTED]] Sent: Friday, February 23, 2001 3:46 PM To: [EMAIL PROTECTED] Subject: RE: CCIE salary Howard, Things like abstract algebra (especially graph theory), principles of real-time operating systems, queueing theory, etc., are all directly relevant. Reading and understanding the Routing Policy Specification Language needs a good background in programming language and abstractions including object orientation. i was not a computer science major, but i do have a good practical handle on networking, protocols, and security and i have several networking certs. how can i develop my skills to reach the level in which i can tackle large scale architecture projects. When I started things, the academic programs weren't there. They are today, and graduate-level courses CAN be relevant -- they may not. I've written several books on design, and Wiley's Networking Council series primarily focuses on network architecture. Priscilla's book. Track the IETF and NANOG mailing lists. Participate in professional societies such as ACM and IEEE. It's worth looking occasionally at some of the technology-oriented business press (e.g., Business Week, Harvard Business Review, Business Communications Week). Subscribe to all the free trade magazines and newspapers available -- eventually you will find what is useful and what is not. Be sure you have strong spoken and written communications skills; you will have to interview people. Know what you don't know. Know that many technical disciplines, not just networking, require lots of theoretical background. By way of analogy, I have little problem dealing with my physicians, because I speak with them as a peer that understands the basic science underlying the discussion. -Original Message- From: Howard C. Berkowitz [mailto:[EMAIL PROTECTED]] Sent: Friday, February 23, 2001 2:33 PM To: [EMAIL PROTECTED] Subject: Re: CCIE salary In my opinion, CCIE is a test of ability of learning and using knowledge, not a test of knowledge itself. No matter a CCIE or not, you can be an expert in Wireless or Optical or other arena, because you have been working on those stuff for a while and you are following it. No body compares a ISP senior engineer who has no certification to CCIE working in enterprise his/her whole life. But in my mind as long as that guy is an CCIE, he should have no problem picking up the job of the ISP senior engineer giving a short time. Jack Jack, True, I'm not a formal CCIE (and consciously do not intend to go through the lab because I don't want to conflict with Cisco NDAs), although I was CCSI-certified in the Old Days, when the testing (pre-1995) was comparable, IMHO, to the current CCIE program. I have a reasonably solid computer science background (again, was in the field prior to their being graduate degrees in it), and am currently working on a book on ISP engineering, having written seveal related books. These days, my work includes designing router products for ISP applications. I've written or contributed to several RFCs and Internet Drafts, including a current draft on single router BGP convergence time, the next draft of which (to be posted next week) will reflect the thinking of several vendors. I can only say that it took me several years to get to a point where I feel comfortable in large-scale ISP architecture and engineering, starting with a solid software and theoretical background. Things like abstract algebra (especially graph theory), principles of real-time operating systems, queueing theory, etc., are all directly relevant. Reading and understanding the Routing Policy Specification Language needs a good background in programming language and abstractions including object orientation. In short, don't plan on walking into a major ISP and assuming a CCIE is anything more than a very minimal indication that you might be able to learn. No one is going to put you into a senior engineering position unless you have lots of knowledge that
Napster internet technology
I am performing research into the technical underpinnings of the Napster program that allows a desktop machine the ability to utilize desktop and internet tools to deliver a truly distributed Internet application. Can anyone assist me by provide technical information on the Napster program? Listed below are specific questions. 1. What development application was used to develop Napster? 2. How does Napster use TCP to distribute software? (i.e. port numbering information, application layer routing) Thanks! Bandele Hinton Motorola Corporation 630-353-8286 (office) 877-992-7925 (pager) [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: core internet technology
I am performing research into the technical underpinnings of the Napster program that allows a desktop machine the ability to utilize desktop and internet tools to deliver a truly distributed Internet application. Can anyone assist me by provide technical information on the Napster program? Listed below are specific questions. 1. What development application was used to develop Napster? 2. How does Napster use TCP to distribute software? (i.e. port numbering information, application layer routing) Thanks! Bandele Hinton Motorola Corporation 630-353-8286 (office) 877-992-7925 (pager) [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: what is the average age of people in this stuff?
Your journey is a very exciting one. I am very respectful of your knowledge and understanding of the business. you mentioned being effective based on how someone thinks. i have discovered that the way a person thinks is vitally important. personally, i am a problem solving thinker. i always look for improvement is a system. with that said, can you more clearly define your idea of how people think? can you teach someone to think from a problem solving perspective? thanks! -Original Message- From: Howard C. Berkowitz [mailto:[EMAIL PROTECTED]] Sent: Monday, February 26, 2001 10:56 AM To: [EMAIL PROTECTED] Subject: Re: what is the average age of people in this stuff? Not quite sure how I fit into this model. I'm 52, but I was about 18 when I first touched a computer, and 19 or 20 when I first did something that was recognizable as network-related (terminal-based timesharing). By 1970, I was doing early distributed computing (medical lab instrument computers to database computers), pre-SNA IBM networking from about '71, ARPANET and X.25 stuff in the early '70s, SNA when it came out in '74, etc. Guessing that I did UNIX-based IP routing starting in the early to mid 80's, and first touched a Cisco router running 9.0 in 1992(?). So, in some respects I fall into the "old" category. It's hardly, though, a problem of learning technology -- the more I know, the easier it is to incorporate new concepts. Learning is as much, or more, fun than it was when I was younger, because I've learned to make it as much play as work, and how to do it efficiently. In all fairness, with what I do in my various "day" and "night" jobs, it really isn't that important for me to memorize lots of the details of individual commands. People tend to want me to figure out product and solution designs, and/or how to learn, than to be hands-on. Understanding how people learn is important. My thinking about a personal CCIE has evolved over the years. At this point, I very consciously do not want to get a CCIE, because I can't be accused of violating an NDA that I never signed. Also, having a CCIE wouldn't particularly affect my compensation or my job prospects. To say that I can't teach someone what they need to know for a CCIE, however, would be to suggest that Don Shula, Joe Gibbs, etc., were ineffective NFL coaches because they weren't qualified to be starting football players while they were coaching. It's also comforting to work with Vint Cerf or Scott Bradner, and know that they are older and still playing! _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: CCIE salary
Howard, Things like abstract algebra (especially graph theory), principles of real-time operating systems, queueing theory, etc., are all directly relevant. Reading and understanding the Routing Policy Specification Language needs a good background in programming language and abstractions including object orientation. i was not a computer science major, but i do have a good practical handle on networking, protocols, and security and i have several networking certs. how can i develop my skills to reach the level in which i can tackle large scale architecture projects. -Original Message- From: Howard C. Berkowitz [mailto:[EMAIL PROTECTED]] Sent: Friday, February 23, 2001 2:33 PM To: [EMAIL PROTECTED] Subject: Re: CCIE salary In my opinion, CCIE is a test of ability of learning and using knowledge, not a test of knowledge itself. No matter a CCIE or not, you can be an expert in Wireless or Optical or other arena, because you have been working on those stuff for a while and you are following it. No body compares a ISP senior engineer who has no certification to CCIE working in enterprise his/her whole life. But in my mind as long as that guy is an CCIE, he should have no problem picking up the job of the ISP senior engineer giving a short time. Jack Jack, True, I'm not a formal CCIE (and consciously do not intend to go through the lab because I don't want to conflict with Cisco NDAs), although I was CCSI-certified in the Old Days, when the testing (pre-1995) was comparable, IMHO, to the current CCIE program. I have a reasonably solid computer science background (again, was in the field prior to their being graduate degrees in it), and am currently working on a book on ISP engineering, having written seveal related books. These days, my work includes designing router products for ISP applications. I've written or contributed to several RFCs and Internet Drafts, including a current draft on single router BGP convergence time, the next draft of which (to be posted next week) will reflect the thinking of several vendors. I can only say that it took me several years to get to a point where I feel comfortable in large-scale ISP architecture and engineering, starting with a solid software and theoretical background. Things like abstract algebra (especially graph theory), principles of real-time operating systems, queueing theory, etc., are all directly relevant. Reading and understanding the Routing Policy Specification Language needs a good background in programming language and abstractions including object orientation. In short, don't plan on walking into a major ISP and assuming a CCIE is anything more than a very minimal indication that you might be able to learn. No one is going to put you into a senior engineering position unless you have lots of knowledge that is not covered by the CCIE program. By "engineering," I don't mean third-level support. I mean deciding peering policy, finding performance problems, designing and implementing QoS, working out the relationships among IGPs, BGP, and MPLS, and coming up with responses to hacking attacks (especially distributed). There is a reason that computer science programs have not been supplanted by the CCIE program. ""Mark Holloway"" [EMAIL PROTECTED] wrote in message 006d01c09dc7$4e10caf0$111fea18@platypus">news:006d01c09dc7$4e10caf0$111fea18@platypus... At Sprint we have a few CCIEs.. But not as many as you think - and we are the #1 reseller of Cisco equipment in the U.S.. I have put my CCIE on hold for now, since I know what CCIEs in Las Vegas earn versus what I make now. The problem is that in the real world, people start to become specialists, and my job title has me working in the field of IP Telephony as well as 802.11b WLANs. So, getting my CCIE right now won't do much. I may go for the CCIE Design later this year. But I recently left my old employer as a "Network Engineer" (designing/merging/expanding our network and troublshoting problems) and recently started at Sprint Long Distance doing Pre-Sales Engineering in 5 different states. My product range is: Nortel PBXs, Nortel Routers/Switches (there are more our there than you think!), Cisco AVVID product line, and Aironet product line. I've had experience with VoATM and VoFR at my last job, setting up tie lines from PBX to PBX over the WAN. IP Phones are new to me, but I'll be traveling to Ontario, Canada, to play at Nortel, and flying to North Carolina to play in Sprint's AVVID lab .. oh yea, I'm going to some Cisco IP Telephony/Call Center training too. :-) - Original Message - From: "Peter Van Oene" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 23, 2001 9:47 AM Subject: Re: CCIE salary The CCIE program does little to develop the skill set of a pure IP engineer in a ISP environment. CCIE has little bearing in my opinion when candidate are
RE: Networking White Papers (NAP and BGP)
The problem I am trying to solve... I am trying to develop a network access strategy based on the use of a NAP for my organization. I am tasked with preparing a whitepaper to address this. -Original Message- From: Howard C. Berkowitz [mailto:[EMAIL PROTECTED]] Sent: Monday, February 12, 2001 11:07 AM To: [EMAIL PROTECTED] Subject: RE: Networking White Papers (NAP and BGP) Based on paliminary research, BGP seems to be the major protocol at the NAP level. Is that true? Yes. What problem are you trying to solve? And if so, why? Furthermore, why is so much attention given to one protocol? I don't really understand this question. Exchange points are completely concerned with interdomain routing. The only standard protocol for interdomain routing is BGP. Is it the only protocol for the job of exchanging routes at the NAP level? Yes/ Finally, will BGP continue to be the protocol of choice as IPv6 develops? Yes, that is one of the purposes for BGP address family extensions. Thanks! -Original Message- From: Howard C. Berkowitz [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 10, 2001 4:54 PM To: [EMAIL PROTECTED] Subject: RE: Networking White Papers (NAP and BGP) As defined in the industry, a Network Access Point (NAP) is a major connection point in the global Internet. It is like a Point-of-Presence (POP) but it is high bandwidth. Currently there are 5 major NAP in the US, but I need white papers on the construction of these major POPs. Hope that helps! NAP is a historical term for what more frequently is called an exchange point; there are many more than five in the US and indeed an increasing number worldwide. There's normally a panel discussion on "news from the exchanges" at each NANOG meeting (http://www.nanog.org), and there are exchange working group meetings at the RIPE meetings for Europe (http://www.ripe.net) Before even beginning to think about designing an exchange or carrier-grade POP, be very familiar with the NANOG and RIPE meeting presentations and with their mailing list minutes. Cisco has some good references: ISP Essentials Power Session http://www.cisco.com/public/cons/isp/documents/IOSEssentials_Seminar.ziphttp://www.cisco.com/public/cons/isp/documents/IOSEssentials_Seminar.zip BGP Routing Workshop http://www.cisco.com/public/cons/workshops/bgp/http://www.cisco.com/public/cons/workshops/bgp/ I discuss some aspects of exchange points in my BGP tutorial series at http://www.certificationzone.com. This coming weekend, at NANOG in Atlanta, I'll be doing an exterior routing tutorial that will partially discuss exchanges and POPs. Slides should be up by Sunday. The presentations may be webcast, but I'm not sure. Check the NANOG site. The classic exchange point design features a carrier-grade physical facility, racks for the individual providers' routers, and a common layer 2 (sometimes layer 3) fabric to interconnect them. In the original NAPs, the providers often kept the BGP workload down by not having a direct BGP connection to every other provider there, but to one or more route servers -- BGP code running on UNIX boxes that do no forwarding, but build the maps of the exchange point. Today, there is less emphasis on the route servers for primary BGP, but there is still peering to them for statistics gathering. Some exchanges use a distributed switched fabric, so there is not one physical room. Instead, the participating providers are linked by ATM. It's something of an urban legend that the top-level providers do significant traffic exchange at the exchange points. At that level, they are far more likely to have private peerings over direct OC-3 or faster links. Exchange points, however, are useful for medium level providers in a given urban or geographic area. Indeed, there is an ever-growing trend to having metropolitan exchange points among cooperating ISPs in small cities. The traditional exchange is for ISPs only, but the line between hosting centers and exchanges is constantly getting more blurry. Large provider POPs are not necessarily smaller than exchanges, but simply have a different management and operational model. I don't want to be negative, but if someone hasn't been playing in the ISP area for a while, is familiar with the NANOG/RIPE materials, etc., they aren't remotely ready to design a carrier-grade POP or exchange by themselves. Cisco consulting engineers, and I'd assume Juniper as well, can be very helpful when such a project is being considered. -Original Message- From: Peter Van Oene [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 10, 2001 1:01 PM To: Hinton Bandele-NBH281 Subject: Re: Networking White Papers (NAP and BGP) What exactly do you consider a NAP to be? *** REPLY SEPARATOR *** On 2/9/2001 at 9:14 AM Hinton Bandele-NBH281 wrote: I am setting up a NAP using 3600's and need a site or location for obtaining whitepapers on both NAP's and
RE: Networking White Papers (NAP and BGP)
As defined in the industry, a Network Access Point (NAP) is a major connection point in the global Internet. It is like a Point-of-Presence (POP) but it is high bandwidth. Currently there are 5 major NAP in the US, but I need white papers on the construction of these major POPs. Hope that helps! -Original Message- From: Peter Van Oene [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 10, 2001 1:01 PM To: Hinton Bandele-NBH281 Subject: Re: Networking White Papers (NAP and BGP) What exactly do you consider a NAP to be? *** REPLY SEPARATOR *** On 2/9/2001 at 9:14 AM Hinton Bandele-NBH281 wrote: I am setting up a NAP using 3600's and need a site or location for obtaining whitepapers on both NAP's and BGP. I am going to use BGP for router redundancy across multiple ISPs. Where can I find these whitepapers on these two subjects? Thanks! Bandele Hinton Motorola Corporation 630-353-8286 (office) 877-992-7925 (pager) [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Networking White Papers (NAP and BGP)
I am setting up a NAP using 3600's and need a site or location for obtaining whitepapers on both NAP's and BGP. I am going to use BGP for router redundancy across multiple ISPs. Where can I find these whitepapers on these two subjects? Thanks! Bandele Hinton Motorola Corporation 630-353-8286 (office) 877-992-7925 (pager) [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
