RE: [AVT] Draft AVT agenda

ROUX Catherine FTRD/DMI/REN <catherine.roux@rd.francetelecom.com> Mon, 03 December 2001 18:36 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20160 for <avt-archive@odin.ietf.org>; Mon, 3 Dec 2001 13:36:46 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA06290 for avt-archive@odin.ietf.org; Mon, 3 Dec 2001 13:36:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA06213; Mon, 3 Dec 2001 13:35:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA06121 for <avt@optimus.ietf.org>; Mon, 3 Dec 2001 13:35:48 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [193.49.124.32]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20065 for <avt@ietf.org>; Mon, 3 Dec 2001 13:35:45 -0500 (EST)
Received: by p-voyageur.rd.francetelecom.fr with Internet Mail Service (5.5.2653.19) id <YFGSPGCD>; Mon, 3 Dec 2001 16:29:44 +0100
Message-ID: <A7615804EC6DD511B90B0004ACE5BE4B5CBCBC@L-RMHS.rd.francetelecom.fr>
From: ROUX Catherine FTRD/DMI/REN <catherine.roux@rd.francetelecom.com>
To: 'Colin Perkins' <csp@isi.edu>, avt@ietf.org
Subject: RE: [AVT] Draft AVT agenda
Date: Mon, 03 Dec 2001 16:28:22 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C17C0F.24EB5240"
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-BeenThere: avt@ietf.org

First I send you a summary of my presentation with open issues.
I send you my slides after.

Thanks to organise the meeting .

Yours sincerely

Cath Roux

TP payload formats for MPEG4
draft-curet-avt-rtp-mpeg4-flexmux-02.txt

Summary

This draft presents the payload format for flexMuxtiplexed files.
It allows to transmit several Elementary Stream in one RTP Channel, to
give and keep a strong synchronism  between the streams which are
multiplexed.

The general  RTP header is kept, but  we have to precise the use OF The
following fields  :
        -The RTP timeStamp is the value of the FCR if it exists or the
emission time
of the RTP packet.
        -The bit M is managed by the upper levels(coder or SL) and indicates
the end of
one or all the Aus which are in this RTP payload.

The payload is compouned of one or several inchanged Flexmux packets.
This payload allows also to transmit the in-band signalling; thus the
flexmux can be dynamically change. This signalling is given in the same
channel as the FCR.
When the signalling is not transmitted IN BAND, we propose a SDP syntax to
transmit it in the out-of-band signalling Channel. So we have added a new
media-type & subType : "application mpeg4-flexmux"
and a new type parameter for the "a" attribute line  "mpeg4-flexmuxinfo"
which can be transmitted in different formS : binary XML or URL 

example
m = application 4444 RTP/AVP  96
a = rtpmap:96 mpeg4-flexmux/1000
a = mpeg4-flexmuxinfo:"http://example.com/FlexMuxdescriptor.dat"

OPEN issues:
We want to discuss the conformity of the proposal when the signalling
is transmitted out of the band (SDP syntax )



-----Message d'origine-----
De : Colin Perkins [mailto:csp@isi.edu]
Envoye : lundi 3 decembre 2001 07:29
A : avt@ietf.org
Objet : [AVT] Draft AVT agenda


Folks,

Enclosed is the draft agenda for the AVT working group meeting at the Salt
Lake City IETF. Please send comments and corrections to the working group
chairs, by Tuesday 4th December.

Those who have agenda time scheduled are requested to prepare a summary of
the issues they wish to discuss, and to send this to the mailing list ahead
of the meeting. This gives folks that won't be attending the opportunity to 
post their comments and concerns, and potentially even reach some consensus,

before the meeting time is consumed. It also gives other participants the 
opportunity to consider the issue in more depth. Summary messages should be 
sent to the mailing list by Tuesday 4th December.

We also request that all presenters send us their slides ahead of time. This

has multiple purposes:

  - It streamlines the presentation process by having the presentations on 
    a single laptop.

  - It avoids the delay that sometimes occurs in getting the presentations
    sent to us after the meeting, for inclusion in the minutes.

  - It allows us to preview the presentations to see if they are following 
    the guidelines for what should be covered during the meeting.

