View source for User talk:Thomas Wright Sulcer/sandbox7

Temporary file: 

(would be great to get permission to upload covers of HB books) 

Possible article title: '''Howard C. Berkowitz'''


[[Image:Linksys Router.png|thumb|right|alt=Picture of a blue box with lights on it.|A [[router]] is like a traffic light on a computer network -- it shunts data traffic to different places or ''routes'' to enable a computer network to function efficiently. Howard C. Berkowitz designed routers like this one.]]
{{TOC|right}}
'''Howard C. Berkowitz''' is an expert on numerous [[computer network]] related subjects such as [[routers]], [[Computer network|network engineering]], [[Information security|information security]], [[medical information system|medical information systems]], and other areas, and has published books on these subjects. Some of his books are used in graduate level courses at [[university|universities]] as textbooks. He has helped build large networks and has worked as a consultant for private industry as well as the [[Government of the United States of America|US federal government]]. He has two [[patent|patents]] pending. He is also a significant contributor to the online encyclopedia [[Citizendium]], a [[Wikipedia]]-like project which values experts and insists that contributors use their real names, and has served in top management and editorial roles at Citizendium. He is a prolific writer and loves to teach. He has wide interests including electronics for [[commercial fishing]], [[cloud computing]], renewable biodiesel applications, [[Environment (biology)|environmentally friendly]] methods, [[Clinical decision support system|clinical computing]], commercial fishing, [[journalism]], [[pharmacology]], [[Federal Emergency Management Agency|emergency management]], and learning new things. He volunteers with the [[Incident Command System]] and the [[Federal Emergency Management Agency]]. He loves [[cat|cats]] and fishing and lives in Cape Cod, [[Massachusetts]].

==Early career==
Berkowitz was born in Newark, [[New Jersey]] after [[World War II]]. While in high school, he was interested in [[biochemistry]], including [[Pathogen|pathogens]], and found a mentor skilled in medicine, microbiology, and biochemistry; he did a research proposal regarding notalysin and finished this in college. He wrote:
{{quote|It probably was just as well that my mother did not know all of what was in my basement lab. No, no [[explosive|explosives]], just pathogens -- I later did make some improvised things that went '''''bang''''', but that was under guidance while a contractor working with [[U.S. Army Special Forces]].}}

In his early career, he worked in microbial [[biochemistry]], [[FEMA|emergency management]], and [[social science]] support to special operations. During the [[Vietnam War]], he helped build tactical sensors. He was trained in [[intelligence analysis]]. He was a technical contributor to the national network architecture known as "C3I". He was the chief developer of [[Clinical decision support system|clinical computing]] at [[Georgetown University]] Hospital and worked with systems such as ''Index Medicus'' to simulate a doctor's expertise.<ref name=twsMar14p>{{cite news
|title= 
|publisher= aionex.com
|date= 2010-03-14
|url= http://www.aionex.com
|accessdate= 2010-03-14
}}</ref> He has two [[patent|patents]] pending.

He worked at [[GTE]] on the insides of telephone [[Computer network|networks]]. He was a member of the Federal Telecommunications Standards Committee from 1976 to 1980). He worked on ways to keep military telecommunications networks functioning after an attack or disruption. He wrote:
{{quote|The US National Communications Systems and military networks were intended to operate under the most extreme conditions ... the network really needed to operate for 20 minutes or so, but you never knew when the 20 minutes would start, and would just have to cope with network elements randomly turning into mushroom clouds.}}
He worked with systems and protocols including FTSC, ANSI, DISY, OSI, ISO 7498, and OSIRM.

He was the first technical staff member at the Corporation for Open Systems. This was a nonprofit industry research center to develop OSI and ISDN protocols. He managed numerous teams and committees on such systems as FTAM, X.25, IEEE 802. He wrote One memorable experience was lecturing about X.25 testing in [[Japan]]:
{{quote|I had the horrible realization that my PowerPoint slides, translated into [[Japanese]], had gotten into a different order than my English-language notes.}}
But he finished the presentation with the help of a multilingual colleague.{{citation needed}}

==Network expertise==
[[Image:PPVPN with P.png|thumb|left|alt=Diagram.|A [[Virtual private network]] is a way to build a secure network on top of more basic networks. Berkowitz helped design them, and advises users in books, speeches, and conferences about how to make them work effectively. This diagram details one VPN design.]]
When the [[Internet]] became more important in the early 1990s, he worked with the [[Internet Engineering Task Force]] to build [[Internet Protocol|Internet protocols]]. He worked with the [[North American Network Operators Group|North American Network Operators Group or NANOG]] and the Internet Research Task Force or IRTF. His focus was on [[router|routing]], particularly with BGP/IDR and OSPF, and Operations & Management, particularly BMWG & OPSEC, as well as network security, real-time applications, and infrastructure.

At Nortel, Berkowitz was a product line manager who worked on communications standards for networks commonly called [[Computer networking session protocols|protocols]]. He was promoted to Senior Advisor in Nortel's corporate [[Scientific method|research]] laboratory and worked on [[Internet Protocol|Internet protocol]] routing. He spoke at the [[Internet]] Society meeting in [[Stockholm]] on the subject of the limits of the Internet routing system. He helped design state-of-the-art routers.

At Cisco, he taught ''Internetwork Design'' which is a way to merge different networks efficiently into a functioning system. His specialties were [[fault tolerance]], [[Router|router design]], [[Simple Network Management Protocol|network management]]. He worked on systems for [[Telecommunications network|telecommunications]], [[Internet Service Provider|Internet Service Providers (or ISPs)]], [[military]] such as [[C3I-ISR]], and [[medicine]].

In network engineering, Berkowitz worked in:
* communications standards. This enables computers from different manufacturers to be able to talk to each other. He's worked with standards such as ISO/CCITT and ANSI.
* designing [[router|routers]]; a router is like a traffic light of a [[computer network]] since it manages [[data]] traffic to prevent jams.
* building systems to [[Simple Network Management Protocol|manage networks]]. He designs systems to enable firms to handle large volumes of data traffic efficiently.
* designing networks for large [[Internet Service Provider|service providers]]
* enterprise networks

==Writing, speaking==
[[Image:CISCO HQ.JPG|thumb|right|alt=Picture of a modern office building of 5 stories.|Berkowitz taught courses at Cisco including ''Internetwork Design''.]]
Berkowitz wrote:
* '''''WAN Survival Guide: Strategies for VPNs and Multiservice Networks''''' (2000) (John Wiley & Sons) # ISBN-10: 0471384283 # ISBN-13: 978-0471384281<ref name=twsMar14p1>{{cite news
|author= Howard Berkowitz 
|title= WAN Survival Guide: Strategies for VPNs and Multiservice Networks
|publisher= Amazon
|date= November 10, 2000
|url= http://www.amazon.com/WAN-Survival-Guide-Strategies-Multiservice/dp/0471384283
|accessdate= 2010-03-14
}}</ref> The book helped managers of Wide Area Networks by helping them assess user requirements, lower costs by using multiservice networking, reducing downtime, managing QoS, using dedicated lines and frame relay and ATM to provide basic services, help managers handle [[Virtual private network|virtual private networks or VPNs]], manage security, roaming, mobility, and database fault tolerance and multihoming. The book was described by several reviewers as an "excellent resource."<ref name=twsMar14o>{{cite news
|title= Bandwidth Solutions For Hungry Companies
|publisher= Router Freak: Router and Switch Reviews and Tips for Network Engineers
|date= 2010-03-14
|url= http://www.routerfreak.com/bandwidth-solutions-for-hungry-companies/
|accessdate= 2010-03-14
}}</ref> Another reviewer wrote: "These topics could be a dry, academic exercise, but (as usual) Howard Berkowitz spices the material with "war stories" of actual WAN technology assignments (and why the customers didn't really want they just asked for) and the injection of humor as a means of remembering rules (such as Schwarzenegger's Laws of Networking).<ref name=twsMar14q>{{cite news 
|title=  Howard strikes again -- WAN Survival Guide: Strategies for VPNs and Multiservice Networks by Howard Berkowitz (review)
|publisher= Amazon
|date= March 24, 2001
|url= http://www.m.amazon.com/gp/cdp/member-reviews/A3993DTTC2J4HN?ie=UTF8&sort_by=MostRecentReview
|accessdate= 2010-03-14
}}</ref> The book is an excellent "place to start" for people wanting to learn more about what's "inside the cloud".

