IETF

I'm quite active in the Internet Engineering Task Force (IETF). I am co-chair of the IP Telephony working group, and was formerly chair of the SIP working group. I am co-author of the Session Initiation Protocol (SIP) RFC 3261. I am also editor of many RFCs and Internet Drafts.

The ideal place to obtain information on SIP is at the Columbia University SIP Page, run by Henning Schulzrinne. The SIP Forum is also a good resource for information.

Slides from IETF Meetings

Can be found here.

SIP/SIPPING/MMUSIC Internet Drafts

Here are pointers to pages for the drafts I have written for SIP, SIPPING and/or MMUSIC which are currently active:
  1. A Media Feature Tag for Application Subtypes
  2. Identifying Services in SIP
  3. Indicating Support for ICE
  4. User Agent Loose Routing
  5. Discovery and HA in SIP Outbound
  6. Coexistence of P-Asserted-ID and SIP Identity
  7. Hitchhikers Guide to SIP
  8. Requirements for Overload Control in SIP
  9. Rejecting Anonymous Requests in SIP
  10. ICE Extension to TCP
  11. Clarifying the Construction of the Route header field in SIP
  12. The Target-Dialog Header Field
  13. Architectural and Design Principles in SIP
  14. Requirements for Consent-Based Communications in SIP
  15. A Framework for Consent-Based Communications in SIP
  16. A Multiplexing Mechanism for the Real-Time Protocol (RTP)
  17. Spam and SIP
  18. An RTP Denial Of Service Attack and its Prevention
  19. Interactive Connectivity Establishment (ICE): A Methodology for NAT Traversal for SIP
  20. Mechanism for Globally Routable UA URIs
  21. A Framework for Application Interaction in SIP
  22. A Framework for Conferencing with the Session Initiation Protocol
  23. A SIP Event Framework for Conferencing State
  24. A SIP Event Framework for Dialog State
  25. Requirements for Session Policy in SIP
  26. NAT and Firewall Scenarios and Solutions for SIP
  27. A SIP Interface to VoiceXML Dialog Servers
  28. An Application Server Component Architecture for SIP
  29. Guidelines for Authors of SIP Extensions
  30. The SIP Session Timer
  31. Use Cases for SIP Caller Preferences and Callee Capabilities
  32. SIP Telephony Call Flow Examples
  33. SCTP as a Transport for SIP

Here are older drafts, for historic purposes. These are not being pursued, or where merged or changed in some way. For information on what happened, click the link.

  1. Requirements for Globally Routable UA URIs
  2. Firewall Control Protocol Framework and Requirements
  3. SIP Enabled Services to Support the Hearing Impaired
  4. The SIP INFO Method Considered Harmful
  5. Proposed Changes to Connection Oriented Media Handling in the Session Description Protocol (SDP)
  6. SIP Call Control
  7. Mandating SIP Extension Support by Servers
  8. Getting SIP Through Firewalls and NATs
  9. SIP Traversal Through Enterprise NATs and Firewalls
  10. Request Header Integrity in SIP and HTTP Digest using Predictive Nonces
  11. Early Media in SIP
  12. Reconstituting Call State in SIP User Agents
  13. Unifying Early Media, Manyfolks, And HERFP
  14. SIP Event Packages for Call Leg and Conference State

Unpublished SIP Documents

I used to have a link here that discussed the problem of request merging; however, this document is now obsolete. Please see the sip-bis specification, versions -05 and later, for details.

SIMPLE and IMPP

