Pronouns: he/him, they/them
Spencer Dawkins is currently a Principal Researcher at Tencent America.
Spencer began participating in the Internet Engineering Task Force in 1996, served as co-chair for the MARTINI, MEDIACTRL, and SIPCLF working groups in the Realtime Applications and Infrastructure Area, and as co-chair for the PILC working group in the Transport Area.
Spencer served on the Internet Architecture Board from 2010 to 2013, when he joined the IESG as Transport Area Director, and served from 2013 to 2019.
Spencer is a recovering IETF process wonk, having served on the General Area Directorate and on the author team for RFC 3774, and as editor for several revisions to the NomCom process specification, and also served on the General Area Review Team from its formation in 2004 until he was selected for the IAB in 2010. Spencer also serves on the Internet Research Steering Group, and served as Technical Director for the SIP Forum from 2012 to 2016.
Prior to joining Tencent, Spencer served as a Senior Standards Manager for Futurewei Technologies and as a consultant for Huawei Technologies, engineered GPRS and VoIP network monitor products for Inet Technologies/Tektronix, did product architecture for protocol accelerators at a start-up and for next-generation SONET switches at Fujitsu Network Communications, and served in a variety of roles at Nortel Networks, where he started out as a business systems computer programmer, but fast-talked his way into networking product development in the R&D group after reading Andrew Tanenbaum’s “Computer Networks”, which changed Spencer’s life.
Spencer holds BBA and MS degrees from the University of North Texas, has a lovely wife named Shirley and four rescue dogs, and volunteers with teenage kids, where the weirdness keeps him young.
|RFC 2757||Jan 2000||Long Thin Networks||11 RFCs|
|RFC 2760||Feb 2000||Ongoing TCP Research Related to Satellites||9 RFCs|
|RFC 3150||Jul 2001||End-to-end Performance Implications of Slow Links||21 RFCs|
|RFC 3155||Aug 2001||End-to-end Performance Implications of Links with Errors||20 RFCs|
|RFC 3933||Nov 2004||A Model for IETF Process Experiments||13 RFCs|
|RFC 4925||Jul 2007||Softwire Problem Statement||12 RFCs|
|RFC 5078||Oct 2007||IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline||3 RFCs|
|RFC 5633||Aug 2009||Nominating Committee Process: Earlier Announcement of Open Positions and Solicitation of Volunteers||2 RFCs|
|RFC 5680||Oct 2009||The Nominating Committee Process: Open Disclosure of Willing Nominees||33 RFCs|
|RFC 7241||Jul 2014||The IEEE 802/IETF Relationship||1 RFC|
|RFC 7418||Dec 2014||An IRTF Primer for IETF Participants||1 RFC|
|RFC 7475||Mar 2015||Increasing the Number of Area Directors in an IETF Area|
|RFC 7890||Jun 2016||Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)||5 RFCs|
|RFC 8318||Jan 2018||IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee||1 RFC|
|RFC 8462||Oct 2018||Report from the IAB Workshop on Managing Radio Networks in an Encrypted World (MaRNEW)||1 RFC|
|RFC 9049||Jun 2021||Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not Taken)||2 RFCs|
|RFC 9317||Oct 2022||Operational Considerations for Streaming Media||1 RFC|
Active Internet-Drafts (3)
Expired Internet-Drafts (30)