Those presenting new drafts: briefly describe the basic problem and your
proposed solution, discuss known issues, limitations and problems, outline
where you want input from the working group, and how you wish us to proceed.
When presenting work which has been previously discussed: describe only the
changes from the previous draft, highlight unresolved problems, and propose
future directions. Presenters are reminded of the requirements for
disclosure 
of intellectual property relating to contributions, in section 10 of RFC
2026. 

Agenda time is conditional on sending both a summary of open issues and a
copy of your slides ahead of the meeting.

We strongly encourage all participants to read all relevent drafts before 
the meeting, and to comment on the open issues raised on the mailing list. 

Thanks for your assistance to try to conduct an effective meeting.

Colin & Steve



============================================================================
===
Audio/Video Transport WG (AVT)

Monday, December 10 at 1930-2200
Wednesday, December 12 at 0900-1130
===================================

CHAIRS: Steve Casner <casner@acm.org>
        Colin Perkins <csp@isi.edu>

AGENDA:

Session 1:

- Introduction and status (Casner/Perkins)				10
	Published or with RFC editor:
		RFC 3158
		draft-ietf-avt-dv-audio-04.txt
		draft-ietf-avt-dv-video-04.txt
	Under revision after IESG review:
		draft-ietf-avt-rtp-amr-10.txt
	Last call:
		draft-ietf-avt-crtp-enhance-03.txt
		draft-ietf-avt-tcrtp-04.txt
		draft-ietf-avt-uxp-01.txt
		draft-ietf-avt-ulp-02.txt 
		draft-ietf-avt-rtp-cn-04.txt

- RTP Payload formats for MPEG-4
	draft-ietf-avt-mpeg4-multiSL-02.txt 		(Gentric)	10
	draft-ietf-avt-mpeg4-simple-00.txt		(van der Meer)	10
	draft-curet-avt-rtp-mpeg4-flexmux-01.txt 	(Roux)		10

- RTP payload format for GSM EFR speech			(Barany)	15
	draft-barany-avt-efr-00.txt
	draft-ietf-avt-profile-new-12.txt section 4.5.9

- RTP Payload Format for EVRC, SMV and Frame-Based Vocoders (Li)	15
	draft-li-avt-vocoder-00.txt 

- RTP Payload Format for AC-3 Streams 			(Flaks)		15
	draft-flaks-avt-rtp-ac3-00.txt

- MWPP: A resilient MIDI RTP packetization 		(Lazzaro)	15
	draft-lazzaro-avt-mwpp-midi-nmp-00.txt

- RTP Payload Format for Distributed Speech Recognition	(Xie)		15
	draft-ietf-avt-dsr-00.txt



Session 2: 

- RTP payload format for JPEG 2000 video streams 	(Edwards)	15
	draft-edwards-avt-rtp-jpeg2000-00.txt

- Update to RTP specification and profile		(Casner)	15
	draft-ietf-avt-rtp-new-11.txt, .ps
	draft-ietf-avt-profile-new-12.txt, .ps
	draft-ietf-avt-rtp-mime-06.txt 
	draft-ietf-avt-rtcp-bw-05.txt

- Secure RTP profile					(Carrara)	15
	draft-ietf-avt-srtp-02.txt

- RTP extensions for classification and priority
	draft-carlberg-rtp-classifier-extension-00.txt	(Carlberg)	 5
	draft-polk-avt-rtpext-res-pri-00.txt		(Polk)		 5
	Discussion							10

- Extended RTP Profile for RTCP-based Feedback		(Ott)		15
	draft-ietf-avt-rtcp-feedback-01.txt
	draft-burmeister-avt-rtcp-feedback-sim-00.txt

- RTP retransmission
	draft-leon-retransmission-01.txt		(Leon)		15
	draft-ietf-avt-rtp-selret-03.txt

- RTCP Extension for SSM Sessions with Unicast feedback (Chesterfield)	15
	draft-chesterfield-avt-rtcpssm-02.txt

- Extending RTCP for call quality metrics		(Massad)	 5


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
http://www1.ietf.org/mailman/listinfo/avt