Re: [AVT] AVT agenda for Atlanta

Ranjith Mukundan <ranjith.mukundan@wipro.com> Thu, 14 November 2002 06:26 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01830 for <avt-archive@odin.ietf.org>; Thu, 14 Nov 2002 01:26:48 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAE6T2m29387 for avt-archive@odin.ietf.org; Thu, 14 Nov 2002 01:29:02 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE6SXv29363; Thu, 14 Nov 2002 01:28:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE6Rbv29341 for <avt@optimus.ietf.org>; Thu, 14 Nov 2002 01:27:37 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01815 for <avt@ietf.org>; Thu, 14 Nov 2002 01:24:49 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5]) by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gAE6RJ112020 for <avt@ietf.org>; Thu, 14 Nov 2002 11:57:21 +0530 (IST)
Received: from blr-ec-msg01.wipro.com ([10.200.50.99]) by blr-ec-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 14 Nov 2002 11:57:20 +0530
Received: from wipro.com ([192.168.178.78]) by blr-ec-msg01.wipro.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 14 Nov 2002 11:57:20 +0530
Message-ID: <3DD3424B.451F7484@wipro.com>
Date: Thu, 14 Nov 2002 11:57:23 +0530
From: Ranjith Mukundan <ranjith.mukundan@wipro.com>
Reply-To: ranjith.mukundan@wipro.com
Organization: Wipro Technologies
X-Mailer: Mozilla 4.74 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>, avt@ietf.org
Subject: Re: [AVT] AVT agenda for Atlanta
References: <200211140048.gAE0mmj23335@chiron.nge.isi.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Nov 2002 06:27:20.0454 (UTC) FILETIME=[E2BB1A60:01C28BA6]
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

List, Colin & Steve:

Apologies for bringing this up at the eleventh hour.

I would like to check the possibility of a discussion slot at the AVT WG meeting to
*briefly* discuss on a new RTP profile that we need to support for on-hook/off-hook
voiceband data transmission over RTP using the encoding rules (SDMF, MDMF, GDMF) &
procedures for the same, as defined in TR-57, GR-30 & GR-31. In circuit switched
world, this is primarily used to transfer the calling line ID information, Visual
Message Waiting Indicator, caller ID on a call waiting call etc from an IDT
(logical part of a central office)  to an RDT (remote digital terminal), over a DLC
interface (like GR-303) without actually DTMF/MF encoding the digits. This
requirements stems from a need to implement the DLC system over a packet network.

Due to a scheduling oversight on our part, this bubbled up our priority list quite
late - and hence we are now very close to the deadline, if not too late already, to
request for an official slot on the AVT WG meeting.

As the requirment is quite straight-foward, we are of the opinion that a brief
informal discussion would also help/suffice - and might not need a slot on AVT WG
meeting, after all. But all the same, do please let us know if a slot (5-10 mins
max) for this can be squeezed into to AVT agenda, if it is not too late already. I
shall post 2-3 slides and any other info (summary of requirements etc) that you
folks think would be relevant to the list, before we can take this up for
discussion in Atlanta.

As the I-D for detailing this requirement is going to be very brief, we felt that
it would help do a viability check on this list and analyse the need rather than
first submit an I-D.

Please to let us know your thoughts.

regards,
ranjith..

Colin Perkins wrote:

> Folks,
>
> Enclosed is the agenda for the AVT meeting in Atlanta.
>
> 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 those who 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 Friday 15th November.
>
> We also request that all presenters send us their slides at least one
> day ahead of time, preferably in PDF format. 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.
>
> Agenda time is conditional on sending both a summary of open issues and a
> copy of your slides ahead of the meeting, and 5 minutes ahead doesn't count!
>
> 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.
>
> 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 Working Group
>
> CHAIRS: Steve Casner <casner@acm.org>
>         Colin Perkins <csp@csperkins.org>
>
> Tuesday, 19 November at 09:00-11:30
> ===================================
>
> Introduction and status update                          (Casner/Perkins)   15
>         draft-kreuter-avt-rtp-clearmode-00.txt
>         draft-ietf-avt-dsr-05.txt
>         draft-ietf-avt-smpte292-video-07.txt
>         Resolution of G.726 payload format endian-issue
>
> The MIDI Wire Protocol Packetization (MWPP)             (Perkins)           5
>         draft-ietf-avt-mwpp-midi-rtp-05.txt
>         draft-lazzaro-avt-mwpp-coding-guidelines-00.txt
>
> RTP end-to-end liveness test                            (Schulzrinne)      10
>
> RTP Payload for DTMF Digits, Tones and Signals          (Schulzrinne)       5
>         draft-ietf-avt-rfc2833bis-01.txt
>
> RTP Payload Format for iLBC                             (Duric)            15
>         draft-ietf-avt-rtp-ilbc-00.txt
>         draft-ietf-avt-ilbc-codec-00.txt
>
> RTP Payload Format for ATRAC-X                          (Romaine)          15
>         draft-hatanaka-avt-rtp-atracx-00.txt
>
> RTP Payload Format for Uncompressed Video               (Gharai)           15
>         draft-ietf-avt-uncomp-video-01.txt
>
> Resolution of comments on draft-ietf-avt-srtp-05.txt    (Casner)           15
>
> Wednesday, 20 November at 13:00-15:00
> =====================================
>
> MIME Type Registration for MPEG-4                       (Lim)              15
>         draft-lim-mpeg4-mime-01.txt
>
> RTP Payload Format for MPEG-4                           (van der Meer)     15
>
> RTP Payload Format for JVT Video                        (Wenger)           15
>         draft-ietf-avt-rtp-h264-00.txt
>
> RTCP Reporting Extensions                               (Clark)            15
>         draft-ietf-avt-rtcp-report-extns-01.txt
>
> Retransmission                                          (Leon)             15
>         draft-ietf-avt-rtp-retransmission-03.txt
>
> RGL codec and payload format                            (Ramalho)          15
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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