The Instant Messaging and Presence Protocol (IMPP) working group was chartered in 1998 to develop a framework and requirements for IM and presence protocols. After finishing that work, they were unable to gain consensus on a single protocol, so a small number of groups were formed to develop separate protocols. One of these is SIMPLE - SIP for Instant Messaging and Presence Leveraging Extensions - which was approved as a working group February 2001. It is standardized a presence and IM protocols based on a proposal I, along with colleagues from dynamicsoft, Columbia U., Cisco, and Microsoft, proposed.

  1. A Data Model for Presence
  2. A Presence Server Processing Model
  3. Multiple Insertions in XCAP
  4. An XML Representation for Expression of Presence Policy Capabilities
  5. An XML Representation for Expressing Policy Capabilities
  6. Extensions to PIDF for Conveying Phone State
  7. An XML Configuration Access Protocol (XCAP)
  8. XCAP Diff XML Format
  9. XCAP Change Logs
  10. An XML Document Format for Representing Resource Lists
  11. Presence Authorization Rules
  12. Requirements for Manipulation of Data Elements in SIMPLE
  13. Advanced Instant Messaging Requirements for the Session Initiation Protocol
  14. A Component Model for SIMPLE
  15. A SIP Event Notification Extension for Resource Lists (formerly Buddy List Presence)
  16. SIP Instant Message Sessions
Here are slides from some meetings:
  1. SIMPLE March 2001 Open Issues

IAB Internet Drafts

  1. What's in a Name: False Assumptions about DNS Names
  2. Considerations for NAT Traversal Techniques

MIDCOM (Middlebox Communications)

MIDCOM is dealing with traversal of applications through firewalls and NATs. I have been actively involved in this group.

  1. Simple Traversal of UDP over NAT (STUN) - A Revision of RFC 3489
  2. Traversal Using Relay NAT (TURN)

IPTEL

The IPTEL group, which I chair, is chartered to work on the TRIP (Telephony Routing over IP) and CPL (Call Processing Language) specifications. You can find a link to the external IPTEL web page at http://www.bell-labs.com/mailing-lists/iptel. The official IETF page is at http://www.ietf.org/html.charters/iptel-charter.html

  1. Requirements for Gateway Registration
  2. Usage of TRIP in Gateways for Exporting Telephony Routes
  3. RFC3219, Telephony Routing over IP
  4. RFC2871, A Framework for Telephony Routing over IP

Audio/Video Transport WG (AVT)

I'm involved in the activities of AVT. I edit a number of the groups working documents. Here's some of them:

  1. RFC3158, RTP Testing Strategies
  2. RFC2733, Generic Forward Error Correction
  3. RFC3009, Registration of parityfec MIME Types
  4. RFC2762, Sampling of the Group Membership in RTP
  5. An RTP Payload Format for Reed Solomon Codes
  6. A Taxonomy of Feedback for Multicast
  7. Issues and Options for RTP Multiplexing
  8. RTP Scalability
  9. Elevating RTP to Protocol Status

Multicast Feedback

Both RTCP and reliable multicast protocol make use of feedback to provide useful information to senders and other participants. This document presents a taxonomy of feedback for multicast, as a potential first step towards constructing a general purpose feedback protocol.

  1. M. Hofmann, J. Nonnenmacher, J. Rosenberg, H. Schulzrinne," A Taxonomy of Feedback for Multicast", IETF Internet Draft draft-hnrs-rmt-avt-feedback-00.txt, June 24, 1999. [Text] [PPT Slides]

Reed Solomon Coding

We've taken the ideas from our parity FEC draft, and discussed how to apply them to Reed Solomon coding

  1. J. Rosenberg, H. Schulzrinne, " An RTP Payload Format for Reed Solomon Codes", IETF Internet Draft draft-ietf-avt-reedsolomon-00.txt, November 1998

RTP Multiplexing

RTP multiplexing is useful between IP telephony gateways, to carry multiple voice streams in one RTP packet. We first proposed the concept at the end of 1996. Its now a working item of AVT.

  1. J. Rosenberg, H. Schulzrinne, "Issues and Options for RTP Multiplexing",IETF Internet Draft draft-ietf-avt-muxissues-00.txt, October 1, 1998. [Text ]
  2. J. Rosenberg, H. Schulzrinne, " An RTP Payload Format for User Multiplexing ", IETF Internet Draft draft-ietf-avt-aggregation-00.txt, May 1998. [Text] [Slides, PPT95]
  3. J. Rosenberg, H. Schulzrinne, "Issues and Options for Voice Aggregation within RTP", IETF Internet Draft, draft-rosenberg-itg-00.txt, December 1996.

