default search action
Robert Sparks
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2023
- [c6]Aaron Chuey, Robert Sparks, Hyowon Gweon:
Young children can identify knowledgeable speakers from their causal influence over listeners. CogSci 2023 - [i29]Robert Sparks:
Multiple SIP Reason Header Field Values. RFC 9366: 1-4 (2023)
2010 – 2019
- 2017
- [j2]Christian Jacquenet, Yannick Lair, Francois Le Faucheur, Kevin J. Ma, A. Jean Mahoney, Brian Rosen, Timothy B. Terriberry, Mo Zanaty, Roni Even, Bron Gondwana, Barry Leiba, Scott Mansfield, Bruce Gracie, Jaafar Elmirghanni, Gonzalo Camarillo, Robert Sparks, Russ Housley:
Standards News. IEEE Commun. Stand. Mag. 1(2): 13-19 (2017) - [i28]Robert Sparks:
Clarifications for When to Use the name-addr Production in SIP Messages. RFC 8217: 1-6 (2017) - 2016
- [i27]Robert Sparks, Tero Kivinen:
Tracking Reviews of Documents. RFC 7735: 1-16 (2016) - [i26]Robert Sparks:
Requirements for Improvements to the IETF Email List Archiving, Web-Based Browsing, and Search Tool. RFC 7842: 1-7 (2016) - 2015
- [i25]Robert Sparks:
Explicit Subscriptions for the REFER Method. RFC 7614: 1-14 (2015) - [i24]Robert Sparks, Adam B. Roach:
Clarifications for the Use of REFER with RFC 6665. RFC 7647: 1-6 (2015) - 2013
- [i23]Robert Sparks:
IMAP Access to IETF Email List Archives. RFC 7017: 1-5 (2013) - 2012
- [i22]Robert Sparks:
Requirements for Archiving IETF Email Lists and for Providing Web-Based Browsing and Searching. RFC 6778: 1-8 (2012) - 2011
- [i21]Cullen Jennings, Kumiko Ono, Robert Sparks, Brian Hibbard:
Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms. RFC 6216: 1-67 (2011) - 2010
- [i20]Jon Peterson, Cullen Jennings, Robert Sparks:
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area. RFC 5727: 1-14 (2010) - [i19]Rohan Mahy, Robert Sparks, Jonathan D. Rosenberg, Daniel Petrie, Alan B. Johnston:
A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP). RFC 5850: 1-44 (2010) - [i18]Robert Sparks, Theo Zourzouvillys:
Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests. RFC 6026: 1-20 (2010)
2000 – 2009
- 2009
- [i17]Robert Sparks, Alan B. Johnston, Daniel Petrie:
Session Initiation Protocol (SIP) Call Control - Transfer. RFC 5589: 1-58 (2009) - [i16]Lisa Dusseault, Robert Sparks:
Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard. RFC 5657: 1-12 (2009) - 2008
- [i15]Vijay K. Gurbani, Chris Boulton, Robert J. Sparks:
Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6). RFC 5118: 1-18 (2008) - [i14]Alan B. Johnston, Robert J. Sparks, Chris Cunningham, Steve Donovan, Kevin Summers:
Session Initiation Protocol Service Examples. RFC 5359: 1-170 (2008) - [i13]Robert Sparks, Scott D. Lawrence, Alan Hawrylyshen, Byron Campen:
Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies. RFC 5393: 1-20 (2008) - 2007
- [j1]Robert Sparks:
SIP: basics and beyond. ACM Queue 5(2): 22-33 (2007) - [c5]Robert Sparks:
VoIP with NATs and Firewalls. LISA 2007 - [c4]Robert Sparks:
SIP/VoIP. LISA 2007 - [i12]Robert J. Sparks:
Multiple Dialog Usages in the Session Initiation Protocol. RFC 5057: 1-26 (2007) - 2006
- [c3]Robert Sparks:
VoIP. LISA 2006 - [i11]Robert J. Sparks:
Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction. RFC 4320: 1-7 (2006) - [i10]Robert J. Sparks:
Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE Transaction. RFC 4321: 1-10 (2006) - [i9]Robert J. Sparks, Alan Hawrylyshen, Alan B. Johnston, Jonathan D. Rosenberg, Henning Schulzrinne:
Session Initiation Protocol (SIP) Torture Test Messages. RFC 4475: 1-53 (2006) - 2005
- [c2]Robert Sparks:
VoIP. LISA 2005 - [i8]Alan B. Johnston, Robert J. Sparks:
Session Description Protocol (SDP) Offer/Answer Examples. RFC 4317: 1-24 (2005) - 2004
- [c1]Robert Sparks:
VoIP and IETF Standards. LISA 2004 - [i7]Robert J. Sparks:
The Session Initiation Protocol (SIP) Referred-By Mechanism. RFC 3892: 1-25 (2004) - 2003
- [i6]Robert J. Sparks:
The Session Initiation Protocol (SIP) Refer Method. RFC 3515: 1-23 (2003) - [i5]Alan B. Johnston, Steve Donovan, Robert Sparks, Chris Cunningham, Kevin Summers:
Session Initiation Protocol (SIP) Basic Call Flow Examples. RFC 3665: 1-94 (2003) - [i4]Alan B. Johnston, Steve Donovan, Robert Sparks, Chris Cunningham, Kevin Summers:
Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows. RFC 3666: 1-118 (2003) - 2002
- [i3]Jonathan D. Rosenberg, Henning Schulzrinne
, Gonzalo Camarillo, Alan B. Johnston, Jon Peterson, Robert Sparks, Mark Handley, Eve M. Schooler:
SIP: Session Initiation Protocol. RFC 3261: 1-269 (2002) - [i2]Robert Sparks:
Internet Media Type message/sipfrag. RFC 3420: 1-8 (2002) - 2001
- [i1]Ben Campbell, Robert J. Sparks:
Control of Service Context using SIP Request-URI. RFC 3087: 1-39 (2001)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from ,
, and
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and
to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-05-03 19:57 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by: