Robert Sparks

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Jonathan D. Rosenberg

> Home > Persons > Robert Sparks

Publications

2010
[i19]
- view
  - electronic edition via DOI (open access)
  - details & citations
  authority control:
- export record
  dblp key:
  - journals/rfc/rfc5850
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/rfc/rfc5850
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)
2006
[i9]
- view
  - electronic edition via DOI (open access)
  - details & citations
  authority control:
- export record
  dblp key:
  - journals/rfc/rfc4475
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/rfc/rfc4475
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)
2002
[i3]
- view
  - electronic edition via DOI (open access)
  - details & citations
  authority control:
- export record
  dblp key:
  - journals/rfc/rfc3261
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/rfc/rfc3261
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)

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.