RTP Scalability

I've worked on timer reconsideration, the scalability algorithm used in RTCP. Its described in several drafts and is now part of the version of RTP going to draft standard.

  1. J. Rosenberg, H. Schulzrinne, "New Results in RTP Scalability", IETF Internet Draft, draft-ietf-avt-byerecon-00.ps, November 1997 Text also available. Slides: [Powerpoint 95][ Postscript][PDF]
  2. J. Rosenberg, H. Schulzrinne, "Timer Reconsideration for Enhanced RTP Scalability", IETF Internet Draft, draft-ietf-avt-reconsider-00.ps, July 1997 Text also available. Slides: [ Postscript]
  3. J. Rosenberg, H. Schulzrinne, "Slides on Timer Reconsideration", presented at the Memphis IETF, April 1997
  4. J. Rosenberg, H. Schulzrinne, "Slides on RTCP Scalability", presented at the San Jose IETF, December 1996

RTP to Protocol Status

We proposed making RTP its own protocol number, to facilitate identification of RTP packets in routers.

  1. J. Rosenberg, B. Aboba, H. Schulzrinne, "Elevating RTP to Protocol Status",IETF Internet Draft, draft-rosenberg-rtpproto-00.txt, March 1998 [PPT Slides] [PDF Slides]

Service Location Protocol (SVRLOC)

Discovering SIP Servers

This work proposes how SLP can be used to discover SIP servers, both registrars and local outbound proxies.

  1. J. Kempf, J. Rosenberg, "Finding a SIP Server with SLP", IETF Internet Draft draft-kempf-sip-findsrv-00.txt, February 15 2000. Work in Progress. [ Text]

Wide Area Service Discovery

I've done some work on wide area services. I also co-chaired a BoF session once on Wide Area Service Discovery. There's a web page for the WASRV BoF. Here are some related drafts:

  1. J. Rosenberg, R. Moats, E. Guttman, H. Schulzrinne, " WASRV Architecutral Principles",IETF Internet Draft draft-rosenberg-wasrv-arch-00.txt, February 1998 [PPT Slides] [PDF Slides]
  2. J. Rosenberg, H. Schulzrinne, "Wide Area Network Service Location", IETF Internet Draft, draft-ietf-svrloc-wasrv-01.txt, November 1997. [Mar 98 Slides, PPT] [Mar 98 Slides, PDF]
  3. J. Rosenberg, H. Schulzrinne, "Wide Area Network Service Location", IETF Internet Draft, draft-ietf-srvloc-wasrv-00.txt, July 1997.

And some slides from presentations:

  1. J. Rosenberg, H. Schulzrinne, "Slides on Wide Area Service Location", presented at the Washington IETF, December 1997. [Powerpoint 95][ Postscript][PDF]
  2. J. Rosenberg, H. Schulzrinne, " Slides on Wide Area Network Service Location",presented at the Munich IETF (svrloc wg) in August 1997

Instant Messaging and Presence Protocol (IMPP)

The IMPP group was formed in the apps area to undertake to task of specifying an instant message and presence protocol, scalable to the Internet. I view IMPP as an integral part of a complete communications sytem, often a precursor or part of Internet telephony. Here are some drafts I have written for it.

Outputs of The Nine

I was a member of a team of nine experts put together to try and come to agreement on what is common, and what is irreconcilably different between the various IMPP protocol proposals. We completed our work on August 22, 2000. Here are the resulting drafts:

  1. D. Crocker, A. Diacakis, F. Mazzoldi, C. Huitema, G. Klyne, M. Rose, J. Rosenberg, R. Sparks, H. Sugano, "A Common Profile for Instant Messaging", IETF Internet Draft draft-mrose-impp-common-00.txt, August 22, 2000. Work in Progress. [Text]
  2. D. Crocker, A. Diacakis, F. Mazzoldi, C. Huitema, G. Klyne, M. Rose, J. Rosenberg, R. Sparks, H. Sugano, "A Framework for Moving IMPP Forward", IETF Internet Draft draft-thenine-impp-differences-00.txt, August 22, 2000. Work in Progress. [Text]

Complete SIP For Presence and IM Solution

This is a collection of draft submitted to IETF on June 15, 2000 for consideration by IESG as the baseline protocol for IM and presence.

  1. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, D. Oran, "SIP Extensions for Presence", IETF Internet Draft draft-rosenberg-impp-presence-00.txt , June 15, 2000. Work In Progress. [Text]
  2. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, D. Oran, "SIP Extensions for Instant Messaging", IETF Internet Draft draft-rosenberg-impp-im-00.txt , June 15, 2000. Work In Progress. [Text]
  3. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, "SIP Extensions for Presence Authorization", IETF Internet Draft draft-rosenberg-impp-qauth-00.txt , June 15, 2000. Work In Progress. [Text]
  4. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, "A Data Format for Presence Using XML", IETF Internet Draft draft-rosenberg-impp-pidf-00.txt , June 15, 2000. Work In Progress. [Text]
  5. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, "A Lightweight Data Information Format (LPIDF)", IETF Internet Draft draft-rosenberg-impp-lpidf-00.txt , June 15, 2000. Work In Progress. [Text]
  6. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, "An XML Based Format for Watcher Information", IETF Internet Draft draft-rosenberg-impp-watcherinfo-00.txt , June 15, 2000. Work In Progress. [Text]
  7. J. Rosenberg, D. Willis, R. Sparks, B. Campbell, H. Schulzrinne, J. Lennox, C. Huitema, B. Aboba, D. Gurle, "An XML Based Format for Presence Buddy Lists", IETF Internet Draft draft-rosenberg-impp-buddylist-00.txt , June 15, 2000. Work In Progress. [Text]

IMPP Model

This document, RFC2778, proposes a model for presence and Instant Messaging. It is an informational RFC generated by the IMPP working group.

  1. M. Day, J. Rosenberg, H. Sugano "A Model for Presence and Instant Messaging "IETF Request For Comments (RFC) 2778, February 2000. Text
  2. M. Day, J. Rosenberg, H. Sugano "A Model for Presence and Instant Messaging "IETF Internet draft draft-ietf-impp-model-03.txt, September 1, 1999. Text
  3. M. Day, J. Rosenberg, H. Sugano "A Model for Presence and Instant Messaging "IETF Internet draft draft-ietf-impp-model-02.txt, August 23, 1999. Text
  4. M. Day, J. Rosenberg, "A Model for Presence and Instant Messaging "IETF Internet draft draft-ietf-impp-model-01.txt, July, 1999. Text
  5. M. Day, J. Rosenberg, "A Model for Presence and Instant Messaging "IETF Internet draft draft-ietf-impp-model-00.txt, April 23, 1999. Text

SIP for Presence

We propose the usage of SIP (RFC2543) for presence. There are several basic reasons why we feel its a good fit:

Our draft goes into more details, providing additional motivations and describing the required extensions for SIP.

  1. J. Rosenberg, H. Schulzrinne, "SIP for Presence", IETF Internet Draft draft-rosenberg-sip-pip-00.txt, November 1998 [Text]

and some slides:

  1. J. Rosenberg "SIP, PIP and IDIP"presented at the 42nd IETF in Chicago, August 1998, to the PIPR BoF Session. [PPT Slides]
  2. J. Rosenberg "Slides on SIP for Presence"presented at the 41st IETF in Los Angeles, March 1998, to the PIPR BoF Session. [PPT Slides] [PDF Slides]