datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Liaison Statement: IETF Liaison Statement from MMUSIC wg: on-going work on RTSP 2.0 and request for information on RTSP extensions

Submission Date: 2008-01-07
From: IETF MMUSIC WG (Jean-Francois Mule)
To: Open Mobile Alliance Broadcasting Working Group (technical-comments@mail.openmobilealliance.org, OMA-LIAISON@MAIL.OPENMOBILEALLIANCE.ORG)
Cc:Dean Willis
Cullen Jennings (IETF RAI Area Director)
Jon Peterson (IETF RAI Area Director)
MMUSIC mailing list
Response Contact: Jean-Francois Mule
Technical Contact: Jean-Francois Mule
Purpose: For action
Deadline: 2008-04-07 Action Taken
Attachments: (none)
Body:
We would like to inform you of the on-going work on version 2.0
   of the Real Time Streaming Protocol (RTSP) in the IETF MMUSIC 
   working group.  RTSP 2.0 is intended to obsolete and replace 
   RTSP 1.0.  We plan to freeze any protocol feature changes by
   August 1st 2008 to complete RTSP 2.0 by the end of 2008.
   The latest Internet-Draft can be found at:
   http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis

   The recently-published RFC 4775 [1] on "Procedures for Protocol
   Extensions and Variations" defines guideline procedures for
   cooperation between the IETF and outside entities on the
   extension of IETF protocols.  It attempts to ensure that
   extensions will conform to the applicable architectural
   principles and technical criteria.  Any development of protocol
   extensions and mechanisms related to RTSP would need to occur
   under the guidelines of RFC 4775.

   We would like to request that any RTSP extensions that may be in
   the scope of RTSP 2.0 or require IETF review (per RFC 4775) be
   discussed in IETF MMUSIC working group to seek wider community
   reviews and expert comments.  We would therefore appreciate if
   you let us know if any group within your organization is working
   on technical specifications that make use of RTSP and if any
   protocol extensions are being considered.  In the case
   extensions are being worked on, we would appreciate if you could
   provide any details (requirements, mechanisms, draft solution,
   etc.).

   Sincerely,

     Joerg Ott (MMUSIC co-chair)
     Jean-Francois Mule (MMUSIC co-chair)

Reference:
 [1]  Bradner S., Carpenter B., Narten T., "Procedures for Protocol
      Extensions and Variations", RFC 4775, December 2006.
      http://tools.ietf.org/html/rfc4775