* '''''Building Service Provider Networks''''' (2002) John Wiley & Sons, ISBN-10: 0471099228 ISBN-13: 978-0471099222<ref name=twsMar14q>{{cite news
|author= Howard Berkowitz
|title= Building Service Provider Networks
|publisher= John Wiley & Sons
|date= May 15, 2002
|url= http://www.amazon.com/Building-Service-Provider-Networks-Berkowitz/dp/0471099228
|accessdate= 2010-03-14
}}</ref> This book offered guidance to network and service provider engineers to help them meet customer needs regarding data, voice, and video. It showed them how to build information systems. The first step is translating customer needs into technical requirements. The next step is managing address space. The book dealt with issues such as data link facilities, core transmission technologies, using the Border Gateway Protocol (and applying it to meet specific customer needs), designing the Point of Presence carrier, scalability of the intraprovider core, interprovider connectivity, and extending [[Virtual private network|Virtual private networks]] beyond a single provider for maximum efficiency. A reviewer of the book wrote: "Howard Berkowitz is known in the networking community for his writing which has helped many, many people earn advanced certifications. But Howard doesn't write to that goal; he writes, instead, to the goal of helping people understand what it takes to make a network actually perform and deliver the business function it was purchased for. This is another in that series of lucid and focused books. -- A. A. Hines, senior network engineer.<ref name=twsMar14r1>{{cite news
|author= A. A. Hines
|title=  Too bad so many startups never read this book
|publisher= Amazon
|date= December 13, 2002
|url= http://www.amazon.com/Building-Service-Provider-Networks-Berkowitz/product-reviews/0471099228/ref=dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1
|accessdate= 2010-03-14
}}</ref> It is used as a textbook at the Victoria University at Wellington in [[New Zealand]] in its school of [[Engineering]] and [[Computer Science]].<ref name=twsMar14r>{{cite news
|title= NWEN 403: Advanced Network Engineering
Course Outline 2010 Tri 1 -- Textbook -- Howard Berkowitz, Building Service Provider Networks 
|publisher= Victoria University at Wellington
|date= 2010-03-14
|url= http://ecs.victoria.ac.nz/Courses/NWEN403_2010T1/CourseOutline
|accessdate= 2010-03-14
}}</ref>

* Numerous industry presentations, speeches, conferences.

* Tutorials on routing for the [[North American Network Operators Group]].<ref name=twsMar14o>{{cite news
|author= Howard C. Berkowitz
|title= Tutorial
|publisher= NANOG
|date= 2010-03-14
|url= http://nanog.org/authors.html
|accessdate= 2010-03-14
}}</ref> 

* He wrote [[Internet Engineering Task Force]] RFCs as author or co-author, including RFC 1912 and RFC 2071.<ref> {{Citation
  | first1 = P
  | last1 = Ferguson
  | first2 = H
  | last2 = Berkowitz
  | title = Network Renumbering Overview: Why would I want it and what is it anyway?
  | year = 1997
  | publisher = IETF
  | url = http://www.ietf.org/rfc/rfc2071.txt
  | id = RFC2071}}</ref>, RFC 2072<ref> {{Citation
  | first1 = H
  | last1 = Berkowitz
  | title = Router Renumbering Guide 
  | year = 1997
  | publisher = IETF
  | url = http://www.ietf.org/rfc/rfc2072.txt
  | id = FDR }}</ref>, RFC 4098<ref>{{Citation
  | first1 = H
  | last1 = Berkowitz
  | first2 = E
  | last2 = Davies
  | first3 = S
  | last3 = Hares
  | first4 = P
  | last4 = Krishnaswamy
  | first5 = M
  | last5 = Lepp
  | title = Terminology for Benchmarking BGP Device Convergence in the Control Plane 
  | year = 2005
  | publisher = IETF
  | url = http://www.ietf.org/rfc/rfc4098.txt
  | id = RFC4098 }}</ref>

==References==
{{reflist}}