[AVTCORE] going forward with draft-lennox-avtcore-rtp-multi-stream

"Roni Even" <ron.even.tlv@gmail.com> Tue, 09 April 2013 07:46 UTC

From: Roni Even <ron.even.tlv@gmail.com>
To: avt@ietf.org
Date: Tue, 09 Apr 2013 10:46:14 +0300
Message-ID: <030101ce34f6$522d9040$f688b0c0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0302_01CE350F.777B3D70"
Thread-Index: Ac409P8YhPv0Pj6eTRmKjBurOm871A==
Content-Language: en-us
Cc: 'Jonathan Lennox' <jonathan@vidyo.com>, 'Colin Perkins' <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: [AVTCORE] going forward with draft-lennox-avtcore-rtp-multi-stream
Precedence: list

Hi,

http://tools.ietf.org/html/draft-lennox-avtcore-rtp-multi-stream-02 was
presented at the Orlando meeting. 

The draft addresses the issue with supporting multiple sources in an RTP
session since current solution will usually support only one source per RTP
session. The draft re-visits RFC 3550 to clarify behavior for multi-source
endpoints and suggests that there may be a need to update RFC 3550 to change
some RTCP timing rules.  It proposes recommendations on optimizations for
reception reports. 

There was a consensus to have this document as a WG document. It will
incorporate some text from draft-ietf-avtcore-multi-media-rtp-session-02
about RTCP size and timing.

Currently we will have the current content but we may look at dividing it to
three draft.

 

The AVTcore chairs are asking  the authors of
draft-lennox-avtcore-rtp-multi-stream to submit it as a WG document and
start working also on updating draft-ietf-avtcore-multi-media-rtp-session-02
accordingly to discuss the multiple payload types in one RTP session. 

 

The author list of both draft is very similar so it should work.

 

Thanks

Roni Even

AVTcore co-chair

[AVTCORE] going forward with draft-lennox-avtcore… Roni Even