Eliot Lear
Encyclopedia
Eliot Lear is a longtime member of the Internet Engineering Task Force
and author of several Request for Comments
. He is a consulting engineer for Cisco Systems
after working for Silicon Graphics
as an Internet Architect. Mr. Lear is a graduate of Rutgers University, in New Brunswick, NJ.
Internet Engineering Task Force
The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite...
and author of several Request for Comments
Request for Comments
In computer network engineering, a Request for Comments is a memorandum published by the Internet Engineering Task Force describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.Through the Internet Society, engineers and...
. He is a consulting engineer for Cisco Systems
Cisco Systems
Cisco Systems, Inc. is an American multinational corporation headquartered in San Jose, California, United States, that designs and sells consumer electronics, networking, voice, and communications technology and services. Cisco has more than 70,000 employees and annual revenue of US$...
after working for Silicon Graphics
Silicon Graphics
Silicon Graphics, Inc. was a manufacturer of high-performance computing solutions, including computer hardware and software, founded in 1981 by Jim Clark...
as an Internet Architect. Mr. Lear is a graduate of Rutgers University, in New Brunswick, NJ.
Requests for Comment
A partial list of RFCs authored or co-authored by Eliot Lear:- RFC 1627 - Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
- RFC 1918 - Address Allocation for Private Internets
- RFC 3617 - Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol
- RFC 4192 - Procedures for Renumbering an IPv6 Network without a Flag Day
- RFC 4219 - Things Multihoming in IPv6 (MULTI6) Developers Should Think About
- RFC 4450 - Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents