From daemon@optimus.ietf.org  Tue Jan  1 00:18:42 2002
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 AAA13237
	for <avt-archive@odin.ietf.org>; Tue, 1 Jan 2002 00:18:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA13712
	for avt-archive@odin.ietf.org; Tue, 1 Jan 2002 00:18:41 -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 AAA13688;
	Tue, 1 Jan 2002 00:16:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA13661
	for <avt@optimus.ietf.org>; Tue, 1 Jan 2002 00:16:30 -0500 (EST)
Received: from web13607.mail.yahoo.com (web13607.mail.yahoo.com [216.136.175.118])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA13225
	for <avt@ietf.org>; Tue, 1 Jan 2002 00:16:30 -0500 (EST)
Message-ID: <20020101051630.17504.qmail@web13607.mail.yahoo.com>
Received: from [164.164.42.6] by web13607.mail.yahoo.com via HTTP; Mon, 31 Dec 2001 21:16:30 PST
Date: Mon, 31 Dec 2001 21:16:30 -0800 (PST)
From: Bino george <a_binogeorge@yahoo.com>
Subject: RE: [AVT] Reg G.711 Silence Suppression Negotiation 
To: avt@ietf.org
Cc: sharma.kanchinadham@wcom.com, csp@isi.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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

Respected Collin and Sharama:
            
          A Large community is waiting for your 
reply.
          
          If new Payload Type 13 is included into
draft-ietf-avt-profile-new-xx. is helpful to us. 

bino
       


=====
Bino George 

Work: 91-080-5588257 extn: 210
"Don't wait to have a lot, to share a bit"

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

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



From daemon@optimus.ietf.org  Tue Jan  1 12:39:13 2002
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 MAA13891
	for <avt-archive@odin.ietf.org>; Tue, 1 Jan 2002 12:39:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00312
	for avt-archive@odin.ietf.org; Tue, 1 Jan 2002 12:39:16 -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 MAA00298;
	Tue, 1 Jan 2002 12:37:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00263
	for <avt@optimus.ietf.org>; Tue, 1 Jan 2002 12:37:31 -0500 (EST)
Received: from purple.nge.isi.edu (reserved.east.isi.edu [65.114.168.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13867
	for <avt@ietf.org>; Tue, 1 Jan 2002 12:37:27 -0500 (EST)
Received: from purple.nge.isi.edu (csp@localhost)
	by purple.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g01HbPn01747;
	Tue, 1 Jan 2002 12:37:25 -0500
Message-Id: <200201011737.g01HbPn01747@purple.nge.isi.edu>
To: Bino george <a_binogeorge@yahoo.com>
cc: avt@ietf.org, sharma.kanchinadham@wcom.com
Subject: Re: [AVT] Reg G.711 Silence Suppression Negotiation 
In-Reply-To: Your message of "Mon, 31 Dec 2001 21:16:30 PST."
             <20020101051630.17504.qmail@web13607.mail.yahoo.com> 
Date: Tue, 01 Jan 2002 12:37:25 -0500
From: Colin Perkins <csp@isi.edu>
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

--> Bino george writes:
>          If new Payload Type 13 is included into
>draft-ietf-avt-profile-new-xx. is helpful to us. 

The new profile lists payload type 13 as reserved. The definition is in the
comfort noise payload format (draft-ietf-avt-rtp-cn-04.txt), along with the
MIME registration.

Colin

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



From daemon@optimus.ietf.org  Wed Jan  2 04:34:01 2002
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 EAA01402
	for <avt-archive@odin.ietf.org>; Wed, 2 Jan 2002 04:33:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA00444
	for avt-archive@odin.ietf.org; Wed, 2 Jan 2002 04:33:58 -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 EAA00416;
	Wed, 2 Jan 2002 04:33:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA00386
	for <avt@optimus.ietf.org>; Wed, 2 Jan 2002 04:33:00 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01384
	for <avt@ietf.org>; Wed, 2 Jan 2002 04:32:58 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id DAA10515;
	Wed, 2 Jan 2002 03:32:30 -0600 (CST)
Received: from ssd (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g029WMm11756;
	Wed, 2 Jan 2002 03:32:24 -0600 (CST)
Message-ID: <015401c1936f$6e54f900$f506ff0a@ssd>
From: "Adetya Gupta" <adetya.gupta@alcatel.com>
To: "RTP" <rtp@vovida.org>, "RTP" <avt@ietf.org>
Date: Wed, 2 Jan 2002 14:55:21 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_014F_01C1939D.807E6480"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Subject: [AVT] doubt
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

This is a multi-part message in MIME format.

------=_NextPart_000_014F_01C1939D.807E6480
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,
           I want u all to help me .
What is the payload type value in the
RTP Header for the VAD CNG packets.

Thanks

Adetya
=20

------=_NextPart_000_014F_01C1939D.807E6480
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I =
want u all=20
to help me .</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What is the payload type value in =
the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>RTP Header for the VAD CNG =
packets.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Adetya</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;</FONT></DIV></BODY></HTML>

------=_NextPart_000_014F_01C1939D.807E6480--


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



From daemon@optimus.ietf.org  Wed Jan  2 05:07:43 2002
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 FAA01743
	for <avt-archive@odin.ietf.org>; Wed, 2 Jan 2002 05:07:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA01270
	for avt-archive@odin.ietf.org; Wed, 2 Jan 2002 05:07:44 -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 FAA01257;
	Wed, 2 Jan 2002 05:07:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA01226
	for <avt@optimus.ietf.org>; Wed, 2 Jan 2002 05:07:18 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01737
	for <avt@ietf.org>; Wed, 2 Jan 2002 05:07:01 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g02A6A110849
	for <avt@ietf.org>; Wed, 2 Jan 2002 15:36:11 +0530 (IST)
Received: from sureshhb ([192.168.178.59]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GPB2QP01.5N2; Wed, 2 Jan 2002 15:36:25 +0530 
Message-ID: <043501c19375$8cd23e50$3bb2a8c0@wipro.com>
Reply-To: "Suresh H.B" <suresh.hebbalagere@wipro.com>
From: "Suresh H.B" <suresh.hebbalagere@wipro.com>
To: "Adetya Gupta" <adetya.gupta@alcatel.com>, "RTP" <rtp@vovida.org>,
        "RTP" <avt@ietf.org>
References: <015401c1936f$6e54f900$f506ff0a@ssd>
Date: Wed, 2 Jan 2002 15:39:22 +0530
Organization: Wipro Technologies
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-5ba94ce4-ff5e-11d5-a940-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [AVT] Re: [Rtp] doubt
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-5ba94ce4-ff5e-11d5-a940-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0431_01C193A3.A66BF5D0"

------=_NextPart_000_0431_01C193A3.A66BF5D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi,

I guess for CNG a static payload type of 13 is assigned for a sampling rate
of 8,000 Hz; if other sampling rates are needed, they MUST be defined
dynamic payload types.

-Suresh


  ----- Original Message -----
  From: Adetya Gupta
  To: RTP ; RTP
  Sent: Wednesday, January 02, 2002 2:55 PM
  Subject: [Rtp] doubt


  Hi All,
             I want u all to help me .
  What is the payload type value in the
  RTP Header for the VAD CNG packets.

  Thanks

  Adetya


------=_NextPart_000_0431_01C193A3.A66BF5D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I guess for CNG a static&nbsp;payload =
type of 13 is=20
assigned for a sampling rate of 8,000 Hz; if&nbsp;other sampling rates =
are=20
needed, they MUST be defined&nbsp;</FONT><FONT face=3DArial =
size=3D2>dynamic payload=20
types.&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-Suresh</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:adetya.gupta@alcatel.com"=20
  title=3Dadetya.gupta@alcatel.com>Adetya Gupta</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:rtp@vovida.org"=20
  title=3Drtp@vovida.org>RTP</A> ; <A href=3D"mailto:avt@ietf.org"=20
  title=3Davt@ietf.org>RTP</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, January 02, =
2002 2:55=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Rtp] doubt</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
  <DIV><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
I want u=20
  all to help me .</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>What is the payload type value in=20
the</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>RTP Header for the VAD CNG =
packets.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Adetya</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2>&nbsp;</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0431_01C193A3.A66BF5D0--



------=_NextPartTM-000-5ba94ce4-ff5e-11d5-a940-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-5ba94ce4-ff5e-11d5-a940-00b0d0d06be8--


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



From daemon@optimus.ietf.org  Wed Jan  2 07:45:46 2002
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 HAA03095
	for <avt-archive@odin.ietf.org>; Wed, 2 Jan 2002 07:45:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA04975
	for avt-archive@odin.ietf.org; Wed, 2 Jan 2002 07:45:48 -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 HAA04829;
	Wed, 2 Jan 2002 07:44:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA04800
	for <avt@optimus.ietf.org>; Wed, 2 Jan 2002 07:44:15 -0500 (EST)
Received: from purple.nge.isi.edu (reserved.east.isi.edu [65.114.168.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03085
	for <avt@ietf.org>; Wed, 2 Jan 2002 07:44:12 -0500 (EST)
Received: from purple.nge.isi.edu (csp@localhost)
	by purple.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g02Ci1t01509;
	Wed, 2 Jan 2002 07:44:02 -0500
Message-Id: <200201021244.g02Ci1t01509@purple.nge.isi.edu>
To: "Adetya Gupta" <adetya.gupta@alcatel.com>
cc: "RTP" <rtp@vovida.org>, "RTP" <avt@ietf.org>
Subject: Re: [AVT] doubt 
In-Reply-To: Your message of "Wed, 02 Jan 2002 14:55:21 +0530."
             <015401c1936f$6e54f900$f506ff0a@ssd> 
Date: Wed, 02 Jan 2002 07:44:01 -0500
From: Colin Perkins <csp@isi.edu>
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

--> "Adetya Gupta" writes:
>Hi All,
>           I want u all to help me .
>What is the payload type value in the
>RTP Header for the VAD CNG packets.

See http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-cn-04.txt

Colin

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



From daemon@ns.ietf.org  Wed Jan  2 20:38:53 2002
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 UAA13869
	for <avt-archive@odin.ietf.org>; Wed, 2 Jan 2002 20:38:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA29783
	for avt-archive@odin.ietf.org; Wed, 2 Jan 2002 20:38:50 -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 UAA29745;
	Wed, 2 Jan 2002 20:37:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29715
	for <avt@ns.ietf.org>; Wed, 2 Jan 2002 20:37:30 -0500 (EST)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13862
	for <avt@ietf.org>; Wed, 2 Jan 2002 20:37:28 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id g031bT809328
	for <avt@ietf.org>; Wed, 2 Jan 2002 17:37:29 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5834af9f29118164e13a8@mailgate2.apple.com>;
 Wed, 2 Jan 2002 17:37:26 -0800
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv2.apple.com (8.11.3/8.11.3) with ESMTP id g031bPw22752;
	Wed, 2 Jan 2002 17:37:25 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p05101003b859631b209d@[17.202.35.52]>
In-Reply-To: <00ea01c18a8f$dd49eb10$087eedd3@Young>
References: <200112211515.fBLFFjA06458@purple.nge.isi.edu>
 <p05101002b84928232a82@[17.202.35.52]>
 <00ea01c18a8f$dd49eb10$087eedd3@Young>
Date: Wed, 2 Jan 2002 17:26:46 -0800
To: "Lim, Young-Kwon" <young@netntv.co.kr>, Colin Perkins <csp@isi.edu>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
Cc: avt@ietf.org, 4on2andIP-sys@advent.ee.columbia.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 11:25 +0900 12/22/01, Lim, Young-Kwon wrote:
>Dear Dave and all,
>
>
>>
>>  So you *could* add the ES-ID attribute to the GSM stream, add an
>>  object descriptor which describes it as 'user private' and so on, but
>>  I don't think you need to unless you need the manipulations (e.g.
>>  spacial positioning of audio) that MPEG-4 could give you.  Makes
>>  sense?
>
>I think the better way is to assign code points (objectType) to AMR if this
>combination seems to be used widely. Any standardization body can ask MPEG
>to work on it via liaison letter. This would solve the problem more
>organized way.
>
>BTW, you don't need to add ES-ID attribute. We can use URL field in ESD to
>point RTP channel (IP address + port number) in this case.
>
>Sincerely,
>Young.

But both of these are attempts to fit things inside the mpeg-4 
framework.  I still maintain that it's perfectly OK to have streams 
in the SDP session that are simply not present in the mpeg-4 session.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@ns.ietf.org  Wed Jan  2 20:46:46 2002
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 UAA13924
	for <avt-archive@odin.ietf.org>; Wed, 2 Jan 2002 20:46:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA29926
	for avt-archive@odin.ietf.org; Wed, 2 Jan 2002 20:46: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 UAA29910;
	Wed, 2 Jan 2002 20:46:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29881
	for <avt@ns.ietf.org>; Wed, 2 Jan 2002 20:46:22 -0500 (EST)
Received: from bullwinkle.real.com ([207.188.22.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13919
	for <avt@ietf.org>; Wed, 2 Jan 2002 20:46:19 -0500 (EST)
Received: from prognet.com ([::ffff:205.219.198.1])
  by bullwinkle.real.com with esmtp; Wed, 02 Jan 2002 17:43:55 -0800
Received: from ROBLA350 ([172.23.100.116])
	by prognet.com (8.9.2/8.9.0) with ESMTP id RAA22997;
	Wed, 2 Jan 2002 17:46:03 -0800 (PST)
Date: Wed, 2 Jan 2002 17:48:14 -0800 (Pacific Standard Time)
From: Rob Lanphier <robla@real.com>
To: Dave Singer <singer@apple.com>
cc: "Lim, Young-Kwon" <young@netntv.co.kr>, Colin Perkins <csp@isi.edu>,
        "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
In-Reply-To: <p05101003b859631b209d@[17.202.35.52]>
Message-ID: <Pine.WNT.4.43.0201021744260.269-100000@robla350.dev.prognet.com>
X-X-Sender: robla@goobox.prognet.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Wed, 2 Jan 2002, Dave Singer wrote:
> At 11:25 +0900 12/22/01, Lim, Young-Kwon wrote:
> >I think the better way [to have AMR co-exist with MPEG-4 video] is to
> >assign code points (objectType) to AMR if this combination seems to be
> >used widely. Any standardization body can ask MPEG to work on it via
> >liaison letter. This would solve the problem more organized way.
> >
> >BTW, you don't need to add ES-ID attribute. We can use URL field in ESD to
> >point RTP channel (IP address + port number) in this case.
>
> But both of these are attempts to fit things inside the mpeg-4
> framework.  I still maintain that it's perfectly OK to have streams
> in the SDP session that are simply not present in the mpeg-4 session.

I fully agree with Dave that this is how things should be.  Dave, are you
arguing that this is the way things are (given the current state of
proposed packetizations), or the way they should be?

Rob



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



From daemon@ns.ietf.org  Wed Jan  2 21:22:03 2002
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 VAA14155
	for <avt-archive@odin.ietf.org>; Wed, 2 Jan 2002 21:22:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA00890
	for avt-archive@odin.ietf.org; Wed, 2 Jan 2002 21:22:05 -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 VAA00858;
	Wed, 2 Jan 2002 21:21:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA00831
	for <avt@ns.ietf.org>; Wed, 2 Jan 2002 21:21:35 -0500 (EST)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14143
	for <avt@ietf.org>; Wed, 2 Jan 2002 21:21:33 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g032LZ108361
	for <avt@ietf.org>; Wed, 2 Jan 2002 18:21:35 -0800 (PST)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5834d80592118164e13a8@mailgate2.apple.com>;
 Wed, 2 Jan 2002 18:21:34 -0800
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv3.apple.com (8.11.3/8.11.3) with ESMTP id g032LY619615;
	Wed, 2 Jan 2002 18:21:34 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p0510100cb8596fc5187b@[17.202.35.52]>
In-Reply-To: 
 <Pine.WNT.4.43.0201021744260.269-100000@robla350.dev.prognet.com>
References: 
 <Pine.WNT.4.43.0201021744260.269-100000@robla350.dev.prognet.com>
Date: Wed, 2 Jan 2002 18:18:18 -0800
To: Rob Lanphier <robla@real.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
Cc: "Lim, Young-Kwon" <young@netntv.co.kr>, Colin Perkins <csp@isi.edu>,
        "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 17:48 -0800 1/2/02, Rob Lanphier wrote:
>On Wed, 2 Jan 2002, Dave Singer wrote:
>>  At 11:25 +0900 12/22/01, Lim, Young-Kwon wrote:
>>  >I think the better way [to have AMR co-exist with MPEG-4 video] is to
>>  >assign code points (objectType) to AMR if this combination seems to be
>>  >used widely. Any standardization body can ask MPEG to work on it via
>>  >liaison letter. This would solve the problem more organized way.
>>  >
>>  >BTW, you don't need to add ES-ID attribute. We can use URL field in ESD to
>>  >point RTP channel (IP address + port number) in this case.
>>
>>  But both of these are attempts to fit things inside the mpeg-4
>>  framework.  I still maintain that it's perfectly OK to have streams
>>  in the SDP session that are simply not present in the mpeg-4 session.
>
>I fully agree with Dave that this is how things should be.  Dave, are you
>arguing that this is the way things are (given the current state of
>proposed packetizations), or the way they should be?
>
>Rob

I maintain that this is how they are.  Nothing in any spec I am aware 
of says that if an IOD is present, it talks about *all* the streams 
in the SDP session.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@optimus.ietf.org  Thu Jan  3 14:44:31 2002
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 OAA09449
	for <avt-archive@odin.ietf.org>; Thu, 3 Jan 2002 14:44:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA16357
	for avt-archive@odin.ietf.org; Thu, 3 Jan 2002 14:44:34 -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 OAA16316;
	Thu, 3 Jan 2002 14:43:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA16283
	for <avt@optimus.ietf.org>; Thu, 3 Jan 2002 14:43:32 -0500 (EST)
Received: from bullwinkle.real.com ([207.188.22.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09409
	for <avt@ietf.org>; Thu, 3 Jan 2002 14:43:28 -0500 (EST)
Received: from prognet.com ([::ffff:205.219.198.1])
  by bullwinkle.real.com with esmtp; Thu, 03 Jan 2002 11:40:56 -0800
Received: from jeffa-laptop.real.com ([172.23.106.160])
	by prognet.com (8.9.2/8.9.0) with ESMTP id LAA08378;
	Thu, 3 Jan 2002 11:43:05 -0800 (PST)
Message-Id: <4.3.2.7.2.20020103105555.03ca0260@mail.real.com>
X-Sender: jeffa@mail.real.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 03 Jan 2002 11:41:36 -0800
To: Dave Singer <singer@apple.com>, Rob Lanphier <robla@real.com>
From: Jeff Ayars <jeffa@real.com>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
Cc: "Lim, Young-Kwon" <young@netntv.co.kr>, Colin Perkins <csp@isi.edu>,
        "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
In-Reply-To: <p0510100cb8596fc5187b@[17.202.35.52]>
References: < <Pine.WNT.4.43.0201021744260.269-100000@robla350.dev.prognet.com>
 <Pine.WNT.4.43.0201021744260.269-100000@robla350.dev.prognet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 06:18 PM 1/2/2002 -0800, Dave Singer wrote:
>At 17:48 -0800 1/2/02, Rob Lanphier wrote:
>>On Wed, 2 Jan 2002, Dave Singer wrote:
>>>  At 11:25 +0900 12/22/01, Lim, Young-Kwon wrote:
>>>  >I think the better way [to have AMR co-exist with MPEG-4 video] is to
>>>  >assign code points (objectType) to AMR if this combination seems to be
>>>  >used widely. Any standardization body can ask MPEG to work on it via
>>>  >liaison letter. This would solve the problem more organized way.
>>>  >
>>>  >BTW, you don't need to add ES-ID attribute. We can use URL field in 
>>> ESD to
>>>  >point RTP channel (IP address + port number) in this case.
>>>
>>>  But both of these are attempts to fit things inside the mpeg-4
>>>  framework.  I still maintain that it's perfectly OK to have streams
>>>  in the SDP session that are simply not present in the mpeg-4 session.
>>
>>I fully agree with Dave that this is how things should be.  Dave, are you
>>arguing that this is the way things are (given the current state of
>>proposed packetizations), or the way they should be?
>>
>>Rob
>
>I maintain that this is how they are.  Nothing in any spec I am aware of 
>says that if an IOD is present, it talks about *all* the streams in the 
>SDP session.
>--

I'm a little lost on this thread but I do have a comment on the draft.

3.1 states:

                  a=mpeg4-iod [<location>]

                   location:  In an RTSP session, this is an optional 
attribute. If not
                   supplied, the IOD is retrieved over the RTSP session by 
using
                   DESCRIBE with an accept of type application/mpeg4-iod.

I read this to say a normal RTSP conversation would look like this:

C->S:   DESCRIBE <url> RTSP/1.0
         Accept: application/sdp

S->C:  RTSP 200 OK
         Content-Type: application/sdp
         Content-Length: ...
         <sdp contents>

< client parses SDP, finds a=mpeg4-iod or a=mpeg4-iod-xmt >

C->S:   DESCRIBE <same url> RTSP/1.0
         Accept: application/mpeg4-iod  <or application/mpeg4-iod-xmt>

S->C:   RTSP 200 OK
         Content-Type: application/mpeg4-iod <or application/mpeg4-iod-xmt>
         Content-Length: ...
         <iod>

< client parses IOD, does some mapping of SDP media entries to presentation 
described by IOD, decides what to setup when, etc..>

Do I have that right?

If so, why the double describe?  Why not just a single describe with all 
description formats in the Accept header?

C->S:   DESCRIBE <same url> RTSP/1.0
         Accept: application/mpeg4-iod, application/mpeg4-iod-xmt, 
application/sdp

Is it the case that SDP is insufficient to describe everything mpeg4-iod 
can?  Is mpeg4-iod insufficient to describe everything SDP can?

If both formats describe the presentation to different application layers 
(is that the right distinction?), to Rob Lanphier's initial question on the 
draft, why a specific extension for mpeg4?  Why not a generic mechanism for 
additional presentation descriptions using a single new SDP attribute 
that's not mpeg4 specific?

JEff


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



From daemon@optimus.ietf.org  Thu Jan  3 14:49:13 2002
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 OAA09607
	for <avt-archive@odin.ietf.org>; Thu, 3 Jan 2002 14:49:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA16494
	for avt-archive@odin.ietf.org; Thu, 3 Jan 2002 14:49:16 -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 OAA16465;
	Thu, 3 Jan 2002 14:48:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA16434
	for <avt@optimus.ietf.org>; Thu, 3 Jan 2002 14:48:46 -0500 (EST)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09596
	for <avt@ietf.org>; Thu, 3 Jan 2002 14:48:42 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g03Jmi103035
	for <avt@ietf.org>; Thu, 3 Jan 2002 11:48:44 -0800 (PST)
Received: from scv1.apple.com (scv1.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5838969b3c118164e13a8@mailgate2.apple.com>;
 Thu, 3 Jan 2002 11:48:36 -0800
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv1.apple.com (8.11.3/8.11.3) with ESMTP id g03Jmae29764;
	Thu, 3 Jan 2002 11:48:36 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p05101006b85a652f1bc1@[17.202.35.52]>
In-Reply-To: <4.3.2.7.2.20020103105555.03ca0260@mail.real.com>
References:  <"
 <Pine.WNT.4.43.0201021744260.269-100000"@robla350.dev.prognet.com>
 <Pine.WNT.4.43.0201021744260.269-100000@robla350.dev.prognet.com>
 <4.3.2.7.2.20020103105555.03ca0260@mail.real.com>
Date: Thu, 3 Jan 2002 11:46:00 -0800
To: Jeff Ayars <jeffa@real.com>, Rob Lanphier <robla@real.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
Cc: "Lim, Young-Kwon" <young@netntv.co.kr>, Colin Perkins <csp@isi.edu>,
        "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 11:41 -0800 1/3/02, Jeff Ayars wrote:
>At 06:18 PM 1/2/2002 -0800, Dave Singer wrote:
>>At 17:48 -0800 1/2/02, Rob Lanphier wrote:
>>>On Wed, 2 Jan 2002, Dave Singer wrote:
>>>>  At 11:25 +0900 12/22/01, Lim, Young-Kwon wrote:
>>>>  >I think the better way [to have AMR co-exist with MPEG-4 video] is to
>>>>  >assign code points (objectType) to AMR if this combination seems to be
>>>>  >used widely. Any standardization body can ask MPEG to work on it via
>>>>  >liaison letter. This would solve the problem more organized way.
>>>>  >
>>>>  >BTW, you don't need to add ES-ID attribute. We can use URL 
>>>>field in ESD to
>>>>  >point RTP channel (IP address + port number) in this case.
>>>>
>>>>  But both of these are attempts to fit things inside the mpeg-4
>>>>  framework.  I still maintain that it's perfectly OK to have streams
>>>>  in the SDP session that are simply not present in the mpeg-4 session.
>>>
>>>I fully agree with Dave that this is how things should be.  Dave, are you
>>>arguing that this is the way things are (given the current state of
>>>proposed packetizations), or the way they should be?
>>>
>>>Rob
>>
>>I maintain that this is how they are.  Nothing in any spec I am 
>>aware of says that if an IOD is present, it talks about *all* the 
>>streams in the SDP session.
>>--
>
>I'm a little lost on this thread but I do have a comment on the draft.
>
>3.1 states:
>
>                  a=mpeg4-iod [<location>]
>
>                   location:  In an RTSP session, this is an optional 
>attribute. If not
>                   supplied, the IOD is retrieved over the RTSP 
>session by using
>                   DESCRIBE with an accept of type application/mpeg4-iod.
>
>I read this to say a normal RTSP conversation would look like this:
>
>C->S:   DESCRIBE <url> RTSP/1.0
>         Accept: application/sdp
>
>S->C:  RTSP 200 OK
>         Content-Type: application/sdp
>         Content-Length: ...
>         <sdp contents>
>
>< client parses SDP, finds a=mpeg4-iod or a=mpeg4-iod-xmt >
>
>C->S:   DESCRIBE <same url> RTSP/1.0
>         Accept: application/mpeg4-iod  <or application/mpeg4-iod-xmt>
>
>S->C:   RTSP 200 OK
>         Content-Type: application/mpeg4-iod <or application/mpeg4-iod-xmt>
>         Content-Length: ...
>         <iod>
>
>< client parses IOD, does some mapping of SDP media entries to 
>presentation described by IOD, decides what to setup when, etc..>
>
>Do I have that right?
>
>If so, why the double describe?  Why not just a single describe with 
>all description formats in the Accept header?
>
>C->S:   DESCRIBE <same url> RTSP/1.0
>         Accept: application/mpeg4-iod, application/mpeg4-iod-xmt, 
>application/sdp
>
>Is it the case that SDP is insufficient to describe everything 
>mpeg4-iod can?  Is mpeg4-iod insufficient to describe everything SDP 
>can?

Yes, and Yes.  The envisaged scenario was a normal RTSP 
server/client, where you initially get the SDP.  That alerts you to 
the IOD, and if you are a terminal that needs an IOD, you can now get 
it.

>
>If both formats describe the presentation to different application 
>layers (is that the right distinction?), to Rob Lanphier's initial 
>question on the draft, why a specific extension for mpeg4?  Why not 
>a generic mechanism for additional presentation descriptions using a 
>single new SDP attribute that's not mpeg4 specific?
>
>JEff

I'd be fine with that.  I just don't know of one.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@optimus.ietf.org  Thu Jan  3 17:48:46 2002
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 RAA12934
	for <avt-archive@odin.ietf.org>; Thu, 3 Jan 2002 17:48:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA23444
	for avt-archive@odin.ietf.org; Thu, 3 Jan 2002 17:48: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 RAA23369;
	Thu, 3 Jan 2002 17:42:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23340
	for <avt@optimus.ietf.org>; Thu, 3 Jan 2002 17:42:38 -0500 (EST)
Received: from bullwinkle.real.com ([207.188.22.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12812
	for <avt@ietf.org>; Thu, 3 Jan 2002 17:42:34 -0500 (EST)
Received: from prognet.com ([::ffff:205.219.198.1])
  by bullwinkle.real.com with esmtp; Thu, 03 Jan 2002 14:40:03 -0800
Received: from ROBLA350 ([172.23.100.116])
	by prognet.com (8.9.2/8.9.0) with ESMTP id OAA19665;
	Thu, 3 Jan 2002 14:42:20 -0800 (PST)
Date: Thu, 3 Jan 2002 14:44:30 -0800 (Pacific Standard Time)
From: Rob Lanphier <robla@real.com>
To: Dave Singer <singer@apple.com>
cc: Jeff Ayars <jeffa@real.com>, "Lim, Young-Kwon" <young@netntv.co.kr>,
        Colin Perkins <csp@isi.edu>, "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
In-Reply-To: <p05101006b85a652f1bc1@[17.202.35.52]>
Message-ID: <Pine.WNT.4.43.0201031439030.235-100000@robla350.dev.prognet.com>
X-X-Sender: robla@goobox.prognet.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Thu, 3 Jan 2002, Dave Singer wrote:
> At 11:41 -0800 1/3/02, Jeff Ayars wrote:
> >If so, why the double describe?  Why not just a single describe with
> >all description formats in the Accept header?
> >
> >C->S:   DESCRIBE <same url> RTSP/1.0
> >         Accept: application/mpeg4-iod, application/mpeg4-iod-xmt,
> >application/sdp
> >
> >Is it the case that SDP is insufficient to describe everything
> >mpeg4-iod can?  Is mpeg4-iod insufficient to describe everything SDP
> >can?
>
> Yes, and Yes.  The envisaged scenario was a normal RTSP
> server/client, where you initially get the SDP.  That alerts you to
> the IOD, and if you are a terminal that needs an IOD, you can now get
> it.

But there's nothing wrong with a normal RTSP server immediately returning
application/mpeg4-iod if the client has indicated mpeg4-iod is an
acceptable DESCRIBE response.  Why the extra SDP step?

> >If both formats describe the presentation to different application
> >layers (is that the right distinction?), to Rob Lanphier's initial
> >question on the draft, why a specific extension for mpeg4?  Why not
> >a generic mechanism for additional presentation descriptions using a
> >single new SDP attribute that's not mpeg4 specific?
>
> I'd be fine with that.  I just don't know of one.

My initial suggestion was that we create one:

a=root:<uri>

...where the URI can be a data URL, or an external reference.

Rob



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



From daemon@optimus.ietf.org  Thu Jan  3 17:58:20 2002
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 RAA13106
	for <avt-archive@odin.ietf.org>; Thu, 3 Jan 2002 17:58:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA23676
	for avt-archive@odin.ietf.org; Thu, 3 Jan 2002 17:58:23 -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 RAA23661;
	Thu, 3 Jan 2002 17:58:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23632
	for <avt@optimus.ietf.org>; Thu, 3 Jan 2002 17:57:59 -0500 (EST)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13093
	for <avt@ietf.org>; Thu, 3 Jan 2002 17:57:55 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g03Mvw113999
	for <avt@ietf.org>; Thu, 3 Jan 2002 14:57:58 -0800 (PST)
Received: from scv1.apple.com (scv1.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T583943f59d118164e13a8@mailgate2.apple.com>;
 Thu, 3 Jan 2002 14:57:57 -0800
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv1.apple.com (8.11.3/8.11.3) with ESMTP id g03Mvue12160;
	Thu, 3 Jan 2002 14:57:56 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p05101014b85a915975a9@[17.202.35.52]>
In-Reply-To: 
 <Pine.WNT.4.43.0201031439030.235-100000@robla350.dev.prognet.com>
References: 
 <Pine.WNT.4.43.0201031439030.235-100000@robla350.dev.prognet.com>
Date: Thu, 3 Jan 2002 14:56:34 -0800
To: Rob Lanphier <robla@real.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
Cc: Jeff Ayars <jeffa@real.com>, "Lim, Young-Kwon" <young@netntv.co.kr>,
        Colin Perkins <csp@isi.edu>, "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 14:44 -0800 1/3/02, Rob Lanphier wrote:
>On Thu, 3 Jan 2002, Dave Singer wrote:
>>  At 11:41 -0800 1/3/02, Jeff Ayars wrote:
>>  >If so, why the double describe?  Why not just a single describe with
>>  >all description formats in the Accept header?
>>  >
>>  >C->S:   DESCRIBE <same url> RTSP/1.0
>>  >         Accept: application/mpeg4-iod, application/mpeg4-iod-xmt,
>>  >application/sdp
>>  >
>>  >Is it the case that SDP is insufficient to describe everything
>>  >mpeg4-iod can?  Is mpeg4-iod insufficient to describe everything SDP
>>  >can?
>>
>>  Yes, and Yes.  The envisaged scenario was a normal RTSP
>>  server/client, where you initially get the SDP.  That alerts you to
>>  the IOD, and if you are a terminal that needs an IOD, you can now get
>>  it.
>
>But there's nothing wrong with a normal RTSP server immediately returning
>application/mpeg4-iod if the client has indicated mpeg4-iod is an
>acceptable DESCRIBE response.  Why the extra SDP step?

The complete session is described by SDP.  In it some of the streams 
belong to an MPEG-4 session which is described (additionally) by an 
IOD.  The IOD tells us, for example, which streams to start decoding 
with (e.g. which is the root scene if there are several scene 
streams).  SDP tells us port mappings and so on.  They are 
complimentary.  We decided against returning them both at once as 
then you'd have to have a multipart message, which seemed 
un-necessarily complex.  But maybe I am wrong.

>
>>  >If both formats describe the presentation to different application
>>  >layers (is that the right distinction?), to Rob Lanphier's initial
>>  >question on the draft, why a specific extension for mpeg4?  Why not
>>  >a generic mechanism for additional presentation descriptions using a
>>  >single new SDP attribute that's not mpeg4 specific?
>>
>>  I'd be fine with that.  I just don't know of one.
>
>My initial suggestion was that we create one:
>
>a=root:<uri>
>
>...where the URI can be a data URL, or an external reference.
>
>Rob

What is the content of the URI?  How do I know whether I need this or 
what I will get if I access it?

The point of the mpeg-4-iod tag was explicitly the warning that some 
of the streams are structured as part of an MPEG-4 session, and to 
decode them right you probably need to know the IOD.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@optimus.ietf.org  Thu Jan  3 22:46:24 2002
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 WAA18498
	for <avt-archive@odin.ietf.org>; Thu, 3 Jan 2002 22:46:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA29395
	for avt-archive@odin.ietf.org; Thu, 3 Jan 2002 22:46:27 -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 WAA29351;
	Thu, 3 Jan 2002 22:43:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA29322
	for <avt@optimus.ietf.org>; Thu, 3 Jan 2002 22:43:12 -0500 (EST)
Received: from bullwinkle.real.com ([207.188.22.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18443
	for <avt@ietf.org>; Thu, 3 Jan 2002 22:43:07 -0500 (EST)
Received: from prognet.com ([::ffff:205.219.198.1])
  by bullwinkle.real.com with esmtp; Thu, 03 Jan 2002 19:40:33 -0800
Received: from ROBLA350 ([172.23.100.116])
	by prognet.com (8.9.2/8.9.0) with ESMTP id TAA23982;
	Thu, 3 Jan 2002 19:42:51 -0800 (PST)
Date: Thu, 3 Jan 2002 19:45:00 -0800 (Pacific Standard Time)
From: Rob Lanphier <robla@real.com>
To: Dave Singer <singer@apple.com>
cc: Jeff Ayars <jeffa@real.com>, "Lim, Young-Kwon" <young@netntv.co.kr>,
        Colin Perkins <csp@isi.edu>, "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
In-Reply-To: <p05101014b85a915975a9@[17.202.35.52]>
Message-ID: <Pine.WNT.4.43.0201031526440.235-100000@robla350.dev.prognet.com>
X-X-Sender: robla@goobox.prognet.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Thu, 3 Jan 2002, Dave Singer wrote:

> At 14:44 -0800 1/3/02, Rob Lanphier wrote:
> >On Thu, 3 Jan 2002, Dave Singer wrote:
> >>  At 11:41 -0800 1/3/02, Jeff Ayars wrote:
> >>  >If so, why the double describe?  Why not just a single describe with
> >>  >all description formats in the Accept header?
> >>  >
> >>  >C->S:   DESCRIBE <same url> RTSP/1.0
> >>  >         Accept: application/mpeg4-iod, application/mpeg4-iod-xmt,
> >>  >application/sdp
> >>  >
> >>  >Is it the case that SDP is insufficient to describe everything
> >>  >mpeg4-iod can?  Is mpeg4-iod insufficient to describe everything SDP
> >>  >can?
> >>
> >>  Yes, and Yes.  The envisaged scenario was a normal RTSP
> >>  server/client, where you initially get the SDP.  That alerts you to
> >>  the IOD, and if you are a terminal that needs an IOD, you can now get
> >>  it.
> >
> >But there's nothing wrong with a normal RTSP server immediately returning
> >application/mpeg4-iod if the client has indicated mpeg4-iod is an
> >acceptable DESCRIBE response.  Why the extra SDP step?
>
> The complete session is described by SDP.  In it some of the streams
> belong to an MPEG-4 session which is described (additionally) by an
> IOD.  The IOD tells us, for example, which streams to start decoding
> with (e.g. which is the root scene if there are several scene
> streams).  SDP tells us port mappings and so on.  They are
> complimentary.  We decided against returning them both at once as
> then you'd have to have a multipart message, which seemed
> un-necessarily complex.  But maybe I am wrong.

I would agree that multi-part MIME would be needlessly complex.  Perhaps
this is a matter of taste, but I don't like the idea that DESCRIBE can be
issued twice *on the same URL* and returns two totally different classes
of information (not just different formats).  It seems that the iod should
always have a different URL than the content (it's fine to make it a
relative URL, the same way stream ids are), thus the location field in the
a=mpeg4-iod line should not be optional.

> >>  >If both formats describe the presentation to different application
> >>  >layers (is that the right distinction?), to Rob Lanphier's initial
> >>  >question on the draft, why a specific extension for mpeg4?  Why not
> >>  >a generic mechanism for additional presentation descriptions using a
> >>  >single new SDP attribute that's not mpeg4 specific?
> >>
> >>  I'd be fine with that.  I just don't know of one.
> >
> >My initial suggestion was that we create one:
> >
> >a=root:<uri>
> >
> >...where the URI can be a data URL, or an external reference.
> >
> >Rob
>
> What is the content of the URI?  [How do I know] what I will get if I
> access it?

In the case of a data URL, the media type is embedded in it.  In the case
of HTTP, it would be in the GET response, and in the case of RTSP, it
could be dictated by the Accept: header.

I do see your point, though.  It would be nice to have the type right
there all of the time.  New proposal:

a=root <uri> [<type>]

The type would be a MIME type.  It would be worthwhile to discuss whether
this would be allowed:

a=root http://foo.com/bar application/mpeg4-iod
a=root http://foo.com/bar application/mpeg4-iod-xmt
a=root http://foo.com/bar application/smil
a=root http://foo.com/bar application/svg
a=root http://foo.com/bar text/html

...i.e. give a whole bunch of options, and leave it to the client to sort
out.

> How do I know whether I need this [...]?

That is a fine question, *regardless* of what the syntax is (current
proposal or any new proposal), unless you are saying that the
"a=mpeg4-iod" header *must* be present whenever streams marked "audio/mp4"
and "video/mp4" are served.

Under my proposal, I guess one could add a "a=needroot" flag on the
individual streams that need this (under the respective m= lines).
Alternately, we could extend this a little further, and allow for multiple
roots (i.e. multiple IODs):

...
a=root <id> <uri> [<type>]
a=root <id> <uri> [<type>]
m=audio....
a=needroot <id>
m=video...
a=needroot <id>

The id would be a concise identifier valid within the document, and would
allow the audio stream and the video stream to be bound to separate IODs
if that was necessary for whatever reason.

> The point of the mpeg-4-iod tag was explicitly the warning that some
> of the streams are structured as part of an MPEG-4 session, and to
> decode them right you probably need to know the IOD.

Which streams?  All of the MPEG-4 streams?  Some of them?  What if some
streams are

Rob



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



From daemon@optimus.ietf.org  Fri Jan  4 12:46:11 2002
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 MAA09466
	for <avt-archive@odin.ietf.org>; Fri, 4 Jan 2002 12:46:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00968
	for avt-archive@odin.ietf.org; Fri, 4 Jan 2002 12:46:13 -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 MAA00914;
	Fri, 4 Jan 2002 12:45:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00883
	for <avt@optimus.ietf.org>; Fri, 4 Jan 2002 12:45:19 -0500 (EST)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09449
	for <avt@ietf.org>; Fri, 4 Jan 2002 12:45:16 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g04HjH125057
	for <avt@ietf.org>; Fri, 4 Jan 2002 09:45:17 -0800 (PST)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T583d4befa1118164e13a8@mailgate2.apple.com>;
 Fri, 4 Jan 2002 09:45:08 -0800
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv3.apple.com (8.11.3/8.11.3) with ESMTP id g04Hj8604582;
	Fri, 4 Jan 2002 09:45:08 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p0510100bb85b98c33255@[17.202.35.52]>
In-Reply-To: 
 <Pine.WNT.4.43.0201031526440.235-100000@robla350.dev.prognet.com>
References: 
 <Pine.WNT.4.43.0201031526440.235-100000@robla350.dev.prognet.com>
Date: Fri, 4 Jan 2002 09:42:54 -0800
To: Rob Lanphier <robla@real.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Comments on draft-singer-mpeg4-ip-03.txt
Cc: Jeff Ayars <jeffa@real.com>, "Lim, Young-Kwon" <young@netntv.co.kr>,
        Colin Perkins <csp@isi.edu>, "avt@ietf.org" <avt@ietf.org>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 19:45 -0800 1/3/02, Rob Lanphier wrote:
>On Thu, 3 Jan 2002, Dave Singer wrote:
>
>>  At 14:44 -0800 1/3/02, Rob Lanphier wrote:
>>  >On Thu, 3 Jan 2002, Dave Singer wrote:
>>  >>  At 11:41 -0800 1/3/02, Jeff Ayars wrote:
>>  >>  >If so, why the double describe?  Why not just a single describe with
>>  >>  >all description formats in the Accept header?
>>  >>  >
>>  >>  >C->S:   DESCRIBE <same url> RTSP/1.0
>>  >>  >         Accept: application/mpeg4-iod, application/mpeg4-iod-xmt,
>>  >>  >application/sdp
>>  >>  >
>>  >>  >Is it the case that SDP is insufficient to describe everything
>>  >>  >mpeg4-iod can?  Is mpeg4-iod insufficient to describe everything SDP
>>  >>  >can?
>>  >>
>>  >>  Yes, and Yes.  The envisaged scenario was a normal RTSP
>>  >>  server/client, where you initially get the SDP.  That alerts you to
>>  >>  the IOD, and if you are a terminal that needs an IOD, you can now get
>>  >>  it.
>>  >
>>  >But there's nothing wrong with a normal RTSP server immediately returning
>>  >application/mpeg4-iod if the client has indicated mpeg4-iod is an
>>  >acceptable DESCRIBE response.  Why the extra SDP step?
>>
>>  The complete session is described by SDP.  In it some of the streams
>>  belong to an MPEG-4 session which is described (additionally) by an
>>  IOD.  The IOD tells us, for example, which streams to start decoding
>>  with (e.g. which is the root scene if there are several scene
>>  streams).  SDP tells us port mappings and so on.  They are
>>  complimentary.  We decided against returning them both at once as
>>  then you'd have to have a multipart message, which seemed
>>  un-necessarily complex.  But maybe I am wrong.
>
>I would agree that multi-part MIME would be needlessly complex.  Perhaps
>this is a matter of taste, but I don't like the idea that DESCRIBE can be
>issued twice *on the same URL* and returns two totally different classes
>of information (not just different formats).  It seems that the iod should
>always have a different URL than the content (it's fine to make it a
>relative URL, the same way stream ids are), thus the location field in the
>a=mpeg4-iod line should not be optional.

I think I might like this idea, but it's worth noting that doing two 
describes with different Accepts seems reasonably clear.  However, I 
understand that this might be seen as two ways of delivering the same 
information.  The problem with requiring the URL, is that it 
ambiguates the URL.  Should I (a) issue another Describe or (b) fetch 
the data at the given URL?  I guess the form of the URL would have to 
tell you.  If it's relative, you can use the same connection.  If 
it's RTSP, open that URL and do a Describe/accept-IOD.  If it's HTTP 
or FTP, do a get of that URL...

would this fly better?

>
>>  >>  >If both formats describe the presentation to different application
>>  >>  >layers (is that the right distinction?), to Rob Lanphier's initial
>>  >>  >question on the draft, why a specific extension for mpeg4?  Why not
>>  >>  >a generic mechanism for additional presentation descriptions using a
>>  >>  >single new SDP attribute that's not mpeg4 specific?
>>  >>
>>  >>  I'd be fine with that.  I just don't know of one.
>>  >
>>  >My initial suggestion was that we create one:
>>  >
>>  >a=root:<uri>
>>  >
>>  >...where the URI can be a data URL, or an external reference.
>>  >
>>  >Rob
>>
>>  What is the content of the URI?  [How do I know] what I will get if I
>>  access it?
>
>In the case of a data URL, the media type is embedded in it.  In the case
>of HTTP, it would be in the GET response, and in the case of RTSP, it
>could be dictated by the Accept: header.
>
>I do see your point, though.  It would be nice to have the type right
>there all of the time.  New proposal:
>
>a=root <uri> [<type>]
>
>The type would be a MIME type.  It would be worthwhile to discuss whether
>this would be allowed:
>
>a=root http://foo.com/bar application/mpeg4-iod
>a=root http://foo.com/bar application/mpeg4-iod-xmt
>a=root http://foo.com/bar application/smil
>a=root http://foo.com/bar application/svg
>a=root http://foo.com/bar text/html
>
>...i.e. give a whole bunch of options, and leave it to the client to sort
>out.
>
>>  How do I know whether I need this [...]?
>
>That is a fine question, *regardless* of what the syntax is (current
>proposal or any new proposal), unless you are saying that the
>"a=mpeg4-iod" header *must* be present whenever streams marked "audio/mp4"
>and "video/mp4" are served.

No, it is present if MPEG-4 *systems* is used for the presentation, 
and you need to know (minimally) the initial OD and BIFS streams, and 
maybe the profile/levels (though these are also tagged on the 
streams), and possibly extension descriptors attached to the IOD.

>Under my proposal, I guess one could add a "a=needroot" flag on the
>individual streams that need this (under the respective m= lines).
>Alternately, we could extend this a little further, and allow for multiple
>roots (i.e. multiple IODs):
>
>...
>a=root <id> <uri> [<type>]
>a=root <id> <uri> [<type>]
>m=audio....
>a=needroot <id>
>m=video...
>a=needroot <id>
>
>The id would be a concise identifier valid within the document, and would
>allow the audio stream and the video stream to be bound to separate IODs
>if that was necessary for whatever reason.
>
>>  The point of the mpeg-4-iod tag was explicitly the warning that some
>>  of the streams are structured as part of an MPEG-4 session, and to
>>  decode them right you probably need to know the IOD.
>
>Which streams?  All of the MPEG-4 streams?  Some of them?  What if some
>streams are
>

cut off in the middle?

you don't need to know;  all you really need to know is that an 
MPEG-4 systems session comprises some of the streams in the session.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@ns.ietf.org  Fri Jan  4 16:12:24 2002
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 QAA13959
	for <avt-archive@odin.ietf.org>; Fri, 4 Jan 2002 16:12:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA07044
	for avt-archive@odin.ietf.org; Fri, 4 Jan 2002 16:12:26 -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 QAA07013;
	Fri, 4 Jan 2002 16:10:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06980
	for <avt@ns.ietf.org>; Fri, 4 Jan 2002 16:10:57 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi.cc.vt.edu [198.82.161.183])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13938
	for <avt@ietf.org>; Fri, 4 Jan 2002 16:10:55 -0500 (EST)
Received: from kwieringo (chsparks.ais.vt.edu [128.173.240.89])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id AKB06341;
	Fri, 4 Jan 2002 16:10:52 -0500 (EST)
Reply-To: <kwieringo@vt.edu>
From: "Ken Wieringo" <kwieringo@vt.edu>
To: <avt@ietf.org>
Date: Fri, 4 Jan 2002 16:10:52 -0500
Message-ID: <JKEPLIOJJCKHPAIKIDDDCEBPCAAA.kwieringo@vt.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [AVT] h248
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
Content-Transfer-Encoding: 7bit

Can someone tell me the definition of H248 MEGACO?
Thanks
Ken
-===========-

Ken Wieringo
IS&C 1900 Kraft Drive
Blacksburg, VA 24060 
540-231-5025

Amateur Radio n4lyo
Army MARS aat3pk/va

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



From daemon@ns.ietf.org  Fri Jan  4 16:45:05 2002
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 QAA14531
	for <avt-archive@odin.ietf.org>; Fri, 4 Jan 2002 16:45:05 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA07749
	for avt-archive@odin.ietf.org; Fri, 4 Jan 2002 16:45:07 -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 QAA07714;
	Fri, 4 Jan 2002 16:43:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA07687
	for <avt@ns.ietf.org>; Fri, 4 Jan 2002 16:43:32 -0500 (EST)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14519
	for <avt@ietf.org>; Fri, 4 Jan 2002 16:43:29 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sj1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id NAA25451; Fri, 4 Jan 2002 13:42:59 -0800 (PST)
Message-Id: <4.1.20020104154224.094554a0@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Fri, 04 Jan 2002 15:42:41 -0600
To: <kwieringo@vt.edu>, <avt@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [AVT] h248
In-Reply-To: <JKEPLIOJJCKHPAIKIDDDCEBPCAAA.kwieringo@vt.edu>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1563325753==_.ALT"
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

--=====================_1563325753==_.ALT
Content-Type: text/plain; charset="us-ascii"


rfc3015

At 04:10 PM 1/4/2002 -0500, Ken Wieringo wrote:
>Can someone tell me the definition of H248 MEGACO?
>Thanks
>Ken
>-===========-
>
>Ken Wieringo
>IS&C 1900 Kraft Drive
>Blacksburg, VA 24060 
>540-231-5025
>
>Amateur Radio n4lyo
>Army MARS aat3pk/va
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>http://www1.ietf.org/mailman/listinfo/avt

*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"

James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com
--=====================_1563325753==_.ALT
Content-Type: text/html; charset="us-ascii"

<html><div>rfc3015</div>
<br>
<div>At 04:10 PM 1/4/2002 -0500, Ken Wieringo wrote:</div>
<div>&gt;Can someone tell me the definition of H248 MEGACO?</div>
<div>&gt;Thanks</div>
<div>&gt;Ken</div>
<div>&gt;-===========-</div>
<div>&gt;</div>
<div>&gt;Ken Wieringo</div>
<div>&gt;IS&amp;C 1900 Kraft Drive</div>
<div>&gt;Blacksburg, VA 24060 </div>
<div>&gt;540-231-5025</div>
<div>&gt;</div>
<div>&gt;Amateur Radio n4lyo</div>
<div>&gt;Army MARS aat3pk/va</div>
<div>&gt;</div>
<div>&gt;_______________________________________________</div>
<div>&gt;Audio/Video Transport Working Group</div>
<div>&gt;avt@ietf.org</div>
<div>&gt;<a href="http://www1.ietf.org/mailman/listinfo/avt" EUDORA=AUTOURL>http://www1.ietf.org/mailman/listinfo/avt</a></div>
<br>

<div align="center">
*************************************<br>
&quot;People generally demand more respect for their own rights than they
are willing to allow for others&quot;<br>
<br>
</div>
James M. Polk<br>
Consulting Engineer<br>
Office of the CTO<br>
<br>
Cisco Systems<br>
2200 East President George Bush Turnpike <br>
Richardson, TX&nbsp; 75082 USA<br>
w) 972.813.5208<br>
f)&nbsp; 972.813.5280<br>
<a href="http://www.cisco.com/" eudora="autourl">www.cisco.com</a></html>

--=====================_1563325753==_.ALT--


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



From daemon@ns.ietf.org  Sat Jan  5 00:21:23 2002
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 AAA21334
	for <avt-archive@odin.ietf.org>; Sat, 5 Jan 2002 00:21:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA19737
	for avt-archive@odin.ietf.org; Sat, 5 Jan 2002 00:21:23 -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 AAA19707;
	Sat, 5 Jan 2002 00:20:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA19676
	for <avt@ns.ietf.org>; Sat, 5 Jan 2002 00:20:03 -0500 (EST)
Received: from inkjetmania.net ([65.170.199.152])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA21327
	for <avt@ietf.org>; Sat, 5 Jan 2002 00:20:01 -0500 (EST)
Date: Sat, 5 Jan 2002 00:20:01 -0500 (EST)
From: 2002-savings@inkjetmania.net
Message-Id: <200201050520.AAA21327@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=200201041647="
To: avt@ietf.org
X-Mailer: C792123.5F8B8106.8725410d0acb89ef3c6f05597f47f174
Organization: US Inkjets
Subject: [AVT] Want to Save in 2002? This is HOW!
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

--=200201041647=
Content-Type: text/html;charset=US-ASCII

<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Are You Tired of Wasting Money on Ink Cartridges</title>
</head>

<body>

<div align="center">
  <center>

<table border="1" borderColor="#12438f" cellPadding="10" cellSpacing="0" width="504" height="413">
  <tbody>
    <tr>
      <td vAlign="top" width="516" height="391">
        <table border="0" cellPadding="0" cellSpacing="0" width="472">
          <tbody>
            <tr>
              <td align="left" width="112"><img alt border="0" src="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/IMAGES/t017-2s.jpg" width="90" height="82"></td>
              <td align="center" width="262" bordercolor="#12438F" style="border-style: solid; border-width: 0"><b><font face="Courier" size="5" color="#CC0000">Are
                You Tired of Wasting Money on Ink &amp; Toner Cartridges?</font></b></td>
              <td align="right" width="92"><img alt border="0" src="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/IMAGES/17g0050s.jpg" width="76" height="76"></td>
            </tr>
          </tbody>
        </table>
        <p class="header" align="center"><b><font size="3"><font color="#12438F">Then</font><font size="4" color="#0000FF">
        </font><font size="4" color="#CC0000">SAVE NOW</font><font size="4" color="#0000FF">
        </font><font size="4" color="#12438F">with our New Year's Specials</font><font size="4" color="#0000CC"> </font><font size="4" color="#CC0000">&amp;</font><font size="4" color="#0000CC">
        </font><font size="4" color="#12438F">
        FREE Shipping!</font></font></b><img alt border="0" src="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/IMAGES/dotted_line.gif" vspace="5" width="464" height="13"><br>        <a href="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/default.asp"><img alt="Click Here" border="0" src="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/IMAGES/click_here_button.gif" width="87" height="24"></a>
        <p><b>We offer you all of this:</b>
        <ul type="disc">
          <li><font color="#12438F"><b>Money-back Satisfaction Guarantee!</b></font>
          <li><font color="#12438F"><b>NO shipping costs, save yourself a trip
            to the store.</b></font>
          <li><font color="#12438F"><b>Save up to 75% off of retail store
            prices!</b></font>
          <li><font color="#12438F"><b>Instant Service - All Orders ship within
            24 hrs via Priority Mail.</b></font>
          <li><font color="#12438F"><b>One year warranty on all cartridges for
            Epson Stylus printers.</b></font>
          <li><font color="#12438F"><b>A 90-day warranty on ALL cartridges.</b></font>
          <li><font color="#12438F"><b>Easy &amp; Secure online ordering!</b></font></li>
        </ul>
        <p align="center"><a href="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/default.asp"><img alt border="0" src="http://www.usainkjets.net!5key=12345index=b1g1@1101711234/store/IMAGES/click_here_button.gif" width="87" height="24" align="center"></a>
        <p align="center"><b><font size="+1">Hurry! Offer ends January 31, 2001.</font></b></p>
      </td>
    </tr>
  </tbody>
</table>

  </center>
</div>
<div align="center">
  <center>
  <table border="0" width="526" height="48">
    <tr>
      <td width="518" height="42" align="center"><font color="#000000" face="Arial" size="1">You
        are receiving this special offer because you have provided permission to
        receive email communications regarding special online promotions or
        offers. To discontinue any further messages from our company,&nbsp;
        please</font><font color="#003333" face="Arial" size="1"> <a href="mailto:opt-out@straminc.com?Subject=UNSUBSCRIBE" style="COLOR: #800000">Click
        Here to Unsubscribe from our Mailing List</a>. </font><font face="Arial" size="1" color="#000000">We
        apologize for any inconvenience.</font></td>
    </tr>
  </table>
  </center>
</div>

</body>

</html>

--=200201041647=--


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



From daemon@optimus.ietf.org  Sat Jan  5 16:08:48 2002
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 QAA07390
	for <avt-archive@odin.ietf.org>; Sat, 5 Jan 2002 16:08:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA21058
	for avt-archive@odin.ietf.org; Sat, 5 Jan 2002 16:08:49 -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 QAA21004;
	Sat, 5 Jan 2002 16:07:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA20971
	for <avt@optimus.ietf.org>; Sat, 5 Jan 2002 16:07:52 -0500 (EST)
Received: from demetrius.hosting.swbell.net (demetrius.hosting.swbell.net [216.100.99.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07304
	for <avt@ietf.org>; Sat, 5 Jan 2002 16:07:49 -0500 (EST)
Received: from pti-inc.com (ppp-64-216-219-50.dialup.stlsmo.swbell.net [64.216.219.50])
	by demetrius.hosting.swbell.net
	id QAA13582; Sat, 5 Jan 2002 16:07:47 -0500 (EST)
	[ConcentricHost SMTP Relay 1.14]
Message-ID: <200201052107.QAA13582@demetrius.hosting.swbell.net>
Date: 05 Jan 02 11:46:13 -0600
From: "Mark Masters"<mark@pti-inc.com>
X-Mailer: MailKing v2.0
To: <avt@ietf.org>
Subject: [AVT] Adv: Semiconductor Training Courseware
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

Greetings:

PTI Seminars is presenting the following courses for semiconductor
personnel....

 For more details call 636-343-1333 and ask for Mark Masters.

 ABCs of IC DESIGN & FABRICATION - Presented by: Denny Frye
 http://www.pti-inc.com/icdesignfab.html
  February 20, 2002 San Jose, CA
  March 11, 2002 Portland, OR
  March 18, 2002 Singapore
  April 9, 2002 Boston, MA
  April 19, 2002 Munich, Germany
  April 30, 2002   Phoenix, AZ
 
This course describes in simple terms a sequential format of   
information that constitutes the major fabrication processes and design  
for integrated devices. This one (1) day seminar gives you a 
comprehensive overview of the semiconductor industry & technology. 
The course will give you the background you need to understand the 
basics of semiconductor devices, how they work, the processing 
technologies & equipment to produce them, and circuit design techniques.
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ABCs of BASIC ELECTRONICS AND DEVICES
 http://www.pti-inc.com/basicmain.html
 March 18, 2002   San Jose, CA

ADVANCED TOPICS IN CMP Chemical Mechanical Planarization
 http://www.pti-inc.com/advancedcmp.html
 March 21-22, 2002   San Jose, CA

DEFECT ISOLATION for MULTI LEVEL FAILURE ANALYSIS
 http://www.pti-inc.com/defectisolation.html
 March 25-26, 2002   San Jose, CA

DEVICE PHYSICS MADE EASY
 http://www.pti-inc.com/physics.html
  April 8, 2002  San Jose, CA
 
Fundamentals of CHEMICAL MECHANICAL PROCESSING
 Presented by: Srini Raghavan 
 http://www.pti-inc.com/cmpmain.html
  March 6, 2002   San Jose, CA

Fundamentals of CHEMICAL VAPOR DEPOSITION
 http://www.pti-inc.com/cvdmain.html
  April 3, 2002   San Jose, CA

Fundamentals of ION IMPLANTATION
 http://www.pti-inc.com/ionmain.html
 April 2, 2002   San Jose, CA

Fundamentals of MEMS DESIGN & FABRICATION
 http://www.pti-inc.com/memsic.html
 April 10, 2002   San Jose, CA
 July 24, 2002  San Francisco, CA

Fundamentals of METALLIZATION
 http://www.pti-inc.com/metalmain.html
 April 4, 2002   San Jose, CA

Fundamentals RF Plasma Generation for Semiconductor Equipment
 http://www.pti-inc.com/rfequipment.html
 April 4, 2002   San Jose, CA
 July 24-25, 2002  San Francisco, CA

Fundamentals of WET & DRY ETCH
 http://www.pti-inc.com/etchmain.html
 March 7, 2002   San Jose, CA

Fundamentals of PHOTOLITHOGRAPHY
 http://www.pti-inc.com/photomain.html
 March 19, 2002   San Jose, CA

Fundamentals of THERMAL PROCESSING
 http://www.pti-inc.com/diffmain.html
 March 12, 2002   San Jose, CA

INTELLECTUAL PROPERTY STRATEGIES 
for SEMICONDUCTOR INDUSTRY COMPANIES
http://www.intellectual.html
 February 18-19, 2002 San Jose, CA
 July 24-25, 2002  San Francisco, CA

Intro to CMOS LAYOUT
 http://www.pti-inc.com/cmos.html
 May 6-7, 2002  San Jose, CA

Intro to DIGITAL SIGNAL PROCESSING
 http://www.pti-inc.com/dsp.html
 April 24-26, 2002  San Jose, CA

Intro to MICRO CONTAMINATION CONTROL
 http://www.pti-inc.com/contamain.html
 March 21, 2002  San Jose, CA

Intro to Optical MEMS for Bio Sensing and Communications 
 http://www.pti-inc.com/mems.html 
 April 11, 2002   San Jose, CA
 
Intro to INTEGRATED YIELD MANAGEMENT
 http://www.pti-inc.com/yieldmanagement.html
 March 4-5, 2002   San Jose, CA
 April 18-19, 2002  Munich, Germany
 May 6-7, 2002  Singapore 

Intro to STATISTICAL PROCESSING CONTROL  (SPC)
 http://www.pti-inc.com/spc.html
 April 9, 2002  San Jose, CA

LOW COST FLIP CHIP & WLCSP TECHNOLOGIES
http://www.pti-inc.com/flipchip.html
  April 8, 2002  San Jose, CA
  April 15, 2002  Munich, Germany
  May 9, 2002  Singapore
  July 19, 2002  San Francisco, CA

PRODUCT MARKETING for the Semiconductor Industry
 http://www.pti-inc.com/productmarketing.html
  February 27, 2002  San Jose, CA
  April 18, 2002  Munich, Germany
  May 9, 2002  Singapore

RF WIRELESS FUNDAMENTALS
 http://www.pti-inc.com/rfwireless.html
 February 25-26, 2002  San Jose, CA

CHECK OUR WEB SITE FOR ADDITIONAL COURSES !!
 http://www.ptiseminars.com

 For a FULL TRAINING SCHEDULE of "open" course dates visit 
  http://www.pti-inc.com/schedule.htm

TO REGISTER Go To
 https://secure.hosting.swbell.net/www.pti-inc.com/registration.html

 TO SPEAK:
    * to an account manager about ATTENDING these courses or having them
 ONSITE
    contact us at (636) 343-1333 in the USA.  Ask for MARK MASTERS.
    * Fax  (636) 343-8642
    * Email: mark@pti-inc.com

 PTI SEMINARS, INC.  "We Exceed Your Expectations!"

 * To unsubscribe please reply to heather@pti-inc.com and in the subject
 "Unsubscribe".  We apologize for any inconvenience.




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



From daemon@optimus.ietf.org  Sun Jan  6 01:44:04 2002
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 BAA12952
	for <avt-archive@odin.ietf.org>; Sun, 6 Jan 2002 01:44:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA12227
	for avt-archive@odin.ietf.org; Sun, 6 Jan 2002 01:44:06 -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 BAA12205;
	Sun, 6 Jan 2002 01:42:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19624
	for <avt@optimus.ietf.org>; Sat, 5 Jan 2002 15:14:04 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06969
	for <avt@ietf.org>; Sat, 5 Jan 2002 15:14:02 -0500 (EST)
Received: from cab.cs.ucsb.edu (cab [128.111.49.120])
	by letters.cs.ucsb.edu (8.10.2+Sun/8.9.3) with ESMTP id g05K6RQ18297;
	Sat, 5 Jan 2002 12:06:28 -0800 (PST)
Received: by cab.cs.ucsb.edu (8.10.2+Sun/SMI-SVR4)
	id g05K6R205678 for ; Sat, 5 Jan 2002 12:06:27 -0800 (PST)
Date: Sat, 5 Jan 2002 12:06:27 -0800 (PST)
From: almeroth@cs.ucsb.edu (Kevin C. Almeroth)
Message-Id: <200201052006.g05K6R205678@cab.cs.ucsb.edu>
To: griff@netlab.uky.edu
Subject: [AVT] NOSSDAV 2002 Submissions Due Soon
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


Important Notes

1.  THE DEADLINE OF JANUARY 13, 2002 IS FAST APPROACHING.

2.  Format is 5 page abstracts in ACM double column format.

3.  Paper submission will be available next week at:
    http://www.nossdav.org/2002/submit.html

4.  Send extension requests to:  almeroth@cs.ucsb.edu or griff@netlab.uky.edu

5.  IWQoS (http://www.cs.virginia.edu/iwqos) is at the same location
    the three days after NOSSDAV, i.e. May 15-17.
-----------------------------------------------

                       The 12th International Workshop on
     Network and Operating Systems Support for Digital Audio and Video
                               (NOSSDAV 2002)

                           Sponsored by ACM SIGMM
                              May 12-14, 2002
                            Miami Beach, Florida

                        http://www.nossdav.org/2002

                              CALL FOR PAPERS

Objectives

The 12th International Workshop on Network and Operating Systems Support for
Digital Audio and Video (NOSSDAV) brings together researchers, developers,
and practitioners from academia and industry to present and discuss new
ideas and future directions in networking and operating systems support for
multimedia. For 11 years, NOSSDAV has proven to be an outstanding forum for
researchers and developers involved in building innovative multimedia
systems, networks, and applications.

Multimedia data such as pictures, MP3s, motion video, digital library
collections, interactive network games, and others have become pervasive,
primary data sources. NOSSDAV seeks to discuss and examine new, efficient,
and effective infrastructure and applications to support these demanding
primary data sources.

To ensure a productive workshop environment, attendance will be limited to
about 75 participants who are active in the field. A key aspect of the
workshop is that it provides extensive discussion periods during which
attendees can informally discuss their current work and future research
directions. Traditionally, NOSSDAV has emphasized high quality experimental
research based on prototype or real systems. NOSSDAV 2002 will continue this
tradition.

Submissions

Submissions are sought in any area related to Network and Operating Systems
Support for Digital Audio and Video. The topics of interest include, but are
not limited to:

   * ubiquitous multimedia services
   * peer-to-peer multimedia services
   * internet telephony
   * broadband streaming media content distribution
   * 3D multimedia and (networked) immersive environments
   * real-time interactive streaming services
   * interactive network games
   * wireless and ad-hoc network multimedia systems
   * multimedia information appliances and consumer devices
   * quality-of-service control and scheduling algorithms
   * differentiated and integrated services networks
   * multimedia caching
   * collaborative conferencing
   * multimedia conference access and QoS policy enforcement
   * digital library access methods

We solicit submissions of 5-page extended abstracts of technical papers,
work-in-progress reports, and position statements. Papers should identify
new problems and explain why they are important, challenge conventional
wisdom, advocate a specific solution, and/or report on actual experience
with real systems. All submissions will be reviewed by the members of the
program committee. Submissions will be selected on the basis of their
originality, technical merit and topical relevance, as well as the
likelihood that the ideas will lead to insightful technical discussions.
Papers submitted to NOSSDAV must not have been published or submitted
elsewhere. Please do not submit abbreviated versions of journal or
conference papers.

Authors of accepted papers will be invited to present at the workshop and
publish full-length versions of their papers in the workshop proceedings.

All submissions must be made through the web. We suggest that authors use
the two-column ACM format for the submissions. Detailed paper submission
guidelines will be available on the WWW page in January.

Important Dates

          Submission Deadline:     January 13, 2002 (midnight PST)
          Acceptance Notification: March 4, 2002
          Camera Ready Deadline:   April 8, 2002
          Workshop:                May 12-14, 2002

NOSSDAV 2002 Program Chairs
 Kevin Almeroth           UC-Santa Barbara
 Jim Griffioen            Univ of Kentucky

Program Committee
 Please see the WWW page.


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



From daemon@optimus.ietf.org  Mon Jan  7 09:08:49 2002
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 JAA14724
	for <avt-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:08:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA06369
	for avt-archive@odin.ietf.org; Mon, 7 Jan 2002 09:08:49 -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 JAA06265;
	Mon, 7 Jan 2002 09:06:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06236
	for <avt@optimus.ietf.org>; Mon, 7 Jan 2002 09:06:43 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14411;
	Mon, 7 Jan 2002 09:06:42 -0500 (EST)
Message-Id: <200201071406.JAA14411@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: avt@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 07 Jan 2002 09:06:42 -0500
Subject: [AVT] I-D ACTION:draft-ietf-avt-ulp-03.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.

	Title		: An RTP Payload Format for Generic FEC with Uneven 
                          Level Protection
	Author(s)	: A. Li et al.
	Filename	: draft-ietf-avt-ulp-03.txt
	Pages		: 29
	Date		: 04-Jan-02
	
This document specifies a payload format for generic forward error
correction to achieve uneven level protection (ULP) of media
encapsulated in RTP. It is an extension to the forward error
correction scheme specified in RFC 2733 [1], and it is also based on
the exclusive-or (parity) operation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-ulp-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-avt-ulp-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-ulp-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020104143415.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-ulp-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-avt-ulp-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020104143415.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Mon Jan  7 10:32:33 2002
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 KAA17320
	for <avt-archive@odin.ietf.org>; Mon, 7 Jan 2002 10:32:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA09625
	for avt-archive@odin.ietf.org; Mon, 7 Jan 2002 10:32:34 -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 KAA09580;
	Mon, 7 Jan 2002 10:31:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09544
	for <avt@optimus.ietf.org>; Mon, 7 Jan 2002 10:31:39 -0500 (EST)
Received: from jenny.panasonic.de (mail.pel.panasonic.de [194.221.52.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17307
	for <avt@ietf.org>; Mon, 7 Jan 2002 10:31:36 -0500 (EST)
Received: from atrgburc (gonzo [192.129.34.15])
 by jenny.panasonic.de (__________PEL__Mail-Server__________)
 with SMTP id <0GPK00F2UR57SY@jenny.panasonic.de> for avt@ietf.org; Mon,
 7 Jan 2002 16:31:56 +0100 (MET)
Date: Mon, 07 Jan 2002 16:31:57 +0100
From: Carsten Burmeister <burmeister@panasonic.de>
To: Ietf-Avt <avt@ietf.org>
Cc: Carsten Burmeister <burmeister@panasonic.de>
Message-id: <NFBBIKDKLMBPPGNIBAGGKEIJCPAA.burmeister@panasonic.de>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [AVT] RTP Retransmissions (discussion restart)
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
Content-Transfer-Encoding: 7BIT

Dear All,

Happy New Year!

I could not attend the last IETF meeting, but from the pre-minutes I saw
that the retransmissions were discussed. As there were also some discussions
on the mailing list before the meeting and in parallel, I would like to try
to summarize those and re-start the discussions.

There are two drafts dealing with retransmissions in RTP: The AVT work item
draft draft-ietf-avt-rtp-selret-03.txt and the proposal of David
draft-leon-rtp-retransmission-01.txt. There have been a couple of changes in
both drafts during the last iteration(s), however I would like to discuss
the drafts only as they are now.

The main difference between the drafts is the following: The AVT-draft
allows sending the retransmissions in the same RTP/RTCP session *and*
sending them in a different RTP/RTCP session. Both possibilities are
separated by the means of some signalling, e.g. SDP. The Leon-draft allows
sending the retransmissions in a different RTP/RTCP session, but forbids
sending the retransmissions in the same RTP/RTCP session.

We propose to allow both options in the AVT-draft, because we think that
there are different applications with different requirements on the
retransmission scheme. The applications we have in mind (e.g. MPEG-4
streaming over unreliable networks) can benefit significantly from sending
the retransmissions in the same session as the original data, because of the
much faster recovery scheme. Norihito Takatori (from Mitsubishi) also
supported this option. David Leon wants to send the retransmissions in a
different RTP session. Especially for the conversational text payload
format, where the indication of lost packets to the receiving application is
recommended, this might be beneficial (however using this indication
together with retransmissions is a little bit more tricky anyway).

To us these discussions already reveal that there is a need for more than
one very restrictive retransmission scheme. As our payload formats can build
these schemes and they can be separated, e.g. by SDP, we think that this
would be a good solution for all.

David has a different opinion and wants to restrict the retransmission
scheme to send the retransmissions always on a different RTP/RTCP session.
Our application design would have problems with that and the performance
would be decreased, e.g. because of the need for additional timers, RTP
sessions and the longer response times.

Are there more opinions or comments?

BR,
Carsten


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



From daemon@optimus.ietf.org  Mon Jan  7 11:22:19 2002
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 LAA19065
	for <avt-archive@odin.ietf.org>; Mon, 7 Jan 2002 11:22:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA11397
	for avt-archive@odin.ietf.org; Mon, 7 Jan 2002 11:22:20 -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 LAA11378;
	Mon, 7 Jan 2002 11:21:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11347
	for <avt@optimus.ietf.org>; Mon, 7 Jan 2002 11:21:31 -0500 (EST)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19050
	for <avt@ietf.org>; Mon, 7 Jan 2002 11:21:28 -0500 (EST)
Received: from mira-sjc5-1.cisco.com (mira-sjc5-1.cisco.com [171.71.163.15])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id g07GKXk22328;
	Mon, 7 Jan 2002 08:20:35 -0800 (PST)
Received: from BFOSTER-W2K.cisco.com (sjc-vpn3-83.cisco.com [10.21.64.83])
	by mira-sjc5-1.cisco.com (Mirapoint)
	with ESMTP id ACY39266;
	Mon, 7 Jan 2002 08:20:31 -0800 (PST)
Message-Id: <4.3.2.7.2.20020107080722.016d6ef8@mira-sjc5-1.cisco.com>
X-Sender: bfoster@mira-sjc5-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 Jan 2002 08:14:47 -0800
To: Carsten Burmeister <burmeister@panasonic.de>
From: Bill Foster <bfoster@cisco.com>
Subject: Re: [AVT] RTP Retransmissions (discussion restart)
Cc: Ietf-Avt <avt@ietf.org>, Carsten Burmeister <burmeister@panasonic.de>
In-Reply-To: <NFBBIKDKLMBPPGNIBAGGKEIJCPAA.burmeister@panasonic.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 04:31 PM 1/7/2002 +0100, Carsten Burmeister wrote:
>Dear All,
>
>Happy New Year!
>
>I could not attend the last IETF meeting, but from the pre-minutes I saw
>that the retransmissions were discussed. As there were also some discussions
>on the mailing list before the meeting and in parallel, I would like to try
>to summarize those and re-start the discussions.
>
>There are two drafts dealing with retransmissions in RTP: The AVT work item
>draft draft-ietf-avt-rtp-selret-03.txt and the proposal of David
>draft-leon-rtp-retransmission-01.txt. There have been a couple of changes in
>both drafts during the last iteration(s), however I would like to discuss
>the drafts only as they are now.
>
>The main difference between the drafts is the following: The AVT-draft
>allows sending the retransmissions in the same RTP/RTCP session *and*
>sending them in a different RTP/RTCP session. Both possibilities are
>separated by the means of some signalling, e.g. SDP. The Leon-draft allows
>sending the retransmissions in a different RTP/RTCP session, but forbids
>sending the retransmissions in the same RTP/RTCP session.
>
>We propose to allow both options in the AVT-draft, because we think that
>there are different applications with different requirements on the
>retransmission scheme. The applications we have in mind (e.g. MPEG-4
>streaming over unreliable networks) can benefit significantly from sending
>the retransmissions in the same session as the original data, because of the
>much faster recovery scheme. Norihito Takatori (from Mitsubishi) also
>supported this option.

I also support this option. The ability to detect the loss of RTX packets 
more quickly by using the same sequence number space as the RTP packets is 
important for some applications. There may be some advantages in some 
applications for having a separate RTP session, but in other applications 
it is a distinct disadvantage. I think we should allow both.

>David Leon wants to send the retransmissions in a
>different RTP session. Especially for the conversational text payload
>format, where the indication of lost packets to the receiving application is
>recommended, this might be beneficial (however using this indication
>together with retransmissions is a little bit more tricky anyway).
>
>To us these discussions already reveal that there is a need for more than
>one very restrictive retransmission scheme. As our payload formats can build
>these schemes and they can be separated, e.g. by SDP, we think that this
>would be a good solution for all.
>
>David has a different opinion and wants to restrict the retransmission
>scheme to send the retransmissions always on a different RTP/RTCP session.
>Our application design would have problems with that and the performance
>would be decreased, e.g. because of the need for additional timers, RTP
>sessions and the longer response times.
>
>Are there more opinions or comments?
>
>BR,
>Carsten
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>http://www1.ietf.org/mailman/listinfo/avt

-----------------------------
Bill Foster
Phone: (250) 758-9418
Fax:     (781) 998-6492


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



From daemon@ns.ietf.org  Mon Jan  7 21:49:06 2002
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 VAA04462
	for <avt-archive@odin.ietf.org>; Mon, 7 Jan 2002 21:49:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA02239
	for avt-archive@odin.ietf.org; Mon, 7 Jan 2002 21:49:08 -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 VAA02212;
	Mon, 7 Jan 2002 21:48:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA02183
	for <avt@ns.ietf.org>; Mon, 7 Jan 2002 21:48:14 -0500 (EST)
Received: from el-postino.s-vision.com ([207.108.173.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04450
	for <avt@ietf.org>; Mon, 7 Jan 2002 21:48:10 -0500 (EST)
Received: by el-postino.s-vision.com with Internet Mail Service (5.5.2653.19)
	id <VD6ADFV8>; Mon, 7 Jan 2002 19:46:57 -0700
Message-ID: <6E031E06378BD311AEF20090273CE1BADFEDC9@el-postino.s-vision.com>
From: Kris Huber <khuber@sorensontech.com>
To: imtch323implementors@mail.imtc.org, "'avt@ietf.org'" <avt@ietf.org>
Date: Mon, 7 Jan 2002 19:46:56 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C197EE.BC709530"
Subject: [AVT] Determination/indication of the number of H.263 macroblocks in a
 slice
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C197EE.BC709530
Content-Type: text/plain;
	charset="iso-8859-1"

Hello H.323 implementors and IETF AVT group,
 
I have a question about implementation of error resilience for video using
H.263's slice mode in the H.323 (or other RTP) environment.  Packets
typically consist of a slice, and when one is lost or too late, the lost
macroblocks should be concealed.  But knowing which macroblocks were lost
seems to require a bit more computation than you would think.  The address
of the last MB in the lost packet can be found quite easily by peeking at
the slice header inside the following packet's payload, but it seems that
VLC decoding of the entire H.263 slice preceeding the missing slice is
necessary to compute the address of the first MB of the missing slice.  Is
this true, or have I missed something?
 
Using the H.245 videoBadMBs command or videoNotDecodedMBs indication, the
range of MB addresses needs to be sent from the decoder to the encoder as
quickly as possible so it can code without dependencies an area that clears
the erroneous video.
One solution would be for the encoder to send the number of macroblocks in
each slice within the packet payload, but I think the payload is not
extensible in a standards-compliant way (is this correct?).
 
Is there another way that I may not be aware of to send the number of
macroblocks in each slice (H.245 messaging, perhaps, if not too slow?).
 
I believe the same thing is true of MPEG-4 video over H.323:  the packet
preceeding the lost packet must be decoded to know the address of the first
missing macroblock.  I suspect this is also true of MPEG-4 video over MPEG-4
systems as well.
 
Also, I vaguely recall reading of some standardization work to specify
packetization and codes for making low-latency reliable channels on IP
networks.  I'd be interested in a pointer to some information on the status
of that.
 
Thanks for any comments on this
 
Best regards,
Kris Huber
Senior Research Engineer
Sorenson Technologies, Inc.
 

------_=_NextPart_001_01C197EE.BC709530
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.3103.1000" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>Hello 
H.323 implementors and IETF AVT group,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>I have 
a question about implementation of&nbsp;error resilience for video using H.263's 
slice mode in the H.323 (or other RTP) environment.&nbsp;&nbsp;Packets typically 
consist of a slice, and when one is lost or too late, the lost macroblocks 
should be concealed.&nbsp; But knowing which macroblocks were lost seems to 
require a bit more computation than you would think.&nbsp; The&nbsp;address of 
the last&nbsp;MB in&nbsp;the lost packet can be found quite easily by peeking at 
the&nbsp;slice header inside the following packet's payload, but&nbsp;it seems 
that&nbsp;VLC decoding of&nbsp;the entire H.263 slice preceeding the 
missing&nbsp;slice is necessary to compute&nbsp;the address of the first 
MB&nbsp;of the missing slice.&nbsp;&nbsp;Is this true, or have I missed 
something?</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial>Using the H.245 
videoBadMBs command or videoNotDecodedMBs indication, the&nbsp;range of MB 
addresses needs to be&nbsp;sent&nbsp;from&nbsp;the decoder to the encoder as 
quickly as possible so it can&nbsp;<SPAN class=532020100-08012002>code without 
dependencies an area that&nbsp;</SPAN>clear<SPAN 
class=532020100-08012002>s</SPAN> the erroneous 
video.</FONT></FONT></FONT></DIV>
<DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>One 
solution would be for the encoder to send&nbsp;the number of macroblocks in each 
slice within the packet payload, but I think the payload is not extensible in a 
standards-compliant way (is this correct?).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>Is 
there another way that I may not be aware of to send the number of macroblocks 
in each slice (H.245 messaging, perhaps, if not too slow?).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT><FONT color=#0000ff face=Arial 
size=2><SPAN class=532020100-08012002>I believe the same&nbsp;thing is true 
of&nbsp;MPEG-4 video over H.323:&nbsp; the packet preceeding the lost 
packet&nbsp;must be decoded to know the address of the first missing 
macroblock.&nbsp; I suspect this is also&nbsp;true of MPEG-4 video over MPEG-4 
systems as well.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>Also, 
I vaguely recall reading of some standardization&nbsp;work to specify 
packetization and codes for making low-latency reliable channels on IP 
networks.&nbsp; I'd be interested in a pointer to some information on the status 
of that.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT><FONT color=#0000ff face=Arial 
size=2><SPAN class=532020100-08012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>Thanks 
for any comments on this</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT><FONT color=#0000ff face=Arial 
size=2><SPAN 
class=532020100-08012002>&nbsp;</DIV></SPAN></FONT></SPAN></FONT></SPAN></FONT><FONT 
color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT></DIV></DIV></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>Best 
regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002>Kris</SPAN></FONT><FONT color=#0000ff face=Arial 
size=2><SPAN class=532020100-08012002> Huber</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=532020100-08012002>Senior 
Research Engineer</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002>Sorenson Technologies, Inc.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=532020100-08012002></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C197EE.BC709530--

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



From daemon@ns.ietf.org  Mon Jan  7 23:11:11 2002
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 XAA06332
	for <avt-archive@odin.ietf.org>; Mon, 7 Jan 2002 23:11:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA04240
	for avt-archive@odin.ietf.org; Mon, 7 Jan 2002 23:11:14 -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 XAA04166;
	Mon, 7 Jan 2002 23:05:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04136
	for <avt@ns.ietf.org>; Mon, 7 Jan 2002 23:05:33 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06246
	for <avt@ietf.org>; Mon, 7 Jan 2002 23:05:29 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0844wp06371;
	Mon, 7 Jan 2002 20:04:59 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 7 Jan 2002 20:06:47 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: "Even ,Roni" <roni.even@polycom.co.il>
cc: "'avt@ietf.org'" <avt@ietf.org>
Subject: Re: [AVT] comments on draft-ietf-avp-rtcp-feedback-01.txt
In-Reply-To: <B2518D608282D511BEA400508BBB91480AEEA9@ACCORD-NTSRV3>
Message-ID: <20020107195811.B71614-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

Roni,

A partial reply to your comments:

> My understanding of the document is that the feedback mechanism is to allow
> a feedback channel between the decoder and encoder to allow immediate repair
> of media stream. After reading the document I have the following comments
>
> 1. In section 6.3 the text is "AVPF entities MUST include Generic INFO
> messages along with any payload-specific ones in compound RTCP packets
> (early as well as  regularly scheduled ones). "  This means that if an
> encoder is capable of supporting "nack" it needs to support generic info.
> The capability to support generic INFO is not explained in 4.2. In 6.2 it
> says that "two general purpose transport layer feedback..." but three are
> listed. In 6.2.3 it states that "The Generic INFO packet MUST only be used
> in conjunction with an application-specific feedback message. " which
> contradict the above text in 6.3.

It was resolved at the meeting that Generic INFO will be eliminated.
It was an attempt to fix a problem but it doesn't help.

> 2. The document leaves open the issue of what the senders should do with the
> feedback. In the video implementations today we see two kind of feedbacks,
> between send and receiver of media, commands and indications. My
> understanding of the nack params (PLI and SLI) is that they are similar to
> the commands, the preferred mode is for them to cause new intra picture or
> MB. This params are for general video media and not for specific codec. The
> indications for specific codec are left to the application layer feedback as
> described in section 6.4. I suggest that the last sentence in 4.2 will be
> changed to  "It is up to the recipients whether or not they send feedback
> information and up to the sender(s) to make use of feedback provided unless
> an action is required by the specific feedback message." The text in 6.3
> will state that PLI and SLI will cause fast updates from the sender. This
> will help with having a consistent response between sender and receiver.

I don't object to your sentence, but the requirement for action is not
specified by this profile, rather by the codec document which defines
the feedback information to be carried with the application-specific
feedback message of this profile.

> 3. In order to be able to use the messages in video switching scenarios we
> need in 6.3 another payload specific message which is PIZ (Picture Freeze).
> This is needed for completeness. Video switch involves freeze and fast
> update and since we have here fast update it is better to have the full
> support.
>
> 4. For information purpose, we have today in video codec specific
> application the following indications used for resilience support, lost
> picture and lost partial picture for H.263 annex U & W. Not decoded MB for
> H.263 appendix I and video bad MB to let the encoder know that those MBs
> cannot be used for prediction.

An email from Kris Huber today was essentially asking about the same thing.

> 5. In section 4.3 the references to other sections like in the description
> of pli, sli and rpsi are not correct.

							-- Steve


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



From daemon@ns.ietf.org  Tue Jan  8 02:33:58 2002
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 CAA17112
	for <avt-archive@odin.ietf.org>; Tue, 8 Jan 2002 02:33:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA18353
	for avt-archive@odin.ietf.org; Tue, 8 Jan 2002 02:33:59 -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 CAA18339;
	Tue, 8 Jan 2002 02:33:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA18308
	for <avt@ns.ietf.org>; Tue, 8 Jan 2002 02:33:10 -0500 (EST)
Received: from accord-ntsrv3.accord-domain ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17105
	for <avt@ietf.org>; Tue, 8 Jan 2002 02:33:07 -0500 (EST)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <ZW3G7831>; Tue, 8 Jan 2002 09:30:03 +0200
Message-ID: <B2518D608282D511BEA400508BBB91480AEECD@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Stephen Casner'" <casner@acm.org>,
        "Even, Roni"
	 <roni.even@polycom.co.il>
Cc: "'avt@ietf.org'" <avt@ietf.org>
Subject: RE: [AVT] comments on draft-ietf-avp-rtcp-feedback-01.txt
Date: Tue, 8 Jan 2002 09:30:03 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
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

Steve,

About my item number 2. Video fast update are relevant to all video media
and not a specific codec  that is why I think that the sentence should be in
this draft. I  also wanted to make a distinction between feedback
indications and action feedback messages. 
Thanks 
Roni Even

-----Original Message-----
From: Stephen Casner [mailto:casner@acm.org]
Sent: Tuesday, January 08, 2002 6:07 AM
To: Even ,Roni
Cc: 'avt@ietf.org'
Subject: Re: [AVT] comments on draft-ietf-avp-rtcp-feedback-01.txt


Roni,

A partial reply to your comments:

> My understanding of the document is that the feedback mechanism is to
allow
> a feedback channel between the decoder and encoder to allow immediate
repair
> of media stream. After reading the document I have the following comments
>
> 1. In section 6.3 the text is "AVPF entities MUST include Generic INFO
> messages along with any payload-specific ones in compound RTCP packets
> (early as well as  regularly scheduled ones). "  This means that if an
> encoder is capable of supporting "nack" it needs to support generic info.
> The capability to support generic INFO is not explained in 4.2. In 6.2 it
> says that "two general purpose transport layer feedback..." but three are
> listed. In 6.2.3 it states that "The Generic INFO packet MUST only be used
> in conjunction with an application-specific feedback message. " which
> contradict the above text in 6.3.

It was resolved at the meeting that Generic INFO will be eliminated.
It was an attempt to fix a problem but it doesn't help.

> 2. The document leaves open the issue of what the senders should do with
the
> feedback. In the video implementations today we see two kind of feedbacks,
> between send and receiver of media, commands and indications. My
> understanding of the nack params (PLI and SLI) is that they are similar to
> the commands, the preferred mode is for them to cause new intra picture or
> MB. This params are for general video media and not for specific codec.
The
> indications for specific codec are left to the application layer feedback
as
> described in section 6.4. I suggest that the last sentence in 4.2 will be
> changed to  "It is up to the recipients whether or not they send feedback
> information and up to the sender(s) to make use of feedback provided
unless
> an action is required by the specific feedback message." The text in 6.3
> will state that PLI and SLI will cause fast updates from the sender. This
> will help with having a consistent response between sender and receiver.

I don't object to your sentence, but the requirement for action is not
specified by this profile, rather by the codec document which defines
the feedback information to be carried with the application-specific
feedback message of this profile.

> 3. In order to be able to use the messages in video switching scenarios we
> need in 6.3 another payload specific message which is PIZ (Picture
Freeze).
> This is needed for completeness. Video switch involves freeze and fast
> update and since we have here fast update it is better to have the full
> support.
>
> 4. For information purpose, we have today in video codec specific
> application the following indications used for resilience support, lost
> picture and lost partial picture for H.263 annex U & W. Not decoded MB for
> H.263 appendix I and video bad MB to let the encoder know that those MBs
> cannot be used for prediction.

An email from Kris Huber today was essentially asking about the same thing.

> 5. In section 4.3 the references to other sections like in the description
> of pli, sli and rpsi are not correct.

							-- Steve

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



From daemon@optimus.ietf.org  Tue Jan  8 20:26:53 2002
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 UAA15794
	for <avt-archive@odin.ietf.org>; Tue, 8 Jan 2002 20:26:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA01339
	for avt-archive@odin.ietf.org; Tue, 8 Jan 2002 20:26:54 -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 UAA01264;
	Tue, 8 Jan 2002 20:23:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA01232
	for <avt@optimus.ietf.org>; Tue, 8 Jan 2002 20:23:27 -0500 (EST)
Received: from 100m.mpr200-1.esr.lvcm.net (IDENT:mirapoint@100m.mpr200-1.esr.lvcm.net [24.234.0.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15747
	for <avt@ietf.org>; Tue, 8 Jan 2002 20:23:24 -0500 (EST)
Received: from yahoo.com (cm245.132.120.24.lvcm.com [24.120.132.245])
	by 100m.mpr200-1.esr.lvcm.net (Mirapoint)
	with SMTP id AUO88715;
	Tue, 8 Jan 2002 17:23:18 -0800 (PST)
Date: Tue, 8 Jan 2002 17:23:18 -0800 (PST)
Message-Id: <200201090123.AUO88715@100m.mpr200-1.esr.lvcm.net>
Content-Type: text/plain; charset=us-ascii
X-Priority: 5
From: John Murdok <dreamerz12002@yahoo.com>
To: avt@ietf.org
Reply-To: dreamerz12002@yahoo.com
Subject: [AVT] Hey!!
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

///////////////////////////////////////////////////////////////// 
ONE TIME MAILING, NO NEED TO REMOVE 
///////////////////////////////////////////////////////////////// 

AS SEEN ON NATIONAL TV : 

''Making over half million dollars every 4 to 5 months from your 
home for an investment of only $25 US Dollars expense one time'' 
THANKS TO THE COMPUTER AGE AND THE INTERNET! 
================================================= 

BE A MILLIONAIRE LIKE OTHERS WITHIN A YEAR!!! 

Before you say ''Bull'', please read the following. This is the 
letter you have been hearing about on the news lately. Due to 
the 
popularity of this letter on the internet, a national weekly 
news 
program recently devoted an entire show to the investigation of 
this program described below, to see if it really can make 
people 
money. 

The show also investigated whether or not the program was legal. 
Their findings proved once and for all that there are 
''absolutely NO laws prohibiting the participation in the 
program and if 
people can follow the simple instructions, they are bound to 
make some mega bucks with only $25 out of pocket cost''. 

DUE TO THE RECENT INCREASE OF POPULARITY & 
RESPECT THIS PROGRAM HAS ATTAINED, IT IS CURRENTLY 
WORKING BETTER THAN EVER. 

This is what one had to say: 
''Thanks to this profitable opportunity. I was approached many 
times before but each time I passed on it. I am so glad I 
finally 
joined just to see what one could expect in return for the 
minimal 
effort and money required. To my astonishment, I received total 
$ 
610,470.00 in 21 weeks, with money still coming in''. 
Pam Hedland, Fort Lee, New Jersey. 

----------------------------------------------------------------- 
-------- 
Here is another testimonial: 

''This program has been around for a long time but I never 
believed in it. But one day when I received this again in the 
mail I decided 
to gamble my $25 on it. I followed the simple instructions and 
viola' - 3 weeks later the money started to come in. First month 
I only made 
$240.00 but the next 2 months after that I made a total of 
$290,000.00. So far, in the past 8 months by re-entering the 
program, I have 
made over $710,000.00 and I am playing it again. The key to 
success in 
this program is to follow the simple steps and NOT change 
anything'' 
More testimonials later but first, 

****PRINT THIS NOW FOR YOUR FUTURE REFERENCE**** 

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 
If you would like to make at least $500,000 every 4 to 5 months 
Easily and comfortably, please read the following...THEN READ IT 
AGAIN and AGAIN!!! 
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 

FOLLOW THE SIMPLE INSTRUCTION BELOW AND YOUR 
FINANCIAL DREAMS WILL COME TRUE, GUARANTEED! 

INSTRUCTIONS: 
****Order all 5 reports shown on the list below. 

****For each report, send $5 CASH, THE NAME & NUMBER OF 
THE REPORT YOU ARE ORDERING and YOUR E-MAIL 
ADDRESS to the person whose name appears ON THAT LIST next 
to the report. MAKE SURE YOUR RETURN ADDRESS IS ON 
YOUR ENVELOPE TOP LEFT CORNER in case of any mail 
problems. 

****When you place your order, make sure you order each of the 5 
Reports. You will need all 5 reports so that you can save them 
on 
your Computer and resell them. YOUR TOTAL COST $5 X 5 = $25.00. 

****Within a few days you will receive, via e-mail, each of the 
5 Reports from these 5 different individuals. Save them on your 
Computer so they will be accessible for you to send to the 
1,000's Of people who will order them from you. Also make a 
floppy of 
these Reports and keep it on your desk in case something happen 
to your 
Computer. 

****IMPORTANT __ DO NOT alter the names of the people who are 
listed next to each report, or their sequence on the list, in 
any 
way other than what is instructed below in step '' 1 through 6 
'' 
or you will loose out on majority of your profits. Once you 
understand the way this works, you will also see how it does not 
work if you change it. 

Remember, this method has been tested, and if you alter, it will 
NOT work!!! People have tried to put their friends/relatives 
names on 
all five thinking they could get all the money. But it does not 
work 
this way. Believe us, we all have tried to be greedy and then 
nothing 
happened. So Do Not try to change anything other than what is 
instructed. Because if you do, it will not work for you. 
Remember, honesty 
reaps the reward!!! 

1....After you have ordered all 5 reports, take this 
advertisement and REMOVE the name & address of the person in 
REPORT #5. This person has made it through the cycle and is no 
doubt counting their fortune. 

2....Move the name & address in REPORT #4 down TO REPORT #5. 

3....Move the name & address in REPORT #3 down TO REPORT #4. 

4....Move the name & address in REPORT #2 down TO REPORT #3. 

5....Move the name & address in REPORT #1 down TO REPORT #2 

6....Insert YOUR name & address in the REPORT #1 Position. 

PLEASE MAKE SURE you copy every name & address 
ACCURATELY! 
================================================= 
****Take this entire letter, with the modified list of names, 
and 
save it on your computer. DO NOT MAKE ANY OTHER CHANGES. Save 
this on a disk as well just in case if you loose any data. 

****To assist you with marketing your business on the internet, 
the 5 reports you purchase will provide you with invaluable 
marketing 
information which includes how to send bulk e-mails legally, 
where to find thousands of free classified ads and much more. 

There are 2 Primary methods to get this venture going: 

METHOD #1 : BY SENDING BULK E-MAIL LEGALLY 
================================================= 
Let's say that you decide to start small, just to see how it 
goes, and we will assume You and those involved send out only 
5,000 
e-mails each. Let's also assume that the mailing receive only a 
0.2% response (the response could be much better but lets just 
say it 
is only 0.2% . Also many people will send out hundreds of 
thousands 
e-mails instead of only 5,000 each). 

Continuing with this example, you send out only 5,000 
e-mails.With a 0.2% response, that is only 10 orders for report 
# 1.Those 10 
people responded by sending out 5,000 e-mail each for a total of 
50,000. 
Out of those 50,000 e-mails only 0.2% responded with orders. 
That's = 
100 people responded and ordered Report # 2. Those 100 people 
mail 
out 5,000 e-mails each for a total of 500,000 e-mails. The 0.2% 
response to that is 1000 orders for Report # 3. Those 1000 
people send out 
5,000 e-mails each for a total of 5 million e-mails sent out. 
The 0.2% 
response to that is 10,000 orders for Report # 4. Those 10,000 
people send out 5,000 e-mails each for a total of 50,000,000 (50 
million) e-mails. The 0.2% response to that is 100,000 orders 
for Report 
#5 

THAT'S 100,000 ORDERS TIMES $5 EACH = $500,000.00 (half 
million). 

Your total income in this example is: 
1..... $50 + 
2..... $500 + 
3..... $5,000 + 
4..... $50,000 + 
5..... $500,000 ......... Grand Total = $555,550.00 

NUMBERS DO NOT LIE. GET A PENCIL & PAPER AND FIGURE 
OUT THE WORST POSSIBLE RESPONSES AND NO MATTER 
HOW YOU CALCULATE IT, YOU WILL STILL MAKE A LOT OF 
MONEY! 


----------------------------------------------------------------- 
-- 
REMEMBER FRIEND, THIS IS ASSUMING ONLY 10 PEOPLE 
ORDERING OUT OF 5,000 YOU MAILED TO. Dare to think for a 
moment what would happen if everyone, or half or even one 4th of 
those people mailed 100,000 e-mails each or more? There are over 
150 million people on the internet worldwide and counting. 
Believe 
me, any people will do just that, and more! 

METHOD #2 : BY PLACING FREE ADS ON THE INTERNET 
================================================= 
Advertising on the net is very very inexpensive and there are 
hundreds of FREE places to advertise. Placing a lot of free ads 
on the 
internet will easily get a larger response. We strongly suggest 
you start 
with method #1 and add METHOD #2 as you go along. For every $5 
you 
receive, all you must do is e-mail them the Report they ordered. 
That's it . Always provide same day service on all orders. This 
will 
guarantee that the e-mail they send out, with your name and 
address on it, 
will be prompt because they can not advertise until they receive 
the 
report. 

_________________AVAILABLE REPORTS__________________ 

ORDER EACH REPORT BY ITS NUMBER & NAME ONLY. 
Notes: Always send $5 cash (US CURRENCY) for each Report. 
Checks NOT accepted. Make sure the cash is concealed by wrapping 
it in at least 2 sheets of paper. On one of those sheets of 
paper, write, or type, the NUMBER & the NAME of the Report you 
are 
ordering, YOUR E-MAIL ADDRESS and your name and postal address. 
(Preferably type, it ensures the right e-mail address for you!) 

Report #1 " The Insiders Guide to Advertising for Free on the 
Net" 

Order Report,#1 from: 
Don Paz
5660 Tahoe dr.
Las Vegas, NV    89142
____________________________________________________ 
REPORT #2 ''The Insider's Guide to SendingBulk e-mail on 
the Net'' 
Order Report #2 from : 
Brian Hafner 
PO Box 2526 
Hartsville, SC 29551 
___________________________________________________ 
REPORT #3 ''The Secret to Multilevel marketing on the Net'' 
Order Report #3 from: 
R.A. Goodew 
1393 Ridgewood Dr. 
Winona, MN. 55987 
___________________________________________________ 
REPORT #4 ''How to become a millionaire utilizing MLM & the 
Net'' 
Order Report #4 from: 
Jennifer Nichole 
PO Box 35 
Fountain City, Wi. 54629-0035 
_____________________________________________________ 
REPORT #5 ''HOW TO SEND 1 MILLION E-MAILS FOR FREE'' 
Order Report #5 from: 
Alyssa Kristine 
PO Box 895 
Winona, MN. 55987 
_____________________________________________________ 
$$$$$$$$$$$$ YOUR SUCCESS GUIDELINES $$$$$$$$$$$$$$ 
Follow these guidelines to guarantee your success: 
***If you do not receive at least 10 orders for Report #1 
within 2 weeks, continue sending e-mails until you do. 
***After you have received 10 orders, 2 to 3 weeks after that 
you 
should receive 100 orders or more for REPORT #2. If you did not, 
continue advertising or sending e-mails until you do. 

***Once you have received 100 or more orders for Report #2, YOU 
CAN RELAX, because the system is already working for you , and 
The cash will continue to roll in! 

THIS IS IMPORTANT TO REMEMBER : Every time your name is 
moved down on the list, you are placed in front of a Different 
report. You can KEEP TRACK of your PROGRESS by watching which 
report people are ordering from you. IF YOU WANT TO 
GENERATE MORE INCOME SEND ANOTHER BATCH OF 
E-MAILS AND START THE WHOLE PROCESS AGAIN. There is 
NO LIMIT to the income you can generate from this business!!! 
______________________________________________________ 

FOLLOWING IS A NOTE FROM THE ORIGINATOR OF THIS 
PROGRAM: 

"You have just received information that can give you financial 
freedom for the rest of your life, with NO RISK and JUST A 
LITTLE 
BIT OF EFFORT. You can make more money in the next few weeks 
and months than you have ever imagined. 

Follow the program EXACTLY AS INSTRUCTED. Do Not change 
it in any way. It works exceedingly well as it is now. Remember 
to e-mail a copy of this exciting report after you have put your 
name and address in Report #1 and moved others to #2 
.........#5 as 
instructed above. One of the people you send this to may send 
out 
100,000 or more e-mails and your name will be on everyone of 
them. Remember though, the more you send out the more potential 
customers you will reach. 
So my friend, I have given you the ideas, information, materials 
and opportunity to become financially independent. IT IS UP TO 
YOU 
NOW! 


****************MORE TESTIMONIALS***************** 

'My name is Mitchell. My wife, Jody and I live in Chicago. I am 
an accountant with a major US Corporation and I make pretty good 
money. When I received this program I grumbled to Jody about 
receiving ''junk mail''. I made fun of the whole thing, spouting 
my knowledge of the population and percentages involved. I 
''knew'' 
it wouldn't work. Jody totally ignored my supposed intelligence 
and 
few days later she jumped in with both feet. I made merciless 
fun of 
her, and was ready to lay the old ''I told you so'' on her when 
the 
thing didn't work. Well, the laugh was on me! Within 3 weeks she 
had 
received 50 responses. Within the next 45 days she had received 
total $ 
147,200.00........ all cash! I was shocked. I have joined Jody 
in her 
''hobby''. Mitchell Wolf, MD , Chicago, Illinois 

----------------------------------------------------------------- 
--------- 
''Not being the gambling type, it took me several weeks to make 
up my mind to participate in this plan. But conservative that I 
am, I 
decided that the initial investment was so little that there was 
just no 
way that I wouldn't get enough orders to at least get my money 
back''. ''I was surprised when I found my medium size post office 
box crammed 
with orders. I made $319,210.00 in the first 12 weeks. The nice 
thing 
about this deal is that it does not matter where people live. 
There 
simply isn't a better investment with a faster return and so 
big''. 
Dan Sondstrom, Alberta, Canada 
----------------------------------------
If you have any questions of the legality of this program, 
contact the 
Office of Associate Director for Marketing Practices, Federal 
Trade 
Commission, Bureau of Consumer Protection, Washington, DC 

This message is sent in compliance of the proposed bill SECTION 
301. per Section 301, Paragraph (a)(2)(C) of S. 1618. This message is not 
intended for residents in the State of Washington, screening of 
addresses has been done to the best 
of our technical ability. 
****************************************************** 
THIS LETTER CONSTITUTES NO GUARANTEES STATED OR 
IMPLIED. IN THE EVENT THAT IT IS DETERMINED THAT 
THIS LETTER CONSTITUTES A GUARANTEE, IT IS NOW 
VOID. ANY TESTIMONIALS OR AMOUNTS OF EARNINGS 
LISTED IN THIS LETTER MAY BE FACTUAL OR FICTITIOUS. 

This email was sent via Ellipse Bulk Emailer v2.0

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



From daemon@optimus.ietf.org  Tue Jan  8 23:04:35 2002
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 XAA19494
	for <avt-archive@odin.ietf.org>; Tue, 8 Jan 2002 23:04:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA05851
	for avt-archive@odin.ietf.org; Tue, 8 Jan 2002 23:04:36 -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 XAA05828;
	Tue, 8 Jan 2002 23:03:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA05798
	for <avt@optimus.ietf.org>; Tue, 8 Jan 2002 23:03:52 -0500 (EST)
Received: from ns.live.com (ns.live.com [66.80.62.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19488
	for <avt@ietf.org>; Tue, 8 Jan 2002 23:03:50 -0500 (EST)
Received: (from rsf@localhost)
	by ns.live.com (8.9.3/8.9.3) id UAA90255;
	Tue, 8 Jan 2002 20:03:48 -0800 (PST)
	(envelope-from rsf)
Message-Id: <4.3.1.1.20020108195131.00c8be90@localhost>
X-Sender: rsf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 08 Jan 2002 20:00:53 -0800
To: avt@ietf.org
From: Ross Finlayson <finlayson@live.com>
Cc: wmay@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [AVT] Can the 'rtpmap' timestamp frequency override static payload
 type's default frequency?
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

Today I saw the following lines in a session's SDP description:
	m=audio 0 RTP/AVP 14
	a=rtpmap:14 MPA/22050

I.e., the session was using the standard MPEG audio payload format (as 
defined in RFC2250), but with a RTP timestamp frequency of 22050 instead of 
90000.

My question: Is this legal?  Section 4.5.13 of 
<draft-ietf-avt-profile-new-12.txt> states
	4.5.13 MPA
	...
	The RTP timestamp clock rate is always 90000,
	independent of the sampling rate.
which suggests that it's not legal to use a RTP timestamp frequency other 
than 90000 for MPA (and MPV, although <draft-ietf-avt-profile-new-12.txt> 
is less explicit in this case).

If the above SDP is not legal, would it have been any more legal if it had said
	m=audio 0 RTP/AVP 96
	a=rtpmap:96 MPA/22050
i.e., using a dynamic payload type instead of the static payload type (14) 
for MPA?

	Ross.


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



From daemon@optimus.ietf.org  Wed Jan  9 17:19:36 2002
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 RAA17784
	for <avt-archive@odin.ietf.org>; Wed, 9 Jan 2002 17:19:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA22074
	for avt-archive@odin.ietf.org; Wed, 9 Jan 2002 17:19:02 -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 RAA22048;
	Wed, 9 Jan 2002 17:17: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 RAA22017
	for <avt@optimus.ietf.org>; Wed, 9 Jan 2002 17:17:50 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17749
	for <avt@ietf.org>; Wed, 9 Jan 2002 17:17:47 -0500 (EST)
Received: from surfcity.research.att.com (surfcity.research.att.com [135.207.128.5])
	by mail-green.research.att.com (Postfix) with ESMTP
	id ABCFD1E0CD; Wed,  9 Jan 2002 17:17:50 -0500 (EST)
Received: from vtpc3 ([135.207.132.105])
	by surfcity.research.att.com (8.8.7/8.8.7) with SMTP id RAA12952;
	Wed, 9 Jan 2002 17:17:49 -0500 (EST)
Message-ID: <009a01c1995b$d73430c0$6984cf87@vtpc3>
Reply-To: "M. Reha Civanlar" <civanlar@research.att.com>
From: "M. Reha Civanlar" <civanlar@research.att.com>
To: <avt@ietf.org>, "Ross Finlayson" <finlayson@live.com>
Cc: <wmay@cisco.com>
References: <4.3.1.1.20020108195131.00c8be90@localhost>
Subject: Re: [AVT] Can the 'rtpmap' timestamp frequency override static payload type's default frequency?
Date: Wed, 9 Jan 2002 17:20:26 -0500
Organization: AT&T Labs - Research
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Yes, it would have been "more legal" (if there is such a thing :-) if it had
used a dynamic payload type for this purpose. As decided in the London
meeting, I am supposed to update RFC 2250 to explicitly state that "any
clock rate can be specified out-of-band using a dynamic payload type with
the payload formats defined in RFC 2250." Then, it will be "really legal."

----------------------------------------------------------------------------
------
M. Reha Civanlar
Division Manager
Speech & Image Processing Services Research Lab
AT&T Labs - Research
200 Laurel Ave. South, A5 4D04
Middletown, NJ 07748
+1 732 420 9170    Fax: +1 732 368 9456
civanlar@research.att.com
http://www.research.att.com/info/mrc


----- Original Message -----
From: "Ross Finlayson" <finlayson@live.com>
To: <avt@ietf.org>
Cc: <wmay@cisco.com>
Sent: Tuesday, January 08, 2002 11:00 PM
Subject: [AVT] Can the 'rtpmap' timestamp frequency override static payload
type's default frequency?


> Today I saw the following lines in a session's SDP description:
> m=audio 0 RTP/AVP 14
> a=rtpmap:14 MPA/22050
>
> I.e., the session was using the standard MPEG audio payload format (as
> defined in RFC2250), but with a RTP timestamp frequency of 22050 instead
of
> 90000.
>
> My question: Is this legal?  Section 4.5.13 of
> <draft-ietf-avt-profile-new-12.txt> states
> 4.5.13 MPA
> ...
> The RTP timestamp clock rate is always 90000,
> independent of the sampling rate.
> which suggests that it's not legal to use a RTP timestamp frequency other
> than 90000 for MPA (and MPV, although <draft-ietf-avt-profile-new-12.txt>
> is less explicit in this case).
>
> If the above SDP is not legal, would it have been any more legal if it had
said
> m=audio 0 RTP/AVP 96
> a=rtpmap:96 MPA/22050
> i.e., using a dynamic payload type instead of the static payload type (14)
> for MPA?
>
> Ross.
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> http://www1.ietf.org/mailman/listinfo/avt
>


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



From daemon@optimus.ietf.org  Wed Jan  9 19:16:36 2002
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 TAA21666
	for <avt-archive@odin.ietf.org>; Wed, 9 Jan 2002 19:16:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA25436
	for avt-archive@odin.ietf.org; Wed, 9 Jan 2002 19:16:37 -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 TAA25418;
	Wed, 9 Jan 2002 19:15:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA25389
	for <avt@optimus.ietf.org>; Wed, 9 Jan 2002 19:15:48 -0500 (EST)
Received: from mailserver.sylantro.com ([65.200.90.207])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA21636
	for <avt@ietf.org>; Wed, 9 Jan 2002 19:15:46 -0500 (EST)
Received: from 172.16.128.12 by mailserver.sylantro.com with ESMTP (
 Tumbleweed MMS SMTP Relay (MMS v4.7)); Wed, 09 Jan 2002 16:10:55 -0800
X-Server-Uuid: 59490da2-986c-11d3-91ca-00104b9c3900
Received: by mailserver.sylantro.com with Internet Mail Service (
 5.5.2653.19) id <CFPMJS3M>; Wed, 9 Jan 2002 16:10:55 -0800
Message-ID: <79FEAA5FABA7D411BF580001023D1BBD010ED000@mailserver.sylantro.com>
From: "Mohsen Soroush-nejad" <Mohsen.Soroushnejad@sylantro.com>
To: avt@ietf.org
Date: Wed, 9 Jan 2002 16:10:52 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-WSS-ID: 10220385108537-01-01
Content-Type: text/plain; 
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] Interworking between different flavors of G729 coder/decoders?
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
Content-Transfer-Encoding: 7bit

I'm kind of new to this, but how do different flavors of G729 interwork?
I know G729 and G729A coder/decoders work fine.
What about G729A and G729AB? or G729A and G729B?

Is there any guidelines on what works and what doesn't?

Thanks,
MS



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



From daemon@optimus.ietf.org  Thu Jan 10 05:36:53 2002
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 FAA12709
	for <avt-archive@odin.ietf.org>; Thu, 10 Jan 2002 05:36:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA21174
	for avt-archive@odin.ietf.org; Thu, 10 Jan 2002 05:36:55 -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 FAA21144;
	Thu, 10 Jan 2002 05:35:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA21111
	for <avt@optimus.ietf.org>; Thu, 10 Jan 2002 05:35:41 -0500 (EST)
Received: from popmail.space.net (popmail.Space.Net [195.30.0.14])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA12702
	for <avt@ietf.org>; Thu, 10 Jan 2002 05:35:38 -0500 (EST)
Received: (qmail 19564 invoked from network); 10 Jan 2002 10:35:39 -0000
Received: from unknown (HELO wodan) (62.145.29.118)
  by popmail.space.net with SMTP; 10 Jan 2002 10:35:39 -0000
X-SpaceNet-Authentification: SMTPafterPOP verified <Matthias.Hofmann@fgmicrotec.com>
From: "Matthias Hofmann" <Matthias.Hofmann@fgmicrotec.com>
To: "Qiaobing Xie" <xieqb@cig.mot.com>, "AVT WG" <avt@ietf.org>
Cc: "Stephen Casner" <casner@acm.org>
Subject: AW: [AVT] Edited AMR draft for your review
Date: Thu, 10 Jan 2002 11:35:29 +0100
Message-ID: <BOEJLJADHEGBFPONEBFDKEPACAAA.Matthias.Hofmann@fgmicrotec.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3C1D7584.19974704@cig.mot.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

>   - We ask the wg to review the revised draft and provide comments by
>     early next Friday.

Maybe its already too late to get it into the revised draft, but anyway;

In chapter 4.2.2.1. in the third paragraph it says:

    The number of class A bits for various coding
    mode in AMR-WB codec is specified as normative in table 2 in
    [4]. These definitions of class A bits MUST be used for this
    payload format.

A definition for the number of class A bits for the AMR-WB Frame Type 9
SID(namely 40)needs to be added, since table 2 in [4] only covers Frame Type
0-8. table 7 in [4] might be ok as reference.

Matthias

Matthias Hofmann
fg microtec GmbH
Kronstadterstr. 9
81677 Muenchen
Germany
Tel.: +49 89 99269515



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



From daemon@optimus.ietf.org  Thu Jan 10 07:57:43 2002
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 HAA13796
	for <avt-archive@odin.ietf.org>; Thu, 10 Jan 2002 07:57:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA25218
	for avt-archive@odin.ietf.org; Thu, 10 Jan 2002 07:57:45 -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 HAA25195;
	Thu, 10 Jan 2002 07:57:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA25156
	for <avt@optimus.ietf.org>; Thu, 10 Jan 2002 07:56:41 -0500 (EST)
Received: from gwsmtp.thomson-csf.com (gwsmtp.thomson-csf.com [195.101.39.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13789
	for <avt@ietf.org>; Thu, 10 Jan 2002 07:56:36 -0500 (EST)
Received: from thomplex.thomson-csf.com (200.3.2.2) by gwsmtp.thomson-csf.com (NPlex 5.1.053)
        id 3C3CD9A50000FA8D for avt@ietf.org; Thu, 10 Jan 2002 13:53:09 +0100
Received: from thomplex.thomson-csf.com (200.3.2.2) by thomplex.thomson-csf.com (NPlex 5.1.036)
        id 3C39481100074425 for avt@ietf.org; Thu, 10 Jan 2002 13:48:41 +0100
Received: from zethos.thomcast.thomson-csf.com (178.3.2.15) by cnfplex.thomcast.thomson-csf.com (NPlex 5.1.053)
        id 3C39C9E90000247F for avt@ietf.org; Thu, 10 Jan 2002 13:57:53 +0100
Received: from thales-bm.com (178.3.1.55) by zethos.thomcast.thomson-csf.com (NPlex 5.1.036)
        id 3C2C9BB600002149; Thu, 10 Jan 2002 13:54:13 +0100
Message-ID: <3C3D8E40.A598098A@thales-bm.com>
Date: Thu, 10 Jan 2002 13:51:12 +0100
From: Marc Le Naour <marc.lenaour@thales-bm.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: =?iso-8859-1?Q?H=E9l=E8ne?= BLANCHER <hblancher@sii.fr>,
        "=?iso-8859-1?Q?Andr=E9?= Lozac'hmeur" <andre.lozachmeur@free.fr>,
        "avt@ietf.org" <avt@ietf.org>,
        BOUGET Loic FTRD/DIH/REN 
	<loic.bouget@rd.francetelecom.com>,
        =?iso-8859-1?Q?C=E9line?= CLOTEAUX 
	<ccloteaux@sii.fr>,
        cesta <cesta@wanadoo.fr>, Christophe PRIAT 
	<cpriat@sii.fr>,
        "corinne.le-naour@bnpparibas.com" 
	<corinne.le-naour@bnpparibas.com>,
        CURET Dominique FTRD/DMI/REN 
	<dominique.curet@rd.francetelecom.fr>,
        EMERIT Marc FTRD/DIH/LAN 
	<marc.emerit@rd.francetelecom.fr>,
        "G. Theile" <theile@irt.de>, Giorgio 
	Zoia <Giorgio.Zoia@epfl.ch>,
        "herve.gourmelon@trium-rd.com" 
	<herve.gourmelon@trium-rd.com>,
        Jacques FOLLIARD 
	<jacques.folliard@trium-rd.com>,
        jegou f <jegou.f@wanadoo.fr>, Kornelia 
	Geiger <geiger@irt.de>,
        Laurent Florentin <lflorentin@sii.fr>,
        LE MENN 
	<lemenn.gael@wanadoo.fr>,
        MAHIEUX Yannick FTRD/DIH/LAN 
	<yannick.mahieux@rd.francetelecom.com>,
        Marce Nicolas 
	<MARCEN@thmulti.com>,
        Moravie Philippe <MORAVIEP@thmulti.com>,
        Olivier 
	MOREL <o.morel@sofrel.com>,
        RIBEYRON Viviane TDF/CCETT/REN 
	<viviane.ribeyron@rd.francetelecom.com>,
        ROUX Catherine FTRD/DMI/REN 
	<catherine.roux@rd.francetelecom.com>,
        Rudolf Rabenstein 
	<rabe@nt.e-technik.uni-erlangen.de>,
        Sandra Brix <brix@emt.iis.fhg.de>,
        Sarah Dehon <sarah.dehon@waika9.com>,
        Thomas Sporer 
	<spo@emt.iis.fhg.de>,
        "ulrich.horbach@studer.ch" 
	<ulrich.horbach@studer.ch>,
        zze-drm2001 cl balr001 
	<drm2001.balr001@rd.francetelecom.com>,
        Diemer de Vries 
	<diemer@akst.tn.tudelft.nl>
Content-Type: multipart/mixed;
 boundary="------------4C28A566B56BF1C7394C26DE"
Subject: [AVT] Email Change
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

This is a multi-part message in MIME format.
--------------4C28A566B56BF1C7394C26DE
Content-Type: multipart/alternative;
 boundary="------------9DC621069B22E3E0B59568AC"


--------------9DC621069B22E3E0B59568AC
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit

Dear all,

Happy and successful new year to everybody !

Just a mail to inform my old e-mail address
"marc.lenaour@thomcast.thomson-csf.com " is not yet a valid address.
My new e-mail address is "marc.lenaour@thales-bm.com"

Thanks you to take into account this change.

Best Regards,

Marc


--------------9DC621069B22E3E0B59568AC
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7Bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<b><font color="#3333FF">Dear all,</font></b><b><font color="#3333FF"></font></b>
<p><b><font color="#3333FF"><font size=+1>Happy and successful new year
to everybody !</font></font></b><b><font color="#3333FF"></font></b>
<p><b><font color="#3333FF">Just a mail to inform my old e-mail address&nbsp;
"marc.lenaour@thomcast.thomson-csf.com " is not yet a valid address.</font></b>
<br><b><font color="#3333FF">My new e-mail address is "marc.lenaour@thales-bm.com"</font></b><b><font color="#3333FF"></font></b>
<p><b><font color="#3333FF">Thanks you to take into account this change.</font></b><b><font color="#3333FF"></font></b>
<p><b><font color="#3333FF">Best Regards,</font></b><b><font color="#3333FF"></font></b>
<p><b><font color="#3333FF">Marc</font></b>
<br><b><font color="#3366FF"></font></b>&nbsp;</html>

--------------9DC621069B22E3E0B59568AC--

--------------4C28A566B56BF1C7394C26DE
Content-Type: text/x-vcard; charset=us-ascii;
 name="marc.lenaour.vcf"
Content-Description: Card for Marc Le Naour
Content-Disposition: attachment;
 filename="marc.lenaour.vcf"
Content-Transfer-Encoding: 7Bit
Content-Transfer-Encoding: 7Bit
Content-Transfer-Encoding: 7Bit

begin:vcard 
n:Le Naour;Marc
tel;fax:(0)299227931
tel;work:(0)299227963
x-mozilla-html:TRUE
url:www.thales-bm.com
org:Thales Broadcast & Multimedia;Multimedia / Video Streaming Line Product
version:2.1
email;internet:marc.lenaour@thales-bm.com
title:Software & Telecom Engineer
adr;quoted-printable:;;40, rue de Bray  =0D=0A;Cesson-Sévigné;;F-35510  ;France
fn:Marc Le Naour
end:vcard

--------------4C28A566B56BF1C7394C26DE--


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



From daemon@optimus.ietf.org  Thu Jan 10 11:27:10 2002
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 LAA18019
	for <avt-archive@odin.ietf.org>; Thu, 10 Jan 2002 11:27:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA02902
	for avt-archive@odin.ietf.org; Thu, 10 Jan 2002 11:27:12 -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 LAA02784;
	Thu, 10 Jan 2002 11:25:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA02757
	for <avt@optimus.ietf.org>; Thu, 10 Jan 2002 11:25:30 -0500 (EST)
Received: from leo.it.comsat.com (leo.it.comsat.com [134.133.253.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17974
	for <avt@ietf.org>; Thu, 10 Jan 2002 11:25:27 -0500 (EST)
Received: from rootvs1.corplan.net (rootvs1.corplan.net [134.133.230.35])
	by leo.it.comsat.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0AGOxA24984
	for <avt@ietf.org>; Thu, 10 Jan 2002 11:24:59 -0500 (EST)
Received: from rootvs1.corplan.net ([134.133.230.35]) by rootvs1.corplan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id ZLF76CBJ; Thu, 10 Jan 2002 11:24:59 -0500
Received: FROM rootexchange.corplan.net BY rootvs1.corplan.net ; Thu Jan 10 11:24:58 2002 -0500
Received: from labs.comsat.com ([134.133.10.103]) by rootexchange.corplan.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 10 Jan 2002 11:24:54 -0500
Message-ID: <3C3DC056.A52412B6@labs.comsat.com>
Date: Thu, 10 Jan 2002 11:24:54 -0500
From: =?iso-8859-1?Q?Sim=E3o?= Campos-Neto <simao.campos@labs.comsat.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>
CC: avt@ietf.org
Subject: Re: [AVT] Interworking between different flavors of G729 coder/decoders?
References: <79FEAA5FABA7D411BF580001023D1BBD010ED000@mailserver.sylantro.com>
Content-Type: multipart/mixed;
 boundary="------------C96F58B9AB585DE90BBB2AF2"
X-OriginalArrivalTime: 10 Jan 2002 16:24:54.0793 (UTC) FILETIME=[565A0F90:01C199F3]
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

This is a multi-part message in MIME format.
--------------C96F58B9AB585DE90BBB2AF2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Mohsen,

As you mentioned, G.729 'main body' ("G.729") and G.729 Annex A
("G.729A") work fine because they share the same bitstream (and operate
at 8 kbit/s). The difference between them is that G.729 has higher
complexity and better quality and G.729A is a simplification of G.729,
yelding lower complexity at a slightly reduced quality. In some
conditions, however, performance would be imperceptible, while in others
it would be noticeable. 

G.729 Annex B defines the silence removal optimized for the G.729
algorithm, so it uses a different payload than the G.729/G.729A 'mode'. 

G.729 also has other operating bit rates ('modes'). One is at 6.4 kbit/s
(G.729 Annex D) and the other is at 11.8 kbit/s (G.729 Annex E). If
silence removal at these rates is intended, then the mechanism in G.729
Annexes F and G, respectively for 6.4 and 11.8 kbit/s, should be used.
The silence removal payload is the same as for Annex B, the difference
resides in the algorithm to calculate the parameters that go into the
payload.

Maybe the least confusing way to view G.729 is to think of it as having
4 operating modes: 6.4, 8, and 11.8 kbit/s; and the silence removal (aka
VAD/CNI) mode. (please note, again, that eventhough the treatment of the
signal to arrive at the 8 kbit/s bitstream is different inside the G.729
and G.729A, the bits seen on the wire are indistinguishable). So RTP
needs to be concerned with 4 payload types for the whole G.729 standard:
G729-6.4, G729, G729-12.2, and G729-SID (the VAD/CNI mode one).

In terms of interoperability, for the 'G729B' (I presume, G.729 plus
VAD/CNI operation) and 'G729AB' (I presume, G.729A plus VAD/CNI
operation), there is no interoperability problem because the 8 kbit/s
bitstream is understood the same by G.729 and G.729A, and both ends
support the VAD/CNi operation of G.728 Annex B.

Let's take the example of one end operating in "G729A" [1] mode and
another end operating "G729AB" [2]; the continuous stream from [1] to
[2] will work OK, but the discontinuous stream from [2] to [1] (since
silence removal will be in operation), plus some "unrecognized" packets
(the SID packets -- which would be discarded), would be seen as lost /
misdelivered packets by the decoder at [1]. I presume that the
connection will still work, but the quality will be greatly impacted, in
particular around the voiced/unvoiced (ie silence/non-silence)
transitions. Similar problem will happen for [1] as 'G729A' and [2] as
'G729B'.

I hope this clarification helps.

Simão Campos-Neto
--
Mohsen Soroush-nejad wrote:
> 
> I'm kind of new to this, but how do different flavors of G729 interwork?
> I know G729 and G729A coder/decoders work fine.
> What about G729A and G729AB? or G729A and G729B?
> 
> Is there any guidelines on what works and what doesn't?
> 
> Thanks,
> MS
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> http://www1.ietf.org/mailman/listinfo/avt

-- 
========================================================================
Simão Ferraz de Campos Neto, Scientist *All comments strictly my own*
LMGT/COMSAT                            Tel:    +1-301-428-4516
22300 Comsat Drive                     Fax:    +1-301-428-9287
Clarksburg MD 20871 - USA           E-mail: simao.campos@labs.comsat.com
========================================================================
  ****** Practice random kindness and senseless acts of beauty ******
========================================================================
--------------C96F58B9AB585DE90BBB2AF2
Content-Type: text/x-vcard; charset=us-ascii;
 name="simao.campos.vcf"
Content-Description: Card for Simão Campos-Neto
Content-Disposition: attachment;
 filename="simao.campos.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Campos-Neto;Simão
tel;fax:+1-301-428-9287
tel;work:+1-301-428-4516
x-mozilla-html:FALSE
url:www.lmgt.com
org:LMGT;Voice Codec Evaluation
adr:;;22300 Comsat Drive;Clarksburg;Md;20871;USA
version:2.1
email;internet:simao.campos@labs.comsat.com
title:Scientist
note;quoted-printable:Vice-Chairman ITU-T SG 16 (Multimedia Systems)=0D=0AChairman WP 3/16 (Media Coding)
fn:Simão Campos-Neto
end:vcard

--------------C96F58B9AB585DE90BBB2AF2--


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



From daemon@optimus.ietf.org  Thu Jan 10 11:41:07 2002
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 LAA18552
	for <avt-archive@odin.ietf.org>; Thu, 10 Jan 2002 11:41:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA03878
	for avt-archive@odin.ietf.org; Thu, 10 Jan 2002 11:41:09 -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 LAA03837;
	Thu, 10 Jan 2002 11:40:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03806
	for <avt@optimus.ietf.org>; Thu, 10 Jan 2002 11:40:23 -0500 (EST)
Received: from leo.it.comsat.com (leo.it.comsat.com [134.133.253.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18534
	for <avt@ietf.org>; Thu, 10 Jan 2002 11:40:21 -0500 (EST)
Received: from rootvs1.corplan.net (rootvs1.corplan.net [134.133.230.35])
	by leo.it.comsat.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0AGdqA25348
	for <avt@ietf.org>; Thu, 10 Jan 2002 11:39:52 -0500 (EST)
Received: from rootvs1.corplan.net ([134.133.230.35]) by rootvs1.corplan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id ZLF76CHH; Thu, 10 Jan 2002 11:39:53 -0500
Received: FROM rootexchange.corplan.net BY rootvs1.corplan.net ; Thu Jan 10 11:39:52 2002 -0500
Received: from labs.comsat.com ([134.133.10.103]) by rootexchange.corplan.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 10 Jan 2002 11:39:52 -0500
Message-ID: <3C3DC3D7.8EC588A9@labs.comsat.com>
Date: Thu, 10 Jan 2002 11:39:51 -0500
From: =?iso-8859-1?Q?Sim=E3o?= Campos-Neto <simao.campos@labs.comsat.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>, avt@ietf.org
Subject: Re: [AVT] Interworking between different flavors of G729 coder/decoders?
References: <79FEAA5FABA7D411BF580001023D1BBD010ED000@mailserver.sylantro.com> <3C3DC056.A52412B6@labs.comsat.com>
Content-Type: multipart/mixed;
 boundary="------------E4754F4E5B228AAA1F730EF9"
X-OriginalArrivalTime: 10 Jan 2002 16:39:52.0184 (UTC) FILETIME=[6D3D0F80:01C199F5]
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

This is a multi-part message in MIME format.
--------------E4754F4E5B228AAA1F730EF9
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Sorry, I meant "G.729 Annex B", not "G.728 Annex B".

Simão Campos-Neto wrote:
> 
> Mohsen,
> ...
> support the VAD/CNi operation of G.728 Annex B.
                                   ^^^^^^^^^^^^^^
> ...
--------------E4754F4E5B228AAA1F730EF9
Content-Type: text/x-vcard; charset=us-ascii;
 name="simao.campos.vcf"
Content-Description: Card for Simão Campos-Neto
Content-Disposition: attachment;
 filename="simao.campos.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Campos-Neto;Simão
tel;fax:+1-301-428-9287
tel;work:+1-301-428-4516
x-mozilla-html:FALSE
url:www.lmgt.com
org:LMGT;Voice Codec Evaluation
adr:;;22300 Comsat Drive;Clarksburg;Md;20871;USA
version:2.1
email;internet:simao.campos@labs.comsat.com
title:Scientist
note;quoted-printable:Vice-Chairman ITU-T SG 16 (Multimedia Systems)=0D=0AChairman WP 3/16 (Media Coding)
fn:Simão Campos-Neto
end:vcard

--------------E4754F4E5B228AAA1F730EF9--


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



From daemon@optimus.ietf.org  Sat Jan 12 11:19:11 2002
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 LAA21744
	for <avt-archive@odin.ietf.org>; Sat, 12 Jan 2002 11:19:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20768
	for avt-archive@odin.ietf.org; Sat, 12 Jan 2002 11:19:14 -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 LAA20746;
	Sat, 12 Jan 2002 11:17:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20720
	for <avt@optimus.ietf.org>; Sat, 12 Jan 2002 11:17:09 -0500 (EST)
Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21725
	for <avt@ietf.org>; Sat, 12 Jan 2002 11:17:05 -0500 (EST)
Received: from [195.20.224.209] (helo=mrvdom02.kundenserver.de)
	by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2)
	id 16PQq3-0004Kb-00
	for avt@ietf.org; Sat, 12 Jan 2002 17:16:59 +0100
Received: from [213.7.219.98] (helo=fortress)
	by mrvdom02.kundenserver.de with smtp (Exim 2.12 #2)
	id 16PQq3-0000XA-00
	for avt@ietf.org; Sat, 12 Jan 2002 17:16:59 +0100
From: =?iso-8859-1?Q?Andre_Fl=F6per?= <andre@floeper.de>
To: <avt@ietf.org>
Date: Sat, 12 Jan 2002 17:15:59 +0100
Message-ID: <IBEEKJIPPOGMDFAALLPHCEHNCAAA.andre@floeper.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
Subject: [AVT] Comments on draft-ietf-avt-srtp-02.txt
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
Content-Transfer-Encoding: 8bit

Hi,

I have a question about the TMMH/16 used for message authentication.

Only transformation of message is described to calculate the tag words, but
what´s about the iteration process to iterate the transformed blocks if you
have messages greater than KEY_LENGTH - TAG_LENGTH like RTP or RTCP packets?


Best regards,

Andre


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



From daemon@optimus.ietf.org  Mon Jan 14 09:38:36 2002
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 JAA03173
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 09:38:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA09000
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 09:38:37 -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 JAA08901;
	Mon, 14 Jan 2002 09:34:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08869
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 09:34:05 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03138
	for <avt@ietf.org>; Mon, 14 Jan 2002 09:34:02 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0EEY3J10608
	for <avt@ietf.org>; Mon, 14 Jan 2002 15:34:03 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Mon Jan 14 15:33:37 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HXH00T>; Mon, 14 Jan 2002 15:33:37 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D83EF65@Esealnt877.al.sw.ericsson.se>
From: "Elisabetta Carrara (ERA)" <Elisabetta.Carrara@era.ericsson.se>
To: avt@ietf.org
Cc: =?iso-8859-1?Q?=27Andre_Fl=F6per=27?= <andre@floeper.de>
Subject: RE: [AVT] Comments on draft-ietf-avt-srtp-02.txt
Date: Mon, 14 Jan 2002 15:33:28 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA08870
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
Content-Transfer-Encoding: 8bit

Hi
thanks a lot for pointing it out, the draft is incomplete there. 
We need to add that the right number of key bits for the 
authentication key has to be supplied from the key derivation
(applied to the default 128-bit master key), thus the key 
derivation has to expand to the desired key length.
We will clarify it.

Regards
/E

> -----Original Message-----
> From: Andre Flöper [mailto:andre@floeper.de]
> Sent: den 12 januari 2002 17:16
> To: avt@ietf.org
> Subject: [AVT] Comments on draft-ietf-avt-srtp-02.txt
> 
> 
> Hi,
> 
> I have a question about the TMMH/16 used for message authentication.
> 
> Only transformation of message is described to calculate the 
> tag words, but
> what´s about the iteration process to iterate the transformed 
> blocks if you
> have messages greater than KEY_LENGTH - TAG_LENGTH like RTP 
> or RTCP packets?
> 
> 
> Best regards,
> 
> Andre
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> http://www1.ietf.org/mailman/listinfo/avt
> 

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



From daemon@optimus.ietf.org  Mon Jan 14 11:05:37 2002
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 LAA05137
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 11:05:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA12183
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 11:05:40 -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 KAA11604;
	Mon, 14 Jan 2002 10:59:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11575
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 10:59:38 -0500 (EST)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04977
	for <avt@ietf.org>; Mon, 14 Jan 2002 10:59:35 -0500 (EST)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-32 #42257)
 id <0GPX00I01R2JT6@firewall.wcom.com> for avt@ietf.org; Mon,
 14 Jan 2002 15:59:07 +0000 (GMT)
Received: from pmismtp01.wcomnet.com ([166.38.62.36])
 by firewall.wcom.com (PMDF V5.2-32 #42257)
 with ESMTP id <0GPX00HECR2IM7@firewall.wcom.com> for avt@ietf.org; Mon,
 14 Jan 2002 15:59:07 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com
 (PMDF V5.2-33 #42258) with SMTP id <0GPX00101R2GO4@pmismtp01.wcomnet.com> for
 avt@ietf.org; Mon, 14 Jan 2002 15:59:06 +0000 (GMT)
Received: from skanchina ([166.35.144.87])
 by pmismtp01.wcomnet.com (PMDF V5.2-33 #42258)
 with SMTP id <0GPX0011NR1MA9@pmismtp01.wcomnet.com> for avt@ietf.org; Mon,
 14 Jan 2002 15:58:34 +0000 (GMT)
Date: Mon, 14 Jan 2002 10:11:51 -0600
From: Sharma Kanchinadham <sharma.kanchinadham@wcom.com>
To: avt@ietf.org
Reply-to: sharma.kanchinadham@wcom.com
Message-id: <000401c19d16$2d5ee680$579023a6@wcomnet.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Subject: [AVT] Regarding G.729
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
Content-Transfer-Encoding: 7bit

simao wrote :

>Maybe the least confusing way to view G.729 is to think of it as having 4
operating modes:
>6.4, 8, and 11.8 kbit/s; and the silence removal (aka VAD/CNI) mode.
(please note,
>>again, that eventhough the treatment of the signal to arrive at the 8
kbit/s bitstream is
 >different inside the G.729 and G.729A, the bits seen on the wire are
indistinguishable). So
>RTP needs to be concerned with 4 payload types for the whole G.729
standard: G729-6.4,
> G729, G729-12.2, and G729-SID (the VAD/CNI mode one).

I believe there is no seperate payload type for G.729-SID. Please see the
following draft


http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-mime-06.txt

The VAD/Silence suppression is negotiated using the "annexb" parameter.
Absence of this parameter or ommission of the a line means "YES".

Please let me know if i am missing anything.





Thanks ,
Sharma Kanchinadham
Worldcom


====================================================================


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



From daemon@optimus.ietf.org  Mon Jan 14 12:23:43 2002
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 MAA08060
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 12:23:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA15375
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 12:23:46 -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 MAA15316;
	Mon, 14 Jan 2002 12:22:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15291
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 12:22:38 -0500 (EST)
Received: from leo.it.comsat.com (leo.it.comsat.com [134.133.253.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07988
	for <avt@ietf.org>; Mon, 14 Jan 2002 12:22:31 -0500 (EST)
Received: from rootvs1.corplan.net (rootvs1.corplan.net [134.133.230.35])
	by leo.it.comsat.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0EHM1A09118
	for <avt@ietf.org>; Mon, 14 Jan 2002 12:22:01 -0500 (EST)
Received: from rootvs1.corplan.net ([134.133.230.35]) by rootvs1.corplan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id ZLF767DA; Mon, 14 Jan 2002 12:22:03 -0500
Received: FROM rootexchange.corplan.net BY rootvs1.corplan.net ; Mon Jan 14 12:22:03 2002 -0500
Received: from labs.comsat.com ([134.133.10.103]) by rootexchange.corplan.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 14 Jan 2002 12:22:03 -0500
Message-ID: <3C431375.E884CFED@labs.comsat.com>
Date: Mon, 14 Jan 2002 12:20:53 -0500
From: =?iso-8859-1?Q?Sim=E3o?= Campos-Neto <simao.campos@labs.comsat.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sharma.kanchinadham@wcom.com
CC: avt@ietf.org
Subject: Re: [AVT] Regarding G.729
References: <000401c19d16$2d5ee680$579023a6@wcomnet.com>
Content-Type: multipart/mixed;
 boundary="------------7F973BA5E460CD163B074A94"
X-OriginalArrivalTime: 14 Jan 2002 17:22:03.0574 (UTC) FILETIME=[FBB78560:01C19D1F]
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

This is a multi-part message in MIME format.
--------------7F973BA5E460CD163B074A94
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Thanks, Sharma,

Sorry, I was a bit loose on my terminology. What I had in mind were
Figures 4,5,6,7 and 8 in
 http://www.ietf.org/internet-drafts/draft-ietf-avt-profile-new-12.txt

Annex B bit packing in Fig 5 is effectively a different payload from
Fig.4, although accomodated within the same general G729 payload type.
G.729D and E are different ones, which should also have an Annex B-type
of parameter (Specifics in G.729 Annex F and G, actually, but defined as
'annexb' in the MIME registration draft since the VAD/DTX bit packing is
the same for 6.4, 8, and 11.8 kbit/s). I am not sure how the receiver is
supposed to know when the bits in the G729 packet (for a "G729B"- or
"G729AB"-type communication) are according to Figure 4 or Figure 5,
since this will dynamically change over the course of the communication.
I guess that the receiver will infer the payload type from the packet
size and signal that to the speech decoder.

Simão.
--
Sharma Kanchinadham wrote:
> 
> simao wrote :
> 
>> Maybe the least confusing way to view G.729 is to think of it as having 4 operating modes:
>> 6.4, 8, and 11.8 kbit/s; and the silence removal (aka VAD/CNI) mode. (please note,
>> again, that eventhough the treatment of the signal to arrive at the 8 kbit/s bitstream is
>> different inside the G.729 and G.729A, the bits seen on the wire are indistinguishable). So
>> RTP needs to be concerned with 4 payload types for the whole G.729 standard: G729-6.4,
>> G729, G729-12.2, and G729-SID (the VAD/CNI mode one).
> 
> I believe there is no seperate payload type for G.729-SID. Please see the
> following draft
> 
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-mime-06.txt
> 
> The VAD/Silence suppression is negotiated using the "annexb" parameter.
> Absence of this parameter or ommission of the a line means "YES".
> 
> Please let me know if i am missing anything.
> 
> Thanks ,
> Sharma Kanchinadham
> Worldcom

-- 
========================================================================
Simão Ferraz de Campos Neto, Scientist *All comments strictly my own*
LMGT/COMSAT                            Tel:    +1-301-428-4516
22300 Comsat Drive                     Fax:    +1-301-428-9287
Clarksburg MD 20871 - USA           E-mail: simao.campos@labs.comsat.com
========================================================================
  ****** Practice random kindness and senseless acts of beauty ******
========================================================================
--------------7F973BA5E460CD163B074A94
Content-Type: text/x-vcard; charset=us-ascii;
 name="simao.campos.vcf"
Content-Description: Card for Simão Campos-Neto
Content-Disposition: attachment;
 filename="simao.campos.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Campos-Neto;Simão
tel;fax:+1-301-428-9287
tel;work:+1-301-428-4516
x-mozilla-html:FALSE
url:www.lmgt.com
org:LMGT;Voice Codec Evaluation
adr:;;22300 Comsat Drive;Clarksburg;Md;20871;USA
version:2.1
email;internet:simao.campos@labs.comsat.com
title:Scientist
note;quoted-printable:Vice-Chairman ITU-T SG 16 (Multimedia Systems)=0D=0AChairman WP 3/16 (Media Coding)
fn:Simão Campos-Neto
end:vcard

--------------7F973BA5E460CD163B074A94--


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



From daemon@optimus.ietf.org  Mon Jan 14 14:06:07 2002
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 OAA13334
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 14:06:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA20434
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 14:06:08 -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 OAA20404;
	Mon, 14 Jan 2002 14:05:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20373
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 14:05:18 -0500 (EST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13264
	for <avt@ietf.org>; Mon, 14 Jan 2002 14:05:15 -0500 (EST)
Received: from [209.178.148.205] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 1225710; Mon, 14 Jan 2002 14:05:14 -0500
From: "Marshall Eubanks" <tme@multicasttech.com>
To: avt@ietf.org
Cc: msec@securemulticast.org, Toerless Eckert <eckert@cisco.com>
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Mon, 14 Jan 2002 14:05:14 -0500
Message-ID: <web-1225710@multicasttech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [AVT] Unicast RTCP back traffic
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
Content-Transfer-Encoding: 8bit

Hello;

Here is a first cut at the security implications and
a possible fix for 
unicast back traffic for SSM type RTCP. This is obviously
an AVT issue, I am sending it to MSEC as well.

This is also available as a pdf on 
http://www.multicasttech.com/papers/unicast_rtcp_analysis.pdf

Regards
Marshall Eubanks
tme@multicasttech.com
---------------------------------

To 	: AVT, MSEC
From 	: T.M. Eubanks
Subject	: Security of Unicast Back Traffic in RTCP
Date	: January 14, 2002

In the standard Any Source Multicast (ASM) model for the
Real Time Control Protocol (RTCP), the ?back traffic? (the
Receiver Reports, or RR?s, the Sender Reports, or SR?s, and
possibly other user defined auxiliary data, all currently
issued by a receiver as part of RTCP) is sent to the source
and all receivers on a multicast group, with the back
traffic bandwidth being  set to a fraction of the total
bandwidth, as determined at each receiver. This model must
change to support Single Source Multicast (SSM), and there
may be ASM or even unicast applications where SSM-like RTCP
back traffic would be desirable [Chesterfield and Ott,
2001].

In the existing ASM RTCP back traffic model, data are
multicast onto a group listened to by the source or sources
and all receivers. For a network that only implements SSM,
this is not possible, and it may not be desirable even for
an ASM enabled network, as SSM only protocols should not
depend on the existence of ASM network capabilities. An
obvious modification of the ASM RTCP model to handle this
situation is to unicast RR and other back traffic to the
source, and then optionally to multicast the data (either in
the form of RR?s, or as summary digests) to the receivers on
a separate SSM group. In many cases, it would be convenient
to separate the functions of the SSM source and the SSM RTCP
server, and thus to send the unicast RTCP back traffic to an
arbitrary Internet address. I will call the general case of
unicast back traffic to an arbitrary location ?SSM-like?
back traffic.

The Problem

The existence of unicast SSM-like back traffic presents a
possibly serious security problem. If any receiver were to
source an arbitrarily high rate of back traffic, then local
resources could be overwhelmed. In addition, if every
receiver were to source an arbitrarily high rate of back
traffic, then the SSM RTCP report server could be
overwhelmed. Even if receiver back traffic were limited to a
low level for each receiver (say by specifying a limit to
the rate of receiver back traffic), then it will still be
possible to create problems by directing the back traffic to
a different IP address. In fact, a large flow of SSM like
RTCP back traffic would constitute a pre-made Distributed
Denial of Service (DDOS) attack if the traffic could be
redirected by an attacker. This attack is called ?packet
bombing? in Chesterfield and Ott [2001]. 

For this security analysis, I assume that the attacker can
spoof IP addresses and insert traffic in such a fashion that
Reverse Path Forwarding (RPF) and other possible checks of
the integrity of the IP routing are passed. (These checks
are an important line of defense, but they cannot be the
only defense as they can be compromised almost trivially in
certain situations, for example for a multicast source on a
large LAN with an exploited host.) I also assume that the
attacker can become a legitimate member of the group, and
thus has access to any keys or other cryptographic
information available to group members. This of course makes
the authentication problem much harder. For example, it
means that simple symmetric key encryption of the RTCP
traffic, or even of the underlying RTP traffic, as is
suggested in Chesterfield and Ott [2001], will not improve
the security of the SSM-like back traffic, as it must be
assumed that the attacker will possess the keys. 

I will assume that the basic means of authentication of back
traffic direction will be through cryptographic hash
functions, such as MD-5 or SHA-1, coupled with public-key
cryptography. These functions are described in detail in
Schneier [1996]. 

In Chesterfield and Ott [2001], the basic means of
protecting against using the back traffic for denial of
service attacks is to only send back traffic to the source,
and to verify the source by verifying the Session
Description Protocol (SDP) message announcing the source.
There are several objections to this procedure :

1.) The source may not be the appropriate place to deal with
the back traffic. The source may not even be reachable by
unicast from the receivers, as is the case with certain
means of distributing IP data by satellite. Conversely,
there may be multiple sources and it may be desirable to
squelch the back traffic to most of the sources, while still
sending it to others.

2.)  This does not solve the security problem. I may be able
to perform a denial of service on the source by spoofing the
control traffic coming from the source, even if the source
was originally authenticated. (For example, I could increase
the amount of back traffic to a point beyond the capacity of
the source to handle.)

This is recognized by Chesterfield and Ott [2001], who state
as requirements that

      - The information providing the unicast feedback
address
      needs to be authenticated as being from a trusted
source. 
		
      - Data integrity of the RTCP traffic from the source,
particularly
      RSI + LJS packets is also required.

but without stating the means for achieving this. 

CISCO?s IPTV currently sends back unicast RTCP traffic back
upon request. A new APP packet is defined and reports can
only be sent to the source. This packet is protected against
change by signing it with an MD5 hash [Toerless Eckert,
personal communication]. Since every receiver presumably has
access to the shared secret, it is hard to see how this
protocol can stop spoofing of the APP messages, independent
of the cryptographic weakness of the MD5 hash.

Of course, there may be multicast applications where there
is tight communication between sources and receivers, such
that each receiver could have a unique shared secret. This
is not an adequate solution, however, in the context of the
current multicast service model.
Another solution (suggested by Bill Fenner) is to include
the back traffic information in the SDP file, which could
then be subject to authentication. The problem I see with
this is that it makes it impossible to change the back
traffic model once it is set up (many applications/users
store SDP information for long periods of time) and it also
complicates the SDP model. SDP information can be sent now
by SAP, by http or by e-mail. Only http could easily be
changed at present to support the new authentication.

A Protocol for Authenticating Back Traffic Requests

In my opinion, authentication of back traffic requests
requires more infrastructure than is available in
Chesterfield and Ott [2001]. Here, I set forth what I see is
one means of performing this authentication.

The new protocol involves getting a public key for the
source, presumably from a Certificate Authority (related
sources could share private keys and announce the same
public one). (The SDP protocol could be amended to
optionally request this.) A new RTCP message, the Report
Direction Message (RDM), is required.

Then

1.) The source sends RDM?s containing 

	the IP address for the source traffic
	the IP address for the back traffic 
the group (or SSM channel) address
	the desired bandwidth for the traffic (the receiver
bandwidth of Chesterfield and Ott) and
the timestamp of the RDM 

2.) The RDM is signed with a cryptographic hash covering all
of the items in # 1 above. 

3.) The cryptographic hash is encrypted with the private key
of the source. The corresponding public key could be found,
e.g. from a Certificate Authority for the source.
This signature, plus the cryptographic hash, is included in
the RDM and multicast to the group.

4.) The RDM is optionally encrypted.

5.) The RDM is sent to the group members as part of  the
RTCP traffic from the sender.

6.) Each receiver verifies the RDM and uses it to direct the
flow of its RTCP back traffic. This includes decryption if
necessary, verifying that the cryptographic hash is correct,
decryption of the RDM signature using the public key of the
source, verifying that the IP address of the source matches
the IP address of the incoming SSM RTP traffic, verifying
that the correct group address is present, and the timestamp
is in the recent past.

In many situations RDM?s need not change for long periods of
time. In that case, the RDM may be verified by simply
checking the cryptographic hash. If the RDM does not change
the direction or the rate of the back traffic, there is no
reason to authenticate it further.

7.) Optionally, the receiver uses information from the
received RDM to provide integrity checks in its back
traffic. The most secure version of this would be to hash
the return RR with some information being sent directly on
the multicast group, which would verify that the receiver
was actually receiving the multicast data.

Also, there needs to be an upper limit to the amount of RTCP
traffic a receiver may source, of order 1 message per
second, as there is no reason to allow an arbitrarily large
amount of back traffic from any specific receiver.

Possible attacks on this protocol include :

1.) The conflict attack. If I can take a valid RPM message
from the source, modify information (say the IP address of
the RTCP server) and then find a variant of the compromised
message that has the same cryptographic hash as the original
RPM message, then the receiver has no way of knowing that
the message has been corrupted, as this message will give
the same public key signature as the original. This is why
it is necessary to digitally sign the RDM message, as
otherwise the attacker could simply modify the RDM as
desired, and generate a new cryptographic hash for the new
message.

It is reasonable to assume that MD5 is subject to conflict
attacks [Dobbertin, 1996], which is presumably why the IESG
has ruled its use out for new protocols. It is often stated
that the keyed HMAC-MD5 extension of MD5 [RFC2403, 1998] is
still secure. However, this is clearly not the case for this
protocol. The additional security for HMAC-MD5 comes from
the use of a key. Since, in this case, the attacker must be
presumed to know the key (which must be shared with the
entire multicast group), the HMAC-MD5 hash could be
compromised in roughly the same time as an unprotected MD5
hash.

2.) The birthday attack. This is not much of a worry. The
SHA-1 algorithm produces a 160 bit hash function. The number
of messages from the same authority that would have to be
searched to have a 50% chance of finding a pair of messages
producing the same hash function is thus about 2^80. If
there were 1 Giga-RPM messages produced per second from one
authority,
it would take 38 million years to find such a pair.

3.) The replay attack. If I capture a valid RDM message, I
can replay it. The utility of this is limited by including
the group and source address in the RDM hash (this makes it
impossible to send the traffic from a very populated group
to the SSM RTCP server for a much lower bandwidth group). If
a (S,G) is being reused by a sloppy source, an attack would
be possible by reusing a RDM from a high bandwidth
application for a lower bandwidth one. The best way to
prevent this would be to include a timestamp, and only allow
RDM?s to be valid for a limit period (say 180 seconds).

Conclusions


I see no way to authenticate RDM type information for large
public SSM sessions without using public key cryptography.
This is much slower than symmetric key cryptography, which
may be a problem for this protocol. On the other hand, it is
only necessary to protect an RDM for the duration of its
validity, and one key verification per minute (which can be
done entirely at the receiver once the public key for the
source is obtained) does not sound especially onerous. This
rate can be kept even lower if, as is reasonable for many
applications, the contents of the RDM message are not
changed for long periods of time.

One specific conclusion I reached is that HMAC-MD5 for this
application is to be avoided. I recommend that SHA-1 be used
instead.

This protocol imposes a fair amount of extra complexity into
the SSM service model. The response of some application
developers may be not to make use of back traffic
authentication. In that case, a reasonable question is
whether multicast is better served by simply not sending any
RTCP back traffic at all, or whether RTCP should include a
low bandwidth default for back traffic information to the
source (under the assumption that extremely large groups
could afford to pay for the extra complexity of
authentication if the back traffic bandwidth became
problematic). If the default were to unicast one message to
the source every 50 seconds in the absence of valid
authentication, then (assuming that the message were 500
bytes), then it would take 700 group members to saturate a
dial-up connection, and several thousand to saturate a
typical DSL connection. Whether this is a reasonable risk is
open to debate.


References

[Dobbertin, 1996] The Status of MD5 after a Recent Attack,
Hans Dobbbertin, CryptoBytes, Vol. 2, 1-5, 1996.

[Chesterfield and Ott, 2001] RTCP Extension for Single
Source Multicast Sessions with  Unicast RTCP feedback,
Julian Chesterfield and Joerg Ott,
draft-chesterfield-avt-rtcpssm-02.txt, 2001.

[RFC2104, 1997] HMAC: Keyed-Hashing for Message
Authentication, H. Krawczyk,  M. Bellare, and R. Canetti,
IETF Request for Comments: 2104, 1997.

[RFC2403, 1998] The Use of HMAC-MD5-96 within ESP and AH,
C. Madson and R. Glenn, IETF Request for Comments: 2403,
1998.

[Schneier, 1996] Applied Cryptography, Bruce Schneier, J.
Wiley, 1996.

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



From daemon@optimus.ietf.org  Mon Jan 14 14:13:58 2002
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 OAA13617
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 14:13:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA20633
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 14:14:00 -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 OAA20609;
	Mon, 14 Jan 2002 14:13:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20578
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 14:13:21 -0500 (EST)
Received: from linkexpress.com.br ([200.252.169.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13599
	for <avt@ietf.org>; Mon, 14 Jan 2002 14:13:13 -0500 (EST)
From: 6unidiploma@msn.com
Received: from riedel.com.br (UnUSED.linkexpress.com.br [200.252.170.131] (may be forged))
	by linkexpress.com.br (8.11.2/8.11.2) with ESMTP id g0EJ11Q23516;
	Mon, 14 Jan 2002 17:01:02 -0200
Received: from PROCESSO/CORREIO by riedel.com.br (Mercury 1.21);
    14 Jan 100 15:59:45 -0300
Received: from CORREIO by PROCESSO (Mercury 1.21); 14 Jan 100 05:06:51 -0300
Received: from 61.68.97.100 by riedel.com.br (Mercury 1.21);
    14 Jan 100 05:06:43 -0300
To: <avt@coastalnet.com>
Cc: <avt@blast.net>, <avt@nationwide.net>, <avt@liberty.com>, <avt@gmu.edu>,
        <avt@mindspring.com>, <avt@llc.net>, <avt@alltel.net>, <avt@mho.net>,
        <avt@mail.ru>, <avt@mindless.com>, <avt@ietf.org>, <avt@goldstate.net>,
        <avt@bol.net.in>, <avt@kih.net>, <avt@lycos.com>, <avt@cac.net>,
        <avt@net56.net>, <avt@ndnet.net>, <avt@cnshb.ru>, <avt@cari.net>,
        <avt@earthlink.com>, <avt@majorisp.net>, <avt@irk.ru>,
        <avt@alaska.net>, <avt@home.net>
Date: Mon, 14 Jan 2002 18:48:01 -0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Reply-To: 6unidiploma@msn.com
Message-ID: <66DD793271F@riedel.com.br>
Content-Transfer-Encoding: 7bit
Subject: [AVT] GET YOUR UNIVERSITY DIPLOMA!!!                         14171
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
Content-Transfer-Encoding: 7bit

U N I V E R S I T Y    D I P L O M A S

Obtain a prosperous future, money earning power,
and the admiration of all.

Diplomas from prestigious non-accredited
universities based on your present knowledge
and life experience.

No required tests, classes, books, or interviews.

Bachelors, masters, MBA, and doctorate (PhD)
diplomas available in the field of your choice.

No one is turned down.

Confidentiality assured.

CALL NOW to receive your diploma
within days!!!

1 - 312 - 803 - 1921


Call 24 hours a day, 7 days a week, including
Sundays and holidays.



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



From daemon@optimus.ietf.org  Mon Jan 14 16:06:31 2002
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 QAA19122
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 16:06:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA25239
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 16:06:25 -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 QAA25166;
	Mon, 14 Jan 2002 16:05:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA25070
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 16:05:30 -0500 (EST)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19082
	for <avt@ietf.org>; Mon, 14 Jan 2002 16:05:26 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 57BC94CE60; Mon, 14 Jan 2002 16:05:24 -0500 (EST)
Received: from research.att.com (ligeti.attlabs.att.com [135.197.15.52])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id QAA14383;
	Mon, 14 Jan 2002 16:05:23 -0500 (EST)
Message-ID: <3C434812.4E6A19EA@research.att.com>
Date: Mon, 14 Jan 2002 13:05:22 -0800
From: Julian Chesterfield <julian@research.att.com>
Organization: AT&T Labs
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Marshall Eubanks <tme@multicasttech.com>
Cc: avt@ietf.org, msec@securemulticast.org, Toerless Eckert <eckert@cisco.com>
Subject: Re: [AVT] Unicast RTCP back traffic
References: <web-1225710@multicasttech.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Marshall,

The question seems to be, to what extent should this draft make
requirements on RTP/RTCP to encrypt/authenticate data? In an original
proposal, we had built into the protocol a method for the source to
reflect back the first RR sent by every receiver to ensure the integrity
of the Source IP address. This was considered to be too complicated for
the purposes of the draft, hence we have been looking at more generic
and simpler encryption/authentication methods. The guidelines that we
are working with are to ensure that the proposal does enough to prevent
DDOS attacks, beyond this it is a recommendation to provide secure
encryption of the session data etc... I think that beyond requiring the
source to sign an RDM message with the same private key as the SDP
message, your proposal doesn't really improve on this. I agree that this
is a useful and important requirement and would be happy to add it to
the draft in the form of a requirement for the source to sign it's SR
messages in the same way.

The second issue you are addressing here is whether the SDP type
information can be changed in a session. This is an issue which applies
equally to current ASM sessions since once a session begins, there is no
specified method to change the session parameters. From this point of
view, I think an RDM type protocol is an interesting idea, but possibly
something that is beyond the scope of enabling unicast feedback for
these types of sessions.

So, it seems to me that by applying the following two rules to the
existing draft, the same could be accomplished:

1 - Add additional SDP attributes to allow definition of the feedback
source address in addition to the SSM source identifier

2 - Require the source to sign the SRs with the same public/private key
pair as used for the original SDP data. This would still enable clients
to share the same public/private key pair

So the issue as I see it is, do we introduce changing of SDP type
attributes during a session in the form of an RDM packet type?

Thanks,

Julian Chesterfield

Marshall Eubanks wrote:

> Hello;
>
> Here is a first cut at the security implications and
> a possible fix for
> unicast back traffic for SSM type RTCP. This is obviously
> an AVT issue, I am sending it to MSEC as well.
>
> This is also available as a pdf on
> http://www.multicasttech.com/papers/unicast_rtcp_analysis.pdf
>
> Regards
> Marshall Eubanks
> tme@multicasttech.com
> ---------------------------------
>
> To      : AVT, MSEC
> From    : T.M. Eubanks
> Subject : Security of Unicast Back Traffic in RTCP
> Date    : January 14, 2002
>
> In the standard Any Source Multicast (ASM) model for the
> Real Time Control Protocol (RTCP), the ?back traffic? (the
> Receiver Reports, or RR?s, the Sender Reports, or SR?s, and
> possibly other user defined auxiliary data, all currently
> issued by a receiver as part of RTCP) is sent to the source
> and all receivers on a multicast group, with the back
> traffic bandwidth being  set to a fraction of the total
> bandwidth, as determined at each receiver. This model must
> change to support Single Source Multicast (SSM), and there
> may be ASM or even unicast applications where SSM-like RTCP
> back traffic would be desirable [Chesterfield and Ott,
> 2001].
>
> In the existing ASM RTCP back traffic model, data are
> multicast onto a group listened to by the source or sources
> and all receivers. For a network that only implements SSM,
> this is not possible, and it may not be desirable even for
> an ASM enabled network, as SSM only protocols should not
> depend on the existence of ASM network capabilities. An
> obvious modification of the ASM RTCP model to handle this
> situation is to unicast RR and other back traffic to the
> source, and then optionally to multicast the data (either in
> the form of RR?s, or as summary digests) to the receivers on
> a separate SSM group. In many cases, it would be convenient
> to separate the functions of the SSM source and the SSM RTCP
> server, and thus to send the unicast RTCP back traffic to an
> arbitrary Internet address. I will call the general case of
> unicast back traffic to an arbitrary location ?SSM-like?
> back traffic.
>
> The Problem
>
> The existence of unicast SSM-like back traffic presents a
> possibly serious security problem. If any receiver were to
> source an arbitrarily high rate of back traffic, then local
> resources could be overwhelmed. In addition, if every
> receiver were to source an arbitrarily high rate of back
> traffic, then the SSM RTCP report server could be
> overwhelmed. Even if receiver back traffic were limited to a
> low level for each receiver (say by specifying a limit to
> the rate of receiver back traffic), then it will still be
> possible to create problems by directing the back traffic to
> a different IP address. In fact, a large flow of SSM like
> RTCP back traffic would constitute a pre-made Distributed
> Denial of Service (DDOS) attack if the traffic could be
> redirected by an attacker. This attack is called ?packet
> bombing? in Chesterfield and Ott [2001].
>
> For this security analysis, I assume that the attacker can
> spoof IP addresses and insert traffic in such a fashion that
> Reverse Path Forwarding (RPF) and other possible checks of
> the integrity of the IP routing are passed. (These checks
> are an important line of defense, but they cannot be the
> only defense as they can be compromised almost trivially in
> certain situations, for example for a multicast source on a
> large LAN with an exploited host.) I also assume that the
> attacker can become a legitimate member of the group, and
> thus has access to any keys or other cryptographic
> information available to group members. This of course makes
> the authentication problem much harder. For example, it
> means that simple symmetric key encryption of the RTCP
> traffic, or even of the underlying RTP traffic, as is
> suggested in Chesterfield and Ott [2001], will not improve
> the security of the SSM-like back traffic, as it must be
> assumed that the attacker will possess the keys.
>
> I will assume that the basic means of authentication of back
> traffic direction will be through cryptographic hash
> functions, such as MD-5 or SHA-1, coupled with public-key
> cryptography. These functions are described in detail in
> Schneier [1996].
>
> In Chesterfield and Ott [2001], the basic means of
> protecting against using the back traffic for denial of
> service attacks is to only send back traffic to the source,
> and to verify the source by verifying the Session
> Description Protocol (SDP) message announcing the source.
> There are several objections to this procedure :
>
> 1.) The source may not be the appropriate place to deal with
> the back traffic. The source may not even be reachable by
> unicast from the receivers, as is the case with certain
> means of distributing IP data by satellite. Conversely,
> there may be multiple sources and it may be desirable to
> squelch the back traffic to most of the sources, while still
> sending it to others.
>
> 2.)  This does not solve the security problem. I may be able
> to perform a denial of service on the source by spoofing the
> control traffic coming from the source, even if the source
> was originally authenticated. (For example, I could increase
> the amount of back traffic to a point beyond the capacity of
> the source to handle.)
>
> This is recognized by Chesterfield and Ott [2001], who state
> as requirements that
>
>       - The information providing the unicast feedback
> address
>       needs to be authenticated as being from a trusted
> source.
>
>       - Data integrity of the RTCP traffic from the source,
> particularly
>       RSI + LJS packets is also required.
>
> but without stating the means for achieving this.
>
> CISCO?s IPTV currently sends back unicast RTCP traffic back
> upon request. A new APP packet is defined and reports can
> only be sent to the source. This packet is protected against
> change by signing it with an MD5 hash [Toerless Eckert,
> personal communication]. Since every receiver presumably has
> access to the shared secret, it is hard to see how this
> protocol can stop spoofing of the APP messages, independent
> of the cryptographic weakness of the MD5 hash.
>
> Of course, there may be multicast applications where there
> is tight communication between sources and receivers, such
> that each receiver could have a unique shared secret. This
> is not an adequate solution, however, in the context of the
> current multicast service model.
> Another solution (suggested by Bill Fenner) is to include
> the back traffic information in the SDP file, which could
> then be subject to authentication. The problem I see with
> this is that it makes it impossible to change the back
> traffic model once it is set up (many applications/users
> store SDP information for long periods of time) and it also
> complicates the SDP model. SDP information can be sent now
> by SAP, by http or by e-mail. Only http could easily be
> changed at present to support the new authentication.
>
> A Protocol for Authenticating Back Traffic Requests
>
> In my opinion, authentication of back traffic requests
> requires more infrastructure than is available in
> Chesterfield and Ott [2001]. Here, I set forth what I see is
> one means of performing this authentication.
>
> The new protocol involves getting a public key for the
> source, presumably from a Certificate Authority (related
> sources could share private keys and announce the same
> public one). (The SDP protocol could be amended to
> optionally request this.) A new RTCP message, the Report
> Direction Message (RDM), is required.
>
> Then
>
> 1.) The source sends RDM?s containing
>
>         the IP address for the source traffic
>         the IP address for the back traffic
> the group (or SSM channel) address
>         the desired bandwidth for the traffic (the receiver
> bandwidth of Chesterfield and Ott) and
> the timestamp of the RDM
>
> 2.) The RDM is signed with a cryptographic hash covering all
> of the items in # 1 above.
>
> 3.) The cryptographic hash is encrypted with the private key
> of the source. The corresponding public key could be found,
> e.g. from a Certificate Authority for the source.
> This signature, plus the cryptographic hash, is included in
> the RDM and multicast to the group.
>
> 4.) The RDM is optionally encrypted.
>
> 5.) The RDM is sent to the group members as part of  the
> RTCP traffic from the sender.
>
> 6.) Each receiver verifies the RDM and uses it to direct the
> flow of its RTCP back traffic. This includes decryption if
> necessary, verifying that the cryptographic hash is correct,
> decryption of the RDM signature using the public key of the
> source, verifying that the IP address of the source matches
> the IP address of the incoming SSM RTP traffic, verifying
> that the correct group address is present, and the timestamp
> is in the recent past.
>
> In many situations RDM?s need not change for long periods of
> time. In that case, the RDM may be verified by simply
> checking the cryptographic hash. If the RDM does not change
> the direction or the rate of the back traffic, there is no
> reason to authenticate it further.
>
> 7.) Optionally, the receiver uses information from the
> received RDM to provide integrity checks in its back
> traffic. The most secure version of this would be to hash
> the return RR with some information being sent directly on
> the multicast group, which would verify that the receiver
> was actually receiving the multicast data.
>
> Also, there needs to be an upper limit to the amount of RTCP
> traffic a receiver may source, of order 1 message per
> second, as there is no reason to allow an arbitrarily large
> amount of back traffic from any specific receiver.
>
> Possible attacks on this protocol include :
>
> 1.) The conflict attack. If I can take a valid RPM message
> from the source, modify information (say the IP address of
> the RTCP server) and then find a variant of the compromised
> message that has the same cryptographic hash as the original
> RPM message, then the receiver has no way of knowing that
> the message has been corrupted, as this message will give
> the same public key signature as the original. This is why
> it is necessary to digitally sign the RDM message, as
> otherwise the attacker could simply modify the RDM as
> desired, and generate a new cryptographic hash for the new
> message.
>
> It is reasonable to assume that MD5 is subject to conflict
> attacks [Dobbertin, 1996], which is presumably why the IESG
> has ruled its use out for new protocols. It is often stated
> that the keyed HMAC-MD5 extension of MD5 [RFC2403, 1998] is
> still secure. However, this is clearly not the case for this
> protocol. The additional security for HMAC-MD5 comes from
> the use of a key. Since, in this case, the attacker must be
> presumed to know the key (which must be shared with the
> entire multicast group), the HMAC-MD5 hash could be
> compromised in roughly the same time as an unprotected MD5
> hash.
>
> 2.) The birthday attack. This is not much of a worry. The
> SHA-1 algorithm produces a 160 bit hash function. The number
> of messages from the same authority that would have to be
> searched to have a 50% chance of finding a pair of messages
> producing the same hash function is thus about 2^80. If
> there were 1 Giga-RPM messages produced per second from one
> authority,
> it would take 38 million years to find such a pair.
>
> 3.) The replay attack. If I capture a valid RDM message, I
> can replay it. The utility of this is limited by including
> the group and source address in the RDM hash (this makes it
> impossible to send the traffic from a very populated group
> to the SSM RTCP server for a much lower bandwidth group). If
> a (S,G) is being reused by a sloppy source, an attack would
> be possible by reusing a RDM from a high bandwidth
> application for a lower bandwidth one. The best way to
> prevent this would be to include a timestamp, and only allow
> RDM?s to be valid for a limit period (say 180 seconds).
>
> Conclusions
>
> I see no way to authenticate RDM type information for large
> public SSM sessions without using public key cryptography.
> This is much slower than symmetric key cryptography, which
> may be a problem for this protocol. On the other hand, it is
> only necessary to protect an RDM for the duration of its
> validity, and one key verification per minute (which can be
> done entirely at the receiver once the public key for the
> source is obtained) does not sound especially onerous. This
> rate can be kept even lower if, as is reasonable for many
> applications, the contents of the RDM message are not
> changed for long periods of time.
>
> One specific conclusion I reached is that HMAC-MD5 for this
> application is to be avoided. I recommend that SHA-1 be used
> instead.
>
> This protocol imposes a fair amount of extra complexity into
> the SSM service model. The response of some application
> developers may be not to make use of back traffic
> authentication. In that case, a reasonable question is
> whether multicast is better served by simply not sending any
> RTCP back traffic at all, or whether RTCP should include a
> low bandwidth default for back traffic information to the
> source (under the assumption that extremely large groups
> could afford to pay for the extra complexity of
> authentication if the back traffic bandwidth became
> problematic). If the default were to unicast one message to
> the source every 50 seconds in the absence of valid
> authentication, then (assuming that the message were 500
> bytes), then it would take 700 group members to saturate a
> dial-up connection, and several thousand to saturate a
> typical DSL connection. Whether this is a reasonable risk is
> open to debate.
>
> References
>
> [Dobbertin, 1996] The Status of MD5 after a Recent Attack,
> Hans Dobbbertin, CryptoBytes, Vol. 2, 1-5, 1996.
>
> [Chesterfield and Ott, 2001] RTCP Extension for Single
> Source Multicast Sessions with  Unicast RTCP feedback,
> Julian Chesterfield and Joerg Ott,
> draft-chesterfield-avt-rtcpssm-02.txt, 2001.
>
> [RFC2104, 1997] HMAC: Keyed-Hashing for Message
> Authentication, H. Krawczyk,  M. Bellare, and R. Canetti,
> IETF Request for Comments: 2104, 1997.
>
> [RFC2403, 1998] The Use of HMAC-MD5-96 within ESP and AH,
> C. Madson and R. Glenn, IETF Request for Comments: 2403,
> 1998.
>
> [Schneier, 1996] Applied Cryptography, Bruce Schneier, J.
> Wiley, 1996.
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> http://www1.ietf.org/mailman/listinfo/avt


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



From daemon@optimus.ietf.org  Mon Jan 14 18:14:40 2002
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 SAA24693
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 18:14:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA00219
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 18:14:43 -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 SAA00191;
	Mon, 14 Jan 2002 18:13:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA00164
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 18:13:52 -0500 (EST)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24634
	for <avt@ietf.org>; Mon, 14 Jan 2002 18:13:49 -0500 (EST)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id QAA00988; Mon, 14 Jan 2002 16:13:51 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id QAA02160; Mon, 14 Jan 2002 16:13:51 -0700 (MST)]
Received: from quantix20.cig.mot.com (quantix20 [160.47.58.31])
	by relay1.cig.mot.com (8.11.4/8.11.4) with ESMTP id g0ENDo107709;
	Mon, 14 Jan 2002 17:13:50 -0600 (CST)
Received: from cig.mot.com (d50-38e1.cig.mot.com [160.47.56.225])
	by quantix20.cig.mot.com (8.8.8+Sun/8.8.8) with ESMTP id RAA25442;
	Mon, 14 Jan 2002 17:18:32 -0600 (CST)
Message-ID: <3C4366B6.DCB11793@cig.mot.com>
Date: Mon, 14 Jan 2002 17:16:06 -0600
From: Qiaobing Xie <xieqb@cig.mot.com>
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Matthias Hofmann <Matthias.Hofmann@fgmicrotec.com>
CC: Qiaobing Xie <Qiaobing_Xie-QXIE1@email.mot.com>, AVT WG <avt@ietf.org>,
        Stephen Casner <casner@acm.org>
Subject: Re: AW: [AVT] Edited AMR draft for your review
References: <BOEJLJADHEGBFPONEBFDKEPACAAA.Matthias.Hofmann@fgmicrotec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hi, Matthias,

It's not late at all. The paragraph in question is going to be revised
when the final v11 comes out (should be soon) and I believe your concern
will be addressed. 

-Qiaobing

Matthias Hofmann wrote:
> 
> >   - We ask the wg to review the revised draft and provide comments by
> >     early next Friday.
> 
> Maybe its already too late to get it into the revised draft, but anyway;
> 
> In chapter 4.2.2.1. in the third paragraph it says:
> 
>     The number of class A bits for various coding
>     mode in AMR-WB codec is specified as normative in table 2 in
>     [4]. These definitions of class A bits MUST be used for this
>     payload format.
> 
> A definition for the number of class A bits for the AMR-WB Frame Type 9
> SID(namely 40)needs to be added, since table 2 in [4] only covers Frame Type
> 0-8. table 7 in [4] might be ok as reference.
> 
> Matthias
> 
> Matthias Hofmann
> fg microtec GmbH
> Kronstadterstr. 9
> 81677 Muenchen
> Germany
> Tel.: +49 89 99269515

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



From daemon@optimus.ietf.org  Mon Jan 14 22:51:13 2002
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 WAA03427
	for <avt-archive@odin.ietf.org>; Mon, 14 Jan 2002 22:51:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA09131
	for avt-archive@odin.ietf.org; Mon, 14 Jan 2002 22:51:17 -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 WAA09082;
	Mon, 14 Jan 2002 22:49:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA08989
	for <avt@optimus.ietf.org>; Mon, 14 Jan 2002 22:49:05 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03409
	for <avt@ietf.org>; Mon, 14 Jan 2002 22:49:00 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0F3mWp21238;
	Mon, 14 Jan 2002 19:48:32 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 14 Jan 2002 19:50:35 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020114194917.G85116-200000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="0-896327955-1011066200=:85116"
Content-ID: <20020114194917.O85116@ash.packetdesign.com>
Subject: [AVT] IETF 52 Salt Lake City meeting minutes
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-896327955-1011066200=:85116
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <20020114194917.O85116@ash.packetdesign.com>

Attached are the minutes for AVT WG.

			-- Steve & Colin

--0-896327955-1011066200=:85116
Content-Type: TEXT/PLAIN; NAME="minutes01dec.txt"
Content-ID: <20020114194320.A85116@ash.packetdesign.com>
Content-Description: 
Content-Disposition: ATTACHMENT; FILENAME="minutes01dec.txt"
Content-Transfer-Encoding: BASE64

QXVkaW8vVmlkZW8gVHJhbnNwb3J0IFdvcmtpbmcgR3JvdXAgTWludXRlcw0K
DQpSZXBvcnRlZCBieSBTdGVwaGVuIENhc25lciBhbmQgQ29saW4gUGVya2lu
cw0KDQpUaGUgQXVkaW8vVmlkZW8gVHJhbnNwb3J0IHdvcmtpbmcgZ3JvdXAg
bWV0IGZvciB0d28gc2Vzc2lvbnMgYXQgdGhlDQo1Mm5kIElFVEYgaW4gU2Fs
dCBMYWtlIENpdHkuICBBcyB1c3VhbCwgd2UgZmlsbGVkIGFsbCB0aGUgc2No
ZWR1bGVkDQp0aW1lICg1IGhvdXJzKSBwbHVzIGEgbGl0dGxlIHJ1bi1vdmVy
IHRpbWUgb24gdGhlIGZpcnN0IHNlc3Npb24gc2luY2UsDQp1bmxpa2UgdGhl
IHVzdWFsIHNjaGVkdWxlLCBpdCB3YXMgaW4gdGhlIE1vbmRheSBuaWdodCBz
bG90LiAgVGhlIGZpcnN0DQpzZXNzaW9uIGNvdmVyZWQgdGhlIFJUUCBwYXls
b2FkIGZvcm1hdHMgYWxyZWFkeSB1bmRlciBkaXNjdXNzaW9uIGluDQp0aGUg
V0cgcGx1cyBwcm9wb3NhbHMgZm9yIGEgZmV3IG5ldyBvbmVzLiAgVGhlIHNl
Y29uZCBzZXNzaW9uIGNvdmVyZWQNCnRoZSBzdGF0dXMgb2YgdGhlIFJUUCBw
cm90b2NvbCBpdHNlbGYsIHBsdXMgc2V2ZXJhbCBleHRlbnNpb25zDQppbmNs
dWRpbmcgbmV3IHByb2ZpbGVzIGZvciBzZWN1cml0eSBhbmQgUlRDUC1iYXNl
ZCBmZWVkYmFjay4NCg0KVGhlIG1lZXRpbmcgb3BlbmVkIHdpdGggYW4gdXBk
YXRlIGJ5IFN0ZXZlIENhc25lciBvbiB0aGUgc3RhdHVzIG9mDQpkb2N1bWVu
dHMgaW4gcHJvY2Vzcy4gIFRoZSBncm91cCBoYXMgaGFkIGEgc2luZ2xlIFJG
QyBwdWJsaXNoZWQgc2luY2UNCnRoZSBsYXN0IG1lZXRpbmc6IFJUUCBUZXN0
aW5nIFN0cmF0ZWdpZXMgKFJGQyAzMTU4KS4gIFRoZSBSVFAgcGF5bG9hZA0K
Zm9ybWF0cyBmb3IgRFYgYXVkaW8gJiB2aWRlbyBhcmUgb24gdGhlIFJGQyBF
ZGl0b3IncyBxdWV1ZS4gIFRoZSBSVFANCnBheWxvYWQgZm9yIEFNUiBhbmQg
QU1SLVdCIGF1ZGlvIGhhcyBiZWVuIHdhaXRpbmcgZm9yIEFEIGFwcHJvdmFs
DQpzaW5jZSBKdWx5LCBidXQgc2hvcnRseSBiZWZvcmUgdGhlIG1lZXRpbmcg
d2UgcmVjZWl2ZWQgbm90aWNlIG9mIElFU0cNCm9iamVjdGlvbnMgdGhhdCB0
aGUgZG9jdW1lbnQgaW4gbm90IHN1ZmZpY2llbnRseSBjbGVhciBpbiBzdHJ1
Y3R1cmUNCmFuZCBsYW5ndWFnZS4gIFN0ZXZlIGFwb2xvZ2l6ZWQgdG8gdGhl
IGF1dGhvcnMgYW5kIHRoZSBvdGhlciBzdGFuZGFyZHMNCmJvZGllcyB3YWl0
aW5nIGZvciB0aGlzIGRvY3VtZW50IGJlY2F1c2UgdGhlIGRlbGF5IGluIHBy
b3ZpZGluZyB0aGlzDQpyZXNwb25zZSBkb2VzIG5vdCByZXByZXNlbnQgc2F0
aXNmYWN0b3J5IHBlcmZvcm1hbmNlIGJ5IHRoZSB3b3JraW5nDQpncm91cCBh
bmQgdGhlIElFVEYuICBIb3dldmVyLCB0aGlzIGFsc28gc2VydmVzIGFzIGEg
bGVzc29uIHRvIHRoZQ0KZ3JvdXAgdGhhdCB3ZSBtdXN0IHB1dCBpbiB0aGUg
ZWZmb3J0IHRvIGNhcmVmdWxseSByZXZpZXcgZG9jdW1lbnRzIGZvcg0KY2xh
cml0eSBvZiB3cml0aW5nIGFuZCBzdHJ1Y3R1cmUgaW4gYWRkaXRpb24gdG8g
dGVjaG5pY2FsIGNvcnJlY3RuZXNzDQpiZWZvcmUgd2Ugc3VibWl0IHRoZW0g
dG8gdGhlIElFU0cuICBUaGUgYXV0aG9ycyBvZiB0aGUgQU1SIGRyYWZ0IGFy
ZQ0KcmV2aXNpbmcgaXQgd2l0aCB0aGUgaGVscCBvZiB0aGUgQVZUIGNoYWly
cyBzbyB0aGF0IGl0IGNhbiBiZQ0KcmVzdWJtaXR0ZWQgdG8gdGhlIElFU0cg
YXMgc29vbiBhcyBwb3NzaWJsZS4NCg0KSW4gYWRkaXRpb24gdG8gdGhlIGRv
Y3VtZW50cyBhbHJlYWR5IGluIHByb2Nlc3MsIHRoZXJlIGFyZSBzZXZlcmFs
DQpkcmFmdHMgcG90ZW50aWFsbHkgcmVhZHkgZm9yIFdHIGxhc3QgY2FsbCBm
b3IgY29tbWVudHMuICBUaGUgd29ya2luZw0KZ3JvdXAgYWdyZWVkIHRoYXQg
dGhlIGZvbGxvd2luZyBkcmFmdHMgc2hvdWxkIGdvIHRvIGxhc3QgY2FsbC4g
IEFsbCBvZg0KdGhlc2UgYXJlIHRvIGdvIHRvIFByb3Bvc2VkIFN0YW5kYXJk
IChleGNlcHQgYXMgbm90ZWQpOg0KDQogIC0gVGhlIENvbWZvcnQgTm9pc2Ug
cGF5bG9hZCBmb3JtYXQgKGRyYWZ0LWlldGYtYXZ0LXJ0cC1jbi0wNC50eHQp
DQogICAgaGFzIHJldmVydGVkIHRvIGEgZml4ZWQgOCBrSHogY2xvY2sgcmF0
ZSBmb3Igc3RhdGljIHBheWxvYWQgdHlwZQ0KICAgIDEzICh0aGUgY2hhbmdl
IHRvIG1ha2UgaXQgdmFyaWFibGUgaW4gdGhlIHByZXZpb3VzIHZlcnNpb24N
CiAgICBjb25mbGljdGVkIHdpdGggdGhlIGRlZmluaXRpb24gb2YgYSBzdGF0
aWMgcGF5bG9hZCB0eXBlKS4gIFRoZXJlDQogICAgd2VyZSBubyBvYmplY3Rp
b25zIHRvIGdvaW5nIHRvIFdHIGxhc3QgY2FsbC4gIFRoZSBtYWluIHF1ZXN0
aW9uDQogICAgZm9yIGxhc3QgY2FsbCBpcyB3aGV0aGVyIHRoZXJlIHdpbGwg
YmUgYW55IGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5DQogICAgcHJvYmxlbXMg
d2l0aCBlYXJseSBpbXBsZW1lbnRhdGlvbnMgb2YgQ04gdGhhdCBpbmNsdWRl
ZCBvbmx5IHRoZQ0KICAgIGFtcGxpdHVkZSBhbmQgbm90IHNwZWN0cmFsIGlu
Zm9ybWF0aW9uPw0KDQogIC0gVGhlIEVuaGFuY2VkIENSVFAgKGRyYWZ0LWll
dGYtYXZ0LWNydHAtZW5oYW5jZS0wMy50eHQpIGFuZA0KICAgIFR1bm5lbGVk
IENSVFAgKGRyYWZ0LWlldGYtYXZ0LXRjcnRwLTA1LnR4dCkgZHJhZnRzIGNv
bXByaXNlIEFWVCdzDQogICAgcHJvZHVjdCBmb3IgUlRQIG11bHRpcGxleGlu
Zy4gIFRoZSBxdWVzdGlvbiByYWlzZWQgYXQgdGhlIGxhc3QNCiAgICBtZWV0
aW5nIGFib3V0IHdoZXRoZXIgdGhlIElQdjQgSUQgZmllbGQgd291bGQgYmUg
bWFpbnRhaW5lZCB1bmRlcg0KICAgIHRoZSAidHdpY2UiIGFsZ29yaXRobSBo
YXMgYmVlbiByZXNvbHZlZCBieSBoYXZpbmcgdGhlIGRlY29tcHJlc3Nvcg0K
ICAgIGxlYXJuIHRoZSBudW1iZXIgb2YgcmVwZXRpdGlvbnMgdGhlIGNvbXBy
ZXNzb3Igd2lsbCBzZW5kLCBhbmQNCiAgICBrbm93aW5nIHRoYXQgdGhlIGNv
bnRleHQgaW5jbHVkaW5nIHRoZSBJRCB3aWxsIGJlIGludGFjdCBpZiBmZXdl
cg0KICAgIHBhY2tldHMgdGhhbiB0aGF0IGhhdmUgYmVlbiBsb3N0LiAgVGhl
IHJvYnVzdCBtb2RlIG9mIG9wZXJhdGlvbiBpcw0KICAgIG5vdyBkZXNjcmli
ZWQgbXVjaCBtb3JlIGNsZWFybHksIGFuZCBQUFAgbmVnb3RpYXRpb24gaGFz
IGJlZW4NCiAgICByZW1vdmVkIHRvIGEgc2VwYXJhdGUgZG9jdW1lbnQuICBU
aGUgZ3JvdXAgaHVtbWVkIGFncmVlbWVudCBmb3INCiAgICBpc3N1aW5nIFdH
IGxhc3Qgb24gdGhlc2UgKHRjcnRwIHdpbGwgYmUgZm9yIEJDUCkuDQoNCiAg
LSBUaGVyZSBhcmUgdHdvIGRyYWZ0cyBmb3IgcGF5bG9hZCBmb3JtYXRzIHRv
IHByb3ZpZGUgdW5lcXVhbCBlcnJvcg0KICAgIHByb3RlY3Rpb24gdG8gZGlm
ZmVyZW50IHBhcnRzIG9mIGEgZGF0YSBzdHJlYW0uICBUaGUgVW5ldmVuIExl
dmVsDQogICAgUHJvdGVjdGlvbiBkcmFmdCAoZHJhZnQtaWV0Zi1hdnQtdWxw
LTAyLnR4dCkgaXMgYW4gZXh0ZW5zaW9uIG9mDQogICAgdGhlIEZFQyBwYXls
b2FkIGZvcm1hdCBpbiBSRkMgMjczMy4gIEl0IHdhcyBhY2NlcHRlZCBmb3Ig
V0cgbGFzdA0KICAgIGNhbGwgbGFzdCB0aW1lLCBidXQgbmVlZGVkIHRoZSBN
SU1FIHJlZ2lzdHJhdGlvbiB0aGF0IHdhcyBhZGRlZCBpbg0KICAgIHRoaXMg
cmV2aXNpb24uICBUaGUgc2Vjb25kIGRyYWZ0IG9uIFVuZXF1YWwgRXJhc3Vy
ZSBQcm90ZWN0aW9uDQogICAgKGRyYWZ0LWlldGYtYXZ0LXV4cC0wMS50eHQp
IHByb3ZpZGVzIGEgc29tZXdoYXQgc2ltaWxhciBzZXJ2aWNlLA0KICAgIGJ1
dCBmb3IgZGlmZmVyZW50IGVudmlyb25tZW50cyBvciByZXF1aXJlbWVudHMu
ICBUaGVzZSB0d28gZHJhZnRzDQogICAgdXNlIGRpZmZlcmVudCB0ZWNobmlx
dWVzIHRoYXQgZG9uJ3QgbWFrZSBzZW5zZSB0byBtZXJnZSwgc28gd2UNCiAg
ICBoYXZlIGRlY2lkZWQgdG8gcHJvY2VlZCB0byBQcm9wb3NlZCBTdGFuZGFy
ZCB3aXRoIGJvdGggb2YgdGhlbSBhbmQNCiAgICBzZWUgd2hldGhlciBzdWZm
aWNpZW50IGltcGxlbWVudGF0aW9uIGludGVyZXN0IGV4aXN0cyBmb3IgZWl0
aGVyLg0KICAgIEluIG9yZGVyIHRvIGNvbnZpbmNlIHRoZSBJRVNHIHRoYXQg
d2Ugc2hvdWxkIHN0YW5kYXJkaXplIHR3bw0KICAgIG1ldGhvZHMsIGVhY2gg
ZHJhZnQgbmVlZHMgdG8gaGF2ZSBhbiBhcHBsaWNhYmlsaXR5IHN0YXRlbWVu
dCB0bw0KICAgIGluZGljYXRlIHdoZW4gaXQgc2hvdWxkIGJlIHVzZWQuICBU
aGUgdXhwIGRyYWZ0IGFscmVhZHkgaGFzIHRoaXM7DQogICAgdGhlIHVscCBk
cmFmdCBuZWVkcyB0byBhZGQgaXQuICBGcm9tIHRoZXNlIHN0YXRlbWVudHMg
d2Ugd2lsbA0KICAgIGNvbXBvc2UgdGhlIGNvdmVyIGxldHRlciB0byB0aGUg
SUVTRyBmb3IgdGhlc2UgdHdvIGRyYWZ0cy4NCg0KT25lIGRyYWZ0IG5vdCBv
biB0aGUgYWdlbmRhIGZvciB0aGlzIG1lZXRpbmcgd2FzIG9uIHRyYW5zZmVy
IG9mIFIyDQpzaWduYWxpbmcgb3ZlciB0aGUgSW50ZXJuZXQgKGRyYWZ0LW1h
cmtvdi1yMm9pcC0wMC50eHQpLiAgSGVubmluZw0KU2NodWx6cmlubmUgaGFz
IGJlZW4gaW4gY29udGFjdCB3aXRoIHRoZSBhdXRob3IgYW5kIHdpbGwgZm9s
ZCBpdCBpbnRvDQphIHJldmlzaW9uIG9mIFJGQyAyODMzLg0KDQoNClJUUCBQ
YXlsb2FkIEZvcm1hdHMgZm9yIE1QRUctNA0KDQpUaGUgZmlyc3QgZ3JvdXAg
b2YgcGF5bG9hZCBmb3JtYXRzIGRpc2N1c3NlZCBhdCB0aGlzIG1lZXRpbmcg
YXJlIGZvcg0KTVBFRy00LiAgUGhpbGlwcGUgR2VudHJpYyBwcmVzZW50ZWQg
YW4gb3ZlcnZpZXcgb2YgdGhlIGZvdXIgcGF5bG9hZA0KZm9ybWF0IGRvY3Vt
ZW50cyBhbmQgdGhlIHJlbGF0aW9uc2hpcHMgYW1vbmcgdGhlbS4NCg0KUkZD
IDMwMTYgd2FzIGluc3RpZ2F0ZWQgYnkgdGhlIElUVSBmb3IgdXNlIGluIEgu
MzIzIGNvbmZlcmVuY2luZyBhbmQNCnRlbGVwaG9ueSBzeXN0ZW1zLiAgSXQg
c3VwcG9ydHMgb25seSB2aWRlbyBlbGVtZW50YXJ5IHN0cmVhbXMgYW5kDQph
dWRpbyBzdHJlYW1zIGVuY2Fwc3VsYXRlZCBpbiBMQVRNIGZvciBhcHBsaWNh
dGlvbnMgdGhhdCBkbyBub3QgbmVlZA0KTVBFRy00IFN5c3RlbXMgZnVuY3Rp
b25zLiAgVGhlICJnZW5lcmljIiBwYXlsb2FkIGZvcm1hdCBzcGVjaWZpZWQg
aW4NCmRyYWZ0LWlldGYtYXZ0LW1wZWc0LW11bHRpU0wtMDMudHh0IGNhbiBl
bmNhcHN1bGF0ZSBhbnkgTVBFRy00DQplbGVtZW50YXJ5IHN0cmVhbSBpbmNs
dWRpbmcgdGhlIFN5bmNocm9uaXphdGlvbiBMYXllciAoU0wpLiAgVGhlIHRo
aXJkDQpkcmFmdCwgZHJhZnQtaWV0Zi1hdnQtbXBlZzQtc2ltcGxlLTAwLnR4
dCwgaXMgbm90IGEgcGF5bG9hZCBmb3JtYXQgb2YNCml0cyBvd24sIGJ1dCBy
YXRoZXIgYW4gYXBwbGljYXRpb24gbm90ZSB3aGljaCBzcGVjaWZpZXMgYSBz
dWJzZXQgb2YNCnRoZSBnZW5lcmljIHBheWxvYWQgZm9ybWF0IG9ubHkgYXVk
aW8gYW5kIHZpZGVvIGVsZW1lbnRhcnkgc3RyZWFtcw0Kd2l0aCBubyBTTC4g
IEl0IGlzIGludGVuZGVkIHRvIHNpbXBsaWZ5IHVuZGVyc3RhbmRpbmcsIGlt
cGxlbWVudGF0aW9uDQphbmQgdXNlIGZvciB0aGUgYXBwbGljYXRpb25zIHBy
b21vdGVkIGJ5IHRoZSBJbnRlcm5ldCBTdHJlYW1pbmcgTWVkaWENCkFsbGlh
bmNlLiAgVGhlIGZvdXJ0aCBkcmFmdCwgZHJhZnQtY3VyZXQtYXZ0LXJ0cC1t
cGVnNC1mbGV4bXV4LTAyLnR4dCwNCmlzIHNlcGFyYXRlIGZyb20gdGhlc2U7
IGl0IHNwZWNpZmllcyBSVFAgdHJhbnNwb3J0IGZvciBNUEVHLTQgY2Fycmll
ZA0KaW4gYSBtdWx0aXBsZXggdG9vbCBkZXNpZ25lZCBieSBNUEVHIGNhbGxl
ZCBGbGV4TXV4LiAgU2VlIFBoaWxpcHBlJ3MNCnNsaWRlcyBmb3IgYSBuaWNl
IHBpY3R1cmUgc2hvd2luZyB0aGUgb3ZlcmxhcCBhbW9uZyB0aGVzZSBwYXls
b2FkDQpmb3JtYXRzLiAgQ29saW4gUGVya2lucyByZXF1ZXN0ZWQgdGhhdCB0
aGlzIHBpY3R1cmUgYmUgaW5jbHVkZWQgaW4gdGhlDQpnZW5lcmljIGRyYWZ0
Lg0KDQpQaGlsaXBwZSBtZW50aW9uZWQgYXMgYW4gYXNpZGUgdGhhdCB0aGVy
ZSBpcyBhIGZpZnRoIGRvY3VtZW50DQpkZXNjcmliaW5nIGZyYW1ld29yayBm
b3IgTVBFRy00IG92ZXIgSVAuICBBIGNvcHkvcGFzdGUgb2YgdGhlIElFVEYN
CmRyYWZ0IGlzIGF0IGFsbW9zdC1zdGFuZGFyZCBzdGF0dXMgaW4gTVBFRyBj
b21taXR0ZWUuICBDb2xpbiBQZXJraW5zDQpzYWlkIGhlIHRob3VnaHQgdGhl
IGRyYWZ0IHdhcyBkZWFkIGJlY2F1c2UgaXQgaGFzIG5vdCBiZWVuIHVwZGF0
ZWQgaW4NCklFVEYgZm9yIGEgbG9uZyB0aW1lLiAgQ29saW4gZXhwcmVzc2Vk
IGNvbmNlcm4gYWJvdXQgdGhlIGRvY3VtZW50DQpiZWluZyBzdGFuZGFyZGl6
ZWQgaW4gTVBFRyBiZWNhdXNlIHRoZXJlIGFyZSBzZXZlcmFsIHByb2JsZW1z
IHdpdGggaXQsDQppbiBwYXJ0aWN1bGFyIHdpdGggaW5jb25zaXN0ZW5jaWVz
IHJlbGF0aXZlIHRvIG90aGVyIGRvY3VtZW50cy4gIFRoaXMNCndhcyB0byBi
ZSBkaXNjdXNzZWQgZnVydGhlciBvZmZsaW5lLg0KDQpUaGUgZ2VuZXJpYyBw
YXlsb2FkIGZvcm1hdCBoYXMgZXZvbHZlZCB0aHJvdWdoIGFib3V0IDEzIHJl
dmlzaW9ucyB3aXRoDQpkaWZmZXJlbnQgbmFtZXMuICBJbiB0aGUgbGFzdCB0
d28gcmV2aXNpb25zLCB3aGljaCB3ZXJlIGRvbmUgc2luY2UgdGhlDQpwcmV2
aW91cyBtZWV0aW5nLCB0aGUgc3BlYyBpcyBub3QgY2hhbmdpbmcgdGVjaG5p
Y2FsbHksIGJ1dCB0aGVyZSBoYXZlDQpiZWVuIGEgbnVtYmVyIG9mIGNsYXJp
ZmljYXRpb25zIHByb21wdGVkIGluIHBhcnQgYnkgcXVlc3Rpb25zIGZyb20N
CmltcGxlbWVudGVycy4gIEluIHBhcnRpY3VsYXIsIHRoZSBkZXNjcmlwdGlv
biBvZiB0aGUgdHdvIGludGVybGVhdmluZw0KbW9kZXMgd2FzIGV4cGxhaW5l
ZCBtb3JlIGNsZWFybHksIGFuZCBhbiBleHBsYW5hdGlvbiB3YXMgYWRkZWQg
dG8gc2F5DQpob3cgdG8gaGFuZGxlIHJvbGxvdmVyIG9mIHRoZSBNUEVHIENU
UyB0aW1lc3RhbXAsIHdoaWNoIGlzIGNhcnJpZWQgaW4NCnRoZSBSVFAgdGlt
ZXN0YW1wLCB3aGVuIHRoZSBDVFMgaXMgc2hvcnRlciB0aGFuIDMyIGJpdHMu
ICBJbiB0aGUgbW9zdA0KcmVjZW50IHJldmlzaW9uLCBzb21lIHRleHQgd2Fz
IHJlc3RydWN0dXJlZCB0byBtYWtlIGl0IGVhc2llciB0byByZWFkLA0KYW5k
IHJlZmVyZW5jZXMgdG8gTVBFRy00IFN5c3RlbXMgd2VyZSByZW1vdmVkIHdo
ZXJlIHRoZSBkZXBlbmRlbmNlIHdhcw0Kbm90IHJlYWxseSByZXF1aXJlZC4N
Cg0KQ29saW4gYWdyZWVzIHRoYXQgdGhpcyByZXZpc2lvbiBpcyBiZXR0ZXIs
IGFsdGhvdWdoIG9uIGhpcyBsYXN0DQpyZWFkLXRocm91Z2ggaGUgZm91bmQg
dGhlcmUgd2VyZSBzdGlsbCBzb21lIGVkaXRvcmlhbCBjaGFuZ2VzIG5lZWRl
ZCwNCm90aGVyd2lzZSBpdCB3aWxsIGNvbWUgYmFjayBmcm9tIHRoZSBJRVNH
IGxpa2UgdGhlIEFNUiBwYXlsb2FkIGZvcm1hdA0KZGlkLiAgSG93ZXZlciwg
dGhlIGJpZyBxdWVzdGlvbiwgd2hpY2ggZ2VuZXJhdGVkIHF1aXRlIGEgYml0
IG9mDQpkaXNjdXNzaW9uLCBpcyB0aGF0IHRoZSBwYXlsb2FkIGZvcm1hdCBy
ZW1haW5zIHF1aXRlIGNvbXBsZXguICBJbg0KcGFydGljdWxhciwgQ29saW4g
Y2xhaW1lZCB0aGF0IHRoZSBpbmNsdXNpb24gb2YgdHdvIGludGVybGVhdmlu
ZyBtb2Rlcw0KaW50cm9kdWNlcyBzaWduaWZpY2FudCBjb21wbGV4aXR5IGZv
ciByZWxhdGl2ZWx5IGxpdHRsZSBnYWluLCBhbmQgdGhhdA0KdGhlIHJlYXNv
biB3ZSBoYXZlIGJvdGggc2ltcGxlIGFuZCBnZW5lcmljIGRyYWZ0cyBpcyBi
ZWNhdXNlIG9mIHRoZQ0KaW5jbHVzaW9uIG9mIHRoZSBzZWNvbmQgaW50ZXJs
ZWF2aW5nIG1ldGhvZCBpbiB0aGUgZ2VuZXJpYyBkcmFmdC4NCg0KUGhpbGlw
cGUgZXhwbGFpbmVkIHRoYXQgdGhlIFRTQkkgbW9kZSBpcyB0aW1lc3RhbXAg
YmFzZWQsIHdpdGggYQ0KdGltZXN0YW1wIG9uIGV2ZXJ5IHBpZWNlIG9mIGRh
dGEuICBJdCB3b3JrcyB3ZWxsIGZvciBhdWRpbyBhbmQgdmlkZW8NCnN0cmVh
bXMgYW5kIGlzIHRoZSBtb2RlIHVzZWQgYnkgSVNNQSBpbiB0aGUgc2ltcGxl
IGRyYWZ0LiAgSG93ZXZlciwNCnRoaXMgZG9lcyBub3Qgd29yayB3aXRoIFN5
c3RlbXMgc3RyZWFtcywgc3VjaCBhcyBzY2VuZSBkZXNjcmlwdGlvbg0Kc3Ry
ZWFtcyBmb3Igd2hpY2ggaXQgaXMgbm90IHBvc3NpYmxlIHRvIGNvbnN0cnVj
dCBhIHRpbWVzdGFtcCBmb3INCmV2ZXJ5IHBpZWNlIHRvIGJlIGludGVybGVh
dmVkLiAgVGhhdCByZXF1aXJlcyB0aGUgSUJJIG1vZGUgaW4gd2hpY2gNCmlu
dGVybGVhdmluZyBpcyBiYXNlZCBvbiB0aGUgaW5kZXggb2YgdGhlIHBhY2tl
dC4gIENvbGluIGNvdW50ZXJlZA0KdGhhdCB0aG9zZSBzdHJlYW1zIG5lZWQg
dG8gYmUgZGVsaXZlcmVkIHJlbGlhYmx5LCBzbyB3aHkgaXMgdGhlcmUgYQ0K
bmVlZCB0byBpbnRlcmxlYXZlIHRoZW0gKHNpbmNlIHRoZSBwdXJwb3NlIG9m
IGludGVybGVhdmluZyBpcyB0bw0KZGlzcGVyc2UgdGhlIGVmZmVjdHMgb2Yg
bG9zcyk/ICBUaGUgYW5zd2VyIGlzIHRoYXQgaW4gY2VydGFpbiBjYXNlcyBv
Zg0KZnJhZ21lbnRhdGlvbiBvZiBhdWRpbyBhbmQgdmlkZW8gYWNjZXNzIHVu
aXRzIGludG8gU0wgcGFja2V0cywgdGhlDQpmcmFnbWVudHMgZG9uJ3QgYWxs
IGNhcnJ5IHRpbWVzdGFtcHMuICBXaXRoIFRTQkkgeW91IGNhbiBvbmx5DQpp
bnRlcmxlYXZlIGVudGlyZSBhdWRpbyBmcmFtZXMsIG5vdCBmcmFnbWVudHMg
b2YgZnJhbWVzIGFzIGlzDQphcHByb3ByaWF0ZSBmb3IgQUFDOyB5b3UgY2Fu
J3QgZGVsaXZlciB0aGUgbW9zdCBhZHZhbmNlZCBhdWRpbyB0b29scw0KaW4g
TVBFRy00Lg0KDQpTdGV2ZSBDYXNuZXIgY29tbWVudGVkIHRoYXQgdGhlIHNl
cGFyYXRlIEFBQyBwYXlsb2FkIGZvcm1hdCBkcmFmdA0KcHJvcG9zZWQgZWFy
bGllciBkZWZpbmVkIGludGVybGVhdmluZyB0byBoYW5kbGUgdGhlIHNwZWNp
ZmljDQpyZXF1aXJlbWVudHMgb2YgdGhhdCBhdWRpbyB0eXBlLiAgUGVyaGFw
cyB0aGlzIGlzIHRoZSBjb3JyZWN0IHdheSB0bw0KaGFuZGxlIG90aGVyIGFk
dmFuY2VkIHJlcXVpcmVtZW50cywgd2l0aCBzcGVjaWZpYyBzb2x1dGlvbnMg
YXMgdGhleQ0KYXJpc2UsIHJhdGhlciB0aGFuIHRyeWluZyB0byBtYWtlIHNv
bWV0aGluZyBnZW5lcmljIHRoYXQgd2lsbCBoYW5kbGUNCmFsbCBvZiB0aGVt
Lg0KDQpEYXZlIFNpbmdlciBleHBsYWluZWQgdGhhdCBwZW9wbGUgZXhwZWN0
IHRvIGltcGxlbWVudCB0cmFuc2xhdG9ycyBmcm9tDQpNUEVHLTQgb24gb3Ro
ZXIgY2hhbm5lbHMsIHdoaWNoIG1heSB1c2UgYW55IGFuZCBhbGwgU0wgZnVu
Y3Rpb25zLCB0bw0KTVBFRy00IG92ZXIgUlRQLiAgVGhleSBiZWxpZXZlIHRo
ZXkgbXVzdCBiZSBhYmxlIHRvIGNhcnJ5IGFueXRoaW5nDQp0aGF0IG1heSBh
cHBlYXIgZXZlbiBpZiB0aGV5IGRvbid0IGhhdmUgYSBjb252aW5jaW5nIGFy
Z3VtZW50IGFzIHRvDQp3aHkgc29tZSBvZiB0aG9zZSB0aGluZ3Mgc2hvdWxk
IGV2ZXIgYXBwZWFyIG9uIHRoZSBTTCBzaWRlLiAgUGhpbGlwcGUNCmFncmVl
ZCB0aGF0IHRoZXJlIGFyZSBmZWF0dXJlcyBpbiBNUEVHLTQgdGhhdCBub2Jv
ZHkgY2FuIHNheSBmb3Igc3VyZQ0Kd2lsbCByZWFsbHkgYmUgbmVlZGVkLCBi
dXQgdGhleSB3YW50IHRvIGtlZXAgdGhlIGZyZWVkb20gdG8gdXNlIHRoZW0u
DQpUaGUgZ2VuZXJpYyBkcmFmdCBkb2VzIGltcG9zZSBzb21lIHJlc3RyaWN0
aW9ucyB0aGF0IHdlcmUgYWdyZWVkIGFmdGVyDQpkaWZmaWN1bHQgZGlzY3Vz
c2lvbnMgaW4gTVBFRywgYW5kIHRoYXQgZ29pbmcgYmFjayB0byB0cnkgdG8g
cmVkdWNlDQpmdW5jdGlvbmFsaXR5IGZ1cnRoZXIgd291bGQgYmUgYSBzZXJp
b3VzIHByb2JsZW0uICBBbiBleGFtcGxlIGZlYXR1cmUNCndoaWNoIG5lZWRz
IHRoZSBhYmlsaXR5IHRvIGludGVybGVhdmUgZnJhZ21lbnRzIGlzIGVycm9y
IHNlbnNpdGl2aXR5DQpjYXRlZ29yaWVzOyB0aGlzIGhhcyBpbiBkZXZlbG9w
bWVudCBpbiBNUEVHIGZvciB0d28geWVhcnMsIGFuZCB0aGUNCmRldmVsb3Bl
cnMgZXhwZWN0IHRvIGhhdmUgc29tZSB3YXkgdG8gY2FycnkgaXQgb24gSVAu
ICBPbiB0aGUgb3RoZXINCmhhbmQsIFN0ZXBoYW4gV2VuZ2VyIGJlbGlldmVz
IHRoaXMgd29yayBkb2VzIG5vdCBhZGRyZXNzIHRoZSBraW5kIG9mDQpwcm9i
bGVtcyB3ZSB3aWxsIHNlZSB3aXRoIHJ0cCB0cmFuc3BvcnQsIGUuZy4gcGFj
a2V0IGxvc3MuDQoNClN0ZXZlIG9ic2VydmVkIHRoYXQgdGhlIGZyaWN0aW9u
IGFyaXNlcyBmcm9tIGEgYmFzaWMgZGlmZmVyZW5jZSBpbg0KcGhpbG9zb3Bo
eSBiZXR3ZWVuIElFVEYgYW5kIElTTzogaW4gSUVURiwgd2Ugc2F5IHRoYXQg
aWYgeW91IGRvbid0DQprbm93IGZvciBzdXJlIHRoYXQgeW91IG5lZWQgc29t
ZSBmZWF0dXJlLCBpdCBzaG91bGQgYmUgbGVmdCBvdXQuICBXZQ0KdHJ5IHRv
IHN0YXJ0IHdpdGggdGhlIGJhc2ljcyBhbmQgbGVhcm4gbGVhcm4gbW9yZSBh
Ym91dCB0aGUgcHJvYmxlbSwNCnRoZW4gYWRkIG9uIG90aGVyIHBpZWNlcyBh
cyB0aGUgcmVhbCBuZWVkIGlzIGRlbW9uc3RyYXRlZC4gIFRoZXJlIG1heQ0K
YmUgc29tZSB0aGluZ3MgeW91IGNhbiBkbyB3aXRoIE1QRUctNCB0aGF0IHlv
dSByZWFsbHkganVzdCBzaG91bGQgbm90DQpkby4gIEEgcHJvZmlsZSBvZiBN
UEVHLTQgY291bGQgcmVzdHJpY3Qgd2hhdCBpcyBhY2NlcHRlZCBmb3IgdHJh
bnNwb3J0DQpvdmVyIFJUUCB0byBhdm9pZCB0aGlzIHByb2JsZW0uICBIZSBh
c2tlZCBob3cgbXVjaCBoYXMgYmVlbg0KaW1wbGVtZW50ZWQ7IHRoZSBJU01B
IGNvbXBhbmllcyBhcmUgaW1wbGVtZW50aW5nIHRoZSBzaW1wbGUgc3Vic2V0
LA0KYnV0IHdoYXQgYWJvdXQgYWxsIHRoZSBtb3JlIGNvbXBsaWNhdGVkIHBh
cnRzIHdlIGhhdmUgYmVlbiBkaXNjdXNzaW5nPw0KDQpEYXZlIFNpbmdlciBy
ZXNwb25kZWQgdGhhdCB3ZSBoYXZlIGEgY2hpY2tlbiBhbmQgZWdnIHByb2Js
ZW0uICBCZWNhdXNlDQppdCBpcyBjb21wbGljYXRlZCwgaW1wbGVtZW50ZXJz
IGFyZSBob2xkaW5nIG9mZiB1bnRpbCB0aGUgZHJhZnRzIHN0b3ANCmNoYW5n
aW5nIGFuZCBiZWNvbWUgYSBzdGFibGUgUkZDLiAgRGF2ZSBPcmFuIGFza2Vk
IGlmIHBlb3BsZSBhcmUgYXdhcmUNCnRoYXQgdGhpcyB3b24ndCBtYWtlIGl0
IHRvIERyYWZ0IFN0YW5kYXJkIHVubGVzcyBhbGwgb2YgdGhlIHBpZWNlcyBh
cmUNCmltcGxlbWVudGVkPyAgSXQgbWlnaHQgZ28gdG8gUHJvcG9zZWQgU3Rh
bmRhcmQsIGJ1dCBhbGwgdGhlIHBpZWNlcw0KdGhhdCBhcmUgbm90IGltcGxl
bWVudGVkIGFuZCBpbnRlcm9wZXJhYmlsaXR5IHRlc3RlZCB3aWxsIGdldCBy
aXBwZWQNCm91dCBhbnl3YXkuICBXZSBwcmVzdW1lIHRoZSBnb2FsIGlzIHRv
IGdldCBhIEZ1bGwgU3RhbmRhcmQgc29tZWRheS4NClNpbmdlciBhZ3JlZWQ7
IHdlIGNhbiBzYXkgdG8gdGhlIHBlb3BsZSB3aG8gaGF2ZSBpbnNpc3RlZCBv
biB0aGVzZQ0KZmVhdHVyZXMgdGhhdCB0aGV5IG11c3Qgc2hvdyB1cyB0aGUg
aW50ZXJvcGVyYXRpbmcgaW1wbGVtZW50YXRpb25zIG9yDQp0aGV5IGdldCB5
YW5rZWQuICBQaGlsaXBwZSBzYWlkIHRoYXQgaW50ZXJvcGVyYWJpbGl0eSBz
dGF0ZW1lbnRzIG1heQ0KYmUgaGFyZCB0byBjb2xsZWN0IGJlY2F1c2UgaW50
ZXJvcGVyYXRpb24gaXMgbm90IGRpc2Nsb3NlZCBwdWJsaWNseSwNCmJ1dCBD
b2xpbiByZXBsaWVkIHRoYXQgdGhlIGludGVyb3AgcmVxdWlyZW1lbnRzIGNh
biBiZSBkb25lIHVuZGVyIE5EQQ0KaWYgbmVjZXNzYXJ5LiAgQ29saW4gYXNr
ZWQgaG93IE1QRUcgd2lsbCByZXNwb25kIGlmIHNvbWUgZmVhdHVyZXMgaW4N
CnRoZSBQcm9wb3NlZCBTdGFuZGFyZCBhcmUgcmVtb3ZlZCB3aGVuIGl0IGdv
ZXMgdG8gRHJhZnQgU3RhbmRhcmQuDQpQaGlsaXBwZSBiZWxpZXZlcyB0aGlz
IGlzIGxpa2VseSB0byBiZSBhIHByb2JsZW0uICBTdGVwaGFuIHN1cm1pc2Vk
DQp0aGF0IHRoZSByZXNwb25zZSB3b3VsZCBsaWtlbHkgYmUgc2ltaWxhciB0
byB0aGF0IG9mIHRoZSBJVFU6ICBpZg0KdGhlcmUgYXJlIGZlYXR1cmVzIHJl
bW92ZWQgYWxvbmcgdGhlIHBhdGggY29kZXBvaW50cyB3aWxsIGJlIGFzc2ln
bmVkDQpmb3IgdGhlIGRpZmZlcmVudCBSRkNzIGF0IHRoZSBkaWZmZXJlbnQg
bGV2ZWxzIHdoZXJlIHRoZSBuZXdlciBvbmUgaXMNCmxlc3MgcG93ZXJmdWwg
dGhhbiB0aGUgb2xkIG9uZS4NCg0KUGhpbGlwcGUgYXNrZWQgZm9yIHRoaXMg
ZHJhZnQgdG8gZ28gdG8gV0cgbGFzdCBjYWxsLiAgQ29saW4gYXNrZWQgZm9y
DQptb3JlIG9waW5pb25zIGZyb20gb3RoZXJzIGFzIHRvIHdoZXRoZXIgdGhl
eSB0aGluayB0aGlzIGlzIG5vdyBhdCBhDQpzdGFibGUgdGVjaG5pY2FsIGxl
dmVsIG9yIHdoZXRoZXIgdGhleSB0aGluayBvdGhlciB0ZWNobmljYWwgY2hh
bmdlcw0Kc2hvdWxkIGJlIG1hZGUuICBIZSBzYWlkIHRoZSBrZXkgcG9pbnQg
dG8gdGFrZSBmcm9tIHRoZSBkaXNjdXNzaW9uIGlzDQp0aGF0IHdlIGFyZSBw
dXNoaW5nIHRoZSBsaW1pdHMgb2Ygd2hhdCB3ZSBjYW4gcHVibGlzaCBhcyBh
biBSRkMNCmJlY2F1c2Ugb2YgdGhlIGNvbXBsZXhpdHkgb2YgaXQuICBXZSBh
cmUgY29uY2VybmVkIHRoYXQgdGhlIElFU0cgaXMNCmdvaW5nIHRvIHRha2Ug
b25lIGxvb2sgYW5kIHJlamVjdCBpdC4gIFdlIGhhdmUgdG8gbWFrZSBhIGRl
Y2lzaW9uOg0Kc2hvdWxkIHdlIGdpdmUgdXAgdHJ5aW5nIHRvIHNpbXBsaWZ5
IHRoaXMgYW5kIGp1c3QgcHVzaCBpdCBub3cuDQoNClN0ZXBoYW4gc3Bva2Ug
aW4gZmF2b3Igb2YgdHJ5aW5nIHRvIGdpdmUgdGhpcyBhIHNob3QgYXQgbGFz
dCBjYWxsLiAgSGUNCnNlZXMgdGhlIGNvbXBsZXhpdHkgYXJndW1lbnQsIGFu
ZCB3b3VsZCBsaWtlIGl0IHRvIGJlIHNpbXBsZXIsIGJ1dA0KdGhpbmtzIHRo
ZXJlIGlzIG5vdCByZWFsIHdheSB0byBtYWtlIGl0IHNpbXBsZXIuICBGb3Ig
ZXhhbXBsZSwgaWYgdGhlDQplbGVtZW50YXJ5IHN0cmVhbSBzZWN0aW9uIHdl
cmUgc3BsaXQgb3V0IGZyb20gdGhlIFNMIHBhY2tldGl6YXRpb24sDQp0aGVu
IHBlb3BsZSB3b3VsZCBjb21lIGJhY2sgYW5kIHN0YXJ0IGFza2luZyBmb3Ig
dGhlIG1pc3NpbmcgcGFydA0KYWdhaW4uICBUaGUgZmFjdCB0aGF0IHBlb3Bs
ZSBhcmUgaW1wbGVtZW50aW5nIGl0IGluZGljYXRlcyB0aGF0IHRoZXJlDQpp
cyBpbnRlcmVzdCBpbiB0aGUgaW5kdXN0cnkuICBXZSBjYW4ndCBtYWtlIGEg
anVkZ21lbnQgb24gd2hldGhlciBpdA0KaXMgdGVjaG5pY2FsbHkgc291bmQg
d2l0aG91dCBzZWVpbmcgc2V2ZXJhbCBpbXBsZW1lbnRhdGlvbnMgb2YgaXQs
IGFuZA0KdGhpcyB3b24ndCBoYXBwZW4gdW50aWwgaXQgaXMgcHVibGlzaGVk
IGFzIGFuIFJGQy4NCg0KU3RldmUgQ2FzbmVyIGFza2VkIGZvciBjb25zZW5z
dXMgZnJvbSB0aGUgcm9vbS4gIFRoZXJlIHdhcyBhIHNsaWdodA0KaHVtIGZv
ciBwcm9jZWVkaW5nIHRvIGxhc3QgY2FsbC4gIENvbGluJ3MgZWRpdG9yaWFs
IHJldmlzaW9ucyB3aWxsIGJlDQp0YWtlbiBhcyBwYXJ0IG9mIGxhc3QgY2Fs
bCBjb21tZW50cy4NCg0KUGhpbGlwcGUgY29uY2x1ZGVkIGhpcyBwcmVzZW50
YXRpb24gd2l0aCB0aGUgc3RhdHVzIG9mIHRoZSBzaW1wbGUNCmRyYWZ0LCBk
cmFmdC1pZXRmLWF2dC1tcGVnNC1zaW1wbGUtMDAudHh0LiAgQSBmZXcgdGV4
dHVhbA0KY2xhcmlmaWNhdGlvbnMgd2VyZSBtYWRlIGFuZCBhIG5ldyBkcmFm
dCByZXZpc2lvbiBpc3N1ZWQgaW4gU2VwdGVtYmVyDQoyMDAxIGFmdGVyIHRo
ZSBMb25kb24gSUVURiBtZWV0aW5nLiAgQXQgdGhhdCBwb2ludCwgdGhlIHRl
Y2huaWNhbCBzcGVjDQp3YXMgZnJvemVuOyBpbiBmYWN0IGl0IGhhcyBiZWVu
IGNvcHkvcGFzdGVkIGludG8gdGhlIElTTUEgMS4wDQp0ZWNobmljYWwgc3Bl
Y2lmaWNhdGlvbiBhcyBhbiBhcHBlbmRpeCBzaW5jZSBpdCBpcyBub3QgYW4g
UkZDIHlldCwNCndpdGggdGhlIGludGVudGlvbiBvZiByZXBsYWNpbmcgdGhh
dCB3aXRoIGEgcmVmZXJlbmNlIHRvIHRoZSBSRkMNCmxhdGVyLiAgRm9yIHRo
aXMgZG9jdW1lbnQgYXMgd2VsbCwgaGUgYXNrcyB0byBnbyB0byBXRyBsYXN0
IGNhbGwuDQoNClN0ZXBoYW4gd2FzIGFnYWluc3QgcnViYmVyIHN0YW1waW5n
IGEgZG9jdW1lbnQgdGhhdCBoYXMgYmVlbiBmcm96ZW4gYnkNCmFub3RoZXIg
Z3JvdXAuICBIaXMgY29uY2VybiB3YXMgdHJpZ2dlcmVkIGJ5IGEgc2ltaWxh
ciBzaXR1YXRpb24gaW4NCnRoZSBJVFUgd2hlcmUgdGhlIHRleHQgb2YgYSBk
cmFmdCB3YXMgaW5jb3Jwb3JhdGVkIGludG8gSC4yMjUuMCwgYnV0DQp0aGUg
c2VtYW50aWNzIG9mIG9uZSBmaWVsZCBjaGFuZ2VkIGJlZm9yZSB0aGUgZHJh
ZnQgd2FzIHB1Ymxpc2hlZCBhcw0KUkZDIDIxOTAuICBUaGUgcmVzdWx0IHdh
cyB0aGF0IGEgc2Vjb25kIGNvZGUgcG9pbnRzIGhhZCB0byBiZSBhc3NpZ25l
ZA0KZm9yIHRoZSBSRkMgMjE5MCBwYXlsb2FkIGZvcm1hdC4gIEhlIHdhbnRz
IHRvIGF2b2lkIGhhdmluZyB0aGlzIGhhcHBlbg0KYWdhaW4uICBQaGlsaXBw
ZSBhbmQgRGF2ZSBTaW5nZXIgYm90aCBzYWlkIHRoZXkgYmVsaWV2ZSB0aGlz
IHNpdHVhdGlvbg0KaXMgZGlmZmVyZW50LiAgVGhlcmUgaGFzIGJlZW4gYSBs
b3Qgb2YgaW50ZXJhY3Rpb24gd2l0aCB0aGUgSUVURiBpbg0KdGhlIGRldmVs
b3BtZW50IG9mIHRoZSBwYXlsb2FkIGZvcm1hdC4gIFRoZSBJU01BIHdvdWxk
IG11Y2ggcHJlZmVyIHRvDQpyZWZlcmVuY2UgdGhlIFJGQy4gIElmIHRoZXJl
IGFyZSBjaGFuZ2VzIHRoYXQgb2NjdXIgaW4gdGhlIFJGQw0KcHJvY2Vzcywg
dGhvc2Ugd2lsbCBiZSBhY2NvbW1vZGF0ZWQgaW4gdmVyc2lvbiAxLjEgb2Yg
dGhlIElTTUEgc3BlYy4NCg0KQ29saW4gc2FpZCB0aGUgbWFpbiBpc3N1ZSBm
b3IgdGhlIGxhc3QgY2FsbCBpcyB0byBtYWtlIHN1cmUgdGhpcyBkcmFmdA0K
aXMgYWJzb2x1dGVseSBjb25zaXN0ZW50IHdpdGggdGhlIGdlbmVyaWMgZHJh
ZnQsIGFuZCBhc2tlZCBmb3Igb3RoZXINCnBlb3BsZSBpbiB0aGUgZ3JvdXAg
dG8gZG8gc29tZSB2ZXJ5IG5pdC1waWNreSBwcm9vZnJlYWRpbmcgb2YgYm90
aA0KZHJhZnRzLiAgUGhpbGlwcGUgYmVsaWV2ZXMgdGhpcyBpcyBub3QgbGlr
ZWx5IHRvIGJlIGEgcHJvYmxlbSBiZWNhdXNlDQp0aGUgY29udHJvdmVyc2lh
bCBpc3N1ZXMgaW4gdGhlIGdlbmVyaWMgZHJhZnQgYXJlIHRoZSBvbmVzIHdo
aWNoIGFyZQ0KZXhjbHVkZWQgZnJvbSB0aGUgc2ltcGxlIGRyYWZ0Lg0KDQpU
aG9zZSBhdCB0aGUgbWVldGluZyBodW1tZWQgaW4gYWdyZWVtZW50IGZvciBp
c3N1aW5nIFdHIGxhc3QgY2FsbC4NClN0ZXZlIHN0YXRlZCBhIHJlbWluZGVy
IHRoYXQgdGhlIGh1bXMgd2UgdGFrZSBpbiB0aGUgbWVldGluZyBhcmUgb25s
eQ0KcHJlbGltaW5hcnkgYWdyZWVtZW50OyB0aGUgZmluYWwgZGVjaXNpb25z
IGFyZSBtYWRlIG9uIHRoZSBtYWlsaW5nDQpsaXN0Lg0KDQpUaGUgdGhpcmQg
cGF5bG9hZCBmb3JtYXQgaXMgZHJhZnQtY3VyZXQtYXZ0LXJ0cC1tcGVnNC1m
bGV4bXV4LTAyLnR4dA0KZm9yIE1QRUctNCBGbGV4TXV4IHN0cmVhbXMsIHBy
ZXNlbnRlZCBieSBDYXRoZXJpbmUgUm91eC4gIFRoaXMgcGF5bG9hZA0KZm9y
bWF0IGlzIHNlcGFyYXRlIGZyb20gdGhlIG90aGVycyBhbmQgd291bGQgYmUg
aWRlbnRpZmllZCBieSBhIG5ldw0KTUlNRSBzdWJ0eXBlIG5hbWUgIm1wZWc0
LWZsZXhtdXgiLiAgVGhlIG1vdGl2YXRpb24gaXMgdGhhdCB0aGVyZSBtYXkN
CmJlIGEgbGFyZ2UgbnVtYmVyIG9mIGVsZW1lbnRhcnkgc3RyZWFtcyBpbiBh
IHNjZW5lLCBzbyB0aGUgRmxleE11eA0KbXVsdGlwbGV4ZXMgYWxsIG9mIHRo
b3NlIGludG8gb25lIFJUUCBzdHJlYW0uICBUaGUgcGF5bG9hZCBmb3JtYXQN
Cml0c2VsZiBpcyBzaW1wbGU6IGFuIGludGVncmFsIG51bWJlciBvZiBGbGV4
TXV4IHBhY2tldHMgYXJlIHBhY2tlZA0KaW50byBvbmUgUlRQIHBhY2tldC4g
IFRoZXJlIGlzIG5vIG5lZWQgZm9yIGZyYWdtZW50YXRpb24gYmVjYXVzZQ0K
ZnJhZ21lbnRhdGlvbiBpcyBoYW5kbGVkIGluIHRoZSBTTCBwYWNrZXRzLg0K
DQpUaGUgY29tcGxpY2F0aW9ucyBhcmlzZSBmcm9tIHRoZSBmYWN0IHRoYXQg
YXMgRmxleE11eCBpcyB1c2VkIG9uIG90aGVyDQpjaGFubmVscywgc3RyZWFt
cyB0aGF0IHJlcXVpcmUgcmVsaWFibGUgdHJhbnNtaXNzaW9uIGFuZCB0aG9z
ZSB0aGF0DQpkb24ndCBhcmUgYWxsIG11bHRpcGxleGVkIHRvZ2V0aGVyIGlu
dG8gb25lIHN0cmVhbS4gIEluIGdlbmVyYWwsIHRoaXMNCndvbid0IHByb3Zp
ZGUgc2F0aXNmYWN0b3J5IHBlcmZvcm1hbmNlIG9uIElQIG5ldHdvcmtzLiAg
SW4gZmFjdCwgYm90aA0KdGhlIGdlbmVyaWMgYW5kIEZsZXhNdXggcGF5bG9h
ZCBmb3JtYXRzIGhhdmUgdGhlIHByb2JsZW0gdGhhdCB0aGV5IGNhbg0KZW5j
YXBzdWxhdGUgc3RyZWFtcyB3aGljaCBtdXN0IGJlIGNvbW11bmljYXRlZCBy
ZWxpYWJseSwgeWV0IHRoZXkNCmRvbid0IHByb3ZpZGUgcmVsaWFibGUgdHJh
bnNwb3J0LiAgVGhpcyBtdXN0IGJlIGFkZHJlc3NlZCBieSBhDQpjb21iaW5h
dGlvbiBvZiBhbiAiYXBwbGljYWJpbGl0eSBzdGF0ZW1lbnQiIGZvciB0aGUg
ZW52aXJvbm1lbnQgaW4NCndoaWNoIHRoZSBwYXlsb2FkIGZvcm1hdCB3aWxs
IHdvcmssIGFuZCB0aGUgcmVzdHJpY3Rpb25zIG9uIHRoZQ0KY29udGVudCBv
ZiB0aGUgcGF5bG9hZCB0aGF0IGFyZSByZXF1aXJlZCB0byBhbGxvdyBpdCB0
byB3b3JrLiAgVGhyZWUNCmlzc3VlcyB3ZXJlIGlkZW50aWZpZWQgZm9yIEZs
ZXhNdXg6DQoNCiAxLiBJdCBtYXkgYmUgbmVjZXNzYXJ5IHRvIHNlbmRpbmcg
dHdvIHR5cGVzIG9mIEZsZXhNdXgsIG9uZSBvdmVyIFJUUA0KICAgIGZvciBh
dWRpbyBhbmQgdmlkZW8gZGF0YSwgYW5kIGFub3RoZXIgdXNpbmcgVENQIG9y
IHNvbWUgb3RoZXINCiAgICBtZWNoYW5pc20gdG8gYWNoaWV2ZSBlcnJvci1m
cmVlIHRyYW5zbWlzc2lvbiBvZiBTeXN0ZW0gZGF0YSBzdWNoDQogICAgYXMg
SU9EIGFuZCBCSUZTLiAgSW4gdGhhdCBjYXNlLCB0aGUgZHJhZnQgbXVzdCBz
cGVjaWZ5IGhvdyB0aGUgdHdvDQogICAgd2lsbCBiZSBzeW5jaHJvbml6ZWQg
YW5kIHdoYXQgdG8gZG8gd2hlbiB0aGUgVENQIHN0cmVhbSBpcyBkZWxheWVk
DQogICAgbW9yZSB0aGFuIHRoZSBSVFAgc3RyZWFtLg0KDQogMi4gVGhlIGNv
bmZpZ3VyYXRpb24gb2YgdGhlIEZsZXhNdXggaXRzZWxmIG1heSBiZSBzdGF0
aWMgYW5kIHNpZ25hbGVkDQogICAgb3V0LW9mLWJhbmQsIGUuZy4sIHdpdGgg
U0RQLiAgKFRoZSBzbGlkZXMgcHJvcG9zZSBhIG5ldyBTRFAgbWVkaWENCiAg
ICBhdHRyaWJ1dGUgYT1tcGVnNC1mbGV4bXV4aW5mbywgYnV0IGFzIGEgcmVz
dWx0IG9mIGRpc2N1c3Npb25zDQogICAgYmVmb3JlIHRoZSBtZWV0aW5nLCB0
aGUgYT1mbXRwIGF0dHJpYnV0ZSB3aWxsIGJlIHVzZWQgaW5zdGVhZC4pDQog
ICAgQWx0ZXJuYXRpdmVseSwgaXQgbWF5IGJlIGR5bmFtaWMgd2l0aCBjb25m
aWd1cmF0aW9uIGNoYW5nZXMNCiAgICB0cmFuc21pdHRlZCBpbi1iYW5kLiAg
SW4gdGhlIGxhdHRlciBjYXNlLCB0aGUgY2hhbmdlcyBtdXN0IGJlDQogICAg
dHJhbnNtaXR0ZWQgd2l0aG91dCBlcnJvcnMgb3Igc3Vic2VxdWVudCBkZWNv
ZGluZyBvZiBwYWNrZXRzIHdpbGwNCiAgICBwcm9kdWNlIGdhcmJhZ2UuDQoN
CiAzLiBBcyBjdXJyZW50bHkgc3BlY2lmaWVkLCB0aGUgUlRQIHRpbWVzdGFt
cCBpbmRpY2F0ZXMgdGhlDQogICAgdHJhbnNtaXNzaW9uIHRpbWUgb2YgdGhl
IFJUUCBwYWNrZXQuICBUaGlzIGNhbiBiZSB1c2VkIGZvciBqaXR0ZXINCiAg
ICBtZWFzdXJlbWVudCBhbmQgcmVtb3ZhbC4gIEhvd2V2ZXIsIGJlY2F1c2Ug
dGhlIGNsb2NrIGlzDQogICAgaW5kZXBlbmRlbnQgb2YgdGhlIENUUyBhbmQg
RFRTIHRpbWVzdGFtcHMgb2YgdGhlIFNMIGxldmVsLCB0aGUgUlRQDQogICAg
dGltZXN0YW1wIGNhbid0IGJlIHVzZWQgdG8gc3luY2hyb25pemUgd2l0aCBv
dGhlciBSVFAgc3RyZWFtcy4NCg0KRm9yIHRoZSBzZWNvbmQgaXNzdWUsIFBo
aWxpcHBlIGFkZGVkIHRoYXQgaXQgaXMgcG9zc2libGUgdG8gc2VuZA0KY29u
ZmlndXJhdGlvbiBjaGFuZ2VzIGVhcmx5IGFuZCB0ZWxsIHdoZW4gdGhleSBi
ZWNvbWVzIHZhbGlkLiAgQnV0DQpTdGV2ZSBzdGF0ZWQgdGhhdCBzb21lIGZv
cm0gb2YgYWNrIHdvdWxkIGJlIG5lZWQgdG8gY29uZmlybSB0aGF0IHRoZQ0K
bmV3IGNvbmZpZ3VyYXRpb24gd2FzIHJlY2VpdmVkIGJlZm9yZSBzdGFydGlu
ZyB0byBzZW5kIHBhY2tldHMgaW4gdGhhdA0KY29uZmlndXJhdGlvbi4gIFBo
aWxpcHBlIHJlcGxpZWQgdGhhdCB0aGUgdGltZSBpdCB0YWtlcyB0byBkbyB0
aGUNCmhhbmRzaGFrZSAodGhlIGFjaykgaXMgdW5ib3VuZGVkLCBidXQgRmxl
eE11eCBpcyBkZXNpZ25lZCBzdWNoIHRoYXQgYQ0KY2hhbmdlIHRvIHRoZSBj
b25maWd1cmF0aW9uIG1pZ2h0IGJlIG1hZGUgZXZlcnkgNTBtcyBhbmQgaXQg
aGFzIHRvDQpoYXBwZW4gcmlnaHQgb24gdGltZS4gIFRoZSByb3VuZC10cmlw
IGRlbGF5IG1heSBiZSBleGNlc3NpdmUuICBTdGV2ZQ0KcG9pbnRlZCBvdXQg
dGhhdCwgYnkgZGVmaW5pdGlvbiwgcmVsaWFibGUgY29tbXVuaWNhdGlvbiBy
ZXF1aXJlcw0KdW5ib3VuZGVkIHRpbWUuICBUaGlzIGlzIGEgZnVuZGFtZW50
YWwgcHJvYmxlbSB3aXRoIHRyeWluZyB0byB0YWtlDQpzb21ldGhpbmcgdGhh
dCB3YXMgb3JpZ2luYWxseSBpbnRlbmRlZCBmb3IgY2FycmlhZ2Ugb3ZlciBh
IGNpcmN1aXQgYW5kDQp0cnlpbmcgdG8gcHV0IGl0IG9uIElQIGFuZCBleHBl
Y3QgdGhhdCBpdCB3aWxsIHdvcmsuICBZb3UgaGF2ZSBtYWtlDQpzb21lIGFj
Y29tbW9kYXRpb25zLg0KDQpEYXZlIFNpbmdlciBzdGF0ZWQgdGhhdCBtaXNk
ZWNvZGluZyBwYWNrZXRzIGR1ZSB0byBhIGxvc3QNCmNvbmZpZ3VyYXRpb24g
cGFja2V0IGlzIHVuYWNjZXB0YWJsZS4gIEhlIHN1Z2dlc3RlZCB0aGF0IG9u
ZSB3YXkgdG8NCmF2b2lkIHRoaXMgaXMgdG8gcHV0IGEgY29uZmlndXJhdGlv
biBzZWVkIChnZW5lcmF0aW9uKSBpbiBldmVyeQ0KcGFja2V0LiAgSWYgeW91
IHNlZSB0aGUgc2VlZCBjaGFuZ2UgYW5kIHlvdSBoYXZlIG5vdCByZWNlaXZl
ZCB0aGUNCmNvcnJlc3BvbmRpbmcgY29uZmlndXJhdGlvbiwgdGhlbiB5b3Ug
ZG9uJ3QgZGVjb2RlIGl0LiAgU3RldmUgYWdyZWVkDQp0aGF0IGEgZ2VuZXJh
dGlvbiBudW1iZXIgY291bGQgYmUgcGFydCBvZiB0aGUgZW5jYXBzdWxhdGlv
biBvZiBGbGV4TXV4DQppbnRvIFJUUCwgYnV0IHRoZXJlIGFyZSBhIG51bWJl
ciBvZiBpc3N1ZXMgbGlrZSB0aGlzIHRoYXQgbXVzdCBiZQ0Kd29ya2VkIHRo
cm91Z2ggYmVmb3JlIHRoaXMgY2FuIGJlIGEgdmFsaWQgcGF5bG9hZCBmb3Jt
YXQuICBJdCBpcyBhDQpjb21iaW5hdGlvbiBvZiB3b3JraW5nIG91dCBtZWNo
YW5pc21zIHRvIHNvbHZlIHByb2JsZW1zIGFuZCBleHByZXNzaW5nDQpyZXN0
cmljdGlvbnMgb24gdGhlIGRvbWFpbiB0byB3aGljaCB0aGUgcGF5bG9hZCBm
b3JtYXQgY2FuIGJlIGFwcGxpZWQNCnNpbmNlIHRoZXJlIGFyZSBzb21lIHBy
b2JsZW1zIHdlIGNhbid0IGZpeC4NCg0KRGF2ZSBpcyBhbHNvIGNvbmNlcm5l
ZCBhYm91dCB0aGUgdGhpcmQgaXNzdWUsIHRpbWVzdGFtcHMuICBGb3INCmV4
YW1wbGUsIGlmIHlvdSB3YW50IHRvIHVzZSBGbGV4TXV4IHRvIHNlbmQgdGlu
eSBhdWRpbyBwYWNrZXRzLCBidXQNCnlvdSB3YW50IHRvIHNlbmQgdmlkZW8g
d2l0aCBpdCBmb3Igd2hpY2ggRmxleE11eCBpcyBpbmFwcHJvcHJpYXRlLCB5
b3UNCmNhbid0IHNlbmQgaXQgYXMgYSBzZXBhcmF0ZSBSVFAgc3RyZWFtIGFu
ZCB1c2UgUlRQIG1ldGhvZHMgdG8NCnN5bmNocm9uaXplLiAgVGhlIG90aGVy
IE1QRUctNCBwYXlsb2FkIGZvcm1hdHMgY2FuIGJlIHN5bmNocm9uaXplZA0K
d2l0aCBHU00gb3IgSDI2MyBvciBvdGhlciBlbmNvZGluZ3MgY2FycmllZCBp
biBSVFAsIGFuZCBzbyBzaG91bGQNCkZsZXhNdXguDQoNClN0ZXZlIGFncmVl
ZCB0aGF0IGlmIHRoZSB0cmFuc21pc3Npb24gdGltZXN0YW1wIGlzIG5vdCBy
ZWFsbHkgcmVxdWlyZWQNCnRvIGRlaml0dGVyIHRoZSBwYWNrZXRzLCBvciBp
ZiBpdCdzIG9ubHkgYSBsaXR0bGUgYml0IGhlbHBmdWwsIHRoZW4NCmNlcnRh
aW5seSBwaWNraW5nIHNvbWV0aGluZyBtb3JlIHVzZWZ1bCBhcyB0aGUgdGlt
ZXN0YW1wIHNvdXJjZSBpcyBhDQpnb29kIGlkZWEuICBUaGUgZGlmZmljdWx0
eSBpcyB0aGF0IHdoZW4gbWFueSBzdHJlYW1zIHRoYXQgZG9uJ3QgaGF2ZSBh
DQpjb21tb24gdGltZSByZWZlcmVuY2UgYXJlIG11bHRpcGxleGVkIHRvZ2V0
aGVyLCB0aGVuIGhvdyBkbyB5b3UgY2hvb3NlDQp3aGljaCB0aW1lc3RhbXAg
aXMgdGhlIHJlZmVyZW5jZT8gIFBoaWxpcHBlIGV4cGxhaW5lZCB0aGF0IG9u
ZSBvZiB0aGUNCnJlYXNvbnMgZm9yIHRoaXMgZGVzaWduIGNob2ljZSBpcyB0
aGF0IFNMIHBhY2tldHMgdGhhdCBhcmUgbm90IHRoZQ0KZmlyc3QgcGFydCBv
ZiBhbiBhY2Nlc3MgdW5pdCBkbyBub3QgY2FycnkgdGhlIHRpbWVzdGFtcC4g
IEEgYm94IGFjdGluZw0KYXMgYSB0cmFuc2xhdG9yIHJlY2VpdmluZyBhIEZs
ZXhNdXggc3RyZWFtIG92ZXIgYSBjaXJjdWl0IGFuZA0KdHJhbnNtaXR0aW5n
IG9uIFJUUCBjb3VsZCBub3QgYXNzaWduIGEgdGltZXN0YW1wIHRvIGVhY2gg
U0wgcGFja2V0Lg0KSG93ZXZlciwgaGUgZGlzYWdyZWVkIHdpdGggdGhhdCBh
c3N1bXB0aW9uIGFuZCBzdWdnZXN0ZWQgdGhhdCBldmVuDQp0aG91Z2ggdGhl
IFNMIHBhY2tldHMgd2l0aGluIHRoZSBGbGV4TXV4IG1heSBoYXZlIGRpZmZl
cmVudA0KdGltZXN0YW1wcywgdGhlIHN5c3RlbSBzaG91bGQgdXNlIGEgcnVs
ZSBzdWNoIGFzIHVzaW5nIHRoZSBzbG93ZXN0DQpvbmUuICBEYXZlIHdlbnQg
ZnVydGhlciB0byBzdWdnZXN0IHRoYXQgYWxsIHRoZSB0aW1lc3RhbXBzIGlu
c2lkZSB0aGUNCkZsZXhNdXggcGFja2V0IHNob3VsZCBiZSByZWNhbGN1bGF0
ZWQgcmVsYXRpdmUgdG8gdGhlIFJUUCB0aW1lc3RhbXAuDQpUaGF0IGNhbGN1
bGF0aW9uIGNvdWxkIGJlIHVuZG9uZSBhdCB0aGUgb3RoZXIgZW5kIGlmIGRl
c2lyZWQuICBUaGVuIGlmDQp0aGUgUlRQIHRpbWVzdGFtcCBnZXRzIG1vdmVk
LCBldmVyeXRoaW5nIG1vdmVzIHdpdGggaXQsIGJ1dCB0aGluZ3MNCnRoYXQg
d2VyZSBzdXBwb3NlZCB0byBiZSBzeW5jaHJvbml6ZWQgY2FuIHN0YXkgc3lu
Y2hyb25pemVkLg0KDQoNClJUUCBwYXlsb2FkIGZvcm1hdCBmb3IgR1NNIEVG
UiBzcGVlY2gNCg0KUGV0ZXIgQmFyYW55IHByZXNlbnRlZCBkcmFmdC1iYXJh
bnktYXZ0LWVmci0wMC50eHQsIGEgcHJvcG9zYWwgZm9yIGENCm5ldyBwYXls
b2FkIGZvcm1hdCBmb3IgR1NNIEVGUiBjb2RlZCBzcGVlY2guICBJdCBzaG91
bGQgYmUgbm90ZWQgdGhhdA0KU2VjdGlvbiA0LjUuOSBvZiBkcmFmdC1pZXRm
LWF2dC1wcm9maWxlLW5ldy0xMi50eHQgYWxyZWFkeSBkZWZpbmVzIGENCnBh
eWxvYWQgZm9ybWF0IGZvciB0aGlzIGNvZGVjLCBzbyB0aGUgbWFpbiBxdWVz
dGlvbiBmb3IgdGhpcyBwcm9wb3NhbA0KaXMgd2hldGhlciBhIGRpZmZlcmVu
dCBwYXlsb2FkIGlzIGp1c3RpZmllZC4NCg0KVGhlIG1vdGl2YXRpb24gZm9y
IHRoaXMgcGF5bG9hZCBmb3JtYXQgaXMgdG8gc3VwcG9ydCBhIGxhcmdlIG51
bWJlciBvZg0KbGVnYWN5IEdTTSB0cmFuc2NlaXZlcnMgYWxyZWFkeSBpbiB0
aGUgZmllbGQgYXMgcGFydCBvZiBhIHRyYW5zaXRpb24NCnRvIEdFUkFOIHBh
Y2tldCBzd2l0Y2hlZCBhcmNoaXRlY3R1cmUuICBUaGVzZSBkZXZpY2VzIGlt
cGxlbWVudCB0aGUNCkVGUiBzcGVlY2ggY29kZWMgd2l0aCBpdHMgcGFydGlj
dWxhciBmb3JtIG9mIGludGVybGVhdmluZyBhbmQgb3RoZXINCmNoYXJhY3Rl
cmlzdGljcy4gIFRoZSBleGlzdGluZyBFRlIgcGF5bG9hZCBmb3JtYXQgZG9l
cyBub3QgcHJvdmlkZSBhDQptZWFucyB0byBjb252ZXkgYW4gaW5kaWNhdGlv
biBvZiBkYW1hZ2VkIGZyYW1lcyB0aGF0IG1heSBiZSBwcm92aWRlZA0KYnkg
YW4gcmFkaW8gaW50ZXJmYWNlIGF0IHRoZSBwb2ludCB3aGVyZSBpdCBpcyBn
YXRld2F5ZWQgdG8gdGhlIHBhY2tldA0KbmV0d29yay4gIFRoZSBwdXJwb3Nl
IG9mIHRoZSBkYW1hZ2VkIGZyYW1lIGluZGljYXRvciBpcyB0byBhbGxvdyB0
aGUNCmRlY29kZXIgYXQgdGhlIFJUUCByZWNlaXZlciB0byBtYWtlIHBhcnRp
YWwgdXNlIG9mIHRoZSBiaXRzIGluIHRoZQ0KZGFtYWdlZCBmcmFtZSBhcyBv
cHBvc2VkIHRvIHRyZWF0aW5nIHRoZSBmcmFtZSBhcyBhIGNvbXBsZXRlIGxv
c3MuDQpUaGUgZHJhZnQgcHJvcG9zZXMgYSBwYXlsb2FkIGZvcm1hdCBzaW1p
bGFyIHRvIHRoZSBleGlzdGluZyBvbmUgYnV0DQpyZXBsYWNlcyB0aGUgNC1i
aXQgc2lnbmF0dXJlIGF0IHRoZSBoZWFkIG9mIGVhY2ggZnJhbWUgd2l0aCBh
IHNldCBvZg0KZmxhZ3MuICBJbiB0aGUgLTAwIGRyYWZ0LCBqdXN0IG9uZSBm
bGFnIGJpdCAoUSkgaXMgZGVmaW5lZCB0byBpbmRpY2F0ZQ0KZ29vZCB2cy4g
ZGFtYWdlZCBmcmFtZXMsIGJ1dCBpbiB0aGUgcHJlc2VudGF0aW9uIGl0IHdh
cyBwcm9wb3NlZCB0bw0KY29weSA0IGJpdHMgZnJvbSBhbiBleGlzdGluZyBj
aXJjdWl0IGludGVyZmFjZSBiZXR3ZWVuIGJhc2Ugc3RhdGlvbnMNCmFuZCBt
b2JpbGUgc3dpdGNoaW5nIGNlbnRlcnMuICBUaG9zZSBiaXRzIGFsc28gaW5k
aWNhdGUgU0lEIGZyYW1lcy4NCg0KU3RldmUgQ2FzbmVyIGFza2VkIHdoeSBu
b3QgdXNlIHRoZSBFRlIgbW9kZSB3aXRoaW4gdGhlIEFNUiBjb2RlYywNCnNp
bmNlIHRoZSBBTVIgcGF5bG9hZCBmb3JtYXQgc3VwcG9ydHMgdGhlIFEgYml0
LiAgVGhlIHJlYXNvbiBpcyB0aGF0DQp0aGUgZXhpc3RpbmcgR1NNIGRldmlj
ZXMgZG8gaW1wbGVtZW50IEVGUiBhbmQgaXRzIGZyYW1pbmcsIGJ1dCBub3Qg
QU1SDQpmcmFtaW5nLg0KDQpDb2xpbiBQZXJraW5zIHN1Z2dlc3RlZCB0aGF0
LCB3aXRoIGFuIGFwcHJvcHJpYXRlIGNob2ljZSBmb3IgdGhlIHNlbnNlDQpv
ZiB0aGUgc3RhdHVzIGJpdHMsIGluIHRoZSBjYXNlIG9mIGEgZ29vZCBwYWNr
ZXQgdGhlIGJpdCBwYXR0ZXJuIHdvdWxkDQpiZSBleGFjdGx5IHRoZSBzYW1l
IGFzIHRoZSA0LWJpdCBzaWduYXR1cmUgaW4gdGhlIGV4aXN0aW5nIHBheWxv
YWQNCmZvcm1hdC4gIElmIG9uZSBvciBtb3JlIHN0YXR1cyBiaXRzIGNoYW5n
ZWQgdG8gaW5kaWNhdGUgYSBkYW1hZ2VkDQpmcmFtZSwgdGhlbiBpbXBsZW1l
bnRhdGlvbnMgb2YgdGhlIGV4aXN0aW5nIHBheWxvYWQgZm9ybWF0IHNob3Vs
ZA0KcmVqZWN0IHRoZSBmcmFtZSBhcyBtYWxmb3JtZWQuICBUaGlzIHdvdWxk
IGFsbG93IGtlZXBpbmcgYSBzaW5nbGUNCnBheWxvYWQgZm9ybWF0IGFuZCBl
eHRlbmRpbmcgaXQgaW4gYSBiYWNrd2FyZC1jb21wYXRpYmxlIG1hbm5lci4N
Cg0KQSBsYXJnZXIgZGlzY3Vzc2lvbiBjZW50ZXJlZCBvbiB0aGUgcXVlc3Rp
b24gb2Ygd2hldGhlciBhZGRpbmcgdGhlDQpzdGF0dXMgYml0cyB3b3VsZCBw
cm92aWRlIGEgc3VmZmljaWVudCBpbXByb3ZlbWVudCBpbiBwZXJmb3JtYW5j
ZSB0bw0KanVzdGlmeSBoYXZpbmcgYSBzZWNvbmQgcGF5bG9hZCBmb3JtYXQu
ICBJbiBwYXJ0aWN1bGFyLCBkb2VzIGENCnJlY2VpdmVyIHByb2Nlc3MgYW55
IG9mIHRoZSBiaXRzIGluIGEgZGFtYWdlZCBmcmFtZSwgb3Igc2ltcGx5IGRp
c2NhcmQNCnRoZW0gYW5kIGRvIGZyYW1lIHN1YnN0aXR1dGlvbi4gIElmIHRo
ZSBsYXR0ZXIsIHRoZW4gdGhlIFJUUCBzZXF1ZW5jZQ0KbnVtYmVyIGFscmVh
ZHkgcHJvdmlkZXMgdGhlIG1lYW5zIHRvIGluZGljYXRlIG1pc3NpbmcgcGFj
a2V0cy4gIFRoZQ0KY2xhaW0gd2FzIG1hZGUgdGhhdCB0aGUgTU9TIChpbnRl
bGxpZ2liaWxpdHkpIHNjb3JlcyB3ZXJlIGRyYW1hdGljYWxseQ0KaW1wcm92
ZWQgYnkgdXNpbmcgdGhlIHBhcnRpYWwgaW5mb3JtYXRpb24gb2YgZGFtYWdl
ZCBmcmFtZXMsIGFsdGhvdWdoDQp0aGF0IGRhdGEgd2FzIG5vdCBhdmFpbGFi
bGUgaW4gdGhlIHByZXNlbnRhdGlvbi4NCg0KSXQgd2FzIHVuY2xlYXIgaW4g
dGhlIGRpc2N1c3Npb24gd2hldGhlciB0aGUgbW90aXZhdGlvbiBmb3IgbWFy
a2luZw0KYmFkIGZyYW1lcyB3aXRoaW4gdGhlIGZyYW1lIHNpZ25hdHVyZSBy
YXRoZXIgdGhhbiBqdXN0IHRyZWF0aW5nDQpkYW1hZ2VkIGZyYW1lcyBhcyBs
b3N0ICh1c2luZyB0aGUgUlRQIHNlcXVlbmNlIG51bWJlcikgc3RlbXMgZnJv
bSBhDQpkZXNpcmUgdG8gcGFzcyB0aGUgYmFkIGZyYW1lIGluZGljYXRpb24g
b3ZlciB0aGUgIm9wdGltaXplZCBiZWFyZXINCmNoYW5uZWwiIHdoZXJlIHRo
ZSBJUC9VRFAvUlRQIGhlYWRlcnMgYXJlIHN0cmlwcGVkICgiemVyby1ieXRl
IGhlYWRlcg0KY29tcHJlc3Npb24iKS4gIElmIHNvLCB0aGVuIHRoZSBmb3Jt
YXQgb2YgZnJhbWVzIHNlbnQgb3ZlciB0aGF0DQpjaGFubmVsIGlzIG5vdCBy
ZWFsbHkgYSBjb25jZXJuIGZvciBBVlQuICBSVFAgd2lsbCBiZSB1c2VkIGJl
dHdlZW4gdGhlDQptb2JpbGUgc3lzdGVtIChSTkMpIGFuZCB0aGUgUFNUTiwg
YnV0IHRoZSBmb2xsb3dpbmcgdGhvdWdodCBhcm9zZQ0KZHVyaW5nIHRoZSBw
cmVwYXJhdGlvbiBvZiB0aGVzZSBtaW51dGVzOiB3aHkgbm90IHVzZSBBTVIg
cGF5bG9hZA0KZm9ybWF0IG9uIHRoZSBwb3J0aW9uIG9mIHRoZSBuZXR3b3Jr
IHdoZXJlIFJUUCBpcyByZWFsbHkgY2FycmllZD8gIEFNUg0KYWxyZWFkeSBp
bmNsdWRlcyB0aGUgUSBiaXQgYW5kIGNhbiBjYXJyeSBHU00tRUZSLiAgVGhl
IGNvbWZvcnQgbm9pc2UNCihTSUQpIGZyYW1lcyBhcmUgZGlmZmVyZW50LCBi
dXQgdGhlIHRyYW5zbGF0aW9uIGNvdWxkIGJlIGhhbmRsZWQgYXMNCnBhcnQg
b2YgdGhlIGdhdGV3YXkgZnVuY3Rpb24gdG8gdGhlIGxlZ2FjeSBwb3J0aW9u
cyBvZiB0aGUgc3lzdGVtLg0KVGhhdCB3YXkgdGhlIHVwc3RyZWFtIHBvcnRp
b25zIG9mIHRoZSBzeXN0ZW0gd291bGQgYWxyZWFkeSBoYXZlDQp0cmFuc2l0
aW9uZWQgdG8gdGhlIG5ld2VyIG1vZGUgb2Ygb3BlcmF0aW9uLg0KDQpQZXRl
ciBhc2tlZCBpZiB0aGlzIHBheWxvYWQgZm9ybWF0IGNhbiBiZWNvbWUgYSB3
b3JraW5nIGdyb3VwIGl0ZW0uDQpDb2xpbiBhc2tlZCBmb3IgYSBodW0sIHRo
ZSByZXN1bHQgb2Ygd2hpY2ggc291bmRlZCBsaWtlIG5lYXJseSBub3RoaW5n
DQppbiBib3RoIGRpcmVjdGlvbnMuICBTdGV2ZSBvYnNlcnZlZCB0aGF0IHRo
ZSBwcm9wb3NhbCBzZWVtcyB0byBiZQ0Kc3RpbGwgaW4gZmx1eCwgYW5kIHRo
YXQgaXQgc2hvdWxkIHN0YWJpbGl6ZSBiZWZvcmUgd2UgY29uc2lkZXIgaXQg
YXMgYQ0Kd29ya2luZyBncm91cCBpdGVtLg0KDQpDb2xpbiBzdWdnZXN0ZWQg
dGhhdCBhbm90aGVyIGluZGl2aWR1YWwgZHJhZnQgc2hvdWxkIGJlIHByb2R1
Y2VkIHdoaWNoDQppbmNsdWRlcyB0aGUgZGF0YSBzaG93aW5nIHRoZSBpbXBy
b3ZlbWVudCBpbiBwZXJmb3JtYW5jZSAoTU9TIHNjb3JlcykNCmFzIGEgcmVz
dWx0IG9mIGluY2x1ZGluZyB0aGUgZGFtYWdlZCBmcmFtZSBpbmRpY2F0aW9u
LCBhbmQgdGhlbiBhdCB0aGUNCm5leHQgbWVldGluZyB3ZSdsbCB0YWtlIHVw
IHdoZXRoZXIgd2Ugc2hvdWxkIGNvbnNpZGVyIGl0IGFzIGEgd29ya2luZw0K
Z3JvdXAgaXRlbS4gIEhlIGFsc28gYXNrZWQgdGhhdCB0aGUgaWRlYSBiZSBj
b25zaWRlcmVkIHRvIGNob29zZSB0aGUNCmJpdCBwYXR0ZXJuIHRvIG1hdGNo
IHRoZSBleGlzdGluZyBzaWduYXR1cmUgaW4gdGhlIG5vcm1hbCBjYXNlLg0K
DQoNClJUUCBQYXlsb2FkIEZvcm1hdCBmb3IgRVZSQywgU01WIGFuZCBGcmFt
ZS1CYXNlZCBWb2NvZGVycw0KDQpBZGFtIExpIHByZXNlbnRlZCBkcmFmdC1s
aS1hdnQtdm9jb2Rlci0wMC50eHQgd2hpY2ggaXMgYWN0dWFsbHkgbm90DQpu
ZXcgYmVjYXVzZSBpdCBpcyB0aGUgY29tYmluYXRpb24gb2YgZHJhZnQtaWV0
Zi1hdnQtZXZyYy0wOC50eHQsIHdoaWNoDQpoYXMgZ29uZSB0aHJvdWdoIHNl
dmVyYWwgcmV2aXNpb25zIGFuZCB3YXMgYWNjZXB0ZWQgZm9yIFdHIGxhc3Qg
Y2FsbCwNCndpdGggZHJhZnQtbWF0aGFpLWF2dC1zbXYtMDAudHh0IGFuZCBk
cmFmdC1lc3BlbGllbi1hdnQtY29tbW9uLTAwLnR4dC4NClRoZSBFVlJDIGFu
ZCBTTVYgcGF5bG9hZCBmb3JtYXQgZHJhZnRzIHdlcmUgY29tYmluZWQgYmVj
YXVzZSB0aGV5IHdlcmUNCmVzc2VudGlhbGx5IHRoZSBzYW1lLCBzbyB0aGUg
Y29tYmluZWQgZHJhZnQganVzdCBuZWVkcyB0byBkZWZpbmUgYm90aA0Kc2V0
cyBvZiBwYXlsb2FkIGZvcm1hdCBjb25zdGFudHMgYW5kIGJvdGggTUlNRSBz
dWJ0eXBlIHJlZ2lzdHJhdGlvbnMuDQpBZGRpdGlvbmFsIGluZm9ybWF0aW9u
IHdhcyBhZGRlZCB0byBzcGVjaWZ5IGhvdyB0aGUgcGF5bG9hZCBmb3JtYXQN
CmNvdWxkIGJlIGV4dGVuZGVkIHRvIG90aGVyIHZvY29kZXJzLg0KDQpUaGVy
ZSB3YXMgb25seSBvbmUgdGVjaG5pY2FsIGNoYW5nZS4gIEZvciB0eXBlIDEg
KG9jdGV0LWFsaWduZWQpDQpwYWNrZXRzLCBhIG5ldyBvbmUtb2N0ZXQgaGVh
ZGVyIGlzIGFkZGVkIHRvIGluZGljYXRlIHRoZSBjb3VudCBvZg0KZnJhbWVz
IHByZXNlbnQgYW5kIHRvIGNhcnJ5IHRoZSBmbG93LWNvbnRyb2wgKHJhdGUg
Y29udHJvbCkgYml0cyB3aGljaA0KdXNlZCB0byBiZSByZXBsaWNhdGVkIGlu
IHRoZSBUYWJsZSBvZiBDb250ZW50cyBlbnRyaWVzIGZvciBlYWNoIGZyYW1l
Lg0KVGhhdCBhbGxvd2VkIHRoZSBUb0MgZW50cmllcyB0byBiZSByZWR1Y2Vk
IGZyb20gOCBiaXRzIHRvIDQgYml0cyBlYWNoLA0Kd2l0aCA0IGJpdHMgb2Yg
cGFkZGluZyBhdCB0aGUgZW5kIG9ubHkgaWYgdGhlIGZyYW1lIGNvdW50IGlz
IG9kZC4gIEZvcg0KdHlwZSAyIHBhY2tldHMgKG5vIHBheWxvYWQgaGVhZGVy
LCBzaW5nbGUgZnJhbWUgb25seSksIHRoZXJlIGlzIG5vDQpjaGFuZ2UuDQoN
CkFkYW0gcmVxdWVzdHMgdGhhdCB0aGlzIGRyYWZ0IGJlIGFjY2VwdGVkIGFz
IGEgV0cgaXRlbSBhbmQgdGhhdCBpdA0KcHJvY2VlZCBxdWlja2x5IHRvIFdH
IGxhc3QgY2FsbCBzaW5jZSB0aGUgRVZSQyBkcmFmdCBoYWQgYWxyZWFkeSBi
ZWVuDQphcHByb3ZlZC4NCg0KQ29saW4gUGVya2lucyBleHByZXNzZWQgY29u
Y2VybiB0aGF0IHRoaXMgZHJhZnQgdHJpZXMgdG8gYmUgdG9vDQpnZW5lcmFs
LiAgQ29tYmluaW5nIEVWUkMgYW5kIFNNViBtYWtlcyBzZW5zZSwgYnV0IHRy
eWluZyB0byBleHRlbmQgaXQNCnRvIGZ1dHVyZSwgYXMteWV0LXVuc3BlY2lm
aWVkIGNvZGVjcyBzZWVtcyB0byBiZSBzdHJldGNoaW5nIGl0IGENCmxpdHRs
ZS4gIEl0IG1heSBiZSBtb3JlIGFwcHJvcHJpYXRlIHRvIGxpbWl0IHRoZSBw
YXlsb2FkIGZvcm1hdCB0bw0KanVzdCB0aG9zZSB0d28gY29kZWNzLiAgSWYg
d2UgaGF2ZSBhbm90aGVyIGNvZGVjIGluIHRoZSBmdXR1cmUsIHdlIGNhbg0K
c2xvdCBpdCBpbnRvIHRoaXMgc2FtZSBmcmFtZXdvcmsgaWYgaXQgaXMgYXBw
cm9wcmlhdGUsIGJ1dCB3ZSBkb24ndA0Kd2FudCB0byBlbmNvdXJhZ2UgcGVv
cGxlIHRvIHNob2UtaG9ybiBjb2RlY3MgaW4uICBZb3UncmUgZ29pbmcgdG8g
aGF2ZQ0KdG8gcHJvZHVjZSBhIG5ldyBSRkMgZm9yIGEgbmV3IGNvZGVjIGlu
IGFueSBjYXNlICh0byBkZWZpbmUgdGhlIE1JTUUNCnR5cGUgYW5kIG90aGVy
IHBhcmFtZXRlcnMpLg0KDQpBZGFtIHJlcGxpZWQgdGhhdCB0aGlzIHBheWxv
YWQgZm9ybWF0IGlzIG5vdCBmb3IgZXZlcnkgY29kZWMsIGJ1dCB0aGF0DQpp
dCB0cmllcyB0byBzcGVjaWZ5IGEgc2V0IG9mIGNyaXRlcmlhIGZvciBvdGhl
ciBjb2RlY3MgdGhhdCBtaWdodCB3YW50DQp0byB1c2UgaXMuICBQZW9wbGUg
Y2FuIGNob29zZSB0byB1c2UgdGhpcyBmb3IgZnV0dXJlIGNvZGVjcyB0aGF0
IG1lZXQNCnRoZSBjcml0ZXJpYSwgb3IgbWF5IGRlc2lnbiBzb21ldGhpbmcg
bmV3LiAgQnV0IENvbGluIG5vdGVkIHRoYXQgdGhlDQpzYW1lIGlzIHRydWUg
b2YgZXZlcnkgcGF5bG9hZCBmb3JtYXQgd2UgaGF2ZSwgc28gaXQgaXMgbm90
IG5lY2Vzc2FyeQ0KdG8gZXhwbGljaXRseSBzdGF0ZSB0aGF0IGluIHRoaXMg
ZHJhZnQuICBUaGlzIGRyYWZ0IGlzIG5vdCBleGNlcHRpb25hbA0KaXQgaXRz
IHJldXNhYmlsaXR5OyBpdCBqdXN0IGhhcHBlbnMgdG8gZml0IGEgY2xhc3Mg
b2YgY29kZWNzLiAgUGV0ZQ0KTWNDYW5uIG9ic2VydmVkIHRoYXQgdGhlIHJl
YXNvbiBFVlJDIGFuZCBTTVYgZml0IHRvZ2V0aGVyIGlzIHRoYXQgdGhleQ0K
d2VyZSBib3RoIGRlc2lnbmVkIGZvciBDRE1BLTIwMDAgYWlyIGludGVyZmFj
ZS4gIEEgbmV3IGNvZGVjIGRlc2lnbmVkDQpmb3IgdGhhdCBpbnRlcmZhY2Ug
d291bGQgcHJvYmFibHkgYWxzbyBmaXQuICBNYXliZSBpdCBpcyBpbmFwcHJv
cHJpYXRlDQp0byBiZSBtb3JlIGJyb2FkIHRoYW4gdGhhdC4NCg0KT25lIHF1
ZXN0aW9uIHdhcyB3aGV0aGVyIHRoZSBkZXNpZ25lciBvZiBhIG5ldyBjb2Rl
Y3Mgd291bGQgaGF2ZSB0bw0KcGF5IGZvciBleHBlbnNpdmUgTU9TIHRlc3Rz
IHRvIGp1c3RpZnkgY3JlYXRpbmcgYSBkaWZmZXJlbnQgcGF5bG9hZA0KZm9y
bWF0LCBub3RpbmcgdGhhdCBzdWNoIGRhdGEgd2FzIHJlcXVlc3RlZCBpbiB0
aGUgZGlzY3Vzc2lvbiBvZiBFRlIuDQpTdGV2ZSByZXBsaWVkIHRoYXQgb25l
IGNhbiBhbHdheXMgZGVmaW5lIGEgbmV3IHBheWxvYWQgZm9ybWF0IGZvciBh
DQpuZXcgY29kZWMuICBUaGUgcHVzaGJhY2sgZm9yIEVGUiBpcyBiZWNhdXNl
IHdlIGFscmVhZHkgaGF2ZSBhIHBheWxvYWQNCmZvcm1hdCBmb3IgdGhhdCBj
b2RlYyBhbmQgd2UgcHJlZmVyIG5vdCB0byBoYXZlIG1vcmUgdGhhbiBvbmUg
Zm9yDQppbnRlcm9wZXJhYmlsaXR5IHJlYXNvbnMuDQoNCkl0IHdhcyBhZ3Jl
ZWQgdG8gbWFrZSBhIHJldmlzaW9uIG9mIHRoaXMgYXMgYSB3b3JraW5nIGdy
b3VwIGRvY3VtZW50Lg0KDQoNClJUUCBQYXlsb2FkIEZvcm1hdCBmb3IgQUMt
MyBTdHJlYW1zDQoNCkphc29uIEZsYWtzIHByZXNlbnRlZCBkcmFmdC1mbGFr
cy1hdnQtcnRwLWFjMy0wMC50eHQgd2hpY2ggc3BlY2lmaWVzIGENCm5ldyBw
YXlsb2FkIGZvcm1hdCBmb3IgdGhlIERvbGJ5IERpZ2l0YWwgQUMtMyBjb2Rl
ZCB1c2VkIGZvciBEVkQNCnJlY29yZGluZ3MgYW5kIEFUU0MgZGlnaXRhbCB0
ZXJyZXN0cmlhbCBUViB3aXRoIHVwIHRvIDUuMSBjaGFubmVscyBvZg0KYXVk
aW8uICBBQy0zIGZyYW1lcyBjb250YWluIHN5bmMgYW5kIENSQyBmaWVsZHMg
cGx1cyAxIHRvIDYgYXVkaW8NCmJsb2Nrcywgb25lIGZvciBlYWNoIGNoYW5u
ZWwgb2YgYXVkaW8uICBUaGUgZnJhbWVzIGFyZSBmYWlybHkgbGFyZ2UsDQp3
aGljaCBtZWFucyB0aGV5IG1heSBiZSBmcmFnbWVudGVkLiAgQXMgYSByZXN1
bHQsIHRoZSBSVFAgcGF5bG9hZA0KZm9ybWF0IHVzZXMgZmllbGRzIG9mIHRo
ZSBSVFAgaGVhZGVyIHdpdGggc3RhbmRhcmQgbWVhbmluZ3MgYnV0IGluIGEN
Cm1hbm5lciBtb3JlIGxpa2UgYSB2aWRlbyBjb2RlYyB0aGFuIGFuIGF1ZGlv
IGNvZGVjLiAgVGhlIHRpbWVzdGFtcA0KY29ycmVzcG9uZHMgdG8gdGhlIHNh
bXBsaW5nIGluc3RhbnQgb2YgdGhlIGZpcnN0IGZyYW1lIGNvbnRhaW5lZCBp
bg0KdGhlIHBhY2tldCwgYW5kIG11bHRpcGxlIHBhY2tldHMgbWF5IGhhdmUg
dGhlIHNhbWUgdGltZXN0YW1wIHdoZW4gYQ0KZnJhbWUgaXMgZnJhZ21lbnRl
ZC4gIFRoZSBtYXJrZXIgYml0IGl0IHNldCBvbiBwYWNrZXRzIHRoYXQgY29u
dGFpbg0KdGhlIGxhc3QgZnJhZ21lbnQgb2YgYSBmcmFtZSAob3Igb25lIG9y
IG1vcmUgd2hvbGUgZnJhbWVzKS4gIFRoZXJlIGlzDQphbiA4LWJpdCBwYXls
b2FkLWZvcm1hdC1zcGVjaWZpYyBoZWFkZXIgKG1pc25hbWVkIGEgaGVhZGVy
IGV4dGVuc2lvbg0KaW4gdGhlIHNsaWRlcykgdGhhdCBzcGVjaWZpZXMgdGhl
IG51bWJlciBvZiBmcmFtZXMgY29udGFpbmVkIGluIHRoZQ0KcGFja2V0LCBh
IGZyYWdtZW50IHNlcXVlbmNlIG51bWJlciAodGhlIHNsaWRlcyBlcnJvbmVv
dXNseSBzYXkgZnJhbWUNCnNlcXVlbmNlIG51bWJlciksIGFuZCBhIHJlZHVu
ZGFudCBkYXRhIGZsYWcuDQoNClRoZSBwYWNrZXQgbWF5IGNvbnRhaW4gbXVs
dGlwbGUgZnJhbWVzLCB0aGUgZmlyc3Qgb2Ygd2hpY2ggbWF5IGJlIGENCmZy
YW1lIGZyYWdtZW50LCBidXQgc2luY2UgdGhlIGZyYW1lcyBhcmUgdXN1YWxs
eSBsYXJnZSAocmFuZ2luZyBmcm9tDQo4MCB0byAzODQwIGJ5dGVzKSB0aGVy
ZSB3aWxsIHVzdWFsbHkgYmUgb25seSBvbmUgZnJhbWUgcGVyIHBhY2tldC4g
IEF0DQp0aGUgbGFyZ2UgZW5kLCBvbmUgZnJhbWUgZXhjZWVkcyB0aGUgTVRV
IG9mIG1vc3QgbmV0d29ya3MsIHNvIGZyYW1lcw0KbWF5IGJlIGZyYWdtZW50
ZWQuICBUaGUgZnJhZ21lbnQgc2VxdWVuY2UgbnVtYmVyIGluY3JlbWVudHMg
d2l0aCBlYWNoDQpmcmFnbWVudCBvZiBhIGZyYW1lLCBzdGFydGluZyBmcm9t
IDAuICBBQy0zIGhhcyBhIHJ1bGUgdGhhdCB0aGUgZmlyc3QNCnR3byBhdWRp
byBibG9ja3MgYXJlIGd1YXJhbnRlZWQgdG8gYmUgaW4gdGhlIGZpcnN0IDUv
OHRocyBvZiBhIGZyYW1lLA0Kd2hpY2ggaXMgY292ZXJlZCBieSB0aGUgZmly
c3QgQ1JDLCBzbyBkZWNvZGluZyBjYW4gc3RhcnQgYXQgdGhhdA0KcG9pbnQu
ICBUaGF0IG1ha2VzIGEgbG9naWNhbCBmcmFnbWVudGF0aW9uIHBvaW50IGZv
ciBSVFAgYXMgd2VsbCB3aGVuDQp0aGUgc2l6ZSBpcyBhcHByb3ByaWF0ZSBm
b3IgdGhlIE1UVSwgYWx0aG91Z2ggd2l0aCBSVFAgdGhlcmUgaXMgbm8NCmd1
YXJhbnRlZSB0aGF0IHRoZSByZW1haW5pbmcgMy84dGhzIHdpbGwgYXJyaXZl
Lg0KDQpPbiBmaWxtLCB0aGVyZSBpcyBhIHJlZHVuZGFudCAyLWNoYW5uZWwg
YXVkaW8gdHJhY2sgdGhhdCBpcyB1c2VkIGlmDQp0aGUgNS4xIGNoYW5uZWwg
ZGlnaXRhbCBhdWRpbyB0cmFjayB3ZWFycyBvdXQuICBUaGlzIHBheWxvYWQg
Zm9ybWF0DQpwcm9wb3NlcyBhbiBhbmFsb2dvdXMgcmVkdW5kYW5jeSBtZWNo
YW5pc20gd2hlcmUgcmVkdW5kYW50IGxvd2VyLXJhdGUNCjItY2hhbm5lbCBk
YXRhIGZvciBmcmFtZSBOKzEgaXMgY2FycmllZCBpbiB0aGUgcGFja2V0IGFs
b25nIHdpdGggdGhlDQpwcmltYXJ5IGRhdGEgZm9yIGZyYW1lIE4uICBQcmVz
ZW5jZSBvZiB0aGUgcmVkdW5kYW50IGRhdGEgaXMgaW5kaWNhdGVkDQpieSBh
IGJpdCBpbiB0aGUgcGF5bG9hZCBoZWFkZXIuDQoNClN0ZXZlIENhc25lciBh
c2tlZCBpZiB0aGUgZnJhZ21lbnQgc2VxdWVuY2UgbnVtYmVyIGlzIG5lZWRl
ZCB0byBrbm93DQpob3cgdG8gcGxhY2UgdGhlIGZyYWdtZW50cy4gIFRoZSBS
VFAgc2VxdWVuY2UgbnVtYmVyIHNob3VsZCBiZQ0Kc3VmZmljaWVudCBmb3Ig
cHV0dGluZyB0aGUgZnJhZ21lbnRzIGluIHRoZSBwcm9wZXIgb3JkZXIuICBJ
ZiB5b3UgYWxzbw0KaGF2ZSBhIHJ1bGUgdGhhdCBvbmx5IHRoZSBmaXJzdCBm
cmFtZSBjYW4gYmUgYSBmcmFnbWVudCwgYW5kIGxhdGVyDQpmcmFtZXMgaW4g
YSBwYWNrZXQgbXVzdCBiZSBpbnRlZ3JhbCwgdGhlbiB0aGVyZSBpcyBubyBj
b25mdXNpb24gYWJvdXQNCmhvdyBtYW55IGZyYWdtZW50cyB0aGVyZSBhcmUu
ICAoVGhpcyBwYXlsb2FkIGZvcm1hdCBkb2VzIGluY2x1ZGUgdGhhdA0KcnVs
ZSwgc28gdGhlIGZyYWdtZW50IHNlcXVlbmNlIG51bWJlciBtYXkgbm90IGJl
IG5lZWRlZC4pICBUd28NCmNvbW1lbnRzIGFyaXNlIGluIHRoZSBwcmVwYXJh
dGlvbiBvZiB0aGVzZSBtaW51dGVzOiBpdCBtYXkgYmUgbW9yZQ0KcHJ1ZGVu
dCB0byB1c2UgYSAzMi1iaXQgcGF5bG9hZCBmb3JtYXQgaGVhZGVyIHNpbmNl
IHRoZXNlIGZyYW1lcyBhcmUNCmxhcmdlIHNvIHRoZSBvdmVyaGVhZCBpcyBu
b3Qgc2lnbmlmaWNhbnQuICBUaGUgY3VycmVudCBmaWVsZA0KZGVmaW5pdGlv
bnMgYXJlIHF1aXRlIHNtYWxsLiAgVGhhdCB3b3VsZCBhbHNvIGFsbG93IHJl
cGxhY2luZyB0aGUNCmZyYWdtZW50IHNlcXVlbmNlIG51bWJlciB3aXRoIGEg
ZnJhZ21lbnQgb2Zmc2V0IHNvIHRoYXQgZGF0YSBtYXkgYmUNCnBsYWNlZCBw
cm9wZXJseSBpbiBhIGNvbnRpZ3VvdXMgYnVmZmVyIGV2ZW4gaWYgdGhlIGZy
YWdtZW50cyBhcnJpdmUNCm91dC1vZi1vcmRlci4NCg0KUGhpbGlwcGUgR2Vu
dHJpYyBhc2tlZCBpZiBkZW11bHRpcGxleGluZyBvZiB0aGUgY2hhbm5lbHMg
d2FzDQpjb25zaWRlcmVkLiAgV291bGQgdGhlcmUgYmUgYW4gYWR2YW50YWdl
IGluIHRyYW5zbWl0dGluZyB0aGUgdHdvIG1haW4NCmNoYW5uZWxzIGluIG9u
ZSBSVFAgc3RyZWFtIGFuZCB0aGUgcmVtYWluaW5nIGNoYW5uZWxzIGluIGFu
b3RoZXI/DQpKYXNvbiByZXBsaWVkIHRoYXQgdGhlIGF1ZGlvIGVuY29kaW5n
IG1ha2VzIHVzZSBvZiBzaW1pbGFyaXRpZXMgYW1vbmcNCmFsbCA2IGNoYW5u
ZWxzLCBzbyB0aGV5IG5lZWQgdG8gYmUgcHJvY2Vzc2VkIHRvZ2V0aGVyLg0K
DQpTdGV2ZSByZW1hcmtlZCB0aGF0IHRoaXMgaXMgYSBwZXJmZWN0bHkgcmVh
c29uYWJsZSBwYXlsb2FkIGZvcm1hdCB0bw0KdW5kZXJ0YWtlIGFzIGEgd29y
ayBpdGVtOyB0aGUgb25seSBjb25zaWRlcmF0aW9uIGlzIHRoZSBudW1iZXIg
b2Ygd29yaw0KaXRlbXMgdGhhdCB3ZSB1bmRlcnRha2UuICBUaGVyZSB3YXMg
YSBmYWlybHkgc3Ryb25nIGh1bSB0byBhY2NlcHQgdGhpcw0Kb25lLg0KDQoN
ClJlc2lsaWVudCBNSURJIFJUUCBwYWNrZXRpemF0aW9uDQoNCkpvaG4gTGF6
emFybyBnYXZlIGEgcHJlc2VudGF0aW9uIG9uIGEgcmVzaWxpZW50IE1JREkg
cGFja2V0aXphdGlvbg0KZGVzaWduZWQgZm9yIG5ldHdvcmsgbXVzaWNhbCBw
ZXJmb3JtYW5jZSBhcyBkZXNjcmliZWQgaW4NCmRyYWZ0LWxhenphcm8tYXZ0
LW13cHAtbWlkaS1ubXAtMDAudHh0LiAgRXZlbiB0aG91Z2ggdGhpcyBpcyB0
aGUgZmlyc3QNCnRpbWUgdGhpcyB3b3JrIHdhcyBicm91Z2h0IHRvIEFWVCwg
ZXhwZXJpbWVudGF0aW9uIHVzaW5nIHRoaXMgcGF5bG9hZA0KZm9ybWF0IHdp
dGggUlRQIGhhcyBiZWVuIGluIHByb2dyZXNzIGZvciBzb21lIHRpbWUsIHNv
IHRoZSBkcmFmdCBpcw0KYWxyZWFkeSBxdWl0ZSBzdWJzdGFudGlhbC4NCg0K
TGF0ZW5jeSBpcyBhbiBpc3N1ZSBmb3IgbmV0d29yayBwZXJmb3JtYW5jZSwg
YnV0IGZvciBkaXN0YW5jZXMgbGlrZQ0KdGhlIDM1MCBtaWxlcyBiZXR3ZWVu
IG5vcnRoZXJuIGFuZCBzb3V0aGVybiBDYWxpZm9ybmlhLCB0aGUgbWVhc3Vy
ZWQNCmRlbGF5IGlzIHRoZSBzYW1lIGFzIGEgMTYtZm9vdCBzZXBhcmF0aW9u
IG9uIHN0YWdlLiAgTmV0d29yaw0KcGVyZm9ybWFuY2UgaXMgZmVhc2libGUg
aW4gc3VjaCBjYXNlcyBzbyBsb25nIGFzIGFkZGl0aW9uYWwgYnVmZmVyaW5n
DQppcyBub3QgYWRkZWQgZm9yIGxhdGUgcGFja2V0cy4gIFRoZSBhbnN3ZXIg
aXMgdG8gc2VuZCB0aGUgTUlESQ0KZW5jb2Rpbmcgb2YgdGhlIG11c2ljaWFu
cycgZ2VzdHVyZXMgYW5kIHR1cm4gdGhlbSBpbnRvIGF1ZGlvIGF0IHRoZQ0K
cmVjZWl2ZXIgd2l0aG91dCBkZWxheS4gIFNlbWFudGljIHJlY292ZXJ5IGZy
b20gbGF0ZSBhbmQgbG9zdCBwYWNrZXRzDQpwcm9kdWNlcyBhIHJlc3VsdCB0
aGF0IGp1c3Qgc291bmRzIGxpa2UgaW1wZXJmZWN0IHBlcmZvcm1hbmNlIHJh
dGhlcg0KdGhhbiBmdW5ueSBub2lzZXMuICBNb3N0IG9mIHRoZSBkcmFmdCBp
cyBhIHNwZWNpZmljYXRpb24gb2Ygd2hhdCB0aGUNCnJ1bGVzIG5lZWQgdG8g
YmUgdG8gbWFrZSB0aGUgc2VtYW50aWMgcmVjb3Zlcnkgc291bmQgZ29vZC4g
IFRoZSBydWxlcw0Kd2VyZSBkZXJpdmVkIGZyb20gdHdvIHllYXJzIG9mIGV4
cGVyaW1lbnRhdGlvbi4NCg0KTUlESSBoYXMgYSB2ZXJ5IGxvdyBkYXRhIHJh
dGUgKGZhc3QgcGlhbm8gcGxheWluZyBpcyAzMDAgYnBzKSwgYnV0IGlzDQp2
ZXJ5IGZyYWdpbGUuICBBIG1pc3NlZCAiTm90ZU9mZiIgY29tbWFuZCBjYXVz
ZXMgYSBodW5nIG5vdGUgZm9yZXZlci4NClRoZSBwcm9wb3NlZCBwYWNrZXRp
emF0aW9uIHVzZXMgYSByZWNvdmVyeSBqb3VybmFsIHRvIHJlY292ZXIgZnJv
bQ0KbG9zdCBwYWNrZXRzIHdpdGhvdXQgcmVxdWlyaW5nIGV4cGxpY2l0IHJl
dHJhbnNtaXNzaW9uLiAgVGhlIHJlY292ZXJ5DQpqb3VybmFsIGlzIHNlbnQg
aW4gZXZlcnkgcGFja2V0IGFuZCBjb250YWlucyBhIG1pbmltYWwgc2Vzc2lv
biBoaXN0b3J5DQpzaW5jZSB0aGUgbGFzdCBjaGVja3BvaW50IHBhY2tldC4g
IFRoZSBjaGVja3BvaW50IGlzIGFkdmFuY2VkIGJ5IHRoZQ0KcmVjZWlwdCBv
ZiB0aGUgUlRDUCAibGFzdCBwYWNrZXQgcmVjZWl2ZWQiIHN0YXRpc3RpYy4g
IFRoaXMgZXZlbiB3b3Jrcw0Kd2l0aCBzbWFsbC1zY2FsZSBtdWx0aWNhc3Qs
IHRha2luZyB0aGUgY2hlY2twb2ludCBmcm9tIHRoZSBsZWFzdA0KYWR2YW5j
ZWQgcmVjZWl2ZXIuICBUaGUgaW5jcmVhc2UgaW4gZGF0YSByYXRlIGlzIG5v
dCB0aGF0IHNpZ25pZmljYW50Og0KNCBrYnBzIGZvciBmYXN0IHBpYW5vIHdv
cmsuICBQYWNrZXRzIHRoYXQgYXJyaXZlIG9uIHRpbWUgYXJlIGFsd2F5cw0K
ZXhlY3V0ZWQsIGJ1dCBhIHBhY2tldCB0aGF0IGFycml2ZXMgbGF0ZSBpcyBw
cm9jZXNzZWQgYWNjb3JkaW5nIHRvIHRoZQ0Kc2VtYW50aWMgcnVsZXMgdGhh
dCBhcmUgc3BlY2lmaWMgdG8gZWFjaCBjb21tYW5kIChlLmcuLCB0aGUgY29t
bWFuZA0KbWF5IGJlIHN1cGVyc2VkZWQgYnkgYSBsYXRlciBwYWNrZXQgdGhh
dCBhcnJpdmVkIGVhcmxpZXIpLg0KDQpUaGUgb3BlbiBpc3N1ZXMgZm9yIHRo
ZSBwYXlsb2FkIGZvcm1hdCBoYXZlIHRvIGRvIHdpdGggaG93IG11Y2ggb2Yg
dGhlDQphbGdvcml0aG0gaXMgbm9ybWF0aXZlLiAgQ3VycmVudGx5LCB0aGUg
c2VtYW50aWMgcmVjb3ZlcnkgcnVsZXMgYXJlDQpub3JtYXRpdmUgaW4gdGhl
IHNlbnNlIG9mIGEgYmVzdCBjdXJyZW50IHByYWN0aWNlLCBidXQgdGhleSBt
YXkgbm90IGJlDQpvcHRpbWFsLiAgVGhlIGFsZ29yaXRobSBmb3IgZGVjaWRp
bmcgb24tdGltZSB2cy4gbGF0ZSBpcyBub3Qgbm9ybWF0aXZlDQpiZWNhdXNl
IGRpZmZlcmVudCBjcml0ZXJpYSBtYXkgYXBwbHkgaW4gZGlmZmVyZW50IHNj
ZW5hcmlvcy4NCg0KU3RldmUgQ2FzbmVyIHJlc3BvbmRlZCB0aGF0IGl0IGlz
IGZpbmUgdG8gaGF2ZSB0aG9zZSBzZW1hbnRpYyBydWxlcyBpbg0KdGhlIGRy
YWZ0LCBpdCBzaG91bGQganVzdCBiZSBzdGF0ZWQgY2xlYXJseSB0aGF0IHRo
aXMgaXMgYSByZWNvbW1lbmRlZA0KcHJhY3RpY2UsIGEgU0hPVUxEIChvciBS
RUNPTU1FTkRFRCkgbm90IGEgTVVTVC4gIFRoaXMgaXMgdGhlIGZpcnN0DQpp
bnN0YW5jZSBvZiBhIHNlbWFudGljIHJlcXVpcmVtZW50IGJlaW5nIG9uIFJU
Q1AgcmVjZWl2ZXIgcmVwb3J0cywNCndoZXJlIHRoZSBwYXlsb2FkIGZvcm1h
dCB3b24ndCB3b3JrIHdpdGhvdXQgUlRDUC4gIFRoYXQncyBuZXcNCnRlcnJp
dG9yeSwgYnV0IHNob3VsZCBub3QgYmUgYSBwcm9ibGVtLiAgSm9obiBoYXMg
c29tZSBjb25jZXJuIGFib3V0DQpzb21lIG9mIHRoZSByb2J1c3QgaGVhZGVy
IGNvbXByZXNzaW9uIHNjaGVtZXMgdGhhdCBkb24ndCBwcmVzZXJ2ZQ0Kc2Vx
dWVuY2UgbnVtYmVycyBleGFjdGx5LiAgQWxsIHRoZSBzZXF1ZW5jZSBudW1i
ZXJzIG5lZWQgdG8gYmUgdGhlDQpyaWdodCBvbmVzLCBub3QganVzdCBjbG9z
ZS4gIFN0ZXZlIHJlcGxpZWQgdGhhdCB0aGUgemVyby1ieXRlIGhlYWRlcg0K
Y29tcHJlc3Npb24gZG9lc24ndCBhcHBseSBoZXJlIGJlY2F1c2UgdGhpcyBt
ZWRpdW0gZG9lc24ndCBoYXZlIHRoZQ0KcmVndWxhciB0aW1pbmcgdGhhdCBz
Y2hlbWUgZGVwZW5kcyB1cG9uLCBzbyBpdCB3b3VsZCBub3QgYmUgdXNlZC4N
Cg0KQW5vdGhlciBvcGVuIGlzc3VlIGlzIHdoZXRoZXIgdGhlIHBheWxvYWQg
Zm9ybWF0J3MgcGVyZm9ybWFuY2UgY291bGQNCmJlIGltcHJvdmVkIHdpdGgg
dGhlIGZsZXhpYmlsaXR5IHVuZGVyIG5ldyBwcm9maWxlcyB0byBkZWZpbmUg
bmV3DQpSVENQLWJhc2VkIGZlZWRiYWNrIHJhdGhlciB0aGFuIGFzc3VtaW5n
IG9ubHkgdGhlIHN0YW5kYXJkIHBhY2tldA0KdHlwZXMuICBCdXQgaXQgc2Vl
bXMgc2ltcGxlciB0byBzdGljayB3aXRoIHRoZSBzdGFuZGFyZCBvbmVzIHNp
bmNlDQp0aGF0IHdvcmtzLiAgQ29saW4gYWdyZWVzLiBTdGljayB3aXRoIHRo
aXMgZm9yIGF0IGxlYXN0IHRoZSBmaXJzdA0KdmVyc2lvbiwgYW5kIGxlYXZl
IG9wZW4gdGhlIHBvc3NpYmlsaXR5IG9mIHVzaW5nIGZlYXR1cmVzIGxpa2UN
ClJUQ1AtYmFzZWQgcmV0cmFuc21pc3Npb24gbGF0ZXIgaWYgYXBwcm9wcmlh
dGUuDQoNClRoZSByZWNvdmVyeSBhbmQgdGltZSBzZW1hbnRpY3Mgb2YgdGhp
cyBwYXlsb2FkIGZvcm1hdCBhcmUgYWxzbw0KY29tcGF0aWJsZSB3aXRoIE1Q
RUctNCBTdHJ1Y3R1cmVkIEF1ZGlvIChNUDQtU0EpLiAgVGhlIGRyYWZ0DQpu
b3JtYXRpdmVseSBpbmNsdWRlcyBNUDQtU0EgZXhlY3V0aW9uIHNlbWFudGlj
cyBmb3Igc29mdHdhcmUNCnN5bnRoZXNpemVycy4gIEhvd2V2ZXIsIHRoaXMg
cGF5bG9hZCBmb3JtYXQgaXMgY29tcGF0aWJsZSB3aXRoIGFsbA0Kc29mdHdh
cmUgc3ludGhlc2l6ZXJzLCBpbmNsdWRpbmcgdGhvc2UgdGhhdCBkbyBub3Qg
dXNlIE1QNC1TQS4NCg0KVGhpcyBwcm9wb3NhbCBuZWVkcyBjYXJlZnVsIHJl
dmlldyBib3RoIGJ5IFJUUC1zYXZ2eSBwZW9wbGUgYW5kIGJ5DQpNSURJLXNh
dnZ5IHBlb3BsZS4gIElFVEYgaGFzIGFuIG9wcG9ydHVuaXR5IGhlcmUgdG8g
bGVhZCBhbGwgdGhlDQptdXNpY2lhbnMgd2hvIGFyZSBqdXN0IHN0YXJ0aW5n
IHRvIGxvb2sgYXQgbmV0d29ya2luZyBkb3duIHRoZSByaWdodA0KcGF0aCBy
YXRoZXIgdGhhbiBoYXZpbmcgdG8gcGF0Y2ggdGhpbmdzIHVwIGxhdGVyLg0K
DQpDb2xpbiBzYWlkIHRoaXMgcHJvcG9zYWwgaXMgImNvb2wiIGFuZCBjbGVh
cmx5IGlzIGEgY2FuZGlkYXRlIGZvcg0Kc3RhbmRhcmRpemF0aW9uLiAgU3Rl
dmUgYWdyZWVkLCBhcyBkaWQgbWFueSBpbiB0aGUgcm9vbS4NCg0KDQpSVFAg
UGF5bG9hZCBGb3JtYXQgZm9yIERpc3RyaWJ1dGVkIFNwZWVjaCBSZWNvZ25p
dGlvbg0KDQpBbHRob3VnaCBkcmFmdC1pZXRmLWF2dC1kc3ItMDAudHh0IGlz
IGEgLTAwIHdvcmtpbmcgZ3JvdXAgZHJhZnQsIGJ1dA0KaXQgaGFzIGJlZW4g
ZGlzY3Vzc2VkIGluIEFWVCBhcyBpbmRpdmlkdWFsIHN1Ym1pc3Npb24gZm9y
IHF1aXRlIHNvbWUNCnRpbWUsIGZpcnN0IGJ5IEplZmYgTWV1bmllciBpbiBK
dWx5LCAyMDAwLCBhbmQgbW9yZSByZWNlbnRseSBieQ0KUWlhb2JpbmcgWGll
LiAgUWlhb2JpbmcncyBwcmVzZW50YXRpb24gd2FzIHZlcnkgc2hvcnQgYmVj
YXVzZSB0aGUgb25seQ0KY2hhbmdlcyBpbiB0aGlzIHJldmlzaW9uIHdlcmUg
dG8gcmVtb3ZlIHRoZSBmcmFtZSBwYWlyIGNvdW50ZXIgc2luY2UNCnRoZSBj
b3VudCBjYW4gYmUgaW5mZXJyZWQgZnJvbSB0aGUgcGFja2V0IGxlbmd0aCwg
YW5kIHRvIHJlbW92ZSB0aGUNCmVuZCBvZiBzcGVlY2ggZmxhZyBzaW5jZSB0
aGF0IGlzIG5vdyBpbmRpY2F0ZWQgYnkgYSBzcGVjaWFsIE5VTEwgZnJhbWUN
CnBhaXIuICBUaGlzIG1lYW5zIHRoYXQgbm93IHRoZXJlIGlzIG5vIHBheWxv
YWQgaGVhZGVyIHJlcXVpcmVkIGF0IGFsbC4NClRoaXMgZHJhZnQgYWxzbyBj
bGFyaWZpZXMgaG93IGRpc2NvbnRpbnVvdXMgdHJhbnNtaXNzaW9uIGNhbiBi
ZQ0Kc3VwcG9ydGVkLiAgVGhlcmUgYXJlIG5vIG9wZW4gaXNzdWVzIHJlbWFp
bmluZy4NCg0KQ29saW4gUGVya2lucyBpZGVudGlmaWVkIG9uZSBzaW1wbGUg
YnVnIGluIHRoZSBkb2N1bWVudDogdGhlIE1JTUUNCnJlZ2lzdHJhdGlvbiBz
cGVjaWZpZXMgYSBwYXJhbWV0ZXIgInNhbXBsZS1yYXRlIiB3aGljaCBzaG91
bGQgYmUgdGhlDQpjb21tb24gcGFyYW1ldGVyICJyYXRlIiBpbnN0ZWFkLg0K
DQpTdGV2ZSBDYXNuZXIgcmVtYXJrZWQgdGhhdCBpdCBpcyBwcmV0dHkgaGFy
ZCB0byBhcmd1ZSB3aXRoIGEgcGF5bG9hZA0KZm9ybWF0IHRoYXQganVzdCBz
YXlzIHB1dCB0aGUgZGF0YSBpbnRvIFJUUCBwYWNrZXRzLiAgU28gdGhpcyBw
cm9wb3NhbA0KaXMgZmluZSwgYW5kIHdlIHNob3VsZCBwcm9jZWVkIHRvIGxh
c3QgY2FsbC4gIFRoZSBncm91cCBodW1tZWQgeWVzLg0KDQoNClJUUCBwYXls
b2FkIGZvcm1hdCBmb3IgSlBFRyAyMDAwIHZpZGVvIHN0cmVhbXMNCg0KRXJp
YyBFZHdhcmRzIHByZXNlbnRlZCBhIG5ldyBSVFAgcGF5bG9hZCBmb3JtYXQg
Zm9yIEpQRUctMjAwMCB2aWRlbw0Kc3RyZWFtcyAoZHJhZnQtZWR3YXJkcy1h
dnQtcnRwLWpwZWctMjAwMC0wMC50eHQpLiAgSlBFRy0yMDAwIGlzIGEgbmV3
DQp2aWRlbyBmb3JtYXQsIHdoaWNoIHByb3ZpZGVzIHN1cGVyaW9yIGxvdyBi
aXQtcmF0ZSBwZXJmb3JtYW5jZSwgc3Ryb25nDQplcnJvciByZXNpbGllbmNl
IGFuZCBzY2FsYWJsZSBvcGVyYXRpb24uICBUaGUga2V5IGZlYXR1cmVzIG9m
IHRoZQ0KcHJvcG9zZWQgUlRQIHBheWxvYWQgZm9ybWF0IGFyZSByb2J1c3Ru
ZXNzIHRvIHBhY2tldCBsb3NzIHRocm91Z2gNCmludGVsbGlnZW50IGZyYWdt
ZW50YXRpb24sIGEgcHJpb3JpdHkgaW5mb3JtYXRpb24gZmllbGQgZm9yIHNj
YWxhYmxlDQpkZWxpdmVyeSBmcm9tIHRoZSBzYW1lIGJpdC1zdHJlYW0sIHBl
cnNpc3RlbmN5IG9mIHRoZSBtYWluIGhlYWRlciB0bw0KbWluaW1pemUgdGhl
IGVmZmVjdHMgb2YgbG9zcy4gIFRoZSBKUEVHIGNvbW1pdHRlZSBoYXMgZXhw
cmVzc2VkDQpjb25zaWRlcmFibGUgaW50ZXJlc3QgaW4gcGFydGljaXBhdGlu
ZyBpbiB0aGlzIHdvcmssIGFuZCB3aWxsIHByb3ZpZGUNCmZlZWRiYWNrIHRv
IEFWVC4NCg0KQWZ0ZXIgZ2l2aW5nIGFuIG92ZXJ2aWV3IG9mIHRoZSBkcmFm
dCwgaGUgcmFpc2VkIHRoZSBvcGVuIGlzc3VlczogYXJlDQp0aGVyZSBhbnkg
c3VnZ2VzdGlvbnMgZm9yIGEgYmV0dGVyIGZyYWdtZW50YXRpb24gc2NoZW1l
PyAgSG93IHRvIHVzZQ0KdGhlIG9wdGlvbmFsIGZpZWxkcz8gIEhvdyB0byBo
YW5kbGUgb3IgZGVmaW5lIHVzZSBvZiBwcmlvcml0eSBtYXBwaW5nDQp0YWJs
ZXM/ICBTdGV2ZSBDYXNuZXIgbm90ZWQgdGhhdCB0aGVyZSBhcmUgbWFueSBk
aWZmZXJlbnQgcGFja2V0DQp0eXBlcywgYW5kIHdvbmRlcmVkIGlmIGFsbCB0
aGUgZGlmZmVyZW50IHR5cGVzIGFyZSB1c2VmdWw/ICBJZiB0aGUNCnJlY2Vp
dmVyIG1ha2VzIHVzZSBvZiB0aGUgdHlwZSBhbmQgcHJpb3JpdHkgZmllbGRz
IHRvIGRvIHNvbWV0aGluZw0KZGlmZmVyZW50LCBhbmQgdGhhdCBpbmZvcm1h
dGlvbiBpcyBub3QgYWxyZWFkeSBhdmFpbGFibGUgaW4gdGhlIGRhdGENCnN0
cmVhbSBpdHNlbGYsIHRoZW4gaXQgbWFrZXMgc2Vuc2UgdG8gaGF2ZSB0aG9z
ZSBoZWFkZXIgZmllbGRzLiAgQnV0LA0KaWYgdGhlIGZpZWxkcyBhcmUgcmVk
dW5kYW50IHdpdGggaW5mb3JtYXRpb24gaW4gdGhlIGRhdGEgc3RyZWFtLCB0
aGVuDQpwdXR0aW5nIGl0IGludG8gdGhlIFJUUCBoZWFkZXIgbWlnaHQgbm90
IGJlIGEgZ29vZCBpZGVhLCBiZWNhdXNlIGl0DQphbGxvd3MgdGhlIHBvc3Np
YmlsaXR5IG9mIGluY29uc2lzdGVuY3kuICBJdCBtYXkgYmUgYXBwcm9wcmlh
dGUgdG8gdXNlDQpvbmx5IGEgcmVkdWNlZCBzdWJzZXQgb2YgdGhlc2UgdHlw
ZXM/ICBTdGV2ZSBhbHNvIG5vdGVkIHRoYXQgdGhlIHVzZQ0Kb2YgUkZDIDIx
MTkgdGVybXMgaXMgbmVlZGVkLg0KDQpNYXJzaGFsbCBFdWJhbmtzIHF1ZXN0
aW9uZWQgdGhlIGxpY2Vuc2luZyB0ZXJtcyBmb3IgdGhpcyBmb3JtYXQuICBJ
dA0Kd2FzIGNsYXJpZmllZCB0aGF0IElQUiBoYXMgbm90IGJlZW4gY2xhaW1l
ZCBvbiB0aGlzIHBheWxvYWQgZm9ybWF0LA0KYW5kIHRoYXQgSlBFRy0yMDAw
IHBhcnQgMSBpcyAidGFyZ2V0ZWQgdG8gYmUgcm95YWx0eSBmcmVlIiAodGhp
cw0KcGF5bG9hZCBmb3JtYXQgdHJhbnNwb3J0cyBhIHNlcmllcyBvZiBKUEVH
LTIwMDAgcGFydCAxIGZyYW1lcykuICBUaGVyZQ0KbWF5IGJlIElQUiBvbiBv
dGhlciBwYXJ0cyBvZiB0aGUgSlBFRy0yMDAwIHN0YW5kYXJkLg0KDQpUaGUg
SlBFRy0yMDAwIHBheWxvYWQgZm9ybWF0IHdhcyBhY2NlcHRlZCBhcyBhIHdv
cmsgaXRlbSBvZiBBVlQuDQoNCg0KVXBkYXRlIHRvIFJUUCBzcGVjaWZpY2F0
aW9uIGFuZCBwcm9maWxlDQoNClN0ZXZlIENhc25lciBkaXNjdXNzZWQgdGhl
IGNoYW5nZXMgdGhhdCBoYXZlIG9jY3VycmVkIGluIHRoZSBSVFANCnNwZWNp
ZmljYXRpb24gc2luY2UgdGhlIGxhc3QgbWVldGluZzogcmVsYXggdGhlIHJl
cXVpcmVtZW50IHRvIHVzZSBhbg0KZXZlbi9vZGQgcG9ydCBwYWlyIGlmIHRo
ZSBwb3J0cyBhcmUgZXhwbGljaXRseSBzaWduYWxlZDsgZXhwbGFpbiB0aGF0
DQpvbmx5IG9uZSBjb21wb3VuZCBSVENQIHNob3VsZCBiZSBzZW50IHBlciBp
bnRlcnZhbCwgYW5kIHRoYXQgeW91DQpzaG91bGQgcm91bmQtcm9iaW4gdGhy
b3VnaCBzb3VyY2VzIGlmIHRoZXJlIGFyZSB0b28gbWFueSB0byBzZW5kDQpy
ZXBvcnRzIGZvciBhbGwgb2YgdGhlbSB3aXRoaW4gdGhlIE1UVTsgYW5kIGV4
cGxhaW4gdGhlIGVmZmVjdCBvZg0KdmFyeWluZyBwYWNrZXQgZHVyYXRpb24g
b24gdGhlIGppdHRlciBjYWxjdWxhdGlvbi4gIFRoZXJlIHdlcmUgYWxzbyBh
DQpudW1iZXIgb2YgbWlub3IgZml4ZXMgYW5kIGNsYXJpZmljYXRpb25zLiAg
VG8gZmFjaWxpdGF0ZSBJRVNHDQphY2NlcHRhbmNlLCB0aGUgb3BlbiBpc3N1
ZXMgc2VjdGlvbiBoYXMgYmVlbiByZW1vdmVkLCB0aGUNCnRhYmxlLW9mLWNv
bnRlbnRzIG1vdmVkIHRvIHRoZSBiZWdpbm5pbmcsIHRoZSByZWZlcmVuY2Vz
IGhhdmUgYmVlbg0Kc3BsaXQgaW50byBub3JtYXRpdmUgYW5kIG5vbi1ub3Jt
YXRpdmUgcGFydHMsIGFuZCB0aGUgY2hhbmdlcyBzaW5jZQ0KUkZDMTg4OSBz
ZWN0aW9uIGhhcyBiZWVuIHVwZGF0ZWQuDQoNCkhlbm5pbmcgU2NodWx6cmlu
bmUgYXNrZWQgYWJvdXQgaW50ZXJvcGVyYWJpbGl0eSByZXF1aXJlbWVudHMg
Zm9yIHRoZQ0KcmVjb25zaWRlcmF0aW9uIGFsZ29yaXRobSwgYW5kIGlmIHdl
IGhhdmUgc2F0aXNmaWVkIHRoZSBJRVNHLiAgU3RldmUNCmV4cGxhaW5lZCB0
aGUgdGVzdHMgd2UgaGF2ZSBkb25lLCBhbmQgc2FpZCB0aGF0IHdlIHNlZW0g
dG8gbWVldCBhbGwNCnRoZSBjb25zdHJhaW50cy4gIENvbGluIFBlcmtpbnMg
bm90ZWQgdGhhdCBoZSBoYXMgZGlzY3Vzc2VkIHRoaXMgd2l0aA0KdGhlIGFy
ZWEgZGlyZWN0b3IsIHdobyBzZWVtcyBoYXBweSB3aXRoIHRoZSB0ZXN0cyBj
b25kdWN0ZWQuDQoNClRoZSBBdWRpby9WaWRlbyBwcm9maWxlIGhhZCBvbmUg
Y2xhcmlmaWNhdGlvbiwgdGhhdCB0aGUgUlRQIHRpbWVzdGFtcA0KdXN1YWxs
eSBlcXVhbHMgdGhlIHNhbXBsaW5nIGNsb2NrLCBidXQgbm90IGFsd2F5cy4g
IFRoZXJlIGFyZSBhbHNvIGENCm51bWJlciBvZiBjaGFuZ2VzIHRvIGZhY2ls
aXRhdGUgSUVTRyBhY2NlcHRhbmNlLCBtdWNoIGFzIHdhcyBkb25lIGZvcg0K
dGhlIFJUUCBzcGVjaWZpY2F0aW9uLiAgVGhlIFJUUCBNSU1FIGRyYWZ0IG5v
dyBiZWdpbnMgd2l0aCBhIHN1bW1hcnkNCmxpc3Qgb2YgdGhlIHN1YnR5cGVz
IGJlaW5nIHJlZ2lzdGVyZWQsIGFuZCBoYXMgdGhlIGNvbW1vbiBmaWVsZHMN
CnJlcGxpY2F0ZWQgaW50byBlYWNoIHJlZ2lzdHJhdGlvbiB0byBtYWtlIHRo
ZW0gaW5kaXZpZHVhbGx5DQpzdGFuZC1hbG9uZSwgcGx1cyBvdGhlciBtaW5v
ciBjbGFyaWZpY2F0aW9ucy4gIFRoZSBSVENQLUJXIGRyYWZ0IGhhcw0KaGFk
IHRoZSBub3RlIGFib3V0IGNvbmZsaWN0IHdpdGggUkZDIDIzMjcgY2hhbmdl
ZCB0byBub3RlIHRoYXQgdGhpcyBpcw0KcmVzb2x2ZWQgaW4gdGhlIHVwZGF0
ZSB0byBTRFAuICBUaGlzIGltcGxpZXMgYSBkZXBlbmRlbmN5IG9uIHRoZSBk
cmFmdA0KZHJhZnQtaWV0Zi1tbXVzaWMtc2RwLW5ldywgd2hpY2ggbWF5IGhv
bGQgdXAgcHVibGljYXRpb24gb2YgdGhlDQpSVENQLUJXIGRyYWZ0Lg0KDQpU
aGUgcGxhbiBpcyB0byBzZW5kIHRoZSBwdWJsaWNhdGlvbiByZXF1ZXN0IGZv
ciBSVFAsIGFuZCB0aGUgcmVsYXRlZA0KZHJhZnRzLCB0byB0aGUgSUVTRyBi
ZWZvcmUgdGhlIG1lZXRpbmcgaXMgb3V0LiAgRG9lcyBhbnlvbmUgb2JqZWN0
Pw0KTm8uICBTdGVwaGFuIFdlbmdlciBhc2tlZCBpZiB0aGUgd29yZGluZyBv
biBjb25nZXN0aW9uIGNvbnRyb2wgd2FzDQpzdWZmaWNpZW50PyAgU3RldmUg
bm90ZWQgdGhhdCB3ZSd2ZSBoYWQgZmVlZGJhY2sgZnJvbSB0aGUgYXJlYQ0K
ZGlyZWN0b3IgdGhhdCBpdCBpcyBva2F5Lg0KDQpUaGUgb2ZmaWNpYWwgcmVx
dWVzdCBmb3IgYWR2YW5jZW1lbnQgb2YgdGhlIFJUUCBzcGVjIGFuZCBBL1Yg
cHJvZmlsZQ0KdG8gRHJhZnQgU3RhbmRhcmQgc3RhdHVzIHdhcyBzZW50IHRv
IHRoZSBBcmVhIERpcmVjdG9yIG9uIEZyaWRheSBvZg0KSUVURiB3ZWVrLCBE
ZWNlbWJlciAxNC4gIFRoaXMgaXMgYSB2ZXJ5IHNpZ25pZmljYW50IG1pbGVz
dG9uZS4NCg0KDQpTZWN1cmUgUlRQIHByb2ZpbGUNCg0KRWxpc2FiZXR0YSBD
YXJyYXJhIGRpc2N1c3NlZCB0aGUgcmVjZW50IGNoYW5nZXMgaW4gU1JUUA0K
KGRyYWZ0LWlldGYtYXZ0LXNydHAtMDIudHh0KS4gIFNpbmNlIHRoZSAtMDEg
dmVyc2lvbiwgdGhlIG9wdGlvbmFsIFNQSQ0KZmllbGQgYW5kIFRFU0xBIGhh
dmUgYmVlbiByZW1vdmVkLCBhbmQgdGhlIGRyYWZ0IGhhcyBiZWVuIHJld3Jp
dHRlbiBhcw0KYSBmcmFtZXdvcmsuICBPdGhlciBjaGFuZ2VzIGluY2x1ZGUg
Y2xhcmlmaWNhdGlvbiBvZiB0aGUNCmNyeXB0by1jb250ZXh0LCBhbmQgdGhl
IFNSVENQIGNvdmVyYWdlLCBhcyByZXF1ZXN0ZWQgaW4gTG9uZG9uLiAgQSBu
ZXcNCnBzZXVkby1yYW5kb20ga2V5IGRlcml2YXRpb24gZnVuY3Rpb24gaGFz
IGJlZW4gYWRkZWQsIHRvIGRlcml2ZSB0aGUNCnNlc3Npb24ga2V5cyBmcm9t
IGEgbWFzdGVyIGtleS4gIENvbGluIFBlcmtpbnMgYXNrZWQgaWYgdGhpcyBr
ZXkNCmRlcml2YXRpb24gc2NoZW1lIHdhcyBtYW5kYXRvcnksIG9yIGlmIHRo
ZSBzZXNzaW9uIGtleXMgY2FuIGJlDQpzdXBwbGllZCBtYW51YWxseT8gIEl0
IGlzIG1hbmRhdG9yeS4gIFRoZSBlbmNyeXB0aW9uIHRyYW5zZm9ybXMNCnN1
cHBvcnRlZCBoYXZlIGJlZW4gdXBkYXRlZCwgd2l0aCBzdXBwb3J0IGZvciBB
RVMtQ00gSUhBIGFuZCBzaGFyZWQNCm1hc3RlciBrZXlzIGJlaW5nIHJlbW92
ZWQuICBUaGUga2V5LXN0cmVhbSBkZWZpbml0aW9uIGhhcyBiZWVuDQp1cGRh
dGVkLCBhbmQgY2xhcmlmaWVkLiAgVGhlIFVNQUMgYXV0aGVudGljYXRpb24g
c2NoZW1lIGhhcyBiZWVuDQpyZW1vdmVkLCBkdWUgdG8gbGFjayBvZiBhIHN0
YWJsZSBzcGVjaWZpY2F0aW9uLCBhbmQgVE1NSC8xNg0KYXV0aGVudGljYXRp
b24gaGFzIGJlZW4gYWRkZWQgYXMgYW4gb3B0aW9uLg0KDQpUaGUgb3BlbiBp
c3N1ZSBpcyAic2hhcmluZyBvZiB0aGUgc2FtZSBtYXN0ZXIga2V5IGFtb25n
IHNldmVyYWwgUlRQDQpzdHJlYW1zIiwgd2hpY2ggd2FzIGEgZGVzaWduIGdv
YWwgaW4gZWFybGllciB2ZXJzaW9ucyBvZiB0aGUgZHJhZnQsDQpidXQgaXMg
bm90IHBvc3NpYmxlIHdpdGggdGhlIG5ldyBkZWZpbml0aW9uIG9mIEFFUy1D
TS4gIFRoZSBzb2x1dGlvbiwNCnRvIGtlZXAgdGhpcyBmdW5jdGlvbiwgaXMg
dG8gaW5zZXJ0IGEgdW5pcXVlLXBlci1zdHJlYW0gdmFsdWUgaW50byB0aGUN
CmluaXRpYWxpemF0aW9uIHZlY3RvciBvZiB0aGUgc3RyZWFtcyB0aGF0IHdp
c2ggdG8gc2hhcmUgdGhlIHNhbWUNCm1hc3RlciBrZXk6IGNhbiB0aGUgU1NS
QyBiZSBzdWNoIGEgdW5pcXVlIHZhbHVlPyAgQ29saW4gUGVya2lucyBhZ3Jl
ZWQNCnRoYXQgdGhpcyBpcyBhIHJlYXNvbmFibGUgY29uc3RyYWludC4NCg0K
U3RldmUgQ2FzbmVyIHByYWlzZWQgdGhlIHJld3JpdGUgYXMgYmVpbmcgYSBn
cmVhdCBjbGFyaWZpY2F0aW9uLCBidXQNCm5vdGVkIHRoZSBjaGFpcnMgY29u
Y2VybiB0aGF0IHRoZSBkcmFmdCBjaGFuZ2VzIHNpZ25pZmljYW50bHkgd2l0
aA0KZWFjaCB2ZXJzaW9uLiAgRWxpc2FiZXR0YSBhc3N1cmVkIHRoZSBncm91
cCB0aGF0IHRoZSBkcmFmdCB3YXMgbm93DQpzdGFibGUgZXhjZXB0IGZvciBl
ZGl0aW5nIGluIHRoZSBvcGVuIGlzc3VlIHNvbHV0aW9uIG1lbnRpb25lZCBh
Ym92ZS4NCkl0IHdhcyBub3RlZCB0aGF0IEhNQUMgaXMgYSAyMC1ieXRlIGF1
dGhlbnRpY2F0aW9uIG1lY2hhbmlzbSwgYnV0IHRoaXMNCmRyYWZ0IHVzZXMg
YSA0LWJ5dGUgdmVyc2lvbj8gIFllcywgaXQgd2FzIGN1dC1kb3duIGZvciBz
cGVlZCBhbmQNCnJlYWwtdGltZSBvcGVyYXRpb24uICBJdCB3YXMgbm90ZWQg
dGhhdCBmaWd1cmUgMSBpbiB0aGUgZHJhZnQgaXMNCm1pc2xlYWRpbmcsIGR1
ZSB0byBhIHBhZGRpbmcgcHJvYmxlbSwgYW5kIG5lZWRzIHRvIGJlIGNsYXJp
ZmllZC4gIEl0DQp3YXMgYXNrZWQgaWYgdW5lcXVhbCBlcnJvciBwcm90ZWN0
aW9uIGlzIHN1cHBvcnRlZD8gIFllcy4NCg0KQW4gaW1wbGVtZW50YXRpb24g
aXMgYXZhaWxhYmxlIGF0DQpodHRwOi8vc291cmNlZm9yZ2UubmV0L3Byb2pl
Y3RzL3NydHAvDQoNClN0ZXZlIENhc25lciBub3RlZCB0aGF0IHRoZXJlIGFy
ZSBhIG51bWJlciBvZiBjbGFyaWZpY2F0aW9ucyB0byBtYWtlLA0KYW5kIHRo
ZSBvcGVuIGlzc3VlIG5lZWRzIHRvIGJlIHJlc29sdmVkLiAgT25jZSB0aGF0
IGlzIGRvbmUsIHRoZSBkcmFmdA0KaXMgZXhwZWN0ZWQgdG8gYmUgcmVhZHkg
Zm9yIHdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsLg0KDQoNClJUUCBleHRlbnNp
b25zIGZvciBjbGFzc2lmaWNhdGlvbiBhbmQgcHJpb3JpdHkNCg0KS2VuIENh
cmxiZXJnIGRpc2N1c3NlZCBSVFAgZXh0ZW5zaW9ucyBmb3IgY2xhc3NpZmlj
YXRpb24NCihkcmFmdC1jYXJsYmVyZy1SVFAtY2xhc3NpZmllci1leHRlbnNp
b24tMDAudHh0KS4gIFRoaXMgaXMgYSBtZWFucyBvZg0KbWFya2luZyBwYWNr
ZXRzLCBmb3IgZXhhbXBsZSB0byBpbmRpY2F0ZSBlbWVyZ2VuY3kgY2FsbHMs
IGRlZmluZWQgYXMgYQ0KaGVhZGVyIGV4dGVuc2lvbi4gIFRoZXJlIGlzIGFs
c28gYSBkcmFmdCBieSBKYW1lcyBQb2xrDQooZHJhZnQtcG9say1hdnQtcnRw
ZXh0LXJlcy1wcmktMDAudHh0KSB0aGF0IGlzIHZlcnkgc2ltaWxhci4NCg0K
RGF2ZSBPcmFuIG5vdGVkIHRoYXQgdGhpcyBpcyBvbmx5IG5lZWRlZCBpZiB5
b3UgbmVlZCB0byBtYXJrIGRpZmZlcmVudA0KcGFja2V0cyBpbiBhIHN0cmVh
bSBkaWZmZXJlbnRseSwgc2luY2Ugb3RoZXJ3aXNlIHlvdSdkIGp1c3Qgc2ln
bmFsIHRoZQ0KY2xhc3NpZmljYXRpb24gYXQgY2FsbCBzZXR1cCB0aW1lLiAg
U3RldmUgQ2FzbmVyIGFuZCBIZW5uaW5nDQpTY2h1bHpyaW5uZSBhbHNvIGV4
cHJlc3NlZCBjb25mdXNpb24gYWJvdXQgd2h5IHRoaXMgd2FzIHVzZWZ1bCwg
YXMNCm9wcG9zZWQgdG8gc2lnbmFsaW5nIGl0IGR1cmluZyBjYWxsIHNldHVw
IG9yIHVzaW5nIHNvbWV0aGluZyBsaWtlDQpkaWZmZXJlbnRpYXRlZCBzZXJ2
aWNlcyB0byBtYXJrIHRoZSBwYWNrZXRzLiAgTXVjaCBkaXNjdXNzaW9uDQpm
b2xsb3dlZCwgb24gdGhlIHByb3BlciBwbGFjZSB0byBzaWduYWwgdGhpcyBp
bmZvcm1hdGlvbiwgd2l0aCB0aGUNCmV2ZW50dWFsIGNvbnNlbnN1cyBiZWlu
ZyB0aGF0IHRoaXMgd2FzIG5vdCBhcHByb3ByaWF0ZSB0byBzaWduYWwgaW4N
ClJUUCBwYWNrZXRzLiAgRnVydGhlciBhY3Rpb24gd2FzIGRlZmVycmVkIHVu
dGlsLCBhbmQgdW5sZXNzLCBhIG1vcmUNCmNvbXBsZXRlIHVzZSBjYXNlIGlz
IGRlZmluZWQuDQoNCg0KRXh0ZW5kZWQgUlRQIFByb2ZpbGUgZm9yIFJUQ1At
YmFzZWQgRmVlZGJhY2sNCg0KSm9lcmcgT3R0IHVwZGF0ZWQgdGhlIGdyb3Vw
IG9uIHRoZSBwcm9maWxlIGZvciBSVENQLWJhc2VkIGZlZWRiYWNrDQooZHJh
ZnQtaWV0Zi1hdnQtcnRjcC1mZWVkYmFjay0wMS50eHQpIGFuZCB0aGUgYXNz
b2NpYXRlZCBzaW11bGF0aW9uDQpyZXN1bHRzIChkcmFmdC1idXJtZWlzdGVy
LWF2dC1ydGNwLWZlZWRiYWNrLXNpbS0wMC50eHQpLiAgQ2hhbmdlcw0Kc2lu
Y2UgdGhlIGxhc3QgbWVldGluZyBpbmNsdWRlIGludmVzdGlnYXRpb25zIGlu
dG8gdGltZXIgZGlzdHJpYnV0aW9uDQphbmQgZGl0aGVyaW5nIHNjaGVtZXMs
IHVwZGF0ZXMgdG8gdGhlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIGFuZA0K
aW50cm9kdWN0aW9uLCBhbmQgZXh0ZW5zaXZlIHNpbXVsYXRpb24sIHJlc3Vs
dHMgb2Ygd2hpY2ggYXJlIHJlcG9ydGVkDQppbiBkcmFmdC1idXJtZWlzdGVy
LWF2dC1ydGNwLWZlZWRiYWNrLXNpbS0wMC50eHQuICBUaGVyZSBhcmUgYWxz
byB0d28NCmludGVyb3BlcmFibGUgaW1wbGVtZW50YXRpb25zLCB3aGljaCBz
ZWVtIHRvIHZhbGlkYXRlIHRoZSBzaW11bGF0aW9uDQpyZXN1bHRzLiAgVGhl
cmUgaXMgb25lIHJlbWFpbmluZyBvcGVuIGlzc3VlOiBzdXBwcmVzc2lvbiBv
ZiB1bmtub3duDQpmZWVkYmFjay4gIFdoYXQgc2hvdWxkIGEgcmVjZWl2ZXIg
ZG8gaWYgaXQgcmVjZWl2ZXMgYSBmZWVkYmFjayBwYWNrZXQNCml0IGRvZXMg
bm90IHVuZGVyc3RhbmQ/ICBTaG91bGQgaXQgc3VwcHJlc3MgaXRzIG93biBm
ZWVkYmFjaz8gIFRoZQ0KYXV0aG9ycyBwcm9wb3NlIHRoYXQgcmVjZWl2ZXJz
IHNob3VsZCBub3Qgc3VwcHJlc3MgaWYgdGhleSByZWNlaXZlDQp1bmtub3du
IHBhY2tldHMuICBTdGV2ZSBDYXNuZXIgYWdyZWVkLCBzYXlpbmcgdGhhdCBo
ZSB3YXMgbm93DQpjb252aW5jZWQgdGhhdCB0aGVyZSBpcyBub3QgYW4gaW1w
bG9zaW9uIHByb2JsZW0uICBIb3dldmVyLCBoZSBub3RlZA0KdGhhdCB0aGUg
ZHJhZnQgbmVlZHMgdG8gZXhwbGFpbiB3aHkgdGhlcmUgaXMgbm90IGFuIGlt
cGxvc2lvbiBwcm9ibGVtDQpzbyB0aGF0IG90aGVycyAoZXNwZWNpYWxseSB0
aGUgSUVTRykgd2lsbCBub3QgYmUgbGVmdCB3b25kZXJpbmcuICBUaGUNCnJl
c3VsdCwgSm9lcmcgbm90ZWQsIGlzIHRoYXQgdGhlIEdlbmVyaWMgSU5GTyBw
YWNrZXQgbmVlZHMgdG8gYmUNCnJlbW92ZWQ7IHRpbWVyIHVzZSBhbHNvIHNo
b3VsZCBiZSBjbGFyaWZpZWQuICBPbmNlIHRoaXMgaXMgZG9uZSwgaXQgaXMN
CmV4cGVjdGVkIHRoYXQgdGhlIGRyYWZ0IHdpbGwgYmUgcmVhZHkgZm9yIGxh
c3QgY2FsbC4gIFN0ZXZlIGFza2VkIGlmDQpmb2xrcyB3ZXJlIGNvbWZvcnRh
YmxlIHdpdGggdGhpcyBleHRlbnNpb24gZ29pbmcgdG8gV0cgbGFzdCBjYWxs
PyAgTm8NCm9iamVjdGlvbnMgd2VyZSByYWlzZWQuDQoNCg0KUlRQIHJldHJh
bnNtaXNzaW9uDQoNCkRhdmlkIExlb24gZGlzY3Vzc2VkIGNoYW5nZXMgdG8g
dGhlIFJUUCByZXRyYW5zbWlzc2lvbiBmcmFtZXdvcmsNCihkcmFmdC1sZW9u
LXJ0cC1yZXRyYW5zbWlzc2lvbi0wMS50eHQpLiAgVGhlIHBheWxvYWQgZm9y
bWF0IGhhcyBiZWVuDQpjaGFuZ2VkIHRvIGJldHRlciB1c2UgdGhlIFJUUCBo
ZWFkZXI7IHRoZSBydWxlcyBleHBsYWluaW5nIGhvdyB0bw0KYXNzb2NpYXRl
IHRoZSBvcmlnaW5hbCBhbmQgcmV0cmFuc21pdHRlZCBzdHJlYW1zIGhhdmUg
YmVlbiBjbGFyaWZpZWQ7DQphbmQgdGhlIHJlYXNvbiB3aHkgcmV0cmFuc21p
c3Npb25zIGFyZSBzZW50IGluIGEgZGlmZmVyZW50IHN0cmVhbSB0bw0KdGhl
IG9yaWdpbmFsIGhhcyBiZWVuIGNsYXJpZmllZCAodG8gYWxsb3cgdGhlIHJl
Y2VpdmVyIHRvDQpkaWZmZXJlbnRpYXRlIGJldHdlZW4gbG9zc2VzIGluIHRo
ZSBvcmlnaW5hbCBzdHJlYW0gYW5kIGxvc3NlcyBvZg0KcmV0cmFuc21pdHRl
ZCBwYWNrZXRzLCBhbmQgdG8gYXZvaWQgY29ycnVwdGluZyB0aGUgUlRDUCBq
aXR0ZXINCmVzdGltYXRlKS4gIEFuIGltcGxlbWVudGF0aW9uIGV4aXN0cywg
YW5kIHBlcmZvcm1hbmNlIHJlc3VsdHMgd2VyZQ0KYnJpZWZseSBwcmVzZW50
ZWQgYW5kIGRpc2N1c3NlZC4gIFN0ZXZlIENhc25lciBub3RlZCB0aGF0IHRo
ZQ0KY29uZ2VzdGlvbiBjb250cm9sIHNlY3Rpb24gbmVlZHMgZXhwYW5zaW9u
IGFuZCBjbGFyaWZpY2F0aW9uLg0KDQpEYXZpZCBMZW9uIGFza2VkIGZvciBm
ZWVkYmFjayBvbiB0aGUgdHJhZGUtb2ZmIGludm9sdmVkIGluIGhhdmluZyB0
d28NClJUUCBzZXNzaW9uLCB2ZXJzdXMgc2VuZGluZyB0aGUgZmVlZGJhY2sg
b24gdGhlIHNhbWUgc2Vzc2lvbiBhcyB0aGUNCm9yaWdpbmFsIG1lZGlhLiAg
U3RldmUgQ2FzbmVyIG5vdGVkIHRoYXQgdGhpcyBpcyB0aGUgbWFpbiBkaWZm
ZXJlbmNlDQpiZXR3ZWVuIHRoaXMgd29yayBhbmQgZHJhZnQtaWV0Zi1hdnQt
cnRwLXNlbHJldC0wMy50eHQuICBTdGVwaGFuDQpXZW5nZXIgY29tbWVudGVk
IHRoYXQgYSByZWNlbnQgSVRVLVQgbWVldGluZyBoYWQgYSBwcm9wb3NhbCBm
b3IgdXNpbmcNCnRoZSBTU1JDIHRvIGlkZW50aWZ5IHNlc3Npb25zLCByYXRo
ZXIgdGhhbiB0aGUgVURQIHBvcnQgbnVtYmVyLCBzaW5jZQ0Kc29tZSBpbXBs
ZW1lbnRhdGlvbnMgaGF2ZSBwcm9ibGVtcyB3aGVuIG1hbnkgcG9ydHMgYXJl
IHVzZWQuICBIZQ0KZG9lc24ndCBsaWtlIHRoYXQgcHJvcG9zYWwsIGJ1dCB3
ZSBtaWdodCB3YW50IHRvIHRha2UgdGhpcyB0eXBlIG9mDQppbXBsZW1lbnRh
dGlvbiBjb25zaWRlcmF0aW9ucyBpbnRvIGFjY291bnQuICBJdCB3YXMgYWxz
byBub3RlZCB0aGF0DQp0aGVyZSBpcyBubyB3YXkgb2Ygc3BlY2lmeWluZyB0
aGF0IHNvbWUgc3Vic2V0IG9mIHBhY2tldHMgaW4gYSBzZXNzaW9uDQphcmUg
bm90IGNhY2hlYWJsZSwgYW5kIHRoYXQgc2VuZGluZyBwYWNrZXRzIGluIGEg
c2luZ2xlIHN0cmVhbSBtYXkNCmNvbmZ1c2UgbmFpdmUgaW1wbGVtZW50YXRp
b25zIG9mIGNhY2hlcy4gIFN0ZXZlIENhc25lciBub3RlZCB0aGF0IGhlDQps
aWtlcyB0aGUgaWRlYSBvZiBrZWVwaW5nIHRoZSByZXRyYW5zbWlzc2lvbnMg
c2VwYXJhdGUsIHNpbmNlIGl0IG1ha2VzDQp0aGUgcHJvdG9jb2wgY2xlYW5l
ciwgbGVhdmluZyBtdWx0aXBsZXhpbmcgdG8gdGhlIGxvd2VyIGxheWVycy4N
Cg0KSGVubmluZyBTY2h1bHpyaW5uZSByYWlzZWQgdGhlIGlzc3VlIG9mIHBp
Z2d5YmFja2luZyByZXRyYW5zbWl0dGVkDQpwYWNrZXRzIG9uIHRoZSBvcmln
aW5hbCBwYWNrZXRzLCBmb3IgZXhhbXBsZSB1c2luZyB0aGUgcGFyaXR5IEZF
Qw0KZm9ybWF0IHRvIHNlbmQgcmV0cmFuc21pdHRlZCBkYXRhICh0byByZWR1
Y2UgdGhlIG92ZXJoZWFkcykuICBKb25hdGhhbg0KUm9zZW5iZXJnIG5vdGVk
IHRoYXQgdGhlIFJGQyAyNzMzIGZvcm1hdCBjb3VsZCBiZSB1c2VkIHVuY2hh
bmdlZCBhcyBhDQpyZXRyYW5zbWlzc2lvbiBmb3JtYXQsIGFzIGFuIGFsdGVy
bmF0aXZlIHRvIHRoaXMgcHJvdG9jb2wuICBTdGV2ZQ0KQ2FzbmVyIG5vdGVk
IHRoYXQgUkZDIDIxOTggbWlnaHQgYWxzbyBiZSBzdWl0YWJsZSwgYWx0aG91
Z2ggaXQgaGFzIGENCmRpZmZlcmVudCBzZXQgb2YgY29uc3RyYWludHMuICBD
b2xpbiBQZXJraW5zIG5vdGVkIHRoYXQgUkZDIDIxOTggYWxzbw0KZG9lc24n
dCBjb21wbGV0ZWx5IHByZXNlcnZlIHRoZSBSVFAgaGVhZGVyIGZpZWxkcy4N
Cg0KRGF2ZSBTaW5nZXIgcmFpc2VkIHRoZSBpc3N1ZSBvZiBjb25nZXN0aW9u
IGNvbnRyb2wsIGNpdGluZyB0aGUNCnBvc2l0aXZlIGZlZWRiYWNrIGxvb3Ag
aW5oZXJlbnQgaW4gYW55IG5vbi1jb25nZXN0aW9uIGNvbnRyb2xsZWQNCnJl
dHJhbnNtaXNzaW9uLiAgVGhpcyBpcyBjbGVhcmx5IHNvbWV0aGluZyB0aGF0
IGlzIG9mIGltcG9ydGFuY2UsIGFuZA0Kc2hvdWxkIGJlIGFkZHJlc3NlZCBp
biB0aGUgZHJhZnQuDQoNCkZ1cnRoZXIgZGlzY3Vzc2lvbiBpcyBjbGVhcmx5
IG5lZWRlZCwgb24gdGhlIG1haWxpbmcgbGlzdC4NCg0KDQpSVENQIEV4dGVu
c2lvbiBmb3IgU1NNIFNlc3Npb25zIHdpdGggVW5pY2FzdCBmZWVkYmFjaw0K
DQpKdWxpYW4gQ2hlc3RlcmZpZWxkIHByZXNlbnRlZCBhbiBSVENQIGV4dGVu
c2lvbiBmb3Igc2luZ2xlIHNvdXJjZQ0KbXVsdGljYXN0IChkcmFmdC1jaGVz
dGVyZmllbGQtYXZ0LXJ0Y3Bzc20tMDIudHh0KSwgdXNpbmcgdW5pY2FzdCBm
b3INClJUQ1AgZmVlZGJhY2suICBDaGFuZ2VzIHNpbmNlIHRoZSBsYXN0IG1l
ZXRpbmc6IHJlc3RydWN0dXJlIHdpdGggbW9yZQ0KZm9jdXMgb24gc2VjdXJp
dHk7IG1vZHVsYXJpemUgdGhlIFJTSSBwYWNrZXQgZm9ybWF0IHdpdGggYWRk
aXRpb24gb2YgYQ0KbmV3IHJlcG9ydCBibG9jayAodGhlIGxvc3Mgaml0dGVy
IHN1bW1hcnkgYmxvY2spOyBTRFAgc2Vzc2lvbiBsZXZlbA0KYXR0cmlidXRl
cyBhZGRyZXNzZWQ7IHRoZSBzb3VyY2UgbWF5IG5vIGxvbmdlciBjaGFuZ2Ug
cmVwb3J0aW5nDQpmb3JtYXRzIGR1cmluZyBhIHNlc3Npb247IHRoZSBjb21w
bGV4aXR5IG9mIHRoZSBtaXhlci90cmFuc2xhdG9yIHJ1bGVzDQpoYXMgYmVl
biByZW1vdmVkOyBtb3JlIGRldGFpbHMgb24gaWRlbnRpZnlpbmcgU1NSQyBj
b2xsaXNpb25zIGhhdmUNCmJlZW4gYWRkZWQuDQoNCkZlZWRiYWNrIHdhcyBz
b2xpY2l0ZWQgb24gdGhlIGxvc3Mgaml0dGVyIHN1bW1hcnkgYmxvY2tzLiAg
Q29saW4NClBlcmtpbnMgd29uZGVyZWQgaWYgdGhlc2UgUlRDUCBleHRlbnNp
b25zLCBvciBzb21ldGhpbmcgbGlrZSB0aGVtLA0KY291bGQgYmUgZXh0cmFj
dGVkIGZyb20gdGhpcyBkcmFmdCB0byBtYWtlIHRoZW0gbW9yZSBnZW5lcmFs
bHkgdXNlZnVsPw0KU3RldmUgQ2FzbmVyIG5vdGVkIHRoYXQgdGhpcyBoYXMs
IHNvIGZhciwgYmVlbiBhIHBhcGVyIGRlc2lnbiBwcm9jZXNzLg0KV2UgbWF5
IG5vdCBrbm93IGlmIHRoaXMgaXMgdXNlZnVsIHVudGlsIHdlIGhhdmUgcmVh
bCBpbXBsZW1lbnRhdGlvbnMuDQpKdWxpYW4gbm90ZWQgdGhhdCBoZSBoYXMg
YW4gaW1wbGVtZW50YXRpb24gaW4gcHJvZ3Jlc3MuDQoNClN0ZXZlIENhc25l
ciBub3RlZCB0aGF0IHRoZSBleHBhbmRlZCBkaXNjdXNzaW9uIG9mIHNlY3Vy
aXR5IGFuZA0KYXV0aGVudGljYXRpb24gaXMgZ29vZCwgYnV0IHdvbmRlcmVk
IGlmIGl0IGlzIHN1ZmZpY2llbnQgKGZvciBleGFtcGxlLA0KYmVjYXVzZSB0
aGlzIHB1dHMgcmVxdWlyZW1lbnRzIGZvciBhdXRoZW50aWNhdGlvbiBvbiB0
aGUgc2lnbmFsaW5nDQpwcm90b2NvbCB1c2VkIHdpdGggaXQsIHdoaWNoIG1h
eSBub3QgYmUga25vd24pLiAgUm9zcyBGaW5sYXlzb24NCndvbmRlcmVkIGlm
IHRoZXJlIGlzIHNvbWUgd2F5IGluIHdoaWNoIHJlY2VpdmVycyBjYW4ga25v
dyB0byBzdG9wDQpzZW5kaW5nIFJUQ1AsIGlmIHRoZXkgZG8gbm90IGhlYXIg
ZnJvbSB0aGUgc2VuZGVyIGZvciBzb21lIHRpbWUNCnBlcmlvZCwgdG8gbGlt
aXQgdGhlIGR1cmF0aW9uIG9mIGFueSBwYWNrZXQgYm9tYmluZyBhdHRhY2s/
DQoNCg0KRXh0ZW5kaW5nIFJUQ1AgZm9yIGNhbGwgcXVhbGl0eSBtZXRyaWNz
DQoNClRoZSBmaW5hbCBwcmVzZW50YXRpb24gd2FzIGJ5IEFsYW4gQ2xhcmss
IGludHJvZHVjaW5nIG5ldyB3b3JrIHRoYXQgaXMNCm5vdCB5ZXQgZGVzY3Jp
YmVkIGluIGFuIGludGVybmV0LWRyYWZ0LiAgVGhlIGFpbSBpcyB0byBpbmNs
dWRlIGV4dHJhDQppbmZvcm1hdGlvbiBpbiBSVENQLCB0byByZXBvcnQgb24g
cGVyY2VpdmVkIHZvaWNlIHF1YWxpdHksIGFmdGVyIGFsbA0KZXJyb3IgY29u
Y2VhbG1lbnQgYW5kIGNvcnJlY3Rpb24gaGFzIGJlZW4gcGVyZm9ybWVkLiAg
RGF2ZSBPcmFuIG5vdGVkDQp0aGF0IGFsbCB0aGlzIGluZm9ybWF0aW9uIGlz
IGF2YWlsYWJsZSB0b2RheSB1c2luZyBTTk1QOyB0aGUNCm1vdGl2YXRpb24g
aXMgcHJlc3VtYWJseSB0aGVyZWZvcmUgc28gdGhlIHNlbmRlciBjYW4gdXNl
IHRoaXMNCmluZm9ybWF0aW9uIHRvIGFkYXB0IGl0cyB0cmFuc21pc3Npb24/
ICBXaGF0IGlzIHRoZSBhZHZhbnRhZ2Ugb2YNCmluY2x1ZGluZyB0aGlzIGlu
Zm9ybWF0aW9uIGluIFJUQ1AsIHJhdGhlciB0aGFuIHVzaW5nIFNOTVA/ICBB
bGFuDQpkaXNhZ3JlZWQgc29tZXdoYXQsIHNheWluZyB0aGF0IHRoZSBpbmZv
cm1hdGlvbiB3YXMgdXNlZnVsIGZvciBuZXR3b3JrDQpwZXJmb3JtYW5jZSBt
b25pdG9yaW5nLiAgRGF2ZSBPcmFuIG5vdGVkIHRoYXQgUlRDUCBkb2VzIG5v
dA0KbmVjZXNzYXJpbHkgZm9sbG93IHRoZSBzYW1lIHBhdGggYXMgdGhlIG1l
ZGlhLCBzbyB5b3UgbWlnaHQgbm90IGJlDQphYmxlIHRvIHNlZSB0aGUgZmVl
ZGJhY2sgYW55d2F5PyAgSGVubmluZyBTY2h1bHpyaW5uZSBub3RlZCB0aGF0
IHRoZQ0Kcm91dGluZyBvZnRlbiBiZWNvbWVzIHN5bW1ldHJpYyBhdCB0aGUg
ZWRnZXMsIHNvIHRoaXMgbWF5IG5vdCBiZSBhbg0KaXNzdWUuICBBbHNvLCBo
ZSBub3RlZCB0aGF0IGludGVyLWRvbWFpbiBTTk1QIGlzIG9mdGVuIG5vdCBw
b3NzaWJsZSwNCnNvIHRoaXMgbWF5IGJlIHVzZWZ1bCBmb3IgdGhhdCBwdXJw
b3NlLiAgSGVubmluZyB3b25kZXJlZCBob3cgdGhlDQppbXBhaXJtZW50IGNv
dWxkIGJlIGV4cHJlc3NlZCwgTU9TIG9yIFBFU1Egc2NvcmVzPyAgWWVzLCBw
ZXJoYXBzLg0KU3RldmUgQ2FzbmVyIHdvbmRlcmVkIGlmIHRoZSBzZW5kZXIg
b3IgcmVjZWl2ZXIgY291bGQgdXNlIHRoaXMNCmluZm9ybWF0aW9uIHRvIGRv
IHRoaW5ncyBkaWZmZXJlbnRseS4gIElmIG5vdCwgd2h5IGluY2x1ZGUgdGhp
cz8gIEZvcg0KZXhhbXBsZSwgdGhlIGRpc3RyaWJ1dGlvbiBvZiBsb3NzIHdp
bGwgY2xlYXJseSBoYXZlIGFuIGltcGFjdCBvbiB0aGUNCnF1YWxpdHksIGJ1
dCBrbm93aW5nIGl0IGRvZXMgbm90IG5lY2Vzc2FyaWx5IGFsbG93IHRoZSBy
ZWNlaXZlciB0byBkbw0Kc29tZXRoaW5nIGRpZmZlcmVudGx5LiAgVGhlIHVz
ZSBjYXNlIG5lZWRzIHRvIGJlIHdlbGwgZGVmaW5lZC4gIENvbGluDQpQZXJr
aW5zIGV4cHJlc3NlZCBhIHNpbWlsYXIgY29uY2VybjogaGUgY2FuIHNlZSBo
b3cgbW9yZSBkZXRhaWwgb24gdGhlDQpsb3NzIG9yIGppdHRlciBwYXR0ZXJu
cyBjYW4gYmUgdXNlZCB0byBhZGFwdCwgYnV0IGhvdyBkb2VzIGEgcGVyY2Vp
dmVkDQpxdWFsaXR5IHNjb3JlIGhlbHA/ICBUaGVyZSB3YXMgbXVjaCByZWxh
dGVkIGRpc2N1c3Npb24uICBIZW5uaW5nDQpTY2h1bHpyaW5uZSBub3RlZCB0
aGF0IFNMQSBtb25pdG9yaW5nIG1pZ2h0IGJlIG9uZSBhcHBsaWNhdGlvbiwg
YXMNCm1pZ2h0IGJlIHJvdXRlIHNlbGVjdGlvbiBiZXR3ZWVuIHRoZSBwdWJs
aWMgbmV0d29yaywgYW5kIGEgcHJpdmF0ZQ0KbGVhc2VkIGxpbmUuICBDb2xp
biBQZXJraW5zIG5vdGVkIHRoYXQgdGhlcmUgaGFzIGJlZW4gZWFybGllciB3
b3JrIG9uDQpwcm92aWRpbmcgbW9yZSBkZXRhaWxlZCBSVENQIGZlZWRiYWNr
IGluIEFWVCwgd2hpY2ggbWlnaHQgYmUgcmVsZXZhbnQuDQpTdGV2ZSBDYXNu
ZXIgYXNrZWQgaWYgdGhlcmUgYXJlIGFueSBJUFIgY29uc2lkZXJhdGlvbnMg
b24gdGhpcyB3b3JrPw0KVGhlcmUgYXJlIG5vdC4gIFRoZSBuZXh0IHN0ZXAg
aW4gdGhpcyB3b3JrIGlzIHRvIHByZXBhcmUgYSBkcmFmdCBvbg0KdGhlc2Ug
aWRlYXMsIGZvciByZXZpZXcgYXQgZnV0dXJlIG1lZXRpbmdzLg0KDQpUaGUg
bWVldGluZyBjb25jbHVkZWQgd2l0aCBhIGJyaWVmIGRlbW9uc3RyYXRpb24g
b2YgdGhlIHJldHJhbnNtaXNzaW9uDQp3b3JrLCBieSBEYXZpZCBMZW9uLg0K

--0-896327955-1011066200=:85116--

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



From daemon@optimus.ietf.org  Wed Jan 16 04:00:31 2002
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 EAA02960
	for <avt-archive@odin.ietf.org>; Wed, 16 Jan 2002 04:00:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA22759
	for avt-archive@odin.ietf.org; Wed, 16 Jan 2002 04:00:33 -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 DAA22439;
	Wed, 16 Jan 2002 03:55:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22408
	for <avt@optimus.ietf.org>; Wed, 16 Jan 2002 03:55:26 -0500 (EST)
Received: from mail.shfe.com.cn (IDENT:root@[202.101.28.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02933
	for <avt@ietf.org>; Wed, 16 Jan 2002 03:55:21 -0500 (EST)
From: us-ordination@yahoo.com
Received: from lance ([202.79.117.228])
	by mail.shfe.com.cn (8.9.3/8.8.7) with SMTP id PAA20930;
	Wed, 16 Jan 2002 15:53:59 +0800
Message-Id: <200201160753.PAA20930@mail.shfe.com.cn>
Reply-To: us-ordination@yahoo.com
To: srini2069@hotmail.com
CC: mehanti@aol.com, zcjensen@hotmail.com, nenegoose@hotmail.com,
        anders365@gateway.net, mskirk@excite.com, sedraw@hotmail.com,
        slim49@hotmail.com, verdon@esb.com, dori_province@hotmail.com,
        harold_11@hotmail.com, janinejanine19@hotmail.com, avt@ietf.org,
        future22@aol.com, lcomm@usa.net, sharris972@aol.com,
        solaye243@hotmail.com, martone@intnet.net, robertr@asymetrix.com,
        clayton@lni.net, azfaulkner@home.com, aamador454@hotmail.com,
        djohnson@cmsinter.net, pfac1@hotmail.com, moxy106@hotmail.com,
        everett@az.com, oreillyp@vei.net, a36dd@hotmail.com,
        72537.2423@compuserve.com, ralph_13@fiam.net, calmagro@hotmail.com,
        fifi001@usa.net, c.vanderford@freeuk.com, geir@mindless.com,
        jftomlin@hotmail.com
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Wed, 16 Jan 2002 03:52:07 -0500
Subject: [AVT] GET ORDAINED BY THE END OF THE WEEK
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

STREET BISHOPS, a U.S. based international ministry, has the authority to ORDAIN you this week.                             

STREET BISHOPS beleives that ordiation should be given to all who ask, regaurdless of thier theological throught, as long as they are committed to serving the hearts and minds of man, following the guidence and love of God. One of the benefits of being LEGAL a member of the clergy, you will be authorized to perform the rites and ceremonies of the church. They include:

WEDDINGS - You can marry earn part-time income officiating marriages on weekends. Couples are searching for a wedding officiates. Most states require that you register your certificate (THAT WE SEND YOU) with the state prior to conducting the ceremony. And we have thousands of inquiries each year requesting ministers all over the country to conduct weddings - we can place you in our database of available officiates! One pastor works full time as a wedding officiate, so can you!

FUNERALS - The simple fact is that people die every day, providing a never-ending need for funeral officiates. Whether its for a friend, family member, or community member, you can fulfill a spiritual as well as community service. Don't settle for a minister you don't know!! Most states require that you register your certificate (THAT WE SEND YOU) with the state prior to conducting the ceremony.

BAPTISMS - What a special way to welcome a child of God. As millions return to church and desire these official ceremonies, you are there to assist them! This adds to your part or full time income as a minister!

PASTORAL COULSELING - Just clergy have for centuries been advisors, you too enjoy limited privileges as a pastoral counselor assisting individuals in their time of need. Of course, forgiveness of Sins is granted to all who ask in sincerity and willingness to change for the better and you can be the one to guide hurting individuals towards healing, love, and God.

CORRECTIONAL FACILITIES - PRISON MINISTRIES - Since you will be a Certified Minister, you can visit others in need. Preach the Word of God to those who have strayed from the flock, who are ready to CHANGE their lives - You can play a major part in that decision!

HOSPITOL MINISTRIES - A an ordained clergy, you can be listed with most hospitals and conduct a successful hospital ministry.

WANT TO START YOUR OWN CHURCH? After your ordination, you may start your own congregation! We can offer much assistance as you begin your new place of worship.

WHICH RELIGION? Street Bishops is an interdenominational/interfaith association. We have ordinained Protestants, Catholics, and other traditions serving God. By serving people you serve the creator, within your own chosen tradition. 

COMMUNITY - You are joining a comminity of beleivers that are back to the basics. Serving others is a priority of our Clergy, come and join out community of service pastors.

Our goal is to make this life changing program affordable so average folks like you can benefit from the advantages of being ordained, therefore the admnistrative costs for processing the ordination is only $29.00.
            
For an administrative fee of only $29.00, you will receive a professionally printed 8-inch by 10-inch color certificate, a Proof of Minister Certification in your name. We pay the shipping. For Shipping OUTSIDE the US please add $15.00.

FAX: To place your order by fax, complete the following form and fax to 1-413-487-7457 or use postal mail. We will not charge your credit card until the documents are in the mail. 

MAIL: For Cash, Check, or Money Order, complete the form below, make your check payable to "Street Bishops"  and mail to

Street Bishops Ordination Committee
3206 South Hopkins Ave, PMB 89
Titusville, Florida 32780

(ALL APPLICATIONS FILLED WITHIN 3 DAYS DAYS OF RECEIVING THEM)
*Please allow 8 days to receive your certificate by mail. If you do not receive your order within 10 days, please send us a fax letting us know of the late arrival.  We will then contact you to figure out why you have not received your order. 

(Please print very clearly in dark ink)

---------------- Ordination Information ------------------------

Name of Applicant:

Address:

City, State, Zip Code:

Phone Number:

Email Address:

Social Security Number:

Denomination (if any):

Preferred Title: (example Rev., Pastor, Fr., Priest, etc) __________________

------------ Credit Card Order Form ----------------------------

Name on Credit Card: 

Address:

City/State/ZIP:

Your email address: 

Your card will be charged $29.00 for your Ordination Certificate/Credentials.

Type of Card, circle one (Visa, MasterCard)

Credit Card Number: 
Sorry, we do not accept Discover or AMEX.

Date Credit Card Expires: 

Phone Number: 

Fax Number: 

---- To order by Check or Money Order ----------------

*Please allow 8 days to receive your certificate by mail. This includes the time for out committee to meet, approve the ordination, perpare the certificate and postal progress.
If you do not receive your order within 10 days, please send us a fax letting us know of the late arrival.  We will then contact you to figure out why you have not received your order.




 .

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



From daemon@optimus.ietf.org  Wed Jan 16 12:19:25 2002
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 MAA14584
	for <avt-archive@odin.ietf.org>; Wed, 16 Jan 2002 12:19:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA10709
	for avt-archive@odin.ietf.org; Wed, 16 Jan 2002 12:19:29 -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 MAA10576;
	Wed, 16 Jan 2002 12:14:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA10547
	for <avt@optimus.ietf.org>; Wed, 16 Jan 2002 12:14:01 -0500 (EST)
Received: from linuxpow.com (IDENT:qmailr@linuxpow.com [12.149.2.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14401
	for <avt@ietf.org>; Wed, 16 Jan 2002 12:13:45 -0500 (EST)
Date: Wed, 16 Jan 2002 12:13:45 -0500 (EST)
Message-Id: <200201161713.MAA14401@ietf.org>
Received: (qmail 24208 invoked from network); 16 Jan 2002 16:30:24 -0000
Received: from buystainlessonline.com (HELO ) (nobody@12.149.2.55)
  by mail.buystainlessonline.com with SMTP; 16 Jan 2002 16:30:24 -0000
To: avt@ietf.org
From: "BuyStainlessOnline.com" <sales@buystainlessonline.com>
Subject: [AVT] The Stainless Steel Network MEGA DEAL
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

Unsubscribe by clicking the link at the bottom of this E-mail! 
It's quick and painless.

The Stainless Steel Network is brought to you by www.buystainlessonline.com

What BuyStainlessOnline users are doing...
----------------------------------------------------------------------
RECENT INQUIRIES:
904L Round Bar
168' 10mm
60'16mm
49' 25mm
NO QUOTE YET

321 Stainless Plate
1/2 x 60 x 96 (7) pcs
QUOTED

440C material, .500" dia x 144" long (840) pcs
QUOTED

310 16ga 48 x 120 20 sheets
QUOTED
------------------------------------------------------------------------
New Items for Sale

OFFER #1  (looking for Best Offer)
Commodity - Stainless Steel Wire.
Grade - AISI 304L.
Size - 0.135"
Surface finish - Matte (Medium Bright)
Condition - Soft Annealed.
U.T.S. - 85,000 to 100,000 psi max.
Quantity - aprox. 40,000 lbs.
Packing - Coils wrapped in HDPE and loaded on Mild Steel Carriers.
Remarks : All material is ex-mill in original mill's packaging.

OFFER #2
Attention Distributors!!! 3,000,000 Pounds of PRIME 304 COILS for sale
The following list of Stainless Steel Hot Rolled Coils is available FOB
Ohio for the following PRICES:
$.50 per pound (1 LOAD min)
$.47 per pound (10 LOAD min)

NOTE, these coils are MILL PRIME... Chemical Properties are listed below
------------------------------------------------------------------------
STEEL	FIN	WIDTH (mm)	THICK (mm)	Weigth (Pounds)	C	Cr	Cu	Mn	Mo	N	Ni	P	S	Si	
304	1	950.0	3.00	 37,238 	0.0450	18.070	0.330	1.470	0.230	0.055	8.090	0.027	0.001	0.350	
304	1	946.0	3.00	 31,698 	0.0470	18.070	0.280	1.320	0.250	0.042	8.040	0.030	0.001	0.360	
304	1	1256.0	3.00	 49,310 	0.0440	18.110	0.240	1.340	0.240	0.042	8.050	0.030	0.001	0.370	
304	1	1255.0	3.00	 44,451 	0.0500	18.290	0.240	1.370	0.250	0.046	8.030	0.031	0.001	0.420	
304	1	1254.0	3.00	 44,572 	0.0500	18.290	0.240	1.370	0.250	0.046	8.030	0.031	0.001	0.420	
304	1	1254.0	3.00	 46,113 	0.0500	18.060	0.320	1.350	0.350	0.042	8.070	0.030	0.001	0.420	
304	1	799.5	3.00	 31,239 	0.0432	18.110	0.250	1.350	0.270	0.042	8.100	0.029	0.001	0.340	
304	1	794.0	3.00	 30,328 	0.0410	18.220	0.280	1.420	0.300	0.047	8.120	0.030	0.001	0.350	
304	1	1256.5	3.00	 49,583 	0.0420	18.110	0.250	1.350	0.270	0.045	8.100	0.029	0.001	0.340	
304	1	1254.5	3.00	 49,453 	0.0420	18.110	0.250	1.350	0.270	0.045	8.100	0.029	0.001	0.340	
304	1	1255.0	3.00	 48,305 	0.0450	18.020	0.320	1.390	0.310	0.046	8.000	0.028	0.001	0.360	
304	1	1252.5	6.00	 49,449 	0.0420	18.030	0.330	1.360	0.240	0.050	8.070	0.025	0.001	0.390	
304	1	1251.5	6.00	 49,427 	0.0410	18.020	0.300	1.350	0.260	0.045	8.090	0.028	0.001	0.380	
304	1	1250.5	6.00	 49,414 	0.0410	18.020	0.300	1.350	0.260	0.045	8.090	0.028	0.001	0.380	
304	1	1253.5	6.00	 49,414 	0.0450	18.080	0.300	1.320	0.250	0.050	8.100	0.031	0.001	0.350	
304	1	1255.5	3.00	 41,821 	0.0430	18.070	0.340	1.390	0.270	0.051	8.100	0.026	0.001	0.480	
304	1	1255.5	2.80	 49,623 	0.0430	18.070	0.340	1.390	0.270	0.051	8.100	0.026	0.001	0.480	
304	1	1254.5	2.80	 49,438 	0.0420	18.090	0.330	1.400	0.330	0.043	8.150	0.026	0.001	0.360	
304	1	1254.0	2.80	 49,436 	0.0420	18.030	0.330	1.360	0.240	0.050	8.070	0.025	0.001	0.390	
304	1	1251.0	2.80	 48,435 	0.0410	18.060	0.270	1.330	0.250	0.051	8.150	0.026	0.001	0.340	
304	1	1256.0	2.80	 49,387 	0.0410	18.060	0.270	1.330	0.250	0.051	8.150	0.026	0.001	0.340	
304	1	1254.5	2.80	 49,493 	0.0410	18.060	0.270	1.330	0.250	0.051	8.150	0.026	0.001	0.340	
304	1	1253.5	2.80	 48,457 	0.0410	18.060	0.270	1.330	0.250	0.051	8.150	0.026	0.001	0.340	
304	1	1221.5	6.00	 49,074 	0.0430	18.060	0.410	1.350	0.240	0.049	8.070	0.027	0.001	0.470	
304	1	1254.5	6.00	 49,334 	0.0430	18.060	0.410	1.350	0.240	0.049	8.070	0.027	0.001	0.470	
304	1	1251.0	6.00	 48,155 	0.0400	18.040	0.320	1.410	0.200	0.050	8.060	0.029	0.001	0.360	
34A	1	947.0	4.70	 37,310 	0.0390	18.130	0.260	1.340	0.190	0.047	8.550	0.027	0.001	0.370	
304	1	951.5	3.00	 36,565 	0.0450	18.050	0.340	1.500	0.270	0.049	8.080	0.031	0.001	0.440	
304	1	950.0	3.00	 37,200 	0.0450	18.050	0.340	1.500	0.270	0.049	8.080	0.031	0.001	0.440	
304	1	951.0	3.00	 37,299 	0.0450	18.050	0.340	1.500	0.270	0.049	8.080	0.031	0.001	0.440	
304	1	949.5	3.00	 37,337 	0.0450	18.050	0.340	1.500	0.270	0.049	8.080	0.031	0.001	0.440	
304	1	948.5	3.00	 37,260 	0.0450	18.050	0.340	1.500	0.270	0.049	8.080	0.031	0.001	0.440	
304	1	1252.0	6.00	 43,333 	0.0450	18.080	0.300	1.320	0.250	0.050	8.100	0.031	0.001	0.350	
304	1	1251.5	6.00	 49,561 	0.0450	18.080	0.300	1.320	0.250	0.050	8.100	0.031	0.001	0.350	
304	1	946.5	3.00	 37,211 	0.0450	18.070	0.330	1.470	0.230	0.055	8.090	0.027	0.001	0.350	
304	1	947.5	3.00	 37,277 	0.0450	18.070	0.330	1.470	0.230	0.055	8.090	0.027	0.001	0.350	
304	1	951.5	3.00	 37,134 	0.0450	18.070	0.330	1.470	0.230	0.055	8.090	0.027	0.001	0.350	
304	1	949.0	3.00	 36,490 	0.0450	18.070	0.330	1.470	0.230	0.055	8.090	0.027	0.001	0.350	
304	1	1255.0	3.00	 48,450 	0.0460	18.030	0.240	1.370	0.210	0.042	8.030	0.029	0.001	0.360	
304	1	1256.0	3.00	 48,338 	0.0460	18.030	0.240	1.370	0.210	0.042	8.030	0.029	0.001	0.360	
304	1	1254.5	3.00	 49,195 	0.0460	18.030	0.240	1.370	0.210	0.042	8.030	0.029	0.001	0.360	
304	1	1255.5	3.00	 49,449 	0.0460	18.030	0.240	1.370	0.210	0.042	8.030	0.029	0.001	0.360	
304	1	1256.5	3.00	 48,638 	0.0450	18.090	0.250	1.360	0.250	0.049	8.070	0.028	0.001	0.370	
304	1	1255.5	3.00	 47,672 	0.0450	18.090	0.250	1.360	0.250	0.049	8.070	0.028	0.001	0.370	
304	1	1255.5	3.00	 49,482 	0.0450	18.090	0.250	1.360	0.250	0.049	8.070	0.028	0.001	0.370	
304	1	1254.5	3.00	 49,493 	0.0450	18.090	0.250	1.360	0.250	0.049	8.070	0.028	0.001	0.370	
304	1	1239.0	3.00	 49,151 	0.0450	18.090	0.250	1.360	0.250	0.049	8.070	0.028	0.001	0.370	
304	1	1255.0	6.00	 49,475 	0.0490	18.030	0.260	1.320	0.280	0.046	8.010	0.031	0.001	0.350	
304	1	1254.5	6.00	 49,286 	0.0490	18.030	0.260	1.320	0.280	0.046	8.010	0.031	0.001	0.350	
304	1	1251.5	6.00	 48,415 	0.0430	18.030	0.250	1.340	0.270	0.050	8.090	0.030	0.001	0.350	
304	1	1251.0	6.00	 47,824 	0.0430	18.030	0.250	1.340	0.270	0.050	8.090	0.030	0.001	0.350	
304	1	1252.5	6.00	 48,364 	0.0430	18.030	0.250	1.340	0.270	0.050	8.090	0.030	0.001	0.350	
34A	1	795.0	3.00	 28,968 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	798.0	3.00	 31,367 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	797.0	3.00	 31,389 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	796.5	3.00	 31,338 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	798.5	3.00	 31,550 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	797.5	3.00	 31,473 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	800.0	3.00	 30,613 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	798.0	3.00	 30,988 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	796.0	3.00	 31,354 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
34A	1	798.0	3.00	 29,374 	0.0400	18.010	0.270	1.370	0.200	0.048	8.550	0.028	0.001	0.300	
304	1	1255.0	3.00	 41,960 	0.0490	18.030	0.260	1.320	0.280	0.046	8.010	0.031	0.001	0.350	
304	1	1253.5	3.00	 41,675 	0.0490	18.030	0.260	1.320	0.280	0.046	8.010	0.031	0.001	0.350	
304	1	1257.0	3.00	 43,397 	0.0420	18.060	0.300	1.380	0.340	0.048	8.040	0.028	0.001	0.350	
304	1	1258.0	3.00	 49,409 	0.0410	18.030	0.270	1.340	0.250	0.050	8.040	0.027	0.001	0.290	
304	1	1253.0	3.00	 49,433 	0.0410	18.030	0.270	1.340	0.250	0.050	8.040	0.027	0.001	0.290	
304	1	1253.0	3.00	 49,563 	0.0400	18.080	0.270	1.390	0.270	0.050	8.070	0.028	0.001	0.350	
304	1	1253.0	3.00	 49,497 	0.0400	18.080	0.270	1.390	0.270	0.050	8.070	0.028	0.001	0.350	
304	1	1256.0	3.00	 49,548 	0.0400	18.080	0.270	1.390	0.270	0.050	8.070	0.028	0.001	0.350	
304	1	1254.5	3.00	 48,616 	0.0400	18.080	0.270	1.390	0.270	0.050	8.070	0.028	0.001	0.350	
304	1	1258.0	3.00	 48,580 	0.0400	18.080	0.270	1.390	0.270	0.050	8.070	0.028	0.001	0.350	
304	1	1254.0	3.00	 49,460 	0.0420	18.060	0.300	1.380	0.340	0.048	8.040	0.028	0.001	0.350	
304	1	1254.0	3.00	 48,472 	0.0430	18.200	0.260	1.360	0.260	0.043	8.070	0.028	0.001	0.380	
34A	1	800.5	3.00	 31,534 	0.0410	18.030	0.330	1.340	0.250	0.050	8.530	0.029	0.001	0.360	
34A	1	798.0	3.00	 31,495 	0.0410	18.030	0.330	1.340	0.250	0.050	8.530	0.029	0.001	0.360	
34A	1	799.0	3.00	 31,499 	0.0410	18.030	0.330	1.340	0.250	0.050	8.530	0.029	0.001	0.360	
34A	1	797.5	3.00	 31,561 	0.0410	18.030	0.330	1.340	0.250	0.050	8.530	0.029	0.001	0.360	
				 3,343,970 											
															
OFFER #3
Stainless Steel SLIT COIL REMNANTS
FOB PHILADELPHIA, PRICES LISTED BELOW, NO MINIMUM PURCHASE.

	This information is provided by BuyStainlessOnline, Inc.				www.buystainlessonline.com					
	Please email Sales@buystainlessonline.com or call 215.604.5922 to place orders.									
	All materials are subject to prior sale.									

Tag	Description	Finish	Thickness	Width	Quantity	Weight	Location	Sale Price	Regular Price	
45146	28 GA 304	2B	0.015	18	1	5031	Phila, P.a.  USA	$1.10	$1.38	
30794	26 GA 201	2D	0.020	21.5	1	4158	Phila, P.a.  USA	$0.88	$1.09	
26202	26 GA 301	2B	0.020	1.375	1	418	Phila, P.a.  USA	$0.63	$0.78	
232512E	26 GA 304	2B	0.020	1.5	3	386	Phila, P.a.  USA	$0.64	$0.80	
45062	26 GA 304	POL/VC	0.020	11.75	1	2393	Phila, P.a.  USA	$0.63	$0.78	
229878	26 GA 430	2B	0.020	3.5	2	936	Phila, P.a.  USA	$0.19	$0.23	
22840	26 GA 430	BA	0.020	4.5	1	906	Phila, P.a.  USA	$0.25	$0.31	
29364	24 GA 301	POL	0.024	4	1	1427	Phila, P.a.  USA	$0.65	$0.81	
29363	24 GA 301	POL	0.024	4	1	1430	Phila, P.a.  USA	$0.65	$0.81	
35176	24 GA 301	POL	0.024	6	2	4727	Phila, P.a.  USA	$0.53	$0.66	
29362A	24 GA 304	POL	0.024	1.187	4	1024	Phila, P.a.  USA	$0.85	$1.06	
186896	24 GA 304	2B	0.024	2.75	9	2790	Phila, P.a.  USA	$0.75	$0.94	
19023	24 GA 304	2B	0.024	3.75	2	2762	Phila, P.a.  USA	$0.71	$0.89	
61931	24 GA 304	2B	0.024	9	1	1122	Phila, P.a.  USA	$0.59	$0.73	
29584	22 GA 301	POL	0.028	3.5	1	680	Phila, P.a.  USA	$0.66	$0.83	
32794	22 GA 301	2B	0.028	6.75	1	1578	Phila, P.a.  USA	$0.54	$0.67	
84108C	22 GA 304	POL	0.028	1.125	2	444	Phila, P.a.  USA	$0.90	$1.13	
29362B	22 GA 304	POL	0.028	1.187	6	1229	Phila, P.a.  USA	$0.85	$1.06	
32948	22 GA 304	POL	0.028	3.75	2	2858	Phila, P.a.  USA	$0.53	$0.66	
44796	22 GA 304	POL	0.028	11.25	1	2159	Phila, P.a.  USA	$0.69	$0.86	
224335	22 GA 430	POL	0.028	5.5	1	970	Phila, P.a.  USA	$0.06	$0.08	
45099	22 GA 430	BA	0.028	10	1	2175	Phila, P.a.  USA	$0.34	$0.42	
45098	22 GA 430	BA	0.028	10	1	2376	Phila, P.a.  USA	$0.34	$0.42	
243739	20 GA 304	2D	0.035	1.5	3	1194	Phila, P.a.  USA	$0.88	$1.09	
32943	20 GA 304	POL	0.035	3.125	3	2218	Phila, P.a.  USA	$0.78	$0.97	
46336C	20 GA 304	POL	0.035	3.5	1	1013	Phila, P.a.  USA	$0.99	$1.23	
48418E	20 GA 304	POL	0.035	4.125	1	877	Phila, P.a.  USA	$0.88	$1.09	
49488	20 GA 304	2B	0.036	6.1	1	948	Phila, P.a.  USA	$0.71	$0.89	
232335D	18 GA 304	POL	0.048	1.75	4	1111	Phila, P.a.  USA	$0.68	$0.84	
27329	18 GA 304	AF	0.048	1.875	1	260	Phila, P.a.  USA	$0.44	$0.55	
32953	18 GA 304	POL	0.048	2.5	1	513	Phila, P.a.  USA	$0.53	$0.66	
186895	18 GA 304	AF	0.048	3.5	1	610	Phila, P.a.  USA	$0.75	$0.94	
43255	18 GA 304	POL	0.048	5.25	4	5076	Phila, P.a.  USA	$0.44	$0.55	
212565	18 GA 409	2B	0.048	3.75	1	1143	Phila, P.a.  USA	$0.09	$0.11	
191101C	16 GA 304	POL	0.058	1	2	386	Phila, P.a.  USA	$0.98	$1.22	
191101B	16 GA 304	POL	0.058	2	3	1490	Phila, P.a.  USA	$0.98	$1.22	
44820	16 GA 304	BA	0.058	10	1	7504	Phila, P.a.  USA	$0.69	$0.86	
33017	16 GA 430	2B	0.058	4	1	1249	Phila, P.a.  USA	$0.25	$0.31	
43259	14 GA 304	POL	0.075	2.625	2	2684	Phila, P.a.  USA	$0.44	$0.55	
43258	14 GA 304	POL	0.075	4.5	2	1750	Phila, P.a.  USA	$0.44	$0.55	
43260	14 GA 304	POL	0.075	4.75	2	1977	Phila, P.a.  USA	$0.44	$0.55	
27327	14 GA 409	AF	0.075	4.562	1	550	Phila, P.a.  USA	$0.31	$0.39	
27328	14 GA 409	AF	0.075	4.687	1	531	Phila, P.a.  USA	$0.31	$0.39	
35360	MISC GA 3003	H14	0.075	1	4	319	Phila, P.a.  USA	$0.50	$0.63	
168033B	13 GA 301	2B	0.083	3.75	4	3518	Phila, P.a.  USA	$0.65	$0.81	
168033C	13 GA 301	2B	0.083	5.25	2	2442	Phila, P.a.  USA	$0.65	$0.81	
168033A	13 GA 301	2B	0.083	5.25	2	2419	Phila, P.a.  USA	$0.65	$0.81	
243738	13 GA 304	2B	0.083	2.187	3	4028	Phila, P.a.  USA	$0.53	$0.66	
215992A	12 GA 304	2B	0.105	2.75	1	1190	Phila, P.a.  USA	$0.50	$0.63	
43257	12 GA 304	POL	0.105	6.437	2	3092	Phila, P.a.  USA	$0.44	$0.55	
243494	12 GA 304	2B	0.105	20.9	1	8050	Phila, P.a.  USA	$0.48	$0.59	
41325	11 GA 304	2B	0.120	3	1	1772	Phila, P.a.  USA	$0.63	$0.78	
41326	11 GA 304	2B	0.120	3	1	1772	Phila, P.a.  USA	$0.63	$0.78	
41327	11 GA 304	2B	0.120	3	1	1752	Phila, P.a.  USA	$0.63	$0.78	
41328	11 GA 304	2B	0.120	3	1	1761	Phila, P.a.  USA	$0.63	$0.78	
215992	11 GA 304	2B	0.120	3.125	1	1150	Phila, P.a.  USA	$0.50	$0.63	
47400D	11 GA 304	POL	0.120	8.22	1	4630	Phila, P.a.  USA	$0.84	$1.05	
38870	11 GA 316	#1	0.120	3.625	2	5454	Phila, P.a.  USA	$0.60	$0.75	
49098	11 GA 430	BA	0.120	7.781	1	1828	Phila, P.a.  USA	$0.31	$0.39	
46217I	11 GA 5052	H32	0.120	1.5	2	500	Phila, P.a.  USA	$1.10	$1.38	
45031	11 GA 304	HRAP	0.123	1	2	927	Phila, P.a.  USA	$0.60	$0.75	
47400A	11 GA 304	POL	0.125	2.625	2	1272	Phila, P.a.  USA	$0.84	$1.05	
47400C	11 GA 304	POL	0.125	2.625	4	2538	Phila, P.a.  USA	$0.84	$1.05	
42144	10 GA 316L	#1	0.130	8	1	3726	Phila, P.a.  USA	$0.78	$0.97	
45027	3/16" 304L	HRAP	0.196	3	1	1745	Phila, P.a.  USA	$0.60	$0.75	
44814A	1/4" 316L	#1	0.250	1	1	286	Phila, P.a.  USA	$0.83	$1.03	
44814C	1/4" 316L	#1	0.250	1	1	344	Phila, P.a.  USA	$0.83	$1.03	
44814F	1/4" 316L	#1	0.250	1.5	2	1690	Phila, P.a.  USA	$0.83	$1.03	
71103F	1/4" 316L	#1	0.250	2	1	1620	Phila, P.a.  USA	$0.56	$0.70	
44814B	1/4" 316L	#1	0.250	2	5	6140	Phila, P.a.  USA	$0.83	$1.03	
44814D	1/4" 316L	#1	0.250	2	5	5635	Phila, P.a.  USA	$0.83	$1.03	
44814E	1/4" 316L	#1	0.250	2	4	4530	Phila, P.a.  USA	$0.83	$1.03	
44814G	1/4" 316L	#1	0.250	2	2	952	Phila, P.a.  USA	$0.83	$1.03	
44814H	1/4" 316L	#1	0.250	4	3	7385	Phila, P.a.  USA	$0.83	$1.03	


www.BuyStainlessOnline.com
Your Place for Stainless Today.

P 215.604.5922
F 240.358.8483

Click Here to REGISTER!
https://www.buystainlessonline.com/registration/registration.php

Unsubscribe By clicking below: 
 http://www.buystainlessonline.com/email/mail.php?action=delete&eval=42523&email=avt@ietf.org

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



From daemon@optimus.ietf.org  Wed Jan 16 17:24:46 2002
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 RAA22305
	for <avt-archive@odin.ietf.org>; Wed, 16 Jan 2002 17:24:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA22298
	for avt-archive@odin.ietf.org; Wed, 16 Jan 2002 17:24:32 -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 RAA22098;
	Wed, 16 Jan 2002 17:18:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22068
	for <avt@optimus.ietf.org>; Wed, 16 Jan 2002 17:18:03 -0500 (EST)
Received: from hiart.co.kr (hiart.co.kr [211.36.44.66])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22196
	for <avt@ietf.org>; Wed, 16 Jan 2002 17:17:59 -0500 (EST)
Received: from gfjhgfky-zqmydv (unverified [61.153.9.26]) by hiart.co.kr
 (EMWAC SMTPRS 0.83) with SMTP id <B0000480774@hiart.co.kr>;
 Thu, 17 Jan 2002 05:30:14 +0900
Message-ID: <B0000480774@hiart.co.kr>
From: stockalert271396@yahoo.com.tw
To: cedolo@gateway.net
CC: mail@aeronomics.com, bandrews@adobe.com, jamie73@ltinet.com,
        hanson@galenalink.com, cmwhitmore@hotmail.com, teachgal@msn.com,
        srini2069@hotmail.com, mehanti@aol.com, zcjensen@hotmail.com,
        nenegoose@hotmail.com, anders365@gateway.net, mskirk@excite.com,
        sedraw@hotmail.com, slim49@hotmail.com, verdon@esb.com,
        dori_province@hotmail.com, harold_11@hotmail.com,
        janinejanine19@hotmail.com, avt@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 17 Jan 2002 04:36:29 +0800
Subject: [AVT] Stock Alert 271396543332222
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

OTC News Alerts' Last 3 Picks have gained 358%!
Here is our next Hot Pick!


Single Source Financial Services Corp. (OTCBB : SSFL)

URGENT BUY AT $ .60 PER SHARE!

SELL TARGET $3.50 PER SHARE!

SSFL is the fastest growing, publicly-traded credit card transaction
processor through its contractual agreements with Visa USA, KeyCorp 
(NYSE : KEY), and Total Systems Services (NYSE : TSS).

Revenues are soaring for SSFL with the capacity to process in excess
of $120,000,000 per month in credit card transactions!

Watch for analyst "Strong Buy Recommendations" and several advisory
Newsletters picking SSFL due to rapid expansion in the Company's 
business.  SSFL's processing volume on behalf of banking institutions
has more than DOUBLED in the last 4 months!

Our track record proves we offer valuable research that builds your
wealth.  We target serious gains for serious investors with a 500%
investment return on SSFL.

DISCLAIMER: Certain statements contained in this newsletter may be 
forward-looking statements within the meaning of The Private Securities 
Litigation Reform Act of 1995. These statements may be identified by 
such terms as "expect", "believe", "may", "will", and "intend" or 
similar terms. We are NOT a registered investment advisor or a broker 
dealer. This is NOT an offer to buy or sell securities. No 
recommendation that the securities of the companies profiled should be 
purchased, sold or held by individuals or entities that learn of the 
profiled companies. This is an independent electronic publication that 
was paid $10,000 by a third party for the electronic dissemination of 
this company information. Be advised that investments in companies 
profiled are considered to be high-risk and use of the information 
provided is for reading purposes only. If anyone decides to act as an 
investor they are advised not to invest without the proper advisement 
from an attorney or a registered financial broker, if any party decides 
to participate as an investor then it will be that investor's sole risk. 
Be advised that the purchase of such high-risk securities may result in 
the loss of some or all of the investment. The publisher of this 
newsletter makes no warranties or guarantees as to the accuracy or the 
completeness of the disclosure. Investors should not rely solely on the 
information presented. Rather, investors should use the information 
provided in this newsletter as a starting point for doing additional 
independent research on the profiled companies in order to allow the 
investor to form their own opinion regarding investing in the profiled 
companies. Factual statements made about the profiled companies are made 
as of the date stated and are subject to change without notice. 
Investing in micro-cap securities is highly speculative and carries an 
extremely high degree of risk. It is possible that an investor's entire 
investment may be lost or impaired due to the speculative nature of the 
companies profiled. All information provided about the profiled 
companies may include information provided by outside sources, such as 
research reports, public filings or computer databases and information 
provided by management of the profiled company.
271396543332222

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



From daemon@optimus.ietf.org  Thu Jan 17 21:49:54 2002
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 VAA19102
	for <avt-archive@odin.ietf.org>; Thu, 17 Jan 2002 21:49:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA06153
	for avt-archive@odin.ietf.org; Thu, 17 Jan 2002 21:49:52 -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 VAA06084;
	Thu, 17 Jan 2002 21:45:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06057
	for <avt@optimus.ietf.org>; Thu, 17 Jan 2002 21:45:41 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19083
	for <avt@ietf.org>; Thu, 17 Jan 2002 21:45:38 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0I2j9p16636;
	Thu, 17 Jan 2002 18:45:10 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Thu, 17 Jan 2002 18:47:18 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020117184453.F91046-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT
Subject: [AVT] Revised WG last call status
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
Content-Transfer-Encoding: 8BIT

At the end of the IETF meeting in SLC, I send a list of action items
from that meeting to be confirmed on the mailing list.  Included in
that list were several drafts to go to WG last call with an ending
date of January 11 (last Friday).  So, that WG last call period has
ended, but for most of these drafts, nary a peep was heard on the
list.

So, Colin and I have discussed this problem and decided on the
following plan:

********************************************************************
* This last call period is extended indefinitely for each draft    *
* until we get at least one valid review from someone not directly *
* involved with production of the draft (i.e., not an author or    *
* contributor).                                                    *
********************************************************************

We envision a couple of ways this might happen:

  - Working group participants who are interested in seeing a
    particular draft be published as an RFC may be motivated to
    provide such a review.

  - We suggest that authors of different drafts might wish to offer to
    to review each other's drafts, maybe pairwise or maybe in a
    "review ring".

  - I'm sure I needn't point out that more than one review would be
    most welcome.

Obviously, someone could dash off a quick message saying "I read draft
xxx and it looks fine to me" without even taking a look.  We're
depending on the integrity of the WG participants to do better than
that.

In making the review, keep in mind the things the IESG is going to be
considering, as described in

    http://www.ietf.org/ID-nits.html

An aspect of the review, as I discussed in my status report at the
start of the SLC meeting (and as reported in the minutes), is making
sure the language is clear and that there are not English nits --
misspellings, tenses mismatched, extraneous or missing plurals,
extraneous or missing articles, etc.  If the reviewer is willing to
mark all of those for the author, that would be great, but at least
please say whether or not the draft needs such corrections.

The drafts currently in WG last call are:

    Comfort Noise payload format (draft-ietf-avt-rtp-cn-04.txt)
        I have reviewed this one and I have a couple of comments I
        will be sending shortly.

    Enhanced CRTP (draft-ietf-avt-crtp-enhance-03.txt)

    Tunneled CRTP (draft-ietf-avt-tcrtp-05.txt)

    Unequal Erasure Protection (draft-ietf-avt-uxp-01.txt)

    Uneven Level Protection (draft-ietf-avt-ulp-03.txt )

    MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)

    MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)

    Distributed Speech Recognition (draft-ietf-avt-dsr-00.txt)

Two more are supposed to start wg last call after being updated as
discussed at the SLC meeting:

    Extended RTP Profile for RTCP-based Feedback
        Actually, there was a message from Roni Even about this one,
        but not a reply.

    Secure RTP profile (draft-ietf-avt-srtp-02.txt)
        There was a question from Andre Flöper about this one, which
        implies at least a partial reading, and a reply.

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


The action item note I send in December also mentioned a draft that
had already gone to the IESG: the RTP payload format and file storage
format for AMR and AMR-WB audio (draft-ietf-avt-rtp-amr-10.txt).  I
mentioned that the IESG response was that the draft was not written
clearly enough.  Qiaobing Xie stepped up quickly with an offer to
rewrite the draft, and I proposed a schedule for the update that was
to have been finished by Christmas.  However, there has been quite a
bit of discussion among the authors, and I did a detailed review
myself which resulted in suggestions for substantial changes.  As a
consequence, it is appropriate that we have the WG review the revised
draft again before it goes back to the IESG.  You should see a new
draft soon.

Naturally, comments on this last call plan are also welcome.

							-- Steve


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



From daemon@optimus.ietf.org  Thu Jan 17 21:52:44 2002
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 VAA19136
	for <avt-archive@odin.ietf.org>; Thu, 17 Jan 2002 21:52:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA06240
	for avt-archive@odin.ietf.org; Thu, 17 Jan 2002 21:52:46 -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 VAA06216;
	Thu, 17 Jan 2002 21:52:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06192
	for <avt@optimus.ietf.org>; Thu, 17 Jan 2002 21:52:22 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19130
	for <avt@ietf.org>; Thu, 17 Jan 2002 21:52:19 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0I2pop16774;
	Thu, 17 Jan 2002 18:51:50 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Thu, 17 Jan 2002 18:53:59 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020117184820.S91046-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [AVT] One note from the minutes
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

The minutes we produce are rather long, but I hope useful to at least
some of you.  Because some of you may have decided not to read through
the minutes, I want to highlight one note:

    The official request for advancement of the RTP spec and A/V
    profile to Draft Standard status was sent to the Area Director on
    Friday of IETF week, December 14.  This is a very significant
    milestone.

I meant to send a note about this to the list on that day, but
apparently I failed to do so.
							-- Steve


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



From daemon@optimus.ietf.org  Thu Jan 17 21:55:42 2002
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 VAA19167
	for <avt-archive@odin.ietf.org>; Thu, 17 Jan 2002 21:55:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA06327
	for avt-archive@odin.ietf.org; Thu, 17 Jan 2002 21:55:41 -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 VAA06312;
	Thu, 17 Jan 2002 21:55:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06281
	for <avt@optimus.ietf.org>; Thu, 17 Jan 2002 21:55:14 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19158
	for <avt@ietf.org>; Thu, 17 Jan 2002 21:55:10 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0I2sgp16843;
	Thu, 17 Jan 2002 18:54:42 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Thu, 17 Jan 2002 18:56:51 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020117185420.P91046-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [AVT] Switch to subscriber-only posting?
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

Should we change the configuration of this mailing list so that posts
are only accepted from subscribers?  That is a pretty effective
technique for reducing spam.  The downside is that it is inconvenient
for people who use multiple mailboxes.
							-- Steve


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



From daemon@optimus.ietf.org  Thu Jan 17 23:53:41 2002
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 XAA22611
	for <avt-archive@odin.ietf.org>; Thu, 17 Jan 2002 23:53:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA13203
	for avt-archive@odin.ietf.org; Thu, 17 Jan 2002 23:53:45 -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 XAA13178;
	Thu, 17 Jan 2002 23:52: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 XAA13154
	for <avt@optimus.ietf.org>; Thu, 17 Jan 2002 23:52:52 -0500 (EST)
Received: from tester.dc90.com ([211.116.140.157])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22606
	for <avt@ietf.org>; Thu, 17 Jan 2002 23:52:46 -0500 (EST)
Message-Id: <200201180452.XAA22606@ietf.org>
Received: (qmail 22978 invoked from network); 18 Jan 2002 02:21:04 -0000
Received: from unknown (HELO pjs) (211.116.140.231)
  by 211.116.140.157 with SMTP; 18 Jan 2002 02:21:04 -0000
From: DC90 <pjs7353@lycos.co.kr>
To: avt@ietf.org
X-Mailer: Microsoft Outlook Express 5.00.2615.200
Reply-To: pjs7353@lycos.co.kr
Date: Fri, 18 Jan 2002 11:20:31 +0900
Mime-Version: 1.0
Content-Type: text/html; charset=ks_c_5601-1987
Subject: [AVT] [±¤°í]BMW 7980¿ø,³ëÆ®ºÏ 2250¿ø, ÇÁ¶ó´Ù ¼ñ´õ¹é 6500¿ø¿¡ Àå¸¸ÇÏ½Ç ¼ö ÀÖ½À´Ï´Ù
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


<!-- saved from url=(0022)http://internet.e-mail -->
<html>

<head>
<title>Á¦¸ñ¾øÀ½</title>
<meta name="generator" content="Namo WebEditor Control 4.0">
</head>

<body bgcolor="white" text="black" link="blue" vlink="purple" alink="red">
<table border="4" cellpadding="0" cellspacing="0" width="593" bordercolor="black">
    <tr>
        <td width="583" bgcolor="black">
            <table border="0" cellpadding="3" cellspacing="0" width="531">
                <tr>
                    <td width="525" height="28" bgcolor="black">
                        <p><b><font color="white">DC90.COM !! ½Å°³³äÀÇ ÀÔÂû½Ä
                        ¼îÇÎ¸ô</font></b></p>
                    </td>
                </tr>
            </table>
        </td>
    </tr>
    <tr>
        <td width="583">
            <table border="0" cellpadding="0" cellspacing="0" width="593">
                <tr>
                    <td width="593">
                        <table border="0" cellpadding="0" cellspacing="0" width="584">
                            <tr>
                                <td width="584" height="60">
                                    <p><a href="http://www.dc90.com"><img src="http://www.dc90.com/img/mail_2.gif" width="594" height="138" border="0"></a></p>
                                </td>
                            </tr>
                        </table>
                    </td>
                </tr>
                <tr>
                    <td width="593">
                                          <table width="595" border="0" cellpadding="0" cellspacing="0">
                    <tr>
                      <td valign="top" width="341">

			<table width="298" border="0" cellpadding="0" cellspacing="0">
                          <tr>
                            <td>
                              <table width="322" border="0" cellpadding="4" cellspacing="0">
				<tr>
                                  <td HEIGHT="3" width="145"></td>
                                                        <td width="161"></td>
                                </tr>
				<tr>
                                  <td colspan="2" width="314">
                                    <div align="left"><img src="http://www.dc90.com/img/index_img1.gif">
                                                            </div>

                                  </td>
                                </tr>
				<tr>
                                                        <td width="145"></td>
                                                        <td width="161"></td>
                                </tr>
                                <tr>
                                  <td class="menu" align="left" valign=middle height="60" width="145"><B><br>BMW 5½Ã¸®Áî 530i</B><br>

                                                            <p> <font size="2">½ÃÁß°¡: 79,800,000¿ø<br>
                                    ÀÔÂû°¡: 7,980¿ø</font><BR><BR>
                                    <A HREF="http://www.dc90.com/tender/tender_view.jsp?tender_prod_num=1007381529016"><font size="2">ÀÔÂû Âü¿©</font></A><A HREF="/tender/tender_view.jsp?tender_prod_num=1007381529016"><font size="2"><img src="http://www.dc90.com/main_img/arrow.gif" width="17" height="17" border="0"></font></A></p>
                                  </td>

                                  <td width="161">
                                    <div align="CENTER"><A HREF="/tender/tender_view.jsp?tender_prod_num=1007381529016"><img src="http://www.dc90.com/product_img/A7/02/01/A70201045001_S_big2.gif" width="170"  border=0></A></div>
                                  </td>

				 </tr>
  			  </table>
                            </td>
                          </tr>
                        </table>
                      </td>
                      <td width="254" valign="top">
                        <table width="265" border="0" cellpadding="0" cellspacing="0">
                          <tr>
                            <td height="181"><a href="http://www.dc90.com/tender/tender_list.jsp?tender_gbn=1"><img src="http://www.dc90.com/main_img/luxury_b.gif" width="264" height="121" border="0"></a></td>
                          </tr>
                        </table>
                      </td>
                    </tr>
                  </table>

                    </td>
                </tr>
                <tr>
                    <td width="593">
                        <p>&nbsp;</p>
                    </td>
                </tr>
            </table>
        </td>
    </tr>
    <tr>
        <td width=" 583" bgcolor="white">
<table border="0" cellpadding="10" cellspacing="0">
    <tr>
        <td width="601" height="149">
            <p><a href="http://www.dc90.com"><b><font size="2" color="#990000">½Å°³³äÀÇ ÀÔÂû½Ä ¼îÇÎ¸ôÀÎ dc90.com</font></b></a><font size="2" color="purple">ÀÌ
            »õ·Ó°Ô ¿ÀÇÂÇß½À´Ï´Ù.</font></p>
            <p><font size="2" color="#990000"><b>dc90.comÀÇ ÀÔÂû½Ä ¼îÇÎ¸ô</b></font><font size="2" color="purple">Àº
            È¥ÀÚ ±¸¸ÅÇÏ±â¿£ ºÎ´ã½º·´°í ±×·¯³ª ²À °®°í ½Í¾ú´ø »óÇ°À» </font><font size="2" color="#990000"><b>¿©·¯¸íÀÌ
            ºñ¿ëÀ» ³ª´©¾î ºÎ´ã</b></font><font size="2" color="purple">ÇÑ ÈÄ,
            </font><font size="2" color="#990000"><b>ÇÑ »ç¶÷ÀÇ ³«ÂûÀÚ¿¡°Ô ¸ô¾ÆÁÖ´Â</b></font><font size="2" color="purple">
            ¹æ½ÄÀÇ ½Å°³³ä ¼îÄª¸ôÀÔ´Ï´Ù.</font></p>
            <p><font size="2" color="#990000"><b>ÀÔÂû¿¡ Âü¿©ÇÑ ÈÄ, ³«ÂûµÇÁö
            ¾Ê¾ÒÀ» °æ¿ì´Â ¾î¶»ÇÏ³Ä°í¿ä?</b></font><font size="2" color="purple">
            <br>°ÆÁ¤¸¶½Ê½Ã¿ä. dc90.comÀº ¿©·¯ºÐÀÌ ÀÔÂû¿¡ »ç¿ëÇÑ ¼ÒÁßÇÑ </font><font size="2" color="#990000"><b>ÀÔÂû±ÝÀ»
            »çÀÌ¹ö¸Ó´Ï·Î</b></font><font size="2" color="purple"> µ¹·Áµå·Á¼­
            dc90.com¿¡¼­ ¿î¿µÇÏ´Â </font><font size="2" color="#990000"><b>ÀÏ¹Ý¼îÇÎ¸ôÀÇ
            »óÇ°À» ÀÚÀ¯·ÎÀÌ ±¸¸Å</b></font><font size="2" color="purple">ÇÒ
            ¼ö ÀÖµµ·Ï ÇÏ¿´½À´Ï´Ù. </font><br></p>
        </td>
    </tr>
</table>
        </td>
    </tr>
    <tr>
        <td width="583">
      <table width="594" border="0" height="350">
        <tr>
          <td width="32" height="37">&nbsp;</td>
          <td width="551" height="37">
            <table width="473" border="0">
              <tr>
                <td height="33"><img src="http://www.dc90.com/event/img/event1.gif" width="80" height="21"></td>
                <td width="400" align="right"><a href="http://www.dc90.com/tender/tender_main.jsp"><img src="http://www.dc90.com/event/img/box_enent_main3.gif" width="104" height="21" border="0"></a></td>
                <td width="40">&nbsp;</td>
              </tr>
            </table>
           </td>
        </tr>
        <tr>
          <td width="32" height="43">&nbsp;</td>
          <td width="551" class="menu" height="43" valign="top"><font color="#C43535">ÀÔÂû¿¡ Âü¿©ÇÏ¸é
            Âü¿©±Ý¾×ÀÇ <b>5%¸¦ ÀÔÂû¿¹Ä¡±ÝÀ¸·Î</b> ¿¹Ä¡ÇØ ÁØ´Ù°í!!!</font><br>
            2002³â 1¿ù 31ÀÏ±îÁö ÀÔÂû¿¡ Âü¿©ÇÏ½Ã´Â ºÐ Áß <b><font color="#C43535">¼±Âø¼ø <br>
            1,000ºÐ</font></b>±îÁö ÀÔÂû¿¡ Âü¿©ÇÑ Âü¿©±Ý¾×ÀÇ 5%¸¦ ÀÔÂû¿¹Ä¡±ÝÀ¸·Î ¿¹Ä¡ÇØ µå¸³´Ï´Ù.<br>
            (´Ü, ÀÔÂûÀÌ Ãë¼ÒµÇ¾î ÀÔÂû¿¹Ä¡±ÝÀ¸·Î È¯ºÒÇÑ °æ¿ì´Â Á¦¿Ü ÇÕ´Ï´Ù.)
           </td>
        </tr>
        <tr>
          <td width="32" height="38">&nbsp;</td>
          <td width="551" height="38">
            <table width="473" border="0">
              <tr>
                <td height="33"><img src="http://www.dc90.com/event/img/event2.gif" width="84" height="22"></td>
                <td width="400" align="right"><a href="http://www.dc90.com/tender/tender_main.jsp"><img src="http://www.dc90.com/event/img/box_enent_main3.gif" width="104" height="21" border="0"></a></td>
                <td width="40">&nbsp;</td>
              </tr>
            </table>
           </td>

        </tr>
        <tr>
          <td width="32" height="132">&nbsp;</td>
          <td width="551" class="menu" height="132" valign="top">
            <p><b><font color="#C43535">ÀÔÂû¿¡ Âü¿©ÇÏ¸é °æÇ°ÀÌ ½ñ¾ÆÁø´Ù!!!</font></b><br>
              2002³â 1¿ù 31ÀÏ±îÁö ÀÔÂû¿¡ <font color="#C43535">ÇÑ¹øÀÌ»ó Âü¿©ÇÏ½Å È¸¿øºÐ Áß ³«Âû¹ÞÁö<br>
              ¸øÇÏ½Å È¸¿ø´Ôµé²²</font>´Â ÃßÃ·À» ÅëÇØ ÇªÁüÇÑ °æÇ°À» µå¸³´Ï´Ù. <br>
              (´Ü, ÇØ´ç »óÇ°ÀÇ ÀÔÂûÀÌ Ãë¼ÒµÈ °æ¿ì´Â Á¦¿Ü ÇÕ´Ï´Ù.)<br>
              <br>
              <b>1µî 1¸í</b> : ³ëÆ®ºÏ[ÈÄÁöÂê][PIII 1GHz] C-7631DV<br>
              <b>2µî 2¸í</b> : »ï¼º Syncmaster LCD 175MP <br>
              <b>3µî 3¸í</b> : OLYMPUS Mu Zoom 140 QD CG<br>
              <b>4µî 4¸í</b> : ÀÔÂû¿¹Ä¡±Ý 20¸¸¿ø <br>
              <b>5µî 5¸í</b> : ÀÔÂû¿¹Ä¡±Ý 10¸¸¿ø </p>
          </td>
        </tr>
        <tr>
          <td width="32" height="33">&nbsp;</td>
          <td width="551" height="33">
            <table width="473" border="0">
              <tr>
                <td height="33"><img src="http://www.dc90.com/event/img/event3.gif" width="84" height="22"></td>
                <td width="400" align="right"><a href="http://www.dc90.com/tender/tender_main.jsp"><img src="http://www.dc90.com/event/img/box_enent_main3.gif" width="104" height="21" border="0"></a></td>
                <td width="40">&nbsp;</td>
              </tr>
            </table>
           </td>
        </tr>
        <tr>
          <td width="32">&nbsp;</td>
          <td width="551" class="menu" valign="top"><b><font color="#C43535">¼ö¼ö·á°¡
            ¸éÁ¦µË´Ï´Ù!!!!</font></b><br>
            2002³â 1¿ù 31ÀÏ±îÁö ÀÔÂû¿¡ Âü¿©ÇÏ½Ã´Â ºÐ²²´Â ¼ö¼ö·á¸¦ °øÁ¦ÇÏÁö ¾ÊÀº <br>
            ÀÔÂûÂü¿©±Ý Àü¾×À» »çÀÌ¹öÄ³½¬·Î Àû¸³ÇÏ¿© µå¸³´Ï´Ù.
          </td>
        </tr>
      </table>

        </td>
    </tr>
    <tr>
        <td width="583" bgcolor="black">
            <table border="0" cellpadding="3" cellspacing="0" width="531">
                <tr>
                    <td width="525" height="28" bgcolor="black" align=center>
                        <font color="white" size="1">Copyright ¨Ï 1998-2001 by DC90. All rights reserved</font>
                    </td>
                </tr>
            </table>
        </td>
    </tr>
</table>
<p>&nbsp;</p>
<p>´ÙÀ½ºÎÅÍ È«º¸¸ÞÀÏÀ» ¹ÞÁö ¾ÊÀ¸½Ã·Á¸é <a href="mailto:recept@tester.dc90.com?subject=¼ö½ÅÀ»°ÅºÎÇÕ´Ï´Ù&body=´ÙÀ½ºÎÅÍ´Â ¸ÞÀÏÀ» º¸³»Áö ¸¶½Ê½Ã¿ä">¿©±â</a>¸¦ ´­·¯ÁÖ¼¼¿ä. </p>
</body>

</html>

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



From daemon@optimus.ietf.org  Fri Jan 18 00:45:27 2002
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 AAA23369
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 00:45:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA15141
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 00:45:28 -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 AAA15082;
	Fri, 18 Jan 2002 00:42:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15051
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 00:42:46 -0500 (EST)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23354
	for <avt@ietf.org>; Fri, 18 Jan 2002 00:42:43 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sj1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id VAA29560 for <avt@ietf.org>; Thu, 17 Jan 2002 21:42:13 -0800 (PST)
Message-Id: <4.1.20020117234109.02f39300@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 17 Jan 2002 23:41:54 -0600
To: AVT WG <avt@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [AVT] Switch to subscriber-only posting?
In-Reply-To: <20020117185420.P91046-100000@ash.packetdesign.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_719672814==_.ALT"
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

--=====================_719672814==_.ALT
Content-Type: text/plain; charset="us-ascii"


I'd like the change

At 06:56 PM 1/17/2002 -0800, Stephen Casner wrote:
>Should we change the configuration of this mailing list so that posts
>are only accepted from subscribers?  That is a pretty effective
>technique for reducing spam.  The downside is that it is inconvenient
>for people who use multiple mailboxes.
>                                                       -- Steve
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt

*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"

James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com
--=====================_719672814==_.ALT
Content-Type: text/html; charset="us-ascii"

<html><div>I'd like the change</div>
<br>
<div>At 06:56 PM 1/17/2002 -0800, Stephen Casner wrote:</div>
<div>&gt;Should we change the configuration of this mailing list so that
posts</div>
<div>&gt;are only accepted from subscribers?&nbsp; That is a pretty
effective</div>
<div>&gt;technique for reducing spam.&nbsp; The downside is that it is
inconvenient</div>
<div>&gt;for people who use multiple mailboxes.</div>
<div>&gt;<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>--
Steve</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;_______________________________________________</div>
<div>&gt;Audio/Video Transport Working Group</div>
<div>&gt;avt@ietf.org</div>
<div>&gt;<a href="https://www1.ietf.org/mailman/listinfo/avt" EUDORA=AUTOURL>https://www1.ietf.org/mailman/listinfo/avt</a></div>
<br>

<div align="center">
*************************************<br>
&quot;People generally demand more respect for their own rights than they
are willing to allow for others&quot;<br>
<br>
</div>
James M. Polk<br>
Consulting Engineer<br>
Office of the CTO<br>
<br>
Cisco Systems<br>
2200 East President George Bush Turnpike <br>
Richardson, TX&nbsp; 75082 USA<br>
w) 972.813.5208<br>
f)&nbsp; 972.813.5280<br>
<a href="http://www.cisco.com/" eudora="autourl">www.cisco.com</a></html>

--=====================_719672814==_.ALT--


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



From daemon@optimus.ietf.org  Fri Jan 18 08:56:02 2002
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 IAA10868
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:55:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12807
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 08:55:59 -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 IAA12764;
	Fri, 18 Jan 2002 08:53:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA12732
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 08:53:43 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10838
	for <avt@ietf.org>; Fri, 18 Jan 2002 08:53:40 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id IAA05770;
	Fri, 18 Jan 2002 08:53:42 -0500 (EST)
Received: from cs.columbia.edu (IDENT:hgs@metroliner.cs.columbia.edu [128.59.19.252])
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g0IDrgJ1028657;
	Fri, 18 Jan 2002 08:53:42 -0500 (EST)
Message-ID: <3C4828E6.10C05EFA@cs.columbia.edu>
Date: Fri, 18 Jan 2002 08:53:42 -0500
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.19-3cucs i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Casner <casner@acm.org>
CC: AVT WG <avt@ietf.org>
Subject: Re: [AVT] Revised WG last call status
References: <20020117184453.F91046-100000@ash.packetdesign.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
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
Content-Transfer-Encoding: 8bit

As an additional measure, I would suggest that each draft is explicitly
assigned at least one, preferably up to three, reviewers. These
reviewers can be suggested by the authors and should be explicitly
charged with the task by the chairs. One possibility is to do the
standard trick commonly employed by conferences and journals: if you
submit a paper, you are asked to review other pending papers. Thus, in
our case, authors of other pending drafts could be assigned such
reviews. The reviews should have deadlines of, say, a month.

Stephen Casner wrote:
> 
> At the end of the IETF meeting in SLC, I send a list of action items
> from that meeting to be confirmed on the mailing list.  Included in
> that list were several drafts to go to WG last call with an ending
> date of January 11 (last Friday).  So, that WG last call period has
> ended, but for most of these drafts, nary a peep was heard on the
> list.
> 
> So, Colin and I have discussed this problem and decided on the
> following plan:
> 
> ********************************************************************
> * This last call period is extended indefinitely for each draft    *
> * until we get at least one valid review from someone not directly *
> * involved with production of the draft (i.e., not an author or    *
> * contributor).                                                    *
> ********************************************************************
> 
> We envision a couple of ways this might happen:
> 
>   - Working group participants who are interested in seeing a
>     particular draft be published as an RFC may be motivated to
>     provide such a review.
> 
>   - We suggest that authors of different drafts might wish to offer to
>     to review each other's drafts, maybe pairwise or maybe in a
>     "review ring".
> 
>   - I'm sure I needn't point out that more than one review would be
>     most welcome.
> 
> Obviously, someone could dash off a quick message saying "I read draft
> xxx and it looks fine to me" without even taking a look.  We're
> depending on the integrity of the WG participants to do better than
> that.
> 
> In making the review, keep in mind the things the IESG is going to be
> considering, as described in
> 
>     http://www.ietf.org/ID-nits.html
> 
> An aspect of the review, as I discussed in my status report at the
> start of the SLC meeting (and as reported in the minutes), is making
> sure the language is clear and that there are not English nits --
> misspellings, tenses mismatched, extraneous or missing plurals,
> extraneous or missing articles, etc.  If the reviewer is willing to
> mark all of those for the author, that would be great, but at least
> please say whether or not the draft needs such corrections.
> 
> The drafts currently in WG last call are:
> 
>     Comfort Noise payload format (draft-ietf-avt-rtp-cn-04.txt)
>         I have reviewed this one and I have a couple of comments I
>         will be sending shortly.
> 
>     Enhanced CRTP (draft-ietf-avt-crtp-enhance-03.txt)
> 
>     Tunneled CRTP (draft-ietf-avt-tcrtp-05.txt)
> 
>     Unequal Erasure Protection (draft-ietf-avt-uxp-01.txt)
> 
>     Uneven Level Protection (draft-ietf-avt-ulp-03.txt )
> 
>     MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)
> 
>     MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)
> 
>     Distributed Speech Recognition (draft-ietf-avt-dsr-00.txt)
> 
> Two more are supposed to start wg last call after being updated as
> discussed at the SLC meeting:
> 
>     Extended RTP Profile for RTCP-based Feedback
>         Actually, there was a message from Roni Even about this one,
>         but not a reply.
> 
>     Secure RTP profile (draft-ietf-avt-srtp-02.txt)
>         There was a question from Andre Flöper about this one, which
>         implies at least a partial reading, and a reply.
> 
>     RTP Payload Format for EVRC, SMV and Frame-Based Vocoders
>     (draft-li-avt-vocoder-00.txt)
> 
> The action item note I send in December also mentioned a draft that
> had already gone to the IESG: the RTP payload format and file storage
> format for AMR and AMR-WB audio (draft-ietf-avt-rtp-amr-10.txt).  I
> mentioned that the IESG response was that the draft was not written
> clearly enough.  Qiaobing Xie stepped up quickly with an offer to
> rewrite the draft, and I proposed a schedule for the update that was
> to have been finished by Christmas.  However, there has been quite a
> bit of discussion among the authors, and I did a detailed review
> myself which resulted in suggestions for substantial changes.  As a
> consequence, it is appropriate that we have the WG review the revised
> draft again before it goes back to the IESG.  You should see a new
> draft soon.
> 
> Naturally, comments on this last call plan are also welcome.
> 
>                                                         -- Steve
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

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



From daemon@optimus.ietf.org  Fri Jan 18 09:02:11 2002
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 JAA11147
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 09:02:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA13397
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 09:02:12 -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 IAA12936;
	Fri, 18 Jan 2002 08:58:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA12905
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 08:58:22 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11007
	for <avt@ietf.org>; Fri, 18 Jan 2002 08:58:20 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id IAA05975;
	Fri, 18 Jan 2002 08:58:22 -0500 (EST)
Received: from cs.columbia.edu (IDENT:hgs@metroliner.cs.columbia.edu [128.59.19.252])
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g0IDwMJ1028707;
	Fri, 18 Jan 2002 08:58:22 -0500 (EST)
Message-ID: <3C4829FE.595866AA@cs.columbia.edu>
Date: Fri, 18 Jan 2002 08:58:22 -0500
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.19-3cucs i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Casner <casner@acm.org>
CC: AVT WG <avt@ietf.org>
Subject: Re: [AVT] Switch to subscriber-only posting?
References: <20020117185420.P91046-100000@ash.packetdesign.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Stephen Casner wrote:
> 
> Should we change the configuration of this mailing list so that posts
> are only accepted from subscribers?  That is a pretty effective
> technique for reducing spam.  The downside is that it is inconvenient
> for people who use multiple mailboxes.

I would welcome such a change. As far as other mailboxes: I believe
mailman, the IETF mailing list software, prompts the owner of the list
to review rejected messages. This allows you or your designated
spammeister to forward any legitimate messages that failed the
membership test. Thus, this would only add a day or two of delay to such
messages. Given that spam messages are becoming increasingly graphic and
are a major pain and expense when traveling, I see no other realistic
option.

Thanks for considering this.

Henning
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

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



From daemon@optimus.ietf.org  Fri Jan 18 09:24:30 2002
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 JAA12229
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 09:24:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA14147
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 09:24:31 -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 JAA14119;
	Fri, 18 Jan 2002 09:22:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14022
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 09:22:30 -0500 (EST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12135
	for <avt@ietf.org>; Fri, 18 Jan 2002 09:22:28 -0500 (EST)
Received: from [165.247.90.87] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 1232103; Fri, 18 Jan 2002 09:22:27 -0500
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [AVT] Revised WG last call status
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>,
        Stephen Casner 
 <casner@acm.org>
Cc: AVT WG <avt@ietf.org>
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Fri, 18 Jan 2002 09:22:27 -0500
Message-ID: <web-1232103@multicasttech.com>
In-Reply-To: <3C4828E6.10C05EFA@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
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
Content-Transfer-Encoding: 8bit

On Fri, 18 Jan 2002 08:53:42 -0500
 "Henning G. Schulzrinne" <hgs@cs.columbia.edu> wrote:
> As an additional measure, I would suggest that each draft
> is explicitly
> assigned at least one, preferably up to three, reviewers.
> These
> reviewers can be suggested by the authors and should be
> explicitly
> charged with the task by the chairs. One possibility is
> to do the
> standard trick commonly employed by conferences and
> journals: if you
> submit a paper, you are asked to review other pending
> papers. Thus, in
> our case, authors of other pending drafts could be
> assigned such
> reviews. The reviews should have deadlines of, say, a
> month.


Hello;

   I am currently reading

Unequal Erasure Protection (draft-ietf-avt-uxp-01.txt)
Uneven Level Protection (draft-ietf-avt-ulp-03.txt )
MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)
MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)

and would be willing to write reviews next week.

Regards
Marshall Eubanks

> 
> Stephen Casner wrote:
> > 
> > At the end of the IETF meeting in SLC, I send a list of
> action items
> > from that meeting to be confirmed on the mailing list.
> Included in
> > that list were several drafts to go to WG last call
> with an ending
> > date of January 11 (last Friday).  So, that WG last
> call period has
> > ended, but for most of these drafts, nary a peep was
> heard on the
> > list.
> > 
> > So, Colin and I have discussed this problem and decided
> on the
> > following plan:
> > 
> > ********************************************************************
> > * This last call period is extended indefinitely for
> each draft    *
> > * until we get at least one valid review from someone
> not directly *
> > * involved with production of the draft (i.e., not an
> author or    *
> > * contributor).
> *
> > ********************************************************************
> > 
> > We envision a couple of ways this might happen:
> > 
> >   - Working group participants who are interested in
> seeing a
> >     particular draft be published as an RFC may be
> motivated to
> >     provide such a review.
> > 
> >   - We suggest that authors of different drafts might
> wish to offer to
> >     to review each other's drafts, maybe pairwise or
> maybe in a
> >     "review ring".
> > 
> >   - I'm sure I needn't point out that more than one
> review would be
> >     most welcome.
> > 
> > Obviously, someone could dash off a quick message
> saying "I read draft
> > xxx and it looks fine to me" without even taking a
> look.  We're
> > depending on the integrity of the WG participants to do
> better than
> > that.
> > 
> > In making the review, keep in mind the things the IESG
> is going to be
> > considering, as described in
> > 
> >     http://www.ietf.org/ID-nits.html
> > 
> > An aspect of the review, as I discussed in my status
> report at the
> > start of the SLC meeting (and as reported in the
> minutes), is making
> > sure the language is clear and that there are not
> English nits --
> > misspellings, tenses mismatched, extraneous or missing
> plurals,
> > extraneous or missing articles, etc.  If the reviewer
> is willing to
> > mark all of those for the author, that would be great,
> but at least
> > please say whether or not the draft needs such
> corrections.
> > 
> > The drafts currently in WG last call are:
> > 
> >     Comfort Noise payload format
> (draft-ietf-avt-rtp-cn-04.txt)
> >         I have reviewed this one and I have a couple of
> comments I
> >         will be sending shortly.
> > 
> >     Enhanced CRTP (draft-ietf-avt-crtp-enhance-03.txt)
> > 
> >     Tunneled CRTP (draft-ietf-avt-tcrtp-05.txt)
> > 
> >     Unequal Erasure Protection
> (draft-ietf-avt-uxp-01.txt)
> > 
> >     Uneven Level Protection (draft-ietf-avt-ulp-03.txt
> )
> > 
> >     MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)
> > 
> >     MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)
> > 
> >     Distributed Speech Recognition
> (draft-ietf-avt-dsr-00.txt)
> > 
> > Two more are supposed to start wg last call after being
> updated as
> > discussed at the SLC meeting:
> > 
> >     Extended RTP Profile for RTCP-based Feedback
> >         Actually, there was a message from Roni Even
> about this one,
> >         but not a reply.
> > 
> >     Secure RTP profile (draft-ietf-avt-srtp-02.txt)
> >         There was a question from Andre Flöper about
> this one, which
> >         implies at least a partial reading, and a
> reply.
> > 
> >     RTP Payload Format for EVRC, SMV and Frame-Based
> Vocoders
> >     (draft-li-avt-vocoder-00.txt)
> > 
> > The action item note I send in December also mentioned
> a draft that
> > had already gone to the IESG: the RTP payload format
> and file storage
> > format for AMR and AMR-WB audio
> (draft-ietf-avt-rtp-amr-10.txt).  I
> > mentioned that the IESG response was that the draft was
> not written
> > clearly enough.  Qiaobing Xie stepped up quickly with
> an offer to
> > rewrite the draft, and I proposed a schedule for the
> update that was
> > to have been finished by Christmas.  However, there has
> been quite a
> > bit of discussion among the authors, and I did a
> detailed review
> > myself which resulted in suggestions for substantial
> changes.  As a
> > consequence, it is appropriate that we have the WG
> review the revised
> > draft again before it goes back to the IESG.  You
> should see a new
> > draft soon.
> > 
> > Naturally, comments on this last call plan are also
> welcome.
> > 
> >
> -- Steve
> > 
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
> 
> -- 
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Fri Jan 18 09:31:22 2002
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 JAA12449
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 09:31:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA14728
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 09:31:24 -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 JAA14597;
	Fri, 18 Jan 2002 09:30:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14566
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 09:30:51 -0500 (EST)
Received: from bootstrap.agcs.com (bootstrap.agcs.com [130.131.48.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12408
	for <avt@ietf.org>; Fri, 18 Jan 2002 09:30:49 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id HAA24541
	for <avt@ietf.org>; Fri, 18 Jan 2002 07:29:22 -0700 (MST)
Received: from mknaomi ([130.131.166.58]) by pxmail1.agcs.com
          (Netscape Messaging Server 3.61)  with SMTP id AAA578
          for <avt@ietf.org>; Fri, 18 Jan 2002 07:30:49 -0700
Received: FROM agcs.com BY mknaomi ; Fri Jan 18 07:30:49 2002 -0700
Message-ID: <3C483198.1DD8585D@agcs.com>
Date: Fri, 18 Jan 2002 07:30:48 -0700
From: Rex Coldren <coldrenr@agcs.com>
Reply-To: coldrenr@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
CC: Stephen Casner <casner@acm.org>, AVT WG <avt@ietf.org>
Subject: Re: [AVT] Revised WG last call status
References: <20020117184453.F91046-100000@ash.packetdesign.com> <3C4828E6.10C05EFA@cs.columbia.edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
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
Content-Transfer-Encoding: 8bit

Another way of looking at this is, if nobody but the author (and his or
her organization) is interested in a draft it should probably not be
proceeding toward standard.  We should probably drop any draft
that doesn't get volunteers to review it.  At least that would save
having to deprecate something later when no interoperable
implementations turn up.

Rex

"Henning G. Schulzrinne" wrote:

> As an additional measure, I would suggest that each draft is explicitly
> assigned at least one, preferably up to three, reviewers. These
> reviewers can be suggested by the authors and should be explicitly
> charged with the task by the chairs. One possibility is to do the
> standard trick commonly employed by conferences and journals: if you
> submit a paper, you are asked to review other pending papers. Thus, in
> our case, authors of other pending drafts could be assigned such
> reviews. The reviews should have deadlines of, say, a month.
>
> Stephen Casner wrote:
> >
> > At the end of the IETF meeting in SLC, I send a list of action items
> > from that meeting to be confirmed on the mailing list.  Included in
> > that list were several drafts to go to WG last call with an ending
> > date of January 11 (last Friday).  So, that WG last call period has
> > ended, but for most of these drafts, nary a peep was heard on the
> > list.
> >
> > So, Colin and I have discussed this problem and decided on the
> > following plan:
> >
> > ********************************************************************
> > * This last call period is extended indefinitely for each draft    *
> > * until we get at least one valid review from someone not directly *
> > * involved with production of the draft (i.e., not an author or    *
> > * contributor).                                                    *
> > ********************************************************************
> >
> > We envision a couple of ways this might happen:
> >
> >   - Working group participants who are interested in seeing a
> >     particular draft be published as an RFC may be motivated to
> >     provide such a review.
> >
> >   - We suggest that authors of different drafts might wish to offer to
> >     to review each other's drafts, maybe pairwise or maybe in a
> >     "review ring".
> >
> >   - I'm sure I needn't point out that more than one review would be
> >     most welcome.
> >
> > Obviously, someone could dash off a quick message saying "I read draft
> > xxx and it looks fine to me" without even taking a look.  We're
> > depending on the integrity of the WG participants to do better than
> > that.
> >
> > In making the review, keep in mind the things the IESG is going to be
> > considering, as described in
> >
> >     http://www.ietf.org/ID-nits.html
> >
> > An aspect of the review, as I discussed in my status report at the
> > start of the SLC meeting (and as reported in the minutes), is making
> > sure the language is clear and that there are not English nits --
> > misspellings, tenses mismatched, extraneous or missing plurals,
> > extraneous or missing articles, etc.  If the reviewer is willing to
> > mark all of those for the author, that would be great, but at least
> > please say whether or not the draft needs such corrections.
> >
> > The drafts currently in WG last call are:
> >
> >     Comfort Noise payload format (draft-ietf-avt-rtp-cn-04.txt)
> >         I have reviewed this one and I have a couple of comments I
> >         will be sending shortly.
> >
> >     Enhanced CRTP (draft-ietf-avt-crtp-enhance-03.txt)
> >
> >     Tunneled CRTP (draft-ietf-avt-tcrtp-05.txt)
> >
> >     Unequal Erasure Protection (draft-ietf-avt-uxp-01.txt)
> >
> >     Uneven Level Protection (draft-ietf-avt-ulp-03.txt )
> >
> >     MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)
> >
> >     MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)
> >
> >     Distributed Speech Recognition (draft-ietf-avt-dsr-00.txt)
> >
> > Two more are supposed to start wg last call after being updated as
> > discussed at the SLC meeting:
> >
> >     Extended RTP Profile for RTCP-based Feedback
> >         Actually, there was a message from Roni Even about this one,
> >         but not a reply.
> >
> >     Secure RTP profile (draft-ietf-avt-srtp-02.txt)
> >         There was a question from Andre Flöper about this one, which
> >         implies at least a partial reading, and a reply.
> >
> >     RTP Payload Format for EVRC, SMV and Frame-Based Vocoders
> >     (draft-li-avt-vocoder-00.txt)
> >
> > The action item note I send in December also mentioned a draft that
> > had already gone to the IESG: the RTP payload format and file storage
> > format for AMR and AMR-WB audio (draft-ietf-avt-rtp-amr-10.txt).  I
> > mentioned that the IESG response was that the draft was not written
> > clearly enough.  Qiaobing Xie stepped up quickly with an offer to
> > rewrite the draft, and I proposed a schedule for the update that was
> > to have been finished by Christmas.  However, there has been quite a
> > bit of discussion among the authors, and I did a detailed review
> > myself which resulted in suggestions for substantial changes.  As a
> > consequence, it is appropriate that we have the WG review the revised
> > draft again before it goes back to the IESG.  You should see a new
> > draft soon.
> >
> > Naturally, comments on this last call plan are also welcome.
> >
> >                                                         -- Steve
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>
> --
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
>
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Fri Jan 18 11:53:50 2002
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 LAA18502
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 11:53:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA22183
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 11:53:53 -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 LAA22037;
	Fri, 18 Jan 2002 11:48:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22006
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 11:48:33 -0500 (EST)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18272
	for <avt@ietf.org>; Fri, 18 Jan 2002 11:48:29 -0500 (EST)
Received: from zrchb200.us.nortel.com (zrchb200.us.nortel.com [47.103.121.45])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IGlTa19860;
	Fri, 18 Jan 2002 10:47:29 -0600 (CST)
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CK6QV4TY>; Fri, 18 Jan 2002 10:47:29 -0600
Message-ID: <1B54FA3A2709D51195C800508BF9386A0311A097@zrc2c000.us.nortel.com>
From: "Peter Barany"<pbarany@nortelnetworks.com>
To: "'Stephen Casner'" <casner@acm.org>, AVT WG <avt@ietf.org>
Subject: RE: [AVT] Switch to subscriber-only posting?
Date: Fri, 18 Jan 2002 10:47:26 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A03F.CF27CB40"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A03F.CF27CB40
Content-Type: text/plain;
	charset="iso-8859-1"

Stephen,

Given the nature and quantity of some of the spam recently, yes. This should
also be the case for other IETF reflectors, if possible. Thanks.

Regards,

Peter Barany
IP Multimedia Standards and Research
Nortel Networks
+1-972-685-2471 (Office)
+1-972-684-3775 (Fax)
+1-972-467-8346 (Mobile)
e-mail: pbarany@nortelnetworks.com

-----Original Message-----
From: Stephen Casner [mailto:casner@acm.org]
Sent: Thursday, January 17, 2002 8:57 PM
To: AVT WG
Subject: [AVT] Switch to subscriber-only posting?


Should we change the configuration of this mailing list so that posts
are only accepted from subscribers?  That is a pretty effective
technique for reducing spam.  The downside is that it is inconvenient
for people who use multiple mailboxes.
							-- Steve


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

------_=_NextPart_001_01C1A03F.CF27CB40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [AVT] Switch to subscriber-only posting?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Stephen,</FONT>
</P>

<P><FONT SIZE=3D2>Given the nature and quantity of some of the spam =
recently, yes. This should also be the case for other IETF reflectors, =
if possible. Thanks.</FONT></P>

<P><FONT SIZE=3D2>Regards,</FONT>
</P>

<P><FONT SIZE=3D2>Peter Barany</FONT>
<BR><FONT SIZE=3D2>IP Multimedia Standards and Research</FONT>
<BR><FONT SIZE=3D2>Nortel Networks</FONT>
<BR><FONT SIZE=3D2>+1-972-685-2471 (Office)</FONT>
<BR><FONT SIZE=3D2>+1-972-684-3775 (Fax)</FONT>
<BR><FONT SIZE=3D2>+1-972-467-8346 (Mobile)</FONT>
<BR><FONT SIZE=3D2>e-mail: pbarany@nortelnetworks.com</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Stephen Casner [<A =
HREF=3D"mailto:casner@acm.org">mailto:casner@acm.org</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 17, 2002 8:57 PM</FONT>
<BR><FONT SIZE=3D2>To: AVT WG</FONT>
<BR><FONT SIZE=3D2>Subject: [AVT] Switch to subscriber-only =
posting?</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Should we change the configuration of this mailing =
list so that posts</FONT>
<BR><FONT SIZE=3D2>are only accepted from subscribers?&nbsp; That is a =
pretty effective</FONT>
<BR><FONT SIZE=3D2>technique for reducing spam.&nbsp; The downside is =
that it is inconvenient</FONT>
<BR><FONT SIZE=3D2>for people who use multiple mailboxes.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>-- =
Steve</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Audio/Video Transport Working Group</FONT>
<BR><FONT SIZE=3D2>avt@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/avt" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/avt</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A03F.CF27CB40--

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



From daemon@optimus.ietf.org  Fri Jan 18 12:10:50 2002
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 MAA19169
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 12:10:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA24612
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 12:10:54 -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 MAA24547;
	Fri, 18 Jan 2002 12:07:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA24517
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 12:07:54 -0500 (EST)
Received: from [209.116.240.194] (foxtrot.nab.org [209.116.240.194])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA19059
	for <avt@ietf.org>; Fri, 18 Jan 2002 12:07:49 -0500 (EST)
Received: from wilma.nab.org by [209.116.240.194]
          via smtpd (for [132.151.1.176]) with SMTP; 18 Jan 2002 17:07:51 UT
Received: (private information removed)
Message-ID: <119889647E5CD31193D4009027991299026DAFD7@wilma.nab.org>
From: "Allison, Art" <AAllison@nab.org>
To: AVT WG <avt@ietf.org>
Subject: RE: [AVT] Switch to subscriber-only posting?
Date: Fri, 18 Jan 2002 12:07:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A042.AA05B160"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A042.AA05B160
Content-Type: text/plain

Firmly support the change.
 

Art 
::{) 
Art Allison 
Director Advanced Engineering 
NAB 
1771 N St NW 
Washington DC 20036 
202 429 5418 

-----Original Message-----
From: James M. Polk [mailto:jmpolk@cisco.com]
Sent: Friday, January 18, 2002 12:42 AM
To: AVT WG
Subject: Re: [AVT] Switch to subscriber-only posting?


I'd like the change

At 06:56 PM 1/17/2002 -0800, Stephen Casner wrote:
>Should we change the configuration of this mailing list so that posts
>are only accepted from subscribers?  That is a pretty effective
>technique for reducing spam.  The downside is that it is inconvenient
>for people who use multiple mailboxes.
>                                                       -- Steve
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
<https://www1.ietf.org/mailman/listinfo/avt> 

*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"


James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com <http://www.cisco.com/>  


------_=_NextPart_001_01C1A042.AA05B160
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">


<META content=3D"MSHTML 5.50.4912.300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D322290717-18012002><FONT face=3DArial =
color=3D#0000ff size=3D2>Firmly=20
support the change.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<P><FONT face=3DArial size=3D2>Art</FONT> <BR><FONT face=3DArial =
size=3D2>::{)</FONT>=20
<BR><FONT face=3DArial size=3D2>Art Allison</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Director Advanced Engineering</FONT> <BR><FONT face=3DArial=20
size=3D2>NAB</FONT> <BR><FONT face=3DArial size=3D2>1771 N St NW</FONT> =
<BR><FONT=20
face=3DArial size=3D2>Washington DC 20036</FONT> <BR><FONT face=3DArial =
size=3D2>202 429=20
5418</FONT> </P>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> James M. Polk=20
  [mailto:jmpolk@cisco.com]<BR><B>Sent:</B> Friday, January 18, 2002 =
12:42=20
  AM<BR><B>To:</B> AVT WG<BR><B>Subject:</B> Re: [AVT] Switch to =
subscriber-only=20
  posting?<BR><BR></FONT></DIV>
  <DIV>I'd like the change</DIV><BR>
  <DIV>At 06:56 PM 1/17/2002 -0800, Stephen Casner wrote:</DIV>
  <DIV>&gt;Should we change the configuration of this mailing list so =
that=20
  posts</DIV>
  <DIV>&gt;are only accepted from subscribers?&nbsp; That is a pretty=20
  effective</DIV>
  <DIV>&gt;technique for reducing spam.&nbsp; The downside is that it =
is=20
  inconvenient</DIV>
  <DIV>&gt;for people who use multiple mailboxes.</DIV>
  =
<DIV>&gt;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</X-TAB><X-TAB=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</X-TAB><X-TAB>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</X-TAB><X-TAB>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</X-TAB><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;</X-TAB><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;</X-TAB><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;</X-TAB>--=20
  Steve</DIV>
  <DIV>&gt;</DIV>
  <DIV>&gt;</DIV>
  <DIV>&gt;_______________________________________________</DIV>
  <DIV>&gt;Audio/Video Transport Working Group</DIV>
  <DIV>&gt;avt@ietf.org</DIV>
  <DIV>&gt;<A href=3D"https://www1.ietf.org/mailman/listinfo/avt"=20
  =
EUDORA=3D"AUTOURL">https://www1.ietf.org/mailman/listinfo/avt</A></DIV><=
BR>
  <DIV align=3Dcenter>*************************************<BR>"People =
generally=20
  demand more respect for their own rights than they are willing to =
allow for=20
  others"<BR><BR></DIV>James M. Polk<BR>Consulting Engineer<BR>Office =
of the=20
  CTO<BR><BR>Cisco Systems<BR>2200 East President George Bush Turnpike=20
  <BR>Richardson, TX&nbsp; 75082 USA<BR>w) 972.813.5208<BR>f)&nbsp;=20
  972.813.5280<BR><A href=3D"http://www.cisco.com/"=20
  eudora=3D"autourl">www.cisco.com</A> </BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1A042.AA05B160--

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



From daemon@optimus.ietf.org  Fri Jan 18 13:14:37 2002
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 NAA21695
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 13:14:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA27325
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 13:14:39 -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 NAA27310;
	Fri, 18 Jan 2002 13:13:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27279
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 13:13:24 -0500 (EST)
Received: from rly-ip01.mx.aol.com (rly-ip01.mx.aol.com [205.188.156.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21609
	for <AVT@IETF.org>; Fri, 18 Jan 2002 13:13:21 -0500 (EST)
Received: from logs-mtc-tk.proxy.aol.com (logs-mtc-tk.proxy.aol.com [64.12.107.5])
	  by rly-ip01.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0)
	  with ESMTP id NAA15385 for <AVT@IETF.org>;
	  Fri, 18 Jan 2002 13:12:42 -0500 (EST)
Received: from VAIO.PacBell.net (ACAF80D9.ipt.aol.com [172.175.128.217])
	by logs-mtc-tk.proxy.aol.com (8.10.0/8.10.0) with ESMTP id g0IHvVb458335
	for <AVT@IETF.org>; Fri, 18 Jan 2002 12:57:33 -0500 (EST)
Message-Id: <5.1.0.14.2.20020118075153.04470a90@PostOffice.PacBell.net>
X-Sender: Celeborn@PostOffice.PacBell.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 18 Jan 2002 07:52:58 -1000
To: AVT <AVT@ietf.org>
From: Peter Johansson <PJohansson@ACM.org>
Subject: Re: [AVT] Switch to subscriber-only posting?
In-Reply-To: <20020117185420.P91046-100000@ash.packetdesign.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Apparently-From: PJohansson@aol.com
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

At 06:56 PM 1/17/02, Stephen Casner wrote:

>Should we change the configuration of this mailing list so that posts are 
>only accepted from subscribers?  That is a pretty effective
>technique for reducing spam.  The downside is that it is inconvenient for 
>people who use multiple mailboxes.

YES!


Regards,

Peter Johansson

Congruent Software, Inc.
98 Colorado Avenue
Berkeley, CA  94707

(510) 527-3926
(510) 527-3856 FAX

PJohansson@ACM.org


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



From daemon@optimus.ietf.org  Fri Jan 18 13:56:59 2002
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 NAA23314
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 13:56:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA29019
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 13:57:01 -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 NAA28937;
	Fri, 18 Jan 2002 13:55:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28897
	for <avt@optimus.ietf.org>; Fri, 18 Jan 2002 13:55:09 -0500 (EST)
Received: from snap.CS.Berkeley.EDU (IDENT:root@snap.CS.Berkeley.EDU [128.32.45.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23248
	for <avt@ietf.org>; Fri, 18 Jan 2002 13:55:03 -0500 (EST)
Received: (from lazzaro@localhost)
	by snap.CS.Berkeley.EDU (8.9.3/8.9.3-ZUUL) id KAA06073
	for avt@ietf.org; Fri, 18 Jan 2002 10:49:25 -0800
Date: Fri, 18 Jan 2002 10:49:25 -0800
From: John Lazzaro <lazzaro@CS.Berkeley.EDU>
Message-Id: <200201181849.KAA06073@snap.CS.Berkeley.EDU>
To: avt@ietf.org
Subject: [AVT] Re: Switch to subscriber-only posting?
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


> From: Stephen Casner <casner@acm.org>
> Should we change the configuration of this mailing list so that posts
> are only accepted from subscribers?  

Given that many of the WG mailing lists are under the ietf.org 
umbrella now, it might be worth considering extending posting
rights to subscribed members of related IETF groups -- it   
seems like the most common reason for a non-AVT-subscriber to
post is to forward a discussion from a related WG list, and if
its technically possible to retain this feature it would be good.

Aside from that caveat, though, blocking non-subscribers sounds
like a great idea ...

-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------

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



From daemon@ns.ietf.org  Fri Jan 18 15:05:51 2002
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 PAA25319
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:05:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA02314
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 15:05:54 -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 PAA02297;
	Fri, 18 Jan 2002 15:05:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02266
	for <avt@ns.ietf.org>; Fri, 18 Jan 2002 15:05:01 -0500 (EST)
Received: from bullwinkle.real.com (bullwinkle.real.com [207.188.22.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25299
	for <avt@ietf.org>; Fri, 18 Jan 2002 15:04:55 -0500 (EST)
Received: from prognet.com ([::ffff:205.219.198.1])
  by bullwinkle.real.com with esmtp; Fri, 18 Jan 2002 12:04:17 -0800
Received: from ROBLA350 ([172.23.100.116])
	by prognet.com (8.9.2/8.9.0) with ESMTP id MAA25650
	for <avt@ietf.org>; Fri, 18 Jan 2002 12:04:26 -0800 (PST)
Date: Fri, 18 Jan 2002 12:05:25 -0800 (Pacific Standard Time)
From: Rob Lanphier <robla@real.com>
To: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] Re: Switch to subscriber-only posting?
In-Reply-To: <200201181849.KAA06073@snap.CS.Berkeley.EDU>
Message-ID: <Pine.WNT.4.43.0201181158450.217-100000@robla350.dev.prognet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

I don't have any strong feelings one way or the other on this.  However,
this did come up on the IETF list before, when someone tried to send a
message to MIDCOM and it bounced:

http://www.ietf.org/mail-archive/ietf/Current/msg10772.html

The MIDCOM mailing list administrator ended up opening the list back up.

Rob

On Fri, 18 Jan 2002, John Lazzaro wrote:

>
> > From: Stephen Casner <casner@acm.org>
> > Should we change the configuration of this mailing list so that posts
> > are only accepted from subscribers?
>
> Given that many of the WG mailing lists are under the ietf.org
> umbrella now, it might be worth considering extending posting
> rights to subscribed members of related IETF groups -- it
> seems like the most common reason for a non-AVT-subscriber to
> post is to forward a discussion from a related WG list, and if
> its technically possible to retain this feature it would be good.
>
> Aside from that caveat, though, blocking non-subscribers sounds
> like a great idea ...
>
> -------------------------------------------------------------------------
> John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
> lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
> -------------------------------------------------------------------------
>
> _______________________________________________
> 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



From daemon@ns.ietf.org  Fri Jan 18 15:12:07 2002
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 PAA25467
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:12:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA02516
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 15:12:10 -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 PAA02482;
	Fri, 18 Jan 2002 15:11:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02454
	for <avt@ns.ietf.org>; Fri, 18 Jan 2002 15:11:28 -0500 (EST)
Received: from [209.116.240.194] (foxtrot.nab.org [209.116.240.194])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA25448
	for <avt@ietf.org>; Fri, 18 Jan 2002 15:11:24 -0500 (EST)
Received: from wilma.nab.org by [209.116.240.194]
          via smtpd (for [132.151.1.176]) with SMTP; 18 Jan 2002 20:11:26 UT
Received: (private information removed)
Message-ID: <119889647E5CD31193D4009027991299026DAFDE@wilma.nab.org>
From: "Allison, Art" <AAllison@nab.org>
To: avt@ietf.org
Subject: RE: [AVT] Re: Switch to subscriber-only posting?
Date: Fri, 18 Jan 2002 15:11:24 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
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

Perhaps the source of much of the spam can be traced back to the open web
page that offers the ability to blindly send to the list.  If that address
were blocked, perhaps much spam would be avoided, and anyone that got the
actual list address could still post.  
I don't have the ability to do this analysis to see if that is the source.
As I have no problem with a hard block, perhaps someone wishing to take a
less severe step might undertake that work.
Art
::{)
Art Allison
Director Advanced Engineering
NAB
1771 N St NW
Washington DC 20036
202 429 5418


-----Original Message-----
From: Rob Lanphier [mailto:robla@real.com]
Sent: Friday, January 18, 2002 3:05 PM
To: avt@ietf.org
Subject: Re: [AVT] Re: Switch to subscriber-only posting?


I don't have any strong feelings one way or the other on this.  However,
this did come up on the IETF list before, when someone tried to send a
message to MIDCOM and it bounced:

http://www.ietf.org/mail-archive/ietf/Current/msg10772.html

The MIDCOM mailing list administrator ended up opening the list back up.

Rob

On Fri, 18 Jan 2002, John Lazzaro wrote:

>
> > From: Stephen Casner <casner@acm.org>
> > Should we change the configuration of this mailing list so that posts
> > are only accepted from subscribers?
>
> Given that many of the WG mailing lists are under the ietf.org
> umbrella now, it might be worth considering extending posting
> rights to subscribed members of related IETF groups -- it
> seems like the most common reason for a non-AVT-subscriber to
> post is to forward a discussion from a related WG list, and if
> its technically possible to retain this feature it would be good.
>
> Aside from that caveat, though, blocking non-subscribers sounds
> like a great idea ...
>
> -------------------------------------------------------------------------
> John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
> lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
> -------------------------------------------------------------------------
>
> _______________________________________________
> 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

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



From daemon@ns.ietf.org  Fri Jan 18 15:17:15 2002
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 PAA25638
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:17:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA02705
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 15:17:18 -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 PAA02677;
	Fri, 18 Jan 2002 15:16:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02647
	for <avt@ns.ietf.org>; Fri, 18 Jan 2002 15:16:44 -0500 (EST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25627
	for <avt@ietf.org>; Fri, 18 Jan 2002 15:16:40 -0500 (EST)
Received: from [63.105.122.236] ([63.105.122.236] verified)
  by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP id 1232473; Fri, 18 Jan 2002 15:16:39 -0500
User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630)
Date: Fri, 18 Jan 2002 15:16:42 -0500
Subject: Re: [AVT] Switch to subscriber-only posting?
From: Marshall Eubanks <tme@multicasttech.com>
To: "Allison, Art" <AAllison@nab.org>, AVT WG <avt@ietf.org>
Message-ID: <B86DECDA.417D%tme@multicasttech.com>
In-Reply-To: <119889647E5CD31193D4009027991299026DAFD7@wilma.nab.org>
Mime-version: 1.0
Content-type: multipart/alternative;
   boundary="MS_Mac_OE_3094211802_4703301_MIME_Part"
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

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--MS_Mac_OE_3094211802_4703301_MIME_Part
Content-type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Firmly support the change.
 

FWIW I do too.

Marshall Eubanks

Art 
::{) 
Art Allison 
Director Advanced Engineering
NAB 
1771 N St NW 
Washington DC 20036
202 429 5418 
-----Original Message-----
From: James M. Polk [mailto:jmpolk@cisco.com]
Sent: Friday, January 18, 2002 12:42 AM
To: AVT WG
Subject: Re: [AVT] Switch to subscriber-only posting?

I'd like the change

At 06:56 PM 1/17/2002 -0800, Stephen Casner wrote:
>Should we change the configuration of this mailing list so that posts
>are only accepted from subscribers?  That is a pretty effective
>technique for reducing spam.  The downside is that it is inconvenient
>for people who use multiple mailboxes.
>                                                       -- Steve
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt


*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"


James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com <http://www.cisco.com/>



-- 
                                Regards
                                Marshall Eubanks



T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624            Fax     : 703-293-9609
e-mail : tme@multicasttech.com

Test your network for multicast : http://www.multicasttech.com/mt/
Check the status of multicast in real time :
http://www.multicasttech.com/status/index.html


--MS_Mac_OE_3094211802_4703301_MIME_Part
Content-type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [AVT] Switch to subscriber-only posting?</TITLE>
</HEAD>
<BODY>
<BLOCKQUOTE><FONT COLOR=3D"#0000FF"><FONT SIZE=3D"2"><FONT FACE=3D"Arial">Firmly =
support the change.<BR>
</FONT></FONT></FONT> <BR>
<BR>
FWIW I do too.<BR>
<BR>
Marshall Eubanks<BR>
<BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">Art</FONT></FONT> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">::{)</FONT></FONT> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">Art Allison</FONT></FONT> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">Director Advanced Engineering</FONT></FON=
T> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">NAB</FONT></FONT> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">1771 N St NW</FONT></FONT> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">Washington DC 20036</FONT></FONT> <BR>
<FONT SIZE=3D"2"><FONT FACE=3D"Arial">202 429 5418</FONT></FONT> <BR>
<BLOCKQUOTE><FONT SIZE=3D"2">-----Original Message-----<BR>
<B>From:</B> James M. Polk [mailto:jmpolk@cisco.com]<BR>
<B>Sent:</B> Friday, January 18, 2002 12:42 AM<BR>
<B>To:</B> AVT WG<BR>
<B>Subject:</B> Re: [AVT] Switch to subscriber-only posting?<BR>
<BR>
</FONT>I'd like the change<BR>
<BR>
At 06:56 PM 1/17/2002 -0800, Stephen Casner wrote:<BR>
&gt;Should we change the configuration of this mailing list so that posts<B=
R>
&gt;are only accepted from subscribers? &nbsp;That is a pretty effective<BR=
>
&gt;technique for reducing spam. &nbsp;The downside is that it is inconveni=
ent<BR>
&gt;for people who use multiple mailboxes.<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;-- Steve<BR>
&gt;<BR>
&gt;<BR>
&gt;_______________________________________________<BR>
&gt;Audio/Video Transport Working Group<BR>
&gt;avt@ietf.org<BR>
&gt;https://www1.ietf.org/mailman/listinfo/avt<BR>
<BR>
<P ALIGN=3DCENTER>
*************************************<BR>
&quot;People generally demand more respect for their own rights than they a=
re willing to allow for others&quot;<BR>
<BR>
<P>
James M. Polk<BR>
Consulting Engineer<BR>
Office of the CTO<BR>
<BR>
Cisco Systems<BR>
2200 East President George Bush Turnpike <BR>
Richardson, TX &nbsp;75082 USA<BR>
w) 972.813.5208<BR>
f) &nbsp;972.813.5280<BR>
www.cisco.com &lt;http://www.cisco.com/&gt; &nbsp;<BR>
</BLOCKQUOTE><BR>
</BLOCKQUOTE><BR>
<BR>
-- <BR>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Regards<BR>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Marshall Eubanks<BR>
<BR>
<BR>
<BR>
T.M. Eubanks<BR>
Multicast Technologies, Inc<BR>
10301 Democracy Lane, Suite 410<BR>
Fairfax, Virginia 22030<BR>
Phone : 703-293-9624 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;Fax &nbsp;&nbsp;&nbsp;&nbsp;: 703-293-9609<BR>
e-mail : tme@multicasttech.com<BR>
<BR>
 Test your network for multicast : http://www.multicasttech.com/mt/<BR>
 Check the status of multicast in real time : &nbsp;&nbsp;&nbsp;&nbsp;<BR>
 http://www.multicasttech.com/status/index.html<BR>
</BODY>
</HTML>


--MS_Mac_OE_3094211802_4703301_MIME_Part--


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



From daemon@ns.ietf.org  Fri Jan 18 15:52:27 2002
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 PAA26490
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:52:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04102
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 15:52:28 -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 PAA04029;
	Fri, 18 Jan 2002 15:50:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04002
	for <avt@ns.ietf.org>; Fri, 18 Jan 2002 15:50:38 -0500 (EST)
Received: from 1971.232.com ([63.238.139.7])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA26425
	for <avt@ietf.org>; Fri, 18 Jan 2002 15:50:35 -0500 (EST)
Message-Id: <200201182050.PAA26425@ietf.org>
Received: (qmail 13066 invoked by uid 0); 18 Jan 2002 18:18:31 -0000
To: avt@ietf.org
Date: Thu, 17 Jan 2002 19:38:52 +0300
From: bestselection12@yahoo.com
MIME-Version: 1.0
Content-Type: text/html;
  charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] Get ready to see BIGGEST teen site on the web!
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
Content-Transfer-Encoding: 7bit


Hello avt@ietf.org!<br><br>
<font face="arial" size="2">
<font size="3"><b>
Get ready to see BIGGEST teen site on the web!!!<br><br><br>
</b></font>

REAL YOUNG TEENS!!!!<br>
Are these girls REALLY 18?!?<br>
<a href="http://picks-up.com/ss/teenhard2/?aid=206558">Click to check this!</a><br><br>

HOT FREE TEEN MOVIE CLIPS AND VIDEO FEEDS!!<br>
<a href="http://picks-up.com/ss/teenhard2/?aid=206558">Click here for watch!</a><br><br>


See little teen girls give head for THE FIRST TIME!!!<br>
They get lessons on how to BLOW!!<br>
<a href="http://picks-up.com/ss/teenhard2/?aid=206558">Click here for watch!</a><br><br>

Watch dirty old men teach young teens to be NASTY!!<br>
<a href="http://picks-up.com/ss/teenhard2/?aid=206558">Click here for watch!</a><br><br>




BUT IT NOT ALL!!!<br>
Updating some times per week.<br>
Excellent quality of pic's and video.<br>
Convenient system of navigation with bookmark and favorites.<br>
And much more...<br>

<a href="http://picks-up.com/ss/teenhard2/?aid=206558">(!!!)Only this month preferential the prices! Hasten(!!!)</a><br><br><br>

Remove from list - <a href="http://picks-up.com/remove.php">click here</a>.<br>

</font>

1976.964


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



From daemon@ns.ietf.org  Fri Jan 18 22:16:20 2002
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 WAA04357
	for <avt-archive@odin.ietf.org>; Fri, 18 Jan 2002 22:16:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA14551
	for avt-archive@odin.ietf.org; Fri, 18 Jan 2002 22:16:24 -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 WAA14521;
	Fri, 18 Jan 2002 22:13:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14490
	for <avt@ns.ietf.org>; Fri, 18 Jan 2002 22:13:45 -0500 (EST)
Received: from purple.nge.isi.edu (they101.east.isi.edu [65.114.168.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04335
	for <avt@ietf.org>; Fri, 18 Jan 2002 22:13:41 -0500 (EST)
Received: from purple.nge.isi.edu (csp@localhost)
	by purple.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g0J3Dig12298;
	Fri, 18 Jan 2002 22:13:44 -0500
Message-Id: <200201190313.g0J3Dig12298@purple.nge.isi.edu>
To: "Allison, Art" <AAllison@nab.org>
cc: avt@ietf.org
Subject: Re: [AVT] Re: Switch to subscriber-only posting? 
In-Reply-To: Your message of "Fri, 18 Jan 2002 15:11:24 EST."
             <119889647E5CD31193D4009027991299026DAFDE@wilma.nab.org> 
Date: Fri, 18 Jan 2002 22:13:43 -0500
From: Colin Perkins <csp@isi.edu>
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

Which open web page?
C.

--> "Allison, Art" writes:
>Perhaps the source of much of the spam can be traced back to the open web
>page that offers the ability to blindly send to the list.  If that address
>were blocked, perhaps much spam would be avoided, and anyone that got the
>actual list address could still post.  
>I don't have the ability to do this analysis to see if that is the source.
>As I have no problem with a hard block, perhaps someone wishing to take a
>less severe step might undertake that work.
>Art
>::{)
>Art Allison
>Director Advanced Engineering
>NAB
>1771 N St NW
>Washington DC 20036
>202 429 5418
>
>
>-----Original Message-----
>From: Rob Lanphier [mailto:robla@real.com]
>Sent: Friday, January 18, 2002 3:05 PM
>To: avt@ietf.org
>Subject: Re: [AVT] Re: Switch to subscriber-only posting?
>
>
>I don't have any strong feelings one way or the other on this.  However,
>this did come up on the IETF list before, when someone tried to send a
>message to MIDCOM and it bounced:
>
>http://www.ietf.org/mail-archive/ietf/Current/msg10772.html
>
>The MIDCOM mailing list administrator ended up opening the list back up.
>
>Rob
>
>On Fri, 18 Jan 2002, John Lazzaro wrote:
>
>>
>> > From: Stephen Casner <casner@acm.org>
>> > Should we change the configuration of this mailing list so that posts
>> > are only accepted from subscribers?
>>
>> Given that many of the WG mailing lists are under the ietf.org
>> umbrella now, it might be worth considering extending posting
>> rights to subscribed members of related IETF groups -- it
>> seems like the most common reason for a non-AVT-subscriber to
>> post is to forward a discussion from a related WG list, and if
>> its technically possible to retain this feature it would be good.
>>
>> Aside from that caveat, though, blocking non-subscribers sounds
>> like a great idea ...
>>
>> -------------------------------------------------------------------------
>> John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
>> lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
>> -------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>
>_______________________________________________
>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



From daemon@optimus.ietf.org  Sat Jan 19 03:32:16 2002
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 DAA17069
	for <avt-archive@odin.ietf.org>; Sat, 19 Jan 2002 03:32:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA01126
	for avt-archive@odin.ietf.org; Sat, 19 Jan 2002 03:32:19 -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 DAA00699;
	Sat, 19 Jan 2002 03:30:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00593
	for <avt@optimus.ietf.org>; Sat, 19 Jan 2002 03:29:57 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17033
	for <avt@ietf.org>; Sat, 19 Jan 2002 03:29:53 -0500 (EST)
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0J8TOp54968;
	Sat, 19 Jan 2002 00:29:24 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Sat, 19 Jan 2002 00:42:55 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020119004000.G15485-200000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1915571904-1011429775=:15485"
Subject: [AVT] Review of CN payload format
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1915571904-1011429775=:15485
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have reviewed draft-ietf-avt-rtp-cn-04.txt, "RTP Payload for Comfort
Noise".  Actually, I've reviewed it before and we have discussed it
several times in AVT over an embarrassingly long period of time.  This
draft is nice and simple, and clearly written.  As I've said before,
the main question is whether there will there be any backwards
compatibility problems with early implementations of CN that included
only the amplitude and not spectral information.  However, I think
we've given plenty of opportunity for comment on that, and the IESG
last call will provide a broader opportunity for review on that point.

I have only a WG last call comments I'd like to see before this goes
to IESG last call, some of which are based on changes in procedures
over the time this draft.  I list the changes here, then for the
convenience of the author I attach a diff file with some specific
suggested text changes.

  - First, I take as WG last call comments the messages from Sharma
    Kanchinadham and others on this list asking for some explicit
    mention of the mechanism to negotiate use of CN.  Now, negotiation
    gets too much into the separate domain of SIP or other control
    protocols, but it is common practice to show SDP usage for a
    payload format, and I think that would be helpful here, too.  I
    wrote a section giving static and dynamic payload examples, and
    saying that omission of a payload type for CN on the media
    description line implies that comfort noise will not be used, but
    it does not imply that silence will not be suppressed.  I also
    added some words in the Guidelines for Use section to clarify that
    the payload type is switched between active and inactive voice
    periods.  Check the attachment to see the wording.

  - As I recently learned in handling the "authors' 48 hours" edits
    for RFC 3189 and 3190, the Abstract section is never numbered.
    So, please change Abstract to be unnumbered and renumber the other
    sections.

  - Since this draft is going to go to the IESG and we presume to RFC
    publication thereafter, the "Resolution of Open Issues" paragraph
    should be deleted from the Abstract section.

  - In the description of the RTP timestamp, I think it is better to
    say that the timestamp marks the beginning of the comfort noise
    period, rather than the beginning of the silence period, because
    comfort noise may be repeated.

  - This revision of the draft put back the appropriate specification
    of static payload type 13.  Since that payload type is assigned
    under the RTP A/V profile (RFC 1890 and the draft revision), that
    profile needs to be referenced.  Also, as I clarified in the
    text of the draft profile revision recently, the 8000 Hz is
    properly the RTP timestamp clock rate, not the sampling rate
    (the two are usually but not always equal).

  - The word "minimising" is the only British spelling in an otherwise
    American English document, so it should be consistent.  :)

  - The IESG and RFC Editor like to see an "IANA Considerations"
    section.  For this draft, I suggest just renaming Section 7.  Then
    it would also be good to add some words there about the assignment
    of payload type 13 in IANA's "RTP Parameters" registry.

  - In the MIME registration, the meaning of the optional parameter
    "rate" should be given.  Also, in Encoding Considerations, let's
    just refer to RFC 1889 rather than the draft revision so as not to
    create a publication dependency.

  - The changes suggested above require three additional RFC
    references.
							-- Steve

--0-1915571904-1011429775=:15485
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="cn.diff"
Content-ID: <20020119004255.L15485@oak.packetdesign.com>
Content-Description: 
Content-Disposition: attachment; filename="cn.diff"
Content-Transfer-Encoding: BASE64

LS0tIGRyYWZ0LWlldGYtYXZ0LXJ0cC1jbi0wNC50eHQJU2F0IERlYyAgOCAx
MzozNTo1MCAyMDAxDQorKysgZHJhZnQtaWV0Zi1hdnQtcnRwLWNuLTA0YS50
eHQJU2F0IEphbiAxOSAwMDoxNToyNiAyMDAyDQpAQCAtMzgsMTUgKzM4LDYg
QEANCiAgICBpdHNlbGYgc3VjaCBhcyBJVFUtVCBSZWNvbW1lbmRhdGlvbnMg
Ry43MTEgWzNdLCBHLjcyNiBbNF0sIEcuNzI3DQogICAgWzVdLCBHLjcyOCBb
Nl0sIGFuZCBHLjcyMiBbN10uDQogDQotICAgUmVzb2x1dGlvbiBvZiBPcGVu
IElzc3Vlcw0KLQ0KLSAgIFRoaXMgcmV2aXNpb24gcmV2ZXJ0cyB0aGUgZGVm
aW5pdGlvbiBvZiB0aGUgc2FtcGxpbmcgcmF0ZSBiYWNrIHRvDQotICAgdGhh
dCBpbiByZXZpc2lvbiAtMDEgb2YgdGhpcyBkb2N1bWVudC4gIEJ5IG1ha2lu
ZyB0aGUgc2FtcGxpbmcgcmF0ZQ0KLSAgIGVxdWFsIHRvIHRoYXQgb2YgdGhl
IGF1ZGlvIGNvZGVjLCBpdCB3YXMgZXNzZW50aWFsbHkgcmVkZWZpbmluZyB0
aGUNCi0gICBtZWFuaW5nIG9mIGEgc3RhdGljIHBheWxvYWQgdG8gc2F5IHRo
YXQgaXQgY291bGQgaGF2ZSBhIHZhcmlhYmxlIFJUUA0KLSAgIGNsb2NrIHJh
dGUuICBUaGUgc2FtcGxpbmcgcmF0ZSBpcyBub3cgZGVmaW5lZCB0byBiZSA4
MDAwIEh6LCBhbmQgYW55DQotICAgb3RoZXIgcmF0ZSByZXF1aXJlcyB0aGUg
dXNlIG9mIGEgZHluYW1pYyBwYXlsb2FkIHR5cGUuICBTZWUgU2VjdGlvbg0K
LSAgIDUgZm9yIGRldGFpbHMuICBObyBvdGhlciBpc3N1ZXMgYXJlIGtub3du
IG9yIGV4cGVjdGVkLg0KIA0KIDIuIENvbnZlbnRpb25zIHVzZWQgaW4gdGhp
cyBkb2N1bWVudA0KIA0KQEAgLTE2OSw5ICsxNjAsMTEgQEANCiANCiAgICBU
aGUgUlRQIGhlYWRlciBmb3IgdGhlIGNvbWZvcnQgbm9pc2UgcGFja2V0IFNI
T1VMRCBiZSBjb25zdHJ1Y3RlZCBhcw0KICAgIGlmIHRoZSBjb21mb3J0IG5v
aXNlIHdlcmUgYW4gaW5kZXBlbmRlbnQgY29kZWMuIFRodXMsIHRoZSBSVFAN
Ci0gICB0aW1lc3RhbXAgZGVzaWduYXRlcyB0aGUgYmVnaW5uaW5nIG9mIHRo
ZSBzaWxlbmNlIHBlcmlvZC4gQSBzdGF0aWMNCi0gICBwYXlsb2FkIHR5cGUg
b2YgMTMgaXMgYXNzaWduZWQgZm9yIGEgc2FtcGxpbmcgcmF0ZSBvZiA4LDAw
MCBIejsgaWYNCi0gICBvdGhlciBzYW1wbGluZyByYXRlcyBhcmUgbmVlZGVk
LCB0aGV5IE1VU1QgYmUgZGVmaW5lZCB0aHJvdWdoDQorICAgdGltZXN0YW1w
IGRlc2lnbmF0ZXMgdGhlIGJlZ2lubmluZyBvZiB0aGUgY29tZm9ydCBub2lz
ZSBwZXJpb2QuIFdoZW4gdGhpcw0KKyAgIHBheWxvYWQgZm9ybWF0IGlzIHVz
ZWQgdW5kZXIgdGhlIFJUUCBwcm9maWxlIHNwZWNpZmllZCBpbiBSRkMgMTg5
MA0KKyAgIFsxMV0sIGEgc3RhdGljIHBheWxvYWQgdHlwZSBvZiAxMyBpcyBh
c3NpZ25lZCBmb3IgUlRQIHRpbWVzdGFtcA0KKyAgIGNsb2NrIHJhdGUgb2Yg
OCwwMDAgSHo7IGlmIG90aGVyIHJhdGVzIGFyZSBuZWVkZWQsIHRoZXkgTVVT
VCBiZQ0KKyAgIGRlZmluZWQgdGhyb3VnaA0KIA0KIFpvcGYgICAgICAgICAg
ICAgICAgU3RhbmRhcmRzIFRyYWNrIC0gQXByaWwsIDIwMDIgICAgICAgICAg
ICAgICAgICAgMw0KIAwNCkBAIC0xOTIsMTEgKzE4NSwxNyBAQA0KICAgIENO
RyBhbGdvcml0aG1zLiAgVGhlIGpvYiBvZiB0aGUgVkFEIGlzIHRvIGRpc2Ny
aW1pbmF0ZSBiZXR3ZWVuDQogICAgYWN0aXZlIGFuZCBpbmFjdGl2ZSB2b2lj
ZSBzZWdtZW50cyBpbiB0aGUgaW5wdXQgc2lnbmFsLiAgRHVyaW5nDQogICAg
aW5hY3RpdmUgdm9pY2Ugc2VnbWVudHMsIHRoZSByb2xlIG9mIHRoZSBDTkcg
aXMgdG8gc3VmZmljaWVudGx5DQotICAgZGVzY3JpYmUgdGhlIGFtYmllbnQg
bm9pc2Ugd2hpbGUgbWluaW1pc2luZyB0aGUgdHJhbnNtaXNzaW9uIHJhdGUu
DQorICAgZGVzY3JpYmUgdGhlIGFtYmllbnQgbm9pc2Ugd2hpbGUgbWluaW1p
emluZyB0aGUgdHJhbnNtaXNzaW9uIHJhdGUuDQogICAgQSBTaWxlbmNlIElu
c2VydGlvbiBEZXNjcmlwdG9yIChTSUQpIGZyYW1lIGNvbnRhaW5pbmcgYSBk
ZXNjcmlwdGlvbg0KLSAgIG9mIHRoZSBub2lzZSBpcyBwYWNrZWQgaW50byB0
aGUgQ04gcGF5bG9hZCBhbmQgc2VudCB0byB0aGUgcmVjZWl2ZXIuDQotICAg
VGhlIERUWCBhbGdvcml0aG0gZGV0ZXJtaW5lcyB3aGVuIGEgU0lEIGZyYW1l
IGlzIHRyYW5zbWl0dGVkLiAgVGhlDQotICAgU0lEIGZyYW1lIGlzIHNlbnQg
b25jZSBhdCB0aGUgYmVnaW5uaW5nIG9mIGEgc2lsZW5jZSBwZXJpb2QsIGJ1
dCB0aGUNCisgICBvZiB0aGUgbm9pc2UgaXMgcGFja2VkIGludG8gdGhlIENO
IHBheWxvYWQgYW5kIHNlbnQgdG8gdGhlIHJlY2VpdmVyDQorICAgdG8gZHJp
dmUgdGhlIENORy4NCisgICBUaGUgRFRYIGFsZ29yaXRobSBkZXRlcm1pbmVz
IHdoZW4gYSBTSUQgZnJhbWUgaXMgdHJhbnNtaXR0ZWQuDQorICAgRHVyaW5n
IGFjdGl2ZSB2b2ljZSBzZWdtZW50cywgcGFja2V0cyBvZiB0aGUgdm9pY2Ug
Y29kZWMgYXJlIHRyYW5zbWl0dGVkDQorICAgYW5kIGluZGljYXRlZCBpbiB0
aGUgUlRQIGhlYWRlciBieSB0aGUgc3RhdGljIG9yIGR5bmFtaWMgcGF5bG9h
ZA0KKyAgIHR5cGUgZm9yIHRoYXQgY29kZWMuICBBdCB0aGUgYmVnaW5uaW5n
IG9mIGFuIGluYWN0aXZlIHZvaWNlIHNlZ21lbnQNCisgICAoc2lsZW5jZSBw
ZXJpb2QpLCBhIFNJRCBmcmFtZSBwYWNrZWQgaW50byBhIENOIHBhY2tldCBp
cw0KKyAgIHRyYW5zbWl0dGVkIGluIHRoZSBzYW1lIFJUUCBzdHJlYW0gYW5k
IGluZGljYXRlZCBieSB0aGUgQ04gcGF5bG9hZA0KKyAgIHR5cGUuICBUaGUg
U0lEIGZyYW1lIA0KICAgIHVwZGF0ZSByYXRlIGlzIGxlZnQgaW1wbGVtZW50
YXRpb24gc3BlY2lmaWMuICBGb3IgZXhhbXBsZSwgdGhlIFNJRA0KICAgIGZy
YW1lIG1heSBiZSBzZW50IHBlcmlvZGljYWxseSBvciBvbmx5IHdoZW4gdGhl
cmUgaXMgYSBzaWduaWZpY2FudA0KICAgIGNoYW5nZSBpbiB0aGUgYmFja2dy
b3VuZCBub2lzZSBjaGFyYWN0ZXJpc3RpY3MuICBUaGUgQ05HIGFsZ29yaXRo
bQ0KQEAgLTIxNiwxMCArMjE1LDUwIEBADQogICAgcGVyZm9ybWFuY2UgaW4g
dGhlIGRlc2lnbiBvZiB0aGUgVkFEL0RUWC9DTkcgYWxnb3JpdGhtcyBhcmUN
CiAgICBkZXNjcmliZWQgaW4gdGhlIEFwcGVuZGl4Lg0KIA0KLTcuIE1JTUUg
TWVkaWEgVHlwZSBSZWdpc3RyYXRpb25zDQorNi4xIFVzYWdlIG9mIFNEUA0K
Kw0KKyAgIFdoZW4gdXNpbmcgdGhlIFNlc3Npb24gRGVzY3JpcHRpb24gUHJv
dG9jb2wgKFNEUCkgWzEyXSB0byBzcGVjaWZ5DQorICAgUlRQIHBheWxvYWQg
aW5mb3JtYXRpb24sIHRoZSB1c2Ugb2YgY29tZm9ydCBub2lzZSBpcyBpbmRp
Y2F0ZWQgYnkNCisgICB0aGUgaW5jbHVzaW9uIG9mIGEgcGF5bG9hZCB0eXBl
IGZvciBDTiBvbiB0aGUgbWVkaWEgZGVzY3JpcHRpb24NCisgICBsaW5lLiAg
V2hlbiB1c2luZyBDTiB3aXRoIHRoZSBSVFAvQVZQIHByb2ZpbGUgWzExXSBh
bmQgYSBjb2RlYw0KKyAgIHdob3NlIFJUUCB0aW1lc3RhbXAgY2xvY2sgcmF0
ZSBpcyA4MDAwIEh6LCBzdWNoIGFzIEcuNzExIChQQ01VLA0KKyAgIHN0YXRp
YyBwYXlsb2FkIHR5cGUgMCksIHRoZSBzdGF0aWMgcGF5bG9hZCB0eXBlIDEz
IGZvciBDTiBjYW4gYmUNCisgICB1c2VkOg0KKw0KKyAgICAgIG09YXVkaW8g
NDkyMzAgUlRQL0FWUCAwIDEzDQorDQorICAgV2hlbiB1c2luZyBDTiB3aXRo
IGEgY29kZWMgdGhhdCBoYXMgYSBkaWZmZXJlbnQgUlRQIHRpbWVzdGFtcCBj
bG9jaw0KKyAgIHJhdGUsIGEgZHluYW1pYyBwYXlsb2FkIHR5cGUgbWFwcGlu
ZyAocnRwbWFwIGF0dHJpYnV0ZSkgaXMNCisgICByZXF1aXJlZC4gIFRoaXMg
ZXhhbXBsZSBzaG93cyBDTiB1c2VkIHdpdGggdGhlIEcuNzIyLjEgY29kZWMg
KHNlZQ0KKyAgIFJGQyAzMDQ3IFsxM10pOg0KKw0KKyAgICAgIG09YXVkaW8g
NDkyMzAgUlRQL0FWUCAxMDEgMTAyDQorICAgICAgYT1ydHBtYXA6MTAxIEc3
MjIxLzE2MDAwDQorICAgICAgYT1mbXRwOjEyMSBiaXRyYXRlPTI0MDAwDQor
ICAgICAgYT1ydHBtYXA6MTAyIENOLzE2MDAwDQorDQorICAgT21pc3Npb24g
b2YgYSBwYXlsb2FkIHR5cGUgZm9yIENOIG9uIHRoZSBtZWRpYSBkZXNjcmlw
dGlvbiBsaW5lDQorICAgaW1wbGllcyB0aGF0IGNvbWZvcnQgbm9pc2Ugd2ls
bCBub3QgYmUgdXNlZCwgYnV0IGl0IGRvZXMgbm90IGltcGx5DQorICAgdGhh
dCBzaWxlbmNlIHdpbGwgbm90IGJlIHN1cHByZXNzZWQuICBEaXNjb250aW51
b3VzIHRyYW5zbWlzc2lvbg0KKyAgIChzaWxlbmNlIHN1cHByZXNzaW9uKSBp
cyBpbmRpY2F0ZWQgYnkgYW4gaW5jcmVtZW50IGluIHRoZSBSVFANCisgICB0
aW1lc3RhbXAgd2l0aG91dCBhIGNvcnJlc3BvbmRpbmcgaW5jcmVtZW50IGlu
IHRoZSBSVFAgc2VxdWVuY2UNCisgICBudW1iZXIuDQorDQorNy4gSUFOQSBD
b25zaWRlcmF0aW9ucw0KIA0KICAgIFRoaXMgc2VjdGlvbiBkZWZpbmVzIGEg
bmV3IFJUUCBwYXlsb2FkIG5hbWUgYW5kIGFzc29jaWF0ZWQgTUlNRQ0KLSAg
IHR5cGUsIENOIChhdWRpby9DTikuDQorICAgdHlwZSwgQ04gKGF1ZGlvL0NO
KS4gVGhlIHBheWxvYWQgZm9ybWF0IHNwZWNpZmllZCBpbiB0aGlzIGRvY3Vt
ZW50DQorICAgaXMgYWxzbyBhc3NpZ25lZCBwYXlsb2FkIHR5cGUgMTMgaW4g
dGhlIFJUUCBQYXlsb2FkIFR5cGVzIHRhYmxlIG9mDQorICAgdGhlIFJUUCBQ
YXJhbWV0ZXJzIHJlZ2lzdHJ5IG1haW50YWluZWQgYnkgdGhlIEludGVybmV0
IEFzc2lnbmVkDQorICAgTnVtYmVycyBBdXRob3JpdHkgKElBTkEpLg0KKw0K
KyAgIFtOb3RlIHRvIElBTkEgYW5kIHRoZSBSRkMgRWRpdG9yLCB0byBiZSBk
ZWxldGVkIGJlZm9yZSBwdWJsaWNhdGlvbg0KKyAgIG9mIHRoaXMgZHJhZnQg
YXMgYW4gUkZDOiBUaGUgUlRQIFBheWxvYWQgVHlwZXMgdGFibGUgcmVmZXJl
bmNlZCBpbg0KKyAgIHRoZSBwcmV2aW91cyBwYXJhZ3JhcGggaXMgImNsb3Nl
ZCIgcGVyIHRoZSBwb2xpY3kgY2hhbmdlDQorICAgZXN0YWJsaXNoZWQgaW4g
ZHJhZnQtaWV0Zi1hdnQtcHJvZmlsZS1uZXctMTIsIGJ1dCB0aGF0IGRyYWZ0
IGFsc28NCisgICBzYXlzICJQYXlsb2FkIHR5cGUgMTMgaXMgcmVzZXJ2ZWQg
Zm9yIGEgY29tZm9ydCBub2lzZSBwYXlsb2FkDQorICAgZm9ybWF0IHRvIGJl
IHNwZWNpZmllZCBpbiBhIHNlcGFyYXRlIFJGQy4iICBUaGlzIGRvY3VtZW50
IGlzDQorICAgaW50ZW5kZWQgdG8gYmUgdGhhdCBzZXBhcmF0ZSBSRkMuXQ0K
IA0KIDcuMSBSZWdpc3RyYXRpb24gb2YgTUlNRSBtZWRpYSB0eXBlIGF1ZGlv
L0NODQogDQpAQCAtMjI5LDcgKzI2OCwxMSBAQA0KIA0KICAgIFJlcXVpcmVk
IHBhcmFtZXRlcnM6IE5vbmUNCiANCi0gICBPcHRpb25hbCBwYXJhbWV0ZXJz
OiByYXRlDQorICAgT3B0aW9uYWwgcGFyYW1ldGVyczoNCisgICByYXRlOiBz
cGVjaWZpZXMgdGhlIFJUUCB0aW1lc3RhbXAgY2xvY2sgcmF0ZSwgd2hpY2gg
aXMgdXN1YWxseSAoYnV0DQorICAgbm90IGFsd2F5cykgZXF1YWwgdG8gdGhl
IHNhbXBsaW5nIHJhdGUuICBUaGlzIHBhcmFtZXRlciBzaG91bGQgaGF2ZQ0K
KyAgIHRoZSBzYW1lIHZhbHVlIGFzIHRoZSBjb2RlYyB1c2VkIGluIGNvbmp1
bmN0aW9uIHdpdGggY29tZm9ydCBub2lzZS4NCisgICBUaGUgZGVmYXVsdCB2
YWx1ZSBpcyA4MDAwLg0KIA0KIA0KIFpvcGYgICAgICAgICAgICAgICAgU3Rh
bmRhcmRzIFRyYWNrIC0gQXByaWwsIDIwMDIgICAgICAgICAgICAgICAgICAg
NA0KQEAgLTIzOCw4ICsyODEsNyBAQA0KIA0KIA0KICAgIEVuY29kaW5nIGNv
bnNpZGVyYXRpb25zOg0KLSAgIFRoaXMgdHlwZSBpcyBvbmx5IGRlZmluZWQg
Zm9yIHRyYW5zZmVyIHZpYSBSVFAgW1JGQyBYWFhYLCBkcmFmdC0NCi0gICBp
ZXRmLWF2dC1ydHAtbmV3XS4NCisgICBUaGlzIHR5cGUgaXMgb25seSBkZWZp
bmVkIGZvciB0cmFuc2ZlciB2aWEgUlRQIFtSRkMgMTg4OV0uDQogDQogICAg
U2VjdXJpdHkgY29uc2lkZXJhdGlvbnM6IHNlZSBTZWN0aW9uIDggIlNlY3Vy
aXR5IENvbnNpZGVyYXRpb25zIi4NCiANCkBAIC0zMTgsNiArMzYwLDE0IEBA
DQogICAgICAgdmVjdG9ycyBmb3IgaW1wbGVtZW50YXRpb24gdmVyaWZpY2F0
aW9uIG9mIHRoZSBhbGdvcml0aG0gb2YgdGhlDQogICAgICAgRy43Mjkgc2ls
ZW5jZSBjb21wcmVzc2lvbiBzY2hlbWUuDQogDQorICAgMTEgU2NodWx6cmlu
bmUsIEguLCAiUlRQIFByb2ZpbGUgZm9yIEF1ZGlvIGFuZCBWaWRlbyBDb25m
ZXJlbmNlcw0KKyAgICAgIHdpdGggTWluaW1hbCBDb250cm9sIiwgUkZDIDE4
OTAsIEphbnVhcnkgMTk5Ni4NCisNCisgICAxMiBIYW5kbGV5LCBNLiBhbmQg
Vi4gSmFjb2Jzb24sICJTRFA6IFNlc3Npb24gRGVzY3JpcHRpb24NCisgICAg
ICBQcm90b2NvbCIsIFJGQyAyMzI3LCBBcHJpbCAxOTk4Lg0KKw0KKyAgIDEz
IEx1dGhpLCBQLiwgIlJUUCBQYXlsb2FkIEZvcm1hdCBmb3IgSVRVLVQgUmVj
b21tZW5kYXRpb24NCisgICAgICBHLjcyMi4xIiwgUkZDIDMwNDcsIEphbnVh
cnkgMjAwMS4NCiANCiANCiA5LiBBdXRob3IncyBBZGRyZXNzDQo=
--0-1915571904-1011429775=:15485--

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



From daemon@optimus.ietf.org  Sun Jan 20 22:14:35 2002
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 WAA20268
	for <avt-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:14:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA07270
	for avt-archive@odin.ietf.org; Sun, 20 Jan 2002 22:14:39 -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 WAA07201;
	Sun, 20 Jan 2002 22:13:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07164
	for <avt@optimus.ietf.org>; Sun, 20 Jan 2002 22:13:21 -0500 (EST)
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20243
	for <avt@ietf.org>; Sun, 20 Jan 2002 22:13:15 -0500 (EST)
From: James_Renkel@3com.com
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0L3CmI04700
	for <avt@ietf.org>; Sun, 20 Jan 2002 19:12:48 -0800 (PST)
Received: from hqsmtp01.3com.com (hqsmtp01.ops.3com.com [139.87.49.79])
	by opal.3com.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0L3Clq00364
	for <avt@ietf.org>; Sun, 20 Jan 2002 19:12:47 -0800 (PST)
Subject: Re: [AVT] Switch to subscriber-only posting?
To: AVT WG <avt@ietf.org>
Date: Sun, 20 Jan 2002 21:12:32 -0600
Message-ID: <OF5A63AA99.B94B15E4-ON86256B48.00118DB5@3com.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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


I fully support the idea. I had thinking about suggesting it. :-)

Jim





Stephen Casner <casner@acm.org>@ietf.org on 01/17/2002 08:56:51 PM

Sent by:  avt-admin@ietf.org


To:   AVT WG <avt@ietf.org>
cc:
Subject:  [AVT] Switch to subscriber-only posting?


Should we change the configuration of this mailing list so that posts
are only accepted from subscribers?  That is a pretty effective
technique for reducing spam.  The downside is that it is inconvenient
for people who use multiple mailboxes.
                                   -- Steve


_______________________________________________
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



From daemon@optimus.ietf.org  Mon Jan 21 11:13:06 2002
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 LAA14409
	for <avt-archive@odin.ietf.org>; Mon, 21 Jan 2002 11:13:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15352
	for avt-archive@odin.ietf.org; Mon, 21 Jan 2002 11:13:09 -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 LAA15326;
	Mon, 21 Jan 2002 11:12:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15297
	for <avt@optimus.ietf.org>; Mon, 21 Jan 2002 11:12:30 -0500 (EST)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14367
	for <avt@ietf.org>; Mon, 21 Jan 2002 11:12:25 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA17193;
	Mon, 21 Jan 2002 17:12:28 +0100 (MET)
Received: from mchh9ega.mchh.siemens.de (mchh9ega.mchh.siemens.de [139.21.204.219])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA07294;
	Mon, 21 Jan 2002 17:12:27 +0100 (MET)
Received: by mchh9ega.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <DMNP7XC4>; Mon, 21 Jan 2002 17:12:27 +0100
Message-ID: <07B0CDE3B76AD31190F700508B5D5D1DDF54E8@mchg9eba.mchh.siemens.de>
From: Faerber Tobias ICM MP PO8 RD MCH83 <Tobias.Faerber@mch.siemens.de>
To: "'Magnus Westerlund'" <magnus.westerlund@era.ericsson.se>
Cc: AVT WG <avt@ietf.org>
Date: Mon, 21 Jan 2002 17:12:26 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [AVT] question on DTX for AMR
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

1) in DTX mode: do you transmit a ToC in case a NO_DATA AMR frame is at the
end of a payload frame ?
e.g. you have {7,7,8,15,15} in one RTP frame ?
so is ther a ToC for the last two AMR frames? I guess not because you can
get the loss from the next timestamp info.

2) what happens if you send lots of NO_DATA frames, e.g. only NO_DATA frames
within one RTP payload. is there any ToC ?
e.g. 15,15,15,15,15 => 5 ToC s? or no one and backmapping through time stamp
of next RTP packet ?


best regards,
Tobi


----------------------------------------------------------------------------
-------
> Faerber Tobias		Siemens AG
ICM MP PO8 RD MCH83 	Information and Communication Mobile

> Tel:	+49 89 722 58578	Grillparzerstrasse 10 a
> mobile:  +49 175 5721351	81675 Munich, Germany
> Fax:	+49 89 722 59070	
mailto:tobias.faerber@mch.siemens.de
----------------------------------------------------------------------------
-------


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



From daemon@optimus.ietf.org  Mon Jan 21 12:38:33 2002
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 MAA17923
	for <avt-archive@odin.ietf.org>; Mon, 21 Jan 2002 12:38:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA20075
	for avt-archive@odin.ietf.org; Mon, 21 Jan 2002 12:38:30 -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 MAA20043;
	Mon, 21 Jan 2002 12:37:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20016
	for <avt@optimus.ietf.org>; Mon, 21 Jan 2002 12:37:46 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17898
	for <avt@ietf.org>; Mon, 21 Jan 2002 12:37:43 -0500 (EST)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g0LHbhIB012569;
	Mon, 21 Jan 2002 18:37:43 +0100 (MET)
Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id SAA28494; Mon, 21 Jan 2002 18:37:43 +0100
Message-ID: <3C4C51E6.81D8CC82@era.ericsson.se>
Date: Mon, 21 Jan 2002 18:37:43 +0100
From: Magnus Westerlund <magnus.westerlund@era.ericsson.se>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Faerber Tobias ICM MP PO8 RD MCH83 <Tobias.Faerber@mch.siemens.de>
CC: AVT WG <avt@ietf.org>
References: <07B0CDE3B76AD31190F700508B5D5D1DDF54E8@mchg9eba.mchh.siemens.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] Re: question on DTX for AMR
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
Content-Transfer-Encoding: 7bit

Hi,

I think both of these questions is answered in the sixth paragraph of section 2.
in draft-ietf-avt-rtp-amr-10.txt.

Faerber Tobias ICM MP PO8 RD MCH83 wrote:

> 1) in DTX mode: do you transmit a ToC in case a NO_DATA AMR frame is at the
> end of a payload frame ?
> e.g. you have {7,7,8,15,15} in one RTP frame ?
> so is ther a ToC for the last two AMR frames? I guess not because you can
> get the loss from the next timestamp info.
>

No you is recommended to exclude all NO_DATA in the end of packets. The
exception is interleaving.

>
> 2) what happens if you send lots of NO_DATA frames, e.g. only NO_DATA frames
> within one RTP payload. is there any ToC ?
> e.g. 15,15,15,15,15 => 5 ToC s? or no one and backmapping through time stamp
> of next RTP packet ?
>

No you should also never begin a packet with a NO_DATA frame, with the exception
of interleaving.

Cheers

Magnus Westerlund

Audio Technology, Ericsson Research
----------------------------------------------------------------------
Ericsson Radio Systems AB  | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@era-t.ericsson.se



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



From daemon@optimus.ietf.org  Mon Jan 21 12:49:21 2002
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 MAA18319
	for <avt-archive@odin.ietf.org>; Mon, 21 Jan 2002 12:49:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA20529
	for avt-archive@odin.ietf.org; Mon, 21 Jan 2002 12:49:23 -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 MAA20510;
	Mon, 21 Jan 2002 12:48:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20481
	for <avt@optimus.ietf.org>; Mon, 21 Jan 2002 12:48:54 -0500 (EST)
Received: from ns2.packetvideo.com (ns2.packetvideo.com [63.214.191.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18310
	for <avt@ietf.org>; Mon, 21 Jan 2002 12:48:51 -0500 (EST)
Received: from misty.packetvideo.com ([63.214.191.76])
	by ns2.packetvideo.com (8.11.4/8.11.4) with ESMTP id g0LHheP84239;
	Mon, 21 Jan 2002 09:43:40 -0800 (PST)
Received: by misty.packetvideo.com with Internet Mail Service (5.5.2653.19)
	id <ZZPX8D2C>; Mon, 21 Jan 2002 09:43:38 -0800
Message-ID: <72660A24B978D411BB8A00B0D03DFE0104F6800D@misty.packetvideo.com>
From: Ralph Neff <neff@PacketVideo.COM>
To: "'Faerber Tobias ICM MP PO8 RD MCH83'" <Tobias.Faerber@mch.siemens.de>
Cc: AVT WG <avt@ietf.org>
Subject: RE: [AVT] question on DTX for AMR
Date: Mon, 21 Jan 2002 09:43:32 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Filter-Version: 1.6a (ns2.packetvideo.com)
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


Hi Tobi,

> 1) in DTX mode: do you transmit a ToC in case a NO_DATA AMR frame is at
the
> end of a payload frame ?
> e.g. you have {7,7,8,15,15} in one RTP frame ?
> so is ther a ToC for the last two AMR frames? I guess not because you can
> get the loss from the next timestamp info.

I agree, there is no reason to add NO_DATA frames at the end.  
They'd only be needed if they were in between
other speech frames in the same packet (e.g. {7,7,8,15,15,7}).
So it's inefficient to put them at the end, but otherwise 
it seems legal (I didn't see anything in the draft prohibiting 
this).

> 2) what happens if you send lots of NO_DATA frames, e.g. only NO_DATA
frames
> within one RTP payload. is there any ToC ?
> e.g. 15,15,15,15,15 => 5 ToC s? or no one and backmapping through time
stamp
> of next RTP packet ?

You SHOULD NOT send packets with all NO_DATA frames (see Section 2.5,
third paragraph of the current draft (10)).  As you said, you detect
the loss when a packet arrives to break the "silence."

-Ralph


> best regards,
> Tobi


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



From daemon@ns.ietf.org  Tue Jan 22 13:37:56 2002
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 NAA04075
	for <avt-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:37:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA03607
	for avt-archive@odin.ietf.org; Tue, 22 Jan 2002 13:37:58 -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 NAA03442;
	Tue, 22 Jan 2002 13:35:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA03413
	for <avt@ns.ietf.org>; Tue, 22 Jan 2002 13:35:34 -0500 (EST)
Received: from NS1.US.PRSERV.NET ([64.180.246.83])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03964
	for <avt@ietf.org>; Tue, 22 Jan 2002 13:35:31 -0500 (EST)
From: sydney@vkistudios.org
Message-Id: <200201221835.NAA03964@ietf.org>
Reply-To: seo@vkistudios.org
To: avt@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Date: Tue, 22 Jan 2002 10:39:04 -0800
Subject: [AVT] ADV: Professional Internet Marketing
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

<HTML>
<HEAD>
<TITLE>Professional Internet Marketing, VKI Studios 1-866-733-8899</TITLE>
<META name="description" content="A web services company specializing dynamic Internet marketing">
<META name="keywords" content="Dynamic Internet Marketing">
<META http-equiv="CONTENT-LANGUAGE" content="English">
<META name="RATING" content="General">
<META name="distribution" content="global">
<META name="copyright" content="copyright 2002, VKI Studios">
<META name="robots" content="index,follow">
<META http-equiv=Expires content="O">
<LINK rel="stylesheet" href="http://www.vkistudios.com/css/vki.css" type="text/css">
</HEAD>

<BODY bgcolor="#FFFFFF" text="#000000" link="#990000" vlink="663333">
<TABLE width="550" border="0" cellspacing="0" cellpadding="2" align="center">
  <TR> 
    <TD class="newsletter" bgcolor="006699" width="190" align="center"> 
      <P><B><A href="http://www.vkistudios.com/form_internet_mkt.html"><BR>
        <IMG src="http://www.vkistudios.com/images/h_internet_mkt.gif" width="183" height="37" alt="VKI Studios - Internet Marketing Is Mission Critical For Your Business" border="0"></A><BR>
        <OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0" width="183" height="20">
          <PARAM name=movie value="http://www.vkistudios.com/swf/ani_email.swf">
          <PARAM name=quality value=high>
          <PARAM name="BGCOLOR" value="006699">
          <EMBED src="http://www.vkistudios.com/swf/ani_email.swf" quality=high pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="183" height="20" bgcolor="006699">
          </EMBED> 
        </OBJECT><BR>
        &nbsp;</B></P>
    </TD>
    <TD class="promo_header" bgcolor="006699" valign="top" align="right" width="360"><FONT color="#FFFFFF"><B>1-866-733-8899</B></FONT>&nbsp;</TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P><IMG src="http://www.vkistudios.com/images/shim_email0.gif" width="1" height="17"><B><FONT color="006699">&quot;VKI 
        increased our web traffic by 550%</FONT></B> which resulted in a 20% increase 
        in revenues in less than six months.&quot; John Keith-King, Curator, Granville 
        Island Museums.</P>
      <P>Would you like to see if you can achieve similar results? <BR>
        Call us at 1-866-733-8899 or fill out our <A href="http://www.vkistudios.com/form_internet_mkt.html">online 
        consultation</A> and receive a <B><FONT color="006699"><BR>
        FREE Search Engine Report<FONT size="-1"> (value $75.00)</FONT></FONT></B></P>
      <P><FONT color="#006699"><B><A href="http://www.vkistudios.com/form_internet_mkt.html"><IMG src="http://www.vkistudios.com/images/button_guarantee.gif" width="185" height="29" alt="Results Guaranteed" border="0"></A></B></FONT></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2">&nbsp;</TD>
  </TR>
  <TR> 
    <TD class="newsletter" valign="bottom" colspan="2"> 
      <P><FONT color="#006699"><B>THE BENEFITS</B></FONT></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI>Your website will become <FONT color="006699"><B>highly visible</B></FONT></LI>
        <LI>Your <FONT color="006699"><B>traffic will grow</B></FONT> exponentially</LI>
        <LI>Measurable and <FONT color="006699"><B>trackable results</B></FONT></LI>
        <LI>You will have an ongoing <FONT color="006699"><B>strategy that adapts 
          </B></FONT>as search engines change<BR>
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"><FONT color="#006699"><B> THE ELEVATION</B></FONT></TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI> Strategy development</LI>
        <LI>Keyword Formulation</LI>
        <LI>Creation of keyword &amp; description META tags</LI>
        <LI>Creation of keyword entry pages</LI>
        <LI>FTP file transfer to server</LI>
        <LI>Submission of web address (URL) to search engines</LI>
        <LI>Submission of web address (URL) to directory sites<BR>
          <A href="http://www.vkistudios.com/se_phase1.html">more info</A><BR>
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"><FONT color="#006699"><B>THE PUSH</B></FONT> 
      - ongoing maintenance includes:</TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI>Optimization - HTML optimization to be search engine friendly</LI>
        <LI>Submission - Proper submission protocol for each individual engine</LI>
        <LI>Registration - Verification of successful submissions</LI>
        <LI>Monitoring - Evaluation of server file logs for search engine activity</LI>
        <LI>Positioning - Fine-tuning of submitted pages</LI>
        <LI>Maintenance - Continuous attendance to all the above actions<BR>
          <A href="http://www.vkistudios.com/form_internet_mkt.html">Online consultation</A> 
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P>Many Search Engines are moving to paid listings so <B><FONT color="006699">ACT 
        NOW!</FONT></B><BR>
        <A href="http://www.vkistudios.com/form_internet_mkt.html">Contact us 
        today to take advantage of our limited time offer.</A></P>
      <P>Please call us: 1-866-733-8899 or (604) 733-1474 - <A href="http://www.vkistudios.com" target="_blank">VKI 
        Studios Inc.</A></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P>&nbsp;</P>
    </TD>
  </TR>
  <TR>
    <TD class="newsletter" colspan="2">If you do not wish to receive further mailings, 
      please <A href="http://www.vkistudios.com/remove/unsubscribe.html">unsubscribe 
      here.</A></TD>
  </TR>
</TABLE>
<P>&nbsp;</P>
</BODY>
</HTML>

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



From daemon@ns.ietf.org  Tue Jan 22 14:46:48 2002
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 OAA07711
	for <avt-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:46:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA08427
	for avt-archive@odin.ietf.org; Tue, 22 Jan 2002 14:46:51 -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 OAA08346;
	Tue, 22 Jan 2002 14:44:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08317
	for <avt@ns.ietf.org>; Tue, 22 Jan 2002 14:44:45 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07636;
	Tue, 22 Jan 2002 14:44:41 -0500 (EST)
Message-Id: <200201221944.OAA07636@ietf.org>
To: IETF-Announce: ;
Cc: avt@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Date: Tue, 22 Jan 2002 14:44:40 -0500
Subject: [AVT] Last Call: RTP: A Transport Protocol for Real-Time
 Applications to Draft Standard
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


The IESG has received a request from the Audio/Video Transport Working
Group to consider publication of the following Internet-Drafts as Draft
Standards:

 o RTP: A Transport Protocol for Real-Time Applications
     <draft-ietf-avt-rtp-new-11.txt>

   This document is intended to replace RFC1889, currently a Proposed
   Standard.

 o RTP Profile for Audio and Video Conferences with Minimal Control
     <draft-ietf-avt-profile-new-12.txt>

   This document is intended to replace RFC1890, currently a Proposed 
   Standard.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by February 5, 2002.

Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-new-11.txt
http://www.ietf.org/internet-drafts/draft-ietf-avt-profile-new-12.txt


Submitted Implementation Report can be accessed at:
http://www.ietf.org/IESG/Implementations/RTP-RTCP-Implementation.txt


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



From daemon@optimus.ietf.org  Wed Jan 23 05:39:28 2002
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 FAA05054
	for <avt-archive@odin.ietf.org>; Wed, 23 Jan 2002 05:39:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA20015
	for avt-archive@odin.ietf.org; Wed, 23 Jan 2002 05:39:30 -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 FAA19962;
	Wed, 23 Jan 2002 05:38:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19931
	for <avt@optimus.ietf.org>; Wed, 23 Jan 2002 05:38:33 -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 FAA05038
	for <avt@ietf.org>; Wed, 23 Jan 2002 05:38:29 -0500 (EST)
Received: by p-voyageur.rd.francetelecom.fr with Internet Mail Service (5.5.2653.19)
	id <C0MR9M8W>; Wed, 23 Jan 2002 11:31:11 +0100
Message-ID: <A7615804EC6DD511B90B0004ACE5BE4B015A5D84@L-RMHS.rd.francetelecom.fr>
From: AVARO Olivier FTRD/DIH/REN <olivier.avaro@rd.francetelecom.com>
To: Rob Lanphier <robla@real.com>, Dave Singer <singer@apple.com>
Cc: 4on2andIP-sys@advent.ee.columbia.edu, avt@ietf.org
Subject: RE: [AVT] MPEG-4 over IP draft: a=mpeg-iod (fwd)
Date: Wed, 23 Jan 2002 11:31:24 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-f3c477b0-0f6f-11d6-b1e4-00508b69ab48"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------=_NextPartTM-000-f3c477b0-0f6f-11d6-b1e4-00508b69ab48
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A3F9.1B64CE60"

------_=_NextPart_001_01C1A3F9.1B64CE60
Content-Type: text/plain



> -----Message d'origine-----
> De : Rob Lanphier [mailto:robla@real.com]
> Envoye : vendredi 21 decembre 2001 21:20
> A : Dave Singer
> Cc : 4on2andIP-sys@advent.ee.columbia.edu; avt@ietf.org
> Objet : Re: [AVT] MPEG-4 over IP draft: a=mpeg-iod (fwd)
> 
> 
> On Fri, 21 Dec 2001, Dave Singer wrote:
> >
> > >A (very belated) comment about singer-mpeg4-ip-03.txt:
> > >http://www.ietf.org/internet-drafts/draft-singer-mpeg4-ip-03.txt
> > >
> > >In Section 3, there's discussion about a new line in the 
> SDP when used with
> > >RTSP/RTP/SDP/MPEG-4 which gives metadata about the IOD 
> (MPEG-4 Initial
> > >Object Descriptor).
> > >
> > >Based on my rudimentary understanding of this, the idea is 
> that an client
> > >implementation should handle the following line as part of 
> an RTSP DESCRIBE
> > >response:
> > >
> > >a=mpeg4-iod [<location>]
> > >
> > >...where <location> is either a URL to a remote source, or 
> (more commonly)
> > >a data URL.
> > >
> > >Based on the presense of the IOD line, the client should 
> *not* issue
> > >subsequent SETUP and PLAY methods for the sources in that stream.
> >
Hi all,
  
> Rather, we
> should just realize that MPEG-4 IODs fall into a broader
> category of "synchronization formats" and that we should have generic
> hooks in SDP for that.

At that stage of the document, we can make editorial correction, but we can
definitly not change the design. It is too late.

I agree with Dave interpretation that I understand the following way :
MPEG-4 content must have this tag on and set properly. This content can be
used by non MPEG-4 terminals in a meaningfull way (they will just ignore it
and use the selfdescription of the streams). Non MPEG-4 streams can be added
to the session, either with the mechanisms suggested by Dave or by Young. I
don't think MPEG cares about which one is used. I guess both of them can
depending if you want to use your proprietary stream in an MPEG presentation
(Young solution) or not (Dave one's).

Kind regards,

Olivier 

------_=_NextPart_001_01C1A3F9.1B64CE60
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [AVT] MPEG-4 over IP draft: a=3Dmpeg-iod (fwd)</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Message d'origine-----</FONT>
<BR><FONT SIZE=3D2>&gt; De : Rob Lanphier [<A =
HREF=3D"mailto:robla@real.com">mailto:robla@real.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Envoy&eacute; : vendredi 21 d&eacute;cembre =
2001 21:20</FONT>
<BR><FONT SIZE=3D2>&gt; &Agrave; : Dave Singer</FONT>
<BR><FONT SIZE=3D2>&gt; Cc : 4on2andIP-sys@advent.ee.columbia.edu; =
avt@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Objet : Re: [AVT] MPEG-4 over IP draft: =
a=3Dmpeg-iod (fwd)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On Fri, 21 Dec 2001, Dave Singer wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;A (very belated) comment about =
singer-mpeg4-ip-03.txt:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-singer-mpeg4-ip-03.txt=
" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-singer-mpeg4=
-ip-03.txt</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;In Section 3, there's discussion about =
a new line in the </FONT>
<BR><FONT SIZE=3D2>&gt; SDP when used with</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;RTSP/RTP/SDP/MPEG-4 which gives =
metadata about the IOD </FONT>
<BR><FONT SIZE=3D2>&gt; (MPEG-4 Initial</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;Object Descriptor).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;Based on my rudimentary understanding =
of this, the idea is </FONT>
<BR><FONT SIZE=3D2>&gt; that an client</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;implementation should handle the =
following line as part of </FONT>
<BR><FONT SIZE=3D2>&gt; an RTSP DESCRIBE</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;response:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;a=3Dmpeg4-iod =
[&lt;location&gt;]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;...where &lt;location&gt; is either a =
URL to a remote source, or </FONT>
<BR><FONT SIZE=3D2>&gt; (more commonly)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;a data URL.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;Based on the presense of the IOD line, =
the client should </FONT>
<BR><FONT SIZE=3D2>&gt; *not* issue</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;subsequent SETUP and PLAY methods for =
the sources in that stream.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>Hi all,</FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Rather, we</FONT>
<BR><FONT SIZE=3D2>&gt; should just realize that MPEG-4 IODs fall into =
a broader</FONT>
<BR><FONT SIZE=3D2>&gt; category of &quot;synchronization formats&quot; =
and that we should have generic</FONT>
<BR><FONT SIZE=3D2>&gt; hooks in SDP for that.</FONT>
</P>

<P><FONT SIZE=3D2>At that stage of the document, we can make editorial =
correction, but we can definitly not change the design. It is too =
late.</FONT></P>

<P><FONT SIZE=3D2>I agree with Dave interpretation that I understand =
the following way : MPEG-4 content must have this tag on and set =
properly. This content can be used by non MPEG-4 terminals in a =
meaningfull way (they will just ignore it and use the selfdescription =
of the streams). Non MPEG-4 streams can be added to the session, either =
with the mechanisms suggested by Dave or by Young. I don't think MPEG =
cares about which one is used. I guess both of them can depending if =
you want to use your proprietary stream in an MPEG presentation (Young =
solution) or not (Dave one's).</FONT></P>

<P><FONT SIZE=3D2>Kind regards,</FONT>
</P>

<P><FONT SIZE=3D2>Olivier </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A3F9.1B64CE60--

------=_NextPartTM-000-f3c477b0-0f6f-11d6-b1e4-00508b69ab48--


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



From daemon@optimus.ietf.org  Wed Jan 23 05:56:52 2002
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 FAA05323
	for <avt-archive@odin.ietf.org>; Wed, 23 Jan 2002 05:56:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA20546
	for avt-archive@odin.ietf.org; Wed, 23 Jan 2002 05:56:50 -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 FAA20527;
	Wed, 23 Jan 2002 05:56:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA20498
	for <avt@optimus.ietf.org>; Wed, 23 Jan 2002 05:56:23 -0500 (EST)
Received: from ms1.uibk.ac.at (ms1.uibk.ac.at [138.232.1.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05318
	for <avt@ietf.org>; Wed, 23 Jan 2002 05:56:19 -0500 (EST)
Received: from c703-pc55.uibk.ac.at (c703-pc55.uibk.ac.at [138.232.65.57] michael.welzl@uibk.ac.at)
  by ms1.uibk.ac.at (8.11.3/E2) with ESMTP id g0NAtEW43697273;
  Wed, 23 Jan 2002 11:55:14 +0100 (MET)
Subject: RE: [AVT] MPEG-4 over IP draft: a=mpeg-iod (fwd)
From: Michael Welzl <michael.welzl@uibk.ac.at>
To: AVARO Olivier FTRD/DIH/REN <olivier.avaro@rd.francetelecom.com>
Cc: Rob Lanphier <robla@real.com>, Dave Singer <singer@apple.com>,
        4on2andIP-sys@advent.ee.columbia.edu, avt@ietf.org
In-Reply-To: 
	<A7615804EC6DD511B90B0004ACE5BE4B015A5D84@L-RMHS.rd.francetelecom.fr>
References: 
	<A7615804EC6DD511B90B0004ACE5BE4B015A5D84@L-RMHS.rd.francetelecom.fr>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0 (Preview Release)
Date: 23 Jan 2002 11:55:26 +0100
Message-Id: <1011783328.2162.29.camel@c703-pc55>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hi,

Due to the good results achieved with UDP Lite in "Performance
Evaluation of UDP Lite for Cellular Video", NOSSDAV 2001, I would
recommend to add a little note about MPEG4 over UDP Lite.

Cheers,
Michael

On Wed, 2002-01-23 at 11:31, AVARO Olivier FTRD/DIH/REN wrote:
> 
> 
> > -----Message d'origine-----
> > De : Rob Lanphier [mailto:robla@real.com]
> > Envoye : vendredi 21 decembre 2001 21:20
> > A : Dave Singer
> > Cc : 4on2andIP-sys@advent.ee.columbia.edu; avt@ietf.org
> > Objet : Re: [AVT] MPEG-4 over IP draft: a=mpeg-iod (fwd)
> > 
> > 
> > On Fri, 21 Dec 2001, Dave Singer wrote:
> > >
> > > >A (very belated) comment about singer-mpeg4-ip-03.txt:
> > > >http://www.ietf.org/internet-drafts/draft-singer-mpeg4-ip-03.txt
> > > >
> > > >In Section 3, there's discussion about a new line in the 
> > SDP when used with
> > > >RTSP/RTP/SDP/MPEG-4 which gives metadata about the IOD 
> > (MPEG-4 Initial
> > > >Object Descriptor).
> > > >
> > > >Based on my rudimentary understanding of this, the idea is 
> > that an client
> > > >implementation should handle the following line as part of 
> > an RTSP DESCRIBE
> > > >response:
> > > >
> > > >a=mpeg4-iod [<location>]
> > > >
> > > >...where <location> is either a URL to a remote source, or 
> > (more commonly)
> > > >a data URL.
> > > >
> > > >Based on the presense of the IOD line, the client should 
> > *not* issue
> > > >subsequent SETUP and PLAY methods for the sources in that stream.
> > >
> Hi all,
>   
> > Rather, we
> > should just realize that MPEG-4 IODs fall into a broader
> > category of "synchronization formats" and that we should have generic
> > hooks in SDP for that.
> 
> At that stage of the document, we can make editorial correction, but we can
> definitly not change the design. It is too late.
> 
> I agree with Dave interpretation that I understand the following way :
> MPEG-4 content must have this tag on and set properly. This content can be
> used by non MPEG-4 terminals in a meaningfull way (they will just ignore it
> and use the selfdescription of the streams). Non MPEG-4 streams can be added
> to the session, either with the mechanisms suggested by Dave or by Young. I
> don't think MPEG cares about which one is used. I guess both of them can
> depending if you want to use your proprietary stream in an MPEG presentation
> (Young solution) or not (Dave one's).
> 
> Kind regards,
> 
> Olivier 



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



From daemon@optimus.ietf.org  Wed Jan 23 15:57:32 2002
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 PAA25133
	for <avt-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:57:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA17352
	for avt-archive@odin.ietf.org; Wed, 23 Jan 2002 15:57:34 -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 PAA17308;
	Wed, 23 Jan 2002 15:56:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA17277
	for <avt@optimus.ietf.org>; Wed, 23 Jan 2002 15:56:29 -0500 (EST)
Received: from bullwinkle.real.com (bullwinkle.real.com [207.188.22.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25108
	for <avt@ietf.org>; Wed, 23 Jan 2002 15:56:26 -0500 (EST)
Received: from prognet.com ([::ffff:205.219.198.1])
  by bullwinkle.real.com with esmtp; Wed, 23 Jan 2002 12:55:48 -0800
Received: from ROBLA350 ([172.23.100.116])
	by prognet.com (8.9.2/8.9.0) with ESMTP id MAA32739;
	Wed, 23 Jan 2002 12:55:56 -0800 (PST)
Date: Wed, 23 Jan 2002 12:56:55 -0800 (Pacific Standard Time)
From: Rob Lanphier <robla@real.com>
To: "AVARO Olivier FTRD/DIH/REN" <olivier.avaro@rd.francetelecom.com>
cc: Dave Singer <singer@apple.com>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>,
        "avt@ietf.org" <avt@ietf.org>
Subject: RE: [AVT] MPEG-4 over IP draft: a=mpeg-iod (fwd)
In-Reply-To: <A7615804EC6DD511B90B0004ACE5BE4B015A5D84@L-RMHS.rd.francetelecom.fr>
Message-ID: <Pine.WNT.4.43.0201231248230.297-100000@robla350.dev.prognet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Wed, 23 Jan 2002, AVARO Olivier FTRD/DIH/REN wrote:
> At that stage of the document, we can make editorial correction, but we can
> definitly not change the design. It is too late.

It may be too late in the MPEG process, but not in the IETF process.  It
would be unfortunate if the two diverged, but if the MPEG committee comes
up with something that is broken, then the IETF can (and should) come up
with something that is not.

The specific point regarding mpeg4-iod is perhaps not worth diverging on,
but Colin raised some issues earlier that I don't think have been
addressed very well.

Rob



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



From daemon@optimus.ietf.org  Wed Jan 23 16:25:34 2002
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 QAA26059
	for <avt-archive@odin.ietf.org>; Wed, 23 Jan 2002 16:25:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA18356
	for avt-archive@odin.ietf.org; Wed, 23 Jan 2002 16:25:37 -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 QAA18338;
	Wed, 23 Jan 2002 16:24:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18302
	for <avt@optimus.ietf.org>; Wed, 23 Jan 2002 16:24:36 -0500 (EST)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26031
	for <avt@ietf.org>; Wed, 23 Jan 2002 16:24:32 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g0NLOX708406
	for <avt@ietf.org>; Wed, 23 Jan 2002 13:24:33 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T589fed999f118164e13bc@mailgate2.apple.com>;
 Wed, 23 Jan 2002 13:24:30 -0800
Received: from [192.168.1.102] (vpn-gh-1078.apple.com [17.254.140.53])
	by scv2.apple.com (8.11.3/8.11.3) with ESMTP id g0NLOTw17329;
	Wed, 23 Jan 2002 13:24:29 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p05010403b874da468ed8@[192.168.1.102]>
In-Reply-To: 
 <Pine.WNT.4.43.0201231248230.297-100000@robla350.dev.prognet.com>
References: 
 <Pine.WNT.4.43.0201231248230.297-100000@robla350.dev.prognet.com>
Date: Wed, 23 Jan 2002 16:23:55 -0500
To: Rob Lanphier <robla@real.com>
From: Dave Singer <singer@apple.com>
Subject: RE: [AVT] MPEG-4 over IP draft: a=mpeg-iod (fwd)
Cc: AVARO Olivier FTRD/DIH/REN <olivier.avaro@rd.francetelecom.com>,
        "4on2andIP-sys@advent.ee.columbia.edu" <4on2andIP-sys@advent.ee.columbia.edu>,
        "avt@ietf.org" <avt@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 12:56 PM -0800 1/23/02, Rob Lanphier wrote:
>On Wed, 23 Jan 2002, AVARO Olivier FTRD/DIH/REN wrote:
>>  At that stage of the document, we can make editorial correction, but we can
>>  definitly not change the design. It is too late.
>
>It may be too late in the MPEG process, but not in the IETF process.  It
>would be unfortunate if the two diverged, but if the MPEG committee comes
>up with something that is broken, then the IETF can (and should) come up
>with something that is not.
>
>The specific point regarding mpeg4-iod is perhaps not worth diverging on,
>but Colin raised some issues earlier that I don't think have been
>addressed very well.
>
>Rob

Don't worry.  I agree, and MPEG folks agreed that these points should 
be addressed.  We have permission to do so at MPEG.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@optimus.ietf.org  Wed Jan 23 23:37:43 2002
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 XAA05880
	for <avt-archive@odin.ietf.org>; Wed, 23 Jan 2002 23:37:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA01361
	for avt-archive@odin.ietf.org; Wed, 23 Jan 2002 23:37:46 -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 XAA01332;
	Wed, 23 Jan 2002 23:36:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA01278
	for <avt@optimus.ietf.org>; Wed, 23 Jan 2002 23:36:52 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05869
	for <avt@ietf.org>; Wed, 23 Jan 2002 23:36:47 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0O4Yip98947;
	Wed, 23 Jan 2002 20:34:45 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Wed, 23 Jan 2002 20:37:05 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Marshall Eubanks <tme@multicasttech.com>
cc: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>, AVT WG <avt@ietf.org>
Subject: Re: [AVT] Revised WG last call status
In-Reply-To: <web-1232103@multicasttech.com>
Message-ID: <20020123203527.F2930-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

Marshall,

>    I am currently reading
>
> Unequal Erasure Protection (draft-ietf-avt-uxp-01.txt)
> Uneven Level Protection (draft-ietf-avt-ulp-03.txt )
> MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)
> MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)
>
> and would be willing to write reviews next week.

Thank you for that generous offer.

I have not seen other offers.  Have reviewing arrangements for other
drafts been made off-list?
							-- Steve


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



From daemon@optimus.ietf.org  Wed Jan 23 23:37:43 2002
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 XAA05889
	for <avt-archive@odin.ietf.org>; Wed, 23 Jan 2002 23:37:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA01375
	for avt-archive@odin.ietf.org; Wed, 23 Jan 2002 23:37:46 -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 XAA01308;
	Wed, 23 Jan 2002 23:36:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA01270
	for <avt@optimus.ietf.org>; Wed, 23 Jan 2002 23:36:51 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05867
	for <avt@ietf.org>; Wed, 23 Jan 2002 23:36:46 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0O4Wqp98919;
	Wed, 23 Jan 2002 20:32:52 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Wed, 23 Jan 2002 20:35:13 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Rex Coldren <coldrenr@agcs.com>
cc: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>, AVT WG <avt@ietf.org>
Subject: Re: [AVT] Revised WG last call status
In-Reply-To: <3C483198.1DD8585D@agcs.com>
Message-ID: <20020123202627.X2930-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Fri, 18 Jan 2002, Rex Coldren wrote:
> Another way of looking at this is, if nobody but the author (and his or
> her organization) is interested in a draft it should probably not be
> proceeding toward standard.  We should probably drop any draft
> that doesn't get volunteers to review it.  At least that would save
> having to deprecate something later when no interoperable
> implementations turn up.

I think that is an excellent point.


"Henning G. Schulzrinne" wrote:
> As an additional measure, I would suggest that each draft is explicitly
> assigned at least one, preferably up to three, reviewers. These
> reviewers can be suggested by the authors and should be explicitly
> charged with the task by the chairs. One possibility is to do the
> standard trick commonly employed by conferences and journals: if you
> submit a paper, you are asked to review other pending papers. Thus, in
> our case, authors of other pending drafts could be assigned such
> reviews. The reviews should have deadlines of, say, a month.

The method I described attempts to achieve the same goal without
putting the chairs in a role of cornering reviewers.  Making the
authors responsible for that task distributes the work, and is
acceptable unless the authors try to subvert the process by a poor
choice of reviewers.  I think we can manage this.  I, too, suggested
that other authors form the fertile pool for selecting reviewers.  I
did not state a deadline; that goes toward Rex's point above.

This does not preclude the chairs from taking action where warranted.

							-- Steve


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



From daemon@ns.ietf.org  Thu Jan 24 12:42:30 2002
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 MAA29026
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 12:42:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA11614
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 12:42:31 -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 MAA11545;
	Thu, 24 Jan 2002 12:41:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11514
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 12:41:42 -0500 (EST)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28986
	for <avt@ietf.org>; Thu, 24 Jan 2002 12:41:30 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sj1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id JAA23918; Thu, 24 Jan 2002 09:40:31 -0800 (PST)
Message-Id: <4.1.20020124113649.013cde88@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 24 Jan 2002 11:40:11 -0600
To: John Lazzaro <lazzaro@CS.Berkeley.EDU>, avt@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [AVT] Re: Switch to subscriber-only posting?
In-Reply-To: <200201181849.KAA06073@snap.CS.Berkeley.EDU>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1281169744==_.ALT"
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

--=====================_1281169744==_.ALT
Content-Type: text/plain; charset="us-ascii"


At 10:49 AM 1/18/2002 -0800, John Lazzaro wrote:
>
>> From: Stephen Casner <casner@acm.org>
>> Should we change the configuration of this mailing list so that posts
>> are only accepted from subscribers?  
>
>Given that many of the WG mailing lists are under the ietf.org 
>umbrella now, it might be worth considering extending posting
>rights to subscribed members of related IETF groups -- it   
>seems like the most common reason for a non-AVT-subscriber to
>post is to forward a discussion from a related WG list, and if
>its technically possible to retain this feature it would be good.

Chairs -- this suggestion from John above seems like the best of all. Can this
filter be set up to accept messages from members of this list AND from members
of other groups on the same server (ietf.org)? This would allow intermingling
between lists -- and that should be encouraged, IMO.

>
>Aside from that caveat, though, blocking non-subscribers sounds
>like a great idea ...
>
>-------------------------------------------------------------------------
>John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
>lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
>-------------------------------------------------------------------------
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt

*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"

James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com
--=====================_1281169744==_.ALT
Content-Type: text/html; charset="us-ascii"

<html><div>At 10:49 AM 1/18/2002 -0800, John Lazzaro wrote:</div>
<div>&gt;</div>
<div>&gt;&gt; From: Stephen Casner &lt;casner@acm.org&gt;</div>
<div>&gt;&gt; Should we change the configuration of this mailing list so
that posts</div>
<div>&gt;&gt; are only accepted from subscribers?&nbsp; </div>
<div>&gt;</div>
<div>&gt;Given that many of the WG mailing lists are under the ietf.org
</div>
<div>&gt;umbrella now, it might be worth considering extending
posting</div>
<div>&gt;rights to subscribed members of related IETF groups --
it&nbsp;&nbsp; </div>
<div>&gt;seems like the most common reason for a non-AVT-subscriber
to</div>
<div>&gt;post is to forward a discussion from a related WG list, and
if</div>
<div>&gt;its technically possible to retain this feature it would be
good.</div>
<br>
<div>Chairs -- this suggestion from John above seems like the best of
all. Can this filter be set up to accept messages from members of this
list AND from members of other groups on the same server (ietf.org)? This
would allow intermingling between lists -- and that should be encouraged,
IMO.</div>
<br>
<div>&gt;</div>
<div>&gt;Aside from that caveat, though, blocking non-subscribers
sounds</div>
<div>&gt;like a great idea ...</div>
<div>&gt;</div>
<div>&gt;-------------------------------------------------------------------------</div>
<div>&gt;John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC
Berkeley</div>
<div>&gt;lazzaro [at] cs [dot] berkeley [dot] edu&nbsp;&nbsp;&nbsp;&nbsp;
<a href="http://www.cs.berkeley.edu/~lazzaro" EUDORA=AUTOURL>www.cs.berkeley.edu/~lazzaro</a></div>
<div>&gt;-------------------------------------------------------------------------</div>
<div>&gt;</div>
<div>&gt;_______________________________________________</div>
<div>&gt;Audio/Video Transport Working Group</div>
<div>&gt;avt@ietf.org</div>
<div>&gt;<a href="https://www1.ietf.org/mailman/listinfo/avt" EUDORA=AUTOURL>https://www1.ietf.org/mailman/listinfo/avt</a></div>
<br>

<div align="center">
*************************************<br>
&quot;People generally demand more respect for their own rights than they
are willing to allow for others&quot;<br>
<br>
</div>
James M. Polk<br>
Consulting Engineer<br>
Office of the CTO<br>
<br>
Cisco Systems<br>
2200 East President George Bush Turnpike <br>
Richardson, TX&nbsp; 75082 USA<br>
w) 972.813.5208<br>
f)&nbsp; 972.813.5280<br>
<a href="http://www.cisco.com/" eudora="autourl">www.cisco.com</a></html>

--=====================_1281169744==_.ALT--


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



From daemon@ns.ietf.org  Thu Jan 24 14:22:31 2002
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 OAA02924
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 14:22:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA16876
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 14:22:33 -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 OAA16819;
	Thu, 24 Jan 2002 14:21:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA16790
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 14:21:20 -0500 (EST)
Received: from purple.nge.isi.edu (purple.nge.isi.edu [65.114.169.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02902
	for <avt@ietf.org>; Thu, 24 Jan 2002 14:21:13 -0500 (EST)
Received: from purple.nge.isi.edu (csp@localhost)
	by purple.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g0OJLG310136;
	Thu, 24 Jan 2002 14:21:16 -0500
Message-Id: <200201241921.g0OJLG310136@purple.nge.isi.edu>
To: "James M. Polk" <jmpolk@cisco.com>
cc: John Lazzaro <lazzaro@CS.Berkeley.EDU>, avt@ietf.org
Subject: Re: [AVT] Re: Switch to subscriber-only posting? 
In-Reply-To: Your message of "Thu, 24 Jan 2002 11:40:11 CST."
             <4.1.20020124113649.013cde88@localhost> 
Date: Thu, 24 Jan 2002 14:21:16 -0500
From: Colin Perkins <csp@isi.edu>
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

--> "James M. Polk" writes:
>At 10:49 AM 1/18/2002 -0800, John Lazzaro wrote:
>>
>>> From: Stephen Casner <casner@acm.org>
>>> Should we change the configuration of this mailing list so that posts
>>> are only accepted from subscribers?  
>>
>>Given that many of the WG mailing lists are under the ietf.org 
>>umbrella now, it might be worth considering extending posting
>>rights to subscribed members of related IETF groups -- it   
>>seems like the most common reason for a non-AVT-subscriber to
>>post is to forward a discussion from a related WG list, and if
>>its technically possible to retain this feature it would be good.
>
>Chairs -- this suggestion from John above seems like the best of all. Can this
>filter be set up to accept messages from members of this list AND from members
>of other groups on the same server (ietf.org)? This would allow intermingling
>between lists -- and that should be encouraged, IMO.

That's not possible with the current setup.

Colin

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



From daemon@ns.ietf.org  Thu Jan 24 15:18:38 2002
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 PAA04441
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 15:18:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA19881
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 15:18:36 -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 PAA19805;
	Thu, 24 Jan 2002 15:17:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19777
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 15:17:18 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04402
	for <avt@ietf.org>; Thu, 24 Jan 2002 15:17:14 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0OKGkp24663;
	Thu, 24 Jan 2002 12:16:46 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Thu, 24 Jan 2002 12:19:08 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Subject: Re: [AVT] Switch to subscriber-only posting?
In-Reply-To: <20020117185420.P91046-100000@ash.packetdesign.com>
Message-ID: <20020124103905.P4441-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

One week ago I asked:

> Should we change the configuration of this mailing list so that posts
> are only accepted from subscribers?  That is a pretty effective
> technique for reducing spam.  The downside is that it is inconvenient
> for people who use multiple mailboxes.

Nobody objected to this change, and many emphatically supported it.
The only concern was that MIDCOM had tried this and it turned into a
long discussion on that list with the eventual result that it was
turned off.  In reading that discussion, it seems that the objections
arose because the poster received an autoreply saying the mail was
rejected, and that the wording of that autoreply was poorly chosen.

That objection can be avoided by not sending an autoreply and relying
on the list administrators (that would be your faithful WG chairs) to
pass or reject the messages.  I was hoping to avoid that work (so I
wouldn't have to look at the spam, either), but it looks like that is
not acceptable.

John Lazzaro made an excellent suggestion that posting by any ietf
list subscriber should be automatically allowed.  I asked Steve Coya
and Stanley Weilnau if the IETF mailman system coud be set up to do
this, and got a negative response.  Stanley seems to think that having
the admin do filtering is sufficient.  I still think this is an idea
that should be pursued, but it looks like a little programming will be
required.

So, we will change the list to subscriber-only, using admin approval
and no autoreply on non-subscriber bounces.

PLEASE, any of you who post from an address other than the one that is
subscribed:  you can subscribe from an alternate address and select no
delivery to that address.  To do this, first subscribe the alternate
address via email or the web link:

   https://www1.ietf.org/mailman/listinfo/avt

Then, after the subscription is established, go back to that web page
and enter the alternate address next to the "Edit Options" button at
the bottom of the page and click that button.  On the options page,
click the "Disable mail delivery" checkbox, enter the password that
you entered for the alternate address into the box at the bottom of
the page, and click "Submit My Changes".

Your password is mailed to you monthly.  If you forget it, you can
click the "Email My Password To Me" button in the middle of the
options page.
							-- Steve


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



From daemon@ns.ietf.org  Thu Jan 24 15:26:57 2002
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 PAA04663
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 15:26:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA20254
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 15:26:55 -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 PAA20233;
	Thu, 24 Jan 2002 15:26:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA20198
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 15:26:13 -0500 (EST)
Received: from snap.CS.Berkeley.EDU (IDENT:root@snap.CS.Berkeley.EDU [128.32.45.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04653
	for <avt@ietf.org>; Thu, 24 Jan 2002 15:26:09 -0500 (EST)
Received: (from lazzaro@localhost)
	by snap.CS.Berkeley.EDU (8.9.3/8.9.3-ZUUL) id MAA02195
	for avt@ietf.org; Thu, 24 Jan 2002 12:26:08 -0800
Date: Thu, 24 Jan 2002 12:26:08 -0800
From: John Lazzaro <lazzaro@CS.Berkeley.EDU>
Message-Id: <200201242026.MAA02195@snap.CS.Berkeley.EDU>
To: avt@ietf.org
Subject: [AVT] Review of draft-ietf-avt-dsr-00.txt
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



> Stephen Casner writes:
>
> I have not seen other offers.  Have reviewing arrangements for other
> drafts been made off-list?

Here's my review of:

    Distributed Speech Recognition (draft-ietf-avt-dsr-00.txt)


From lowest level of abstraction to highest ...


[1] Spelling errors:

engin --> engine
engins --> engines
increacing --> increasing
recogziers --> recognizers

It looks like engin made it into someone's spell-checker dictionary,
given how many times this misspelling shows up ...


[2] Sentence structure:

  o "encapsulating a front-end signal processing feature streams"

    Plurality issue -- remove the "a".

  o "A solution that combats this uses a scheme called [...]"

    Never use "this" as a noun -- try:

    To address this problem, we use a distributed speech 
    recognition (DSR) architecture.

  o "The remote device processes the speech, compresses, and error protects
    the bitstream, [...]"

    Either remove the comma after "compresses", or add a noun phrase:

    compresses the data, and adds error protection to the bitstream

  o "Therefore, it will be desirable"

    Verb tense problems: you've committed to using present tense in
    this document, so a future-tense sentence like this one is not
    good style -- rewrite. Read through the document front to back
    looking for other future tense sentences, and rewrite them too!
   
  o "frame-pairs"

    Ditch the dash -- pair is the noun, frame is the adjective, the
    two work fine together without needing a dash.

  o "A decreasing number of FPs per payload packet [...]"

    The using of increasing/decreasing is bad form here -- we're not
    talking about dynamically changing the FPs per packet, we're 
    discussing the optimal number of FPs per packet as a static 
    decision. Rewrite.

  o "rises the potential of the loss of a large number"

    Bad English -- try:

    "increases the probability of catastrophic packet loss"

  o "A contiguous segment of DSR frames"

    Try:

    a set DSR frames coding an unbroken speech segment transmitted
    from the terminal to the server

  o "This is a lossy compression, with the output being a frame 
     containing an integer representation of the encoded speech."

    I tried reading this a few times, but I can't see why you'd
    bother noting the coefficients are integers -- I don't know
    of anyone coding mel-cepstra coefficients as floats or char
    strings :-). Delete or rephrase.


[3] IETF issues

   o At the head and the tail of the document, replace the 
     "expires in 6 months" phrase with the actual date of 
     expiration.

   o Someone with more experience in IETF stuff should search
     on RECOMMENDED, SHOULD, and MUST, to make sure each usage
     rises to the level where it deserves the all-caps, RFC-2119
     connotation -- I suspect a few of them are really lower-case
     in reality.

   o The bitfield figures lack titles -- add a "Figure N" and a title
     under each bitfield, and refer to each in the text as "Figure N."


[4] Content -- micro issues

    o Psychologically, its very comforting to see RTP headers on
      the top of payload bitfields -- it reminds people that the
      bitfield shown is the entire payload. So add them to the
      appropriate figures.

    o Explicit comments about the marker bit, timestamp, and 
      sequence number are in order -- even if each comment is 
      "no special usage or semantics", having such a comment
      acts to caution implementors not to do "embrace and extend"
      on the RTP header (the marker bit is always tempting ...). 
      Also, be explicit about the dynamic payload number, to 
      remind implementors the days of static payload numbers are
      over.

    o The packetization has a bunch of implicit decisions in it,
      about where in the transmission chain it makes sense to
      do the obvious "over-the-air" stuff (packing idx's and
      frames into sub-octets, and adding the 4-bit CRCs). By
      putting them in the RTP packet, instead of defining an
      octet-based, non-CRC packetization, the assumption is
      that general-purpose servers doing SR are better at doing
      bit-level ops than the device that interfaces the on-air
      to the first IP link. Specifically:

      [1] not zero-padding each idx coefficient to be 8 bits
      [2] failing [1], not zero-padding each frame or frame pair
          to be octet-aligned.
      [3] including the 4-bit CRC

      are consequences of this decision. Do people in the group
      feel comfortable with this decision?


[5] Content -- macro issues.

    I realize suggestions of the sort I'm about to make are out
    of place this late in the review process -- I'm bringing them
    up to inspire someone else to do a better next-generation 
    packetization, not because I expect the authors to start
    from scratch on this one :-).

    I think defining an unparameterized, plain-vanilla mel-cepstra
    front end is the wrong way to go. Back when I was doing SR
    work, so much of the difference between "usable recognizers"
    and "useless ones" revolved around customizing a basic 
    front-end algorithm (say, cepstra) to work well with a
    particular task and a particular back-end recognition engine.
    Many of these parameterization can't be done well (or at all)
    on the vanilla cepstra representation received by the server --
    it needs to be done as part of the front-end calculations.

    To be specific:

       -- the frame window length
       -- the frame window period (independent of window length)
       -- number and quantization of cepstra
       -- inclusion of C0 (volume) and pitch information
       -- alternative filter-bank spacing (other than mel-spacing)
       -- size of FFT used to compute cepstra on
       -- audio pre-emphasis and DC filtering
       -- use of spectral subtraction, RASTA, and other well-known,
          well-tested noise-reduction techniques, many of which have
          parameters as well

     A packetization that let a server and a handset negotiate a 
     common set of cepstra parameterizations based on the list above,
     falling back on the simplest default if all else fails, probably
     could halve your error rate in the real-world, relative to using
     a vanilla mel-cepstra. In addition, some of these parameterizations
     would serve to reduce the bandwidth for a given performance rate
     (most notably, customizing the number and quantization of the 
      coefficients). 

     I think this sort of scheme is doable, given the maturity of 
     RTP, SIP, and the speech recognition community's front-end lore.

     
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------


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



From daemon@ns.ietf.org  Thu Jan 24 16:07:28 2002
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 QAA05957
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 16:07:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23386
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 16:07:32 -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 QAA23335;
	Thu, 24 Jan 2002 16:07:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23302
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 16:06:58 -0500 (EST)
Received: from snap.CS.Berkeley.EDU (IDENT:root@snap.CS.Berkeley.EDU [128.32.45.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05939
	for <avt@ietf.org>; Thu, 24 Jan 2002 16:06:53 -0500 (EST)
Received: (from lazzaro@localhost)
	by snap.CS.Berkeley.EDU (8.9.3/8.9.3-ZUUL) id NAA02336
	for avt@ietf.org; Thu, 24 Jan 2002 13:06:53 -0800
Date: Thu, 24 Jan 2002 13:06:53 -0800
From: John Lazzaro <lazzaro@CS.Berkeley.EDU>
Message-Id: <200201242106.NAA02336@snap.CS.Berkeley.EDU>
To: avt@ietf.org
Subject: [AVT] Resend of draft-ietf-avt-dsr-00.txt review ...
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



Resending my draft-ietf-avt-dsr-00.txt review -- it looks like my
first attempt to post was mangled (at least it is in the archives.


> Stephen Casner writes:
>
> I have not seen other offers.  Have reviewing arrangements for other
> drafts been made off-list?

Here's my review of:

    Distributed Speech Recognition (draft-ietf-avt-dsr-00.txt)

[1] Spelling errors:

engin --> engine
engins --> engines
increacing --> increasing
recogziers --> recognizers

It looks like engin made it into someone's spell-checker dictionary,
given how many times this misspelling shows up ...


[2] Sentence structure:

  o "encapsulating a front-end signal processing feature streams"

    Plurality issue -- remove the "a".

  o "A solution that combats this uses a scheme called [...]"

    Never use "this" as a noun -- try:

    To address this problem, we use a distributed speech 
    recognition (DSR) architecture.

  o "The remote device processes the speech, compresses, and error protects
    the bitstream, [...]"

    Either remove the comma after "compresses", or add a noun phrase:

    compresses the data, and adds error protection to the bitstream

  o "Therefore, it will be desirable"

    Verb tense problems: you've committed to using present tense in
    this document, so a future-tense sentence like this one is not
    good style -- rewrite. Read through the document front to back
    looking for other future tense sentences, and rewrite them too!
   
  o "frame-pairs"

    Ditch the dash -- pair is the noun, frame is the adjective, the
    two work fine together without needing a dash.

  o "A decreasing number of FPs per payload packet [...]"

    The using of increasing/decreasing is bad form here -- we're not
    talking about dynamically changing the FPs per packet, we're 
    discussing the optimal number of FPs per packet as a static 
    decision. Rewrite.

  o "rises the potential of the loss of a large number"

    Bad English -- try:

    "increases the probability of catastrophic packet loss"

  o "A contiguous segment of DSR frames"

    Try:

    a set DSR frames coding an unbroken speech segment transmitted
    from the terminal to the server

  o "This is a lossy compression, with the output being a frame 
     containing an integer representation of the encoded speech."

    I tried reading this a few times, but I can't see why you'd
    bother noting the coefficients are integers -- I don't know
    of anyone coding mel-cepstra coefficients as floats or char
    strings :-). Delete or rephrase.


[3] IETF issues

   o At the head and the tail of the document, replace the 
     "expires in 6 months" phrase with the actual date of 
     expiration.

   o Someone with more experience in IETF stuff should search
     on RECOMMENDED, SHOULD, and MUST, to make sure each usage
     rises to the level where it deserves the all-caps, RFC-2119
     connotation -- I suspect a few of them are really lower-case
     in reality.

   o The bitfield figures lack titles -- add a "Figure N" and a title
     under each bitfield, and refer to each in the text as "Figure N."


[4] Content -- micro issues

    o Psychologically, its very comforting to see RTP headers on
      the top of payload bitfields -- it reminds people that the
      bitfield shown is the entire payload. So add them to the
      appropriate figures.

    o Explicit comments about the marker bit, timestamp, and 
      sequence number are in order -- even if each comment is 
      "no special usage or semantics", having such a comment
      acts to caution implementors not to do "embrace and extend"
      on the RTP header (the marker bit is always tempting ...). 
      Also, be explicit about the dynamic payload number, to 
      remind implementors the days of static payload numbers are
      over.

    o The packetization has a bunch of implicit decisions in it,
      about where in the transmission chain it makes sense to
      do the obvious "over-the-air" stuff (packing idx's and
      frames into sub-octets, and adding the 4-bit CRCs). By
      putting them in the RTP packet, instead of defining an
      octet-based, non-CRC packetization, the assumption is
      that general-purpose servers doing SR are better at doing
      bit-level ops than the device that interfaces the on-air
      to the first IP link. Specifically:

      [1] not zero-padding each idx coefficient to be 8 bits
      [2] failing [1], not zero-padding each frame or frame pair
          to be octet-aligned.
      [3] including the 4-bit CRC

      are consequences of this decision. Do people in the group
      feel comfortable with this decision?


[5] Content -- macro issues.

    I realize suggestions of the sort I'm about to make are out
    of place this late in the review process -- I'm bringing them
    up to inspire someone else to do a better next-generation 
    packetization, not because I expect the authors to start
    from scratch on this one :-).

    I think defining an unparameterized, plain-vanilla mel-cepstra
    front end is the wrong way to go. Back when I was doing SR
    work, so much of the difference between "usable recognizers"
    and "useless ones" revolved around customizing a basic 
    front-end algorithm (say, cepstra) to work well with a
    particular task and a particular back-end recognition engine.
    Many of these parameterization can't be done well (or at all)
    on the vanilla cepstra representation received by the server --
    it needs to be done as part of the front-end calculations.

    To be specific:

       -- the frame window length
       -- the frame window period (independent of window length)
       -- number and quantization of cepstra
       -- inclusion of C0 (volume) and pitch information
       -- alternative filter-bank spacing (other than mel-spacing)
       -- size of FFT used to compute cepstra on
       -- audio pre-emphasis and DC filtering
       -- use of spectral subtraction, RASTA, and other well-known,
          well-tested noise-reduction techniques, many of which have
          parameters as well

     A packetization that let a server and a handset negotiate a 
     common set of cepstra parameterizations based on the list above,
     falling back on the simplest default if all else fails, probably
     could halve your error rate in the real-world, relative to using
     a vanilla mel-cepstra. In addition, some of these parameterizations
     would serve to reduce the bandwidth for a given performance rate
     (most notably, customizing the number and quantization of the 
      coefficients). 

     I think this sort of scheme is doable, given the maturity of 
     RTP, SIP, and the speech recognition community's front-end lore.

     
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------



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



From daemon@ns.ietf.org  Thu Jan 24 19:28:06 2002
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 TAA10545
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 19:28:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA03928
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 19:28:07 -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 TAA03903;
	Thu, 24 Jan 2002 19:27:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA03872
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 19:27:23 -0500 (EST)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10525
	for <avt@ietf.org>; Thu, 24 Jan 2002 19:27:21 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sj1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id QAA10224; Thu, 24 Jan 2002 16:26:16 -0800 (PST)
Message-Id: <4.1.20020124182541.02ef3750@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 24 Jan 2002 18:25:56 -0600
To: Colin Perkins <csp@isi.edu>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [AVT] Re: Switch to subscriber-only posting? 
Cc: John Lazzaro <lazzaro@CS.Berkeley.EDU>, avt@ietf.org
In-Reply-To: <200201241921.g0OJLG310136@purple.nge.isi.edu>
References: <Your message of "Thu, 24 Jan 2002 11:40:11 CST."             <4.1.20020124113649.013cde88@localhost>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1305514760==_.ALT"
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

--=====================_1305514760==_.ALT
Content-Type: text/plain; charset="us-ascii"


bummer

At 02:21 PM 1/24/2002 -0500, Colin Perkins wrote:
>--> "James M. Polk" writes:
>>At 10:49 AM 1/18/2002 -0800, John Lazzaro wrote:
>>>
>>>> From: Stephen Casner <casner@acm.org>
>>>> Should we change the configuration of this mailing list so that posts
>>>> are only accepted from subscribers?  
>>>
>>>Given that many of the WG mailing lists are under the ietf.org 
>>>umbrella now, it might be worth considering extending posting
>>>rights to subscribed members of related IETF groups -- it   
>>>seems like the most common reason for a non-AVT-subscriber to
>>>post is to forward a discussion from a related WG list, and if
>>>its technically possible to retain this feature it would be good.
>>
>>Chairs -- this suggestion from John above seems like the best of all. Can
this
>>filter be set up to accept messages from members of this list AND from
members
>>of other groups on the same server (ietf.org)? This would allow intermingling
>>between lists -- and that should be encouraged, IMO.
>
>That's not possible with the current setup.
>
>Colin

*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"

James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com
--=====================_1305514760==_.ALT
Content-Type: text/html; charset="us-ascii"

<html><div>bummer</div>
<br>
<div>At 02:21 PM 1/24/2002 -0500, Colin Perkins wrote:</div>
<div>&gt;--&gt; &quot;James M. Polk&quot; writes:</div>
<div>&gt;&gt;At 10:49 AM 1/18/2002 -0800, John Lazzaro wrote:</div>
<div>&gt;&gt;&gt;</div>
<div>&gt;&gt;&gt;&gt; From: Stephen Casner &lt;casner@acm.org&gt;</div>
<div>&gt;&gt;&gt;&gt; Should we change the configuration of this mailing
list so that posts</div>
<div>&gt;&gt;&gt;&gt; are only accepted from subscribers?&nbsp; </div>
<div>&gt;&gt;&gt;</div>
<div>&gt;&gt;&gt;Given that many of the WG mailing lists are under the
ietf.org </div>
<div>&gt;&gt;&gt;umbrella now, it might be worth considering extending
posting</div>
<div>&gt;&gt;&gt;rights to subscribed members of related IETF groups --
it&nbsp;&nbsp; </div>
<div>&gt;&gt;&gt;seems like the most common reason for a
non-AVT-subscriber to</div>
<div>&gt;&gt;&gt;post is to forward a discussion from a related WG list,
and if</div>
<div>&gt;&gt;&gt;its technically possible to retain this feature it would
be good.</div>
<div>&gt;&gt;</div>
<div>&gt;&gt;Chairs -- this suggestion from John above seems like the
best of all. Can this</div>
<div>&gt;&gt;filter be set up to accept messages from members of this
list AND from members</div>
<div>&gt;&gt;of other groups on the same server (ietf.org)? This would
allow intermingling</div>
<div>&gt;&gt;between lists -- and that should be encouraged, IMO.</div>
<div>&gt;</div>
<div>&gt;That's not possible with the current setup.</div>
<div>&gt;</div>
<div>&gt;Colin</div>
<br>

<div align="center">
*************************************<br>
&quot;People generally demand more respect for their own rights than they
are willing to allow for others&quot;<br>
<br>
</div>
James M. Polk<br>
Consulting Engineer<br>
Office of the CTO<br>
<br>
Cisco Systems<br>
2200 East President George Bush Turnpike <br>
Richardson, TX&nbsp; 75082 USA<br>
w) 972.813.5208<br>
f)&nbsp; 972.813.5280<br>
<a href="http://www.cisco.com/" eudora="autourl">www.cisco.com</a></html>

--=====================_1305514760==_.ALT--


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



From daemon@ns.ietf.org  Thu Jan 24 21:02:12 2002
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 VAA11836
	for <avt-archive@odin.ietf.org>; Thu, 24 Jan 2002 21:02:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA07804
	for avt-archive@odin.ietf.org; Thu, 24 Jan 2002 21:02:14 -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 VAA07723;
	Thu, 24 Jan 2002 21:01:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07632
	for <avt@ns.ietf.org>; Thu, 24 Jan 2002 21:01:23 -0500 (EST)
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11817
	for <avt@ietf.org>; Thu, 24 Jan 2002 21:01:19 -0500 (EST)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate4.mot.com (motgate4 2.1) with ESMTP id TAA21253 for <avt@ietf.org>; Thu, 24 Jan 2002 19:01:21 -0700 (MST)]
Received: [from relay2.cig.mot.com (relay2.cig.mot.com [136.182.15.24]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id SAA23536 for <avt@ietf.org>; Thu, 24 Jan 2002 18:50:22 -0700 (MST)]
Received: from quantix20.cig.mot.com (quantix20 [160.47.58.31])
	by relay2.cig.mot.com (8.11.4/8.11.4) with ESMTP id g0P21Ir18714;
	Thu, 24 Jan 2002 20:01:19 -0600 (CST)
Received: from cig.mot.com (d50-384a.cig.mot.com [160.47.56.74])
	by quantix20.cig.mot.com (8.8.8+Sun/8.8.8) with ESMTP id UAA07855;
	Thu, 24 Jan 2002 20:06:06 -0600 (CST)
Message-ID: <3C50BD51.312C4AB6@cig.mot.com>
Date: Thu, 24 Jan 2002 20:05:05 -0600
From: Qiaobing Xie <xieqb@cig.mot.com>
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Lazzaro <lazzaro@CS.Berkeley.EDU>
CC: avt@ietf.org
Subject: Re: [AVT] Review of draft-ietf-avt-dsr-00.txt
References: <200201242026.MAA02195@snap.CS.Berkeley.EDU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

John,

Thanks for the detailed reading. I agree with most of your editorial
suggestions and will improve the text as you've suggested. Please see my
other responses in-line...

-Qiaobing

John Lazzaro wrote:
...snip...
>   o "frame-pairs"
> 
>     Ditch the dash -- pair is the noun, frame is the adjective, the
>     two work fine together without needing a dash.

It is meant to emphasize the term (so that the causal reader won't
misread it as frame and get confused).

...snip...
>     o The packetization has a bunch of implicit decisions in it,
>       about where in the transmission chain it makes sense to
>       do the obvious "over-the-air" stuff (packing idx's and
>       frames into sub-octets, and adding the 4-bit CRCs). By
>       putting them in the RTP packet, instead of defining an
>       octet-based, non-CRC packetization, the assumption is
>       that general-purpose servers doing SR are better at doing
>       bit-level ops than the device that interfaces the on-air
>       to the first IP link. Specifically:
> 
>       [1] not zero-padding each idx coefficient to be 8 bits
>       [2] failing [1], not zero-padding each frame or frame pair
>           to be octet-aligned.
>       [3] including the 4-bit CRC
> 
>       are consequences of this decision. Do people in the group
>       feel comfortable with this decision?

We had similar discussions on this "bitwise vs. octet-aligned" issue
over other payload types (such as AMR) in avt, and there were equally
strong arguments made from both sides. One view to support a more
compact packetization is that, CPUs in modern general purpose servers
are getting more powerful and getting better at bit-level ops and there
is not going to be a big performance difference as they had 10 years
ago. But the over-the-air bandwidth scarcity can only get worse over the
time. 

> 
> [5] Content -- macro issues.
> 
>     I realize suggestions of the sort I'm about to make are out
>     of place this late in the review process -- I'm bringing them
>     up to inspire someone else to do a better next-generation
>     packetization, not because I expect the authors to start
>     from scratch on this one :-).
>
>     I think defining an unparameterized, plain-vanilla mel-cepstra
>     front end is the wrong way to go. Back when I was doing SR
>     work, so much of the difference between "usable recognizers"
>     and "useless ones" revolved around customizing a basic
>     front-end algorithm (say, cepstra) to work well with a
>     particular task and a particular back-end recognition engine.
>     Many of these parameterization can't be done well (or at all)
>     on the vanilla cepstra representation received by the server --
>     it needs to be done as part of the front-end calculations.

A lot of SR people in ETSI AURARO project probably will not agree on
your view about the "unparameterized, plain-vanilla mel-cepstra"
front-end. In the contrary, there is solid consensus in ETSI that this
front-end is very acceptable. As you noted, however, this is out of the
scope of IETF AVT.

But you do have a good point about the future front-end types. In the
draft, we've anticipated the need of accommodating the future front-end
types and have included the following paragraph in section 5:

======
In this memo, we only define the frame-pair formats that MUST be used
when the ESTI ES 201 108 Front-end Codec [ES201108] is used. Frame-
pair formats for future DSR front-end codecs may be defined in
separate IETF documents. 
=====

In fact, I know there are research works going on in some private
companies as well as in ETSI to define more advanced front-end types.
Our view is that, the definition of front-end types is out of scope of
IETF avt working group. But once the new front-end type reaches its
maturity and becomes an industrial standard, a new frame-pair will be
created in IETF to accommodate it (if the existing one(s) is not good
enough) and a new MIME parameter value will be registered with IANA.

>     To be specific:
> 
>        -- the frame window length
>        -- the frame window period (independent of window length)
>        -- number and quantization of cepstra
>        -- inclusion of C0 (volume) and pitch information
>        -- alternative filter-bank spacing (other than mel-spacing)
>        -- size of FFT used to compute cepstra on
>        -- audio pre-emphasis and DC filtering
>        -- use of spectral subtraction, RASTA, and other well-known,
>           well-tested noise-reduction techniques, many of which have
>           parameters as well
> 
>      A packetization that let a server and a handset negotiate a
>      common set of cepstra parameterizations based on the list above,
>      falling back on the simplest default if all else fails, probably
>      could halve your error rate in the real-world, relative to using
>      a vanilla mel-cepstra. In addition, some of these parameterizations
>      would serve to reduce the bandwidth for a given performance rate
>      (most notably, customizing the number and quantization of the
>       coefficients).
> 
>      I think this sort of scheme is doable, given the maturity of
>      RTP, SIP, and the speech recognition community's front-end lore.

Yes, I tend to agree with you. But I think the key is to first have the
SR community/industry to reach its consensus on which and how best these
advanced parameterizations should be standardized. At that point, it
should be trivial to open new MIME params or define new frame-pairs to
support these parameterizations over an RTP session. 

> 
> 
> -------------------------------------------------------------------------
> John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
> lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
> -------------------------------------------------------------------------
> 
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Fri Jan 25 06:52:59 2002
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 GAA29422
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 06:52:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA10047
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 06:53:01 -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 GAA09988;
	Fri, 25 Jan 2002 06:52:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA09957
	for <avt@optimus.ietf.org>; Fri, 25 Jan 2002 06:51:58 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29194;
	Fri, 25 Jan 2002 06:51:55 -0500 (EST)
Message-Id: <200201251151.GAA29194@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: avt@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 25 Jan 2002 06:51:55 -0500
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-cn-05.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.

	Title		: RTP Payload for Comfort Noise
	Author(s)	: R. Zopf
	Filename	: draft-ietf-avt-rtp-cn-05.txt
	Pages		: 8
	Date		: 24-Jan-02
	
This document describes an RTP [2] payload format for transporting
comfort noise (CN).  The CN payload type is primarily for use with
audio codecs that do not support comfort noise as part of the codec
itself such as ITU-T Recommendations G.711 [3], G.726 [4], G.727
[5], G.728 [6], and G.722 [7].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-cn-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-avt-rtp-cn-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-cn-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020124133321.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-cn-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtp-cn-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020124133321.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From daemon@ns.ietf.org  Fri Jan 25 14:34:07 2002
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 OAA12144
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 14:34:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA05256
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 14:34:09 -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 OAA05136;
	Fri, 25 Jan 2002 14:31:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05105
	for <avt@ns.ietf.org>; Fri, 25 Jan 2002 14:31:46 -0500 (EST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12103
	for <avt@ietf.org>; Fri, 25 Jan 2002 14:31:42 -0500 (EST)
Received: from [63.105.122.236] ([63.105.122.236] verified)
  by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP id 1236913; Fri, 25 Jan 2002 14:31:40 -0500
User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630)
Date: Fri, 25 Jan 2002 14:31:44 -0500
Subject: Re: [AVT] Switch to subscriber-only posting?
From: Marshall Eubanks <tme@multicasttech.com>
To: Stephen Casner <casner@acm.org>, AVT WG <avt@ietf.org>
Message-ID: <B8771CCF.42D8%tme@multicasttech.com>
In-Reply-To: <20020124103905.P4441-100000@ash.packetdesign.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

> One week ago I asked:
> 
>> Should we change the configuration of this mailing list so that posts
>> are only accepted from subscribers?  That is a pretty effective
>> technique for reducing spam.  The downside is that it is inconvenient
>> for people who use multiple mailboxes.
> 
> Nobody objected to this change, and many emphatically supported it.
> The only concern was that MIDCOM had tried this and it turned into a
> long discussion on that list with the eventual result that it was
> turned off.  In reading that discussion, it seems that the objections
> arose because the poster received an autoreply saying the mail was
> rejected, and that the wording of that autoreply was poorly chosen.
> 
> That objection can be avoided by not sending an autoreply and relying
> on the list administrators (that would be your faithful WG chairs) to
> pass or reject the messages.  I was hoping to avoid that work (so I
> wouldn't have to look at the spam, either), but it looks like that is
> not acceptable.
> 


The trouble is that, if you use aliases and multiple e-mail platforms, you
can be registered under one name and use another.

(In my case, tme is aliased to marshall_eubanks.)

So, if you are using a web browser based e-mail, it may change how your
name appears to the listserve, and messages may bounce.

802.11b is reducing the frequency of this, but...

What I tell people is that you should see to your messages sent to the list.
If you do not see a message you sent after a reasonable interval (12 hours),
then there is an error.

This needs to be stated somewhere on the web page or an IETF mail list
trouble page...

Marshall

> John Lazzaro made an excellent suggestion that posting by any ietf
> list subscriber should be automatically allowed.  I asked Steve Coya
> and Stanley Weilnau if the IETF mailman system coud be set up to do
> this, and got a negative response.  Stanley seems to think that having
> the admin do filtering is sufficient.  I still think this is an idea
> that should be pursued, but it looks like a little programming will be
> required.
> 
> So, we will change the list to subscriber-only, using admin approval
> and no autoreply on non-subscriber bounces.
> 
> PLEASE, any of you who post from an address other than the one that is
> subscribed:  you can subscribe from an alternate address and select no
> delivery to that address.  To do this, first subscribe the alternate
> address via email or the web link:
> 
> https://www1.ietf.org/mailman/listinfo/avt
> 
> Then, after the subscription is established, go back to that web page
> and enter the alternate address next to the "Edit Options" button at
> the bottom of the page and click that button.  On the options page,
> click the "Disable mail delivery" checkbox, enter the password that
> you entered for the alternate address into the box at the bottom of
> the page, and click "Submit My Changes".
> 
> Your password is mailed to you monthly.  If you forget it, you can
> click the "Email My Password To Me" button in the middle of the
> options page.
> -- Steve
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

-- 
                                 Regards
                                 Marshall Eubanks


T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624            Fax     : 703-293-9609
e-mail : tme@multicasttech.com

 Test your network for multicast : http://www.multicasttech.com/mt/
 Check the status of multicast in real time :
 http://www.multicasttech.com/status/index.html


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



From daemon@ns.ietf.org  Fri Jan 25 14:34:15 2002
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 OAA12161
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 14:34:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA05280
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 14:34:17 -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 OAA05175;
	Fri, 25 Jan 2002 14:31:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05142
	for <avt@ns.ietf.org>; Fri, 25 Jan 2002 14:31:56 -0500 (EST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12106
	for <avt@ietf.org>; Fri, 25 Jan 2002 14:31:52 -0500 (EST)
Received: from [63.105.122.236] ([63.105.122.236] verified)
  by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP id 1236914; Fri, 25 Jan 2002 14:31:50 -0500
User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630)
Date: Fri, 25 Jan 2002 14:31:54 -0500
Subject: Re: [AVT] Switch to subscriber-only posting?
From: Marshall Eubanks <tme@multicasttech.com>
To: Stephen Casner <casner@acm.org>, AVT WG <avt@ietf.org>
Message-ID: <B8771CCF.42D8%tme@multicasttech.com>
In-Reply-To: <20020124103905.P4441-100000@ash.packetdesign.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

> One week ago I asked:
> 
>> Should we change the configuration of this mailing list so that posts
>> are only accepted from subscribers?  That is a pretty effective
>> technique for reducing spam.  The downside is that it is inconvenient
>> for people who use multiple mailboxes.
> 
> Nobody objected to this change, and many emphatically supported it.
> The only concern was that MIDCOM had tried this and it turned into a
> long discussion on that list with the eventual result that it was
> turned off.  In reading that discussion, it seems that the objections
> arose because the poster received an autoreply saying the mail was
> rejected, and that the wording of that autoreply was poorly chosen.
> 
> That objection can be avoided by not sending an autoreply and relying
> on the list administrators (that would be your faithful WG chairs) to
> pass or reject the messages.  I was hoping to avoid that work (so I
> wouldn't have to look at the spam, either), but it looks like that is
> not acceptable.
> 


The trouble is that, if you use aliases and multiple e-mail platforms, you
can be registered under one name and use another.

(In my case, tme is aliased to marshall_eubanks.)

So, if you are using a web browser based e-mail, it may change how your
name appears to the listserve, and messages may bounce.

802.11b is reducing the frequency of this, but...

What I tell people is that you should see to your messages sent to the list.
If you do not see a message you sent after a reasonable interval (12 hours),
then there is an error.

This needs to be stated somewhere on the web page or an IETF mail list
trouble page...

Marshall

> John Lazzaro made an excellent suggestion that posting by any ietf
> list subscriber should be automatically allowed.  I asked Steve Coya
> and Stanley Weilnau if the IETF mailman system coud be set up to do
> this, and got a negative response.  Stanley seems to think that having
> the admin do filtering is sufficient.  I still think this is an idea
> that should be pursued, but it looks like a little programming will be
> required.
> 
> So, we will change the list to subscriber-only, using admin approval
> and no autoreply on non-subscriber bounces.
> 
> PLEASE, any of you who post from an address other than the one that is
> subscribed:  you can subscribe from an alternate address and select no
> delivery to that address.  To do this, first subscribe the alternate
> address via email or the web link:
> 
> https://www1.ietf.org/mailman/listinfo/avt
> 
> Then, after the subscription is established, go back to that web page
> and enter the alternate address next to the "Edit Options" button at
> the bottom of the page and click that button.  On the options page,
> click the "Disable mail delivery" checkbox, enter the password that
> you entered for the alternate address into the box at the bottom of
> the page, and click "Submit My Changes".
> 
> Your password is mailed to you monthly.  If you forget it, you can
> click the "Email My Password To Me" button in the middle of the
> options page.
> -- Steve
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

-- 
                                 Regards
                                 Marshall Eubanks


T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624            Fax     : 703-293-9609
e-mail : tme@multicasttech.com

 Test your network for multicast : http://www.multicasttech.com/mt/
 Check the status of multicast in real time :
 http://www.multicasttech.com/status/index.html


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



From daemon@ns.ietf.org  Fri Jan 25 14:47:37 2002
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 OAA12433
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 14:47:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA05957
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 14:47:40 -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 OAA05846;
	Fri, 25 Jan 2002 14:45:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01420
	for <avt@optimus.ietf.org>; Fri, 25 Jan 2002 03:03:39 -0500 (EST)
Received: from mailcity.com (fes2.whowhere.com [209.185.123.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA26841
	for <avt@ietf.org>; Fri, 25 Jan 2002 03:03:37 -0500 (EST)
Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Fri Jan 25 00:02:54 2002
To: avt@ietf.org, rtp@vovida.org
Date: Fri, 25 Jan 2002 00:02:54 -0800
From: "sharad saxena" <sharad.saxena@lycos.com>
Message-ID: <DFLNDJDEHKICCBAA@mailcity.com>
Mime-Version: 1.0
X-Sent-Mail: off
Reply-To: sharad.saxena@lycos.com
X-Mailer: MailCity Service
X-Priority: 3
X-Sender-Ip: 164.164.31.3
Organization: Lycos Mail  (http://mail.lycos.com:80)
Content-Type: text/plain; charset=us-ascii
Content-Language: en
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] dynamic payload
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
Content-Transfer-Encoding: 7bit

hi all

  I am a newbie in rtp and while going through the documents(rfcs), I have come across abt dynamic payload type. Can any one tell me what is the advantage of having dynamic payload type and brief explaination abt how to use it will be very helpful.

regs
saxena 





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



From daemon@ns.ietf.org  Fri Jan 25 15:35:06 2002
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 PAA13545
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 15:35:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA08492
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 15:35:09 -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 PAA08379;
	Fri, 25 Jan 2002 15:32:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA06214
	for <avt@ns.ietf.org>; Fri, 25 Jan 2002 14:54:13 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12665
	for <avt@ietf.org>; Fri, 25 Jan 2002 14:54:09 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0PJrWp63606;
	Fri, 25 Jan 2002 11:53:32 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Fri, 25 Jan 2002 11:55:57 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Marshall Eubanks <tme@multicasttech.com>
cc: AVT WG <avt@ietf.org>
Subject: Re: [AVT] Switch to subscriber-only posting?
In-Reply-To: <B8771CCF.42D8%tme@multicasttech.com>
Message-ID: <20020125115027.L6070-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

Marshall,

> The trouble is that, if you use aliases and multiple e-mail platforms, you
> can be registered under one name and use another.
>
> (In my case, tme is aliased to marshall_eubanks.)

That can be accommodated by subscribing all your aliases to the list
but setting the "Disable mail delivery" option for all but one of them
so you only get one copy, as I explained in the bottom part of my message.

> So, if you are using a web browser based e-mail, it may change how your
> name appears to the listserve, and messages may bounce.

Are you saying that each time you use it, the name on mail you sent is
different from previous times?  That we can't handle.  But if the name
is the same every time you use a particular web browser email service,
then you can sign up for the names associated with all the services
you need to use.

I'll include the part of my message about multiple signups:

> > PLEASE, any of you who post from an address other than the one that is
> > subscribed:  you can subscribe from an alternate address and select no
> > delivery to that address.  To do this, first subscribe the alternate
> > address via email or the web link:
> >
> > https://www1.ietf.org/mailman/listinfo/avt
> >
> > Then, after the subscription is established, go back to that web page
> > and enter the alternate address next to the "Edit Options" button at
> > the bottom of the page and click that button.  On the options page,
> > click the "Disable mail delivery" checkbox, enter the password that
> > you entered for the alternate address into the box at the bottom of
> > the page, and click "Submit My Changes".
> >
> > Your password is mailed to you monthly.  If you forget it, you can
> > click the "Email My Password To Me" button in the middle of the
> > options page.
							-- Steve



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



From daemon@ns.ietf.org  Fri Jan 25 16:36:34 2002
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 QAA14948
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 16:36:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA11924
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 16:36:37 -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 QAA11812;
	Fri, 25 Jan 2002 16:34:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10522
	for <avt@ns.ietf.org>; Fri, 25 Jan 2002 16:24:14 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14693
	for <avt@ietf.org>; Fri, 25 Jan 2002 16:24:09 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0PLLFp66404;
	Fri, 25 Jan 2002 13:21:15 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Fri, 25 Jan 2002 13:23:39 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: sharad saxena <sharad.saxena@lycos.com>
cc: <avt@ietf.org>, <rtp@vovida.org>
Subject: Re: [AVT] dynamic payload
In-Reply-To: <DFLNDJDEHKICCBAA@mailcity.com>
Message-ID: <20020125132051.I6070-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Fri, 25 Jan 2002, sharad saxena wrote:

>   I am a newbie in rtp and while going through the documents(rfcs),
>   I have come across abt dynamic payload type. Can any one tell me
>   what is the advantage of having dynamic payload type and brief
>   explaination abt how to use it will be very helpful.

I believe the motivation for using dynamic paylod types is clearly
explained in

http://www.ietf.org/internet-drafts/draft-ietf-avt-profile-new-12.txt

How to define dynamic payload types using the rtpmap attribute in SDP
is explained in RFC2327.
							-- Steve



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



From daemon@ns.ietf.org  Fri Jan 25 16:38:42 2002
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 QAA14997
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 16:38:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA12157
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 16:38:45 -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 QAA11960;
	Fri, 25 Jan 2002 16:37:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11537
	for <avt@ns.ietf.org>; Fri, 25 Jan 2002 16:30:45 -0500 (EST)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14840
	for <avt@ietf.org>; Fri, 25 Jan 2002 16:30:40 -0500 (EST)
Received: from mira-sjc5-9.cisco.com (mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id g0PLUCI12081;
	Fri, 25 Jan 2002 13:30:12 -0800 (PST)
Received: from kimle-lnx.cisco.com (kimle-lnx.cisco.com [128.107.140.126])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ABW84151;
	Fri, 25 Jan 2002 13:30:21 -0800 (PST)
From: Kim Le <kimle@cisco.com>
To: sharad.saxena@lycos.com
Cc: avt@ietf.org, rtp@vovida.org
In-Reply-To: <DFLNDJDEHKICCBAA@mailcity.com>
References: <DFLNDJDEHKICCBAA@mailcity.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0.1 
Date: 25 Jan 2002 23:30:11 +0200
Message-Id: <1011994211.19087.12.camel@kimle-lnx.cisco.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [AVT] Re: [Rtp] dynamic payload
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
Content-Transfer-Encoding: 7bit

Dynamic payload is for any non standard data, but both sender and
reciever must agree on a number.

Out of band DTMF is sent over a dynamic payload type 101 or something
like that.

-Kim


On Fri, 2002-01-25 at 10:02, sharad saxena wrote:
> hi all
> 
>   I am a newbie in rtp and while going through the documents(rfcs), I have come across abt dynamic payload type. Can any one tell me what is the advantage of having dynamic payload type and brief explaination abt how to use it will be very helpful.
> 
> regs
> saxena 
> 
> 
> 
> _______________________________________________
> rtp mailing list
> rtp@vovida.org
> http://www.vovida.org/mailman/listinfo/rtp




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



From daemon@ns.ietf.org  Fri Jan 25 17:04:10 2002
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 RAA15606
	for <avt-archive@odin.ietf.org>; Fri, 25 Jan 2002 17:04:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA13586
	for avt-archive@odin.ietf.org; Fri, 25 Jan 2002 17:04:14 -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 RAA13515;
	Fri, 25 Jan 2002 17:02:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA13484
	for <avt@ns.ietf.org>; Fri, 25 Jan 2002 17:02:27 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15566
	for <avt@ietf.org>; Fri, 25 Jan 2002 17:02:22 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0PM1lp67789;
	Fri, 25 Jan 2002 14:01:47 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Fri, 25 Jan 2002 14:04:08 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Kim Le <kimle@cisco.com>
cc: <sharad.saxena@lycos.com>, <avt@ietf.org>, <rtp@vovida.org>
Subject: Re: [AVT] Re: [Rtp] dynamic payload
In-Reply-To: <1011994211.19087.12.camel@kimle-lnx.cisco.com>
Message-ID: <20020125134804.O6070-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On 25 Jan 2002, Kim Le wrote:

> Dynamic payload is for any non standard data, but both sender and
> reciever must agree on a number.

The phrase "non standard data" may be misleading.  All new payload
formats, including those which become standards, must use dynamic
payload types because static payload type numbers are no longer being
assigned.

> Out of band DTMF is sent over a dynamic payload type 101 or something
> like that.

When DTMF signals are sent (in band) over RTP using RFC 2833, a
dynamic paylod type will be used, but the chosen number is dynamic, it
is not always 101 or any other fixed number.  That is, I should say,
in a proper implementation.
							-- Steve


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



From daemon@optimus.ietf.org  Sat Jan 26 10:49:34 2002
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 KAA08102
	for <avt-archive@odin.ietf.org>; Sat, 26 Jan 2002 10:49:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA26001
	for avt-archive@odin.ietf.org; Sat, 26 Jan 2002 10:49:37 -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 KAA25955;
	Sat, 26 Jan 2002 10:47:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA25924
	for <avt@optimus.ietf.org>; Sat, 26 Jan 2002 10:47:39 -0500 (EST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08090
	for <avt@ietf.org>; Sat, 26 Jan 2002 10:47:35 -0500 (EST)
Received: from [165.247.90.194] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 1237386; Sat, 26 Jan 2002 10:47:35 -0500
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [AVT] Switch to subscriber-only posting?
To: Stephen Casner <casner@acm.org>,
        Marshall Eubanks 
 <tme@multicasttech.com>
Cc: AVT WG <avt@ietf.org>
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Sat, 26 Jan 2002 10:47:35 -0500
Message-ID: <web-1237386@multicasttech.com>
In-Reply-To: <20020125115027.L6070-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
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
Content-Transfer-Encoding: 8bit

On Fri, 25 Jan 2002 11:55:57 -0800 (PST)
 Stephen Casner <casner@acm.org> wrote:
> Marshall,
> 
> > The trouble is that, if you use aliases and multiple
> e-mail platforms, you
> > can be registered under one name and use another.
> >
> > (In my case, tme is aliased to marshall_eubanks.)
> 
> That can be accommodated by subscribing all your aliases
> to the list
> but setting the "Disable mail delivery" option for all
> but one of them
> so you only get one copy, as I explained in the bottom
> part of my message.
> 
 
Dear Stephen;

    That is of course what I do, forced by circumstances. At
a recent conference, I used a web browser based emailer to
send some messages (to msec). These bounced because that
emailer treated aliases differently.

    Because msec had an autoreply, I was able to debug and
fix this in a few minutes. I just don't want people to have
their messages disappear into the ether without a clue.

     Again, if you are not going to have an autoreply, the
web site should make it clear that you should see a copy of 
your message, and failure to do so is an error.

    BTW, I like the idea of allowing cross posts between
IETF list members. More than once I have responded to a post
sent to more than one list, only to have the "other" list
post bounce, as I was not so subscribed.

             Marshall

> > So, if you are using a web browser based e-mail, it may
> change how your
> > name appears to the listserve, and messages may bounce.
> 
> Are you saying that each time you use it, the name on
> mail you sent is
> different from previous times?  That we can't handle.
> But if the name
> is the same every time you use a particular web browser
> email service,
> then you can sign up for the names associated with all
> the services
> you need to use.
> 
> I'll include the part of my message about multiple
> signups:
> 
> > > PLEASE, any of you who post from an address other
> than the one that is
> > > subscribed:  you can subscribe from an alternate
> address and select no
> > > delivery to that address.  To do this, first
> subscribe the alternate
> > > address via email or the web link:
> > >
> > > https://www1.ietf.org/mailman/listinfo/avt
> > >
> > > Then, after the subscription is established, go back
> to that web page
> > > and enter the alternate address next to the "Edit
> Options" button at
> > > the bottom of the page and click that button.  On the
> options page,
> > > click the "Disable mail delivery" checkbox, enter the
> password that
> > > you entered for the alternate address into the box at
> the bottom of
> > > the page, and click "Submit My Changes".
> > >
> > > Your password is mailed to you monthly.  If you
> forget it, you can
> > > click the "Email My Password To Me" button in the
> middle of the
> > > options page.
> 							-- Steve
> 
> 
> 
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Sun Jan 27 16:51:03 2002
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 QAA03846
	for <avt-archive@odin.ietf.org>; Sun, 27 Jan 2002 16:51:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA26768
	for avt-archive@odin.ietf.org; Sun, 27 Jan 2002 16:51:05 -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 QAA26711;
	Sun, 27 Jan 2002 16:49:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26680
	for <avt@optimus.ietf.org>; Sun, 27 Jan 2002 16:49:35 -0500 (EST)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03833
	for <avt@ietf.org>; Sun, 27 Jan 2002 16:49:31 -0500 (EST)
Received: from tzi.uni-bremen.de (root@localhost [127.0.0.1])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g0RLn9407051;
	Sun, 27 Jan 2002 22:49:09 +0100 (MET)
Message-ID: <3C5475C0.FE5D0CCF@tzi.uni-bremen.de>
Date: Sun, 27 Jan 2002 22:48:48 +0100
From: Joerg Ott <jo@tzi.uni-bremen.de>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Casner <casner@acm.org>
CC: "Even ,Roni" <roni.even@polycom.co.il>, "'avt@ietf.org'" <avt@ietf.org>
Subject: Re: [AVT] comments on draft-ietf-avp-rtcp-feedback-01.txt
References: <20020107195811.B71614-100000@ash.packetdesign.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Roni,

finally, a bit more of a reply:

> > 1. In section 6.3 the text is "AVPF entities MUST include Generic INFO
> > messages along with any payload-specific ones in compound RTCP packets
> > (early as well as  regularly scheduled ones). "  This means that if an
> > encoder is capable of supporting "nack" it needs to support generic info.
> > The capability to support generic INFO is not explained in 4.2. In 6.2 it
> > says that "two general purpose transport layer feedback..." but three are
> > listed. In 6.2.3 it states that "The Generic INFO packet MUST only be used
> > in conjunction with an application-specific feedback message. " which
> > contradict the above text in 6.3.
> 
> It was resolved at the meeting that Generic INFO will be eliminated.
> It was an attempt to fix a problem but it doesn't help.

Yes.  This has been removed from the spec.  Some further explanatory text
regarding feedback collisions will be added.

> > 2. The document leaves open the issue of what the senders should do with the
> > feedback. In the video implementations today we see two kind of feedbacks,
> > between send and receiver of media, commands and indications. My
> > understanding of the nack params (PLI and SLI) is that they are similar to
> > the commands, the preferred mode is for them to cause new intra picture or
> > MB. This params are for general video media and not for specific codec. The
> > indications for specific codec are left to the application layer feedback as
> > described in section 6.4. I suggest that the last sentence in 4.2 will be
> > changed to  "It is up to the recipients whether or not they send feedback
> > information and up to the sender(s) to make use of feedback provided unless
> > an action is required by the specific feedback message." The text in 6.3
> > will state that PLI and SLI will cause fast updates from the sender. This
> > will help with having a consistent response between sender and receiver.
> 
> I don't object to your sentence, but the requirement for action is not
> specified by this profile, rather by the codec document which defines
> the feedback information to be carried with the application-specific
> feedback message of this profile.

Right.  In particular, we cannot mandate a certain behavior in response to a
single message at the sender since, in total, such an action (e.g. fast update)
may interfere with the goal congestion control.  It needs to be determined
individually per application, session, and sender what the appropriate actions
would be.  Video coding standards such as H.263 specify how to deal with 
feedback, so there is no need to replicate this here.

> > 3. In order to be able to use the messages in video switching scenarios we
> > need in 6.3 another payload specific message which is PIZ (Picture Freeze).
> > This is needed for completeness. Video switch involves freeze and fast
> > update and since we have here fast update it is better to have the full
> > support.

This is not really feedback as the remainder of the document addresses it.
Isn't this a control message sent in the same direction as the video stream
(rather than in the opposite direction) and hence it is something to be
conceptually included in an SR rather than an RR message.  Apparently, there
is some use to this message but in my understanding it does not really
belong to the feedback concept; so where would one put it?  It probably
falls more or less into the category of general control commands that are
synch'ed with a media stream's tinming.

> >
> > 4. For information purpose, we have today in video codec specific
> > application the following indications used for resilience support, lost
> > picture and lost partial picture for H.263 annex U & W. Not decoded MB for
> > H.263 appendix I and video bad MB to let the encoder know that those MBs
> > cannot be used for prediction.
> 
> An email from Kris Huber today was essentially asking about the same thing.

If you could provide me with some wording and the necessary bits I'd be
happy to include these in the respective section of the draft.

> > 5. In section 4.3 the references to other sections like in the description
> > of pli, sli and rpsi are not correct.

Oops, at some time in the past, automated section references got messed up
and I went to manual updating.  Will fix this in the next revision of the
draft (coming soon).

Thanks for pointing this out!

Joerg

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



From daemon@optimus.ietf.org  Mon Jan 28 01:27:19 2002
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 BAA10902
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 01:27:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA22374
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 01:27:19 -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 BAA22334;
	Mon, 28 Jan 2002 01:26:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA22306
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 01:26:18 -0500 (EST)
Received: from accord-ntsrv3.accord-domain ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10892
	for <avt@ietf.org>; Mon, 28 Jan 2002 01:26:16 -0500 (EST)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <DGHK2Y91>; Mon, 28 Jan 2002 08:26:05 +0200
Message-ID: <B2518D608282D511BEA400508BBB91480AEF50@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, Stephen Casner <casner@acm.org>
Cc: "Even, Roni" <roni.even@polycom.co.il>, "'avt@ietf.org'"
	 <avt@ietf.org>,
        "Stephan Wenger (E-mail)" <stewe@cs.tu-berlin.de>
Subject: RE: [AVT] comments on draft-ietf-avp-rtcp-feedback-01.txt
Date: Mon, 28 Jan 2002 08:26:04 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
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

Hi Joerg,

About fastupdate in item 2. The reason for fastupdate request from the
receiver is done due to lost synchronization that can happen due to packet
loss or change of received video by the receiver. This is the general
situation and is not dependent on H.261 or H.263 or any specific annex. This
should be a request for action. the indications that I mentioned in item 4
are codec dependent and are left for the sender to decide what to do. I
would like to have PLI and SLI serve as fast update causing an intra frame.
As for item 4 I will send a suggested text during the week
Thanks
Roni

-----Original Message-----
From: Joerg Ott [mailto:jo@tzi.uni-bremen.de]
Sent: Sunday, January 27, 2002 11:49 PM
To: Stephen Casner
Cc: Even ,Roni; 'avt@ietf.org'
Subject: Re: [AVT] comments on draft-ietf-avp-rtcp-feedback-01.txt


Roni,

finally, a bit more of a reply:

> > 1. In section 6.3 the text is "AVPF entities MUST include Generic INFO
> > messages along with any payload-specific ones in compound RTCP packets
> > (early as well as  regularly scheduled ones). "  This means that if an
> > encoder is capable of supporting "nack" it needs to support generic
info.
> > The capability to support generic INFO is not explained in 4.2. In 6.2
it
> > says that "two general purpose transport layer feedback..." but three
are
> > listed. In 6.2.3 it states that "The Generic INFO packet MUST only be
used
> > in conjunction with an application-specific feedback message. " which
> > contradict the above text in 6.3.
> 
> It was resolved at the meeting that Generic INFO will be eliminated.
> It was an attempt to fix a problem but it doesn't help.

Yes.  This has been removed from the spec.  Some further explanatory text
regarding feedback collisions will be added.

> > 2. The document leaves open the issue of what the senders should do with
the
> > feedback. In the video implementations today we see two kind of
feedbacks,
> > between send and receiver of media, commands and indications. My
> > understanding of the nack params (PLI and SLI) is that they are similar
to
> > the commands, the preferred mode is for them to cause new intra picture
or
> > MB. This params are for general video media and not for specific codec.
The
> > indications for specific codec are left to the application layer
feedback as
> > described in section 6.4. I suggest that the last sentence in 4.2 will
be
> > changed to  "It is up to the recipients whether or not they send
feedback
> > information and up to the sender(s) to make use of feedback provided
unless
> > an action is required by the specific feedback message." The text in 6.3
> > will state that PLI and SLI will cause fast updates from the sender.
This
> > will help with having a consistent response between sender and receiver.
> 
> I don't object to your sentence, but the requirement for action is not
> specified by this profile, rather by the codec document which defines
> the feedback information to be carried with the application-specific
> feedback message of this profile.

Right.  In particular, we cannot mandate a certain behavior in response to a
single message at the sender since, in total, such an action (e.g. fast
update)
may interfere with the goal congestion control.  It needs to be determined
individually per application, session, and sender what the appropriate
actions
would be.  Video coding standards such as H.263 specify how to deal with 
feedback, so there is no need to replicate this here.

> > 3. In order to be able to use the messages in video switching scenarios
we
> > need in 6.3 another payload specific message which is PIZ (Picture
Freeze).
> > This is needed for completeness. Video switch involves freeze and fast
> > update and since we have here fast update it is better to have the full
> > support.

This is not really feedback as the remainder of the document addresses it.
Isn't this a control message sent in the same direction as the video stream
(rather than in the opposite direction) and hence it is something to be
conceptually included in an SR rather than an RR message.  Apparently, there
is some use to this message but in my understanding it does not really
belong to the feedback concept; so where would one put it?  It probably
falls more or less into the category of general control commands that are
synch'ed with a media stream's tinming.

> >
> > 4. For information purpose, we have today in video codec specific
> > application the following indications used for resilience support, lost
> > picture and lost partial picture for H.263 annex U & W. Not decoded MB
for
> > H.263 appendix I and video bad MB to let the encoder know that those MBs
> > cannot be used for prediction.
> 
> An email from Kris Huber today was essentially asking about the same
thing.

If you could provide me with some wording and the necessary bits I'd be
happy to include these in the respective section of the draft.

> > 5. In section 4.3 the references to other sections like in the
description
> > of pli, sli and rpsi are not correct.

Oops, at some time in the past, automated section references got messed up
and I went to manual updating.  Will fix this in the next revision of the
draft (coming soon).

Thanks for pointing this out!

Joerg

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



From daemon@optimus.ietf.org  Mon Jan 28 04:21:54 2002
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 EAA21167
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 04:21:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA29381
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 04:21:56 -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 EAA29366;
	Mon, 28 Jan 2002 04:21:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA29335
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 04:21:20 -0500 (EST)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21147
	for <avt@ietf.org>; Mon, 28 Jan 2002 04:21:17 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id KAA02658
	for <avt@ietf.org>; Mon, 28 Jan 2002 10:21:13 +0100 (MET)
Received: from mchh9eea.mchh.siemens.de (mchh9eea.mchh.siemens.de [139.21.204.218])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id KAA24392
	for <avt@ietf.org>; Mon, 28 Jan 2002 10:21:13 +0100 (MET)
Received: by mchh9eea.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <D3RL6G3X>; Mon, 28 Jan 2002 10:19:35 +0100
Message-ID: <07B0CDE3B76AD31190F700508B5D5D1DDF5533@mchg9eba.mchh.siemens.de>
From: Faerber Tobias ICM MP PO8 RD MCH83 <Tobias.Faerber@mch.siemens.de>
To: AVT WG <avt@ietf.org>
Date: Mon, 28 Jan 2002 10:21:11 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [AVT] Question on AMR PL-format: CRC building
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

In case there is a NO_DATA frame within a RTP payload containing several 
AMR frames, e.g. (7,7,8,15,15,7), and CRC bits are transmitted, is there 
a CRC entry for the NO_DATA frames as well? I could not find anything in 
draft-ietf-avt-rtp-amr-10.txt on this. In my opinion it would make not 
much sense to send CRC bits for NO_DATA frames, as there is nothing to 
protect and they would just have to be 0's. From the PT entries you 
would be able to associate the right CRC bits to the data containing 
frames. However, this would have to be specified clearly, since it 
cannot easily be seen from the payload contents which method has been 
used.



----------------------------------------------------------------------------
-------
 Faerber Tobias		Siemens AG
----------------------------------------------------------------------------
-------

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



From daemon@optimus.ietf.org  Mon Jan 28 04:50:57 2002
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 EAA21430
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 04:50:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA00708
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 04:50:59 -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 EAA00673;
	Mon, 28 Jan 2002 04:50:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA00644
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 04:50:22 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21424
	for <avt@ietf.org>; Mon, 28 Jan 2002 04:50:18 -0500 (EST)
From: ari.lakaniemi@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0S9oNt14231
	for <avt@ietf.org>; Mon, 28 Jan 2002 11:50:23 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58b9572c97ac158f22077@esvir02nok.ntc.nokia.com>;
 Mon, 28 Jan 2002 11:50:20 +0200
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Mon, 28 Jan 2002 11:50:17 +0200
Received: from trebe004.NOE.Nokia.com ([172.22.232.177]) by esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 28 Jan 2002 11:50:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [AVT] Question on AMR PL-format: CRC building
Date: Mon, 28 Jan 2002 11:50:16 +0200
Message-ID: <481D6FFB3BD60E4CB590F39C59098400A430D6@trebe004.NOE.Nokia.com>
Thread-Topic: [AVT] Question on AMR PL-format: CRC building
Thread-Index: AcGn3TMKL/YBggvfRkaEw0fLWRo1kwAAvDMw
To: <Tobias.Faerber@mch.siemens.de>, <avt@ietf.org>
X-OriginalArrivalTime: 28 Jan 2002 09:50:17.0110 (UTC) FILETIME=[30C9DB60:01C1A7E1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA00645
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
Content-Transfer-Encoding: 8bit

hello Tobias,

I agree with you, there should not be CRC bits for NO_DATA frames.
Actually this is already specified in the draft, in section 2.3:

"
   FT (4 bits): Frame type indicator, indicating the AMR or AMR-WB
   speech coding mode or comfort noise (SID) mode. The mapping of
   existing modes to FT is given in Table 1a in [2] for AMR and in Table
   1a in [4] for AMR-WB. If FT=14 (speech lost, available only in AMR-
   WB) or FT=15 (No transmission/no reception) no CRC or payload frame
   is present.
"

br,
Ari

> -----Original Message-----
> From: ext Faerber Tobias ICM MP PO8 RD MCH83
> [mailto:Tobias.Faerber@mch.siemens.de]
> Sent: 28 January, 2002 11:21
> To: AVT WG
> Subject: [AVT] Question on AMR PL-format: CRC building
> 
> 
> In case there is a NO_DATA frame within a RTP payload 
> containing several 
> AMR frames, e.g. (7,7,8,15,15,7), and CRC bits are 
> transmitted, is there 
> a CRC entry for the NO_DATA frames as well? I could not find 
> anything in 
> draft-ietf-avt-rtp-amr-10.txt on this. In my opinion it would 
> make not 
> much sense to send CRC bits for NO_DATA frames, as there is 
> nothing to 
> protect and they would just have to be 0's. From the PT entries you 
> would be able to associate the right CRC bits to the data containing 
> frames. However, this would have to be specified clearly, since it 
> cannot easily be seen from the payload contents which method has been 
> used.
> 
> 
> 
> --------------------------------------------------------------
> --------------
> -------
>  Faerber Tobias		Siemens AG
> --------------------------------------------------------------
> --------------
> -------
> 
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Mon Jan 28 06:10:30 2002
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 GAA22093
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 06:10:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA04035
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 06:10:33 -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 GAA03997;
	Mon, 28 Jan 2002 06:09:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03967
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 06:09:32 -0500 (EST)
Received: from web8005.mail.in.yahoo.com (web8005.in.yahoo.com [203.199.70.65])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA22080
	for <avt@ietf.org>; Mon, 28 Jan 2002 06:09:27 -0500 (EST)
Message-ID: <20020128110857.41617.qmail@web8005.mail.in.yahoo.com>
Received: from [164.164.42.6] by web8005.mail.in.yahoo.com via HTTP; Mon, 28 Jan 2002 03:08:57 PST
Date: Mon, 28 Jan 2002 03:08:57 -0800 (PST)
From: Rama Lakshmi <ramalakshmi_m@yahoo.co.in>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [AVT] Doubts regarding RFC 2833
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

Hi  all ,

         I have following doubts regarding RFC2833
1.What is the need for using in-band signalling when
out-of-band
signalling has so many advantages ?
2.what kind of signalling is used in PSTN ?
3.What is the  relation between PSTN  signalling(
in-band ) and SS7
signalling( out-of-band ) ?
4.When there is packet loss in transmission of  rfc
2833 packets 
whether
it should be retransmitted or  the data should be
recovered  from
redundant data ( as said in rfc 2198 )?
5.What is the gateway that should be  used when using
rfc 2833  ?

Thanks in advance ,
Rams



__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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



From daemon@optimus.ietf.org  Mon Jan 28 08:12:52 2002
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 IAA23851
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 08:12:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA08984
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 08:12:54 -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 IAA08970;
	Mon, 28 Jan 2002 08:12:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA08939
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 08:12:15 -0500 (EST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23842
	for <avt@ietf.org>; Mon, 28 Jan 2002 08:12:12 -0500 (EST)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id g0SDBvI07656;
	Mon, 28 Jan 2002 08:11:57 -0500 (EST)
Received: from cisco.com (rtp-vpn2-272.cisco.com [10.82.241.16])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AAN97283;
	Mon, 28 Jan 2002 08:11:41 -0500 (EST)
Message-ID: <3C5550D1.A38CA1D9@cisco.com>
Date: Mon, 28 Jan 2002 08:23:30 -0500
From: Wayne Mills <wmills@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rama Lakshmi <ramalakshmi_m@yahoo.co.in>
CC: avt@ietf.org
Subject: Re: [AVT] Doubts regarding RFC 2833
References: <20020128110857.41617.qmail@web8005.mail.in.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit



Rama Lakshmi wrote:

> Hi  all ,
>
>          I have following doubts regarding RFC2833
> 1.What is the need for using in-band signalling when
> out-of-band
> signalling has so many advantages ?

I can think of one advantage.  RTP, through sequence numbers and other
timing info, allows the receiving party to more accurately reproduce the
timing of the in-band signals when regenerated on the PSTN side.  With
OOB signalling, it's more difficult to reproduce the timing of the
signal w/r/t the original media stream it came from, since media and
signalling may take different paths through the network and are less (or
not?) correlated.

Regards,
Wayne.

>
> 2.what kind of signalling is used in PSTN ?
> 3.What is the  relation between PSTN  signalling(
> in-band ) and SS7
> signalling( out-of-band ) ?
> 4.When there is packet loss in transmission of  rfc
> 2833 packets
> whether
> it should be retransmitted or  the data should be
> recovered  from
> redundant data ( as said in rfc 2198 )?
> 5.What is the gateway that should be  used when using
> rfc 2833  ?
>
> Thanks in advance ,
> Rams
>
> __________________________________________________
> Do You Yahoo!?
> Great stuff seeking new owners in Yahoo! Auctions!
> http://auctions.yahoo.com
>
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Mon Jan 28 09:14:15 2002
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 JAA26530
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 09:14:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA13021
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 09:14:18 -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 JAA12991;
	Mon, 28 Jan 2002 09:13:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA00614
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 04:50:13 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21421
	for <avt@ietf.org>; Mon, 28 Jan 2002 04:50:08 -0500 (EST)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0S9o9301605;
	Mon, 28 Jan 2002 10:50:09 +0100 (MET)
Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id KAA23103; Mon, 28 Jan 2002 10:48:26 +0100
Message-ID: <3C551E69.A659F991@era.ericsson.se>
Date: Mon, 28 Jan 2002 10:48:25 +0100
From: Magnus Westerlund <magnus.westerlund@era.ericsson.se>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Faerber Tobias ICM MP PO8 RD MCH83 <Tobias.Faerber@mch.siemens.de>
CC: AVT WG <avt@ietf.org>
Subject: Re: [AVT] Question on AMR PL-format: CRC building
References: <07B0CDE3B76AD31190F700508B5D5D1DDF5533@mchg9eba.mchh.siemens.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hi Tobias

No, There shall not be a CRC entry for frames of type NO_DATA. This will be well
specified in the soon finished update.

Cheers

Magnus


Faerber Tobias ICM MP PO8 RD MCH83 wrote:

> In case there is a NO_DATA frame within a RTP payload containing several
> AMR frames, e.g. (7,7,8,15,15,7), and CRC bits are transmitted, is there
> a CRC entry for the NO_DATA frames as well? I could not find anything in
> draft-ietf-avt-rtp-amr-10.txt on this. In my opinion it would make not
> much sense to send CRC bits for NO_DATA frames, as there is nothing to
> protect and they would just have to be 0's. From the PT entries you
> would be able to associate the right CRC bits to the data containing
> frames. However, this would have to be specified clearly, since it
> cannot easily be seen from the payload contents which method has been
> used.
>
> ----------------------------------------------------------------------------
> -------
>  Faerber Tobias         Siemens AG
> ----------------------------------------------------------------------------
> -------
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

--

Magnus Westerlund

Audio Technology, Ericsson Research
----------------------------------------------------------------------
Ericsson Radio Systems AB  | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@era-t.ericsson.se




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



From daemon@optimus.ietf.org  Mon Jan 28 10:18:08 2002
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 KAA28899
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 10:18:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA16318
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 10:18:12 -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 KAA16229;
	Mon, 28 Jan 2002 10:16:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA16198
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 10:16:32 -0500 (EST)
Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28840
	for <avt@ietf.org>; Mon, 28 Jan 2002 10:16:27 -0500 (EST)
Received: from zrtpd004.us.nortel.com (zrtpd004.us.nortel.com [47.28.160.173])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0SFFsH25497;
	Mon, 28 Jan 2002 10:15:54 -0500 (EST)
Received: from zrtpd0jk.us.nortel.com ([47.140.202.36]) by zrtpd004.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id CJV3BTBP; Mon, 28 Jan 2002 10:15:53 -0500
Received: from americasm01.nt.com (pnc0d04n.us.nortel.com [47.142.169.119]) by zrtpd0jk.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id ZZR86TVB; Mon, 28 Jan 2002 10:16:10 -0500
Message-ID: <3C556BDA.D88D08EB@americasm01.nt.com>
Date: Mon, 28 Jan 2002 10:18:50 -0500
X-Sybari-Space: 00000000 00000000 00000000
From: "Chris Fulmer"<chrisf@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rama Lakshmi <ramalakshmi_m@yahoo.co.in>
CC: avt@ietf.org
Subject: Re: [AVT] Doubts regarding RFC 2833
References: <20020128110857.41617.qmail@web8005.mail.in.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Rama --

Rama Lakshmi wrote:

> Hi  all ,
>
>          I have following doubts regarding RFC2833
> 1.What is the need for using in-band signalling when
> out-of-band
> signalling has so many advantages ?

Several...  First of all, the out-of-band signalling doesn't
necessarily terminate at the same place that your bearer
path does.  Secondly, many applications use DTMF tones
for the user to singal to the remote end (ie voice-mail systems,
IVR systems, etc...)  Third, you need to make sure that the
out-of-band DTMF arrives at the remote end at the correct
point in time in the call.

> 2.what kind of signalling is used in PSTN ?

The PSTN uses both in-band and out-of-band signalling.

> 3.What is the  relation between PSTN  signalling(
> in-band ) and SS7
> signalling( out-of-band ) ?

SS7 is a primary way of carrying signalling information
between switches.  It's one way of doing PSTN signalling,
but not the only way.

> 4.When there is packet loss in transmission of  rfc
> 2833 packets
> whether
> it should be retransmitted or  the data should be
> recovered  from
> redundant data ( as said in rfc 2198 )?

Depends on your application, but in general you don't
have time to ask for retransmission -- that's why the
redundant information is there.

> 5.What is the gateway that should be  used when using
> rfc 2833  ?

Uhh...  Any gateway that supports RFC 2833.  2833 is a fairly
new RFC, so there are a lot of gateways on the market now
that don't do 2833, but if you ask the equipment providers,
they're probably adding it right now.  Your gateway choice
will be determined in large part by what control protocols
you want to use (are you doing a H.323 gateway, MGCP, H.248,
etc...) and what's your termination into the telephony world
(analog, PRI, T1/E1, SS7), as well as things like size, power
requirements, cost, etc....

(Apart from that, my answer is going to be "A Nortel Gateway,
of course....")

--
C



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



From daemon@optimus.ietf.org  Mon Jan 28 16:20:49 2002
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 QAA09276
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 16:20:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA05971
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 16:20:52 -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 QAA05830;
	Mon, 28 Jan 2002 16:20:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA05801
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 16:20:08 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09251
	for <avt@ietf.org>; Mon, 28 Jan 2002 16:20:03 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0SLJap43926;
	Mon, 28 Jan 2002 13:19:36 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 28 Jan 2002 13:22:06 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020128132055.D12881-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [AVT] Request for publication as Proposed Standard (fwd)
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

FYI.
	-- Steve

---------- Forwarded message ----------
Date: Mon, 28 Jan 2002 13:17:08 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Allison Mankin <mankin@ISI.EDU>, Scott Bradner <sob@harvard.edu>
Cc: iesg-secretary@ietf.org, Colin Perkins <csp@ISI.EDU>
Subject: Request for publication as Proposed Standard

The Audio/Video Transport working group hereby requests that the
following Internet Draft be published as a Proposed Standard RFC:

        Title           : RTP Payload for Comfort Noise
        Author(s)       : R. Zopf
        Filename        : draft-ietf-avt-rtp-cn-05.txt
        Pages           : 8
        Date            : 24-Jan-02

This draft is a product of the AVT WG and has been in development for
more than a year.  It is an extension of a comfort noise payload
format that was included in early revisions of the RTP A/V Profile,
draft-ietf-avt-profile-new, but which was separated out when the ITU-T
undertook specification and testing of the more complete method
specified in ITU-T Recommendation G.711 and referenced in this draft.

There was one controversial change introduced in the -03 revision, but
after group discussion that change was reverted.  The only open
question is whether there are any counterexamples to the claim that
this extended method is backward compatible with the simpler version
from the early revisions of draft-ietf-avt-profile-new.  We have not
identified any conflicts in the review and last call within the WG.
The IESG Last Call provides the appropriate opportunity for a final
check on that question.
                                                -- Steve & Colin


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



From daemon@optimus.ietf.org  Mon Jan 28 18:47:14 2002
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 SAA11402
	for <avt-archive@odin.ietf.org>; Mon, 28 Jan 2002 18:47:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA11347
	for avt-archive@odin.ietf.org; Mon, 28 Jan 2002 18:47:17 -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 SAA11272;
	Mon, 28 Jan 2002 18:43:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11243
	for <avt@optimus.ietf.org>; Mon, 28 Jan 2002 18:43:54 -0500 (EST)
Received: from odin.tuclab ([208.1.25.242])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11380
	for <avt@ietf.org>; Mon, 28 Jan 2002 18:43:49 -0500 (EST)
Received: from effnet.com (zeus.tuclab [172.16.11.10])
	by odin.tuclab (8.11.2/8.11.2) with ESMTP id g0SNcZ210767
	for <avt@ietf.org>; Mon, 28 Jan 2002 16:38:35 -0700
Message-ID: <3C55E0FA.4060007@effnet.com>
Date: Mon, 28 Jan 2002 16:38:34 -0700
From: Somasundaram Perianayagam <somu@effnet.com>
Reply-To: somu@effnet.com
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] Enhanced CRTP Review
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
Content-Transfer-Encoding: 7bit

Here's my review of Enhanced CRTP:

Both my points are quite small. The draft looked great.

1)

"This document describes a header compression scheme for point to
point links with packet loss and long delays."

I guess it would be good if "packet loss" can be quantified here.
You know like "links with high rate of packet loss".

2)

"CONTEXT_STATE packets SHOULD also be repeated N+1 times (using the
same sequence number) to provide a similar measure of robustness
against packet loss."

Since we can maintain seperate N's for every context we have a question 
here "what is N + 1 here?"

To be safe you can assume N+1 to be the largest among the contexts for 
which context repair is required.

regards
Somu

Effnet Inc


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



From daemon@optimus.ietf.org  Tue Jan 29 13:35:00 2002
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 NAA12918
	for <avt-archive@odin.ietf.org>; Tue, 29 Jan 2002 13:35:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA20975
	for avt-archive@odin.ietf.org; Tue, 29 Jan 2002 13:35:02 -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 NAA20896;
	Tue, 29 Jan 2002 13:33:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20868
	for <avt@optimus.ietf.org>; Tue, 29 Jan 2002 13:33:19 -0500 (EST)
Received: from ns.live.com (ns.live.com [66.80.62.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12843
	for <avt@ietf.org>; Tue, 29 Jan 2002 13:33:15 -0500 (EST)
Received: (from rsf@localhost)
	by ns.live.com (8.9.3/8.9.3) id KAA02615;
	Tue, 29 Jan 2002 10:33:17 -0800 (PST)
	(envelope-from rsf)
Message-Id: <4.3.1.1.20020129102633.00ca3410@localhost>
X-Sender: rsf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 29 Jan 2002 10:31:18 -0800
To: avt@ietf.org
From: Ross Finlayson <finlayson@live.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [AVT] Open source H.263+ video encoder implementation?
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

Does anyone know of a good open source implementation of a H.263+ video 
encoder?

To date I've been using the "tmn-x" implementation that's used by "vic", 
but I've been disappointed in its performance - e.g., on a 233 MHz Pentium 
box (admittedly, this is a low-end machine these days), it takes an average 
of *570 ms* to encode each frame.  Does anyone know of  a better 
implementation?

(To make this message at least partially on-topic :-), the encoded video 
will streamed using RTP (RFC 2429).)

	Ross.


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



From daemon@ns.ietf.org  Tue Jan 29 16:31:37 2002
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 QAA21547
	for <avt-archive@odin.ietf.org>; Tue, 29 Jan 2002 16:31:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA01406
	for avt-archive@odin.ietf.org; Tue, 29 Jan 2002 16:31:41 -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 QAA01334;
	Tue, 29 Jan 2002 16:31:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA01294
	for <avt@ns.ietf.org>; Tue, 29 Jan 2002 16:31:07 -0500 (EST)
Received: from icsl.icsl.ucla.edu (icsl.ICSL.UCLA.EDU [128.97.90.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21536
	for <avt@ietf.org>; Tue, 29 Jan 2002 16:31:02 -0500 (EST)
Received: from scope (Pc127.ICSL.UCLA.EDU [128.97.90.127])
	by icsl.icsl.ucla.edu (8.8.8+Sun/8.8.8(ICSL0003-amavis)) with SMTP id NAA26806;
	Tue, 29 Jan 2002 13:31:04 -0800 (PST)
From: "Adam Li" <adamli@icsl.ucla.edu>
To: "Ross Finlayson" <finlayson@live.com>, <avt@ietf.org>
Subject: RE: [AVT] Open source H.263+ video encoder implementation?
Date: Tue, 29 Jan 2002 13:31:13 -0800
Message-ID: <NEBBLMIKILMNOPFCPHHFKENEDAAA.adamli@icsl.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <4.3.1.1.20020129102633.00ca3410@localhost>
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit


As far as I know, there is no open source H.263+ codec available.

The UBC/Telenor TMN implementation was the last one out there, but it is no
longer maintained anymore. UBC used to have a version based on that which
can be got for a fee, but that was not longer available also.

Hope it helps.

Adam

> -----Original Message-----
> From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of Ross
> Finlayson
> Sent: Tuesday, January 29, 2002 10:31 AM
> To: avt@ietf.org
> Subject: [AVT] Open source H.263+ video encoder implementation?
>
>
> Does anyone know of a good open source implementation of a H.263+ video
> encoder?
>
> To date I've been using the "tmn-x" implementation that's used by "vic",
> but I've been disappointed in its performance - e.g., on a 233
> MHz Pentium
> box (admittedly, this is a low-end machine these days), it takes
> an average
> of *570 ms* to encode each frame.  Does anyone know of  a better
> implementation?
>
> (To make this message at least partially on-topic :-), the encoded video
> will streamed using RTP (RFC 2429).)
>
> 	Ross.
>
>
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Wed Jan 30 03:28:28 2002
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 DAA12482
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 03:28:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA10036
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 03:28:29 -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 DAA09872;
	Wed, 30 Jan 2002 03:25:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09847
	for <avt@ns.ietf.org>; Wed, 30 Jan 2002 03:25:48 -0500 (EST)
Received: from stsl.siemens.com.tw (stsl.siemens.com.tw [192.72.45.189])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12450
	for <avt@ietf.org>; Wed, 30 Jan 2002 03:25:45 -0500 (EST)
Received: from stslex.siemens.com.tw (stslex [140.231.62.94])
	by stsl.siemens.com.tw (8.11.6/8.11.6) with ESMTP id g0U8RtF28086
	for <avt@ietf.org>; Wed, 30 Jan 2002 16:27:55 +0800 (CST)
Received: by stslex.siemens.com.tw with Internet Mail Service (5.5.2653.19)
	id <CVTTM39S>; Wed, 30 Jan 2002 16:25:43 +0800
Message-ID: <92C0C0AC8AE8D411864300105A835CBB50170B@stslex.siemens.com.tw>
From: Moter Du <moter.du@siemens.com>
To: "'avt@ietf.org'" <avt@ietf.org>
Date: Wed, 30 Jan 2002 16:25:39 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A967.B3229C00"
Subject: [AVT] cRTP questions
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A967.B3229C00
Content-Type: text/plain

Hi,

Is the idea to compress IP/UDP/RTP strictly limited to low-speed serial
line?

The question comes from CSMA/CD, efficiency analysis in theory shows the
larger the frame is, the better the efficiency it achieves.  That means,
CSMA/CD link efficiency (e.g., fast-ethernet) wouldn't gain from header
compression, because the phsical frame is reduced while the headers are
reduced.  But meanwhile, I heard many companies claim their ethernet-based
VoIP gateways outperform due to cRTP.

Thanks.

Moter

------_=_NextPart_001_01C1A967.B3229C00
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>cRTP questions</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>Is the idea to compress IP/UDP/RTP strictly limited =
to low-speed serial line?</FONT>
</P>

<P><FONT SIZE=3D2>The question comes from CSMA/CD, efficiency analysis =
in theory shows the larger the frame is, the better the efficiency it =
achieves.&nbsp; That means, CSMA/CD link efficiency (e.g., =
fast-ethernet) wouldn't gain from header compression, because the =
phsical frame is reduced while the headers are reduced.&nbsp; But =
meanwhile, I heard many companies claim their ethernet-based VoIP =
gateways outperform due to cRTP.</FONT></P>

<P><FONT SIZE=3D2>Thanks.</FONT>
</P>

<P><FONT SIZE=3D2>Moter</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A967.B3229C00--

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



From daemon@optimus.ietf.org  Wed Jan 30 04:10:59 2002
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 EAA12916
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:10:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA12356
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 04:11:00 -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 EAA12330;
	Wed, 30 Jan 2002 04:10:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12303
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 04:10:27 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12910
	for <avt@ietf.org>; Wed, 30 Jan 2002 04:10:25 -0500 (EST)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0U9AQC11946
	for <avt@ietf.org>; Wed, 30 Jan 2002 10:10:26 +0100 (MET)
Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id KAA10399; Wed, 30 Jan 2002 10:10:25 +0100
Message-ID: <3C57B881.97FA7928@era.ericsson.se>
Date: Wed, 30 Jan 2002 10:10:25 +0100
From: Magnus Westerlund <magnus.westerlund@era.ericsson.se>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] New AMR draft available
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
Content-Transfer-Encoding: 7bit

Hi,

The updating of the AMR RTP payload format draft has now produced some
results. A new draft has been submitted to the IETF draft repository,
until it is available there you can get it at the following location:

"http://standards.ericsson.net/westerlund/draft-ietf-avt-rtp-amr-11.txt"

So please start reviewing immediately as we are trying to meet a
deadline. There are only a single technical change in this version
compared to version 10, and that is multi-channel support. This has been
added without changing a single bit when using a single channel. There
is major editorial changes, like restructuring, and added text,
explaining things better.

Happy reading

Magnus Westerlund

Audio Technology, Ericsson Research
----------------------------------------------------------------------
Ericsson Radio Systems AB  | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@era-t.ericsson.se




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



From daemon@optimus.ietf.org  Wed Jan 30 04:24:02 2002
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 EAA13088
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:24:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA12672
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 04:24:04 -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 EAA12625;
	Wed, 30 Jan 2002 04:22:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12595
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 04:22:09 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13050
	for <avt@ietf.org>; Wed, 30 Jan 2002 04:22:07 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g0U9M7X4015030
	for <avt@ietf.org>; Wed, 30 Jan 2002 10:22:07 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Jan 30 10:21:50 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKC8PTC>; Wed, 30 Jan 2002 10:12:53 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050023BC3D8@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: avt@ietf.org
Date: Wed, 30 Jan 2002 10:22:02 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [AVT] Another review of enhanced CRTP
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

Hi all,

I was asked to review the ECRTP draft, and have some minor inputs
that might be useful to take into account. Overall, I think the
document is fine, and with one exception, all my comments are of
a pure editorial nature. I am especially satisfied with the way
the "IP-ID versus Twice" issue was resolved.

1) Let's start with the only technical comment, which is just a
   suggestion. Why not let the HDRCKSUM (section 2.2) cover also
   the IP ID for IPv4, in addition to the IP-pseudo header, the
   UDP header, and the first 12 octets of UDP data (e.g. RTP). By 
   including the IP ID, the concerns about using Twice (section
   2.3, 5th paragraph) would only apply to IPv4 with enabled
   UDP checksum (if the HDRCKSUM is enabled). 

   This is just a suggestion, and a question whether you have 
   considered that option. Let us know your opinions.

2) In section 2, first bullet, I think it would be good to
   clarify "RTP values". Are you addressing all RTP fields, or
   just a subset, and in that case, which fields are addressed.
   Please clarify that.

3) In section 2.2, second paragraph, it could be useful to
   indicate that a disabled (set to zero) UDP checksum is a case
   only possible for IPv4.

4) In section 3, should there be a reference to the updated 
   RFC2509? What is the status of that document anyway?

5) Finally some formatting comments:
5a) There are no page beaks (form feed) in the document
5b) I am missing headers, footers, and especially page numbers
5c) The expiration date is missing at the last page
5d) The indentation is only "correct" in sections 3, 6, and 7

Otherwise I think the document is fine and fully support the idea
of submitting it (with correction) for PS.

Cheers,
/Lars-Erik

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



From daemon@optimus.ietf.org  Wed Jan 30 07:27:27 2002
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 HAA16186
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 07:27:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA21565
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 07:27:28 -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 HAA21486;
	Wed, 30 Jan 2002 07:26:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21457
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 07:26:37 -0500 (EST)
Received: from gateway.ncoretech.com (IDENT:root@[164.164.42.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16162
	for <avt@ietf.org>; Wed, 30 Jan 2002 07:26:31 -0500 (EST)
Received: from ncoretech.com (IDENT:root@mail.ncoretech.com [192.168.1.3])
	by gateway.ncoretech.com (8.10.0/8.10.0) with ESMTP id g0UCQRY19303
	for <avt@ietf.org>; Wed, 30 Jan 2002 17:56:27 +0530
Received: (from root@localhost)
	by ncoretech.com (8.10.0/8.10.0) id g0UCQR010821
	for avt@ietf.org.VIRCHECK; Wed, 30 Jan 2002 17:56:27 +0530
Received: from ncoretech.com (ws186.ncoretech.com [192.168.1.186])
	by ncoretech.com (8.10.0/8.10.0) with ESMTP id g0UCQQK10732;
	Wed, 30 Jan 2002 17:56:26 +0530
Message-ID: <3C57E8C9.65C0B4DC@ncoretech.com>
Date: Wed, 30 Jan 2002 18:06:25 +0530
From: angai <angai@ncoretech.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.7 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: avt@ietf.org, rtp@vovida.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-AntiVirus: scanned for viruses on Wed Jan 30 17:56:26 IST 2002
Content-Transfer-Encoding: 7bit
Subject: [AVT] Doubts in RFC 2833
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
Content-Transfer-Encoding: 7bit

Hi members ,

          After reading the explanation for Doubts in RFC2833  we have
the following doubt :
           1.which payload type  should be used for Rtp packet which
carries combined data of tones and events ?
              Whether it should  be payload type negotiated for DTMF or
payload negotiated for Tones ?

Thanks in Advance  ,
Angai



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



From daemon@optimus.ietf.org  Wed Jan 30 08:54:12 2002
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 IAA18481
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 08:54:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA26528
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 08:54:14 -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 IAA26412;
	Wed, 30 Jan 2002 08:52:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26372
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 08:52:55 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18393
	for <avt@ietf.org>; Wed, 30 Jan 2002 08:52:52 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA09579;
	Wed, 30 Jan 2002 14:52:49 +0100 (MET)
Received: from mchh9eea.mchh.siemens.de (mchh9eea.mchh.siemens.de [139.21.204.218])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA28058;
	Wed, 30 Jan 2002 14:52:51 +0100 (MET)
Received: by mchh9eea.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <D6SPTWG3>; Wed, 30 Jan 2002 14:51:12 +0100
Message-ID: <07B0CDE3B76AD31190F700508B5D5D1DDF5564@mchg9eba.mchh.siemens.de>
From: Faerber Tobias ICM MP PO8 RD MCH83 <Tobias.Faerber@mch.siemens.de>
To: "'Magnus Westerlund'" <magnus.westerlund@era.ericsson.se>,
        IETF AVT WG
	 <avt@ietf.org>
Subject: RE: [AVT] New AMR draft available
Date: Wed, 30 Jan 2002 14:52:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

hi all,
please include like in draft10 (2.7) an own little section describing which
part is to be considered mandatory and which is optional ? i know there is
written something in 4.2 but to make it easier for implementers all features
and the their implementation considerations should be given globally.

is multichannel support optional ? I guess yes....

about fomatting: to my opinion it would be nice to include the hint for bit
sorting into classes that the tables of Annex B in TS26.101 should be used

best,
Tobi

----------------------------------------------------------------------------
-------
> Faerber Tobias		Siemens AG
ICM MP PO8 RD MCH83 	Information and Communication Mobile

> Tel:	+49 89 722 58578	Grillparzerstrasse 10 a
> mobile:  +49 175 5721351	81675 Munich, Germany
> Fax:	+49 89 722 59070	
mailto:tobias.faerber@mch.siemens.de
----------------------------------------------------------------------------
-------


> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@era.ericsson.se]
> Sent: Mittwoch, 30. Januar 2002 10:10
> To: IETF AVT WG
> Subject: [AVT] New AMR draft available
> 
> 
> Hi,
> 
> The updating of the AMR RTP payload format draft has now produced some
> results. A new draft has been submitted to the IETF draft repository,
> until it is available there you can get it at the following location:
> 
> "http://standards.ericsson.net/westerlund/draft-ietf-avt-rtp-a
mr-11.txt"

So please start reviewing immediately as we are trying to meet a
deadline. There are only a single technical change in this version
compared to version 10, and that is multi-channel support. This has been
added without changing a single bit when using a single channel. There
is major editorial changes, like restructuring, and added text,
explaining things better.

Happy reading

Magnus Westerlund

Audio Technology, Ericsson Research
----------------------------------------------------------------------
Ericsson Radio Systems AB  | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@era-t.ericsson.se




_______________________________________________
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



From daemon@optimus.ietf.org  Wed Jan 30 11:51:08 2002
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 LAA24863
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 11:51:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08115
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 11:51:06 -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 LAA07536;
	Wed, 30 Jan 2002 11:42:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07449
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 11:42:40 -0500 (EST)
Received: from speechworks.com (valmiki.speechworks.com [63.113.17.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24559
	for <avt@ietf.org>; Wed, 30 Jan 2002 11:42:37 -0500 (EST)
Received: from vishnu.speechworks.com (mailhost.speechworks.com [206.234.64.17])
	by speechworks.com (8.10.2+Sun/8.9.3) with ESMTP id g0UGklY15701
	for <avt@ietf.org>; Wed, 30 Jan 2002 11:46:47 -0500 (EST)
Received: from galaxy (localhost [127.0.0.1])
	by vishnu.speechworks.com (8.10.2+Sun/8.9.3) with SMTP id g0UGgc212888
	for <avt@ietf.org>; Wed, 30 Jan 2002 11:42:38 -0500 (EST)
From: "Priscilla Walther" <priscilla.walther@speechworks.com>
To: <avt@ietf.org>
Date: Wed, 30 Jan 2002 11:42:37 -0500
Message-ID: <ACEJIPIJFOPDOOMGEGBJAEELCKAA.priscilla.walther@speechworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [AVT] Review of draft-ietf-avt-dsr-00.txt
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
Content-Transfer-Encoding: 7bit

			       Comments on draft-ietf-avt-dsr-00.txt

General Comments:
This is an important specification, enabling improved accuracy by speech
recognition engines when audio is transported over packet networks.
Currently, the most prevalent uses would be over the Internet, over
private VoIP networks, and for IP networks linked to the PSTN via
VoIP gateways.  After the launch of 3G networks, this payload format
will become even more important, both to improve accuracy and to
reduce bandwidth over wireless networks.  The specification is a good
fit with other evolving VoIP specifications such as SIP, VoiceXML, and
MRCP.

While I support this specification in general, our Speech Scientists
noted a few minor technical details that should be addressed.  These are
listed in the "Speech Science Notes" section of my comments.  In addition, I
have made a number of editorial comments.  These are either listed in the
"Editorial Notes" section of my comments or they are marked inline.
The comments marked inline are indicated by a pair of beginning and ending
markers ("XX").  Between the pair of markers are either comments
about the text or there is a suggested re-wording of that text.
Suggested re-wordings are indicated using the following format:
'original-text'->'replacement-text'.

Speech Science Notes:
- I'd add something regarding transmission of the DSR mime type
registration.  Does that (or can that) happen at the beginning of each
transmission?

- there's no mention of endpointing or startpointing ... only that it
happens on the client side ... it should make explicit mention of end- and
start-  though.

Editorial Notes:
Global observations -
* engin -> engine
* if you've set up an abbreviation, use it (e.g., SE for Speech
Engine, FP for frame pairs)
* frame pairs not frame-pairs
* paragraphs must have at least two sentences
* I know what a Front-End is and how it relates to this spec,
  but many readers may not.  Give a high-level description early
  in the doc.
* In general, if you are using speech reco terminology, you should
  give a high-level description early in the doc and/or add a glossary.
* add and use the following abbreviation:  FE for Front-End.


-----------------------------------------------------------------------
Internet Engineering Task Force	                       Q. Xie, Motorola
Audio Video Transport WG                            D. Pearce, Motorola
INTERNET-DRAFT                                  S. Balasuriya, Motorola
                                                      Y. Kim, VerbalTek
                                                        S. H. Maes, IBM
                                               Hari Garudadri, Qualcomm

XXInsert correct dateXX
Expires in six months                                     Nov. 12, 2001


         RTP Payload Format for Distributed Speech Recognition
                    <draft-ietf-avt-dsr-00.txt>


Status of this Memo

This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of [RFC2026].

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- Drafts
as reference material or to cite them other than as "work in
progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.


1. Abstract

XXMake this two sentences.  Too hard to parse.XX

This document specifies an RTP payload format for encapsulating a
front-end signal processing feature streams for distributed speech
recognition (DSR) systems, with the ETSI Standard ES 201 108 front-end
being the default codec.


2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC-2119].


3. Introduction

Motivated by technology advances in the field of speech recognition,
voice interfaces to XXcut 'a variety of'XX services (such as airline
information systems, unified messaging,
XX "such as" eliminates the need for the phrase  'and the like'XX)
are becoming more
XX'and more' is redundantXX prevalent. In parallel, the popularity of
mobile XXredundant 'computing and communications'XX devices
has also increased dramatically. However, the voice codecs typically
employed in mobile
XXphones or devices yes - systems no. 'systems'->'phones'XX
were designed to optimize audible voice quality and not speech recognition
accuracy, and using these codecs with speech recognizers can result in poor
recognition performance. For systems that can be accessed from
XX'multiple' -> 'heterogeneous'XX
networks using multiple speech
codecs, recognition system designers are further challenged to
accommodate the characteristics of these differences in a robust
manner. Channel errors and lost data packets in these networks result
in further degradation of the speech signal.

In traditional systems as described above, the entire speech recognizer lies
on the server XXcut 'appliance'XX.
It is forced to use incoming speech in whatever condition it arrives
XX'in' is redundant'XX
after the network decodes the vocoded speech. A solution that combats this
XXadd 'problem' or similar nounXX
uses a scheme called "distributed speech recognition" (DSR). In
XX'this system' -> 'DSR'XX,
the remote device acts as a thin client in communication with a speech
recognition server, also called a speech engine (SE). The remote device
processes the speech, compresses
XXadd a noun or noun phrase such as 'it'XX, and
XX'error protects' is NOT a verbXX
the bitstream in a manner optimal for speech recognition. The speech
XX'engin' misspelling - also, why not use the abbreviation you've just
introduced?XX
then uses this representation directly, minimizing the signal
processing necessary and benefiting from enhanced error concealment.

XX'engin' misspelled throughout - but also again why not use SE????XX
To achieve interoperability with different client devices and speech
engins, a common format is needed. Within the "Aurora" DSR working
group of the European Telecommunications Standards Institute (ETSI), a
payload has been defined and was published as a standard in February
2000 [ES201108]. XX reference to std belongs after the word 'standard',
not after '2000'XX

XX'interactive voice user interface dialogues' redundant 'between a caller
and a voice service'- XX
For interactive voice user interface dialogues between a caller and a
voice service, low latency is
XXcut 'also'XX
a high priority along with accurate speech recognition. While jitter in
the speech recognizer input is not particularly important, many issues
related to speech interaction over an IP-based connection are still
relevant.
Therefore, it will be desirable to use the DSR payload in an RTP-based
session.


3.1 Typical Scenarios for Using DSR Payload Format

The following diagrams show some typical use scenarios of the DSR RTP
payload format.

XXagain, why say Speech Engine when you've got that abbreviation?XX

  +--------+                     +----------+
  |IP USER |  IP/UDP/RTP/DSR     |IP SPEECH |
  |TERMINAL|-------------------->|  ENGINE  |
  |        |                     |          |
  +--------+                     +----------+


  +--------+  DSR over      +-------+                +----------+
  | Non-IP |  Circuit link  |       | IP/UDP/RTP/DSR |IP SPEECH |
  |  USER  |:::::::::::::::>|GATEWAY|--------------->|  ENGINE  |
  |TERMINAL|  ETSI payload  |       |                |          |
  +--------+  format        +-------+                +----------+


  +--------+                  +-------+  DSR over       +----------+
  |IP USER |  IP/UDP/RTP/DSR  |       |  circuit link   |  Non-IP  |
  |TERMINAL|----------------->|GATEWAY|::::::::::::::::>|  SPEECH  |
  |        |                  |       |  ETSI payload   |  ENGINE  |
  +--------+                  +-------+  format         +----------+

    Figure 1: Typical Scenarios for Using DSR Payload Format.

XXWow - what a long opening sentence!!  Can you break it up?XX
For the different scenarios in Figure 1, the speech recognizer resides
in the speech engin, while a DSR front-end encoder inside the User
Terminal performs front-end speech processing and sends the resultant
data to the speech engin in the form of "frame-pairs" (FPs). Each
frame-pair normally contains two sets of encoded speech vectors
representing 20ms of original speech.
XXwhy do you keep setting up abbreviations that you don't use?XX
XXYou don't need the hyphen.XX

4. DSR RTP Payload Format

XXI know what a front-end is but you've never introduced that
concept back when you could have.  You need to explain that
in your document's introductory paragraph.XX

The DSR RTP payload is formed by concatenating a series of DSR
frame-pairs. The format of the DSR frame-pair may vary from one
front-end type to another, see Section 5 for details.

Each DSR payload MUST be octet-aligned at the end, i.e., if a DSR
payload does not end on an octet boundary, it then MUST be padded at
the end with zeros to the next octet boundary.

The following example shows a DSR payload carrying 3 92-bit-long frame
pairs:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                         FP #1 (92 bits)                       |
   +                                                       +-+-+-+-+
   |                                                       |       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+       +
   |                                                               |
   +                                                               +
   |                         FP #2 (92 bits)                       |
   +                                               +-+-+-+-+-+-+-+-+
   |                                               |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               +
   |                                                               |
   +                         FP #3 (92 bits)                       +
   |                                                               |
   +                                       +-+-+-+-+-+-+-+-+-+-+-+-+
   |                                       |0|0|0|0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


In this example, the payload is shown with 4 zeros padded at the end
to make it octet-aligned.

XXEvery paragraph must have at least two sentendes.  Combine the next
three sentences into one paragraph.XX
The number of FPs per payload packet should be determined by the
latency and bandwidth requirements of the DSR application.

A decreasing number of FPs per payload packet reduces the bandwidth
efficiency due to the RTP header overhead, while an
XXincreacing->increasingXX
number of FPs per packet causes longer end-to-end delay and hence bigger
recognition latency.

XXA new paragraph can't start with the word "Furthermore", since
"Furthermore" indicates continuation of the previous thought, which
should all be contained in the same paragraph.  Also, the following sentence
doesn't make sense.XX
Furthermore, an increasing number of FPs per packet rises the
potential of the loss of a large number of consecutive frame-pairs,
which is a situation most speech recogziers have difficult to deal
with.

XXAgain, shouldn't start a new paragraph with "therefore", since it's a
continuation of the previous thought.  And again, at least two sentences
are required to make a single paragraph.XX
Therefore, it is RECOMMENDED that the number of FPs per DSR
payload packet be minimized, subject to meeting the application's
requirements on network bandwidth efficiency.

RTP header compression [RFC2508] SHOULD be considered to improve
network bandwidth efficiency.


4.1. Support for Discontinuous Transmission

XX'are only sent' ->'are sent only'XX
XXThis section needs a clearer explanation.  Maybe you need to swap the
order of the first two sentences??  Be sure to define terminology before
you use it.  For example, not everyone may be familiar with the term
"discontinuous transmission" or how it can occur.  If they stumble over
the first half of your sentence, they may not get to the second half of
the sentence, where you explain by implication what discontinuous
transmission is.  Same with contiguous segment.XX
The DSR RTP payloads may be used for discontinuous transmission so
that DSR FPs are only sent when speech has been detected at the
terminal equipment. A contiguous segment of DSR frames to be transmitted
from
the terminal to the server is called a Transmission Segment.

A DSR frame inside a transmission segment can be either a speech frame
or a non-speech frame, depending on the nature of the section of the
speech signal it represents.

XXNeed to explain "hangover time".  You've given a value, but haven't
said exactly what it is.XX
The end of a transmission segment is determined at the sending end
equipment when the number of consecutive non-speech frames exceeds the
hangover time. A typical value used for the hangover time is 1.5
seconds.

After all FPs in a transmission segment are sent, the front-end SHOULD
indicate the end of the current transmission segment by sending one or
more Null FPs.
XXNeed to define technically precisely the content of a Null FP.  (The
previous comment was made before I read further down where you define
a Null FP.  Maybe you just need to give a forward reference to that
section of the doc.)XX

5. Frame-pair Format
XX'present'->'current'XX
Depending on the type of the DSR front-end encoder to be used in the
present DSR RTP session, the frame-pair format may be different.

XXsingular ('a') vs plural ('sessions')XX
XX'speech engine the type' -> 'SE of the type'XX
When setting up a DSR RTP sessions, the user terminal will inform the
XX'speech engine the type' -> SE of the type'XX
of the front-end encoder, using the
front-end-type MIME parameter as defined in Section 7.

XX'we only define the frame-pair' -> 'we define only the FP'XX
In this memo, we only define the frame-pair formats that MUST be used
when the ESTI ES 201 108 Front-end Codec [ES201108] is used. Frame-
pair formats for future DSR front-end codecs may be defined in
separate IETF documents.

XX'Frame-Pair Formats For ETSI' -> 'FP Formats For The ETSI'XX
5.1. Frame-Pair Formats For ETSI ES 201 108 Front-end Codec

The ETSI Standard ES 201 108 for DSR [ES201108] defines a signal
processing front-end and compression scheme for speech input to a
speech recognition system. Some relevant characteristics of this ETSI
DSR front-end codec are summarized below.

The coding algorithm, a standard mel-cepstral technique common to many
speech recognition systems, supports three raw sampling rates: 8 kHz,
11 kHz, and 16 kHz. The mel-cepstral calculation is a frame-based
scheme that produces an output vector every 10 ms.

After calculation of the mel-cepstral representation, the
representation is quantized via split-vector quantization to reduce
the data rate of the encoded stream. This is a lossy compression, with
the output being a frame containing an integer representation of the
encoded speech.


5.1.1 Format of Speech and Non-speech FPs
XX'For ES' -> 'For the ES'XX
For ES 201 108 Front-end Codec, the following mel-cepstral frame MUST
be used, as defined in [ES201108]:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  idx(0,1) |  idx(2,3) |  idx(4,5) |  idx(6,7) |  idx(8,9) |idx
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   (10,11) |   idx(12,13)  |
   +-+-+-+-+-+-+-+-+-+-+-+-+

The length of a frame is 44 bits representing 10ms of voice.

As defined in [ES201108], pairs of the quantized 10ms mel-cepstral
frames MUST be grouped together and protected with a 4-bit CRC,
forming a 92-bit long frame-pair:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Frame #1  (44 bits)                      |
   +                       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       |          Frame #2 (44 bits)           |
   +-+-+-+-+-+-+-+-+-+-+-+-+                       +-+-+-+-+-+-+-+-+
   |                                               | CRC   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Therefore, each frame-pair represents 20ms of original speech.

The 4-bit CRC MUST be calculated using the formula defined in 6.2.4 in
[ES201108].


5.1.2 Format of Null FPs
XX'Null FP MUST be defined by'-> 'A Null FP is defined by' XX
Null FP MUST be defined by setting the content of the first and
second frame in the FP to null (i.e., filling the first 88 bits of the
FP with 0's). The 4-bit CRC MUST be calculated the same way as
described for speech FPs in 5.1.1.


6. DSR MIME Type Registration

Media Type name:     audio

Media subtype name:  DSR

Required parameters: none

Optional parameters for RTP mode:

XX'Indicating'->'Indicates'XX
 sample-rate: Indicating the sample rate of the speech. Valid values
	      include: 8k, 11k, and 16k.

	      If this parameter is not present, 8k sample rate is
	      assumed.

 front-end-type: Indicating the type of the front-end codec to be used
		 for this DSR session. Valid values are:

		 etsi_mfcc - indicates that ETSI ES 201 108 Front-end
		 Codec as defined in [ES201108] will be used.

XX'indicates that other' -> 'indicates that another'
		 unspecified - indicates that other front-end codec
		 will be used.

		 If this parameter is absent, ETSI ES 201 108
		 Front-end will be assumed.

 maxptime:  The maximum amount of media which can be encapsulated in
            each packet, expressed as time in milliseconds. The time
            shall be calculated as the sum of the time the media
            present in the packet represents. The time SHOULD be a
            multiple of the frame pair size (i.e., one FP <-> 20ms).

XX'assumed to 60ms'->'assumed to be 60ms'XX
	    If this parameter is not present, maxptime will be assumed
	    to 60ms.

XXWhat are all these <TBD>'s if you want to go to RFC status?XX

Encoding considerations : <TBD>

Security considerations : <TBD>

Interoperability considerations : <TBD>

Person & email address to contact for further information: <TBD>

Intended usage: COMMON. It is expected that many VoIP applications
(as well as mobile applications) will use this type.

Author/Change controller:
  <TBD>
  IETF Audio/Video transport working group


7. Security Considerations

Implementations using the payload defined in this specification are
subject to the security considerations discussed in the RTP
specification [RFC1889] and the RTP profile [RFC1890]. This payload
does not specify any different security services.


8. References


[ES201108] European Telecommunications Standards Institute (ETSI)
   Standard ES 201 108, "Speech Processing, Transmission and Quality
   Aspects (STQ); Distributed Speech Recognition; Front-end Feature
   Extraction Algorithm; Compression Algorithms," Ver. 1.1.2, April
   11, 2000. http://webapp.etsi.org/pda/home.asp?wki_id=9948

[RFC1889] H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson,
   "RTP: A transport protocol for real-time applications," Internet
   Draft, Internet Engineering Task Force, Feb. 1999 Work in progress,
   revision to RFC 1889.

[RFC1890] H. Schulzrinne and S. Casner, "RTP Profile for Audio and
   Video Conferences with Minimal Control," Internet Draft
   draft-ietf-avt-profile-new-08.txt, Work in Progress January 14,
   2000, revision to RFC 1890.

[RFC2016] Bradner, S., "The Internet Standards Process -- Revision 3",
   BCP 9, RFC 2026, October 1996.

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
   Requirement Levels", BCP 14, RFC 2119, March 1997

[RFC2508] S. Casner and V. Jacobson, "Compressing IP/UDP/RTP Headers
   for Low-Speed Serial Links," RFC 2508, February 1999.



9.   Acknowledgments

The design presented here benefits greatly from an earlier work on DSR
RTP payload design by Jeff Meunier. XX'Jeff Meunier'-> 'Jeff Meunier
and Priscilla Walther."  (Jeff and I worked on that one together.
You should add my name as a previous reference too.)XX


10. Author's Addresses

Qiaobing Xie                        Tel:   +1-847-632-3028
Motorola, Inc.                      EMail: qxie1@email.mot.com
1501 W. Shure Drive, 2-F9
Arlington Heights, IL 60004, USA

David Pearce                        Tel: +44 (0)1256 484 436
Motorola Labs                       EMail: bdp003@motorola.com
UK Research Laboratory
Jays Close
Viables Industrial Estate
Basingstoke, HANTS, RG22 4PD

Senaka Balasuriya                   Tel:   +1-630-353-8347
Motorola, Inc.              EMail: Senaka.Balasuriya@motorola.com
1411 Opus Place, Suite 350
Downers Grover, IL 60515, USA

Yoon Kim                            Tel: +1-408-768-4974
VerbalTek, Inc.                     EMail: yoonie@verbaltek.com
2921 Copper Rd.
Santa Clara, CA 95051

Stephane H. Maes                    Tel: +1-914-945-2908
IBM                                 EMail: smaes@us.ibm.com
TJ Watson Research Center
P.O. Box 218,
Yorktown Heights, NY 10598, USA.

Hari Garudadri                      Tel:
Qualcomm                            EMail: hgarudad@qualcomm.com







      This Internet Draft expires in 6 months from Nov. 2001.




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



From daemon@optimus.ietf.org  Wed Jan 30 14:09:18 2002
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 OAA29543
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 14:09:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17033
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 14:09:19 -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 OAA16632;
	Wed, 30 Jan 2002 14:04:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09588
	for <avt@ns.ietf.org>; Wed, 30 Jan 2002 03:13:03 -0500 (EST)
Received: from stsl.siemens.com.tw (stsl.siemens.com.tw [192.72.45.189])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12333
	for <avt@ietf.org>; Wed, 30 Jan 2002 03:12:59 -0500 (EST)
Received: from stslex.siemens.com.tw (stslex [140.231.62.94])
	by stsl.siemens.com.tw (8.11.6/8.11.6) with ESMTP id g0U8F9F27752
	for <avt@ietf.org>; Wed, 30 Jan 2002 16:15:09 +0800 (CST)
Received: by stslex.siemens.com.tw with Internet Mail Service (5.5.2653.19)
	id <CVTTM36M>; Wed, 30 Jan 2002 16:12:58 +0800
Message-ID: <92C0C0AC8AE8D411864300105A835CBB501708@stslex.siemens.com.tw>
From: Moter Du <moter.du@siemens.com>
To: "'avt@ietf.org'" <avt@ietf.org>
Date: Wed, 30 Jan 2002 16:11:46 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A965.C2525050"
Subject: [AVT] cRTP questions
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A965.C2525050
Content-Type: text/plain;
	charset="big5"

Hi,

Is the idea to compress IP/UDP/RTP strictly limited to low-speed serial
line?

The question comes from CSMA/CD, efficiency analysis in theory shows the
larger the frame is, the better the efficiency it achieves.  That means,
CSMA/CD link efficiency (e.g., fast-ethernet) wouldn't gain from header
compression, because the phsical frame is reduced while the headers are
reduced.  But meanwhile, I heard many companies claim their ethernet-based
VoIP gateways outperform due to cRTP.

Thanks.

Moter

------_=_NextPart_001_01C1A965.C2525050
Content-Type: text/html;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dbig5">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>cRTP questions</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>Is the idea to compress IP/UDP/RTP strictly limited =
to low-speed serial line?</FONT>
</P>

<P><FONT SIZE=3D2>The question comes from CSMA/CD, efficiency analysis =
in theory shows the larger the frame is, the better the efficiency it =
achieves.&nbsp; That means, CSMA/CD link efficiency (e.g., =
fast-ethernet) wouldn't gain from header compression, because the =
phsical frame is reduced while the headers are reduced.&nbsp; But =
meanwhile, I heard many companies claim their ethernet-based VoIP =
gateways outperform due to cRTP.</FONT></P>

<P><FONT SIZE=3D2>Thanks.</FONT>
</P>

<P><FONT SIZE=3D2>Moter</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A965.C2525050--


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



From daemon@optimus.ietf.org  Wed Jan 30 16:31:19 2002
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 QAA02625
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 16:31:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA24453
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 16:31:21 -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 QAA23918;
	Wed, 30 Jan 2002 16:27:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23889
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 16:27:14 -0500 (EST)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02532
	for <avt@ietf.org>; Wed, 30 Jan 2002 16:27:10 -0500 (EST)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate.mot.com (motgate 2.1) with ESMTP id OAA18784 for <avt@ietf.org>; Wed, 30 Jan 2002 14:27:12 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id OAA15806 for <avt@ietf.org>; Wed, 30 Jan 2002 14:16:05 -0700 (MST)]
Received: from quantix20.cig.mot.com (quantix20 [160.47.58.31])
	by relay1.cig.mot.com (8.11.4/8.11.4) with ESMTP id g0ULRB915200;
	Wed, 30 Jan 2002 15:27:11 -0600 (CST)
Received: from cig.mot.com (d50-384a.cig.mot.com [160.47.56.74])
	by quantix20.cig.mot.com (8.8.8+Sun/8.8.8) with ESMTP id PAA15681;
	Wed, 30 Jan 2002 15:32:00 -0600 (CST)
Message-ID: <3C586572.B8A206B2@cig.mot.com>
Date: Wed, 30 Jan 2002 15:28:18 -0600
From: Qiaobing Xie <xieqb@cig.mot.com>
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: AVT List <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] DSR/RTP demonstrated
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
Content-Transfer-Encoding: 7bit

FYI...

An inter-op testing/demonstration of DSR over RTP was conducted between
Motorola and SpeechWorks implementations and was reported in the news:

<http://www.businesswire.com/cgi-bin/f_headline.cgi?bw.012902/220292379&ticker=SPWX&ticker=MOT>

I was told that the implementations were based on a previous revision of
the draft but there is plan to update to the latest version.

-Qiaobing

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



From daemon@optimus.ietf.org  Wed Jan 30 19:41:52 2002
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 TAA05494
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 19:41:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA02500
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 19:41:52 -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 TAA01598;
	Wed, 30 Jan 2002 19:21:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01567
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 19:21:47 -0500 (EST)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05238
	for <avt@ietf.org>; Wed, 30 Jan 2002 19:21:45 -0500 (EST)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id RAA19590 for <avt@ietf.org>; Wed, 30 Jan 2002 17:21:46 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id RAA06703 for <avt@ietf.org>; Wed, 30 Jan 2002 17:21:45 -0700 (MST)]
Received: from quantix20.cig.mot.com (quantix20 [160.47.58.31])
	by relay1.cig.mot.com (8.11.4/8.11.4) with ESMTP id g0V0Lj927014;
	Wed, 30 Jan 2002 18:21:45 -0600 (CST)
Received: from cig.mot.com (d50-384a.cig.mot.com [160.47.56.74])
	by quantix20.cig.mot.com (8.8.8+Sun/8.8.8) with ESMTP id SAA15836;
	Wed, 30 Jan 2002 18:26:34 -0600 (CST)
Message-ID: <3C588E5C.D0851CE6@cig.mot.com>
Date: Wed, 30 Jan 2002 18:22:52 -0600
From: Qiaobing Xie <xieqb@cig.mot.com>
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Priscilla Walther <priscilla.walther@speechworks.com>
CC: avt@ietf.org
Subject: Re: [AVT] Review of draft-ietf-avt-dsr-00.txt
References: <ACEJIPIJFOPDOOMGEGBJAEELCKAA.priscilla.walther@speechworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hi, Priscilla,

Thanks for the comments. Please see my responses in-line....

Priscilla Walther wrote:
...snip....
> Speech Science Notes:
> - I'd add something regarding transmission of the DSR mime type
> registration.  Does that (or can that) happen at the beginning of each
> transmission?

The registered mime types will be used to build a session description
string as defined in SDP (session description protocol). But what
mechanism to use to pass this session description information to the
remote end is left to the application to decide. It is normally some
session control protocol, such as MGCP or MEGACO. This session
information normally is passed at the setup of a session (i.e., before
any speech frame is transmitted).

> 
> - there's no mention of endpointing or startpointing ... only that it
> happens on the client side ... it should make explicit mention of end- and
> start-  though.

I think this is sufficiently covered by the ETSI document which defines
the front-end (ie., client) behaviors. Am I right, David?

> 
> Editorial Notes:
> Global observations -
> * engin -> engine
> * if you've set up an abbreviation, use it (e.g., SE for Speech
> Engine, FP for frame pairs)
> * frame pairs not frame-pairs
> * paragraphs must have at least two sentences
> * I know what a Front-End is and how it relates to this spec,
>   but many readers may not.  Give a high-level description early
>   in the doc.
> * In general, if you are using speech reco terminology, you should
>   give a high-level description early in the doc and/or add a glossary.
> * add and use the following abbreviation:  FE for Front-End.

Agreed to all above. Will be make the changes. And I will incorporate
your in-line editorial changes as well.

regards,
-Qiaobing

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



From daemon@optimus.ietf.org  Wed Jan 30 20:36:48 2002
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 UAA06085
	for <avt-archive@odin.ietf.org>; Wed, 30 Jan 2002 20:36:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA04974
	for avt-archive@odin.ietf.org; Wed, 30 Jan 2002 20:36:49 -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 UAA04875;
	Wed, 30 Jan 2002 20:32:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA04846
	for <avt@optimus.ietf.org>; Wed, 30 Jan 2002 20:32:18 -0500 (EST)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06033
	for <avt@ietf.org>; Wed, 30 Jan 2002 20:32:16 -0500 (EST)
Received: from mira-sjcm-2.cisco.com (mira-sjcm-2.cisco.com [171.69.24.14])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id g0V1Vl623620;
	Wed, 30 Jan 2002 17:31:47 -0800 (PST)
Received: from tmima-w2k.cisco.com (sjc-vpn1-210.cisco.com [10.21.96.210])
	by mira-sjcm-2.cisco.com (Mirapoint)
	with ESMTP id ABO64334;
	Wed, 30 Jan 2002 17:31:25 -0800 (PST)
Message-Id: <4.3.2.7.2.20020130002955.03c35e90@mira-sjcm-2.cisco.com>
X-Sender: tmima@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 30 Jan 2002 17:13:04 -0800
To: somu@effnet.com, avt@ietf.org
From: Tmima Koren <tmima@cisco.com>
Subject: Re: [AVT] Enhanced CRTP Review
In-Reply-To: <3C55E0FA.4060007@effnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Hi Somu
Thanks for reviewing the Enhanced CRTP draft and especially for catching 
the ambiguity of the N in the CONTEXT_STATE packet.
We'll update the draft according to your suggestions
Thanks again
Tmima


At 04:38 PM 1/28/2002 -0700, Somasundaram Perianayagam wrote:
>Here's my review of Enhanced CRTP:
>
>Both my points are quite small. The draft looked great.
>
>1)
>
>"This document describes a header compression scheme for point to
>point links with packet loss and long delays."
>
>I guess it would be good if "packet loss" can be quantified here.
>You know like "links with high rate of packet loss".
>
>2)
>
>"CONTEXT_STATE packets SHOULD also be repeated N+1 times (using the
>same sequence number) to provide a similar measure of robustness
>against packet loss."
>
>Since we can maintain seperate N's for every context we have a question 
>here "what is N + 1 here?"
>
>To be safe you can assume N+1 to be the largest among the contexts for 
>which context repair is required.
>
>regards
>Somu
>
>Effnet Inc
>
>
>_______________________________________________
>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



From daemon@optimus.ietf.org  Thu Jan 31 03:22:28 2002
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 DAA21920
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 03:22:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA01146
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 03:22:30 -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 DAA01122;
	Thu, 31 Jan 2002 03:21:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01091
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 03:21:48 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21914
	for <avt@ietf.org>; Thu, 31 Jan 2002 03:21:44 -0500 (EST)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA09738
	for <avt@ietf.org>; Thu, 31 Jan 2002 09:21:40 +0100 (MET)
Received: from mchh159e.mch4.siemens.de ([139.21.130.171])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA19887
	for <avt@ietf.org>; Thu, 31 Jan 2002 09:21:40 +0100 (MET)
Received: by mchh159e.mch.pn.siemens.de with Internet Mail Service (5.5.2653.19)
	id <DW2FRB0N>; Thu, 31 Jan 2002 09:21:41 +0100
Message-ID: <DA6599EBFD6CF042B0B77964CFF620950BFD89@MCHH162E>
From: Euchner Martin  ICN M SR 3 <Martin.Euchner@icn.siemens.de>
To: "'avt@ietf.org'" <avt@ietf.org>,
        Euchner Martin  ICN M SR 3
	 <Martin.Euchner@icn.siemens.de>
Date: Thu, 31 Jan 2002 09:21:42 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [AVT] SRTP: (In)security of encrypted SID Frames - A new Security Threa
 t?
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

Dear SRTP and security experts,


This text raises a security concern upon the RTP payload voice encryption as
accomplished by SRTP for example. The conclusion is to further investigate
analysis of this security issue but also to consider this issue in the
security consideration section of SRTP.

Background
Certain voice codecs and voice compression algorithms provide the capability
of silence detection and silence suppression (see e.g. G.723.1, G.729AB,
G.728 and also new G.711 Appendix II). Instead of transmitting the sampled
silence signal itself, these schemes rather transmit silence parameters as
SID frames. The purpose of this mechanism is to reduce bandwidth on the wire
and generate comfort noise at the peer side when there isn't any significant
input signal at the source.

Basically, SID frames provide an indication of detected silence and the
duration of this event. SID frames usually provide compact parameters as
input to a noise generator on the recipient's end instead of the actual
sampled silence. Typically, SID frames are much shorter than encoded voice
payload; SID frames may even be of a short fixed length, as opposed to some
codecs in which voice frames are of variable length.

So far, multimedia security schemes such as SRTP encrypt all voice payload
regardless of its semantics and contents. Doing this is straightforward.
Thus, at present, SRTP does not distinguish between actual encoded voice
payload data and SID frames. All application layer plaintext content is
encrypted as ciphertext in the same manner.

Thesis
However, there are doubts on whether this security technique would not be
subject to the following security weakness:

While the purpose of encryption is to conceal the contents of the
transmitted data, the characteristics of SID frames would allow an attacker
intercepting ciphertext to deduce that encrypted SID frames were
transmitted. Thus, by traffic analysis, an attacker could distinguish
between encrypted SID frames and actual encrypted voide/video etc.

It is presumed and appears likely that SID frame patterns provide much less
entropy than any other regular voice data. This would be due to the fact
that the SID frame provides only very few parameters that would not change
dramatically from one SID frame to another. As such plaintext SID frame
content could probably be guessed with much higher probability than varying
voice content.

Assuming this to hold true however, would permit cryptoanalysts and
attackers specifically, to efficiently run known-plaintext attacks assuming
available ciphertext material by interception and guessed SID plaintexts.
While brute-force attacks on arbitrary ciphertext would be always possible
in theory, it is believed that brute-force attacks or known plaintext
attacks are infeasible in practice when assuming high entropy plaintext and
strong encryption ciphers.

Although SID frames would be encrypted, the presence of a SID frame could be
deduced as the ciphertext would be of shorter length typically. As a result
of a successful known-plaintext attack, the attacker would obtain the
session encryption key and thereby would be able to decrypt any encrypted
voice payload. This attack appears feasible when done off-line but depending
of the efficiency of the known-plaintext attack, an online attack might be
feasible as well. This would break the entire security scheme.

Conclusion
While the RTP payload encryption method as specified by SRTP has not been
proven broken yet, we believe that this issue as pointed out above should be
taken seriously. While any detailed analysis is not yet available, we see
enough motivation by the raised concern above, to further cryptanalyze the
ramifications of SID frame encryption. We encourage security experts to
think about the problem and attempt to prove or disprove the thesis. It is
to be noted, that a similar security concern might persist for encrypted
video frames as well for particular video codecs, where the video payload
headers were mostly constant or vary only moderately.

If the security issue would turn out to be true, we seek appropriate
technical countermeasures how to improve the multimedia payload encryption
method. One possibility could be not to encrypt SID frames but rather
transmit SID frames in plaintext. This would be acceptable and valid as the
content of a SID frame itself would not leak any confidential information to
an outsider. Doing this however, would make it necessary to in-band signal
within the RTP packet that certain payload was not encrypted and thereby let
the recipient selectively by-pass the decryption function. An appropriate
signalling means should be defined then.

In any way, it is proposed to address this security matter in the security
consideration section of SRTP.


I appreciate any comments and feedback on this matter and would particularly
like to know whether this issue has already been researched anywhere so far.


With kind regards

Martin Euchner.
-----------------------------------------------------------------------
| Dipl.-Inf.                     Rapporteur Q.G/SG16
| Martin Euchner                 Phone: +49 89 722 55790
| Siemens AG.....................Fax  : +49 89 722 47713
| ICN M SR 3                     mailto:Martin.Euchner@icn.siemens.de
|                                mailto:martin.euchner@ties.itu.int
| Hofmannstr. 51                 Intranet:
http://intranet.icn.siemens.de/marketing/cs27/topics/security/
| D-81359 Muenchen               Internet: http://www.siemens.de/
| __________________
| Germany     
-----------------------------------------------------------------------


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



From daemon@optimus.ietf.org  Thu Jan 31 03:51:14 2002
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 DAA22271
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 03:51:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA02806
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 03:51:12 -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 DAA02614;
	Thu, 31 Jan 2002 03:47:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02588
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 03:47:18 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22235
	for <avt@ietf.org>; Thu, 31 Jan 2002 03:47:10 -0500 (EST)
From: ari.lakaniemi@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0V8lGZ19374
	for <avt@ietf.org>; Thu, 31 Jan 2002 10:47:16 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58c8906d50ac158f22077@esvir02nok.ntc.nokia.com>;
 Thu, 31 Jan 2002 10:47:10 +0200
Received: from esebe014.NOE.Nokia.com ([172.21.138.53]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Thu, 31 Jan 2002 10:47:04 +0200
Received: from trebe004.NOE.Nokia.com ([172.22.232.177]) by esebe014.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 31 Jan 2002 10:47:00 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [AVT] New AMR draft available
Date: Thu, 31 Jan 2002 10:46:59 +0200
Message-ID: <481D6FFB3BD60E4CB590F39C59098400A430EB@trebe004.NOE.Nokia.com>
Thread-Topic: [AVT] New AMR draft available
Thread-Index: AcGplaEy5aaQivUeTM2q0+6G+ts9ZAAmTMvw
To: <Tobias.Faerber@mch.siemens.de>, <magnus.westerlund@era.ericsson.se>,
        <avt@ietf.org>
X-OriginalArrivalTime: 31 Jan 2002 08:47:00.0149 (UTC) FILETIME=[D8DCD650:01C1AA33]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA02589
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
Content-Transfer-Encoding: 8bit

hello Tobias,

> 
> hi all,
> please include like in draft10 (2.7) an own little section 
> describing which
> part is to be considered mandatory and which is optional ? i 
> know there is
> written something in 4.2 but to make it easier for 
> implementers all features
> and the their implementation considerations should be given globally.
> 

As you mention, section 4.2 says that robust sorting, interleaving and frame CRCs are optional. But it really could be a good idea to edit the wording a bit to state this more clearly.

> is multichannel support optional ? I guess yes....
> 

Support for multichannel operation is optional, the number of channels can be explicitly specified in session setup and can therefore be forced to be one.
I hope this is indicated clearly enough by following quotations from the draft.

Excerpt from section 3.5 Support for Multi-Channel Session:
"
   At the session setup, out-of-band signalling, e.g., using the
   rtpmap attribute in SDP, must be used to indicate the number of
   channels in the session and the order of the speech frames from
   different channels in each frame-block.
"

Furthermore, in section 8.3. Mapping MIME Parameters into SDP the drafts says:
"
    - The MIME subtype (payload format name) goes in SDP "a=rtpmap" as
      the encoding name.  The RTP clock rate in "a=rtpmap" MUST be
      8000 for AMR and 16000 for AMR-WB, and the encoding parameters
      (number of channels) MUST either be explicitly set to N or
      omitted, implying a default value of 1. The values of N that are
      allowed is specified in Section 4.1 in [24].
"

> about fomatting: to my opinion it would be nice to include 
> the hint for bit
> sorting into classes that the tables of Annex B in TS26.101 
> should be used
> 

I think the bit-sorting issue is taken care of by the references to 3GPP specifications (from section 4.3.3. Speech Data):
"
   ... The order and numbering notation of the
   bits are as specified for Interface Format 1 (IF1) in [2] for AMR
   and [4] for AMR-WB. As specified there, the bits of speech frames
   have been rearranged in order of decreasing sensitivity, while the
   bits of comfort noise frames are in the order produced by the
   encoder. The resulting bit sequence for a frame of length K bits
   is denoted d(0), d(1), ..., d(K-1).
"
where [2] and [4] are references to 3GPP frame format documents for AMR and AMR-WB, respectively. These documents specify the bit ordering for both codecs.
Do you think this is not clear enough definition?

> best,
> Tobi
> 

br,
Ari

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



From daemon@optimus.ietf.org  Thu Jan 31 05:19:34 2002
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 FAA23047
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 05:19:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA06777
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 05:19:38 -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 FAA06662;
	Thu, 31 Jan 2002 05:17:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA06637
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 05:16:58 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23021
	for <avt@ietf.org>; Thu, 31 Jan 2002 05:16:53 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g0VAGuX4007819
	for <avt@ietf.org>; Thu, 31 Jan 2002 11:16:56 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Thu Jan 31 11:16:52 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKC0AJA>; Thu, 31 Jan 2002 11:07:37 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D83F107@Esealnt877.al.sw.ericsson.se>
From: "Elisabetta Carrara (ERA)" <Elisabetta.Carrara@era.ericsson.se>
To: "'avt@ietf.org'" <avt@ietf.org>
Cc: "'Euchner Martin  ICN M SR 3'" <Martin.Euchner@icn.siemens.de>
Subject: RE: [AVT] SRTP: (In)security of encrypted SID Frames - A new Secu
	rity Threa t?
Date: Thu, 31 Jan 2002 11:16:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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


Hi Martin!

The attack model considered when designing stream ciphers
*is* that large amounts of plaintext are known. 
A cipher whose security would depend on plaintext entropy 
would be completely unacceptable. 

In SRTP we use AES in counter mode (or f8 mode). Both of these modes
are provably secure under the assumption that AES is a "pseudo random
permutation" (which is widely believed). The proof of security implies 
the following: even if an attacker has a large amount of known plaintext
(and thus, knows the output of the corresponding keystream segments), 
it will in no way help him to deduce *any* non-trivial information about 
an unknown plaintext portion.

If they did, there would be a fundamental design flaw in AES, 
which would probably render all use of AES insecure.

Thus, your concern is a general stream cipher issue. The alternative,
using a block cipher would be completely unacceptable from wireless
(bit-error) point of view. Moreover, except for the fact that a block cipher can
(marginally) conceal the length (up to block boundaries), there is really nothing
that suggests that AES is more or less secure when runs as a block cipher, or
as a stream cipher.

Section 10.3 does consider the issue. We can expand it, and also add something like:

"Due to the way a stream cipher combines plaintext
with its output, (secure) stream ciphers are designed to resist known
plaintext attacks."

thanks, 
cheers,

/Mats & Elisabetta


> -----Original Message-----
> From: Euchner Martin ICN M SR 3 [mailto:Martin.Euchner@icn.siemens.de]
> Sent: den 31 januari 2002 09:22
> To: 'avt@ietf.org'; Euchner Martin ICN M SR 3
> Subject: [AVT] SRTP: (In)security of encrypted SID Frames - A new
> Security Threa t?
> 
> 
> Dear SRTP and security experts,
> 
> 
> This text raises a security concern upon the RTP payload 
> voice encryption as
> accomplished by SRTP for example. The conclusion is to 
> further investigate
> analysis of this security issue but also to consider this issue in the
> security consideration section of SRTP.
> 
> Background
> Certain voice codecs and voice compression algorithms provide 
> the capability
> of silence detection and silence suppression (see e.g. 
> G.723.1, G.729AB,
> G.728 and also new G.711 Appendix II). Instead of 
> transmitting the sampled
> silence signal itself, these schemes rather transmit silence 
> parameters as
> SID frames. The purpose of this mechanism is to reduce 
> bandwidth on the wire
> and generate comfort noise at the peer side when there isn't 
> any significant
> input signal at the source.
> 
> Basically, SID frames provide an indication of detected 
> silence and the
> duration of this event. SID frames usually provide compact 
> parameters as
> input to a noise generator on the recipient's end instead of 
> the actual
> sampled silence. Typically, SID frames are much shorter than 
> encoded voice
> payload; SID frames may even be of a short fixed length, as 
> opposed to some
> codecs in which voice frames are of variable length.
> 
> So far, multimedia security schemes such as SRTP encrypt all 
> voice payload
> regardless of its semantics and contents. Doing this is 
> straightforward.
> Thus, at present, SRTP does not distinguish between actual 
> encoded voice
> payload data and SID frames. All application layer plaintext 
> content is
> encrypted as ciphertext in the same manner.
> 
> Thesis
> However, there are doubts on whether this security technique 
> would not be
> subject to the following security weakness:
> 
> While the purpose of encryption is to conceal the contents of the
> transmitted data, the characteristics of SID frames would 
> allow an attacker
> intercepting ciphertext to deduce that encrypted SID frames were
> transmitted. Thus, by traffic analysis, an attacker could distinguish
> between encrypted SID frames and actual encrypted voide/video etc.
> 
> It is presumed and appears likely that SID frame patterns 
> provide much less
> entropy than any other regular voice data. This would be due 
> to the fact
> that the SID frame provides only very few parameters that 
> would not change
> dramatically from one SID frame to another. As such plaintext 
> SID frame
> content could probably be guessed with much higher 
> probability than varying
> voice content.
> 
> Assuming this to hold true however, would permit cryptoanalysts and
> attackers specifically, to efficiently run known-plaintext 
> attacks assuming
> available ciphertext material by interception and guessed SID 
> plaintexts.
> While brute-force attacks on arbitrary ciphertext would be 
> always possible
> in theory, it is believed that brute-force attacks or known plaintext
> attacks are infeasible in practice when assuming high entropy 
> plaintext and
> strong encryption ciphers.
> 
> Although SID frames would be encrypted, the presence of a SID 
> frame could be
> deduced as the ciphertext would be of shorter length 
> typically. As a result
> of a successful known-plaintext attack, the attacker would obtain the
> session encryption key and thereby would be able to decrypt 
> any encrypted
> voice payload. This attack appears feasible when done 
> off-line but depending
> of the efficiency of the known-plaintext attack, an online 
> attack might be
> feasible as well. This would break the entire security scheme.
> 
> Conclusion
> While the RTP payload encryption method as specified by SRTP 
> has not been
> proven broken yet, we believe that this issue as pointed out 
> above should be
> taken seriously. While any detailed analysis is not yet 
> available, we see
> enough motivation by the raised concern above, to further 
> cryptanalyze the
> ramifications of SID frame encryption. We encourage security 
> experts to
> think about the problem and attempt to prove or disprove the 
> thesis. It is
> to be noted, that a similar security concern might persist 
> for encrypted
> video frames as well for particular video codecs, where the 
> video payload
> headers were mostly constant or vary only moderately.
> 
> If the security issue would turn out to be true, we seek appropriate
> technical countermeasures how to improve the multimedia 
> payload encryption
> method. One possibility could be not to encrypt SID frames but rather
> transmit SID frames in plaintext. This would be acceptable 
> and valid as the
> content of a SID frame itself would not leak any confidential 
> information to
> an outsider. Doing this however, would make it necessary to 
> in-band signal
> within the RTP packet that certain payload was not encrypted 
> and thereby let
> the recipient selectively by-pass the decryption function. An 
> appropriate
> signalling means should be defined then.
> 
> In any way, it is proposed to address this security matter in 
> the security
> consideration section of SRTP.
> 
> 
> I appreciate any comments and feedback on this matter and 
> would particularly
> like to know whether this issue has already been researched 
> anywhere so far.
> 
> 
> With kind regards
> 
> Martin Euchner.
> --------------------------------------------------------------
> ---------
> | Dipl.-Inf.                     Rapporteur Q.G/SG16
> | Martin Euchner                 Phone: +49 89 722 55790
> | Siemens AG.....................Fax  : +49 89 722 47713
> | ICN M SR 3                     mailto:Martin.Euchner@icn.siemens.de
> |                                mailto:martin.euchner@ties.itu.int
> | Hofmannstr. 51                 Intranet:
> http://intranet.icn.siemens.de/marketing/cs27/topics/security/
> | D-81359 Muenchen               Internet: http://www.siemens.de/
> | __________________
> | Germany     
> --------------------------------------------------------------
> ---------
> 
> 
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Thu Jan 31 05:40:03 2002
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 FAA23261
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 05:40:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA07791
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 05:40:07 -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 FAA07778;
	Thu, 31 Jan 2002 05:39:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA07747
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 05:39:13 -0500 (EST)
Received: from cnxtmgmt1.conexant.com (cnxtsmtp1.conexant.com [198.62.9.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23251
	for <avt@ietf.org>; Thu, 31 Jan 2002 05:39:08 -0500 (EST)
From: michael.whitfield@mindspeed.com
Received: from npblnh1.nb.mindspeed.com (npblnh1.la.mindspeed.com [10.231.18.16])
	by cnxtmgmt1.conexant.com (8.9.3/8.9.3) with ESMTP id CAA23006
	for <avt@ietf.org>; Thu, 31 Jan 2002 02:39:11 -0800 (PST)
Received: from sophiam1.sophia.mindspeed.com ([10.1.124.21])
          by npblnh1.nb.mindspeed.com (Lotus Domino Release 5.0.8)
          with ESMTP id 2002013102391072:22332 ;
          Thu, 31 Jan 2002 02:39:10 -0800 
To: "'avt@ietf.org'" <avt@ietf.org>
Subject: Re: [AVT] cRTP questions
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF2B32DE1D.C6A93A2A-ONC1256B52.003A8D15@sophia.mindspeed.com>
Date: Thu, 31 Jan 2002 11:47:47 +0100
X-MIMETrack: Serialize by Router on SOPHIAM1/Server/Mindspeed(Release 5.0.8 |June 18, 2001) at
 01/31/2002 11:47:47 AM,
	Serialize complete at 01/31/2002 11:47:47 AM,
	Itemize by SMTP Server on NPBLNH1/Server/Conexant(Release 5.0.8 |June 18, 2001) at
 01/31/2002 02:39:10 AM,
	Serialize by Router on NPBLNH1/Server/Conexant(Release 5.0.8 |June 18, 2001) at
 01/31/2002 02:39:12 AM,
	Serialize complete at 01/31/2002 02:39:12 AM
Content-Type: multipart/alternative; boundary="=_alternative 003A3DAEC1256B52_="
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

This is a multipart message in MIME format.
--=_alternative 003A3DAEC1256B52_=
Content-Type: text/plain; charset="us-ascii"

Efficiency can be misleading.  If you measure efficiency as the total 
number of bytes sent in a given period, then having extra bytes increases 
your efficiency (even if these bytes are just padding).  But if you 
measure efficiency as the number of useful bytes sent in a given period, 
extra bytes decrease your efficiency.

Michael.





Moter Du <moter.du@siemens.com>
Sent by: avt-admin@ietf.org
30/01/02 09:11

 
        To:     "'avt@ietf.org'" <avt@ietf.org>
        cc: 
        Subject:        [AVT] cRTP questions


Hi, 
Is the idea to compress IP/UDP/RTP strictly limited to low-speed serial 
line? 
The question comes from CSMA/CD, efficiency analysis in theory shows the 
larger the frame is, the better the efficiency it achieves.  That means, 
CSMA/CD link efficiency (e.g., fast-ethernet) wouldn't gain from header 
compression, because the phsical frame is reduced while the headers are 
reduced.  But meanwhile, I heard many companies claim their ethernet-based 
VoIP gateways outperform due to cRTP.
Thanks. 
Moter 


--=_alternative 003A3DAEC1256B52_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Efficiency can be misleading. &nbsp;If you measure efficiency as the total number of bytes sent in a given period, then having extra bytes increases your efficiency (even if these bytes are just padding). &nbsp;But if you measure efficiency as the number of useful bytes sent in a given period, extra bytes decrease your efficiency.</font>
<br>
<br><font size=2 face="sans-serif">Michael.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Moter Du &lt;moter.du@siemens.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: avt-admin@ietf.org</font>
<p><font size=1 face="sans-serif">30/01/02 09:11</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;'avt@ietf.org'&quot; &lt;avt@ietf.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;[AVT] cRTP questions</font></table>
<br>
<br>
<br><font size=2 face="Arial">Hi,</font><font size=3 face="Arial"> </font>
<p><font size=2 face="Arial">Is the idea to compress IP/UDP/RTP strictly limited to low-speed serial line?</font><font size=3 face="Arial"> </font>
<p><font size=2 face="Arial">The question comes from CSMA/CD, efficiency analysis in theory shows the larger the frame is, the better the efficiency it achieves. &nbsp;That means, CSMA/CD link efficiency (e.g., fast-ethernet) wouldn't gain from header compression, because the phsical frame is reduced while the headers are reduced. &nbsp;But meanwhile, I heard many companies claim their ethernet-based VoIP gateways outperform due to cRTP.</font>
<p><font size=2 face="Arial">Thanks.</font><font size=3 face="Arial"> </font>
<p><font size=2 face="Arial">Moter</font><font size=3 face="Arial"> </font>
<p>
<p>
--=_alternative 003A3DAEC1256B52_=--

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



From daemon@optimus.ietf.org  Thu Jan 31 06:07:26 2002
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 GAA23468
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 06:07:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA08866
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 06:07:30 -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 GAA08710;
	Thu, 31 Jan 2002 06:03:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA08678
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 06:03:39 -0500 (EST)
Received: from nero.informatik.uni-wuerzburg.de (root@wi3x05.informatik.uni-wuerzburg.de [132.187.106.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23411
	for <avt@ietf.org>; Thu, 31 Jan 2002 06:03:34 -0500 (EST)
Received: from informatik.uni-wuerzburg.de (vesta.informatik.uni-wuerzburg.de [132.187.106.113])
	by nero.informatik.uni-wuerzburg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id g0VArUE05402
	for <avt@ietf.org>; Thu, 31 Jan 2002 11:53:30 +0100
Message-ID: <3C5927BA.B89F2A22@informatik.uni-wuerzburg.de>
Date: Thu, 31 Jan 2002 12:17:14 +0100
From: Michael Menth <menth@informatik.uni-wuerzburg.de>
Organization: =?iso-8859-1?Q?Universit=E4t=20W=FCrzburg?=
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "'avt@ietf.org'" <avt@ietf.org>
Subject: Re: [AVT] cRTP questions
References: <OF2B32DE1D.C6A93A2A-ONC1256B52.003A8D15@sophia.mindspeed.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit


Hi,

I did some investigations on the performance of tunneling compressed 
RTP aka RTP multiplexing that focuses on the sent useful bytes: 
http://www-info3.informatik.uni-wuerzburg.de/~menth/Publications/itc-ss12.pdf
http://www-info3.informatik.uni-wuerzburg.de/~menth/Publications/PROMS2000.pdf

With simple compressed RTP payload this is similar. In particular we 
made a study on compressed RTP/UDP/IP/MPLS headers:
http://www-info3.informatik.uni-wuerzburg.de/TR/tr291.pdf

Kind regards, Michael


michael.whitfield@mindspeed.com wrote:
> 
> Efficiency can be misleading.  If you measure efficiency as the total
> number of bytes sent in a given period, then having extra bytes
> increases your efficiency (even if these bytes are just padding).  But
> if you measure efficiency as the number of useful bytes sent in a
> given period, extra bytes decrease your efficiency.
> 
> Michael.
> 
>   Moter Du <moter.du@siemens.com>
>   Sent by: avt-admin@ietf.org             To:        "'avt@ietf.org'"
>                                   <avt@ietf.org>
>   30/01/02 09:11                          cc:
>                                           Subject:        [AVT] cRTP
>                                   questions
> 
> Hi,
> 
> Is the idea to compress IP/UDP/RTP strictly limited to low-speed
> serial line?
> 
> The question comes from CSMA/CD, efficiency analysis in theory shows
> the larger the frame is, the better the efficiency it achieves.  That
> means, CSMA/CD link efficiency (e.g., fast-ethernet) wouldn't gain
> from header compression, because the phsical frame is reduced while
> the headers are reduced.  But meanwhile, I heard many companies claim
> their ethernet-based VoIP gateways outperform due to cRTP.
> 
> Thanks.
> 
> Moter

-- 
Dipl.-Inform. Michael Menth
University of Wuerzburg, Institute of Computer Science
Am Hubland, D-97074 Wuerzburg, Germany, room A212
phone: (+49)-931/888-6644, fax: (+49)-931/888-6632
mailto:menth@informatik.uni-wuerzburg.de
http://www-info3.informatik.uni-wuerzburg.de/~menth

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



From daemon@optimus.ietf.org  Thu Jan 31 06:30:10 2002
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 GAA23657
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 06:30:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA09785
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 06:30:13 -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 GAA09653;
	Thu, 31 Jan 2002 06:29:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA09563
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 06:29:15 -0500 (EST)
Received: from stsl.siemens.com.tw (stsl.siemens.com.tw [192.72.45.189])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23628
	for <avt@ietf.org>; Thu, 31 Jan 2002 06:29:11 -0500 (EST)
Received: from stslex.siemens.com.tw (stslex [140.231.62.94])
	by stsl.siemens.com.tw (8.11.6/8.11.6) with ESMTP id g0VBV4F23707;
	Thu, 31 Jan 2002 19:31:04 +0800 (CST)
Received: by stslex.siemens.com.tw with Internet Mail Service (5.5.2653.19)
	id <CVTTMVZS>; Thu, 31 Jan 2002 19:28:54 +0800
Message-ID: <92C0C0AC8AE8D411864300105A835CBB501713@stslex.siemens.com.tw>
From: Moter Du <moter.du@siemens.com>
To: "'michael.whitfield@mindspeed.com'" <michael.whitfield@mindspeed.com>
Cc: "'avt@ietf.org'" <avt@ietf.org>
Subject: RE: [AVT] cRTP questions
Date: Thu, 31 Jan 2002 19:26:59 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA4A.327DEDA0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA4A.327DEDA0
Content-Type: text/plain

Totally agree your words, but they're not what I was pointing.

Given a number of transmitting stations, transmission rate, media type,
etc., mostly the average efficiency (utilization, throughput, whatever) can
be figured out.  No more and less in average.  That case compression
technologies are normally developped under certain consumptions.

My questions came from some commercial announcements which almost misled me
(can't deny, I'm rather new in this area).  And surely now I understand many
rely on underlying multiplexing/segmentation/others capabilities to optimize
the efficiency.  Thanks for your advice.

Moter


-----Original Message-----
From: michael.whitfield@mindspeed.com
[mailto:michael.whitfield@mindspeed.com]
Sent: Thursday, January 31, 2002 6:48 PM
To: 'avt@ietf.org'
Subject: Re: [AVT] cRTP questions



Efficiency can be misleading.  If you measure efficiency as the total number
of bytes sent in a given period, then having extra bytes increases your
efficiency (even if these bytes are just padding).  But if you measure
efficiency as the number of useful bytes sent in a given period, extra bytes
decrease your efficiency. 

Michael. 



Moter Du <moter.du@siemens.com> 
Sent by: avt-admin@ietf.org 
30/01/02 09:11 
        
        To:        "'avt@ietf.org'" <avt@ietf.org> 
        cc:         
        Subject:        [AVT] cRTP questions



Hi, 
Is the idea to compress IP/UDP/RTP strictly limited to low-speed serial
line? 
The question comes from CSMA/CD, efficiency analysis in theory shows the
larger the frame is, the better the efficiency it achieves.  That means,
CSMA/CD link efficiency (e.g., fast-ethernet) wouldn't gain from header
compression, because the phsical frame is reduced while the headers are
reduced.  But meanwhile, I heard many companies claim their ethernet-based
VoIP gateways outperform due to cRTP. 
Thanks. 
Moter 

------_=_NextPart_001_01C1AA4A.327DEDA0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [AVT] cRTP questions</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Totally agree your words, but they're not what I was =
pointing.</FONT>
</P>

<P><FONT SIZE=3D2>Given a number of transmitting stations, transmission =
rate, media type, etc., mostly the average efficiency (utilization, =
throughput, whatever) can be figured out.&nbsp; No more and less in =
average.&nbsp; That case compression technologies are normally =
developped under certain consumptions.</FONT></P>

<P><FONT SIZE=3D2>My questions came from some commercial announcements =
which almost misled me (can't deny, I'm rather new in this area).&nbsp; =
And surely now I understand many rely on underlying =
multiplexing/segmentation/others capabilities to optimize the =
efficiency.&nbsp; Thanks for your advice.</FONT></P>

<P><FONT SIZE=3D2>Moter</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: michael.whitfield@mindspeed.com [<A =
HREF=3D"mailto:michael.whitfield@mindspeed.com">mailto:michael.whitfield=
@mindspeed.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 31, 2002 6:48 PM</FONT>
<BR><FONT SIZE=3D2>To: 'avt@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [AVT] cRTP questions</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Efficiency can be misleading.&nbsp; If you measure =
efficiency as the total number of bytes sent in a given period, then =
having extra bytes increases your efficiency (even if these bytes are =
just padding).&nbsp; But if you measure efficiency as the number of =
useful bytes sent in a given period, extra bytes decrease your =
efficiency. </FONT></P>

<P><FONT SIZE=3D2>Michael. </FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Moter Du &lt;moter.du@siemens.com&gt; </FONT>
<BR><FONT SIZE=3D2>Sent by: avt-admin@ietf.org </FONT>
<BR><FONT SIZE=3D2>30/01/02 09:11 </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
To:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;'avt@ietf.org'&quot; &lt;avt@ietf.org&gt; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
cc:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [AVT] cRTP =
questions</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi, </FONT>
<BR><FONT SIZE=3D2>Is the idea to compress IP/UDP/RTP strictly limited =
to low-speed serial line? </FONT>
<BR><FONT SIZE=3D2>The question comes from CSMA/CD, efficiency analysis =
in theory shows the larger the frame is, the better the efficiency it =
achieves.&nbsp; That means, CSMA/CD link efficiency (e.g., =
fast-ethernet) wouldn't gain from header compression, because the =
phsical frame is reduced while the headers are reduced.&nbsp; But =
meanwhile, I heard many companies claim their ethernet-based VoIP =
gateways outperform due to cRTP. </FONT></P>

<P><FONT SIZE=3D2>Thanks. </FONT>
<BR><FONT SIZE=3D2>Moter </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1AA4A.327DEDA0--

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



From daemon@optimus.ietf.org  Thu Jan 31 07:04:41 2002
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 HAA24126
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 07:04:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA11520
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 07:04:44 -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 HAA10939;
	Thu, 31 Jan 2002 07:00:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10901
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 07:00:10 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23871;
	Thu, 31 Jan 2002 07:00:07 -0500 (EST)
Message-Id: <200201311200.HAA23871@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: avt@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 31 Jan 2002 07:00:06 -0500
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-amr-11.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.

	Title		: RTP payload format and file storage format for AMR and
                          AMR-WB audio
	Author(s)	: J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie
	Filename	: draft-ietf-avt-rtp-amr-11.txt
	Pages		: 41
	Date		: 30-Jan-02
	
This document specifies a real-time transport protocol (RTP)
payload format to be used for AMR and AMR-WB encoded speech
signals. The payload format is designed to be able to interoperate
with existing AMR and AMR-WB transport formats on non-IP
networks. In addition, a file format is specified for transport of
AMR and AMR-WB speech data in storage mode applications such as
email. Two separate MIME type registrations are included, one for
AMR and one for AMR-WB, specifying use of both the RTP payload
format and the storage format.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amr-11.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-avt-rtp-amr-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-amr-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020130093619.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-amr-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtp-amr-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020130093619.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Thu Jan 31 08:52:41 2002
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 IAA26433
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 08:52:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA16402
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 08:52:45 -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 IAA16224;
	Thu, 31 Jan 2002 08:48:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16196
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 08:48:23 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26249
	for <avt@ietf.org>; Thu, 31 Jan 2002 08:48:18 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA09903;
	Thu, 31 Jan 2002 14:48:18 +0100 (MET)
Received: from mchh9eea.mchh.siemens.de (mchh9eea.mchh.siemens.de [139.21.204.218])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA24294;
	Thu, 31 Jan 2002 14:48:19 +0100 (MET)
Received: by mchh9eea.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <D6SPT8SZ>; Thu, 31 Jan 2002 14:46:38 +0100
Message-ID: <07B0CDE3B76AD31190F700508B5D5D1DDF556F@mchg9eba.mchh.siemens.de>
From: Faerber Tobias ICM MP PO8 RD MCH83 <Tobias.Faerber@mch.siemens.de>
To: "'ari.lakaniemi@nokia.com'" <ari.lakaniemi@nokia.com>,
        magnus.westerlund@era.ericsson.se, avt@ietf.org
Subject: RE: [AVT] New AMR draft available
Date: Thu, 31 Jan 2002 14:48:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

hi,
everythiong which is to be known you can find in the text but if you start
out implementing it is the easiest to have an own section containing a
mandatory and optional hint. currently we and some other companies are doing
interop testing at IMTC and it shows that such a clear statement makes work
much easier instead of having to search through the reffering passeges in
the text.
just two lines or like that:

X.x Implementation rules

mandatory features: bw eff. mode, octet alignment
optional features : robust sorting,CRC,interleavin, multichannel support


about sorting:
of course it is clear. just wanted to point it out more directly. 

best regards,
Tobi

----------------------------------------------------------------------------
-------
> Faerber Tobias		Siemens AG
ICM MP PO8 RD MCH83 	Information and Communication Mobile

> Tel:	+49 89 722 58578	Grillparzerstrasse 10 a
> mobile:  +49 175 5721351	81675 Munich, Germany
> Fax:	+49 89 722 59070	
mailto:tobias.faerber@mch.siemens.de
----------------------------------------------------------------------------
-------


> -----Original Message-----
> From: ari.lakaniemi@nokia.com [mailto:ari.lakaniemi@nokia.com]
> Sent: Donnerstag, 31. Januar 2002 09:47
> To: Faerber Tobias ICM MP PO8 RD MCH83;
> magnus.westerlund@era.ericsson.se; avt@ietf.org
> Subject: RE: [AVT] New AMR draft available
> 
> 
> hello Tobias,
> 
> > 
> > hi all,
> > please include like in draft10 (2.7) an own little section 
> > describing which
> > part is to be considered mandatory and which is optional ? i 
> > know there is
> > written something in 4.2 but to make it easier for 
> > implementers all features
> > and the their implementation considerations should be given 
> globally.
> > 
> 
> As you mention, section 4.2 says that robust sorting, 
> interleaving and frame CRCs are optional. But it really could 
> be a good idea to edit the wording a bit to state this more clearly.
> 
> > is multichannel support optional ? I guess yes....
> > 
> 
> Support for multichannel operation is optional, the number of 
> channels can be explicitly specified in session setup and can 
> therefore be forced to be one.
> I hope this is indicated clearly enough by following 
> quotations from the draft.
> 
> Excerpt from section 3.5 Support for Multi-Channel Session:
> "
>    At the session setup, out-of-band signalling, e.g., using the
>    rtpmap attribute in SDP, must be used to indicate the number of
>    channels in the session and the order of the speech frames from
>    different channels in each frame-block.
> "
> 
> Furthermore, in section 8.3. Mapping MIME Parameters into SDP 
> the drafts says:
> "
>     - The MIME subtype (payload format name) goes in SDP "a=rtpmap" as
>       the encoding name.  The RTP clock rate in "a=rtpmap" MUST be
>       8000 for AMR and 16000 for AMR-WB, and the encoding parameters
>       (number of channels) MUST either be explicitly set to N or
>       omitted, implying a default value of 1. The values of N that are
>       allowed is specified in Section 4.1 in [24].
> "
> 
> > about fomatting: to my opinion it would be nice to include 
> > the hint for bit
> > sorting into classes that the tables of Annex B in TS26.101 
> > should be used
> > 
> 
> I think the bit-sorting issue is taken care of by the 
> references to 3GPP specifications (from section 4.3.3. Speech Data):
> "
>    ... The order and numbering notation of the
>    bits are as specified for Interface Format 1 (IF1) in [2] for AMR
>    and [4] for AMR-WB. As specified there, the bits of speech frames
>    have been rearranged in order of decreasing sensitivity, while the
>    bits of comfort noise frames are in the order produced by the
>    encoder. The resulting bit sequence for a frame of length K bits
>    is denoted d(0), d(1), ..., d(K-1).
> "
> where [2] and [4] are references to 3GPP frame format 
> documents for AMR and AMR-WB, respectively. These documents 
> specify the bit ordering for both codecs.
> Do you think this is not clear enough definition?
> 
> > best,
> > Tobi
> > 
> 
> br,
> Ari
> 

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



From daemon@optimus.ietf.org  Thu Jan 31 09:17:58 2002
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 JAA27283
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 09:17:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA18361
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 09:18:02 -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 JAA18131;
	Thu, 31 Jan 2002 09:13:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA18101
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 09:13:33 -0500 (EST)
Received: from speechworks.com (valmiki.speechworks.com [63.113.17.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27132
	for <avt@ietf.org>; Thu, 31 Jan 2002 09:13:28 -0500 (EST)
Received: from vishnu.speechworks.com (mailhost.speechworks.com [206.234.64.17])
	by speechworks.com (8.10.2+Sun/8.9.3) with ESMTP id g0VEHcY08099;
	Thu, 31 Jan 2002 09:17:38 -0500 (EST)
Received: from galaxy (localhost [127.0.0.1])
	by vishnu.speechworks.com (8.10.2+Sun/8.9.3) with SMTP id g0VEDTP07810;
	Thu, 31 Jan 2002 09:13:29 -0500 (EST)
From: "Priscilla Walther" <priscilla.walther@speechworks.com>
To: "Qiaobing Xie" <xieqb@cig.mot.com>
Cc: <avt@ietf.org>
Subject: RE: [AVT] Review of draft-ietf-avt-dsr-00.txt
Date: Thu, 31 Jan 2002 09:13:29 -0500
Message-ID: <ACEJIPIJFOPDOOMGEGBJEEFHCKAA.priscilla.walther@speechworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3C588E5C.D0851CE6@cig.mot.com>
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Thanks Qiaobing.  I'll pass your comments back to our speech scientist.
In the mean time, if anyone else sends me comments and I don't reply, 
please know that I'm on vacation in three hours :-) so I won't be able
to get back to you for a couple of weeks.  

Kind regards,

Pris


> -----Original Message-----
> From: Qiaobing Xie [mailto:xieqb@cig.mot.com]
> Sent: Wednesday, January 30, 2002 7:23 PM
> To: Priscilla Walther
> Cc: avt@ietf.org
> Subject: Re: [AVT] Review of draft-ietf-avt-dsr-00.txt
> 
> 
> Hi, Priscilla,
> 
> Thanks for the comments. Please see my responses in-line....
> 
> Priscilla Walther wrote:
> ...snip....
> > Speech Science Notes:
> > - I'd add something regarding transmission of the DSR mime type
> > registration.  Does that (or can that) happen at the beginning of each
> > transmission?
> 
> The registered mime types will be used to build a session description
> string as defined in SDP (session description protocol). But what
> mechanism to use to pass this session description information to the
> remote end is left to the application to decide. It is normally some
> session control protocol, such as MGCP or MEGACO. This session
> information normally is passed at the setup of a session (i.e., before
> any speech frame is transmitted).
> 
> > 
> > - there's no mention of endpointing or startpointing ... only that it
> > happens on the client side ... it should make explicit mention 
> of end- and
> > start-  though.
> 
> I think this is sufficiently covered by the ETSI document which defines
> the front-end (ie., client) behaviors. Am I right, David?
> 
> > 
> > Editorial Notes:
> > Global observations -
> > * engin -> engine
> > * if you've set up an abbreviation, use it (e.g., SE for Speech
> > Engine, FP for frame pairs)
> > * frame pairs not frame-pairs
> > * paragraphs must have at least two sentences
> > * I know what a Front-End is and how it relates to this spec,
> >   but many readers may not.  Give a high-level description early
> >   in the doc.
> > * In general, if you are using speech reco terminology, you should
> >   give a high-level description early in the doc and/or add a glossary.
> > * add and use the following abbreviation:  FE for Front-End.
> 
> Agreed to all above. Will be make the changes. And I will incorporate
> your in-line editorial changes as well.
> 
> regards,
> -Qiaobing
> 

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



From daemon@optimus.ietf.org  Thu Jan 31 11:52:02 2002
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 LAA02999
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 11:52:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA04103
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 11:52:05 -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 LAA03844;
	Thu, 31 Jan 2002 11:47:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03813
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 11:47:31 -0500 (EST)
Received: from gw-nl5.philips.com (gw-nl5.philips.com [212.153.235.99])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02857
	for <avt@ietf.org>; Thu, 31 Jan 2002 11:47:27 -0500 (EST)
From: philippe.gentric@philips.com
Received: from smtpscan-nl1.philips.com (localhost.philips.com [127.0.0.1])
          by gw-nl5.philips.com with ESMTP id RAA23232
          for <avt@ietf.org>; Thu, 31 Jan 2002 17:47:28 +0100 (MET)
          (envelope-from philippe.gentric@philips.com)
Received: from smtpscan-nl1.philips.com(130.139.36.21) by gw-nl5.philips.com via mwrap (4.0a)
	id xma023225; Thu, 31 Jan 02 17:47:29 +0100
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) 
	by smtpscan-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id RAA19419
	for <avt@ietf.org>; Thu, 31 Jan 2002 17:47:27 +0100 (MET)
Received: from hbg001soh.diamond.philips.com (e1soh01.diamond.philips.com [130.143.165.212]) 
	by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id RAA27111
	for <avt@ietf.org>; Thu, 31 Jan 2002 17:47:27 +0100 (MET)
To: avt@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF0994C842.04E52CA3-ONC1256B52.00591735@diamond.philips.com>
Date: Thu, 31 Jan 2002 17:43:29 +0100
X-MIMETrack: Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.5 |September
 22, 2000) at 31/01/2002 18:05:43,
	Serialize complete at 31/01/2002 18:05:44,
	Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.5 |September
 22, 2000) at 31/01/2002 18:05:44
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 005C9D3EC1256B52_="
Subject: [AVT] one question about the MPEG-4 generic RTP payload format (multiSL)
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

This is a multipart message in MIME format.
--=_alternative 005C9D3EC1256B52_=
Content-Type: text/plain; charset="us-ascii"

hi all,

There has been a lot of oral traffic and email traffic on other reflectors
(and recently about the emmerging H26L work !) about the issue that the 
draft
currently recommends that RTP time stamps SHOULD NOT
have random offsets, which is contradictory to the SHOULD in the RTP spec

Originally the "should not" was introduced because there was a concern 
that random offsets
would make it difficult to synchronize one RTP source with another non-RTP
(say downloaded .mp4 file) source.

Recent discussions indicated that this issue could rather be delegated to 
an application
integration stage (or to another "hat" specification such as the ones 
issued
by other bodies, 3GPP, ISMA, whatever)

 I want to ask on this reflector:

****************
would anybody object if this "should not " is simply removed i.e.
the "classical" RTP time stamp offset is always assumed ?
*****************

NB: Assuming that nobody objects I dont plan to add any explanatory 
comments
in the draft itself (that non-RTP source sync is out of scope).


Regards,


Philippe Gentric
Software Architect
Philips MP4Net
philippe.gentric@philips.com
http://www.mpeg-4.philips.com
--=_alternative 005C9D3EC1256B52_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="sans-serif">hi all,</font>
<br>
<br><font size=2 face="sans-serif">There has been a lot of oral traffic and email traffic on other reflectors</font>
<br><font size=2 face="sans-serif">(and recently about the emmerging H26L work !) about the issue that the draft</font>
<br><font size=2 face="sans-serif">currently recommends that RTP time stamps SHOULD NOT</font>
<br><font size=2 face="sans-serif">have random offsets, which is contradictory to the SHOULD in the RTP spec</font>
<br>
<br><font size=2 face="sans-serif">Originally the &quot;should not&quot; was introduced because there was a concern that random offsets</font>
<br><font size=2 face="sans-serif">would make it difficult to synchronize one RTP source with another non-RTP</font>
<br><font size=2 face="sans-serif">(say downloaded .mp4 file) source.</font>
<br>
<br><font size=2 face="sans-serif">Recent discussions indicated that this issue could rather be delegated to an application</font>
<br><font size=2 face="sans-serif">integration stage (or to another &quot;hat&quot; specification such as the ones issued</font>
<br><font size=2 face="sans-serif">by other bodies, 3GPP, ISMA, whatever)</font>
<br>
<br><font size=2 face="sans-serif">&nbsp;I want to ask on this reflector:</font>
<br>
<br><font size=2 face="sans-serif">****************</font>
<br><font size=2 face="sans-serif">would anybody object if this &quot;should not &quot; is simply removed i.e.</font>
<br><font size=2 face="sans-serif">the &quot;classical&quot; RTP time stamp offset is always assumed ?</font>
<br><font size=2 face="sans-serif">*****************</font>
<br>
<br><font size=2 face="sans-serif">NB: Assuming that nobody objects I dont plan to add any explanatory comments</font>
<br><font size=2 face="sans-serif">in the draft itself (that non-RTP source sync is out of scope).</font>
<br>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br>
<br><font size=2 face="sans-serif"><br>
Philippe Gentric<br>
Software Architect<br>
Philips MP4Net<br>
philippe.gentric@philips.com<br>
http://www.mpeg-4.philips.com</font>
--=_alternative 005C9D3EC1256B52_=--

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



From daemon@optimus.ietf.org  Thu Jan 31 12:28:30 2002
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 MAA04544
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 12:28:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA08207
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 12:28:30 -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 MAA07770;
	Thu, 31 Jan 2002 12:23:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07724
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 12:23:31 -0500 (EST)
Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04420
	for <avt@ietf.org>; Thu, 31 Jan 2002 12:23:26 -0500 (EST)
Received: from VAIOStW2.cs.tu-berlin.de (root@kuerbis.cs.tu-berlin.de [130.149.25.60])
	by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id SAA29409;
	Thu, 31 Jan 2002 18:17:55 +0100 (MET)
Message-Id: <5.1.0.14.2.20020131181429.02b0f008@mail.cs.tu-berlin.de>
X-Sender: stewe@mail.cs.tu-berlin.de
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 31 Jan 2002 18:17:05 +0100
To: philippe.gentric@philips.com
From: Stephan Wenger <stewe@cs.tu-berlin.de>
Subject: Re: [AVT] one question about the MPEG-4 generic RTP payload
  format (multiSL)
Cc: avt@ietf.org
In-Reply-To: <OF0994C842.04E52CA3-ONC1256B52.00591735@diamond.philips.co
 m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Dear Philippe,

At 05:43 PM 1/31/2002 +0100, philippe.gentric@philips.com wrote:
>would anybody object if this "should not " is simply removed i.e.
>the "classical" RTP time stamp offset is always assumed ?

This is the right course of action, and I'm happy to see this
proposed change.

Stephan




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



From daemon@optimus.ietf.org  Thu Jan 31 12:56:49 2002
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 MAA05675
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 12:56:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA09976
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 12:56:52 -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 MAA09835;
	Thu, 31 Jan 2002 12:53:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09805
	for <avt@optimus.ietf.org>; Thu, 31 Jan 2002 12:53:39 -0500 (EST)
Received: from ss3000e.cselt.it (ss3000e.cselt.it [163.162.41.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05533
	for <avt@ietf.org>; Thu, 31 Jan 2002 12:53:35 -0500 (EST)
Received: from EXC2K02B.cselt.it (clu2k02a.cselt.it [163.162.21.237])
 by ss3000e.cselt.it (PMDF V5.2-31 #43137)
 with ESMTP id <0GQT0080DDAON8@ss3000e.cselt.it> for avt@ietf.org; Thu,
 31 Jan 2002 18:44:49 +0100 (MET)
Date: Thu, 31 Jan 2002 18:53:02 +0100
From: Franceschini Guido <Guido.Franceschini@TILAB.COM>
Subject: RE: [AVT] one question about the MPEG-4 generic RTP payload
 format(multiSL)
To: philippe.gentric@philips.com, avt@ietf.org
Message-id: <C6F9A3197E8AC64EA69C079B97C81F2F0B94EF@EXC2K02B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.4712.0
Content-type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA80.20EC9652"
Thread-Topic: [AVT] one question about the MPEG-4 generic RTP payload
 format(multiSL)
Thread-Index: AcGqdyLkuqLubvvKSl6ldUbnhFE9bQACFljQ
Content-Class: urn:content-classes:message
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1AA80.20EC9652
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Philippe, all,
=20
The "SHOULD NOT" was introduced for enabling synchronization of MPEG-4
content delivered with RTP and MPEG-4 content delivered somehow
differently.
=20
I understand that this rule represents an ugly exception within RTP
I am less convinced that this rule represents as well a real security
hole, since in MPEG-4 timestamps as well as sequence numbers are allowed
to have any starting value.
=20
If (but only if !!! ) an alternative solution is found that fulfills the
requirement, then I would obviously not object to cancel that rule. But
please show an alternative solution first!
=20
Best regards
=20
Guido Franceschini
TILAB - Multimedia Division
Via G.Reiss Romoli 274
I-10148 Torino, Italy
tel + 39 011 228 6137
fax + 39 011 228 6299
=20
-----Original Message-----
From: philippe.gentric@philips.com [mailto:philippe.gentric@philips.com]

Sent: Thursday, January 31, 2002 5:43 PM
To: avt@ietf.org
Subject: [AVT] one question about the MPEG-4 generic RTP payload
format(multiSL)
=20



hi all,=20

There has been a lot of oral traffic and email traffic on other
reflectors=20
(and recently about the emmerging H26L work !) about the issue that the
draft=20
currently recommends that RTP time stamps SHOULD NOT=20
have random offsets, which is contradictory to the SHOULD in the RTP
spec=20

Originally the "should not" was introduced because there was a concern
that random offsets=20
would make it difficult to synchronize one RTP source with another
non-RTP=20
(say downloaded .mp4 file) source.=20

Recent discussions indicated that this issue could rather be delegated
to an application=20
integration stage (or to another "hat" specification such as the ones
issued=20
by other bodies, 3GPP, ISMA, whatever)=20

 I want to ask on this reflector:=20

****************=20
would anybody object if this "should not " is simply removed i.e.=20
the "classical" RTP time stamp offset is always assumed ?=20
*****************=20

NB: Assuming that nobody objects I dont plan to add any explanatory
comments=20
in the draft itself (that non-RTP source sync is out of scope).=20


Regards,=20


Philippe Gentric
Software Architect
Philips MP4Net
philippe.gentric@philips.com
http://www.mpeg-4.philips.com

------_=_NextPart_001_01C1AA80.20EC9652
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C1AA88.828D7F70">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"time"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"date"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:"Times New Roman";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:auto;
	mso-font-signature:0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Philippe, =
all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The &#8220;SHOULD NOT&#8221; was
introduced for enabling synchronization of MPEG-4 content delivered with =
RTP
and MPEG-4 content delivered somehow =
differently.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I understand that this rule =
represents an
ugly exception within RTP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I am less convinced that this rule
represents as well a real security hole, since in MPEG-4 timestamps as =
well as
sequence numbers are allowed to have any starting =
value.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If (but only <span class=3DGramE>if =
!!!</span>
) an alternative solution is found that fulfills the requirement, then I =
would
obviously not object to cancel that rule. But please show an alternative
solution first!<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Best =
regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy;mso-no-proof:yes'>Guido =
Franceschini<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-layout-grid-align:none;text-autospace:none'><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;mso-no-proof:yes'>TILAB - Multimedia =
Division<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-layout-grid-align:none;text-autospace:none'><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;mso-no-proof:yes'>Via G.Reiss Romoli =
274<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-layout-grid-align:none;text-autospace:none'><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;mso-no-proof:yes'>I-10148 =
</span></font><st1:place><st1:City><font
  size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
  color:navy;mso-no-proof:yes'>Torino</span></font></st1:City><font =
size=3D2
 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
 color:navy;mso-no-proof:yes'>, </span></font><st1:country-region><font =
size=3D2
  color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
  =
color:navy;mso-no-proof:yes'>Italy</span></font></st1:country-region></st=
1:place><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-layout-grid-align:none;text-autospace:none'><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;mso-no-proof:yes'>tel + 39 011 228 =
6137<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-layout-grid-align:none;text-autospace:none'><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;mso-no-proof:yes'>fax + 39 011 228 =
6299<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
philippe.gentric@philips.com
[mailto:philippe.gentric@philips.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> =
</span></font><st1:date
Month=3D"1" Day=3D"31" Year=3D"2002"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
 10.0pt;font-family:Tahoma'>Thursday, January 31, =
2002</span></font></st1:date><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> </span></font><st1:time
Hour=3D"17" Minute=3D"43"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
 font-family:Tahoma'>5:43 PM</span></font></st1:time><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'><br>
<b><span style=3D'font-weight:bold'>To:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [AVT] one =
question about
the MPEG-4 generic RTP payload format(multiSL)</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'><br>
</span></font><br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>hi
all,</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>There
has been a lot of oral traffic and email traffic on other =
reflectors</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>(and
recently about the emmerging H26L work !) about the issue that the =
draft</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>currently
recommends that RTP time stamps SHOULD NOT</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>have
random offsets, which is contradictory to the SHOULD in the RTP =
spec</span></font>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Originally
the &quot;should not&quot; was introduced because there was a concern =
that
random offsets</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>would
make it difficult to synchronize one RTP source with another =
non-RTP</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>(say
downloaded .mp4 file) source.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Recent
discussions indicated that this issue could rather be delegated to an
application</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>integration
stage (or to another &quot;hat&quot; specification such as the ones =
issued</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>by
other bodies, 3GPP, ISMA, whatever)</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;I
want to ask on this reflector:</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>****************</span>=
</font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>would
anybody object if this &quot;should not &quot; is simply removed =
i.e.</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>the
&quot;classical&quot; RTP time stamp offset is always assumed =
?</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>*****************</span=
></font>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>NB:
Assuming that nobody objects I dont plan to add any explanatory =
comments</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>in
the draft itself (that non-RTP source sync is out of =
scope).</span></font> <br>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Regards,</span></font>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'><br>
Philippe Gentric<br>
Software Architect<br>
Philips MP4Net<br>
philippe.gentric@philips.com<br>
http://www.mpeg-4.philips.com</span></font><o:p></o:p></p>

</div>

</body>

</html>
=00
------_=_NextPart_001_01C1AA80.20EC9652--

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



From daemon@ns.ietf.org  Thu Jan 31 14:11:42 2002
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 OAA08528
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:11:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14477
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 14:11:45 -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 OAA14434;
	Thu, 31 Jan 2002 14:10: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 OAA14406
	for <avt@ns.ietf.org>; Thu, 31 Jan 2002 14:10:52 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08475;
	Thu, 31 Jan 2002 14:10:48 -0500 (EST)
Message-Id: <200201311910.OAA08475@ietf.org>
To: IETF-Announce: ;
Cc: avt@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Date: Thu, 31 Jan 2002 14:10:47 -0500
Subject: [AVT] Last Call: RTP payload format and file storage format for AMR
 and AMR-WB audio to Proposed Standard
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


The IESG has received a request from the Audio/Video Transport Working
Group to consider RTP payload format and file storage format for AMR
and AMR-WB audio <draft-ietf-avt-rtp-amr-11.txt> as a Proposed
Standard.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by February 14, 2002.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amr-11.txt



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



From daemon@ns.ietf.org  Thu Jan 31 14:15:33 2002
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 OAA08593
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:15:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14609
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 14:15:36 -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 OAA14051;
	Thu, 31 Jan 2002 14:05:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13938
	for <avt@ns.ietf.org>; Thu, 31 Jan 2002 14:05:15 -0500 (EST)
Received: from gw-nl4.philips.com (gw-nl4.philips.com [212.153.190.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08267;
	Thu, 31 Jan 2002 14:05:10 -0500 (EST)
From: philippe.gentric@philips.com
Received: from smtpscan-nl1.philips.com (localhost.philips.com [127.0.0.1])
          by gw-nl4.philips.com with ESMTP id UAA09505;
          Thu, 31 Jan 2002 20:03:58 +0100 (CET)
          (envelope-from philippe.gentric@philips.com)
Received: from smtpscan-nl1.philips.com(130.139.36.21) by gw-nl4.philips.com via mwrap (4.0a)
	id xma009501; Thu, 31 Jan 02 20:03:58 +0100
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) 
	by smtpscan-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id UAA03275; Thu, 31 Jan 2002 20:04:40 +0100 (MET)
Received: from hbg001soh.diamond.philips.com (e1soh01.diamond.philips.com [130.143.165.212]) 
	by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id UAA22618; Thu, 31 Jan 2002 20:04:39 +0100 (MET)
To: Franceschini Guido <Guido.Franceschini@TILAB.COM>
Cc: avt@ietf.org, avt-admin@ietf.org
Subject: RE: [AVT] one question about the MPEG-4 generic RTP payload format(multiSL)
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFD1B848B5.220CB4D4-ONC1256B52.00649236@diamond.philips.com>
Date: Thu, 31 Jan 2002 20:00:48 +0100
X-MIMETrack: Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.5 |September
 22, 2000) at 31/01/2002 20:22:56,
	Serialize complete at 31/01/2002 20:22:56
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 00692F44C1256B52_="
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

This is a multipart message in MIME format.
--=_alternative 00692F44C1256B52_=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Guido,

you write:

"If (but only if !!! ) an alternative solution is found that fulfills the=20
requirement"

**********

OH but I can think of several ways to fix the problem !
and they would be better than that half hearted attempt !

i.e. the hypothetical existence of an alternative solution does not change =

the conclusion:
because the point is that ANY solution is irrelevant.... to *this* draft.

specifically from an IETF point of view any solution
need not and should not be be inside a RTP payload format !!

(yes ! finaly I think like an IETF guy, amazing no ?)

why ?

1.

you *cannot* use this  "should not" for interoperable synchronisation "as=20
is"
because a "should not" is not enough to create a normative behavior
at the SENDER side, which is the issue at stake here...

specifically the only thing that a "should not" allows you
is that if you design a solution that would work on top of it
 you may feel a bit better about not using random offsets,
hu ? .. ;-)

=3D=3D> you still need to define a specification for it, because
outside of this specification you will not have interop !!

2.

also you cannot have more that a "should not" because
there are too many RTP implementations out there that
assume/create a random offset AND we want to
interoperate with them ...

=3D=3D> unless for a specific application you *specify separately*  that on=
ly
server X can be used ... etc .... back to square one!


*******************

in conclusion:

since you *will* have to specify something on top of it to *really* make=20
it work,

why complicate/twist the RTP payload format ?

hum?

********************

I propose instead that we make another draft that will define how
to synchronize an RTP source using this payload format
with another non-RTP source of MPEG content ...

THAT would be the proper IETF way to proceed ...

Regards,


Philippe Gentric
Software Architect
Philips MP4Net
philippe.gentric@philips.com
http://www.mpeg-4.philips.com




Franceschini Guido <Guido.Franceschini@TILAB.COM>
Sent by: avt-admin@ietf.org
01/31/2002 18:53

=20
        To:     Philippe Gentric/LIM/CE/PHILIPS@EMEA1
avt@ietf.org
        cc:=20
        Subject:        RE: [AVT] one question about the MPEG-4 generic RTP=
 payload=20
format(multiSL)
        Classification:=20



Philippe, all,
=20
The "SHOULD NOT" was introduced for enabling synchronization of MPEG-4=20
content delivered with RTP and MPEG-4 content delivered somehow=20
differently.
=20
I understand that this rule represents an ugly exception within RTP
I am less convinced that this rule represents as well a real security=20
hole, since in MPEG-4 timestamps as well as sequence numbers are allowed=20
to have any starting value.
=20
If (but only if !!! ) an alternative solution is found that fulfills the=20
requirement, then I would obviously not object to cancel that rule. But=20
please show an alternative solution first!
=20
Best regards
=20
Guido Franceschini
TILAB - Multimedia Division
Via G.Reiss Romoli 274
I-10148 Torino, Italy
tel + 39 011 228 6137
fax + 39 011 228 6299
=20
-----Original Message-----
From: philippe.gentric@philips.com [mailto:philippe.gentric@philips.com]=20
Sent: Thursday, January 31, 2002 5:43 PM
To: avt@ietf.org
Subject: [AVT] one question about the MPEG-4 generic RTP payload format(mul=
tiSL)
=20



hi all,=20

There has been a lot of oral traffic and email traffic on other reflectors =

(and recently about the emmerging H26L work !) about the issue that the=20
draft=20
currently recommends that RTP time stamps SHOULD NOT=20
have random offsets, which is contradictory to the SHOULD in the RTP spec=20

Originally the "should not" was introduced because there was a concern=20
that random offsets=20
would make it difficult to synchronize one RTP source with another non-RTP =

(say downloaded .mp4 file) source.=20

Recent discussions indicated that this issue could rather be delegated to=20
an application=20
integration stage (or to another "hat" specification such as the ones=20
issued=20
by other bodies, 3GPP, ISMA, whatever)=20

 I want to ask on this reflector:=20

****************=20
would anybody object if this "should not " is simply removed i.e.=20
the "classical" RTP time stamp offset is always assumed ?=20
*****************=20

NB: Assuming that nobody objects I dont plan to add any explanatory=20
comments=20
in the draft itself (that non-RTP source sync is out of scope).=20


Regards,=20


Philippe Gentric
Software Architect
Philips MP4Net
philippe.gentric@philips.com
http://www.mpeg-4.philips.com


--=_alternative 00692F44C1256B52_=
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">Guido,</font>
<br>
<br><font size=3D2 face=3D"sans-serif">you write:</font>
<br>
<br><font size=3D2 face=3D"sans-serif">&quot;</font><font size=3D2 color=3D=
#000080 face=3D"Arial">If (but only if !!! ) an alternative solution is fou=
nd that fulfills the requirement</font><font size=3D2 face=3D"sans-serif">&=
quot;</font>
<br>
<br><font size=3D2 face=3D"sans-serif">**********</font>
<br>
<br><font size=3D2 face=3D"sans-serif">OH but I can think of several ways t=
o fix the problem !</font>
<br><font size=3D2 face=3D"sans-serif">and they would be better than that h=
alf hearted attempt !</font>
<br>
<br><font size=3D2 face=3D"sans-serif">i.e. the hypothetical existence of a=
n alternative solution does not change the conclusion:</font>
<br><font size=3D2 face=3D"sans-serif">because the point is that ANY soluti=
on is irrelevant.... to *this* draft.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">specifically from an IETF point of v=
iew any solution</font>
<br><font size=3D2 face=3D"sans-serif">need not and should not be be inside=
 a RTP payload format !!</font>
<br>
<br><font size=3D2 face=3D"sans-serif">(yes ! finaly I think like an IETF g=
uy, amazing no ?)</font>
<br>
<br><font size=3D2 face=3D"sans-serif">why ?</font>
<br>
<br><font size=3D2 face=3D"sans-serif">1.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">you *cannot* use this &nbsp;&quot;sh=
ould not&quot; for interoperable synchronisation &quot;as is&quot;</font>
<br><font size=3D2 face=3D"sans-serif">because a &quot;should not&quot; is =
not enough to create a normative behavior</font>
<br><font size=3D2 face=3D"sans-serif">at the SENDER side, which is the iss=
ue at stake here...</font>
<br>
<br><font size=3D2 face=3D"sans-serif">specifically the only thing that a &=
quot;should not&quot; allows you</font>
<br><font size=3D2 face=3D"sans-serif">is that if you design a solution tha=
t would work on top of it</font>
<br><font size=3D2 face=3D"sans-serif">&nbsp;you may feel a bit better abou=
t not using random offsets,</font>
<br><font size=3D2 face=3D"sans-serif">hu ? .. ;-)</font>
<br>
<br><font size=3D2 face=3D"sans-serif">=3D=3D&gt; you still need to define =
a specification for it, because</font>
<br><font size=3D2 face=3D"sans-serif">outside of this specification you wi=
ll not have interop !!</font>
<br>
<br><font size=3D2 face=3D"sans-serif">2.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">also you cannot have more that a &qu=
ot;should not&quot; because</font>
<br><font size=3D2 face=3D"sans-serif">there are too many RTP implementatio=
ns out there that</font>
<br><font size=3D2 face=3D"sans-serif">assume/create a random offset AND we=
 want to</font>
<br><font size=3D2 face=3D"sans-serif">interoperate with them ...</font>
<br>
<br><font size=3D2 face=3D"sans-serif">=3D=3D&gt; unless for a specific app=
lication you *specify separately* &nbsp;that only</font>
<br><font size=3D2 face=3D"sans-serif">server X can be used ... etc .... ba=
ck to square one!</font>
<br>
<br>
<br><font size=3D2 face=3D"sans-serif">*******************</font>
<br>
<br><font size=3D2 face=3D"sans-serif">in conclusion:</font>
<br>
<br><font size=3D2 face=3D"sans-serif">since you *will* have to specify som=
ething on top of it to *really* make it work,</font>
<br>
<br><font size=3D2 face=3D"sans-serif">why complicate/twist the RTP payload=
 format ?</font>
<br>
<br><font size=3D2 face=3D"sans-serif">hum?</font>
<br>
<br><font size=3D2 face=3D"sans-serif">********************</font>
<br>
<br><font size=3D2 face=3D"sans-serif">I propose instead that we make anoth=
er draft that will define how</font>
<br><font size=3D2 face=3D"sans-serif">to synchronize an RTP source using t=
his payload format</font>
<br><font size=3D2 face=3D"sans-serif">with another non-RTP source of MPEG =
content ...</font>
<br>
<br><font size=3D2 face=3D"sans-serif">THAT would be the proper IETF way to=
 proceed ...</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Regards,<br>
</font>
<br><font size=3D2 face=3D"sans-serif"><br>
Philippe Gentric<br>
Software Architect<br>
Philips MP4Net<br>
philippe.gentric@philips.com<br>
http://www.mpeg-4.philips.com</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<td><font size=3D1 face=3D"sans-serif"><b>Franceschini Guido &lt;Guido.Fran=
ceschini@TILAB.COM&gt;</b></font>
<br><font size=3D1 face=3D"sans-serif">Sent by: avt-admin@ietf.org</font>
<p><font size=3D1 face=3D"sans-serif">01/31/2002 18:53</font>
<br>
<td><font size=3D1 face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbs=
p; &nbsp; &nbsp; &nbsp;Philippe Gentric/LIM/CE/PHILIPS@EMEA1<br>
avt@ietf.org</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbs=
p; &nbsp; &nbsp; &nbsp;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject:=
 &nbsp; &nbsp; &nbsp; &nbsp;RE: [AVT] one question about the MPEG-4 generic=
 RTP payload format(multiSL)</font>
<p><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Classific=
ation: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br></table>
<br>
<br>
<br><font size=3D2 color=3D#000080 face=3D"Arial">Philippe, all,</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">&nbsp;</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">The "SHOULD NOT" was intro=
duced for enabling synchronization of MPEG-4 content delivered with RTP and=
 MPEG-4 content delivered somehow differently.</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">&nbsp;</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">I understand that this rul=
e represents an ugly exception within RTP</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">I am less convinced that t=
his rule represents as well a real security hole, since in MPEG-4 timestamp=
s as well as sequence numbers are allowed to have any starting value.</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">&nbsp;</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">If (but only if !!! ) an a=
lternative solution is found that fulfills the requirement, then I would ob=
viously not object to cancel that rule. But please show an alternative solu=
tion first!</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">&nbsp;</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">Best regards</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">&nbsp;</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">Guido Franceschini</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">TILAB - Multimedia Divisio=
n</font>
<p><font size=3D2 color=3D#000080 face=3D"Arial">Via G.Reiss Romoli 274</fo=
nt>
<p><font size=3D2 color=3D#000080 face=3D"Arial">I-10148 Torino, Italy</fon=
t>
<p><font size=3D2 color=3D#000080 face=3D"Arial">tel + 39 011 228 6137</fon=
t>
<p><font size=3D2 color=3D#000080 face=3D"Arial">fax + 39 011 228 6299</fon=
t>
<p><font size=3D2 color=3D#000080 face=3D"Arial">&nbsp;</font>
<p><font size=3D2 face=3D"Tahoma">-----Original Message-----<b><br>
From:</b> philippe.gentric@philips.com [mailto:philippe.gentric@philips.com=
] <b><br>
Sent:</b> Thursday, January 31, 2002 5:43 PM<b><br>
To:</b> avt@ietf.org<b><br>
Subject:</b> [AVT] one question about the MPEG-4 generic RTP payload format=
(multiSL)</font>
<p><font size=3D3 face=3D"Times New Roman">&nbsp;</font>
<p><font size=3D2 face=3D"sans-serif"><br>
</font><font size=3D3 face=3D"Times New Roman"><br>
</font><font size=3D2 face=3D"sans-serif"><br>
hi all,</font><font size=3D3 face=3D"Times New Roman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
There has been a lot of oral traffic and email traffic on other reflectors<=
/font><font size=3D3 face=3D"Times New Roman"> </font><font size=3D2 face=
=3D"sans-serif"><br>
(and recently about the emmerging H26L work !) about the issue that the dra=
ft</font><font size=3D3 face=3D"Times New Roman"> </font><font size=3D2 fac=
e=3D"sans-serif"><br>
currently recommends that RTP time stamps SHOULD NOT</font><font size=3D3 f=
ace=3D"Times New Roman"> </font><font size=3D2 face=3D"sans-serif"><br>
have random offsets, which is contradictory to the SHOULD in the RTP spec</=
font><font size=3D3 face=3D"Times New Roman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
Originally the &quot;should not&quot; was introduced because there was a co=
ncern that random offsets</font><font size=3D3 face=3D"Times New Roman"> </=
font><font size=3D2 face=3D"sans-serif"><br>
would make it difficult to synchronize one RTP source with another non-RTP<=
/font><font size=3D3 face=3D"Times New Roman"> </font><font size=3D2 face=
=3D"sans-serif"><br>
(say downloaded .mp4 file) source.</font><font size=3D3 face=3D"Times New R=
oman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
Recent discussions indicated that this issue could rather be delegated to a=
n application</font><font size=3D3 face=3D"Times New Roman"> </font><font s=
ize=3D2 face=3D"sans-serif"><br>
integration stage (or to another &quot;hat&quot; specification such as the =
ones issued</font><font size=3D3 face=3D"Times New Roman"> </font><font siz=
e=3D2 face=3D"sans-serif"><br>
by other bodies, 3GPP, ISMA, whatever)</font><font size=3D3 face=3D"Times N=
ew Roman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
 I want to ask on this reflector:</font><font size=3D3 face=3D"Times New Ro=
man"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
****************</font><font size=3D3 face=3D"Times New Roman"> </font><fon=
t size=3D2 face=3D"sans-serif"><br>
would anybody object if this &quot;should not &quot; is simply removed i.e.=
</font><font size=3D3 face=3D"Times New Roman"> </font><font size=3D2 face=
=3D"sans-serif"><br>
the &quot;classical&quot; RTP time stamp offset is always assumed ?</font><=
font size=3D3 face=3D"Times New Roman"> </font><font size=3D2 face=3D"sans-=
serif"><br>
*****************</font><font size=3D3 face=3D"Times New Roman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
NB: Assuming that nobody objects I dont plan to add any explanatory comment=
s</font><font size=3D3 face=3D"Times New Roman"> </font><font size=3D2 face=
=3D"sans-serif"><br>
in the draft itself (that non-RTP source sync is out of scope).</font><font=
 size=3D3 face=3D"Times New Roman"> <br>
<br>
</font><font size=3D2 face=3D"sans-serif"><br>
Regards,</font><font size=3D3 face=3D"Times New Roman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
<br>
Philippe Gentric<br>
Software Architect<br>
Philips MP4Net<br>
philippe.gentric@philips.com</font>
<br><font size=3D2 face=3D"sans-serif">http://www.mpeg-4.philips.com</font>
<br>
<br>
--=_alternative 00692F44C1256B52_=--

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



From daemon@ns.ietf.org  Thu Jan 31 18:56:24 2002
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 SAA15872
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 18:56:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA01915
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 18:56:28 -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 SAA01688;
	Thu, 31 Jan 2002 18:51:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01639
	for <avt@ns.ietf.org>; Thu, 31 Jan 2002 18:51:18 -0500 (EST)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15805;
	Thu, 31 Jan 2002 18:51:11 -0500 (EST)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id g0VNpDQ23641;
	Thu, 31 Jan 2002 15:51:13 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T58c9a6a716118164e13b4@mailgate2.apple.com>;
 Thu, 31 Jan 2002 15:51:04 -0800
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv2.apple.com (8.11.3/8.11.3) with ESMTP id g0VNp3w23400;
	Thu, 31 Jan 2002 15:51:03 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p0510101fb87f87e40263@[17.202.35.52]>
In-Reply-To: <OFD1B848B5.220CB4D4-ONC1256B52.00649236@diamond.philips.com>
References: <OFD1B848B5.220CB4D4-ONC1256B52.00649236@diamond.philips.com>
Date: Thu, 31 Jan 2002 15:49:25 -0800
To: philippe.gentric@philips.com,
        Franceschini Guido <Guido.Franceschini@tilab.com>
From: Dave Singer <singer@apple.com>
Subject: RE: [AVT] one question about the MPEG-4 generic RTP payload 
 format(multiSL)
Cc: avt@ietf.org, avt-admin@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

I'm with Philippe

the packaging spec that allows both RTP and other delivery means 
should specify how the time-lines are aligned.  Only one solution is 
using the same bit-values;  the kind of RTP-NTP mapping that RTSP 
does is another.  Yet a third is simply knowing that the two pieces 
of content have a simultaneous start, and driving them from the same 
clock.  There are many.  Such a spec should also discuss how to 
manage buffers when the two sources are not synchronized (basically, 
you have to run at the speed of the slowest source and buffer the 
faster ones).  It's a bigger question than a mere "should not" in 
this spec.
-- 
David Singer
Apple Computer/QuickTime

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



From daemon@ns.ietf.org  Thu Jan 31 18:58:03 2002
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 SAA15906
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 18:58:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA02027
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 18:58:07 -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 SAA02004;
	Thu, 31 Jan 2002 18:57:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01973
	for <avt@ns.ietf.org>; Thu, 31 Jan 2002 18:57:43 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15901
	for <avt@ietf.org>; Thu, 31 Jan 2002 18:57:38 -0500 (EST)
Received: from RKUMAR-W2K.cisco.com (dhcp-128-107-142-103.cisco.com [128.107.142.103]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id PAA07181; Thu, 31 Jan 2002 15:57:10 -0800 (PST)
Message-Id: <4.3.2.7.2.20020131154955.01e903d0@mira-sjc5-8.cisco.com>
X-Sender: rkumar@mira-sjc5-8.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 31 Jan 2002 15:55:32 -0800
To: avt@ietf.org
From: Rajesh Kumar <rkumar@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [AVT] Address/port to which separate FEC stream is directed
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

Jonathan, Henning

rfc2733 seems to mandate that a separate FEC stream, when produced, must be 
sent to a different port or IP address. Isn't is possible to send the FEC 
packets to the same port/address as the media packets? Even if this is 
do,  you cannot omit the parameters <port>, <network type>,  <address type> 
and <connection address>, right?

a=fmtp:<number> <port> <network type> <address type> <connection address>

Thanks

Rajesh Kumar
Cisco Systems


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



From daemon@ns.ietf.org  Thu Jan 31 19:03:00 2002
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 TAA15987
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 19:03:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA02644
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 19:03:03 -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 TAA02613;
	Thu, 31 Jan 2002 19:02:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02584
	for <avt@ns.ietf.org>; Thu, 31 Jan 2002 19:02:38 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15970
	for <avt@ietf.org>; Thu, 31 Jan 2002 19:02:33 -0500 (EST)
Received: from RKUMAR-W2K.cisco.com (dhcp-128-107-142-103.cisco.com [128.107.142.103]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA11612 for <avt@ietf.org>; Thu, 31 Jan 2002 16:02:01 -0800 (PST)
Message-Id: <4.3.2.7.2.20020131160000.01eee0d0@mira-sjc5-8.cisco.com>
X-Sender: rkumar@mira-sjc5-8.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 31 Jan 2002 16:00:23 -0800
To: avt@ietf.org
From: Rajesh Kumar <rkumar@cisco.com>
Subject: [AVT] Address/port to which separate FEC stream is directed
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Jonathan, Henning

rfc2733 seems to mandate that a separate FEC stream, when produced, must be 
sent to a different port or IP address. Isn't is possible to send the FEC 
packets to the same port/address as the media packets? Even if this is 
do,  you cannot omit the parameters <port>, <network type>,  <address type> 
and <connection address>, right?

a=fmtp:<number> <port> <network type> <address type> <connection address>

Thanks

Rajesh Kumar
Cisco Systems


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



From daemon@ns.ietf.org  Thu Jan 31 23:21:52 2002
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 XAA21173
	for <avt-archive@odin.ietf.org>; Thu, 31 Jan 2002 23:21:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA12145
	for avt-archive@odin.ietf.org; Thu, 31 Jan 2002 23:21:52 -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 XAA12126;
	Thu, 31 Jan 2002 23:21:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA12099
	for <avt@ns.ietf.org>; Thu, 31 Jan 2002 23:21:16 -0500 (EST)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21169
	for <avt@ietf.org>; Thu, 31 Jan 2002 23:21:10 -0500 (EST)
Received: from dynamicsoft.com ([63.113.46.67])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g114LO6Y010518;
	Thu, 31 Jan 2002 23:21:24 -0500 (EST)
Message-ID: <3C5A179B.5E0B3AB@dynamicsoft.com>
Date: Thu, 31 Jan 2002 23:20:43 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rajesh Kumar <rkumar@cisco.com>
CC: avt@ietf.org
Subject: Re: [AVT] Address/port to which separate FEC stream is directed
References: <4.3.2.7.2.20020131154955.01e903d0@mira-sjc5-8.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit



Rajesh Kumar wrote:
> 
> Jonathan, Henning
> 
> rfc2733 seems to mandate that a separate FEC stream, when produced, must
> be
> sent to a different port or IP address. Isn't is possible to send the
> FEC
> packets to the same port/address as the media packets? Even if this is
> do,  you cannot omit the parameters <port>, <network type>,  <address
> type>
> and <connection address>, right?

Well, my recollection is fuzzy here, but I recall that we decided that a
separate RTP session was better. One reason that I remember was rtp
header compression/rohc, since the timestamp predictors would be wrong
every time a FEC packet was emitted. I suspect there are other reasons
too, but that is the one I remember. 

Anyway, rfc2733 does explicitly say that the FEC stream is sent as a
separate RTP session. Its in section 3:

 The FEC packets are not sent in the same RTP stream as the media
   packets. They can be sent as a separate stream, or as a secondary
   codec in the redundant codec payload format [5].

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com

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



