From exim@www1.ietf.org  Mon Mar  1 04:14:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04150
	for <avt-archive@odin.ietf.org>; Mon, 1 Mar 2004 04:14:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxjV4-0004cm-W3
	for avt-archive@odin.ietf.org; Mon, 01 Mar 2004 04:14:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i219EAua017775
	for avt-archive@odin.ietf.org; Mon, 1 Mar 2004 04:14:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxjUw-0004by-0c; Mon, 01 Mar 2004 04:14:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxjUY-0004bO-2k
	for avt@optimus.ietf.org; Mon, 01 Mar 2004 04:13:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04127
	for <avt@ietf.org>; Mon, 1 Mar 2004 04:13:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxjUV-0002Sm-00
	for avt@ietf.org; Mon, 01 Mar 2004 04:13:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxjTj-0002OD-00
	for avt@ietf.org; Mon, 01 Mar 2004 04:12:48 -0500
Received: from vw1.pel.panasonic.de ([194.162.191.15] helo=MailRelay.Panasonic.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxjTD-0002II-00
	for avt@ietf.org; Mon, 01 Mar 2004 04:12:15 -0500
Received: from localhost ([127.0.0.1])
	by MailRelay.Panasonic.de;
	Mon, 1 Mar 2004 10:12:52 +0100
Received: from mcomlap9 ([10.11.11.4]) by mail.pel.panasonic.de with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 1 Mar 2004 10:10:28 +0100
Reply-To: <rey@panasonic.de>
From: "Jose Rey" <rey@panasonic.de>
To: "IETF AVT WG" <avt@ietf.org>
Cc: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Subject: RE: [AVT] Comments on draft-rey-avt-3gpp-timed-text-02.txtU
Date: Mon, 1 Mar 2004 10:10:34 +0100
Message-ID: <FDEEJECAGFFPBFPHMIIPKEDGHGAA.rey@panasonic.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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 V5.00.2919.6600
Importance: Normal
In-Reply-To: <403CDBC3.5030107@ericsson.com>
X-OriginalArrivalTime: 01 Mar 2004 09:10:28.0703 (UTC) FILETIME=[0A5F1EF0:01C3FF6D]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA04128
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable


Hi Magnus,

as usual, thanks a lot for the comments ;)

See inline,


> -----Original Message-----
> From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of
Magnus
> Westerlund
> Sent: Wednesday, February 25, 2004 6:31 PM
> To: IETF AVT WG
> Subject: [AVT] Comments on draft-rey-avt-3gpp-timed-text-02.txtU
>
>
> Hi Jose,
>
> Here is a number of comments on your draft. I like this much more than
> the previous proposal.
>
> 1. In the next update don't forget to update all the boilerplate for
IPR
> and copyright according to RFC 3667 and 3668.
>
OK

> 2. Abstract: "3GPP timed
>     text is time-lined decorated text media format whose defined
storage
>     format is the ISO (International Standardisation Organisation)
Base
>     Media File Format."
>
> This is not correct. the 3GPP Timed text is stored in the 3GP file
> format, which is based on the ISO Base Media File Format.
>
> 3. section 2, second paragraph: "3GPP timed text is a 3GP file format
> for time-lined decorated text specified in [1]." I would say that
"3GPP
> Timed Text is a media format for time-lined decorated text, with a
> defined storage in the 3GP file format."
>
Yes to both above.

> 4. Section 2.1, bullet 3: "This is especially useful for live
streaming
> (where the contents are not known a priori) or to protect this
> information through other mechanisms like FEC [4] or retransmission
> [13]." The second part of the sentence is not correct. The possibility
> to protect the important sample descriptions are not a reason for
having
> in-band sample descriptions. So please split it out, as FEC and
> retransmission is means to make it work.
>
Wording is not clear. Will change it.

> 5. Section 3, first bullet. "A text sample contains a text length
> indication, a text string, and zero or several modifier boxes (the
> decoration of the text)." Is not "zero or more" a better term, or is
it
> impossible to have only one modifier box?
>
"zero or more" is more precise.

> 6. Section 3, bullet list. Please adjust the formatting, having the
> lines after the first be adjusted further in so the "-" mark i alone
at
> the left makes it more clear that it is a bullet list.
>
OK.

> 7. Section 3, second bullet: "A fragment may either text strings and
> modifiers or just one of these." This sentence is very strange.

actually this sentence is incorrect since we don't allow text strings
and modifiers
to be in the same fragment.
It should say:

"A fragment may consist of either text strings or modifier box
contents."


>
> 8. Section 4, Marker bit: The current definition is unclear if one
only
> has a single complete text sample, should one have the marker bit set
or
> not.
Yes, as usual, it MUST be set. Will clarify.

>
> 9. Section 4, Timestamp: By putting the word "earliest" in the first
> sentence of the timestamp paragraph, you will not have to redefine the
> initial meaning a few lines down and it fits both single and multi
> sample cases. I would also think about using normative SHALL or MUST
in
> the definition to make readers aware of that this is something
important
> to follow.
>
OK.

> 10. Section 4, Timestamp: "The value timestamp clockrate is copied
> directly from the 3GP file: the value of "timescale" in the Media
Header
> Box is to be used." Is this a SHALL or SHOULD?

MUST/SHALL.

> With the RTP payload it
> will be possible to create 3GPP Timed text without ever storing it
> first. Therefore I think that some general guidance on timestamp rates
> should be written.

Right, for live content streaming...I'll write something on that

> Also, is the clock rate in the 3GP file fixed or can
> it be different between different files.

Every track (audio/video (includes timed text)) in a 3GP file has a
exactly one media header box. The 'timescale' value included there is
for that media and that's the one we use as clockrate.
The duration field refers to the number of cycles the text sample
'uses', so that sdur/timescale =3D duration[s]

Apart from that, the 3GP file includes a 'presentation' timescale value.
This is not consider in the draft.

In general, between files of them can be different.



>
> 11. Section 4.1: "It appears more appropriate to encode text samples
> without taking the path MTU into account." I think that it most
> applications is will be rather easy to ensure that created samples are
> not to big.

Right, this sentence addresses those cases. This sentence cannot be read
as stand-alone, though. It is the conclusion of the previous sentences.
>
> 12. section 4.1, Third bullet: "- it is RECOMMENDED to include as
fewer
> text sample fragments as possible in an RTP packet." First the
language
> is wrong "few" instead of "fewer".
OK

> Secondly, should one really include
> multiple fragments in a RTP packet. Isn't it much better to ensure
that
> one does not fragment.
>
The sentence is implicitly saying that one should not interleave
fragments, it is not reasonable to do so, since the lost of such a
packet might affect several samples.

On the other hand it is not possible to avoid fragmentation in every
situation as the draft explains in section 4.1.

> 13. Section 4.2: It is not clear if the payload are formed: header
> header data data, or header data header data. could you please
clarify.

Yes.

>
> 14. Section 4.2, the payload header? Is there a reason why the
reserved
> bits are left most in the first byte?

Not really.

> Otherwise I would recommend them
> to be placed between UL and TYPE. That way the bits could in the
future
> either be used to extend the TYPE field or for more indication bits.
>

Good idea, I'll take that in.


> 15. Section 4.2, L definition. "By default this flag is reset." I
guess
> that reset is having the bit take the value of 0. Please define reset
if
> you are going to use it.
>
OK

> 16. Section 4.2, The L bit. Is is really worth having the length field
> as a variable field. It will be needed in all cases except when only a
> single data unit is in a packet. Thus I don't think the overhead from
> these two bytes are in anyway excessive. The number of RTP packets
from
> timed text are rather few. In a subtitling usage, their is only a
single
> new sample every few seconds. I think simplicity is an advantage here.
>

It is certainly easier that way.

> 17. Section 4.2, SIDX: "To allow SIDX wrap-up, clients SHALL keep as
> valid only those values of SIDX outside of the interval (X+128) modulo
> 255, where X is the last SIDX value received." I think you need to
> specify it as an interval not a single value which (X+128) modulo 255
> are. I think you should define this as a client shall only use the
> sample entries that are (X-127)..(X) modulo 255.
>

This mechanism is faulty. The actual way it should work has been
discussed in the last days.  We decided to split it into two different
SIDX spaces: for dynamic and static types. It should work this way:

- Dynamic in-band SIDXs get values between 1 and 127, both inclusive.
- Static out-of-band SIDXs allowed are betwen 128 and 254 both
inclusive.
- 0,255 reserved

The wrap-up mechanism for dynamic SIDXs is as follows:  a sliding window
of a maximum 64 values is allowed per session.  This window may move
during the session:i.e. everytime a new undefined value comes the
algorithm redefines the interval of active values that fall in the
interval and keeps these SIDXs as active.  Typical sessions shouldn't
need more than 64 SIDXs. E.g.

if SIDXs received were 63,64,65, then SIDX belonging 2<->65 are
considered valid. The other values 66-128 + 1 invalid.

Dynamic values may be updated in-band. Static values not. Static values
have no wrap-up mechanism since they should be much less in number (no
need for that).


What do you think?

> 18. Section 4.2, SDUR: "However, samples of unknown duration MAY
precede
> sample descriptions, as they have no duration." I think duration is
the
> wrong word here. Sample descriptions is lacking timing information.
They
> are simply sent out and exist.
>
OK

> 19. Section 4.2: I think that making each type format its own
> sub-chapter and giving the name would increase the readability.
>
OK

> 20. section 4.2: Type=3D2: If you make the Len field permanent I think
the
> SDUR field should be shifted left one byte, the SLEN moved to the end
> and the TOTAL|This byte precede the SDUR field, that way one allows
for
> easier processing of the fields on a 32 bit machine.

OK,

from here:

*TYPE2*
|R|U|L|TYPE|LEN|SIDX|SLEN|SDUR|TOTL|THIS|
<---1-----><-2-><-1><--2><--3><---1----->


to:
*TYPE2*
|R|U|L|TYPE|LEN|SIDX|SDUR|TOTL|THIS|SLEN|
<---1-----><-2-><--1><--3><----1---><-2->
<-------32bit-------><---32bit----->

The others would be:

*TYPE1*
|R|U|L|TYPE|LEN|SIDX|SDUR|
<--1-------><2-><-1-><--3>
<-------32bit------->
which also fulfils your comment.

*TYPE 3&4* would be 4 bytes, thus also complying.




>
> 21. Section 4. type 2, TOTAL and THIS. I think the rules for how one
can
> send fragments in relation to other packets needs to be clarified.
OK.


> In
> general I think the fragmentation concept could be explained on a more
> general level. The concept of having different types for splitting
text
> and modifiers and that different rules apply could be explained prior
to
> defining the boxes.
>
I'll include an introductory explanation at the end of section 4.1
before the actual definition.

> 22. section 8. Please add an statement that unknown parameters SHALL
be
> ignored. That way there is some chance of extending the format in a
> predictable way in the future.
>
OK

> 23. Section 8. The reference to the timed text specification. Are you
> referring to the release 5 or release 6. As the release 6 is not yet
> frozen, how is the intended timing between the payload format and the
> timed text specification for release 6?
>
Both docs contain (except for editorials) the same thing.

The target is still to have this payload format for Release 6, which is
not due to March'04 anymore. In March a decision will be taken as to
when to freeze Release 6, probably September '04

> 24. Section 9. You have two definitions of how the parameters intended
> for the "a=3Dfmtp" line shall be mapped. Ether you keep the two line
> stating "the REQUIRED .." and "The OPTIONAL", or you use only the
> following line.
>

OK

> 25. Section 9.1, the mapping of the clockrate is unclear. It does not
> state exactly to what the 3GP file formats "timescale" value shall be
> copied to.

This is already explained in the Annex.  I think I'll add some comments
and refer to the Annex also including the explanation above.

>Also must this really be done, one could translate all times
> if desired.

Sorry, I don't understand this sentence. What do you mean?

> 26. Section 9. Missing Offer Answer section.

OK

>
> 27. Section 11. Please write the IANA section as a statement what IANA
> must do. In this case it seems appropriate to write. "IANA is request
to
> register one MIME type (3GPP-tt) as defined by section 8."
>
OK

> 28. Section 12. Are there any data in the 3GPP timed text media format
> that can be introduced that would result in significant higher
> processing requirements for a receiver, thus enabling DOS attacks?
>

I think not.


Cheers ,

Jos=E9

>
> Cheers
>
> Magnus
>
>
>
>
>
> --
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>
>
> This communication is confidential and intended solely for the
> addressee(s). Any unauthorized review, use, disclosure or
> distribution is prohibited. If you believe this message has been
> sent to you in error, please notify the sender by replying to
> this transmission and delete the message without disclosing it. Thank
you.
>
> E-mail including attachments is susceptible to data corruption,
> interruption, unauthorized amendment, tampering and viruses, and
> we only send and receive e-mails on the basis that we are not
> liable for any such corruption, interception, amendment,
> tampering or viruses or any consequences thereof.
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Mon Mar  1 19:55:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17264
	for <avt-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:55:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxyBp-0001FY-MK
	for avt-archive@odin.ietf.org; Mon, 01 Mar 2004 19:55:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220tHYq004803
	for avt-archive@odin.ietf.org; Mon, 1 Mar 2004 19:55:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxyBb-0001De-Vx; Mon, 01 Mar 2004 19:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxyAi-0001BB-Mc
	for avt@optimus.ietf.org; Mon, 01 Mar 2004 19:54:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17157
	for <avt@ietf.org>; Mon, 1 Mar 2004 19:54:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyAg-0002Yp-00
	for avt@ietf.org; Mon, 01 Mar 2004 19:54:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axy9e-0002Rp-00
	for avt@ietf.org; Mon, 01 Mar 2004 19:53:02 -0500
Received: from [192.103.16.205] (helo=multihop.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy8j-00021Q-00
	for avt@ietf.org; Mon, 01 Mar 2004 19:52:05 -0500
Received: from [218.37.224.72] (wideload.dhcp.ietf59.or.kr [218.37.224.72])
	by multihop.net (8.12.10/8.12.10) with ESMTP id i220qkr4017886
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <avt@ietf.org>; Mon, 1 Mar 2004 16:52:48 -0800 (PST)
	(envelope-from tj@kniveton.com)
Mime-Version: 1.0 (Apple Message framework v612)
To: avt@ietf.org
Message-Id: <808BA157-6BE3-11D8-AA6C-000A95DA08F2@kniveton.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-5--1050344827; protocol="application/pkcs7-signature"
From: "T.J. Kniveton" <tj@kniveton.com>
Date: Tue, 2 Mar 2004 09:49:46 +0900
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [AVT] Suggestion for ATRAC draft
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>


--Apple-Mail-5--1050344827
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I would like to suggest that the ATRAC draft presented in the WG today 
add all of the sample rates for ATRAC formats it supports, unless there 
is some reason not to. Seems like it would be easier to do that rather 
than force transmitter to downsample (i.e. ATRAC3 48k -> 44.1k).

-TJ
--Apple-Mail-5--1050344827
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEEjCCBA4w
ggN3oAMCAQICAQgwDQYJKoZIhvcNAQEEBQAwgbkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxp
Zm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMRowGAYDVQQKExFNdWx0aWhvcCBOZXR3b3Jr
czEmMCQGA1UECxMdU2VjdXJpdHkgSW5mcmFzdHJ1Y3R1cmUgR3JvdXAxGTAXBgNVBAMTEGlpby5t
dWx0aWhvcC5uZXQxHjAcBgkqhkiG9w0BCQEWD2NhQG11bHRpaG9wLm5ldDAeFw0wMzExMjIwMDMw
MjZaFw0wODExMjAwMDMwMjZaMIGqMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEW
MBQGA1UEBxMNU2FuIEZyYW5jaXNjbzEaMBgGA1UEChMRTXVsdGlob3AgTmV0d29ya3MxGjAYBgNV
BAsTEU1haWwgU2VuZGluZyBVbml0MRYwFAYDVQQDEw1ULkouIEtuaXZldG9uMR4wHAYJKoZIhvcN
AQkBFg90akBrbml2ZXRvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMOyGVi3ZeqI
A+thWuShiTnHWEBAOCPlbsX6nSssNdB4QNZWRmZfBr5I2Okj/E5flongKGToDI17j1aIakZ/FIkA
+2gvTBxonCFvtySFn7sQ9JYVkw8QCFopEEvug3TTxGqsc3UfvFUgpEQ0berx4juC6bCRZoFey5Ss
A68nqs9hAgMBAAGjggExMIIBLTAJBgNVHRMEAjAAMBgGCWCGSAGG+EIBDQQLFglUcnVzdCBtZS4w
HQYDVR0OBBYEFJ9elKRQr9QN4AlUWPuDDDd+30e7MIHmBgNVHSMEgd4wgduAFOQDibOvWu1mlL3o
8nqpjMsx+Q5GoYG/pIG8MIG5MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQG
A1UEBxMNU2FuIEZyYW5jaXNjbzEaMBgGA1UEChMRTXVsdGlob3AgTmV0d29ya3MxJjAkBgNVBAsT
HVNlY3VyaXR5IEluZnJhc3RydWN0dXJlIEdyb3VwMRkwFwYDVQQDExBpaW8ubXVsdGlob3AubmV0
MR4wHAYJKoZIhvcNAQkBFg9jYUBtdWx0aWhvcC5uZXSCAQAwDQYJKoZIhvcNAQEEBQADgYEAThZg
UzZQwvrd6ysmFdzYC8mnfrKBiM80IOzh9o3/ZywlfduKhl70Z92WEFt8/KA3Tehu16YHm/FN0RCj
DqA8agRMj0b/bjIPGxhX4QfJU/ADdhuGw+ZCPBaK3d+rbS/4+j7hCavSwqtnvXOCN7KYj+KkPm21
e8OBM6rS/wFtxYgxggNvMIIDawIBATCBvzCBuTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlm
b3JuaWExFjAUBgNVBAcTDVNhbiBGcmFuY2lzY28xGjAYBgNVBAoTEU11bHRpaG9wIE5ldHdvcmtz
MSYwJAYDVQQLEx1TZWN1cml0eSBJbmZyYXN0cnVjdHVyZSBHcm91cDEZMBcGA1UEAxMQaWlvLm11
bHRpaG9wLm5ldDEeMBwGCSqGSIb3DQEJARYPY2FAbXVsdGlob3AubmV0AgEIMAkGBSsOAwIaBQCg
ggIFMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MDMwMjAwNDk0
N1owIwYJKoZIhvcNAQkEMRYEFNpZyIOgqiUUEQFO99pH2nznYBqeMIHQBgkrBgEEAYI3EAQxgcIw
gb8wgbkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJh
bmNpc2NvMRowGAYDVQQKExFNdWx0aWhvcCBOZXR3b3JrczEmMCQGA1UECxMdU2VjdXJpdHkgSW5m
cmFzdHJ1Y3R1cmUgR3JvdXAxGTAXBgNVBAMTEGlpby5tdWx0aWhvcC5uZXQxHjAcBgkqhkiG9w0B
CQEWD2NhQG11bHRpaG9wLm5ldAIBCDCB0gYLKoZIhvcNAQkQAgsxgcKggb8wgbkxCzAJBgNVBAYT
AlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMRowGAYDVQQK
ExFNdWx0aWhvcCBOZXR3b3JrczEmMCQGA1UECxMdU2VjdXJpdHkgSW5mcmFzdHJ1Y3R1cmUgR3Jv
dXAxGTAXBgNVBAMTEGlpby5tdWx0aWhvcC5uZXQxHjAcBgkqhkiG9w0BCQEWD2NhQG11bHRpaG9w
Lm5ldAIBCDANBgkqhkiG9w0BAQEFAASBgGchC8aOA1oOPCByFoi7wcwYCm5MLy9Y0QKQTxK65gvo
PpYhu3Z/U+UP4xjuRQi+jB+j3S4X9DWwF/q47hGzqS3bVQs0EyCyBrsueK29I8sq5Hr7AbxuxW2k
NeTWmOFb7m0iue9WBfVEU6GguMyK9dcJKIkEyZrz7JPlyxlt3PPwAAAAAAAA

--Apple-Mail-5--1050344827--


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



From exim@www1.ietf.org  Mon Mar  1 20:42:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20712
	for <avt-archive@odin.ietf.org>; Mon, 1 Mar 2004 20:42:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axyv7-0000za-AE
	for avt-archive@odin.ietf.org; Mon, 01 Mar 2004 20:42:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i221g5MU003769
	for avt-archive@odin.ietf.org; Mon, 1 Mar 2004 20:42:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axyv4-0000ww-Lo; Mon, 01 Mar 2004 20:42:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxyuM-0000rU-PJ
	for avt@optimus.ietf.org; Mon, 01 Mar 2004 20:41:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20603
	for <avt@ietf.org>; Mon, 1 Mar 2004 20:41:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyuK-0001OW-00
	for avt@ietf.org; Mon, 01 Mar 2004 20:41:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxytT-0001Hy-00
	for avt@ietf.org; Mon, 01 Mar 2004 20:40:24 -0500
Received: from [192.103.16.205] (helo=multihop.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axysj-0000qH-00
	for avt@ietf.org; Mon, 01 Mar 2004 20:39:37 -0500
Received: from [218.37.224.72] (wideload.wireless.ietf59.or.kr [218.37.224.72])
	by multihop.net (8.12.10/8.12.10) with ESMTP id i221dtr4018001
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <avt@ietf.org>; Mon, 1 Mar 2004 17:39:57 -0800 (PST)
	(envelope-from tj@kniveton.com)
Mime-Version: 1.0 (Apple Message framework v612)
To: avt@ietf.org
Message-Id: <16093A00-6BEA-11D8-AA6C-000A95DA08F2@kniveton.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-8--1047517043; protocol="application/pkcs7-signature"
From: "T.J. Kniveton" <tj@kniveton.com>
Date: Tue, 2 Mar 2004 10:36:54 +0900
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [AVT] ATRAC sampling rates
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>


--Apple-Mail-8--1047517043
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

Oops, I made a mistake -- I was thinking of what used to be called 
ATRAC3, which was really ATRAC1, version 3 (kind of like MP3 is MPEG1 
layer 3), and those minidisc recorders had 48k -> 44.1k downsamplers. 
The newer ATRAC3 (with MDLP) does not have the 48k sampling rate or 
downsamplers. So never mind, and sorry for the confusion.

-TJ

--Apple-Mail-8--1047517043
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEEjCCBA4w
ggN3oAMCAQICAQgwDQYJKoZIhvcNAQEEBQAwgbkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxp
Zm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMRowGAYDVQQKExFNdWx0aWhvcCBOZXR3b3Jr
czEmMCQGA1UECxMdU2VjdXJpdHkgSW5mcmFzdHJ1Y3R1cmUgR3JvdXAxGTAXBgNVBAMTEGlpby5t
dWx0aWhvcC5uZXQxHjAcBgkqhkiG9w0BCQEWD2NhQG11bHRpaG9wLm5ldDAeFw0wMzExMjIwMDMw
MjZaFw0wODExMjAwMDMwMjZaMIGqMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEW
MBQGA1UEBxMNU2FuIEZyYW5jaXNjbzEaMBgGA1UEChMRTXVsdGlob3AgTmV0d29ya3MxGjAYBgNV
BAsTEU1haWwgU2VuZGluZyBVbml0MRYwFAYDVQQDEw1ULkouIEtuaXZldG9uMR4wHAYJKoZIhvcN
AQkBFg90akBrbml2ZXRvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMOyGVi3ZeqI
A+thWuShiTnHWEBAOCPlbsX6nSssNdB4QNZWRmZfBr5I2Okj/E5flongKGToDI17j1aIakZ/FIkA
+2gvTBxonCFvtySFn7sQ9JYVkw8QCFopEEvug3TTxGqsc3UfvFUgpEQ0berx4juC6bCRZoFey5Ss
A68nqs9hAgMBAAGjggExMIIBLTAJBgNVHRMEAjAAMBgGCWCGSAGG+EIBDQQLFglUcnVzdCBtZS4w
HQYDVR0OBBYEFJ9elKRQr9QN4AlUWPuDDDd+30e7MIHmBgNVHSMEgd4wgduAFOQDibOvWu1mlL3o
8nqpjMsx+Q5GoYG/pIG8MIG5MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQG
A1UEBxMNU2FuIEZyYW5jaXNjbzEaMBgGA1UEChMRTXVsdGlob3AgTmV0d29ya3MxJjAkBgNVBAsT
HVNlY3VyaXR5IEluZnJhc3RydWN0dXJlIEdyb3VwMRkwFwYDVQQDExBpaW8ubXVsdGlob3AubmV0
MR4wHAYJKoZIhvcNAQkBFg9jYUBtdWx0aWhvcC5uZXSCAQAwDQYJKoZIhvcNAQEEBQADgYEAThZg
UzZQwvrd6ysmFdzYC8mnfrKBiM80IOzh9o3/ZywlfduKhl70Z92WEFt8/KA3Tehu16YHm/FN0RCj
DqA8agRMj0b/bjIPGxhX4QfJU/ADdhuGw+ZCPBaK3d+rbS/4+j7hCavSwqtnvXOCN7KYj+KkPm21
e8OBM6rS/wFtxYgxggNvMIIDawIBATCBvzCBuTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlm
b3JuaWExFjAUBgNVBAcTDVNhbiBGcmFuY2lzY28xGjAYBgNVBAoTEU11bHRpaG9wIE5ldHdvcmtz
MSYwJAYDVQQLEx1TZWN1cml0eSBJbmZyYXN0cnVjdHVyZSBHcm91cDEZMBcGA1UEAxMQaWlvLm11
bHRpaG9wLm5ldDEeMBwGCSqGSIb3DQEJARYPY2FAbXVsdGlob3AubmV0AgEIMAkGBSsOAwIaBQCg
ggIFMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MDMwMjAxMzY1
NFowIwYJKoZIhvcNAQkEMRYEFOej4yiMk3ALtf4/Zau4zQ+BjYluMIHQBgkrBgEEAYI3EAQxgcIw
gb8wgbkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJh
bmNpc2NvMRowGAYDVQQKExFNdWx0aWhvcCBOZXR3b3JrczEmMCQGA1UECxMdU2VjdXJpdHkgSW5m
cmFzdHJ1Y3R1cmUgR3JvdXAxGTAXBgNVBAMTEGlpby5tdWx0aWhvcC5uZXQxHjAcBgkqhkiG9w0B
CQEWD2NhQG11bHRpaG9wLm5ldAIBCDCB0gYLKoZIhvcNAQkQAgsxgcKggb8wgbkxCzAJBgNVBAYT
AlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMRowGAYDVQQK
ExFNdWx0aWhvcCBOZXR3b3JrczEmMCQGA1UECxMdU2VjdXJpdHkgSW5mcmFzdHJ1Y3R1cmUgR3Jv
dXAxGTAXBgNVBAMTEGlpby5tdWx0aWhvcC5uZXQxHjAcBgkqhkiG9w0BCQEWD2NhQG11bHRpaG9w
Lm5ldAIBCDANBgkqhkiG9w0BAQEFAASBgIrwRe/Q5sZQ3xRdaCIH+UVq9o6gjmDOH2Xig7oMUCFP
imnZBsugrDo4bU/S0jSIndr6OWQZ+wzNny8Vt+n36ELxEnq1cCyCJaSC5r/RlQJcy65Y9myu6q7+
9vbo9IDNVQRy6TCmbGP0W72g4vm3GyWBSlYlNiN+j4wIpB0j1D9LAAAAAAAA

--Apple-Mail-8--1047517043--


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



From exim@www1.ietf.org  Tue Mar  2 01:17:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05267
	for <avt-archive@odin.ietf.org>; Tue, 2 Mar 2004 01:17:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay3DR-0005t5-NB
	for avt-archive@odin.ietf.org; Tue, 02 Mar 2004 01:17:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i226HHAZ022572
	for avt-archive@odin.ietf.org; Tue, 2 Mar 2004 01:17:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay3DA-0005lU-Nq; Tue, 02 Mar 2004 01:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay3CR-0005Wh-3B
	for avt@optimus.ietf.org; Tue, 02 Mar 2004 01:16:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05190
	for <avt@ietf.org>; Tue, 2 Mar 2004 01:16:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay3CO-00040s-00
	for avt@ietf.org; Tue, 02 Mar 2004 01:16:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay3BW-0003vF-00
	for avt@ietf.org; Tue, 02 Mar 2004 01:15:18 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay3Ak-0003j1-00
	for avt@ietf.org; Tue, 02 Mar 2004 01:14:30 -0500
Received: from [210.93.162.110] (port=1359 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1Ay3AA-00068l-00
	for avt@ietf.org; Tue, 02 Mar 2004 06:13:55 +0000
Date: Tue, 2 Mar 2004 15:13:57 +0900
From: Colin Perkins <csp@csperkins.org>
To: avt@ietf.org
Message-Id: <20040302151357.130b6529.csp@csperkins.org>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Presentation materials for Seoul meeting
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Copies of the presentation materials used in the AVT meetings at the Seoul
IETF can be found at http://www.dcs.gla.ac.uk/~csp/ietf59-avt/

This is a temporary home, and the materials will migrate onto the IETF web
site after the meeting.

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Tue Mar  2 18:43:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09950
	for <avt-archive@odin.ietf.org>; Tue, 2 Mar 2004 18:43:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyJXg-0000Nh-30
	for avt-archive@odin.ietf.org; Tue, 02 Mar 2004 18:43:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22NhFbY001414
	for avt-archive@odin.ietf.org; Tue, 2 Mar 2004 18:43:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyJXS-0000LO-Qw; Tue, 02 Mar 2004 18:43:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxqzO-0002qu-7n
	for avt@optimus.ietf.org; Mon, 01 Mar 2004 12:13:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23065
	for <avt@ietf.org>; Mon, 1 Mar 2004 12:13:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxqzM-0005FK-00
	for avt@ietf.org; Mon, 01 Mar 2004 12:13:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxqyT-00059P-00
	for avt@ietf.org; Mon, 01 Mar 2004 12:13:02 -0500
Received: from moods.dsi.unifi.it ([150.217.15.88])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxqxY-00052e-00
	for avt@ietf.org; Mon, 01 Mar 2004 12:12:04 -0500
Received: from moods.dsi.unifi.it (moods.dsi.unifi.it [127.0.0.1])
	by moods.dsi.unifi.it (8.12.5/8.12.8) with ESMTP id i21HBF7d019782
	for <avt@ietf.org>; Mon, 1 Mar 2004 18:11:15 +0100
Received: (from wedelmusic@localhost)
	by moods.dsi.unifi.it (8.12.5/8.12.5/Submit) id i21HBE10019780
	for avt@ietf.org; Mon, 1 Mar 2004 18:11:14 +0100
Date: Mon, 1 Mar 2004 18:11:14 +0100
Message-Id: <200403011711.i21HBE10019780@moods.dsi.unifi.it>
To: avt@ietf.org
From: "WEDELMUSIC" <wedelmusic@moods.dsi.unifi.it>
Reply-to: wedelmusic@dsi.unifi.it
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=REMOVE_SUBJ autolearn=no 
	version=2.60
Subject: [AVT] CFP: Int. Conf. on WEB Delivering of Music, WEDELMUSIC 2004, Barcelona, Spain
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Sorry for any multiple reception of this message.
If you do not want to receive further information about WEDELMUSIC 2004, please send back an email with REMOVE on the subject.

The topics of this e-mail are:

Call for Papers, submission deadline: 20th March 2004
    4th International Conference on Web Delivering of Music, WEDELMUSIC 2004
    Universitat Pompeu Fabra, Barcelona, Spain 
    13th-15th September 2004

Call for participation
    3rd Open Workshop MUSICNETWORK, Munich, March 2004
    MPEG AHG on Music Notation Requirements
    13-14 of March 2004, Munich, Germany

Announcement of co-location of
    4th Open Workshop MUSICNETWORK
    Universitat Pompeu Fabra, Barcelona, Spain 
    14th-16th September 2004

Cheers,
Paolo Nesi, Jaime Delgado, Kia Ng

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.

Call for Papers
4th International Conference on Web Delivering of Music, WEDELMUSIC 2004
Universitat Pompeu Fabra, Barcelona, Spain 
13th-15th September 2004

http://www.upf.edu/wedelmusic2004/    http://www.wedelmusic.org/

Content distribution is presently not anymore limited to music and is becoming more 
cross media oriented. New distribution models for old and new content formats are 
opening new paths: i-TV, mobile phones, PDAs, etc. The development of the Internet 
technologies introduces strong impact on system architectures and business processes. New national and international regulations, policies and market evolution are 
constraining the distribution mechanisms. Novel distribution models, development 
and application of pervasive computing and multimedia strongly influence this multi-
disciplinary field. The need of content control and monitoring is demanding effective 
Digital Rights Management (DRM) solutions integrated with sustainable business and 
transaction models. These technologies impact on the production and modelling of 
cross media content.

WEDELMUSIC-2004 aims to explore these major topics in cross media field, to address 
novel approaches for distributing content to larger audiences, providing wider access
 and encouraging broader participation. The impact of these developments on cultural 
heritage is also considered, together with their availability to people with limited access to content.

The conference is open to all the enabling technologies behind these problems. We 
are promoting discussion and interaction among researchers, practitioners, developers, 
final users, technology transfer experts, and project managers. 

Topics

Topics of interest include, but are not restricted to: 

--Protection formats and tools for music 
--Transaction models for delivering music, Business models for publishers 
--Copyright ownership protection 
--Digital Rights Management 
--High quality Audio Coding 
--Watermarking techniques for various media types 
--Formats and models for distribution 
--Music manipulation and analysis, transcoding, etc.. 
--Music and tools for impaired people - Braille 
--Publishers and distributors servers 
--Cross media delivery on multi-channel systems, mobile, i-TV, PDAs, Internet, etc. 
--Automatic cross media content production 
--MPEG-4, MPEG-7 and MPEG-21 
--Viewing and listening tools for music 
--Music editing and manipulation 
--Music education techniques 
--Content based retrieval 
--Conversion and digital adaptation aspects, techniques and tools 
--Music imaging, music sheet digitalisation,
--Solutions for cultural heritage valorisation 

see for other topics the web site. 

Research Papers

Papers should describe original and significant work in the research and practice 
of the main topics listed above. Research case studies, applications and experiments 
are particularly welcome. Papers should be limited to approx. 2000-5000 words 
(8 pages) in length. Of the accepted paper, 8 pages will be published in the conference 
proceedings. The conference proceedings book will be published by the IEEE Computer 
Society.

Industrial Papers

Proposals for papers and reports of Applications and Tools are also welcome. 
These may consist of experiences from actual utilisation of tools or industrial 
practice and models. Proposals will be reviewed by the Industrial members of the 
Program Committee. Papers should be limited to approx. 1000-2500 words (4 pages)
 in length. Of the accepted paper, 4 pages will be published in the conference 
proceedings. 

Submissions

All submissions and proposals should be written in English following the IEEE 
format and submitted in PDF format via email to 

wedelmusic04-submission@altair.upf.edu 

by  20 March 2004.


-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.
4th Open Workshop MUSICNETWORK
Universitat Pompeu Fabra, Barcelona, Spain 
14th-16th September 2004

More details and the call for contribution will appear on:
http://www.interactivemusicnetwork.org 

After the 3rd Open Workshop as described in the following section

The access is free of charge, supported by the European Commission.

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.

Call for PARTICIPATION
3rd Open Workshop MUSICNETWORK, Munich, March 2004
MPEG AHG on Music Notation Requirements
13-14 of March 2004, Munich, Germany

http://www.interactivemusicnetwork.org 
http://www.dsi.unifi.it/~nesi/mpeg/MUSICNETWORK-OW-March-2004-Description-v1-4-clean.htm
http://www.dsi.unifi.it/~nesi/mpeg/ahg-mn-65-66.html

located at:
Technische Universität München, Germany: http://www.mpeg-68.de/location.php 

The Open Workshop of MUSICNETWORK is at its third edition. The modeling ofmusic 
notation/representation is a complex problem. Music representation can be used 
for several different purposes: entertainment, music education, infotainment, 
music archiving and retrieval, music querying, music production, music profiling,
 etc. In the current Internet and Multimedia age many other applications are 
strongly getting the market attention and most of them will become more diffuse 
of the present applications in short time. End users have discovered the multimedia 
experience, and thus, the traditional music models are going to be replaced by 
their integration with multimedia, audio visual, cross media. At present, there is
 a lack of Music Notation/Representation standard integrated with multimedia. The 
aim of this workshop is to make a further step to arrive at standardizing a Music 
Notation/Representation Model and Decoder integrated into the MPEG environment, 
that presently can be regarded as the most active and powerful set of standard 
formats for multimedia consumers. 

The topics of the workshop are related mainly focused on:

--Music Notation/Representation requirements 
--Music Protection and Distribution
--Music Description and its usage on Archive Query

Please Contribute with your work on the above topics, for details see the www site 
of the workshop.

The access is be free of charge, supported by the European Commission.
PLEASE MAKE THE REGISTRATION ON THE WWW OF THE MUSICNETWORK.

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.
4th Open Workshop MUSICNETWORK
Universitat Pompeu Fabra, Barcelona, Spain 
14th-16th September 2004

More details and  the call for contribution will appear on:
http://www.interactivemusicnetwork.org 

after the 3rd Open Workshop as described in the following section

The access is be free of charge, supported by the European COmmission.

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.

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



From exim@www1.ietf.org  Thu Mar  4 06:06:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08832
	for <avt-archive@odin.ietf.org>; Thu, 4 Mar 2004 06:06:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayqg5-0002M5-9S
	for avt-archive@odin.ietf.org; Thu, 04 Mar 2004 06:06:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24B69Ub009002
	for avt-archive@odin.ietf.org; Thu, 4 Mar 2004 06:06:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayqfy-0002K2-7V; Thu, 04 Mar 2004 06:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyqeT-00027T-S6
	for avt@optimus.ietf.org; Thu, 04 Mar 2004 06:04:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08736
	for <avt@ietf.org>; Thu, 4 Mar 2004 06:04:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyqeQ-0002Wp-00
	for avt@ietf.org; Thu, 04 Mar 2004 06:04:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyqdR-0002M3-00
	for avt@ietf.org; Thu, 04 Mar 2004 06:03:26 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyqcZ-000216-00
	for avt@ietf.org; Thu, 04 Mar 2004 06:02:31 -0500
Received: from mac-0-20-e0-89-cb-be.wireless.ietf59.or.kr ([218.37.230.107]:1857 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1Ayqc4-0005XX-00
	for avt@ietf.org; Thu, 04 Mar 2004 11:02:01 +0000
Date: Thu, 4 Mar 2004 20:01:47 +0900
From: Colin Perkins <csp@csperkins.org>
To: avt@ietf.org
Subject: Re: [AVT] ello! =))
Message-Id: <20040304200147.3cead4f5.csp@csperkins.org>
In-Reply-To: <gebvyohksngaatqsthx@csperkins.org>
References: <gebvyohksngaatqsthx@csperkins.org>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> csp@csperkins.org writes:
> ------------------  Virus Warning Message (on ietf-mx)
> 
> Found virus WORM_BAGLE.GEN-1 in file MoreInfo.zip
> The file is deleted.
> 
> ---------------------------------------------------------

Again, someone on the list has a virus, but this didn't come from me. A
check of the headers indicates the it came from a host in Poland.

Apologies for the noise...

Colin

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



From exim@www1.ietf.org  Sat Mar  6 17:19:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07025
	for <avt-archive@odin.ietf.org>; Sat, 6 Mar 2004 17:19:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Azk7x-0008ST-7t
	for avt-archive@odin.ietf.org; Sat, 06 Mar 2004 17:18:37 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i26MIbKU032462
	for avt-archive@odin.ietf.org; Sat, 6 Mar 2004 17:18:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Azk7N-0008Qy-2G; Sat, 06 Mar 2004 17:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Azj4L-0004Gs-Ja
	for avt@optimus.ietf.org; Sat, 06 Mar 2004 16:10:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05167
	for <avt@ietf.org>; Sat, 6 Mar 2004 16:10:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Azj4J-0000pW-00
	for avt@ietf.org; Sat, 06 Mar 2004 16:10:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Azj3L-0000gT-00
	for avt@ietf.org; Sat, 06 Mar 2004 16:09:47 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Azj2M-0000QG-00
	for avt@ietf.org; Sat, 06 Mar 2004 16:08:46 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61188 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1Azj1p-0007HK-00
	for avt@ietf.org; Sat, 06 Mar 2004 21:08:13 +0000
Date: Sat, 6 Mar 2004 17:52:51 +0900
From: Colin Perkins <csp@csperkins.org>
To: avt@ietf.org
Subject: Re: [AVT] Advancing RTP spec & profile to Full Standard
Message-Id: <20040306175251.36768e28.csp@csperkins.org>
In-Reply-To: <20040129012413.480e897d.csp@csperkins.org>
References: <20040129012413.480e897d.csp@csperkins.org>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Colin Perkins <csp@csperkins.org> writes:
> From: Colin Perkins <csp@csperkins.org>
> To: avt@ietf.org
> Subject: [AVT] Advancing RTP spec & profile to Full Standard
> Date: Thu, 29 Jan 2004 01:24:13 +0000
> 
> Folks,
> 
> The RTP specification (RFC 3550) and the RTP Audio/Video Profile (RFC
> 3551) have remained at the Draft Standard level for more than four
> months, and past the occurrence of one IETF meeting.  This exceeds the
> requirements of RFC 2026 for advancement to full Internet Standard
> status.
> 
> Consequently, with the concurrence of the AVT working group, we would
> like to send a request to the IESG that these RFCs be advanced unchanged
> to Full Internet Standard.  If you have any comments on this step, either
> agreement or objections, please reply to the mailing list.
> 
> Colin, Magnus and Steve

We have received no objections, and several comments in favour of this
proposal. Accordingly, we will request that the IESG advance the RTP 
specification and A/V profile to Full Standard.

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Tue Mar  9 03:21:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13935
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 03:21:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cUK-0008Bc-QJ
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 03:21:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i298LKvE031410
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 03:21:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cU5-00087u-PH; Tue, 09 Mar 2004 03:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cTX-00082e-FV
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 03:20:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13878
	for <avt@ietf.org>; Tue, 9 Mar 2004 03:20:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0cTV-0001xW-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:20:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0cSX-0001nq-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:19:29 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0cRj-0001dq-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:18:39 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i298IbAh017743
	for <avt@ietf.org>; Tue, 9 Mar 2004 09:18:37 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 9 Mar 2004 09:18:37 +0100
Received: from ericsson.com (EFI9301K2PCDLTL.ki.sw.ericsson.se [147.214.34.102]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id FYFT4GZY; Tue, 9 Mar 2004 09:19:26 +0100
Message-ID: <404C765A.3020005@ericsson.com>
Date: Mon, 08 Mar 2004 14:34:18 +0100
X-Sybari-Trust: fc471480 2c4885b5 39802fef 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Mar 2004 08:18:37.0849 (UTC) FILETIME=[1F767890:01C405AF]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comments on draft-ash-avt-ecrtp-over-mpls-reqs-01.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

During the IETF meeting it was requested that we accept the requirements 
document as a AVT WG document. We have Allison's approval for taking 
this on within the WG, so unless someone raises very good reasons, this 
will become a WG document. To get started on the first version of the WG 
document I like to give the following comments.

1. I would like to documents title and filename to reflect what the 
document is for, namely requirements for header compression over MPLS. 
It is not specific to ECRTP, although it appears a good match for the 
requirements. It was unfortunate that the milestone specifies ECRTP, 
however please remember to be a bit broader in the thinking. Thus I 
would suggest that a new title: "Requirements for header compression 
over MPLS". And as filename I would suggest 
draft-ietf-avt-hc-mpls-req-00.txt for the first version.

2. Two to get this document published as an informational document the 
editors would need to ensure that all ID nits are meet. This includes 
things like page breaks at the right places, etc.

3. To make the document a bit more agnostic to the actual header 
compression standard used, I would suggest that one replaces most 
occurrences in the abstract, and introduction  of ECRTP with HC (Header 
Compression).

4. I would also like to warn about using RFC 2119 words as they are in a 
requirements document, it may make more sense to define them as it is 
desired.

5. I would also suggest that one tries to improve the motivation why 
ECRTP is in fact the right header compression protocol to use. To make 
this clear I would recommend a section describing the properties of MPLS 
label switched path and what requirements that places on the header 
compression algorithm. Also the actual requirements on the signalling 
part needs to be considered.

6. It would also be desirable if one could move some of the solution 
conclusions in chapter 3 to its own chapter. Chapter 3 will be clearer 
if one concentrates on stating goals and requirements with their 
motivation.


Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com




This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar  9 04:10:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13934
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 03:21:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cUK-0008Bb-Pg
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 03:21:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i298LKln031411
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 03:21:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cU3-00087Z-6n; Tue, 09 Mar 2004 03:21:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cTV-00082U-AI
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 03:20:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13872
	for <avt@ietf.org>; Tue, 9 Mar 2004 03:20:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0cTT-0001xH-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:20:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0cST-0001nR-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:19:26 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0cRh-0001di-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:18:37 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i298IcYG027929
	for <avt@ietf.org>; Tue, 9 Mar 2004 09:18:38 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 9 Mar 2004 09:18:38 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id FYF9TV31; Tue, 9 Mar 2004 09:18:38 +0100
Message-ID: <404C8823.1030405@ericsson.com>
Date: Mon, 08 Mar 2004 15:50:11 +0100
X-Sybari-Trust: 141c8a93 2c4885b5 39802fef 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Mar 2004 08:18:38.0151 (UTC) FILETIME=[1FA48D70:01C405AF]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Commetns on Header compression for MPLS LSPs (draft-ash-avt-ecrtp-over-mpls-protocol-00.txt)
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

Having reviewed the solutions proposal document I would like to take a 
few steps back, and discuss the issues on a higher level. We should also 
not be carried into to much detail yet until the requirements work is 
completed.

In my understanding we will need a few components in the total system.

A. A signalling protocol for an MPLS ingress router (A) to 
determine/create the LSP that will go to a HC enabled egress router (B). 
That protocol seems to need to signal the following information:
- What HC algorithms it support
- What LSP that will go from A->B and for HC algorithms that uses 
feedback the return path B->A, which indicates HC enabled packets.
- Further HC algorithm parameters, for example maximum number of session 
contexts.

B. To create a mapping for the HC algorithm into the LSP. Here it seems 
that ECRTP would need to have identifiers for its packet types, while 
ROHC would not need anything.

The solution does not require anything more as I see it. It can be 
enhanced with description of how an ingress router determines what flows 
to do HC on, for example through the header compression hints that exist 
for RSVP, see RFC 3006. An ingress router can also use heuristics or any 
other method it desires to determine if it should apply header 
compression on a certain packet flow. Thus I don't see a need to talk 
about specific applications of RTP or UDP that can benefit from this work.

Something else that I reacted to in the draft was the indication that 
one needs to actually use a signalling session context identifiers. As I 
understand it, a compressor simply selects one from the available pool 
and establish it using a full context packet.


Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com




This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar  9 04:15:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16791
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 04:15:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0dKR-0004Uk-2G
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 04:15:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i299FAvM017277
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 04:15:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0dKI-0004Tn-MZ; Tue, 09 Mar 2004 04:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0dJg-0004Sq-Ip
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 04:14:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16729
	for <avt@ietf.org>; Tue, 9 Mar 2004 04:14:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0dJd-0004Ik-00
	for avt@ietf.org; Tue, 09 Mar 2004 04:14:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0dIi-00049N-00
	for avt@ietf.org; Tue, 09 Mar 2004 04:13:25 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0dHy-00040K-00
	for avt@ietf.org; Tue, 09 Mar 2004 04:12:38 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i299CdYG012492
	for <avt@ietf.org>; Tue, 9 Mar 2004 10:12:39 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 9 Mar 2004 10:12:39 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <GSLNTDQN>; Tue, 9 Mar 2004 10:12:38 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E949C@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "Magnus Westerlund (KI/EAB)" <magnus.westerlund@ericsson.com>,
        IETF AVT WG <avt@ietf.org>
Subject: RE: [AVT] Commetns on Header compression for MPLS LSPs (draft-ash
	-avt-ecrtp-over-mpls-protocol-00.txt)
Date: Tue, 9 Mar 2004 10:11:46 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 09 Mar 2004 09:12:39.0083 (UTC) FILETIME=[AB6387B0:01C405B6]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

One additional comment on this draft is that it has too much
background information, basically copied from the requirements
draft. Much of this could be stripped out, making the document
more compact and focused, as it refers to the requirements doc
anyway.

Apart from that, I fully agree with Magnus comments below.

/L-E

> -----Original Message-----
> From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf 
> Of Magnus
> Westerlund (KI/EAB)
> Sent: den 8 mars 2004 15:50
> To: IETF AVT WG
> Subject: [AVT] Commetns on Header compression for MPLS LSPs
> (draft-ash-avt-ecrtp-over-mpls-protocol-00.txt)
> 
> 
> Hi,
> 
> Having reviewed the solutions proposal document I would like 
> to take a 
> few steps back, and discuss the issues on a higher level. We 
> should also 
> not be carried into to much detail yet until the requirements work is 
> completed.
> 
> In my understanding we will need a few components in the total system.
> 
> A. A signalling protocol for an MPLS ingress router (A) to 
> determine/create the LSP that will go to a HC enabled egress 
> router (B). 
> That protocol seems to need to signal the following information:
> - What HC algorithms it support
> - What LSP that will go from A->B and for HC algorithms that uses 
> feedback the return path B->A, which indicates HC enabled packets.
> - Further HC algorithm parameters, for example maximum number 
> of session 
> contexts.
> 
> B. To create a mapping for the HC algorithm into the LSP. 
> Here it seems 
> that ECRTP would need to have identifiers for its packet types, while 
> ROHC would not need anything.
> 
> The solution does not require anything more as I see it. It can be 
> enhanced with description of how an ingress router determines 
> what flows 
> to do HC on, for example through the header compression hints 
> that exist 
> for RSVP, see RFC 3006. An ingress router can also use 
> heuristics or any 
> other method it desires to determine if it should apply header 
> compression on a certain packet flow. Thus I don't see a need to talk 
> about specific applications of RTP or UDP that can benefit 
> from this work.
> 
> Something else that I reacted to in the draft was the indication that 
> one needs to actually use a signalling session context 
> identifiers. As I 
> understand it, a compressor simply selects one from the 
> available pool 
> and establish it using a full context packet.
> 
> 
> Cheers
> 
> Magnus Westerlund
> 
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar  9 04:19:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16998
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 04:19:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0dOJ-0004tZ-3I
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 04:19:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i299JAET018766
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 04:19:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0dO9-0004mP-Mq; Tue, 09 Mar 2004 04:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0dNi-0004lE-P0
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 04:18:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16944
	for <avt@ietf.org>; Tue, 9 Mar 2004 04:18:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0dNf-00052X-00
	for avt@ietf.org; Tue, 09 Mar 2004 04:18:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0dMt-0004qk-00
	for avt@ietf.org; Tue, 09 Mar 2004 04:17:44 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0dLt-0004g3-00
	for avt@ietf.org; Tue, 09 Mar 2004 04:16:41 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i299GgAh000907
	for <avt@ietf.org>; Tue, 9 Mar 2004 10:16:42 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 9 Mar 2004 10:16:42 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <GSLNT10S>; Tue, 9 Mar 2004 10:16:41 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E949D@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "Magnus Westerlund (KI/EAB)" <magnus.westerlund@ericsson.com>,
        IETF AVT WG <avt@ietf.org>
Subject: RE: [AVT] Comments on draft-ash-avt-ecrtp-over-mpls-reqs-01.txt
Date: Tue, 9 Mar 2004 10:15:49 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 09 Mar 2004 09:16:42.0102 (UTC) FILETIME=[3C3D4960:01C405B7]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Magnus and others,

This captures very well the concerns I expressed on the AVT session,
I just want to stress point 5 a little bit. A brief summary of how
all candidate schemes (CRTP, eCRTP and ROHC) should be included,
explaining how each scheme would map to the needs, as well as what
would have to be added to make each scheme applicable.

/L-E

> -----Original Message-----
> From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf 
> Of Magnus
> Westerlund (KI/EAB)
> Sent: den 8 mars 2004 14:34
> To: IETF AVT WG
> Subject: [AVT] Comments on draft-ash-avt-ecrtp-over-mpls-reqs-01.txt
> 
> 
> Hi,
> 
> During the IETF meeting it was requested that we accept the 
> requirements 
> document as a AVT WG document. We have Allison's approval for taking 
> this on within the WG, so unless someone raises very good 
> reasons, this 
> will become a WG document. To get started on the first 
> version of the WG 
> document I like to give the following comments.
> 
> 1. I would like to documents title and filename to reflect what the 
> document is for, namely requirements for header compression 
> over MPLS. 
> It is not specific to ECRTP, although it appears a good match for the 
> requirements. It was unfortunate that the milestone specifies ECRTP, 
> however please remember to be a bit broader in the thinking. Thus I 
> would suggest that a new title: "Requirements for header compression 
> over MPLS". And as filename I would suggest 
> draft-ietf-avt-hc-mpls-req-00.txt for the first version.
> 
> 2. Two to get this document published as an informational 
> document the 
> editors would need to ensure that all ID nits are meet. This includes 
> things like page breaks at the right places, etc.
> 
> 3. To make the document a bit more agnostic to the actual header 
> compression standard used, I would suggest that one replaces most 
> occurrences in the abstract, and introduction  of ECRTP with 
> HC (Header 
> Compression).
> 
> 4. I would also like to warn about using RFC 2119 words as 
> they are in a 
> requirements document, it may make more sense to define them as it is 
> desired.
> 
> 5. I would also suggest that one tries to improve the motivation why 
> ECRTP is in fact the right header compression protocol to 
> use. To make 
> this clear I would recommend a section describing the 
> properties of MPLS 
> label switched path and what requirements that places on the header 
> compression algorithm. Also the actual requirements on the signalling 
> part needs to be considered.
> 
> 6. It would also be desirable if one could move some of the solution 
> conclusions in chapter 3 to its own chapter. Chapter 3 will 
> be clearer 
> if one concentrates on stating goals and requirements with their 
> motivation.
> 
> 
> Cheers
> 
> Magnus Westerlund
> 
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> 
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar  9 10:37:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01757
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 10:37:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0jHa-00042e-E0
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 10:36:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i29Facxa015369
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 10:36:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0jHB-0003ix-20; Tue, 09 Mar 2004 10:36:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0cAx-00076S-Rp
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 03:01:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13204
	for <avt@ietf.org>; Tue, 9 Mar 2004 03:01:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0cAt-0006k4-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:01:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0c9x-0006c0-00
	for avt@ietf.org; Tue, 09 Mar 2004 03:00:18 -0500
Received: from web40911.mail.yahoo.com ([66.218.78.208])
	by ietf-mx with smtp (Exim 4.12)
	id 1B0c94-0006M9-00
	for avt@ietf.org; Tue, 09 Mar 2004 02:59:22 -0500
Message-ID: <20040309075853.85538.qmail@web40911.mail.yahoo.com>
Received: from [161.85.127.140] by web40911.mail.yahoo.com via HTTP; Mon, 08 Mar 2004 23:58:53 PST
Date: Mon, 8 Mar 2004 23:58:53 -0800 (PST)
From: Raoul Mallart <raoul_mallart@yahoo.com>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1799781234-1078819133=:84772"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [AVT] AMR is not free anymore?
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

--0-1799781234-1078819133=:84772
Content-Type: text/plain; charset=us-ascii
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA13205
Content-Transfer-Encoding: quoted-printable

Was anybody aware that a licencing system has been put in place for AMR (=
RFC 3267) ?
=20
See http://www.voiceage.com/amr.html
=20
Any comment on the prices?
=20
My comment in one word:  WOW !
=20
Best regards


---------------------------------
Do you Yahoo!?
Yahoo! Search - Find what you=92re looking for faster.
--0-1799781234-1078819133=:84772
Content-Type: text/html; charset=us-ascii
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA13205
Content-Transfer-Encoding: quoted-printable

<DIV>Was anybody aware that a licencing system has been put in place for =
AMR (RFC 3267) ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>See <A href=3D"http://www.voiceage.com/amr.html">http://www.voiceage=
.com/amr.html</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>Any comment on the prices?</DIV>
<DIV>&nbsp;</DIV>
<DIV>My comment in one word:&nbsp; WOW !</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards</DIV><p><hr SIZE=3D1>
Do you Yahoo!?<br>
Yahoo! Search - <a href=3D"http://search.yahoo.com/?fr=3Dad-mailsig-home"=
>Find what you=92re looking for faster.</a>
--0-1799781234-1078819133=:84772--

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



From exim@www1.ietf.org  Tue Mar  9 10:37:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01776
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 10:37:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0jHa-00042c-DX
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 10:36:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i29Fac4E015371
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 10:36:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0jHM-0003qA-Fm; Tue, 09 Mar 2004 10:36:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0h64-00027B-6r
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 08:16:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25718
	for <avt@ietf.org>; Tue, 9 Mar 2004 08:16:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0h63-0000Vh-00
	for avt@ietf.org; Tue, 09 Mar 2004 08:16:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0h56-0000MV-00
	for avt@ietf.org; Tue, 09 Mar 2004 08:15:38 -0500
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0h4V-0000DQ-00
	for avt@ietf.org; Tue, 09 Mar 2004 08:14:59 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id i29DEsd16788;
	Tue, 9 Mar 2004 14:14:54 +0100 (MET)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i29DErV26127;
	Tue, 9 Mar 2004 14:14:53 +0100 (MET)
Received: from mchh274e.mchh.siemens.de (mchh274e.mchh.siemens.de [139.21.200.84])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id OAA20162;
	Tue, 9 Mar 2004 14:15:07 +0100 (MET)
Received: by mchh274e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <FFTVQ7H4>; Tue, 9 Mar 2004 14:14:51 +0100
Message-ID: <FF8AC5030873D6118BCB0002A58EDA990374C33F@MCHH2A7E>
From: Belling Thomas <thomas.belling@siemens.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Cc: avt@ietf.org
Subject: RE: [AVT] The need for Offer/Answer sections in RTP payload forma
	 t specifications
Date: Tue, 9 Mar 2004 14:14:49 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by goliath.siemens.de id i29DEsd16788
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi Magnus,

a rather late response to your email, but a draft standard replacing RFC3=
267 will probably not be available tomorrow anyway, with no internet draf=
t existing up to now.
I want to suggest some improvments to yout text, and start with an explan=
ation:


The main issue that needs to be clarified in my understanding is the diff=
erence between what Jonathan Rosenberg called *negotiated* or *declarativ=
e" attributes.
In RFC 3264, Section 6.1, I read:
"
   The interpretation of fmtp parameters in an offer depends on the
   parameters.  In many cases, those parameters describe specific
   configurations of the media format, and should therefore be processed
   as the media format value itself would be.  This means that the same
   fmtp parameters with the same values MUST be present in the answer if
   the media format they describe is present in the answer.  Other fmtp
   parameters are more like parameters, for which it is perfectly
   acceptable for each agent to use different values.  In that case, the
   answer MAY contain fmtp parameters, and those MAY have the same
   values as those in the offer, or they MAY be different.  SDP
   extensions that define new parameters SHOULD specify the proper
   interpretation in offer/answer.
"
As a general remark, it is beneficial to remember the recommendation of R=
FC 3264 to define an SDP offer/answer handling for MIME parameters when d=
efining new RTP payload types. I am not aware of examples where this has =
been followed up to now.


For the AMR MIME parameters, I see three classes:

1. Parameters defining the transport format:
(octet-align, crc, robust-sorting, interleaving, and channels)
The sender and receiver of an RTP stream need to agree on the transport f=
ormat to be used.
For a bidirectional media stream, one could try to allow different transp=
ort formats for the RTP IP flows in different directions. However, I do n=
ot see a real requirement for such semantics. It is highly probable that =
a host supports the same transport format both for sending and receiving.=
 And it seems to be difficult to find SDP offer-answer semantics that wou=
ld allow expressing different transport formats for both directions, whil=
e at the same time satisfying the requirement that both an RTP sender an =
an RTP receiver needs to express a supported transport format.
I therefore suggest that an SDP answerer MUST include these parameters un=
modified compared to the SDP offer.
Between the lines of your proposed text, I read that you have the same un=
derstanding.

2. packetisation time (ptime,maxptime)
In RFC 3264, Section 6.1, the handling is defined for "ptime", and "maxpt=
ime" should follow the same principle. For a bidirectional media stream, =
it is allowed to use different packetisation times for IP flows in opposi=
te directions:
"
   The answerer MAY include a non-zero ptime attribute for any media
   stream; this indicates the packetization interval that the answerer
   would like to receive.  There is no requirement that the
   packetization interval be the same in each direction for a particular
   stream.
...
   Once the answerer has sent the answer, it MUST be prepared to receive
   media for any recvonly streams described by that answer.  ...
   When sending media, it SHOULD use a packetization
   interval equal to the value of the ptime attribute in the offer, if
   any was present.
"

3. Codec configuration Parameters ("mode-set", "mode-change-period", and
"mode-change-neighbor").  Demanding that these parameters are equal in SD=
P offer and answer would lead to a high call failure rate, as there is a =
fair chance that hosts do not support all conceivable combinations of the=
se parameters. For instance, an SDP answerer might support only a subset =
of the modes in the mode set of the SDP offer. Furthermore, an AMR client=
 might not support a mode-change-period other than 1 or a restriction to =
mode-change-neighbor when sending, but be capable to handle received AMR =
with other settings. The interoberability to the usage in 3GPP should als=
o be considered when defining a proper handling of these parameters. In p=
articular, the parameters mode-change-period", and "mode-change-neighbor"=
 were probably introduced with this as only purpose. In the interworking =
scenarios with the Cs domain of 3GPP, the network is able to insert trans=
coders, if a mismatch of the parameters between SDP offer and answer occu=
rs, and therefore priority should be given to call completion. I suggest =
defining suitable negotiation rules for all of these parameters.
The tricky issue will be backward compatibility to RFC3264, where the rul=
es were open. My hope for the "mode-set" parameter is that the suggested =
rules were intuitively followed in implementations. My hope for the "mode=
-change-period" and "mode-change-neighbor" parameters is that they were n=
ot used up to now.


As a minor issue,I noticed that RFC 3264 states in clause 4.5:
"To achieve basic interoperability an implementation SHOULD at least impl=
ement both
bandwidth-efficient and octet-aligned mode for single channel."
You suggest "the offerer is RECOMMENDED to also offer an payload type con=
taining only the
octet-align configuration with a single channel"
The restriction to octet alligned seems a bit arbitrary, and I would ther=
efore suggest recommending  that either a simple octet-alligned or bandwi=
dth-efficient configuration should also be offered.



I would therefore like to suggest the following improvments to your text =
(marked as >>>   <<<) :


8.3.1 Offer-Answer Model Considerations

To achieve good interoperability with the AMR or the AMR-WB RTP payload
in an Offer-Answer usage in SDP >>>[RFC3264]<<< the following >>>applies<=
<<:

- Each combination of the RTP payload >>>transport format<<< configuratio=
n parameters
(octet-align, crc, robust-sorting, interleaving, and channels) is unique
in its bit-pattern and not compatible with any other combination. Due to
the application dependent nature of any configuration and they being
optionally to implement, care must be taken. When creating an offer in
an application desiring to use the more advance features (crc,
robust-sorting, interleaving, or more than one channel), the offerer is
RECOMMENDED to also offer an payload type containing only the
octet-align >>> or bandwidth efficient <<< configuration with a single ch=
annel. If multiple
configurations are of interest to the application they may all be
offered, however care should be taken to not offer too many payload types.
>>> An SDP answerer MUST include the received parameters "octet-align", "=
crc",
"robust-sorting", "interleaving" and "channels" for a media format in the=
 SDP offer unmodified in the SDP answer, unless it removes the media form=
at. The SDP offerer and answerer MUST encode AMR or WB-AMR packets for th=
is media format as described by these parameters.<<<

>>>
- If an SDP offer containing a "mode-set" parameter for a media format is=
 received, the SDP answerer MUST include the "mode-set" parameter for thi=
s media format in the SDP answer, unless it removes the media format. The=
 SDP answerer MUST remove modes it does not support from the mode set, an=
d MUST NOT add any modes. If no mode set for a media format was contained=
 in the SDP offer, but the SDP answerer does not support all modes, the S=
DP answerer MUST include a "mode-set" parameter without the unsupported m=
odes for the media format in the SDP answer, unless it removes the media =
format. The SDP answerer MAY also remove modes it does support but not wa=
nt to use. The SDP offerer and answerer MUST only use the modes in the SD=
P answer to encode AMR or WB-AMR and to request mode changes. <<<


- The parameters "mode-change-period" and "mode-change-neighbor" SHOULD o=
nly be used when really needed due to gateway scenarios.
>>>In an SDP offer, the parameters express the configuration the offerer =
will use to encode AMR or WB-AMR of a media format, and also the configur=
ation it whishes for received AMR or WB-AMR. If an SDP offer for a media =
format is received, and the SDP answerer is not capable to decode AMR or =
WB-AMR with the "mode-change-period" and "mode-change-neighbor" configura=
tion implied in the offer for this media format, the SDP answerer MUST re=
ject this media format. Otherwise, if an SDP offer for a media format is =
received, and the SDP answerer is not capable to encode AMR or WB-AMR wit=
h the "mode-change-period" and "mode-change-neighbor" configuration impli=
ed in the offer, the SDP answer MUST include a "mode-change-period" and "=
mode-change-neighbor" configuration it is capable to encode in the SDP an=
swer for this media format, unless it removes the media format. Otherwise=
, if an SDP answer containing the parameter "mode-change-period" or "mode=
-change-neighbor" for a media format is received, the SDP answerer SHOULD=
 include the parameter unmodified in the SDP answer. The SDP answerer MUS=
T encode AMR or WB-AMR as expressed by the "mode-change-period" and "mode=
-change-neighbor" configuration in the SDP answer. If the SDP offerer rec=
eives an SDP answer with a "mode-change-period" and "mode-change-neighbor=
" configuration it is not able to decode, the SDP offerer MUST reject thi=
s media format in a new SDP offer.<<< (For backward compatibility, perhap=
s some "MUST"s need to become "SHOULD"s, depending what has alredy been i=
mplemented)


- The parameters "maxptime" and "ptime" >>will<< in most cases not >>a<<f=
fect
the interoperability, however the setting of the parameters can >>a<<ffec=
t
the performance of the application. >>> The SDP offer-answer handling of =
the "ptime" parameter is described in [RFC3264]. The "maxptime" parameter=
 MUST be handled in the same way. <<<




Best regards, Thomas

----------------------------------
Dr. Thomas Belling
Siemens AG          =20
Sankt-Martin-Str. 76=20
D-81541 M=FCnchen Germany
ICM N PG SP ST N1
MCH M 34 307
Tel     +49 89 636 75207
Fax     +49 89 636 75577
Mobile  +49 172 2974678
Email   Thomas.Belling@siemens.com




-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Tuesday, January 27, 2004 11:57 AM
To: Belling Thomas
Cc: avt@ietf.org
Subject: Re: [AVT] The need for Offer/Answer sections in RTP payload form=
a t specifications


Hi Thomas,

Belling Thomas wrote:

>Dear Magnus and Collin,
>
>thank you for this initiative.
>We also had some internal dicussions about the AMR RTP payload format,
>RFC 3267, with that respect.
>Is there any intention to remmedy this, e.g. by updating the RFC or
>writing an additional one?
>
>Best regards, Thomas
>
> =20
>

We authors are planning on updating RFC 3267 to go draft standard, then=20
we can address this.. We will also fix some small issues with the text,=20
however the current errata for RFC 3267 is very short.

I have written an initial proposal for this text which I include below,=20
however please remember that it is a first version. Comments are welcome.

Cheers

Magnus

---------- Text Proposal for new chapter 8.3 -------------
8.3. Mapping MIME Parameters into SDP

  The information carried in the MIME media type specification has a
  specific mapping to fields in the Session Description Protocol (SDP)
  [11], which is commonly used to describe RTP sessions.  When SDP is
  used to specify sessions employing the AMR or AMR-WB codec, the
  mapping is as follows:

     -  The MIME type ("audio") goes in SDP "m=3D" as the media name.

     -  The MIME subtype (payload format name) goes in SDP "a=3Drtpmap"
        as the encoding name.  The RTP clock rate in "a=3Drtpmap" 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].

     -  The parameters "ptime" and "maxptime" go in the SDP "a=3Dptime"
        and "a=3Dmaxptime" attributes, respectively.

     -  Any remaining parameters go in the SDP "a=3Dfmtp" attribute by
        copying them directly from the MIME media type string as a
        semicolon separated list of parameter=3Dvalue pairs.

8.3.1 Offer-Answer Model Considerations

To achieve good interoperability with the AMR or the AMR-WB RTP payload
in an Offer-Answer usage in SDP the following considerations should be ma=
de:

- Each combination of the RTP payload configuration parameters
(octet-align, crc, robust-sorting, interleaving, and channels) is unique
in its bit-pattern and not compatible with any other combination. Due to
the application dependent nature of any configuration and they being
optionally to implement, care must be taken. When creating an offer in
an application desiring to use the more advance features (crc,
robust-sorting, interleaving, or more than one channel), the offerer is
RECOMMENDED to also offer an payload type containing only the
octet-align configuration with a single channel. If multiple
configurations are of interest to the application they may all be
offered, however care should be taken to not offer too many payload types.

- The parameters "mode-set", "mode-change-period", and
"mode-change-neighbor" SHOULD only be used when really needed due to
gateway scenarios, however their nature are such that they must either
be supported or no interoperability exist.

- The parameters "maxptime" and "ptime" should in most cases not effect
the interoperability, however the setting of the parameters can effect
the performance of the application.

8.3.2 Examples

  Some example SDP session descriptions utilizing AMR and AMR-WB
  encodings follow.  In these examples, long a=3Dfmtp lines are folded to
  meet the column width constraints of this document; the backslash
  ("\") at the end of a line and the carriage return that follows it
  should be ignored.

  Example of usage of AMR in a possible GSM gateway scenario:

   m=3Daudio 49120 RTP/AVP 97
   a=3Drtpmap:97 AMR/8000/1
   a=3Dfmtp:97 mode-set=3D0,2,5,7; mode-change-period=3D2; \
     mode-change-neighbor=3D1
   a=3Dmaxptime:20

  Example of usage of AMR-WB in a possible VoIP scenario where UEP may
be used (99) and a fallback declaration (98):

   m=3Daudio 49120 RTP/AVP 99 98
   a=3Drtpmap:99 AMR-WB/16000
   a=3Dfmtp:99 octet-align=3D1; crc=3D1
   a=3Drtpmap:98 AMR-WB/16000
   a=3Dfmtp:98 octet-align=3D1

  Example of usage of AMR-WB in a possible streaming scenario (two
  channel stereo):

   m=3Daudio 49120 RTP/AVP 99 100
   a=3Drtpmap:99 AMR-WB/16000/2
   a=3Dfmtp:99 interleaving=3D30
   a=3Dmaxptime:100

  Note that the payload format (encoding) names are commonly shown in
  upper case.  MIME subtypes are commonly shown in lower case.  These
  names are case-insensitive in both places.  Similarly, parameter
  names are case-insensitive both in MIME types and in the default
  mapping to the SDP a=3Dfmtp attribute.



--=20

Magnus Westerlund=20

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


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



From exim@www1.ietf.org  Tue Mar  9 11:46:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07570
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 11:46:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0kMw-0007f7-W1
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 11:46:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i29GkEuJ029407
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 11:46:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0kMm-0007bb-76; Tue, 09 Mar 2004 11:46:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0kMg-0007a1-BY
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 11:45:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07541
	for <avt@ietf.org>; Tue, 9 Mar 2004 11:45:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0kMf-0001EC-00
	for avt@ietf.org; Tue, 09 Mar 2004 11:45:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0kLi-00013A-00
	for avt@ietf.org; Tue, 09 Mar 2004 11:44:58 -0500
Received: from m205-235.dsl.tsoft.com ([198.144.205.235] helo=lists.herlein.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0kKY-0000s9-00
	for avt@ietf.org; Tue, 09 Mar 2004 11:43:46 -0500
Received: from folly.herlein.com (folly.herlein.com [192.168.70.5])
	by lists.herlein.com (Postfix) with ESMTP id 0E09F96E
	for <avt@ietf.org>; Tue,  9 Mar 2004 08:55:11 -0800 (PST)
Date: Tue, 9 Mar 2004 08:43:46 -0800 (PST)
From: Greg Herlein <gherlein@herlein.com>
To: avt@ietf.org
Subject: Re: [AVT] AMR is not free anymore?
In-Reply-To: <20040309075853.85538.qmail@web40911.mail.yahoo.com>
Message-ID: <Pine.LNX.4.58.0403090840320.4527@folly.herlein.com>
References: <20040309075853.85538.qmail@web40911.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

> Was anybody aware that a licencing system has been put in place
> for AMR (RFC 3267) ?

Gee, all the more reason for folks to take a serious look at 
the speex codec, which is believed to be patent free, and is 100% 
open source and licensed with a variant of the BSD license so 
it's quite commercial friendly.

	http://www.speex.org/

Greg Herlein

PS - a draft RTP payload format for speex is awaiting posting 
with the draft administrators - I expect it to be posted in the 
next few days.



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



From exim@www1.ietf.org  Tue Mar  9 22:52:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15946
	for <avt-archive@odin.ietf.org>; Tue, 9 Mar 2004 22:52:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0uks-0000er-T8
	for avt-archive@odin.ietf.org; Tue, 09 Mar 2004 22:51:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2A3pcXe002480
	for avt-archive@odin.ietf.org; Tue, 9 Mar 2004 22:51:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0ukI-0000Yz-24; Tue, 09 Mar 2004 22:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0ujg-0000Xd-7x
	for avt@optimus.ietf.org; Tue, 09 Mar 2004 22:50:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15822
	for <avt@ietf.org>; Tue, 9 Mar 2004 22:50:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0ujc-0005wB-00
	for avt@ietf.org; Tue, 09 Mar 2004 22:50:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0uig-0005ju-00
	for avt@ietf.org; Tue, 09 Mar 2004 22:49:23 -0500
Received: from ns.live.com ([66.80.62.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0uhn-0005Z2-00
	for avt@ietf.org; Tue, 09 Mar 2004 22:48:27 -0500
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.12.11/8.12.10) with ESMTP id i2A3mRs5055818
	for <avt@ietf.org>; Tue, 9 Mar 2004 19:48:27 -0800 (PST)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.12.11/8.12.9/Submit) id i2A3mRwO055817;
	Tue, 9 Mar 2004 19:48:27 -0800 (PST)
	(envelope-from rsf)
Message-Id: <6.0.1.1.1.20040309194348.02782730@localhost>
X-Sender: rsf@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 09 Mar 2004 19:48:15 -0800
To: avt@ietf.org
From: Ross Finlayson <finlayson@live.com>
Subject: Re: [AVT] AMR is not free anymore?
In-Reply-To: <20040309075853.85538.qmail@web40911.mail.yahoo.com>
References: <20040309075853.85538.qmail@web40911.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

At 11:58 PM 3/8/04, Raoul Mallart wrote:
>Was anybody aware that a licencing system has been put in place for AMR 
>(RFC 3267) ?

Just so there's no confusion: This licensing system applies to the use of 
AMR *encoders* or *decoders* - not to the use of RFC 3267, which describes 
merely how (already-encoded) AMR frames are transported using RTP.

There is no Intellectual Property Notice attached to RFC 3267, and (AFAIK) 
noone is claiming that RFC 3267 infringes upon any patents.


	Ross Finlayson
	LIVE.COM
	<http://www.live.com/>


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



From exim@www1.ietf.org  Wed Mar 10 03:01:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25022
	for <avt-archive@odin.ietf.org>; Wed, 10 Mar 2004 03:01:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0yeN-00008O-SY
	for avt-archive@odin.ietf.org; Wed, 10 Mar 2004 03:01:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2A81Bag000467
	for avt-archive@odin.ietf.org; Wed, 10 Mar 2004 03:01:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0yeF-00006W-24; Wed, 10 Mar 2004 03:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0yde-0008TG-5Q
	for avt@optimus.ietf.org; Wed, 10 Mar 2004 03:00:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24962
	for <avt@ietf.org>; Wed, 10 Mar 2004 03:00:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0yda-0002Fa-00
	for avt@ietf.org; Wed, 10 Mar 2004 03:00:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0ycf-00026i-00
	for avt@ietf.org; Wed, 10 Mar 2004 02:59:25 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0ycP-0001xf-00
	for avt@ietf.org; Wed, 10 Mar 2004 02:59:09 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2A7x2YG020614
	for <avt@ietf.org>; Wed, 10 Mar 2004 08:59:06 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 10 Mar 2004 08:59:02 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id FYFT8VLR; Wed, 10 Mar 2004 08:59:54 +0100
Message-ID: <404ECA0B.9050109@ericsson.com>
Date: Wed, 10 Mar 2004 08:55:55 +0100
X-Sybari-Trust: db139671 2c4885b5 73569057 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Subject: Re: [AVT] AMR is not free anymore?
References: rsf@localhost (Unverified) <6.0.1.1.1.20040309194348.02782730@localhost>
In-Reply-To: <6.0.1.1.1.20040309194348.02782730@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Mar 2004 07:59:02.0004 (UTC) FILETIME=[8D048340:01C40675]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

[To be very clear, this response is definitely without my Chair-hat]

To all of my knowledge no IPR claims exist in relation to the RTP 
payload format (RFC 3267). That the codec was encumbered has been known 
since the standardization of the codec.

Please do notice that it is possible to build certain applications which 
only has AMR decoder functionality that does not have per unit/channels 
charges associated with them in regards to the patent pool.

Regards

Magnus


Ross Finlayson wrote:

> At 11:58 PM 3/8/04, Raoul Mallart wrote:
> 
>>Was anybody aware that a licencing system has been put in place for AMR
> 
> 
>>(RFC 3267) ?
> 
> 
> Just so there's no confusion: This licensing system applies to the use
> of 
> AMR *encoders* or *decoders* - not to the use of RFC 3267, which
> describes 
> merely how (already-encoded) AMR frames are transported using RTP.
> 
> There is no Intellectual Property Notice attached to RFC 3267, and
> (AFAIK) 
> noone is claiming that RFC 3267 infringes upon any patents.
> 
> 
> 	Ross Finlayson
> 	LIVE.COM
> 	<http://www.live.com/>
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Wed Mar 10 07:43:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06061
	for <avt-archive@odin.ietf.org>; Wed, 10 Mar 2004 07:43:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B133I-0006uq-Rr
	for avt-archive@odin.ietf.org; Wed, 10 Mar 2004 07:43:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AChCJ4026580
	for avt-archive@odin.ietf.org; Wed, 10 Mar 2004 07:43:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1337-0006ts-B5; Wed, 10 Mar 2004 07:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B132F-0006rY-0Q
	for avt@optimus.ietf.org; Wed, 10 Mar 2004 07:42:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06000
	for <avt@ietf.org>; Wed, 10 Mar 2004 07:42:06 -0500 (EST)
From: Oleg.Litvak@ecitele.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B132E-0004x8-00
	for avt@ietf.org; Wed, 10 Mar 2004 07:42:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B130r-0004ms-00
	for avt@ietf.org; Wed, 10 Mar 2004 07:40:42 -0500
Received: from mink.ecitele.com ([147.234.1.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B130R-0004dR-00; Wed, 10 Mar 2004 07:40:15 -0500
Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125])
	by mink.ecitele.com (8.12.10+Sun/8.12.10) with ESMTP id i2ACYbE2024830;
	Wed, 10 Mar 2004 14:34:38 +0200 (IST)
Subject: Re: [AVT] Last Call: 'Tunneling multiplexed Compressed RTP ('TCRTP')' to
 BCP
To: iesg@ietf.org, avt@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OFF52063EE.E9F6C1EF-ONC2256E53.003B2BE7@ecitele.com>
Date: Wed, 10 Mar 2004 14:40:09 +0200
X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at
 03/10/2004 02:40:12 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>


Dear colleagues,

The TCRTP method improves the bandwidth utilization of RTP streams by a
combination of standard protocols. These  provide
compression, multiplexing, and tunneling over a network path. This method,
may be used for RTP multiplexing standardization but there are some
disadvantages which may be overcome using other methods. The disadvantages
of the TCRTP method are as follows:
   not applicable for networks with packet loss >5%
   does not allow operation through NAT/PAT devices
   allows only one tunnel between peers
   does not save a tunnel in switching to backup IP interface
   L2TP protocol, as an essential part of TCRTP, is too complex for this
   application

I suggest doing the following:
   remove prohibition of development of other RTP multiplexing standards
   from TCRTP abstract  draft
   define unambiguously application area and conditions of the TCRTP Method
   define scope of the document

Best regards.

Oleg Litvak
Associate VP - VoIP System Architect

VERAZ Networks Ltd.
Tel:  +972-3-9266576
Mobile:     +972-55-786576
Fax:  +972-3-9268300
E-mail:     Oleg.Litvak@veraznetworks.com
http://www.veraznetworks.com




                                                                                                                                       
                      The IESG                                                                                                         
                      <iesg-secretary@         To:      IETF-Announce :;                                                               
                      ietf.org>                cc:                                                                                     
                      Sent by:                 Subject: [AVT] Last Call: 'Tunneling multiplexed Compressed RTP ('TCRTP')' to BCP       
                      avt-admin@ietf.o                                                                                                 
                      rg                                                                                                               
                                                                                                                                       
                                                                                                                                       
                      16/02/2004 18:19                                                                                                 
                      Please respond                                                                                                   
                      to iesg                                                                                                          
                                                                                                                                       
                                                                                                                                       



The IESG has received a request from the Audio/Video Transport WG to
conside

the following document:

- 'Tunneling multiplexed Compressed RTP ('TCRTP') '
   <draft-ietf-avt-tcrtp-07.txt> as a BCP

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 2004-03-12.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-avt-tcrtp-07.txt


_______________________________________________
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 exim@www1.ietf.org  Wed Mar 10 10:38:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16041
	for <avt-archive@odin.ietf.org>; Wed, 10 Mar 2004 10:38:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15mu-0006Kp-DL
	for avt-archive@odin.ietf.org; Wed, 10 Mar 2004 10:38:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AFcSuu024297
	for avt-archive@odin.ietf.org; Wed, 10 Mar 2004 10:38:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15ko-0005wY-AF; Wed, 10 Mar 2004 10:36:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15ji-0005td-Mt
	for avt@optimus.ietf.org; Wed, 10 Mar 2004 10:35:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15685
	for <avt@ietf.org>; Wed, 10 Mar 2004 10:34:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B15jW-0005Mm-00
	for avt@ietf.org; Wed, 10 Mar 2004 10:34:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B15iJ-0005B6-00
	for avt@ietf.org; Wed, 10 Mar 2004 10:33:44 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B15hQ-000521-00
	for avt@ietf.org; Wed, 10 Mar 2004 10:32:48 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id i2AFWjd18007
	for <avt@ietf.org>; Wed, 10 Mar 2004 16:32:45 +0100 (MET)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id i2AFWiV18637
	for <avt@ietf.org>; Wed, 10 Mar 2004 16:32:44 +0100 (MET)
Received: from mchh274e.mchh.siemens.de (mchh274e.mchh.siemens.de [139.21.200.84])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id QAA20989
	for <avt@ietf.org>; Wed, 10 Mar 2004 16:33:03 +0100 (MET)
Received: by mchh274e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <FFTVR9B1>; Wed, 10 Mar 2004 16:32:43 +0100
Message-ID: <FF8AC5030873D6118BCB0002A58EDA990374C347@mchh2a7e.mchh.siemens.de>
From: Belling Thomas <thomas.belling@siemens.com>
To: "'avt@ietf.org'" <avt@ietf.org>
Date: Wed, 10 Mar 2004 16:32:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C406B4.EC04C212"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_40_50,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [AVT] minor improvment to RFC3267
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

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_01C406B4.EC04C212
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Magnus, all,

I would like another minor improvment to RFC3267, that you may consider =
for a possible bis draft.

Clause 8.1 now reads:
"
      mode-set:  Requested AMR mode set.  Restricts the active codec
               mode set to a subset of all modes.  Possible values are =
a
               comma separated list of modes from the set: 0,...,7 (see
               Table 1a [2]).  If such mode set is specified by the
               decoder, the encoder MUST abide by the request and MUST
               NOT use modes outside of the subset.  If not present, =
all
               codec modes are allowed for the session.
"

The text as it is right now rules out that you use the SID mode 8 in =
combination with a restricted mode set.

As an editorial thing, I also suggest replacing the Reference to Table =
1a in 3GPP TS 26.101 with an internal Reference to table 1 in the RFC, =
as the information is identical and this enhances the readability.

I would suggest the following improved text, which is in line with the =
usage within 3GPP:
"
      mode-set:  Requested AMR mode set.  Restricts the active codec
               mode set to a subset of all modes.  Possible values are =
a
               comma separated list of modes from the set: 0,...,7 (see
               Table 1). The SID mode 8 is never included in the mode =
set, but
               may always be used.  If a mode set is specified by the
               decoder, the encoder MUST abide by the request and MUST
               NOT use modes outside of the subset except for mode 8.
               If not present, all  codec modes are allowed for the =
session.
"

A similar change should be done in Clause 8.2 for WB-AMR:
"
      mode-set:  Requested AMR-WB mode set.  Restricts the active codec
               mode set to a subset of all modes.  Possible values are =
a
               comma separated list of modes from the set: 0,...,8 (see
               Table 1a [4]). The SID mode 9 is never included in the =
mode set, but
               may always be used.  If a mode set is specified by the
               decoder, the encoder MUST abide by the request and MUST
               NOT use modes outside of the subset except for mode 9.
               If not present, all  codec modes are allowed for the =
session.
"


Best regards, Thomas


----------------------------------
Dr. Thomas Belling
Siemens AG          =20
Sankt-Martin-Str. 76=20
D-81541 M=FCnchen Germany
ICM N PG SP ST N1
MCH M 34 307
Tel     +49 89 636 75207
Fax     +49 89 636 75577
Mobile  +49 172 2974678
Email   Thomas.Belling@siemens.com




------_=_NextPart_001_01C406B4.EC04C212
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.2657.73">
<TITLE>minor improvment to RFC3267</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Dear Magnus, all,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I would like another minor improvment =
to RFC3267, that you may consider for a possible bis draft.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Clause 8.1 now reads:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
mode-set:&nbsp; Requested AMR mode set.&nbsp; Restricts the active =
codec</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; mode set to a subset of all modes.&nbsp; =
Possible values are a</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; comma separated list of modes from the set: =
0,...,7 (see</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1a [2]).&nbsp; If such mode set is =
specified by the</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; decoder, the encoder MUST abide by the =
request and MUST</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; NOT use modes outside of the subset.&nbsp; =
If not present, all</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; codec modes are allowed for the =
session.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The text as it is right now rules out =
that you use the SID mode 8 in combination with a restricted mode =
set.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As an editorial thing, I also suggest =
replacing the Reference to Table 1a in 3GPP TS 26.101 with an internal =
Reference to table 1 in the RFC, as the information is identical and =
this enhances the readability.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I would suggest the following improved =
text, which is in line with the usage within 3GPP:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
mode-set:&nbsp; Requested AMR mode set.&nbsp; Restricts the active =
codec</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; mode set to a subset of all modes.&nbsp; =
Possible values are a</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; comma separated list of modes from the set: =
0,...,7 (see</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1). The SID mode 8 is never included =
in the mode set, but</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; may always be used.&nbsp; If a mode set is =
specified by the</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; decoder, the encoder MUST abide by the =
request and MUST</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; NOT use modes outside of the subset except =
for mode 8.</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; If not present, all&nbsp; codec modes are =
allowed for the session.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A similar change should be done in =
Clause 8.2 for WB-AMR:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
mode-set:&nbsp; Requested AMR-WB mode set.&nbsp; Restricts the active =
codec</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; mode set to a subset of all modes.&nbsp; =
Possible values are a</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; comma separated list of modes from the set: =
0,...,8 (see</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1a [4]). The SID mode 9 is never =
included in the mode set, but</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; may always be used.&nbsp; If a mode set is =
specified by the</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; decoder, the encoder MUST abide by the =
request and MUST</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; NOT use modes outside of the subset except =
for mode 9.</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; If not present, all&nbsp; codec modes are =
allowed for the session.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best regards, Thomas</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier =
New">----------------------------------</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Dr. Thomas Belling</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Siemens =
AG&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Sankt-Martin-Str. 76 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">D-81541 M=FCnchen =
Germany</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">ICM N PG SP ST N1</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">MCH M 34 307</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Tel&nbsp;&nbsp;&nbsp;&nbsp; +49 =
89 636 75207</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Fax&nbsp;&nbsp;&nbsp;&nbsp; +49 =
89 636 75577</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Mobile&nbsp; +49 172 =
2974678</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Email&nbsp;&nbsp; =
Thomas.Belling@siemens.com</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C406B4.EC04C212--

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



From exim@www1.ietf.org  Thu Mar 11 02:32:03 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16724
	for <avt-archive@odin.ietf.org>; Thu, 11 Mar 2004 02:32:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1KfB-0005tp-1w
	for avt-archive@odin.ietf.org; Thu, 11 Mar 2004 02:31:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2B7VSD5022672
	for avt-archive@odin.ietf.org; Thu, 11 Mar 2004 02:31:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1Kel-0005qc-AD; Thu, 11 Mar 2004 02:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1Ke5-0005nY-MS
	for avt@optimus.ietf.org; Thu, 11 Mar 2004 02:30:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16664
	for <avt@ietf.org>; Thu, 11 Mar 2004 02:30:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1Ke1-0005QY-00
	for avt@ietf.org; Thu, 11 Mar 2004 02:30:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1Kd7-00059z-00
	for avt@ietf.org; Thu, 11 Mar 2004 02:29:22 -0500
Received: from beta.dmz-eu.st.com ([164.129.1.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1KcP-0004sq-00; Thu, 11 Mar 2004 02:28:37 -0500
Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9])
	by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP
	id 9FF9DDD65; Thu, 11 Mar 2004 07:27:52 +0000 (GMT)
Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 60012)
	id 7BD54F40C; Thu, 11 Mar 2004 07:27:52 +0000 (GMT)
Received: from mail1.agr.st.com (localhost [127.0.0.1])
	by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP
	id 12FC712301; Thu, 11 Mar 2004 07:27:52 +0000 (GMT)
Received: from st.com (agr53.agr.st.com [164.130.17.161])
	by mail1.agr.st.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AAD01738 (AUTH "diego melpignano");
	Thu, 11 Mar 2004 08:27:50 +0100 (CET)
Message-ID: <405014F6.17CC6892@st.com>
Date: Thu, 11 Mar 2004 08:27:50 +0100
From: Diego MELPIGNANO <diego.melpignano@st.com>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Oleg.Litvak@ecitele.com
Cc: iesg@ietf.org, avt@ietf.org
Subject: Re: [AVT] Last Call: 'Tunneling multiplexed Compressed RTP ('TCRTP')' 
 toBCP
References: <OFF52063EE.E9F6C1EF-ONC2256E53.003B2BE7@ecitele.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear Oleg and all,
also in my opinion the TCRTP abstract is too strong in prohibiting other RTP multiplexing schemes.
There are other application domains where RTP multiplexing is a desirable feature but an L2TP tunnel is not.
This advocates for a better definition of the application domain and the scope of this standard, which seems to be limited to "large
voice trunking applications".
I would suggest this is clearly highlighted in the abstract as well as in the introduction.

    Take care.

    Diego.

Oleg.Litvak@ecitele.com wrote:

> Dear colleagues,
>
> The TCRTP method improves the bandwidth utilization of RTP streams by a
> combination of standard protocols. These  provide
> compression, multiplexing, and tunneling over a network path. This method,
> may be used for RTP multiplexing standardization but there are some
> disadvantages which may be overcome using other methods. The disadvantages
> of the TCRTP method are as follows:
>    not applicable for networks with packet loss >5%
>    does not allow operation through NAT/PAT devices
>    allows only one tunnel between peers
>    does not save a tunnel in switching to backup IP interface
>    L2TP protocol, as an essential part of TCRTP, is too complex for this
>    application
>
> I suggest doing the following:
>    remove prohibition of development of other RTP multiplexing standards
>    from TCRTP abstract  draft
>    define unambiguously application area and conditions of the TCRTP Method
>    define scope of the document
>
> Best regards.
>
> Oleg Litvak
> Associate VP - VoIP System Architect
>
> VERAZ Networks Ltd.
> Tel:  +972-3-9266576
> Mobile:     +972-55-786576
> Fax:  +972-3-9268300
> E-mail:     Oleg.Litvak@veraznetworks.com
> http://www.veraznetworks.com
>
>
>                       The IESG
>                       <iesg-secretary@         To:      IETF-Announce :;
>                       ietf.org>                cc:
>                       Sent by:                 Subject: [AVT] Last Call: 'Tunneling multiplexed Compressed RTP ('TCRTP')' to BCP
>                       avt-admin@ietf.o
>                       rg
>
>
>                       16/02/2004 18:19
>                       Please respond
>                       to iesg
>
>
>
> The IESG has received a request from the Audio/Video Transport WG to
> conside
>
> the following document:
>
> - 'Tunneling multiplexed Compressed RTP ('TCRTP') '
>    <draft-ietf-avt-tcrtp-07.txt> as a BCP
>
> 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 2004-03-12.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-avt-tcrtp-07.txt
>
> _______________________________________________
> 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

--
Diego Melpignano
Advanced System Technologies - ST Microelectronics
Centro direzionale Colleoni, building "la Dialettica"
20041 Agrate Brianza ITALY
t. +39 039 603 7409 -  f. +39 039 603 6129
mailto:diego.melpignano@st.com



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



From exim@www1.ietf.org  Fri Mar 12 18:32:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27473
	for <avt-archive@odin.ietf.org>; Fri, 12 Mar 2004 18:32:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1w8W-0001XH-Ug
	for avt-archive@odin.ietf.org; Fri, 12 Mar 2004 18:32:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2CNWGPU005899
	for avt-archive@odin.ietf.org; Fri, 12 Mar 2004 18:32:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1w8H-0001WY-Mz; Fri, 12 Mar 2004 18:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1w89-0001Vq-8b
	for avt@optimus.ietf.org; Fri, 12 Mar 2004 18:31:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27442
	for <avt@ietf.org>; Fri, 12 Mar 2004 18:31:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1w86-0007h7-00
	for avt@ietf.org; Fri, 12 Mar 2004 18:31:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1w78-0007fH-00
	for avt@ietf.org; Fri, 12 Mar 2004 18:30:50 -0500
Received: from gamma.isi.edu ([128.9.144.145])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1w6b-0007dl-00; Fri, 12 Mar 2004 18:30:17 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i2CNUHk10901;
	Fri, 12 Mar 2004 15:30:17 -0800 (PST)
Message-Id: <200403122330.i2CNUHk10901@gamma.isi.edu>
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, avt@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 12 Mar 2004 15:30:17 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.0 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Subject: [AVT] RFC 3711 on The Secure Real-time Transport Protocol (SRTP)
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3711

        Title:      The Secure Real-time Transport Protocol (SRTP)
        Author(s):  M. Baugher, D. McGrew, M. Naslund, E. Carrara,
                    K. Norrman
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    mbaugher@cisco.com, mcgrew@cisco.com,
                    mats.naslund@ericsson.com,
                    elisabetta.carrara@ericsson.com,
                    karl.norrman@ericsson.com
        Pages:      56
        Characters: 134270
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-srtp-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3711.txt


This document describes the Secure Real-time Transport Protocol
(SRTP), a profile of the Real-time Transport Protocol (RTP), which
can provide confidentiality, message authentication, and replay
protection to the RTP traffic and to the control traffic for RTP,
the Real-time Transport Control Protocol (RTCP).

This document is a product of Audio/Video Transport Working Group of
the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <040312152853.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3711

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3711.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <040312152853.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

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



From exim@www1.ietf.org  Sun Mar 14 14:59:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03527
	for <avt-archive@odin.ietf.org>; Sun, 14 Mar 2004 14:59:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2blf-0004V4-Ir
	for avt-archive@odin.ietf.org; Sun, 14 Mar 2004 14:59:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EJxRLp017292
	for avt-archive@odin.ietf.org; Sun, 14 Mar 2004 14:59:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2bl5-00049U-V2; Sun, 14 Mar 2004 14:58:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2ZEl-0004gZ-EE
	for avt@optimus.ietf.org; Sun, 14 Mar 2004 12:17:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27871
	for <avt@ietf.org>; Sun, 14 Mar 2004 12:17:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2ZEj-000087-00
	for avt@ietf.org; Sun, 14 Mar 2004 12:17:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2ZDh-0007n7-00
	for avt@ietf.org; Sun, 14 Mar 2004 12:16:14 -0500
Received: from bzq-179-16-107.cust.bezeqint.net ([212.179.16.107] helo=accord-mail.israel.polycom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2ZD5-0007aZ-00
	for avt@ietf.org; Sun, 14 Mar 2004 12:15:35 -0500
Received: by accord-mail.israel.polycom.com with Internet Mail Service (5.5.2653.19)
	id <1YRKZ0X5>; Sun, 14 Mar 2004 19:14:56 +0200
Message-ID: <E173F9D0511CA94581BC3FA62F06848DA946FC@accord-mail.israel.polycom.com>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>,
        "Even, Roni"
	 <roni.even@polycom.co.il>, avt@ietf.org
Date: Sun, 14 Mar 2004 19:14:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [AVT] RE: Comments on draft-ietf-avt-rfc2429bis-00.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Magnus,
Most of my comments are inline

As for comment 21 - I would like to take out the MaxBR since I do not think
it is needed. The bW can be specified using b= with AS and also using RFC
3556  and draft-ietf-mmusic-sdp-bwparam-05.txt 

Thanks
Roni

*************************************
Roni Even
VP Product Planning
Polycom Israel

Tel: +972-3-9251200
Cell: +972-55-481099
email:roni.even@polycom.co.il
*******************************************


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
Sent: Friday, January 30, 2004 4:55 PM
To: roni.even@polycom.co.il; avt@ietf.org
Subject: Comments on draft-ietf-avt-rfc2429bis-00.txt


Hi

Here is my comments on the update of RFC 2429. A lot of comments are 
similar to the ones for draft-ietf-avt-rfc2032-bis-00.txt.

1. Please try to submit documents with correct document dates, this says 
november.
RE: OK

2. In section 1, declare the intentions that this will update RFC 2429.
RE:OK

3. Conventions used in this document is missing. RFC 2119 pointer, and 
probably some other things should be here.
RE:OK

4. Section 2: fifth paragraph: Here I think one today should put in 
pointers at RTCP feedback.
RE: OK, I will add a reference for RTCP feedback as a method for back
channel.

5. Please work through and upgrade where appropriate to normative language.

6. Section 3: There should somewhere in the format specification be a 
note about that the usage of the timestamp make the RTCP jitter 
calculation to be less useful as it introduces jitter before transmission.

RE: I am not sure I understand, but is it special for H.263 or general RTP
issue.


7. Section 3. Payload type: Please update the text with reference to 
profiles and usage of dynamic payload types.

RE: OK


8. Section 5.1: Reserved bits: I think it is appropriate to add: "MUST 
be ignored by receivers."

RE: OK

9. Section 5.1: PLEN: "If PLEN>0, the extra picture header
   is attached immediately following the rest of the payload header."
I don't think it is clear enough what attached immediately following the 
rest of payload header. Is this before or after the other video 
redundancy coding header extension?

RE: I think it is clear from the first two paragraph of section 5

10. Section 6.1: What is the start code bit order?

RE: There is a general question if we need to have text that duplicate H.263

11. Section 8.1, This registration updates the previous registered 
version in RFC 3555. please spell this out.

RE:OK

12. Section 8: Again the space separated list needs to be replace with 
semicolon separated.

RE: So you want the parameters in the a=fmtp line to be comma separated
instead of space separated. I am not sure, I see the parameters as space
separated while values for the parameters are comma separated, example is :
CIF=4  QCIF=3 SQCIF=2 CUSTOM=360, 240, 2

13. Section 8.1: all parameters needs values, and default 
interpretations. Some parameters could be changed into values for a new 
aggregating parameter.

RE: I am not sure I understand. The parameters are optional so they may be
specified or not. Some parameters like CIF have values that are specified if
the parameter is specified, but there is no default value.

14. There is need for RFC editor consideration.

15. Section 8.1.1: In the Author/Change controller a stray ">"

RE: OK, Thanks

16. Section 8.1.1: PAR: It does not define how the values are separated, 
colon maybe.

RE: OK

17. Section 8.1.2: I don't know if you can make a parameter registration 
though reference.

RE: I assume you mean for the interlace parameter, I will get the text from
annex X but I thought that it is better to reference then to copy from the
other spec.

18. Section 8.2.1: Please change the title of  "... options with SIP" to 
Offer/Answer.
RE: OK


19. Section 8.2.1: The order of the pictures size is not defined within 
the MIME parameter space at all. I think it belongs there if it is needed.

RE: OK, I will move the  text on the order of the picture sizes.

20. Section 8.2.1: The example using picture sizes: The definition of 
custom does not declare that space is allowed in the comma separated list.

RE: OK, I will cancel the spaces.

21. Section 8.2.1: MaxBR and BPP: "MaxBitRate is video
   decoder property, hence it differs from SDP b : bandwidth-value
   attribute which refers more to application's total bandwidth (an
   application consists often of both audio and video)."

What the b= SDP parameter refers to depends on the modifier, CT, AS, RS, 
RR. So I think you need to be a bit more specific here.

See in the top.

22. Section 9. I thought that most video codecs contains some 
non-uniform processing depending on input. Is this not at least a small 
threat of DOS.

RE:The text is from the original RFC

23. Section 9: I am missing the following topics: Integrity, and 
Authentication. Congestion control on best effort networks is also a 
consideration as the codec can after all produce a rather high bandwidth.

RE: I will add a sentence about congestion. In general all these issues are
general to RTP and I will write the right reference

24. Section 11, belongs in the conventions section in the beginning.

RE: I will check why it is here

25. Should RFC 2190 be declared historic?

RE: Yes, I think tat was the agreement

26. What MIME type should be recommended to support in this new version.

RE: I would like to use the old MIME types H.263-1998 and H.263-2000 and
just add the optional parameters

27. What is the interoperability status on all parts of this specification?

RE: I will write about backward compatibility and how to use the new
parameters.

28. The new parameters and possibly some other changes needs 
interoperability statements.



29. Section 12: The numbering of the changes are strange.
RE: Saw it, I will check and fix

30. Please get the correct contact information for the previous authors. 
And contact them to in regards to there possible interaction with this 
specification in the future.
RE: OK


31. Please get correct page breaks.

Cheers

Magnus Westerlund 

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


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



From exim@www1.ietf.org  Mon Mar 15 04:24:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16640
	for <avt-archive@odin.ietf.org>; Mon, 15 Mar 2004 04:24:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2oKc-0000pM-TO
	for avt-archive@odin.ietf.org; Mon, 15 Mar 2004 04:24:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2F9OMMG003092
	for avt-archive@odin.ietf.org; Mon, 15 Mar 2004 04:24:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2oKM-0000kK-EM; Mon, 15 Mar 2004 04:24:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2nLz-0005q2-Kv
	for avt@optimus.ietf.org; Mon, 15 Mar 2004 03:21:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14180
	for <avt@ietf.org>; Mon, 15 Mar 2004 03:21:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2nLx-0005ZS-00
	for avt@ietf.org; Mon, 15 Mar 2004 03:21:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2nL0-0005Sf-00
	for avt@ietf.org; Mon, 15 Mar 2004 03:20:43 -0500
Received: from bzq-179-16-107.cust.bezeqint.net ([212.179.16.107] helo=accord-mail.israel.polycom.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2nKX-0005LR-00
	for avt@ietf.org; Mon, 15 Mar 2004 03:20:14 -0500
Received: by accord-mail.israel.polycom.com with Internet Mail Service (5.5.2653.19)
	id <1YRK5186>; Mon, 15 Mar 2004 10:19:40 +0200
Message-ID: <E173F9D0511CA94581BC3FA62F06848DA946FF@accord-mail.israel.polycom.com>
From: "Even, Roni" <roni.even@polycom.co.il>
To: avt@ietf.org
Date: Mon, 15 Mar 2004 10:19:34 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [AVT] Bandwidth for video codecs.
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Hi,
In draft-ietf-avt-rfc2429bis-00.txt, I have a MaxBR parameter. This
parameter specify the max bit rates in units of 100 bits/sec, it was added
from a previous draft from Petri. SDP RFC 2327 specifies the AS modifier to
be used for media level for the b= in units of kbit/sec. There are cases
were using the AS modifier is not good enough since you need to specify the
max bit rate in a more precise number then kbit/sec. 
draft-ietf-mmusic-sdp-bwparam-05.txt defines a new bandwidth (b=) modifier
TIAS which can used to specify the bw in unit of bit per second. I would
like to take out the MaxBR from the RFC2429 and recommend in the text to use
the TIAS modifier to specify the maximum video bit rate.

Roni



*************************************
Roni Even

Polycom Israel

Tel: +972-3-9251200
Cell: +972-55-481099
email:roni.even@polycom.co.il
*******************************************


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



From exim@www1.ietf.org  Wed Mar 17 23:34:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29971
	for <avt-archive@odin.ietf.org>; Wed, 17 Mar 2004 23:34:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3pEM-0003po-Rt
	for avt-archive@odin.ietf.org; Wed, 17 Mar 2004 23:34:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I4Y6Ja014731
	for avt-archive@odin.ietf.org; Wed, 17 Mar 2004 23:34:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3pEH-0003ok-E1; Wed, 17 Mar 2004 23:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3pDJ-0003oC-DR
	for avt@optimus.ietf.org; Wed, 17 Mar 2004 23:33:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29926
	for <avt@ietf.org>; Wed, 17 Mar 2004 23:32:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3pDH-0000ed-00
	for avt@ietf.org; Wed, 17 Mar 2004 23:32:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3pCI-0000YC-00
	for avt@ietf.org; Wed, 17 Mar 2004 23:31:59 -0500
Received: from relay2.eecs.berkeley.edu ([169.229.60.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3pBb-0000SE-00
	for avt@ietf.org; Wed, 17 Mar 2004 23:31:15 -0500
Received: from relay3.EECS.Berkeley.EDU (localhost [127.0.0.1])
	by relay2.EECS.Berkeley.EDU (8.12.10/8.9.3) with ESMTP id i2I4VFdv006780
	for <avt@ietf.org>; Wed, 17 Mar 2004 20:31:15 -0800 (PST)
Received: from gateway.EECS.Berkeley.EDU (nsmail@gateway.EECS.Berkeley.EDU [169.229.60.73])
	by relay3.EECS.Berkeley.EDU (8.12.10/8.9.3) with ESMTP id i2I4VEd3029212
	for <avt@ietf.org>; Wed, 17 Mar 2004 20:31:14 -0800 (PST)
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU
          [128.32.34.73]) by gateway.EECS.Berkeley.EDU (Netscape Messaging
          Server 4.15) with ESMTP id HUR8K000.84Y for <avt@ietf.org>; Wed,
          17 Mar 2004 20:31:12 -0800 
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <161747A3-7895-11D8-9D2E-00039372C384@eecs.berkeley.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: avt@ietf.org
From: "John Lazzaro" <lazzaro@eecs.berkeley.edu>
Date: Wed, 17 Mar 2004 20:31:12 -0800
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] RTP MIDI I-Ds updated ...
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi everyone,

	Just sent refreshed versions of the RTP MIDI I-Ds
off to internet-drafts, you can download them now from
the Berkeley mirror:

http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-rtp-midi.txt
http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-guide.txt

	The Change Logs are short so I'll post them at
the end of this message.  Of interest to IETF folks will
be the added paragraphs throughout Appendix C.5,
that provide Offer/Answer implementation advice for
each fmtp parameter.

	The current plan is to keep the window for
"pre-Last-Call comments" open through early April,
then do one last refresh (if necessary) and request
the Last Call.

---

M.  Change Log for <draft-ietf-avt-rtp-midi-format-02.txt>

[Note to RFC Editors: this Appendix, and its Table of Contents listing,
should be removed from the final version of the memo]

The changes below reflect comments on the candidate Last Call documents.

   o  Chapter E has been added to the channel journal (changes
      appear in Section 5 and Appendices A.7, C.1.3, and D).
      Chapter E supplements Chapter N, to code information to
      reduce transient artifacts for MIDI NoteOn/NoteOff commands
      in special situations. Chapter E targets applications that:
      (1) have several NoteOn commands happening at the same time
      for the same MIDI note number on the same MIDI channel, and (2)
      applications that use release velocity.  For applications
      do not use MIDI in this way, Chapter E is never required
      to appear in a channel journal.  Chapter E has been
      coded into the sfront NMP reference implementation.
      Note that the chapter ordering in the channel journal
      Table of Contents has been reordered so that Chapter E
      appears in an optimal position (Figure 9).

   o  In Chapter A (Appendix A.8), the N bit was renamed the
      X bit, and the polarity of the bit was inverted.  These
      changes improve uniformity with other chapters.

   o  Added comments to Appendices C.1 and C.4 to show how
      the chapter inclusion parameters may be used to statically
      partition a MIDI source between two streams.

   o  Added Offer/Answer interoperability notes to the
      definitions of all fmtp parameters in Appendix C.  These
      notes appear inline for each parameter type, and appear
      in Appendices C.1 (final paragraph of preamble), C.1.1
      (paragraphs that follow the session description example),
      C.1.2 (final two paragraphs), C.1.3 (paragraphs 5 and 6),
      C.2 (final paragraph of preamble), C.3.1 (5th paragraph),
      C.3.2 (paragraph 5), C.4 (second to last paragraph of the
      preamble), C.5 (preamble).

   o  Acknowledgements expanded.

----

G.  Change Log for <draft-ietf-avt-rtp-midi-guidelines-02.txt>

[Note to RFC Editors: this Appendix, and its Table of Contents listing,
should be removed from the final version of the memo]

The document has changed to reflect the addition of Chapter E to the
recovery channel journal.  In Section 2, "E" has been added to
ch_unused.  In the preambles of Sections 5 and 7, we explain the
assumptions that permit excluding Chapter E from the example.

In Section 7.2 (description of note recovery algorithms) we address
Chapter E issues in more detail, and fix incorrect statements about the
applicability of the presented algorithm to note patterns other than
NoteOn->NoteOff->NoteOn->NoteOff.

---
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
lazzaro [at] cs [dot] berkeley [dot] edu
---


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



From exim@www1.ietf.org  Thu Mar 18 09:49:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14834
	for <avt-archive@odin.ietf.org>; Thu, 18 Mar 2004 09:49:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ypb-0004H6-LG
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 09:49:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IEnBiQ016427
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 09:49:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ypS-0004Fs-JD; Thu, 18 Mar 2004 09:49:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yp4-00044i-Dw
	for avt@optimus.ietf.org; Thu, 18 Mar 2004 09:48:38 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14640;
	Thu, 18 Mar 2004 09:48:34 -0500 (EST)
Message-Id: <200403181448.JAA14640@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, 18 Mar 2004 09:48:34 -0500
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-midi-format-02.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

--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 for MIDI
	Author(s)	: J. Lazzaro
	Filename	: draft-ietf-avt-rtp-midi-format-02.txt
	Pages		: 124
	Date		: 2004-3-17
	
This memo describes an RTP payload format for the MIDI command
language.  The format encodes all commands that may legally appear
on a MIDI 1.0 DIN cable.  The format is suitable for interactive
applications (such as the remote operation of musical instruments)
and content-delivery applications (such as file streaming).  The
format may be used over unicast and multicast UDP as well as TCP,
and defines tools for graceful recovery from packet loss.  Stream
behavior, including the MIDI rendering method, may be customized
during session setup.  The format also serves as a mode for the
mpeg4-generic format, to support the MPEG 4 Audio Object Types for
General MIDI, Downloadable Sounds Level 2, and Structured Audio.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-format-02.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-midi-format-02.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-midi-format-02.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:	<2004-3-18101202.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-midi-format-02.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Thu Mar 18 10:37:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14836
	for <avt-archive@odin.ietf.org>; Thu, 18 Mar 2004 09:49:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ypb-0004H7-Lf
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 09:49:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IEnBgd016425
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 09:49:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ypR-0004Fj-Sm; Thu, 18 Mar 2004 09:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yoz-00044V-2H
	for avt@optimus.ietf.org; Thu, 18 Mar 2004 09:48:33 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14624;
	Thu, 18 Mar 2004 09:48:29 -0500 (EST)
Message-Id: <200403181448.JAA14624@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, 18 Mar 2004 09:48:29 -0500
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-midi-guidelines-02.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

--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 Implementation Guide for RTP MIDI
	Author(s)	: J. Lazzaro
	Filename	: draft-ietf-avt-rtp-midi-guidelines-02.txt
	Pages		: 37
	Date		: 2004-3-17
	
This memo offers non-normative implementation guidance for the RTP
     MIDI payload format.  The memo presents its advice in the context
     of a network musical performance application.  In this application
     two musicians, located in different physical locations, interact
     over a network to perform as they would if located in the same
     room.  Underlying the performances are RTP MIDI sessions over
     unicast UDP.  Algorithms for sending and receiving recovery
     journals (the resiliency structure for the payload format) are
     described in detail.  Although the memo focuses on network musical
     performance, the presented implementation advice is relevant to
     other RTP MIDI applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-guidelines-02.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-midi-guidelines-02.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-midi-guidelines-02.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:	<2004-3-18101154.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-midi-guidelines-02.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Thu Mar 18 14:06:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01191
	for <avt-archive@odin.ietf.org>; Thu, 18 Mar 2004 14:06:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42qG-0002gt-Ra
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 14:06:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IJ68xb010292
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 14:06:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42q9-0002eQ-6j; Thu, 18 Mar 2004 14:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42pj-0002cp-Ui
	for avt@optimus.ietf.org; Thu, 18 Mar 2004 14:05:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01176
	for <avt@ietf.org>; Thu, 18 Mar 2004 14:05:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42ph-0003hM-00
	for avt@ietf.org; Thu, 18 Mar 2004 14:05:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B42op-0003fS-00
	for avt@ietf.org; Thu, 18 Mar 2004 14:04:40 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42ob-0003cv-00
	for avt@ietf.org; Thu, 18 Mar 2004 14:04:26 -0500
Received: from rkumar-w2k01.cisco.com ([128.107.170.183])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i2IJ3nRP012774;
	Thu, 18 Mar 2004 11:03:50 -0800 (PST)
Message-Id: <4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
X-Sender: rkumar@vtg-um-e2k1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Mar 2004 11:03:49 -0800
To: Colin Perkins <csp@csperkins.org>, ruediger.kreuter@siemens.com
From: Rajesh Kumar <rkumar@cisco.com>
Cc: avt@ietf.org, magnus.westerlund@ericsson.com, dea@cisco.com,
        hisham@cisco.com, rbiskner@cisco.com, miriyala@cisco.com
In-Reply-To: <484975AB-D49D-11D7-88B7-000A957FC5F2@csperkins.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [AVT] Clearmode definition.
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Are there plans to address N x 64 clear mode (N > 1) in 
draft-ietf-avt-rtp-clearmode-04.txt ?

One method might be to have N as a MIME parameter.

I recommend that we do.

Thanks,

Rajesh


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



From exim@www1.ietf.org  Thu Mar 18 15:21:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06303
	for <avt-archive@odin.ietf.org>; Thu, 18 Mar 2004 15:21:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B440r-00011n-TN
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 15:21:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IKL9qn003893
	for avt-archive@odin.ietf.org; Thu, 18 Mar 2004 15:21:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B440j-0000r1-01; Thu, 18 Mar 2004 15:21:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B440K-0000fX-LB
	for avt@optimus.ietf.org; Thu, 18 Mar 2004 15:20:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06178
	for <avt@ietf.org>; Thu, 18 Mar 2004 15:20:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B440J-0000iO-00
	for avt@ietf.org; Thu, 18 Mar 2004 15:20:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B43zR-0000eN-00
	for avt@ietf.org; Thu, 18 Mar 2004 15:19:41 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43yY-0000ZT-00
	for avt@ietf.org; Thu, 18 Mar 2004 15:18:47 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 18 Mar 2004 12:23:20 +0000
Received: from rkumar-w2k01.cisco.com ([128.107.170.183])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i2IKICaE017797;
	Thu, 18 Mar 2004 12:18:12 -0800 (PST)
Message-Id: <4.3.2.7.2.20040318121718.025fc8a0@vtg-um-e2k1.cisco.com>
X-Sender: rkumar@vtg-um-e2k1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Mar 2004 12:18:11 -0800
To: Colin Perkins <csp@csperkins.org>
From: Rajesh Kumar <rkumar@cisco.com>
Cc: ruediger.kreuter@siemens.com, avt@ietf.org, magnus.westerlund@ericsson.com,
        dea@cisco.com, hisham@cisco.com, rbiskner@cisco.com,
        miriyala@cisco.com
In-Reply-To: <20040318201239.195bbd59.csp@csperkins.org>
References: <4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
 <484975AB-D49D-11D7-88B7-000A957FC5F2@csperkins.org>
 <4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [AVT] Re: Clearmode definition.
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

At 08:12 PM 3/18/2004 +0000, Colin Perkins wrote:
>--> Rajesh Kumar <rkumar@cisco.com> writes:
> > Are there plans to address N x 64 clear mode (N > 1) in
> > draft-ietf-avt-rtp-clearmode-04.txt ?
> >
> > One method might be to have N as a MIME parameter.
> >
> > I recommend that we do.
>
>No. This is explicitly out of scope of AVT, and will be addressed in the
>PWE3 working group.

I do not understand why 64 kbps clearmode is any different from 384 kbps. 
Both can be negotiated codecs for a session type. N x 64 should be 
negotiable session by session and not just relegated to the provisioned 
tunnel category. I recommend a MIME definition for it if you do not want to 
fold it into the MIME for 64 kbps clear mode, although I would prefer the 
latter.



>--
>Colin Perkins
>http://csperkins.org/


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



From exim@www1.ietf.org  Fri Mar 19 00:35:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01984
	for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 00:35:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Cez-0002FZ-IU
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 00:35:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J5Z90M008625
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 00:35:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Cet-0002EQ-AC; Fri, 19 Mar 2004 00:35:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Cem-0002Dn-2J
	for avt@optimus.ietf.org; Fri, 19 Mar 2004 00:34:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01976
	for <avt@ietf.org>; Fri, 19 Mar 2004 00:34:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Cej-0001uc-00
	for avt@ietf.org; Fri, 19 Mar 2004 00:34:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4Cdr-0001rP-00
	for avt@ietf.org; Fri, 19 Mar 2004 00:34:00 -0500
Received: from smtp104.mail.sc5.yahoo.com ([66.163.169.223])
	by ietf-mx with smtp (Exim 4.12)
	id 1B4CdH-0001nn-00
	for avt@ietf.org; Fri, 19 Mar 2004 00:33:23 -0500
Received: from unknown (HELO mp-liyf) (ipmutimedia@220.248.128.41 with login)
  by smtp104.mail.sc5.yahoo.com with SMTP; 19 Mar 2004 05:33:22 -0000
From: "liyunfeng" <ipmutimedia@yahoo.com.cn>
To: "avt@ietf.org" <avt@ietf.org>
X-mailer: Foxmail 4.2 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Mar 2004 13:34:18 +0800
Message-Id: <E1B4CdH-0001nn-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] (no subject)
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

hi:

I have got a draft =A1=B0draft-davies-fw-nat-traversal-00.txt=A1=B1=A3=ACbut=
 I do not know the state of this draft.

=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1liyunfeng
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1ipmutimedia@yahoo.com.cn
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-03-19



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



From exim@www1.ietf.org  Fri Mar 19 03:16:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21751
	for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 03:16:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4FAt-0005HB-NV
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 03:16:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J8GFGW020275
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 03:16:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4FAg-0005GC-5l; Fri, 19 Mar 2004 03:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4FAZ-0005Fk-7h
	for avt@optimus.ietf.org; Fri, 19 Mar 2004 03:15:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21727
	for <avt@ietf.org>; Fri, 19 Mar 2004 03:15:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4FAX-0005DX-00
	for avt@ietf.org; Fri, 19 Mar 2004 03:15:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4F9Y-00058m-00
	for avt@ietf.org; Fri, 19 Mar 2004 03:14:53 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4F8Z-00050s-00
	for avt@ietf.org; Fri, 19 Mar 2004 03:13:51 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2J8DmAh017840
	for <avt@ietf.org>; Fri, 19 Mar 2004 09:13:52 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 19 Mar 2004 09:13:48 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id G4A54D2A; Fri, 19 Mar 2004 09:15:29 +0100
Message-ID: <405AAAEE.2010402@ericsson.com>
Date: Fri, 19 Mar 2004 09:10:22 +0100
X-Sybari-Trust: 9c6890a1 272a6e05 94024609 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: liyunfeng <ipmutimedia@yahoo.com.cn>
CC: avt@ietf.org
Subject: Re: [AVT] Finding drafts and their status
References: <E1B4CdH-0001nn-00@ietf-mx>
In-Reply-To: <E1B4CdH-0001nn-00@ietf-mx>
Content-Type: text/plain; charset=GB2312
X-OriginalArrivalTime: 19 Mar 2004 08:13:48.0463 (UTC) FILETIME=[1B1B2BF0:01C40D8A]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id i2J8DmAh017840
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

For these type of questions I recommend that people to use the datatracke=
r.
https://datatracker.ietf.org/public/pidtracker.cgi

Enter the filename without the version number or .txt, i.e. remove in
this case  "-00.txt", in the filename field.

The draft tracker will tell the status of the draft and what the current
 version is. If it is not found it has either never been submitted or
simply expired. One caution is in cases where individual submission
becomes working group document, then the individual expires and WG
document has a new filename. In this case it may work to search on the
last part of the filename, i.e. "fw-nat-traversal". The advantage of
using the status tracker rather than the draft search engine is that it
has the draft names of all RFCs published since they started using it.
It will also explain why drafts that appear to have expired, are simply
in the process of being published and thus do not expire.

In this particular case there is no hit, therefore I interpret it as
being expired. You that have this draft, please check publication and
expire dates within the draft.

The datatracker is also a good tool for keeping track of the progress
since a draft has been requested to be published.

Cheers

Magnus

liyunfeng wrote:

> hi:
>=20
> I have got a draft =A1=B0draft-davies-fw-nat-traversal-00.txt=A1=B1=A3=AC=
but I do
> not know the state of this draft.
>=20
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1liyunfeng
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1ipmutimedia@yahoo.com.c=
n
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-03-19
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20

--=20

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Fri Mar 19 04:01:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23131
	for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 04:01:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4FsL-0008GW-LX
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 04:01:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J919wL031741
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 04:01:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4FsG-0008Dv-4x; Fri, 19 Mar 2004 04:01:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B43tc-0006HI-R1
	for avt@optimus.ietf.org; Thu, 18 Mar 2004 15:13:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05409
	for <avt@ietf.org>; Thu, 18 Mar 2004 15:13:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43tb-0000Kx-00
	for avt@ietf.org; Thu, 18 Mar 2004 15:13:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B43sg-0000Ij-00
	for avt@ietf.org; Thu, 18 Mar 2004 15:12:43 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43sK-0000GL-00
	for avt@ietf.org; Thu, 18 Mar 2004 15:12:20 -0500
Received: from spaatz ([130.209.242.185]:1581 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B43rd-00060Y-00; Thu, 18 Mar 2004 20:11:37 +0000
Date: Thu, 18 Mar 2004 20:12:39 +0000
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar@cisco.com>
Cc: ruediger.kreuter@siemens.com, avt@ietf.org, magnus.westerlund@ericsson.com,
        dea@cisco.com, hisham@cisco.com, rbiskner@cisco.com,
        miriyala@cisco.com
Message-Id: <20040318201239.195bbd59.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
References: <484975AB-D49D-11D7-88B7-000A957FC5F2@csperkins.org>
	<4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Re: Clearmode definition.
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar@cisco.com> writes:
> Are there plans to address N x 64 clear mode (N > 1) in 
> draft-ietf-avt-rtp-clearmode-04.txt ?
> 
> One method might be to have N as a MIME parameter.
> 
> I recommend that we do.

No. This is explicitly out of scope of AVT, and will be addressed in the
PWE3 working group.

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Fri Mar 19 04:35:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24366
	for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 04:35:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4GPF-0002ay-03
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 04:35:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J9Z84Y009925
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 04:35:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4GP8-0002Za-Sa; Fri, 19 Mar 2004 04:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4GNS-0002UU-Cg
	for avt@optimus.ietf.org; Fri, 19 Mar 2004 04:33:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24244
	for <avt@ietf.org>; Fri, 19 Mar 2004 04:33:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4GNP-0003FE-00
	for avt@ietf.org; Fri, 19 Mar 2004 04:33:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4GMZ-0003A0-00
	for avt@ietf.org; Fri, 19 Mar 2004 04:32:23 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4GLt-00032S-00
	for avt@ietf.org; Fri, 19 Mar 2004 04:31:41 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63248 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B4GLG-0000FY-00; Fri, 19 Mar 2004 09:31:02 +0000
Date: Fri, 19 Mar 2004 09:31:55 +0000
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar@cisco.com>
Cc: ruediger.kreuter@siemens.com, avt@ietf.org, magnus.westerlund@ericsson.com,
        dea@cisco.com, hisham@cisco.com, rbiskner@cisco.com,
        miriyala@cisco.com
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040319093155.26e5a778.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040318121718.025fc8a0@vtg-um-e2k1.cisco.com>
References: <4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
	<484975AB-D49D-11D7-88B7-000A957FC5F2@csperkins.org>
	<4.3.2.7.2.20040318110015.01d99c58@vtg-um-e2k1.cisco.com>
	<4.3.2.7.2.20040318121718.025fc8a0@vtg-um-e2k1.cisco.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar@cisco.com> writes:
> At 08:12 PM 3/18/2004 +0000, Colin Perkins wrote:
> >--> Rajesh Kumar <rkumar@cisco.com> writes:
> > > Are there plans to address N x 64 clear mode (N > 1) in
> > > draft-ietf-avt-rtp-clearmode-04.txt ?
> > >
> > > One method might be to have N as a MIME parameter.
> > >
> > > I recommend that we do.
> >
> >No. This is explicitly out of scope of AVT, and will be addressed in the
> >PWE3 working group.
> 
> I do not understand why 64 kbps clearmode is any different from 384 kbps.
> 
> Both can be negotiated codecs for a session type. N x 64 should be 
> negotiable session by session and not just relegated to the provisioned 
> tunnel category. I recommend a MIME definition for it if you do not want
> to fold it into the MIME for 64 kbps clear mode, although I would prefer
> the latter.

As I mentioned before, the PWE3 working group is the appropriate place to
discuss this question. 

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Fri Mar 19 06:26:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26636
	for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 06:26:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4I8k-0000Ov-Gn
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 06:26:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JBQEDX001524
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 06:26:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4I8d-0000L8-SS; Fri, 19 Mar 2004 06:26:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4I7n-0008T1-PN
	for avt@optimus.ietf.org; Fri, 19 Mar 2004 06:25:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26476
	for <avt@ietf.org>; Fri, 19 Mar 2004 06:25:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4H4f-0006KF-00
	for avt@ietf.org; Fri, 19 Mar 2004 05:17:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4H3k-0006HZ-00
	for avt@ietf.org; Fri, 19 Mar 2004 05:17:01 -0500
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4H2v-0006E7-00
	for avt@ietf.org; Fri, 19 Mar 2004 05:16:09 -0500
Received: from argos.ee.surrey.ac.uk ([131.227.89.15] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 1B4H2i-0003zL-00; Fri, 19 Mar 2004 10:15:56 +0000
Date: Fri, 19 Mar 2004 10:15:54 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@argos.ee.surrey.ac.uk
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
cc: liyunfeng <ipmutimedia@yahoo.com.cn>, "" <avt@ietf.org>
Subject: Re: [AVT] Finding drafts and their status
In-Reply-To: <405AAAEE.2010402@ericsson.com>
Message-ID: <Pine.GSO.4.50.0403191008190.8701-100000@argos.ee.surrey.ac.uk>
References: <E1B4CdH-0001nn-00@ietf-mx> <405AAAEE.2010402@ericsson.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=GB2312
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Scanner: exiscan *1B4H2i-0003zL-00*WLU5HDgHTHw* (SECM, UniS)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: QUOTED-PRINTABLE

Additionally, http://www.watersprings.org/ provides a searchable index
of published internet-drafts - all versions. Very useful for version
comparison, even at publication stage when e.g. figuring out missing
references.

L.

On Fri, 19 Mar 2004, Magnus Westerlund wrote:

> Date: Fri, 19 Mar 2004 09:10:22 +0100
> From: Magnus Westerlund <magnus.westerlund@ericsson.com>
> To: liyunfeng <ipmutimedia@yahoo.com.cn>
> Cc: avt@ietf.org
> Subject: Re: [AVT] Finding drafts and their status
>
> Hi,
>
> For these type of questions I recommend that people to use the datatracke=
r.
> https://datatracker.ietf.org/public/pidtracker.cgi
>
> Enter the filename without the version number or .txt, i.e. remove in
> this case  "-00.txt", in the filename field.
>
> The draft tracker will tell the status of the draft and what the current
>  version is. If it is not found it has either never been submitted or
> simply expired. One caution is in cases where individual submission
> becomes working group document, then the individual expires and WG
> document has a new filename. In this case it may work to search on the
> last part of the filename, i.e. "fw-nat-traversal". The advantage of
> using the status tracker rather than the draft search engine is that it
> has the draft names of all RFCs published since they started using it.
> It will also explain why drafts that appear to have expired, are simply
> in the process of being published and thus do not expire.
>
> In this particular case there is no hit, therefore I interpret it as
> being expired. You that have this draft, please check publication and
> expire dates within the draft.
>
> The datatracker is also a good tool for keeping track of the progress
> since a draft has been requested to be published.
>
> Cheers
>
> Magnus
>
> liyunfeng wrote:
>
> > hi:
> >
> > I have got a draft =A1=B0draft-davies-fw-nat-traversal-00.txt=A1=B1=A3=
=ACbut I do
> > not know the state of this draft.
> >
> > =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1liyunfeng
> > =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1ipmutimedia@yahoo.com.c=
n
> > =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-03-19
> >
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
> >
>
> --
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>
> This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibited.=
 If you believe this message has been sent to you in error, please notify t=
he sender by replying to this transmission and delete the message without d=
isclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and re=
ceive e-mails on the basis that we are not liable for any such corruption, =
interception, amendment, tampering or viruses or any consequences thereof.
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@eim.surrey.ac.uk>

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



From exim@www1.ietf.org  Fri Mar 19 06:53:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28073
	for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 06:53:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4IYi-0002bv-1X
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 06:53:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JBr4RF010034
	for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 06:53:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4IYf-0002bI-S2; Fri, 19 Mar 2004 06:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4IYI-0002aj-RX
	for avt@optimus.ietf.org; Fri, 19 Mar 2004 06:52:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28049
	for <avt@ietf.org>; Fri, 19 Mar 2004 06:52:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4IYD-0000Mw-00
	for avt@ietf.org; Fri, 19 Mar 2004 06:52:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4IX0-0000GK-00
	for avt@ietf.org; Fri, 19 Mar 2004 06:51:21 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4IVx-0000Ae-00
	for avt@ietf.org; Fri, 19 Mar 2004 06:50:13 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id i2JBo4E27473;
	Fri, 19 Mar 2004 12:50:04 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i2JBo3V22577;
	Fri, 19 Mar 2004 12:50:03 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <FF52RAT5>; Fri, 19 Mar 2004 12:49:18 +0100
Message-ID: <BB70B8DDF080D511AFB50003474B8D390168ED7F@MCHP9GRAS>
From: Kreuter Ruediger <ruediger.kreuter@siemens.com>
To: "'Rajesh Kumar'" <rkumar@cisco.com>
Cc: avt@ietf.org, Colin Perkins <csp@csperkins.org>,
        magnus.westerlund@ericsson.com, dea@cisco.com, hisham@cisco.com,
        rbiskner@cisco.com, miriyala@cisco.com
Date: Fri, 19 Mar 2004 12:48:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
Subject: [AVT] RE: Clearmode definition.
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

I introduced Nx64kbit/s into one of the early
versions of the Clearmode draft, to open a 
discussion about this issue (after an according
request in the AVT mailing list).
In response we had a discussion about this issue
in AVT and PWE3 and finaly decided to reduce
the Clearmode draft to 1X64kbit/s - for several
reasons.

1)
There were several drafts to this time 
dealing with Nx64kbit/s and PWE3 was in the 
process to harmonize them into one. We didn't 
want to come up with an additional approach.

2)
Just introducing a parameter N for Nx64kbit/s
is not enough. For N>1 you must describe how
the channels are packed in the RTP packet.
And there are several alternatives.
Additionally other information is needed.

There was a controverse discussion in PWE3
which leaded to reason
3)
When we discussed this issue with PWE3, it
became clear that the Nx64kbit/s would need
much more time to finish then a pure
Clearmode draft and we wanted to speed up
the MIME type registration for Clearmode.


So I agree with Colin, that we leave Nx64kbit
the the PWE3 group.

Regards, Ruediger





> -----Original Message-----
> From: Rajesh Kumar [mailto:rkumar@cisco.com] 
> Sent: Thursday, March 18, 2004 9:18 PM
> To: Colin Perkins
> Cc: Kreuter Ruediger; avt@ietf.org; 
> magnus.westerlund@ericsson.com; dea@cisco.com; 
> hisham@cisco.com; rbiskner@cisco.com; miriyala@cisco.com
> Subject: Re: Clearmode definition.
> 
> 
> At 08:12 PM 3/18/2004 +0000, Colin Perkins wrote:
> >--> Rajesh Kumar <rkumar@cisco.com> writes:
> > > Are there plans to address N x 64 clear mode (N > 1) in 
> > > draft-ietf-avt-rtp-clearmode-04.txt ?
> > >
> > > One method might be to have N as a MIME parameter.
> > >
> > > I recommend that we do.
> >
> >No. This is explicitly out of scope of AVT, and will be addressed in 
> >the PWE3 working group.
> 
> I do not understand why 64 kbps clearmode is any different 
> from 384 kbps. 
> Both can be negotiated codecs for a session type. N x 64 should be 
> negotiable session by session and not just relegated to the 
> provisioned 
> tunnel category. I recommend a MIME definition for it if you 
> do not want to 
> fold it into the MIME for 64 kbps clear mode, although I 
> would prefer the 
> latter.
> 
> 
> 
> >--
> >Colin Perkins
> >http://csperkins.org/
> 

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



From exim@www1.ietf.org  Sun Mar 21 10:16:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15260
	for <avt-archive@odin.ietf.org>; Sun, 21 Mar 2004 10:16:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54gL-0005uu-W2
	for avt-archive@odin.ietf.org; Sun, 21 Mar 2004 10:16:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LFG9aa022692
	for avt-archive@odin.ietf.org; Sun, 21 Mar 2004 10:16:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54gD-0005rE-O1; Sun, 21 Mar 2004 10:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54fy-0005nK-Hd
	for avt@optimus.ietf.org; Sun, 21 Mar 2004 10:15:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15182
	for <avt@ietf.org>; Sun, 21 Mar 2004 10:15:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B54fw-0001pO-00
	for avt@ietf.org; Sun, 21 Mar 2004 10:15:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B54f8-0001jd-00
	for avt@ietf.org; Sun, 21 Mar 2004 10:14:54 -0500
Received: from radmail1.rad.co.il ([62.0.23.193] helo=antivir1.rad.co.il)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B54eJ-0001VK-00
	for avt@ietf.org; Sun, 21 Mar 2004 10:14:03 -0500
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i2LFDBxF016412
	for <avt@ietf.org>; Sun, 21 Mar 2004 17:13:11 +0200 (IST)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i2LFDAte016404
	for <avt@ietf.org>; Sun, 21 Mar 2004 17:13:11 +0200 (IST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Re: Clearmode definition.
Date: Sun, 21 Mar 2004 17:13:31 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A52024E9B9A@exrad2.ad.rad.co.il>
Thread-Topic: [AVT] Re: Clearmode definition.
Thread-Index: AcQNkMHFRyTPM2khTimRUv6aWeJJ/wBxBziQ
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Rajesh Kumar" <rkumar@cisco.com>, "Colin Perkins" <csp@csperkins.org>
Cc: <avt@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

=20
> --> Rajesh Kumar <rkumar@cisco.com> writes:
> > Are there plans to address N x 64 clear mode (N > 1) in=20
> > draft-ietf-avt-rtp-clearmode-04.txt ?
> >=20
> > One method might be to have N as a MIME parameter.
> >=20
> > I recommend that we do.
>=20
> No. This is explicitly out of scope of AVT, and will be=20
> addressed in the PWE3 working group.

N*DS0 (i.e. N 64Kbps timeslots) with or without CAS
is defined in the PWE3 TDM requirements draft as a structured TDM
service.

Right now in PWE we have three TDM drafts:

1) The standards track one is SAToP (Structure Agnostic TDM over
Packet),
but this only handles full T1, E1, E3 or T3 trunks
(whether structured or not). Thus this doesn't address N*64.

2) CESoPSN - candidiate informational RFC
This draft can handle N*DS0 by encapsulating one or more frames or N
timeslots
per packet, with or without RTP.

3) TDMoIP - candidate informational RFC
This draft can handle N*DS0 by using AAL1 which appends
pointers to identify the first timeslot.=20
If the 64K channels are carrying HDLC data, there is a mode
which suppresses idle flags.

As you can see, the treatment of N*DS0 is only in the informational
drafts,
not in the standards track one.

The current suggestion for communicating N is via the PWE control
protocol,
where there is a parameter called CEP/TDM bit rate.

Y(J)S

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



From exim@www1.ietf.org  Mon Mar 22 10:43:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01998
	for <avt-archive@odin.ietf.org>; Mon, 22 Mar 2004 10:43:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RaE-0003RJ-5z
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 10:43:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MFhLw0013168
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 10:43:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RZu-0003PJ-Jw; Mon, 22 Mar 2004 10:43:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RYb-0003KP-OA
	for avt@optimus.ietf.org; Mon, 22 Mar 2004 10:41:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01759
	for <avt@ietf.org>; Mon, 22 Mar 2004 10:41:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5RYY-0002EY-00
	for avt@ietf.org; Mon, 22 Mar 2004 10:41:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5RXi-00027W-00
	for avt@ietf.org; Mon, 22 Mar 2004 10:40:46 -0500
Received: from endeavor.poss.com ([198.70.184.137] helo=smtp.poss.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5RWy-0001pk-00
	for avt@ietf.org; Mon, 22 Mar 2004 10:40:00 -0500
Received: from conversion-daemon.endeavor.poss.com by endeavor.poss.com
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 id <0HUZ00201HUV1Y@endeavor.poss.com> for avt@ietf.org; Mon,
 22 Mar 2004 10:39:24 -0500 (EST)
Received: from kan1 (ws-194144.va.rr.com [24.28.194.144])
 by endeavor.poss.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14
 2003)) with ESMTPA id <0HUZ00E8CI5NYV@endeavor.poss.com>; Mon,
 22 Mar 2004 10:39:24 -0500 (EST)
Date: Mon, 22 Mar 2004 10:40:29 -0500
From: "Kevin A. Noll" <kevin.noll@perfectorder.com>
To: avt@ietf.org
Cc: schulzrinne@cs.columbia.edu, scott.petrack@edial.com
Message-id: <PPEKLDPHBHOIHMHKFGLLKEGCCPAA.kevin.noll@perfectorder.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [AVT] RFC2833 and 2833bis
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT


Please forgive me if this has been a topic of discussion already,
but I have not been able to find any references to it...

I am interested in understanding the correct handling of lost
packets in the context of RFC 2833 and draft-ietf-avt-rfc2833bis-04. 

I have not found any clear explanation for what a receiver should
do in the event that:

1. The "marker" at the beginning of an event is lost? 

Should the receiver:
	a. ignore the entire event
	b. assume that the marker was lost and playout the event per 
	the event messages that are received (i.e. non-marker and the 
	"end").

I would think that (b) would be the better choice.

2. Only the "end" flag is received? (This is only a variation on
item (1) above.


--kan--
--
Kevin A. Noll, KD4WOZ
CCIE 10948, CCDP
Perfect Order, Inc.		
Kevin.Noll@perfectorder.com
717-796-1936


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



From exim@www1.ietf.org  Mon Mar 22 15:43:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19556
	for <avt-archive@odin.ietf.org>; Mon, 22 Mar 2004 15:43:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5WGR-00071I-0w
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 15:43:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MKhE9C026931
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 15:43:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5WGD-0006vN-A3; Mon, 22 Mar 2004 15:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5WFu-0006qT-DR
	for avt@optimus.ietf.org; Mon, 22 Mar 2004 15:42:42 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19278;
	Mon, 22 Mar 2004 15:42:39 -0500 (EST)
Message-Id: <200403222042.PAA19278@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, 22 Mar 2004 15:42:39 -0500
Subject: [AVT] I-D ACTION:draft-ietf-avt-text-red-02.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

--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		: Registration of the text/red MIME Sub-Type
	Author(s)	: P. Jones
	Filename	: draft-ietf-avt-text-red-02.txt
	Pages		: 6
	Date		: 2004-3-22
	
This document defines the text/red MIME sub-type.  The actual RTP
   packetization for this MIME type is specified in RFC 2198.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-text-red-02.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-text-red-02.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-text-red-02.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:	<2004-3-22151155.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-text-red-02.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Mon Mar 22 17:17:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28443
	for <avt-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:17:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XjQ-0006mn-KN
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 17:17:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMHGrq026079
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 17:17:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XjB-0006lM-Nk; Mon, 22 Mar 2004 17:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Nn7-0002UR-6w
	for avt@optimus.ietf.org; Mon, 22 Mar 2004 06:40:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17531
	for <avt@ietf.org>; Mon, 22 Mar 2004 06:40:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Nn3-0003O4-00
	for avt@ietf.org; Mon, 22 Mar 2004 06:40:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5NmA-0003Jr-00
	for avt@ietf.org; Mon, 22 Mar 2004 06:39:28 -0500
Received: from bzq-179-22-133.cust.bezeqint.net ([212.179.22.133] helo=lodmsg01.corp.audiocodes.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5NlY-0003Du-00
	for avt@ietf.org; Mon, 22 Mar 2004 06:38:49 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C41001.B6C2C148"
Date: Mon, 22 Mar 2004 13:35:02 +0200
Message-ID: <3F7A8186EE94CE4BB13996B62E7370F07E05E9@lodmsg01.corp.audiocodes.com>
Thread-Topic: RFC2833 bis_4
Thread-Index: AcQP8u87l5taC4zwSiqzA8dj+ksPyQABMWewAADsW9AAADZocAABQiZw
From: "Moshe Samoha" <MosheS@audiocodes.com>
To: "schulzrinne@cs.columbia.edu" <'schulzrinne@cs.columbia.edu'.cnri.reston.va.us>,
        "scott.petrack@edial.com" <'scott.petrack@edial.com'.cnri.reston.va.us>,
        <avt@ietf.org>
Cc: "Oren Peleg" <OrenP@audiocodes.com>,
        "Yuval Nissan" <YuvalN@audiocodes.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=HTML_FONTCOLOR_UNKNOWN,
	HTML_MESSAGE autolearn=no version=2.60
Subject: [AVT] RE: RFC2833 bis_4
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C41001.B6C2C148
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The mistake is at Table 14 - R2 Backward Register Signals from
"draft-ietf-avt-rfc2833bis-04"

=20

=20

=20

Moshe.

-----Original Message-----
From: Oren Peleg=20
Sent: Monday, March 22, 2004 12:56 PM
To: Yuval Nissan; Moshe Samoha
Subject: FW: RFC2833 bis_4
Importance: High

=20

FYI

=20

-----Original Message-----
From: Oren Peleg=20
Sent: Monday, March 22, 2004 12:56 PM
To: 'schulzrinne@cs.columbia.edu'; 'scott.petrack@edial.com'
Cc: avt@ietf.org
Subject: FW: RFC2833 bis_4
Importance: High

=20

Please look below - it seems that some kind of technical mistake was
done in the latest draft in regarding to the MF frequency tables.

=20

Regards,

=20

Oren P.

=20

-----Original Message-----
From: Moshe Samoha=20
Sent: Monday, March 22, 2004 12:27 PM
To: Oren Peleg; Yuval Nissan
Subject: RE: RFC2833 bis_4
Importance: High

=20

I rechecked the issue.

It seems that X-axis and the Y-axis have been replaced at table number
13.

If we replaced them, it is compatible to our old implementation.

=20

=20

=20

=20

=20

=20

Moshe.

-----Original Message-----
From: Moshe Samoha=20
Sent: Monday, March 22, 2004 11:49 AM
To: Oren Peleg; Yuval Nissan
Subject: RFC2833 bis_4
Importance: High

=20

We found out that we are not compatible with the last RFC2833 draft
"draft-ietf-avt-rfc2833bis-04" MFR2 Backward signaling.

=20

Code

Frequency=20

=20

Old

New

1

1140/1020

1020/1140

2

1140/900

1020/1020

3

1020/900

1020/900

4

1140/780

900/1020

5

1020/780

900/900

6

900/780

900/780

7

1140/660

780/1020

8

1020/660

780/900

9

900/660

780/780

10

780/660

780/660

11

1140/540

660/1020

12

1020/540

660/900

13

900/540

660/780

14

780/540

660/660

15

660/540

660/540

=20

=20

=20

Moshe.

=20


------_=_NextPart_001_01C41001.B6C2C148
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.emailstyle17
	{font-family:Arial;
	color:windowtext;}
span.emailstyle18
	{font-family:Arial;
	color:navy;}
span.emailstyle19
	{font-family:Arial;
	color:navy;}
span.emailstyle20
	{font-family:Arial;
	color:navy;}
span.EmailStyle21
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The mistake is at <b><span =
style=3D'font-weight:bold'>Table 14</span></b>
- R2 Backward Register Signals from =
&#8220;</span></font>draft-ietf-avt-rfc2833bis-04&#8221;</p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</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'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>Moshe.</span></font></p>

</div>

<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> </span></font><font =
size=3D2
 face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>Oren =
Peleg</span></font><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> </span></font><font =
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Monday, March
 22, 2004</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=3D2 face=3DTahoma><span
 style=3D'font-size:10.0pt;font-family:Tahoma'>12:56 =
PM</span></font><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> </span></font><font =
size=3D2
 face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>Yuval =
Nissan</span></font><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>; </span></font><font
 size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Moshe
 Samoha</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> FW: RFC2833 =
bis_4<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</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'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>FYI</span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></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> Oren Peleg <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> </span></font><font =
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Monday, March
 22, 2004</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=3D2 face=3DTahoma><span
 style=3D'font-size:10.0pt;font-family:Tahoma'>12:56 =
PM</span></font><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> =
'schulzrinne@cs.columbia.edu';
'scott.petrack@edial.com'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> FW: RFC2833 =
bis_4<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</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'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Please look =
below &#8211;
it seems that some kind of technical mistake was done in the latest =
draft in
regarding to the MF frequency tables.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Regards,</span></=
font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Oren =
P.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></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> Moshe Samoha <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> </span></font><font =
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Monday, March
 22, 2004</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=3D2 face=3DTahoma><span
 style=3D'font-size:10.0pt;font-family:Tahoma'>12:27 =
PM</span></font><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> Oren Peleg; Yuval =
Nissan<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: RFC2833 =
bis_4<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</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'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>I rechecked the =
issue.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>It seems that =
X-axis and
the Y-axis have been replaced at table number 13.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>If we replaced =
them, it
is compatible to our old implementation.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
dir=3DRTL></span><font size=3D2
color=3Dnavy face=3DArial><span lang=3DHE dir=3DRTL =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'><span dir=3DRTL></span>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;color:navy'>Moshe.</span></font></p>

</div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><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> Moshe Samoha <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> </span></font><font =
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Monday, March
 22, 2004</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=3D2 face=3DTahoma><span
 style=3D'font-size:10.0pt;font-family:Tahoma'>11:49 =
AM</span></font><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> Oren Peleg; Yuval =
Nissan<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RFC2833 =
bis_4<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>We found out that we are =
not
compatible with the last RFC2833 draft =
&#8220;</span></font>draft-ietf-avt-rfc2833bis-04&#8221;
MFR2 Backward signaling.</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
 style=3D'margin-left:1.0in;border-collapse:collapse'>
 <tr>
  <td width=3D71 bgcolor=3D"#E0E0E0" style=3D'width:53.6pt;border:solid =
windowtext 1.0pt;
  background:#E0E0E0;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><b><font size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Code</span></font></b></p>
  </td>
  <td width=3D228 colspan=3D2 bgcolor=3D"#E0E0E0" =
style=3D'width:171.0pt;border:solid windowtext 1.0pt;
  border-left:none;background:#E0E0E0;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><b><font size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Frequency
  </span></font></b></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 bgcolor=3D"#BFBFBF" style=3D'width:53.6pt;border:solid =
windowtext 1.0pt;
  border-top:none;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Old</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>New</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/1020</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/1140</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>2</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/900</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>3</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/900</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>4</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/780</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>5</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/780</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>6</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/780</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/780</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>7</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>8</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>9</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/780</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>10</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/660</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>11</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>12</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>13</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/780</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>14</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/660</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>15</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/540</span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
face=3D"Times New Roman"><span
style=3D'font-size:10.0pt'>Moshe.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>
=00
------_=_NextPart_001_01C41001.B6C2C148--

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



From exim@www1.ietf.org  Mon Mar 22 17:17:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28460
	for <avt-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:17:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XjQ-0006mm-K9
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 17:17:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMHG5U026078
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 17:17:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XjB-0006lE-13; Mon, 22 Mar 2004 17:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5NBI-0005wr-A8
	for avt@optimus.ietf.org; Mon, 22 Mar 2004 06:01:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15905
	for <avt@ietf.org>; Mon, 22 Mar 2004 06:01:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5NBE-000766-00
	for avt@ietf.org; Mon, 22 Mar 2004 06:01:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5NAG-0006zs-00
	for avt@ietf.org; Mon, 22 Mar 2004 06:00:17 -0500
Received: from bzq-179-22-133.cust.bezeqint.net ([212.179.22.133] helo=lodmsg01.corp.audiocodes.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5N9K-0006qJ-00
	for avt@ietf.org; Mon, 22 Mar 2004 05:59:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40FFC.30EDE4EE"
Date: Mon, 22 Mar 2004 12:55:30 +0200
Message-ID: <BF10CC312C7A9C4FA2988BE360BAE44DABF031@lodmsg01.corp.audiocodes.com>
Thread-Topic: RFC2833 bis_4
Thread-Index: AcQP8u87l5taC4zwSiqzA8dj+ksPyQABMWewAADsW9A=
X-Priority: 1
Priority: Urgent
Importance: high
From: "Oren Peleg" <OrenP@audiocodes.com>
To: <schulzrinne@cs.columbia.edu>, <scott.petrack@edial.com>
Cc: <avt@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.4 required=5.0 tests=HTML_FONTCOLOR_UNKNOWN,
	HTML_MESSAGE,PRIORITY_NO_NAME,X_PRIORITY_HIGH autolearn=no 
	version=2.60
Subject: [AVT] FW: RFC2833 bis_4
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C40FFC.30EDE4EE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please look below - it seems that some kind of technical mistake was
done in the latest draft in regarding to the MF frequency tables.

=20

Regards,

=20

Oren P.

=20

-----Original Message-----
From: Moshe Samoha=20
Sent: Monday, March 22, 2004 12:27 PM
To: Oren Peleg; Yuval Nissan
Subject: RE: RFC2833 bis_4
Importance: High

=20

I rechecked the issue.

It seems that X-axis and the Y-axis have been replaced at table number
13.

If we replaced them, it is compatible to our old implementation.

=20

=20

=20

=20

=20

=20

Moshe.

-----Original Message-----
From: Moshe Samoha=20
Sent: Monday, March 22, 2004 11:49 AM
To: Oren Peleg; Yuval Nissan
Subject: RFC2833 bis_4
Importance: High

=20

We found out that we are not compatible with the last RFC2833 draft
"draft-ietf-avt-rfc2833bis-04" MFR2 Backward signaling.

=20

Code

Frequency=20

=20

Old

New

1

1140/1020

1020/1140

2

1140/900

1020/1020

3

1020/900

1020/900

4

1140/780

900/1020

5

1020/780

900/900

6

900/780

900/780

7

1140/660

780/1020

8

1020/660

780/900

9

900/660

780/780

10

780/660

780/660

11

1140/540

660/1020

12

1020/540

660/900

13

900/540

660/780

14

780/540

660/660

15

660/540

660/540

=20

=20

=20

Moshe.

=20


------_=_NextPart_001_01C40FFC.30EDE4EE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.emailstyle17
	{font-family:Arial;
	color:windowtext;}
span.emailstyle18
	{font-family:Arial;
	color:navy;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<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'>Please look below &#8211; it seems =
that
some kind of technical mistake was done in the latest draft in regarding =
to the
MF frequency tables.</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'>&nbsp;</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'>Regards,</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'>&nbsp;</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'>Oren 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'>&nbsp;</span></font></p>

<p class=3DMsoNormal><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> Moshe Samoha <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> </span></font><font =
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Monday, March
 22, 2004</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=3D2 face=3DTahoma><span
 style=3D'font-size:10.0pt;font-family:Tahoma'>12:27 =
PM</span></font><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> Oren Peleg; Yuval =
Nissan<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: RFC2833 =
bis_4<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</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 rechecked the =
issue.</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'>It seems that X-axis and the Y-axis =
have
been replaced at table number 13.</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 we replaced them, it is =
compatible to
our old implementation.</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'>&nbsp;</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'>&nbsp;</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'>&nbsp;</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'>&nbsp;</span></font></p>

<p class=3DMsoNormal><span dir=3DRTL></span><font size=3D2 color=3Dnavy =
face=3DArial><span
lang=3DHE dir=3DRTL =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><span
dir=3DRTL></span>&nbsp;</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'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>Moshe.</span></font></p>

</div>

<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> Moshe Samoha <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> </span></font><font =
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Monday, March
 22, 2004</span></font><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=3D2 face=3DTahoma><span
 style=3D'font-size:10.0pt;font-family:Tahoma'>11:49 =
AM</span></font><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> Oren Peleg; Yuval =
Nissan<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RFC2833 =
bis_4<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</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'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>We found out that we are =
not
compatible with the last RFC2833 draft =
&#8220;</span></font>draft-ietf-avt-rfc2833bis-04&#8221;
MFR2 Backward signaling.</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
 style=3D'margin-left:.5in;border-collapse:collapse'>
 <tr>
  <td width=3D71 bgcolor=3D"#E0E0E0" style=3D'width:53.6pt;border:solid =
windowtext 1.0pt;
  background:#E0E0E0;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><b><font size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Code</span></font></b></p>
  </td>
  <td width=3D228 colspan=3D2 bgcolor=3D"#E0E0E0" =
style=3D'width:171.0pt;border:solid windowtext 1.0pt;
  border-left:none;background:#E0E0E0;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><b><font size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Frequency
  </span></font></b></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 bgcolor=3D"#BFBFBF" style=3D'width:53.6pt;border:solid =
windowtext 1.0pt;
  border-top:none;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Old</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>New</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/1020</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/1140</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>2</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/900</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>3</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/900</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>4</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/780</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>5</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/780</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>6</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/780</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/780</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>7</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>8</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>9</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/780</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>10</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/660</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/660</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>11</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1140/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/1020</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>12</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>1020/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/900</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>13</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>900/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/780</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>14</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>780/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/660</span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D71 style=3D'width:53.6pt;border:solid windowtext =
1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>15</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/540</span></font></p>
  </td>
  <td width=3D114 =
style=3D'width:85.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext =
1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>660/540</span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3D"Times New Roman"><span
style=3D'font-size:10.0pt'>Moshe.</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'>&nbsp;</span></font></p>

</div>

</body>

</html>
=00
------_=_NextPart_001_01C40FFC.30EDE4EE--

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



From exim@www1.ietf.org  Mon Mar 22 17:43:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00182
	for <avt-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:43:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y8q-0001SM-1a
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 17:43:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMhVXi005539
	for avt-archive@odin.ietf.org; Mon, 22 Mar 2004 17:43:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y8Y-0001PS-AK; Mon, 22 Mar 2004 17:43:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y4U-00015o-Oe
	for avt@optimus.ietf.org; Mon, 22 Mar 2004 17:39:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29948
	for <avt@ietf.org>; Mon, 22 Mar 2004 17:38:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y4S-0001vV-00
	for avt@ietf.org; Mon, 22 Mar 2004 17:39:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Y3Q-0001pQ-00
	for avt@ietf.org; Mon, 22 Mar 2004 17:37:57 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y2w-0001i7-00
	for avt@ietf.org; Mon, 22 Mar 2004 17:37:27 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63034 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B5Y2O-00038L-00
	for avt@ietf.org; Mon, 22 Mar 2004 22:36:52 +0000
Date: Mon, 22 Mar 2004 22:37:52 +0000
From: Colin Perkins <csp@csperkins.org>
To: avt@ietf.org
Message-Id: <20040322223752.6694b80d.csp@csperkins.org>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Reminder: mailing list policy
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

A reminder that, as a way of reducing spam, the AVT mailing list holds
email sent by non-subscribers for approval. This filter catches over 50
messages each day, the overwhelming majority of which are spam which is
deleted. If you post to the list using an address which is not subscribed,
your mail will likely be delayed, and may be accidently discarded, since
approval is a manual process. 

We would urge everyone considering posting to subscribe to the list first,
to ease the approval load. You may mark the address such that mail is not
delivered to it, if you wish to send from a different address to that you
use to receive mail.

Colin

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



From exim@www1.ietf.org  Tue Mar 23 03:32:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11351
	for <avt-archive@odin.ietf.org>; Tue, 23 Mar 2004 03:32:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5hKU-0003YY-Ap
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 03:32:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N8WAw3013669
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 03:32:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5hKM-0003X7-Hi; Tue, 23 Mar 2004 03:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5gW3-00073d-BY
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 02:40:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09626
	for <avt@ietf.org>; Tue, 23 Mar 2004 02:40:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5gVz-00052N-00
	for avt@ietf.org; Tue, 23 Mar 2004 02:39:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5gV1-0004wZ-00
	for avt@ietf.org; Tue, 23 Mar 2004 02:39:00 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5gUA-0004kI-00
	for avt@ietf.org; Tue, 23 Mar 2004 02:38:06 -0500
Received: from rkumar-w2k01.cisco.com (sjc-vpn1-1021.cisco.com [10.21.99.253])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i2N7bWQK021113;
	Mon, 22 Mar 2004 23:37:32 -0800 (PST)
Message-Id: <4.3.2.7.2.20040322233426.01cc3a50@vtg-um-e2k1.cisco.com>
X-Sender: rkumar@vtg-um-e2k1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 22 Mar 2004 23:37:31 -0800
To: "Yaakov Stein" <yaakov_s@rad.com>
From: Rajesh Kumar <rkumar@cisco.com>
Subject: RE: [AVT] Re: Clearmode definition.
Cc: "Colin Perkins" <csp@csperkins.org>, <avt@ietf.org>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52024E9B9A@exrad2.ad.rad.co.
 il>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Yaakov,
One of the cases you mention include an RTP encapsulation of Nx64. Unless 
you have already done so, I recommend you register a MIME for it and allow 
its session-by-session negotiation using SDP, H.245 or other means. My 
guess from having read the PWE3 drafts in the past is that you are limiting 
the application to a provisioned RTP Nx64 session. While that is adequate 
in some applications, others will require/prefer the signaled establishment 
of Nx64 sessions.

Best regards,

Rajesh

At 05:13 PM 3/21/2004 +0200, Yaakov Stein wrote:
>
> > --> Rajesh Kumar <rkumar@cisco.com> writes:
> > > Are there plans to address N x 64 clear mode (N > 1) in
> > > draft-ietf-avt-rtp-clearmode-04.txt ?
> > >
> > > One method might be to have N as a MIME parameter.
> > >
> > > I recommend that we do.
> >
> > No. This is explicitly out of scope of AVT, and will be
> > addressed in the PWE3 working group.
>
>N*DS0 (i.e. N 64Kbps timeslots) with or without CAS
>is defined in the PWE3 TDM requirements draft as a structured TDM
>service.
>
>Right now in PWE we have three TDM drafts:
>
>1) The standards track one is SAToP (Structure Agnostic TDM over
>Packet),
>but this only handles full T1, E1, E3 or T3 trunks
>(whether structured or not). Thus this doesn't address N*64.
>
>2) CESoPSN - candidiate informational RFC
>This draft can handle N*DS0 by encapsulating one or more frames or N
>timeslots
>per packet, with or without RTP.
>
>3) TDMoIP - candidate informational RFC
>This draft can handle N*DS0 by using AAL1 which appends
>pointers to identify the first timeslot.
>If the 64K channels are carrying HDLC data, there is a mode
>which suppresses idle flags.
>
>As you can see, the treatment of N*DS0 is only in the informational
>drafts,
>not in the standards track one.
>
>The current suggestion for communicating N is via the PWE control
>protocol,
>where there is a parameter called CEP/TDM bit rate.
>
>Y(J)S


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



From exim@www1.ietf.org  Tue Mar 23 06:40:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19994
	for <avt-archive@odin.ietf.org>; Tue, 23 Mar 2004 06:40:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5kGP-0002aM-LE
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 06:40:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NBe9ll009918
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 06:40:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5kGI-0002ZD-V1; Tue, 23 Mar 2004 06:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5kFW-0002To-92
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 06:39:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19939
	for <avt@ietf.org>; Tue, 23 Mar 2004 06:39:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5kFR-0002af-00
	for avt@ietf.org; Tue, 23 Mar 2004 06:39:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5kEd-0002UY-00
	for avt@ietf.org; Tue, 23 Mar 2004 06:38:20 -0500
Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5kDq-0002Gm-00
	for avt@ietf.org; Tue, 23 Mar 2004 06:37:30 -0500
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i2NBaVxF016581
	for <avt@ietf.org>; Tue, 23 Mar 2004 13:36:31 +0200 (IST)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i2NBaUte016566
	for <avt@ietf.org>; Tue, 23 Mar 2004 13:36:30 +0200 (IST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Re: Clearmode definition.
Date: Tue, 23 Mar 2004 13:36:05 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
Thread-Topic: [AVT] Re: Clearmode definition.
Thread-Index: AcQQqbvbqaEQPYE5QPGKWQfmZpKj4QAIAYlg
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Rajesh Kumar" <rkumar@cisco.com>
Cc: "Colin Perkins" <csp@csperkins.org>, <avt@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

=20
> Yaakov,
> One of the cases you mention include an RTP encapsulation of=20
> Nx64. Unless you have already done so, I recommend you=20
> register a MIME for it and allow its session-by-session=20
> negotiation using SDP, H.245 or other means. My guess from=20
> having read the PWE3 drafts in the past is that you are=20
> limiting the application to a provisioned RTP Nx64 session.=20
> While that is adequate in some applications, others will=20
> require/prefer the signaled establishment of Nx64 sessions.

Rajesh,=20

Since this is a PW protocol, it works in the PWE fashion.
Either the PW is manually provisioned, or it is set up
using the PW control protocol.=20

In either case it is not envisioned that this connection
will be set-up and torn-down on a "session per session" basis,
just as a T1 or E1 is not torn-down after a phone conversation.

This is another difference between what we are doing in PWE3,
and the typical AVT method of working.

The point of my previous email was that even if it is decided
that PWE is a proper place to standardize methods for
transport of N*64 flows over IP, their treatment at PWE3
may not be what you are looking for.

In particular, MIME types and use of SDP are entirely
alien to the PWE3 way of doing things.

Hence if you have a need for an RTP encapsulation of N*64k,=20
I would suggest that the AVT WG look into it,
trying to keep the encapsulation compatible with the
appropriate PWE draft.

Y(J)S

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



From exim@www1.ietf.org  Tue Mar 23 10:40:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04217
	for <avt-archive@odin.ietf.org>; Tue, 23 Mar 2004 10:40:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5o0Q-0007kN-Dz
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:39:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NFds6a029778
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:39:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5nyT-00079R-B9; Tue, 23 Mar 2004 10:37:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5nxP-00072c-E1
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 10:36:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04074
	for <avt@ietf.org>; Tue, 23 Mar 2004 10:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5nxI-0003cP-00
	for avt@ietf.org; Tue, 23 Mar 2004 10:36:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5nwZ-0003Ty-00
	for avt@ietf.org; Tue, 23 Mar 2004 10:35:56 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5nvf-0003ED-00
	for avt@ietf.org; Tue, 23 Mar 2004 10:34:59 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 23 Mar 2004 07:34:45 -0800
Received: from rkumar-w2k01.cisco.com (sjc-vpn4-814.cisco.com [10.21.83.45])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2NFYO8Q019471;
	Tue, 23 Mar 2004 07:34:25 -0800 (PST)
Message-Id: <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
X-Sender: rkumar999@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 23 Mar 2004 07:34:24 -0800
To: "Yaakov Stein" <yaakov_s@rad.com>
From: Rajesh Kumar <rkumar999@comcast.net>
Subject: RE: [AVT] Re: Clearmode definition.
Cc: "Rajesh Kumar" <rkumar@cisco.com>, "Colin Perkins" <csp@csperkins.org>,
        <avt@ietf.org>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.
 il>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_308128244==_.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_MESSAGE 
	autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

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

Yaakov,

At 01:36 PM 3/23/2004 +0200, Yaakov Stein wrote:
>
> > Yaakov,
> > One of the cases you mention include an RTP encapsulation of
> > Nx64. Unless you have already done so, I recommend you
> > register a MIME for it and allow its session-by-session
> > negotiation using SDP, H.245 or other means. My guess from
> > having read the PWE3 drafts in the past is that you are
> > limiting the application to a provisioned RTP Nx64 session.
> > While that is adequate in some applications, others will
> > require/prefer the signaled establishment of Nx64 sessions.
>
>Rajesh,
>
>Since this is a PW protocol, it works in the PWE fashion.
>Either the PW is manually provisioned, or it is set up
>using the PW control protocol.
>
>In either case it is not envisioned that this connection
>will be set-up and torn-down on a "session per session" basis,
>just as a T1 or E1 is not torn-down after a phone conversation.
>
>This is another difference between what we are doing in PWE3,
>and the typical AVT method of working.
>
>The point of my previous email was that even if it is decided
>that PWE is a proper place to standardize methods for
>transport of N*64 flows over IP, their treatment at PWE3
>may not be what you are looking for.
>
>In particular, MIME types and use of SDP are entirely
>alien to the PWE3 way of doing things.
>
>Hence if you have a need for an RTP encapsulation of N*64k,
>I would suggest that the AVT WG look into it,
>trying to keep the encapsulation compatible with the
>appropriate PWE draft.

This is what I requested from the AVT group but they indicated I go to the 
PWE3 group for it. However, if, between the two groups, we think that a 
MIME for nx64 over RTP will not be widely useful, then we can drop it. 
Registration of vendor-specific MIMEs is also possible, but is this the way 
we want to go? Either way, I would like us in AVT and PWE3 to make a 
conscious choice.

Rajesh


>Y(J)S
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt

--=====================_308128244==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Yaakov,<br>
<br>
At 01:36 PM 3/23/2004 +0200, Yaakov Stein wrote:<br>
<blockquote type=cite cite>&nbsp;<br>
&gt; Yaakov,<br>
&gt; One of the cases you mention include an RTP encapsulation of <br>
&gt; Nx64. Unless you have already done so, I recommend you <br>
&gt; register a MIME for it and allow its session-by-session <br>
&gt; negotiation using SDP, H.245 or other means. My guess from <br>
&gt; having read the PWE3 drafts in the past is that you are <br>
&gt; limiting the application to a provisioned RTP Nx64 session. <br>
&gt; While that is adequate in some applications, others will <br>
&gt; require/prefer the signaled establishment of Nx64 sessions.<br>
<br>
Rajesh, <br>
<br>
Since this is a PW protocol, it works in the PWE fashion.<br>
Either the PW is manually provisioned, or it is set up<br>
using the PW control protocol. <br>
<br>
In either case it is not envisioned that this connection<br>
will be set-up and torn-down on a &quot;session per session&quot;
basis,<br>
just as a T1 or E1 is not torn-down after a phone conversation.<br>
<br>
This is another difference between what we are doing in PWE3,<br>
and the typical AVT method of working.<br>
<br>
The point of my previous email was that even if it is decided<br>
that PWE is a proper place to standardize methods for<br>
transport of N*64 flows over IP, their treatment at PWE3<br>
may not be what you are looking for.<br>
<br>
In particular, MIME types and use of SDP are entirely<br>
alien to the PWE3 way of doing things.<br>
<br>
Hence if you have a need for an RTP encapsulation of N*64k, <br>
I would suggest that the AVT WG look into it,<br>
trying to keep the encapsulation compatible with the<br>
appropriate PWE
draft.</blockquote><font face="Times New Roman, Times"><br>
This is what I requested from the AVT group but they indicated I go to
the PWE3 group for it. However, if, between the two groups, we think that
a MIME for nx64 over RTP will not be widely useful, then we can drop it.
Registration of vendor-specific MIMEs is also possible, but is this the
way we want to go? Either way, I would like us in AVT and PWE3 to make a
conscious choice.<br>
<br>
Rajesh<br>
<br>
<br>
</font><blockquote type=cite cite>Y(J)S<br>
<br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
avt@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/avt" eudora="autourl">https://www1.ietf.org/mailman/listinfo/avt</a>
</blockquote></html>

--=====================_308128244==_.ALT--


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



From exim@www1.ietf.org  Tue Mar 23 10:57:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05426
	for <avt-archive@odin.ietf.org>; Tue, 23 Mar 2004 10:57:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oGi-00019h-Jx
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:56:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NFui6J004322
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:56:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oG3-0000pV-3l; Tue, 23 Mar 2004 10:56:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5n8m-0003hx-PX
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 09:44:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29804
	for <avt@ietf.org>; Tue, 23 Mar 2004 09:44:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5n8k-0003p3-00
	for avt@ietf.org; Tue, 23 Mar 2004 09:44:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5n7m-0003ed-00
	for avt@ietf.org; Tue, 23 Mar 2004 09:43:28 -0500
Received: from radmail.rad.co.il ([212.117.147.38] helo=antivir1.rad.co.il)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5n6f-0003K0-00
	for avt@ietf.org; Tue, 23 Mar 2004 09:42:18 -0500
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i2NEfJxF008865
	for <avt@ietf.org>; Tue, 23 Mar 2004 16:41:19 +0200 (IST)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i2NEfIte008856
	for <avt@ietf.org>; Tue, 23 Mar 2004 16:41:18 +0200 (IST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C410E4.C870586E"
Subject: RE: [AVT] RE: RFC2833 bis_4
Date: Tue, 23 Mar 2004 16:40:26 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A52024E9EDF@exrad2.ad.rad.co.il>
Thread-Topic: [AVT] RE: RFC2833 bis_4
Thread-Index: AcQP8u87l5taC4zwSiqzA8dj+ksPyQABMWewAADsW9AAADZocAABQiZwADNCYNA=
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Moshe Samoha" <MosheS@audiocodes.com>,
        "schulzrinne@cs.columbia.edu" <schulzrinne@cs.columbia.edu'.cnri.reston.va.us>,
        "scott.petrack@edial.com" <scott.petrack@edial.com'.cnri.reston.va.us>,
        <avt@ietf.org>
Cc: "Oren Peleg" <OrenP@audiocodes.com>,
        "Yuval Nissan" <YuvalN@audiocodes.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE,
	HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE,HTML_TAG_EXISTS_TBODY 
	autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C410E4.C870586E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Table 14 even has several "MF" tones with only a single tone!
=20
The best way to ensure that there are no mistakes is to stay close to
Q.441.
=20
There we see that the forward and backward combinations
are the same, except for the following exchange of frequencies:
=20
  FWD  BKWD
  1380     540
  1500     660
  1620     780
  1740     900
  1860   1020=20
  1980   1140
=20
Also, note that unlike that which is stated in the text,
MFR2 is not always MFCR2, i.e. there are places where R2 is
not compelled. Even when compelled, there are non-standard
ways of compelling (e.g. Socotel which uses a single acknowledgement
tone).
=20
Note also that not all implementations utilize all the R2 frequencies.
=20
Y(J)S
=20
=20


________________________________

	From: avt-admin@ietf.org [mailto:avt-admin@ietf.org] On Behalf
Of Moshe Samoha
	Sent: Monday, March 22, 2004 13:35
	To: schulzrinne@cs.columbia.edu; scott.petrack@edial.com;
avt@ietf.org
	Cc: Oren Peleg; Yuval Nissan
	Subject: [AVT] RE: RFC2833 bis_4
=09
=09

	The mistake is at Table 14 - R2 Backward Register Signals from
"draft-ietf-avt-rfc2833bis-04"

	=20

	=20

	=20

	Moshe.

	-----Original Message-----
	From: Oren Peleg=20
	Sent: Monday, March 22, 2004 12:56 PM
	To: Yuval Nissan; Moshe Samoha
	Subject: FW: RFC2833 bis_4
	Importance: High

	=20

	FYI

	=20

	-----Original Message-----
	From: Oren Peleg=20
	Sent: Monday, March 22, 2004 12:56 PM
	To: 'schulzrinne@cs.columbia.edu'; 'scott.petrack@edial.com'
	Cc: avt@ietf.org
	Subject: FW: RFC2833 bis_4
	Importance: High

	=20

	Please look below - it seems that some kind of technical mistake
was done in the latest draft in regarding to the MF frequency tables.

	=20

	Regards,

	=20

	Oren P.

	=20

	-----Original Message-----
	From: Moshe Samoha=20
	Sent: Monday, March 22, 2004 12:27 PM
	To: Oren Peleg; Yuval Nissan
	Subject: RE: RFC2833 bis_4
	Importance: High

	=20

	I rechecked the issue.

	It seems that X-axis and the Y-axis have been replaced at table
number 13.

	If we replaced them, it is compatible to our old implementation.

	=20

	=20

	=20

	=20

	=20

	=20

	Moshe.

	-----Original Message-----
	From: Moshe Samoha=20
	Sent: Monday, March 22, 2004 11:49 AM
	To: Oren Peleg; Yuval Nissan
	Subject: RFC2833 bis_4
	Importance: High

	=20

	We found out that we are not compatible with the last RFC2833
draft "draft-ietf-avt-rfc2833bis-04" MFR2 Backward signaling.

	=20

Code

Frequency=20

=20

Old

New

1

1140/1020

1020/1140

2

1140/900

1020/1020

3

1020/900

1020/900

4

1140/780

900/1020

5

1020/780

900/900

6

900/780

900/780

7

1140/660

780/1020

8

1020/660

780/900

9

900/660

780/780

10

780/660

780/660

11

1140/540

660/1020

12

1020/540

660/900

13

900/540

660/780

14

780/540

660/660

15

660/540

660/540

	=20

	=20

	=20

	Moshe.

	=20


------_=_NextPart_001_01C410E4.C870586E
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.emailstyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
SPAN.emailstyle18 {
	COLOR: navy; FONT-FAMILY: Arial
}
SPAN.emailstyle19 {
	COLOR: navy; FONT-FAMILY: Arial
}
SPAN.emailstyle20 {
	COLOR: navy; FONT-FAMILY: Arial
}
SPAN.EmailStyle21 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Table=20
14 even has several "MF" tones with only a single =
tone!</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>The=20
best way to ensure that there are no mistakes is to stay =
</FONT></SPAN><SPAN=20
class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>close to=20
Q.441.</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>There=20
we see that the forward and backward combinations</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>are=20
the same, except for the following exchange of =
frequencies:</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;=20
FWD&nbsp; BKWD</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;=20
1380&nbsp;&nbsp;&nbsp;&nbsp; 540</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;=20
1500&nbsp;&nbsp;&nbsp;&nbsp; 660</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;=20
1620&nbsp;&nbsp;&nbsp;&nbsp; 780</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;&nbsp;1740&nbsp;&nbsp;&nbsp; =
&nbsp;900</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;=20
1860&nbsp;&nbsp;&nbsp;1020 </FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;=20
1980&nbsp;&nbsp; 1140</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Also,&nbsp;note that unlike that which is stated in the=20
text,</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004></SPAN><SPAN =
class=3D812395911-23032004><FONT=20
face=3DArial color=3D#0000ff size=3D2>MFR2 is not always MFCR2, i.e. =
there are places=20
where R2 is</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>not=20
compelled. Even when compelled, there =
are&nbsp;non-standard</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>ways=20
of compelling (e.g. Socotel which uses a single acknowledgement=20
tone).</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Note=20
also that not all implementations utilize all the R2=20
frequencies.</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Y(J)S</FONT></SPAN></DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D812395911-23032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> avt-admin@ietf.org=20
  [mailto:avt-admin@ietf.org] <B>On Behalf Of </B>Moshe =
Samoha<BR><B>Sent:</B>=20
  Monday, March 22, 2004 13:35<BR><B>To:</B> =
schulzrinne@cs.columbia.edu;=20
  scott.petrack@edial.com; avt@ietf.org<BR><B>Cc:</B> Oren Peleg; Yuval=20
  Nissan<BR><B>Subject:</B> [AVT] RE: RFC2833 bis_4<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The mistake is at =
<B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Table 14</SPAN></B> - R2 Backward Register =
Signals=20
  from &#8220;</SPAN></FONT>draft-ietf-avt-rfc2833bis-04&#8221;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy">Moshe.</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B>=20
  </SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Oren =
Peleg</SPAN></FONT><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
</SPAN></FONT><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">Monday,=20
  March 22, 2004</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> </SPAN></FONT><FONT =
face=3DTahoma=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">12:56=20
  PM</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> </SPAN></FONT><FONT =
face=3DTahoma=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Yuval=20
  Nissan</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">; </SPAN></FONT><FONT =
face=3DTahoma=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Moshe=20
  Samoha</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> FW: RFC2833 =
bis_4<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Importance:</SPAN></B> =
High</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">FYI</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Oren Peleg=20
  <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
</SPAN></FONT><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">Monday,=20
  March 22, 2004</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> </SPAN></FONT><FONT =
face=3DTahoma=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">12:56=20
  PM</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
'schulzrinne@cs.columbia.edu';=20
  'scott.petrack@edial.com'<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Cc:</SPAN></B>=20
  avt@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> FW:=20
  RFC2833 bis_4<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Importance:</SPAN></B>=20
  High</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Please=20
  look below &#8211; it seems that some kind of technical mistake was =
done in the=20
  latest draft in regarding to the MF frequency =
tables.</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Oren=20
  P.</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Moshe=20
  Samoha <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B>=20
  </SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Monday, March 22,=20
  2004</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> </SPAN></FONT><FONT =
face=3DTahoma=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">12:27=20
  PM</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Oren Peleg; Yuval =
Nissan<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: RFC2833 =
bis_4<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Importance:</SPAN></B> =
High</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">I=20
  rechecked the issue.</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">It seems=20
  that X-axis and the Y-axis have been replaced at table number=20
  13.</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">If we=20
  replaced them, it is compatible to our old =
implementation.</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
dir=3Drtl></SPAN><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN lang=3DHE dir=3Drtl=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
  dir=3Drtl></SPAN></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy">Moshe.</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DTahoma =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Moshe=20
  Samoha <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B>=20
  </SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Monday, March 22,=20
  2004</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> </SPAN></FONT><FONT =
face=3DTahoma=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">11:49=20
  AM</SPAN></FONT><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Oren Peleg; Yuval =
Nissan<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RFC2833 =
bis_4<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Importance:</SPAN></B> =
High</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We found out that we are =
not=20
  compatible with the last RFC2833 draft=20
  &#8220;</SPAN></FONT>draft-ietf-avt-rfc2833bis-04&#8221; MFR2 Backward =
signaling.</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <TABLE class=3DMsoNormalTable=20
  style=3D"MARGIN-LEFT: 1in; BORDER-COLLAPSE: collapse" cellSpacing=3D0=20
  cellPadding=3D0 border=3D0>
    <TBODY>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: =
#e0e0e0; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: =
53.6pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71 bgColor=3D#e0e0e0>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><B><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: =
12pt">Code</SPAN></FONT></B></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: =
#e0e0e0; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 171pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D228 bgColor=3D#e0e0e0 colSpan=3D2>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><B><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 12pt">Frequency=20
        </SPAN></FONT></B></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; BACKGROUND: #bfbfbf; =
PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71 bgColor=3D#bfbfbf>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">Old</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">New</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1140/1020</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/1140</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">2</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1140/900</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/1020</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">3</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/900</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/900</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">4</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1140/780</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">900/1020</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">5</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/780</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">900/900</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">6</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">900/780</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">900/780</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">7</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1140/660</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">780/1020</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">8</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/660</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">780/900</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">9</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">900/660</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">780/780</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">10</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">780/660</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">780/660</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">11</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1140/540</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">660/1020</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">12</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">1020/540</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">660/900</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">13</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">900/540</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">660/780</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">14</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">780/540</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">660/660</SPAN></FONT></P></TD></TR>
    <TR>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: windowtext 1pt solid; WIDTH: 53.6pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D71>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">15</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">660/540</SPAN></FONT></P></TD>
      <TD=20
      style=3D"BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; =
BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; WIDTH: 85.5pt; PADDING-TOP: 0in; =
BORDER-BOTTOM: windowtext 1pt solid"=20
      width=3D114>
        <P class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">660/540</SPAN></FONT></P></TD></TR></TBODY></TABLE>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Moshe.</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C410E4.C870586E--

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



From exim@www1.ietf.org  Tue Mar 23 11:43:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05424
	for <avt-archive@odin.ietf.org>; Tue, 23 Mar 2004 10:57:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oGi-00019j-Kj
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:56:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NFui6u004321
	for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:56:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oG3-0000pq-R2; Tue, 23 Mar 2004 10:56:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5o3z-0008JW-9E
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 10:43:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04552
	for <avt@ietf.org>; Tue, 23 Mar 2004 10:43:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5o3w-0004dM-00
	for avt@ietf.org; Tue, 23 Mar 2004 10:43:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5o33-0004UT-00
	for avt@ietf.org; Tue, 23 Mar 2004 10:42:38 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5o2E-0004Hv-00
	for avt@ietf.org; Tue, 23 Mar 2004 10:41:47 -0500
Received: from mangole ([130.209.247.112]:3712 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B5o1h-0000TF-00; Tue, 23 Mar 2004 15:41:13 +0000
Date: Tue, 23 Mar 2004 15:42:16 +0000
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar999@comcast.net>
Cc: yaakov_s@rad.com, rkumar@cisco.com, avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040323154216.3f652c43.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
References: <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
	<4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar999@comcast.net> writes:
...
> >Hence if you have a need for an RTP encapsulation of N*64k,
> >I would suggest that the AVT WG look into it,
> >trying to keep the encapsulation compatible with the
> >appropriate PWE draft.
> 
> This is what I requested from the AVT group but they indicated I go to
> the PWE3 group for it. However, if, between the two groups, we think that
> a MIME for nx64 over RTP will not be widely useful, then we can drop it. 
> Registration of vendor-specific MIMEs is also possible, but is this the
> way we want to go? Either way, I would like us in AVT and PWE3 to make a 
> conscious choice.

What would be the use case for having the MIME type registered? I've not
heard a reason why the mechanisms being developed in PWE3 are insufficient.

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Wed Mar 24 02:26:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26646
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 02:26:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62mB-0006aW-4S
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 02:26:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O7QBe7025323
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 02:26:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62m2-0006YX-RB; Wed, 24 Mar 2004 02:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62lK-0006F2-2w
	for avt@optimus.ietf.org; Wed, 24 Mar 2004 02:25:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25211
	for <avt@ietf.org>; Wed, 24 Mar 2004 02:25:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62lG-0002qi-00
	for avt@ietf.org; Wed, 24 Mar 2004 02:25:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B62kD-0002ew-00
	for avt@ietf.org; Wed, 24 Mar 2004 02:24:10 -0500
Received: from mail3.pi.se ([195.7.64.137] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62jE-0002SU-00
	for avt@ietf.org; Wed, 24 Mar 2004 02:23:09 -0500
Received: from vit (136.240.13.217.in-addr.dgcsystems.net [217.13.240.136])
	(authenticated (0 bits))
	by mail3.pi.se (8.12.10/8.11.2) with ESMTP id i2O7KZpO001862;
	Wed, 24 Mar 2004 08:20:39 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "avt IETF" <avt@ietf.org>
Cc: "STF267" <stf267@etsi.org>, "Toip list" <toip@snowshore.com>,
        "AG 9 ITS" <ag9@its.se>
Subject: [avt]  New version of RFC2793bis - rtp payload format for text coinversation is published
Date: Wed, 24 Mar 2004 08:23:07 +0100
Message-ID: <BHEHLFPKIPMLPFNFAHJKOEJPDOAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0000_01C41179.3C5B06D0"
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.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C41179.3C5B06D0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MIME-Autoconverted: from 8bit to quoted-printable by mail3.pi.se id i2O7KZpO001862
Content-Transfer-Encoding: quoted-printable

A new version of RFC2793bis, RTP payload format for text conversation is
published by IETF as announced in the mail below.

This version (-03) contains slight modifications from the previous versio=
n
in response to comments received in the mail list and in the avt meeting =
in
Seoul.

The following is a summary of the main changes referring to the modified
sections:
------
3.2 The description of the use of the audio/t140 format is slightly
modified, by deleting a sentence about it being not suitable for
multimedia.

3.7 Timestamp for audio/t140. A sentence about what to do if different
payload types in the same stream use different clock rates is deleted. Th=
at
is a general RTP problem.

3.8 Renamed to "structure of redundant data"

4.2 New section inserted describing the mechanisms for detection of loss.

11. Reference to SRTP changed from ietf-draft to RFC 3711

------
Furthermore, a new version of ietf-draft-avt-text-red has been published,
also meeting modification requirements from Seoul by minor changes. The
announcement is copied last in this mail.

It is my hope that the increased clarity of these specifications will
contribute to ease the development of interoperable text communication
solutions.

Regards

Gunnar Hellstr=F6m
-------------------------------------------
Gunnar Hellstr=F6m
Omnitor AB
Renathv=E4gen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------


-----Original Message-----
From: owner-ietf-announce@ietf.org
[mailto:owner-ietf-announce@ietf.org]On Behalf Of
Internet-Drafts@ietf.org
Sent: Thursday, March 18, 2004 3:49 PM
To: IETF-Announce:
Subject: I-D ACTION:draft-ietf-avt-rfc2793bis-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: RTP Payload for Text Conversation
	Author(s)	: G. Hellstrom
	Filename	: draft-ietf-avt-rfc2793bis-03.txt
	Pages		: 21
	Date		: 2004-3-17

This memo describes how to carry text conversation session contents
in RTP packets. Text conversation session contents are specified in
ITU-T Recommendation T.140 [1].

Text conversation is used alone or in connection to other
conversational facilities such as video and voice, to form multimedia
conversation services.

This RTP payload description contains an optional possibility to
include redundant text from already transmitted packets in order to
reduce the risk of text loss caused by packet loss. The redundancy
coding follows RFC 2198.

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


------------text-red-----------------------------------------------------=
--
--------------

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 t=
he
IETF.

	Title		: Registration of the text/red MIME Sub-Type
	Author(s)	: P. Jones
	Filename	: draft-ietf-avt-text-red-02.txt
	Pages		: 6
	Date		: 2004-3-22

This document defines the text/red MIME sub-type.  The actual RTP
   packetization for this MIME type is specified in RFC 2198.

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

------=_NextPart_000_0000_01C41179.3C5B06D0
Content-Type: Message/External-body;
	name="ATT00025.dat"
Content-Disposition: attachment;
	filename="ATT00025.dat"
Content-Transfer-Encoding: 7bit

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

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

------=_NextPart_000_0000_01C41179.3C5B06D0
Content-Type: Message/External-body;
	name="draft-ietf-avt-rfc2793bis-03.txt"
Content-Disposition: attachment;
	filename="draft-ietf-avt-rfc2793bis-03.txt"
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0000_01C41179.3C5B06D0--



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



From exim@www1.ietf.org  Wed Mar 24 03:32:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04869
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 03:32:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B63o2-0006vS-Ep
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 03:32:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O8WAbJ026577
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 03:32:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B63nu-0006nI-4j; Wed, 24 Mar 2004 03:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5olt-0005Lh-Bz
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 11:28:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08432
	for <avt@ietf.org>; Tue, 23 Mar 2004 11:28:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ols-0004Am-00
	for avt@ietf.org; Tue, 23 Mar 2004 11:28:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5oky-0003zH-00
	for avt@ietf.org; Tue, 23 Mar 2004 11:28:01 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5oiy-0003ZS-00
	for avt@ietf.org; Tue, 23 Mar 2004 11:25:57 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 23 Mar 2004 08:25:42 -0800
Received: from rkumar-w2k01.cisco.com (sjc-vpn4-814.cisco.com [10.21.83.45])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i2NGPLQK027284;
	Tue, 23 Mar 2004 08:25:22 -0800 (PST)
Message-Id: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
X-Sender: rkumar@vtg-um-e2k1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 23 Mar 2004 08:25:21 -0800
To: Colin Perkins <csp@csperkins.org>
From: Rajesh Kumar <rkumar@cisco.com>
Subject: Re: [AVT] Re: Clearmode definition.
Cc: Rajesh Kumar <rkumar999@comcast.net>, yaakov_s@rad.com, avt@ietf.org
In-Reply-To: <20040323161109.5d252831.csp@csperkins.org>
References: <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
 <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
 <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
 <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
 <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_311185471==_.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_MESSAGE,
	MAILTO_TO_SPAM_ADDR autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

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

At 04:11 PM 3/23/2004 +0000, Colin Perkins wrote:
>--> Rajesh Kumar <rkumar999@comcast.net> writes:
> > At 03:42 PM 3/23/2004 +0000, Colin Perkins wrote:
> > >What would be the use case for having the MIME type registered? I've not
> > >heard a reason why the mechanisms being developed in PWE3 are
> > >insufficient.
> >
> > Say you set up an 384 kbps call via SIP for your video. You do not use
> > the relevant video MIME because what gets put in RTP is nx64 and the
> > video/audio is one step removed.
> >
> > You may not want to proliferate signaling in your network.
>
>Again, what is the application scenario? Why the need to signal Nx64 kbps
>clearmode, rather than the appropriate video format?

Because in this case you would encapsulate a 384 kbps clear channel in RTP. 
The video and other streams would be within this Nx64 container.


> > This may not be of general interest so I am dropping AVT.
>
>Added back, since I'd like input from the wider group.
>
>--
>Colin Perkins
>http://csperkins.org/

--=====================_311185471==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
At 04:11 PM 3/23/2004 +0000, Colin Perkins wrote:<br>
<blockquote type=cite cite>--&gt; Rajesh Kumar
&lt;rkumar999@comcast.net&gt; writes:<br>
&gt; At 03:42 PM 3/23/2004 +0000, Colin Perkins wrote:<br>
&gt; &gt;What would be the use case for having the MIME type registered?
I've not<br>
&gt; &gt;heard a reason why the mechanisms being developed in PWE3
are<br>
&gt; &gt;insufficient.<br>
&gt; <br>
&gt; Say you set up an 384 kbps call via SIP for your video. You do not
use<br>
&gt; the relevant video MIME because what gets put in RTP is nx64 and the
<br>
&gt; video/audio is one step removed.<br>
&gt; <br>
&gt; You may not want to proliferate signaling in your network.<br>
<br>
Again, what is the application scenario? Why the need to signal Nx64
kbps<br>
clearmode, rather than the appropriate video
format?</blockquote><font face="Times New Roman, Times"><br>
Because in this case you would encapsulate a 384 kbps clear channel in
RTP. The video and other streams would be within this Nx64
container.<br>
<br>
<br>
</font><blockquote type=cite cite>&gt; This may not be of general
interest so I am dropping AVT.<br>
<br>
Added back, since I'd like input from the wider group.<br>
<br>
-- <br>
Colin Perkins<br>
<a href="http://csperkins.org/" eudora="autourl">http://csperkins.org/</a>
</blockquote></html>

--=====================_311185471==_.ALT--


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



From exim@www1.ietf.org  Wed Mar 24 04:18:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04870
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 03:32:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B63o2-0006vX-El
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 03:32:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O8WAnP026576
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 03:32:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B63nt-0006ms-Ck; Wed, 24 Mar 2004 03:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oVq-0003LJ-6B
	for avt@optimus.ietf.org; Tue, 23 Mar 2004 11:12:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06672
	for <avt@ietf.org>; Tue, 23 Mar 2004 11:12:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5oVp-0001IG-00
	for avt@ietf.org; Tue, 23 Mar 2004 11:12:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5oUs-0001CG-00
	for avt@ietf.org; Tue, 23 Mar 2004 11:11:22 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5oUB-00011F-00
	for avt@ietf.org; Tue, 23 Mar 2004 11:10:39 -0500
Received: from mangole ([130.209.247.112]:3744 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B5oTe-0000kO-00; Tue, 23 Mar 2004 16:10:06 +0000
Date: Tue, 23 Mar 2004 16:11:09 +0000
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar999@comcast.net>
Cc: yaakov_s@rad.com, rkumar@cisco.com, avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040323161109.5d252831.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
References: <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
	<27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
	<4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
	<4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar999@comcast.net> writes:
> At 03:42 PM 3/23/2004 +0000, Colin Perkins wrote:
> >What would be the use case for having the MIME type registered? I've not
> >heard a reason why the mechanisms being developed in PWE3 are
> >insufficient.
> 
> Say you set up an 384 kbps call via SIP for your video. You do not use
> the relevant video MIME because what gets put in RTP is nx64 and the 
> video/audio is one step removed.
> 
> You may not want to proliferate signaling in your network.

Again, what is the application scenario? Why the need to signal Nx64 kbps
clearmode, rather than the appropriate video format?

> This may not be of general interest so I am dropping AVT.

Added back, since I'd like input from the wider group.

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Wed Mar 24 09:24:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23942
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 09:24:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B69Ic-0007w0-7C
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 09:24:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OEO6Ga030481
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 09:24:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B69IX-0007v2-A7; Wed, 24 Mar 2004 09:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B69Hw-0007tI-OR
	for avt@optimus.ietf.org; Wed, 24 Mar 2004 09:23:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23845
	for <avt@ietf.org>; Wed, 24 Mar 2004 09:23:22 -0500 (EST)
From: jan.vandermeer@philips.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B69Hv-00064L-00
	for avt@ietf.org; Wed, 24 Mar 2004 09:23:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B69H5-0005oQ-00
	for avt@ietf.org; Wed, 24 Mar 2004 09:22:31 -0500
Received: from [61.11.19.149] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B69G5-0005WI-00
	for avt@ietf.org; Wed, 24 Mar 2004 09:21:31 -0500
To: avt@ietf.org
Date: Sun, 21 Mar 2004 01:04:04 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0014_00003E35.0000489E"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B69G5-0005WI-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [AVT] Re: Your picture
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0014_00003E35.0000489E
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Here is the file.

------=_NextPart_000_0014_00003E35.0000489E
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: your_picture.pif, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

------=_NextPart_000_0014_00003E35.0000489E--



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



From exim@www1.ietf.org  Wed Mar 24 11:25:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04327
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 11:25:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BBo-0002CT-HQ
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 11:25:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OGPCEB008456
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 11:25:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BBg-0002B1-PR; Wed, 24 Mar 2004 11:25:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BB1-00025k-J7
	for avt@optimus.ietf.org; Wed, 24 Mar 2004 11:24:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04288
	for <avt@ietf.org>; Wed, 24 Mar 2004 11:24:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6BB0-0000fe-00
	for avt@ietf.org; Wed, 24 Mar 2004 11:24:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6BA6-0000d8-00
	for avt@ietf.org; Wed, 24 Mar 2004 11:23:27 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6B9Z-0000ZM-00
	for avt@ietf.org; Wed, 24 Mar 2004 11:22:53 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2OGMqqY017752
	for <avt@ietf.org>; Wed, 24 Mar 2004 17:22:52 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 24 Mar 2004 17:22:51 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HJS1DJZ6; Wed, 24 Mar 2004 17:22:51 +0100
Message-ID: <4061B5DB.9020705@ericsson.com>
Date: Wed, 24 Mar 2004 17:22:51 +0100
X-Sybari-Trust: 24962acb 2c4885b5 63750edc 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>,
        "Paul E. Jones" <paulej@packetizer.com>
CC: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Mar 2004 16:22:51.0501 (UTC) FILETIME=[40FC31D0:01C411BC]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comments on draft-ietf-avt-rfc2793bis-03.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

Here is my comments from a review of this draft. As this draft was 
intended I will be extra hard on the ID nits, see link on:
http://www.ietf.org/ID.html

1. The whole draft has 15 extra left columns. This can't be there, there 
is a strict requirement on maximum of 72 columns of text.

2. The correct page breaks are missing.

3. The author list contains a blank line.

4. The first line in the left column of the header says AVT Working 
Group. Of historic reasons it should say "Network Working Group"

5. The updated boiler plate according to RFC 3667 and RFC 3668 must be 
used.

6. The RFC editor notes on the first page, are to early. Please move 
them back, at least to after the TOC. But this is also commonly a 
section at the end of the draft.

7. Section 3. I think this section is mixing to many things into one 
brew. I have previously complained on the structure. I think that a 
simple restructuring of the draft would help immensely. I would propose 
the following:
In section 3 define the RTP payload format, RTP header fields, and other 
things directly related to the payload.

Create a new section for on usage of RFC 2198 redundancy. This would 
basically be moving section, 3.4, 3.5, 3.8, 3.9 and parts of 4.3 into 
this new section.

8. Section 3.1: I think this section need to be a bit clearer on what it 
defines. Currently it says:

   "A text conversation RTP packet as specified by the text/t140 payload
    format consists of an RTP header as defined in RFC 3550 [2] followed
    immediately by a block of T.140 data, referred to as a "T140block"
    (see section 3.3).  There are no additional headers specific to this
    payload format."

I would suggest that this is reformulated to:

The text/t140 conversation RTP payload format consists of one and only 
one block of T.140 data, referred to as a "T140block" (see section 3.3). 
There are no additional headers specific to this payload format. The 
fields in the RTP header is set as defined in section 3.7.

The problem with the old text is that it doesn't clearly define what the 
RTP payload was. Instead it defined an RTP packet, which when combined 
with RFC 2198 never exist in the described form. Because then the RTP 
header has its field defined per RFC 2198, and also the payload is per 
RFC 2198. Also due to text later in the discussion on usage of the 
redundancy there is need for a clear understanding of what the RTP 
payload is.

9. Same as 8 but for section 3.2.

10. Section 3.4: "The T140blocks MAY be transmitted redundantly 
according to the payload format defined in RFC 2198 [3]." Please replace 
  "T140blocks" with the "t140 RTP payloads". Reason is that RFC 2198 
sends RTP payloads redundantly.

11. Section 3.6: "Association of RTP streams is dependent on the 
particular session application and is outside the scope of this 
document." Please remove "session".

12. Section 4.2: "With both text/t140 and audio/t140, the loss of the 
last packet of a sequence of packets cannot be detected until the next 
text packet is transmitted." Please replace transmitted, with received. 
The receiver needs to get a new sequence number or T140 block counter to 
be able to determine if things has become lost.

13. Section 4.3:
   "As an alternative (or in addition) to redundancy, Forward Error
    Correction mechanisms MAY be used when transmitting text, as per RFC
    2733 [8] or any other mechanism with the purpose of increasing the
    reliability of text transmission."

This text is redundant with section 3.5. Please gather things in one place.

14. Section 5.
   "To control the character transmission rate, the MIME parameter "cps="
    in the "fmtp" attribute [7] is defined (see section 8 ). It is used
    in SDP with the following syntax: "

The parameter is named "cps" not "cps=" The equal sign is a result of 
the name value pair that is used in fmtp lines.

15. Section 5, last paragraph. The network is another reason why a 
receiver may receive higher character rates. For example buffering that 
is more quickly sent than gathered could give this behaviour.

16. Section 6.3:
   "Below is an example of SDP similar to the above example, but also
    utilizing RFC 2198 to provide redundancy for the text packets:

        m=text 11000 RTP/AVP 98 100
        a=rtpmap:98 t140/1000
        a=rtpmap:100 red/1000
        a=fmtp:100 98/98 "

I think one should point out in this text that one signals only that one 
will use on layer of text redundancy. IF one would use three levels of 
redundancy then the fmtp line would read:
    a=fmtp:100 98/98/98/98

17. Section 11, The SRTP reference is only informative. A normative 
reference is something that one has a normative dependency of in this 
specification.

18. Don't forget to update section 13, and 14.

And please go through the ID-Nits list. I have not checked everything on 
this list, but I expect you to do it.

Cheers



-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Wed Mar 24 12:36:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08219
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 12:36:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CIN-0002SD-I1
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 12:36:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OHa33N009381
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 12:36:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CHN-0002Ip-64; Wed, 24 Mar 2004 12:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CGv-0002Hc-6L
	for avt@optimus.ietf.org; Wed, 24 Mar 2004 12:34:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08178
	for <avt@ietf.org>; Wed, 24 Mar 2004 12:34:19 -0500 (EST)
From: singer@apple.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CGj-0005lO-00
	for avt@ietf.org; Wed, 24 Mar 2004 12:34:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6CFq-0005iV-00
	for avt@ietf.org; Wed, 24 Mar 2004 12:33:26 -0500
Received: from [64.26.134.195] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CFI-0005eg-00
	for avt@ietf.org; Wed, 24 Mar 2004 12:32:52 -0500
To: avt@ietf.org
Date: Wed, 24 Mar 2004 12:32:53 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B6CFI-0005eg-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.8 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [AVT] Re: Re: corrected
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Your document is attached to this mail.

++++ Attachment: No Virus found
++++ Norman AntiVirus - www.norman.com


------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: screensaver.pif, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

------=_NextPart_000_0016----=_NextPart_000_0016--



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



From exim@www1.ietf.org  Wed Mar 24 19:16:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01768
	for <avt-archive@odin.ietf.org>; Wed, 24 Mar 2004 19:16:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6IXY-0001hl-GR
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 19:16:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2P0G8fV006516
	for avt-archive@odin.ietf.org; Wed, 24 Mar 2004 19:16:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6IXR-0001en-OX; Wed, 24 Mar 2004 19:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6IX3-0001XK-0E
	for avt@optimus.ietf.org; Wed, 24 Mar 2004 19:15:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01755
	for <avt@ietf.org>; Wed, 24 Mar 2004 19:15:36 -0500 (EST)
From: david.leon@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6IX1-0006Zk-00
	for avt@ietf.org; Wed, 24 Mar 2004 19:15:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6IW4-0006WN-00
	for avt@ietf.org; Wed, 24 Mar 2004 19:14:36 -0500
Received: from dt162n17.tampabay.rr.com ([24.92.202.23] helo=your-m5d4u9r2uv)
	by ietf-mx with smtp (Exim 4.12)
	id 1B6IVZ-0006T9-00
	for avt@ietf.org; Wed, 24 Mar 2004 19:14:05 -0500
Date: Wed, 24 Mar 2004 19:13:58 -0500
To: avt@ietf.org
Message-ID: <lqufcubllgegdwaacab@nokia.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------xfdsjtvmrfpagnxkykiv"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Subject: [AVT] Weah, hello! :-)
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

----------xfdsjtvmrfpagnxkykiv
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_BAGLE.GEN-1 in file Readme.zip
The uncleanable file is deleted.

---------------------------------------------------------

----------xfdsjtvmrfpagnxkykiv
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 The  access is open !!!

password --  18628

----------xfdsjtvmrfpagnxkykiv
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

Readme.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------xfdsjtvmrfpagnxkykiv--



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



From exim@www1.ietf.org  Thu Mar 25 09:09:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21689
	for <avt-archive@odin.ietf.org>; Thu, 25 Mar 2004 09:09:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VY0-0006oy-AI
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 09:09:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PE9Swe026194
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 09:09:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VXU-0006aO-Nc; Thu, 25 Mar 2004 09:08:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6SjD-00033D-31
	for avt@optimus.ietf.org; Thu, 25 Mar 2004 06:08:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14931
	for <avt@ietf.org>; Thu, 25 Mar 2004 06:08:46 -0500 (EST)
From: philkerr@elec.gla.ac.uk
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Sj9-0003rC-00
	for avt@ietf.org; Thu, 25 Mar 2004 06:08:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6SiD-0003mc-00
	for avt@ietf.org; Thu, 25 Mar 2004 06:07:49 -0500
Received: from [213.231.81.55] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1B6ShJ-0003i4-00
	for avt@ietf.org; Thu, 25 Mar 2004 06:06:53 -0500
To: avt@ietf.org
Date: Thu, 25 Mar 2004 11:06:50 +0000
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="56474878"
Message-Id: <E1B6ShJ-0003i4-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME autolearn=no version=2.60
Subject: [AVT] warning
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

--56474878
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

here is the document.

--56474878
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: website.exe, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

--56474878--


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



From exim@www1.ietf.org  Thu Mar 25 09:11:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22101
	for <avt-archive@odin.ietf.org>; Thu, 25 Mar 2004 09:11:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VZU-0007j2-TW
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 09:11:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PEAxfW029621
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 09:10:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VZL-0007d3-Fx; Thu, 25 Mar 2004 09:10:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6UHC-00016B-Lq
	for avt@optimus.ietf.org; Thu, 25 Mar 2004 07:48:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18137
	for <avt@ietf.org>; Thu, 25 Mar 2004 07:48:00 -0500 (EST)
From: philkerr@elec.gla.ac.uk
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6UHB-0005h4-00
	for avt@ietf.org; Thu, 25 Mar 2004 07:48:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6UGL-0005bQ-00
	for avt@ietf.org; Thu, 25 Mar 2004 07:47:09 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6UFU-0005Vk-00
	for avt@ietf.org; Thu, 25 Mar 2004 07:46:16 -0500
Received: from 152.red-217-126-240.pooles.rima-tde.net ([217.126.240.152] helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6UF0-00042G-Q2
	for avt@ietf.org; Thu, 25 Mar 2004 07:45:50 -0500
To: avt@ietf.org
Date: Thu, 25 Mar 2004 13:45:28 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B6UF0-00042G-Q2@mx2.foretec.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.4 required=5.0 tests=MIME_BOUND_NEXTPART,
	MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
Subject: [AVT] Re: Re: data
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.P in file document.txt                                                                   .exe (in data.zip)
The uncleanable file is deleted.

---------------------------------------------------------

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Please confirm the document.


------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

data.zip is removed from here because it contains a virus.

---------------------------------------------------------
------=_NextPart_000_0016----=_NextPart_000_0016--




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



From exim@www1.ietf.org  Thu Mar 25 09:56:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26185
	for <avt-archive@odin.ietf.org>; Thu, 25 Mar 2004 09:56:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6WHK-0007Pb-Gg
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 09:56:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PEuIop028489
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 09:56:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6WHF-0007Nn-7m; Thu, 25 Mar 2004 09:56:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6WGT-0007Jf-HY
	for avt@optimus.ietf.org; Thu, 25 Mar 2004 09:55:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25993
	for <avt@ietf.org>; Thu, 25 Mar 2004 09:55:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6WGR-0003tS-00
	for avt@ietf.org; Thu, 25 Mar 2004 09:55:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6WFE-0003kY-00
	for avt@ietf.org; Thu, 25 Mar 2004 09:54:09 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6WES-0003fS-00
	for avt@ietf.org; Thu, 25 Mar 2004 09:53:20 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2PErJqY015304
	for <avt@ietf.org>; Thu, 25 Mar 2004 15:53:19 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 25 Mar 2004 15:53:17 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HQ46882L; Thu, 25 Mar 2004 15:53:18 +0100
Message-ID: <4062F25E.7040102@ericsson.com>
Date: Thu, 25 Mar 2004 15:53:18 +0100
X-Sybari-Trust: f7c98d4d 2c4885b5 ae329ef6 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Mar 2004 14:53:17.0701 (UTC) FILETIME=[E85D2350:01C41278]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Issue with Offer/Answer in H.264 RTP payload format
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

During the work to finalize a version of the H.264 RTP payload format 
draft we have encountered an issue that we would like to have feedback 
on. However as this is mostly related to MMUSIC, we have posted the mail 
describing the issue on the MMUSIC mailing list. It can be read by non 
subscribers in the following message in the list archive:

http://www1.ietf.org/mail-archive/working-groups/mmusic/current/msg02377.html

Please send comments on this to the MMUSIC list.


Best Regards

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Thu Mar 25 11:26:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05095
	for <avt-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:26:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XgH-00007G-M2
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 11:26:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGQ9OB000445
	for avt-archive@odin.ietf.org; Thu, 25 Mar 2004 11:26:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xg9-00006Z-9B; Thu, 25 Mar 2004 11:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XfZ-00005L-CN
	for avt@optimus.ietf.org; Thu, 25 Mar 2004 11:25:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05011
	for <avt@ietf.org>; Thu, 25 Mar 2004 11:25:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XfX-0004qs-00
	for avt@ietf.org; Thu, 25 Mar 2004 11:25:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xef-0004oL-00
	for avt@ietf.org; Thu, 25 Mar 2004 11:24:29 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xe0-0004m6-00
	for avt@ietf.org; Thu, 25 Mar 2004 11:23:49 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2PGNlYG009447
	for <avt@ietf.org>; Thu, 25 Mar 2004 17:23:47 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 25 Mar 2004 17:23:47 +0100
Received: from ericsson.com (sealwp01-23.sw.ericsson.se [153.88.142.23]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HQ469NY6; Thu, 25 Mar 2004 17:03:20 +0100
Message-ID: <406302C7.2050707@ericsson.com>
Date: Thu, 25 Mar 2004 17:03:19 +0100
X-Sybari-Trust: 084d4e50 2c4885b5 ae329ef6 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Mar 2004 16:23:47.0045 (UTC) FILETIME=[8C814950:01C41285]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] WG Last Call: draft-ietf-avt-text-red-02.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This is to announce a working group last call on the "Registration of 
the text/red MIME Sub-Type" (draft-ietf-avt-text-red-02.txt).
http://www.ietf.org/internet-drafts/draft-ietf-avt-text-red-02.txt

Please send any final comments on this draft to the mailing list by
Thursday the 8th April 2004.
At that time, we will consider if it is appropriate to request
publication of this draft as a proposed standard RFC.

Note that this draft will not be advanced until we receive at least one
valid review from someone not directly involved with production of the
draft (i.e., not an author or a major contributor).

Regards

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Fri Mar 26 07:47:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17277
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 07:47:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6qk0-0001Ra-J7
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 07:47:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QClGCI005540
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 07:47:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6qjl-0001Pd-Rw; Fri, 26 Mar 2004 07:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6qh5-0001Gg-VD
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 07:44:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17114
	for <avt@ietf.org>; Fri, 26 Mar 2004 07:44:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6qh5-0005Ye-00
	for avt@ietf.org; Fri, 26 Mar 2004 07:44:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6qg6-0005Rs-00
	for avt@ietf.org; Fri, 26 Mar 2004 07:43:17 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6qfk-0005MF-00
	for avt@ietf.org; Fri, 26 Mar 2004 07:42:52 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2QCgnYG003066
	for <avt@ietf.org>; Fri, 26 Mar 2004 13:42:50 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 26 Mar 2004 13:42:49 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HV03HWLP; Fri, 26 Mar 2004 13:42:49 +0100
Message-ID: <40642549.2090001@ericsson.com>
Date: Fri, 26 Mar 2004 13:42:49 +0100
X-Sybari-Trust: 23797e41 272a6e05 0f59bdcd 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
CC: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/mixed;
 boundary="------------000205000204040202020908"
X-OriginalArrivalTime: 26 Mar 2004 12:42:49.0498 (UTC) FILETIME=[D8CDE7A0:01C4132F]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_QP_NO_CHARSET 
	autolearn=no version=2.60
Subject: [AVT] AVT WG Minutes from IEFT 59 in Seoul
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.
--------------000205000204040202020908
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi AVTers,

Here is a preliminary version of the AVT minutes. Any comments on these 
must be directed to the chairs or the list before the 1st of April as 
they needs to be submitted to the proceedings.


Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


--------------000205000204040202020908
Content-Type: text/plain;
 name="IETF59-AVT-minutes.txt"
Content-Disposition: inline;
 filename="IETF59-AVT-minutes.txt"
X-MIME-Autoconverted: from 8bit to quoted-printable by penguin-ext.wise.edt.ericsson.se id i2QCgnYG003066
Content-Transfer-Encoding: quoted-printable

Audio/Video Transport Working Group Minutes

Reported by Magnus Westerlund and Colin Perkins

   The AVT working group had two sessions during the 59th IETF meeting, t=
he
   first on Tuesday morning, and the second on Wednesday afternoon. Durin=
g
   these sessions the WG discussed RTP payload formats for different medi=
a
   codecs, RTCP Extensions for SSM, header compression requirements for
   MPLS, a NOOP RTP payload format with RTCP request hint, and a new RTP
   profile for congestion control with TFRC.=20


Introduction and Status Update

   The meeting began with a status update from the chairs. Two RFCs have
   been published since the last meeting (RFC 3611 and RFC 3640) and one
   draft (draft-ietf-avt-srtp-09.txt) is in the RFC editor's queue. Five=20
   AVT drafts that have been reviewed by the IESG and need to be updated
   to address the review comments:

   	draft-ietf-avt-rtcp-feedback-08.txt
   	draft-burmeister-avt-rtcp-feedback-sim-05.txt
	draft-ietf-avt-rtp-ilbc-04.txt=20
	draft-ietf-avt-ilbc-codec-04.txt=20
	draft-ietf-avt-rtp- clearmode-04.txt

   A non-working group draft that has been reviewed by the group
   (draft-jones-avt-audio-t38-03.txt) is also in IESG review, however the
   ITU has make changes to the underlying reference, and these need to be
   reflected in the draft before it can advance.

   There are two drafts awaiting AD review (draft-ietf-avt-uncomp-video-0=
6.txt
   and draft-ietf-avt-rtp-retransmission-09.txt) and and one in IETF Last=
 Call
   (draft-ietf-avt-tcrtp-07.txt). AVT has 24 working group drafts and 15=20
   individual drafts that are either being reviewed by AVT, or targetted=20
   to become AVT WG documents.

   Roni Even asked if the RFC number for SRTP has been assigned, since th=
e
   ITU wishes to reference it.  The answer is that it is possible in thes=
e
   cases to get the RFC number, and such requests should be sent to the W=
G
   chairs along with motivation for pre-assignment. The earlier in regard=
s
   to any deadline such requests are expressed, the easier it is to fulfi=
l
   them.=20

   Magnus Westerlund reported on the status of several drafts that were n=
ot
   otherwise discussed:

   - draft-ietf-avt-rfc2833bis-04.txt has received major updates for clar=
ity=20
     and to add new events, and needs review.

   - draft-ietf-avt-ulp-09.txt has been updated to address prior comments=
,
     and needs review. A third-party IPR notice has been received for RFC
     2733 and this draft. The IPR holder is Lucent, who has a general IPR
     statement (see http://www.ietf.org/ipr.html). Clarification on the
     status of the IPR relating to these drafts has been sought, and will
     be made available once received.

   - draft-ietf-avt-uxp-06.txt is awaiting an update to address previous
     comments.

   - draft-ietf-avt-mpeg1and2-mod-00.txt has not been updated. It needs
     review to be able to progress towards Draft Standard.

   - draft-ietf-avt-rtp-dsr-codecs-00.txt is the result of merging the
     three separate DSR drafts. Review is needed, to see if this draft=20
     is ready for WG Last Call.

   - draft-ietf-avt-profile-savpf-00.txt needs review by the group, and a=
n
     update after review comments have been given. It is hoped that it wi=
ll
     be ready for WG Last Call after the update.=20

   - draft-ietf-avt-rfc3119bis-02.txt has been updated and is planned to=20
     go for draft standard. See also interoperability draft.=20

   - A new version of draft-ietf-avt-rtp-h264-04.txt was submitted before
     the meeting, but since then the need for some small updates has been
     noticed. After the update it is expected to be ready for working gro=
up
     last call.

   - draft-ietf-avt-rtp-jpeg2000-04.txt needs review. Please comment to t=
he
     mailing list.=20

   - draft-kerr-avt-vorbis-rtp-03.txt needs review. Please comment to the
     mailing list.=20

   - draft-herlein-speex-rtp-profile-01 has expired, and needs to be upda=
ted=20
     if work is desired to progress.=20

   - draft-ramalho-rgl-rtpformat-02.txt has expired, and also needs to be
     updated. Comments were provided, to be reflected in the update.

   - draft-chen-rtp-bv-02.txt needs review. The authors have requested th=
at
     this draft become an AVT work item: comments are solicited and shoul=
d
     be sent to the mailing list.
    =20
   - A number of comments on draft-ahmadi-avt-rtp-vmr-wb-00.txt were give=
n=20
     during the previous IETF meeting, these need to be addressed in orde=
r
     to progress the draft.=20

   - draft-ash-avt-ecrtp-over-mpls-protocol-00.txt is an initial proposal=
=20
     to address the requirements for MPLS header compression identified i=
n=20
     draft-ash-avt-ecrtp-over-mpls-reqs-01.txt. This cannot progress unti=
l
     requirements and charter discussion have been completed.

   - draft-clark-avt-rtpmibv2-00.txt  needs an update to address comments
     given on the draft. Author intends to do this in the near future.

   - draft-finlayson-avt-mpa-robust-interoperability-00.txt is an initial=
=20
     submission, on what needs to be tested to verify interoperability of
     the Robust MP3 payload format, in order to go to Draft Standard.=20

   - draft-perkins-avt-rtp-reactive-fec-00.txt was a proposal on use of
     RFC 2733 as a retransmission format, intended as an alternative to=20
     the RTP payload format for retransmission. However this proposal is=20
     IPR encumbered through RFC 2733.

   - draft-tseng-avt-rtcp-streaming-extens-00.txt received a number of =20
     comments before and during the last IETF meeting. These need to be
     addressed if the work is to proceed.

   Finally, the chairs asked for comments on the previously announced
   intent to advance the RTP specification and Profile for Audio/Video
   Conferences with Minimal Control (RFC 3550 and 3551) to Full Standard,
   without changes. No objections was made.=20


Updates on behalf of author

   On behalf of John Lazarro, Colin Perkins outlined the status of the RT=
P
   payload format for MIDI (draft-ietf-avt-midi-rtp-01.txt) and associate=
d
   guidelines (draft-ietf-avt-midi-guidelines-01.txt). The current versio=
ns=20
   are given as candidate for WG last call, to be reviewed by MMA and the
   working group. Please review and send comments to list.

   Colin also noted that the RTP framing for connection oriented transpor=
t
   (draft-ietf-avt-rtp-framing-contrans-00.txt) is awaiting resolution of
   the comedia draft in MMUSIC, and accordingly has not been updated.

   Unfortunately an update of Andrea Basso's Requirements for transport o=
f
   video control commands (draft-basso-avt-videoconreq-00.txt) did not me=
et
   the draft deadlines. An update will be submitted after the meeting. Th=
is
   will clarify the terminology, cut down the command list to those used =
in
   the IETF. Please review this when it becomes available.


RTP payload format for AMR-WB+ audio codec=09

   Ari Lakaniemi discussed draft-sjoberg-avt-rtp-amrwbplus-01.txt. This
   revision clarifies interoperability scenarios with AMR-WB, specifies
   how to signal mono and stereo sessions in SDP, and adds offer/answer
   considerations recommending that one declares also the non-optional
   parts when using optional features of the AMR-WB+ codec and payload
   format.=20

   The remaining issue is to track the codec development as it is being
   finalized.  It was noted that the AMR-WB+ codec has been selected as=20
   an optional codec to be included in the PSS and MSS services of 3GPP
   with plans to finalize the specification in May for a 3GPP release 6
   deadline that has been postponed to at least June.

   Colin Perkins asked why the Code Mode Request (CMR) field is not used?
   This is primarily because AMR-WB+ is not intended for conversational
   use, and so is not expected to be used with gateways that might cause
   rapid mode requests to be transported from the receiver to the sender.
   Colin asked for clarification of the use cases, and noted that the=20
   draft should also consider if it's appropriate to use the CMR fields=20
   as a hint for congestion control.

   Dave Lindberg asked if there is a reason for not considering AMR-WB+ f=
or
   conversational use? The answer is that the AMR-WB+ codec has a longer
   algorithmic delay then AMR-WB.

   The opinion of the room was that the AMR-WB+ payload format should be
   accepted as an AVT work item.


Introduction of ATRAC family payload format.

   Matthew Romaine discussed draft-hatanaka-avt-rtp-atrac-family-00.txt, =
a
   new RTP payload format for all ATRAC audio codecs. The previous attemp=
t
   for an RTP payload format for only ATRAC-X has been abandoned due to i=
ts
   complexity, and to enable a format that encompass all codec versions.
   The new format is intended to be much simpler.

   Magnus Westerlund asked if the FrOff field is approriate, since change=
s
   in the number of redundant frames will change the buffering needed, an=
d
   may force a receiver to adapt its playout delay. Colin Perkins remarke=
d
   that such changes are commonly done before a talk spurt, so the playou=
t=20
   delay can easily be various. Magnus' concern about this is that for an
   audio codec, a lot of the material is continuous without talkspurt-lik=
e=20
   behaviour, preventing in-band changes of the redundancy offset may be
   appropriate. Colin remarked that there exists a need to vary the frame
   offset to adapt to network behaviour anyway, so this shouldn't be a=20
   significant problem (RFC 2198 allows such changes in redundancy offset
   also). =20

   There have also been comments about the MIME types for the payload
   format. The proposal is to have one for each codec version. There are =
a
   few required parameters, for example a channels parameter that contain=
s
   different mappings of the channel, not number of channels.

   Regarding the SDP initialization, Magnus Westerlund noted that only th=
e
   sample rate/channels can go into the "a=3Drtpmap" SDP attribute. All o=
ther
   parameters need to go into "a=3Dfmtp" line.=20

   The draft has made significant progress in regards to previous version=
s.


3GPP Timed Text

   Jose Rey presented draft-rey-avt-3gpp-timed-text-02.txt.  The draft ha=
s
   been restructured and simplified by removal of advanced fragmentation =
of
   modifiers. Unless all modifiers fragments arrive, modifiers can't be
   applied. The structure has also be changed to be compatible with RFC
   3640.

   Colin Perkins asked if it is possible to detect the number of characte=
rs
   that have been lost within a fragmented block? This is not a possible,
   however no one has raised problems with this. Colin requested that the
   draft be explicit about the limitation, to be certain it is handled
   correctly, since the handling differs from other real time text format=
s.
   Issues raised by Magnus Westerlund about the possibility to always hav=
e
   a length field were presented, but there were no additional comments.

   Another issue is the ability to repeat modifier fragments and sample
   descriptions: it was asked if this feature should be retained, or
   disallowed in favour of external methods like FEC or retransmission? =20
   No suggestions were made.

   Should it be mandatory to support sample description both in-band and
   out-of-band? Colin commented that if one relies on inband signalling,
   one must measure the transport characteristics to provide appropriate
   reliability and specify what a receiver does if a sample descriptor is
   not received.  Colin stressed that if one allows inband signalling of
   sample descriptors at all one needs to address these issues. (Name?) o=
f
   University of Korea asked why not making inband mandatory. The issue i=
s
   still that the problems with inband would need to be resolved.=20

   Colin commented that the draft is written assuming data is sourced fro=
m
   a file. As it is possible to generate text on the fly, the draft shoul=
d
   be updated to in language reflect that.=20

   The authors hope this work can be completed to meet the 3GPP release 6
   deadline, which may be as early as June 2004. The chairs noted that th=
e
   draft is still far from complete, and that work will have to proceed=20
   rapidly if this deadline is to be met.

   The chairs asked if this draft should be taken as a AVT WG item?  The
   sense of the room was that were were few supporters, but none against.
   Hence, unless there are objections from the list, this will become an
   AVT work item.


Payload format for Text Conversation (RFC2793bis)

   Gunnar Hellstr=F6m presented draft-ietf-avt-rfc2793bis-02.txt, noting =
that
   this version is believed to address all comments received to date. Mag=
nus=20
   Westerlund raised that one issue that has not been addressed: when usi=
ng
   the "audio/t140" format and switching between text and speech, it is
   possible for a packet to be lost, and for the receiver to be unable to
   determine if that was a text or a speech packet. This is likely not a
   problem, but should be better documented. Magnus also noted that the
   document is also missing a section mapping the MIME parameters onto SD=
P,
   and an offer-answer considerations section.=20

   Gunnar continued with a presentation of draft-ietf-avt-text-red-01.txt.
   Magnus raised a comment that the PT MIME parameter should reflect how =
it
   is actually defined in RFC 2198. Colin was of the opinion that it shou=
ld
   say the same thing as the other media versions of RED, see RFC 3555, a=
nd
   any clarifications should be made when RFC 2198 is updated.

   ITU study group 16 has need for these documents by November. In order =
to
   meet this deadline, updated drafts should be produced, ready for worki=
ng
   group last call by early April 2004.=20


H.261 and H.263 payload parameters

   Roni Even discussed the RTP updated payload formats for H.261 and H.26=
3:
   draft-ietf-avt-rfc2032-bis-00.txt and draft-ietf-avt-rfc2429-bis-00.tx=
t.
   These add new codec parameters needed, for example, by video conferenc=
e
   and also clarify a number of issues with the older RFCs.=20

   An issue raised is how the Annex and profile/level parameters interact=
,
   for example which of them overrides the other. The proposal is to not
   use them together, to avoid this problem.

   Another issue was that only parameters that are known to be used have
   been included in these drafts. Input from implementors is solicited,
   asking if the parameters are sufficient or if any are missing.=20

   The author list will also need to be trimmed to avoid problems with th=
e
   current guidelines on number of authors. Colin commented that this is
   something the contributors will need to agree between themselves on.
   Magnus noted that correct contact information and the ability to revie=
w
   and sign off on the draft during the final "authors 48 hours" period a=
re
   needed by anyone listed as an author.

   Colin commented that there is need for editorial pass, to check where
   the RFC 2119 normative language should be used.=20

   There is interest to implement these drafts by different companies, an=
d
   therefore this work should be moved forward. After another update it i=
s
   hoped that WG last call will be possible.=20


Verifying the media path using RTP No-Op & Preconditions=20

   Flemming Andreasen discussed draft-wing-avt-rtp-noop-00.txt and its
   relation to draft-andreasen-mmusic-connectivityprecondition-00.txt.=20
   This work was also discussed during the MMUSIC session, however mostly
   in regards to signalling and usage. The presentation in AVT was more
   directed towards the RTP related issues.=20

   It was noted that Cisco claims IPR in relation to this payload format
   and it's application, and are willing to license this under reasonable
   and non-discriminatory terms. Colin Perkins asked for elaboration on t=
he
   IPR. Flemming made it clear that the patent application is applicable =
to
   the RTP payload format, separate from its use with the connectivity=20
   preconditions.

   The payload format is intended to be used to open pinholes in NATs and
   firewalls, to verify connectivity and quality over a media path and to
   keep alive NAT and firewall bindings. As discussed in MMUSIC, there is
   some overlap between this proposal, and STUN and ICE.

   Roni Even asked why only the audio/noop MIME type is listed? The answe=
r
   is that there is no reason for not having it for all media types in us=
e.
   The draft is simply missing registration of all the media types that a=
re
   appropriate.

   Dan Romascanu noted that it is not very clear from the draft how you c=
an
   determine the actual media path characteristics through the use of RTC=
P,
   and how to separate the reception quality reports for the NOOP traffic
   from other media traffic. Flemming noted that the RTP SSRC can be used
   to separate traffic, and promised to work on the text, clarifying this=
.=20

   Magnus Westerlund and Colin Perkins noted that the draft is unclear on
   the interactions between its immediate feedback request and the usual
   RTCP timers (in both the standard A/V profile and in the RTCP feedback
   profile). Clarification was requested.

   Jonathan Rosenberg was doubtful of the need to request immediate RTCP
   reports. He supported the functionality of an RTP payload format that =
is
   discarded, to keep NAT bindings alive when media is on hold, but asked
   the group to consider the need for requesting immediate RTCP reports a=
nd
   to clarify the problem and requirements before jumping into the soluti=
on
   space.  =20

   Jonathan also noted, as he did in the MMUSIC session, that ICE and STU=
N
   would still be needed for NAT traversal, and so can't be replaced with
   this mechanism.=20

   Roni Even also commented that the use case for checking the MTU might
   need feedback, however the QoS diagnostic does look like a different
   issue.=20

   Colin Perkins concluded that the draft must be updated and clarified o=
n
   use cases, and what problems it solves.


RTCP Extensions for SSM Sessions with Unicast Feedback=20

   J=F6rg Ott discussed draft-ietf-avt-rtcpssm-06.txt. This has been upda=
ted
   to address the behaviour of distribution sources and to clarify how th=
e
   two ways of specifying RTCP receiver report bandwidth interact. Also,
   the security considerations and IANA considerations have received some
   significant updates. Colin Perkins commented that the security section
   now looks much better, and solicited review from the working group.=20

   A remaining issue is to specify how sender reports unicast to the
   distribution source are to be forwarded, removing the need for the
   number of sender report block. Otherwise, while there are a few
   previously discussed issues that still need to be included, the
   draft is believed to be almost complete.=20


Requirements for ECRTP over MPLS

   Jerry Ash discussed draft-ash-avt-ecrtp-over-mpls-reqs-01.txt, which h=
as
   been updated to address comments raised in the last meeting and on the
   mailing list. Lars-Erik Johansson, commented that draft has been
   significantly improved and supported it becoming an working group draf=
t.
   However, he noted that it would be good if the draft could be enhanced
   to better explain why ECRTP is the right choice, and explain the issue=
s
   with using CRTP or ROHC as an alternative. Kristofer Sandlund commente=
d
   that ECRTP is not that strong against reordering, and that ROHC has
   better compression efficiency. It would also be better if the draft
   explained what order of reordering that can be expected. Jerry answere=
d
   that it is not intended to exclude ROHC from future usage. Colin Perki=
ns
   clarified that AVT does not have the necessary experience to specify
   ROHC over MPLS, however the framework must ensure that this work can b=
e
   done.=20

   Allison Mankin asked if ROHC really has become resistant to reordering.
   Lars-Erik answered that currently no, however this has been discussed
   and the solution is known. However as there has been no need previousl=
y
   the solution has not been written up. Lars-Erik also commented that
   ECRTP needs to use lower layers to identify the packet type, which ROH=
C
   handles internally.=20

   The draft was requested to become an AVT WG item. This seems acceptabl=
e
   with the current maturity of the draft, and was taken as an assumption.
   It will be expected that an updated draft be produced to address the
   comments received here. This will also need expert review from the MPL=
S
   community.=20

   Jerry has also produced an initial draft proposing a protocol to addre=
ss
   the requirements (draft-ash-avt-ecrtp-over-mpls-protocol-00.txt). Coli=
n
   commented that AVT is an appropriate temporary home this draft, until =
we
   figure out the proper home(s) for it. However the draft would benefit =
by
   taking a step backwards, to better explain the rationale for the propo=
sed=20
   solution.=20

   Allison Mankin, asked what the reason for having SIP calls in the draf=
t.
   Jerry answered that it was put in there to illustrate the how VoIP and
   the RSVP extension would fit together. However there are no strong
   reasons for keeping it in the draft, and it can easily be moved or
   removed. Allison also stated state there definitely seems to be reason=
s
   for keeping the work within AVT for the moment.=20


RTP Profile for TCP Friendly Rate Control

   Ladan Gharai presented draft-gharai-avt-tfrc-profile-00.txt, a proposa=
l
   for using TFRC based congestion control with RTP using RTCP feedback.
   Her presentation included in a short introduction to TFRC, outlining t=
he
   new information that needs to transported in RTP and RTCP to support t=
he
   TFRC algorithm. The initial proposal extends both RTP and RTCP, and
   therefore needs to be new RTP profile.=20

   Technical issues that exist are:=20

   - The size of RTCP feedback, since RTCP packets will typically be at
     least 80 octets.

   - The size of the profile specific additions to the RTP header. The
     current proposal adds 8 octets to the RTP header.

   - The RTCP feedback rate, as TFRC either sends feedback once per sent
     packet, or once per RTT, this can be significant bit-rate. Thus the
     normal RTCP bit-rate restrictions will not provide sufficient bit-ra=
te=20
     for a lot of applications.=20

   It is also important to clarify the relation to the DCCP protocol. It =
is
   clear that DCCP provides more functionality than an RTP profile for TF=
RC
   congestion control, and that that functionality is useful and benefici=
al
   to developers. However, a new RTP profile will be easier to deploy, as
   it only involves application-level changes. An RTP profile for TFRC wi=
ll=20
   allow application developers to experiment and gain experience with TF=
RC
   congestion control in the short term, with the hope of easing migratio=
n
   to DCCP in the longer term.=20

   Anders Klemets asked how the use of AVPF to request retransmission may
   affect the algorithm? It is clear that retransmission needs to also be=
=20
   congestion controlled, and that the interactions with the changed timi=
ng
   rules of AVPF will definitely need to be considered.=20

   A second question was if the TFRC algorithm implies a fixed packet siz=
e.
   Mark Handley answered that TFRC needs to know what the packet size is,
   it can be varied during a session. Sally Floyd also commented that she
   is planning to work on TFRC-PS, a variant of TFRC for applications tha=
t
   don't want to change their send rate, but instead vary their packet
   size.=20

   The big question is: does creating an RTP profile for TFRC make sense?

   Brian Rosen commented that the draft would need a strong applicability
   statement explaining the effects TFRC will have on a media stream, and
   pointed to the long discussion on the AVT and DCCP mailing lists after
   the last IETF meeting.

   Mark Handley agreed that creating an RTP profile for TFRC is a good
   idea, and that it complements DCCP. Where DCCP is a long term solution
   with more benefits, a RTP profile would be a good short term solution.=
=20

   Joerg Ott also thinks it is a good idea. However he raised concern abo=
ut
   the number profiles, and the interaction between a TFRC profile and th=
e
   current profiles. Colin commented that this is definitely an open issu=
e
   that will need to be further considered.

   Aaron Falk requested that if this work goes forward, that any findings
   about the behaviour should be given as input to the DCCP working group=
,
   and especially to their user guide document. Tom Phelan also commented
   that the reverse is also true. For example the discussion in DCCP has
   already resulted in changes in CCID 3. This work should be tracked als=
o
   by an RTP profile.

   Mark Handley commented that with the current proposal for RTP header
   changes, this profile over UDP will actually use 32-bits more than RTP
   over DCCP. In DCCP this has been achieved through the usage of 4 free
   bits in the DCCP header. There should be made some effort for finding =
a
   better way to encode the necessary information into the RTP header.=20

   Geetha Srikantan was concerned with the fact that if an ISP is policin=
g
   the UDP flows, how is a TFRC controlled UDP flow separated from other
   non-congestion controlled flows? It should at least be clarified what
   the assumptions are, and what can be expected.=20

   Allison Mankin commented with a point she borrowed from Mark Handley: =
it
   is difficult to get the implementation of congestion control correct,
   with a rather large risk that there are bugs within an implementation.
   DCCP will definitely be easier for an application, since it can be
   implemented above a known-good congestion control implementation.=20

   Colin Perkins concluded that there is certainly interest for performin=
g
   this work. The WG will need re-chartering to take this aboard. This ca=
n
   be considered while the draft is updated to address comments and clari=
fy
   the motivation for the work.

				  - * -=20


--------------000205000204040202020908--


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



From exim@www1.ietf.org  Fri Mar 26 07:47:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17282
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 07:47:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6qk0-0001RZ-Ir
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 07:47:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QClGsE005539
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 07:47:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6qjl-0001PS-5w; Fri, 26 Mar 2004 07:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6pwY-0006Xr-6M
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 06:56:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14950
	for <avt@ietf.org>; Fri, 26 Mar 2004 06:56:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6pwT-0000p5-00
	for avt@ietf.org; Fri, 26 Mar 2004 06:56:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6pvb-0000jg-00
	for avt@ietf.org; Fri, 26 Mar 2004 06:55:11 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6pux-0000cj-00
	for avt@ietf.org; Fri, 26 Mar 2004 06:54:31 -0500
Received: from pub-243.nesc.ed.ac.uk ([129.215.30.243]:2339 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B6puK-0007Ri-00; Fri, 26 Mar 2004 11:53:52 +0000
Date: Fri, 26 Mar 2004 11:02:38 +0000
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar@cisco.com>
Cc: rkumar999@comcast.net, yaakov_s@rad.com, avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040326110238.5e8aeba2.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
References: <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
	<4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
	<27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
	<4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
	<4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
	<4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar@cisco.com> writes:
> At 04:11 PM 3/23/2004 +0000, Colin Perkins wrote:
> >--> Rajesh Kumar <rkumar999@comcast.net> writes:
> > > At 03:42 PM 3/23/2004 +0000, Colin Perkins wrote:
> > > >What would be the use case for having the MIME type registered? I've
> > > >not heard a reason why the mechanisms being developed in PWE3 are
> > > >insufficient.
> > >
> > > Say you set up an 384 kbps call via SIP for your video. You do not
> > > use the relevant video MIME because what gets put in RTP is nx64 and
> > > the video/audio is one step removed.
> > >
> > > You may not want to proliferate signaling in your network.
> >
> >Again, what is the application scenario? Why the need to signal Nx64
> >kbps clearmode, rather than the appropriate video format?
> 
> Because in this case you would encapsulate a 384 kbps clear channel in
> RTP. The video and other streams would be within this Nx64 container.

Right - you have a pseudo-wire emulation, running multiple streams within
the pseudo-wire. This would seem to be a typical application for the PWE3
mechanisms, rather than something AVT should consider. 

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Fri Mar 26 08:05:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17982
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 08:05:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6r1D-0002SC-Px
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 08:05:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QD53ns009428
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 08:05:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6r1C-0002RR-22; Fri, 26 Mar 2004 08:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6r0P-0002Pr-26
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 08:04:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17931
	for <avt@ietf.org>; Fri, 26 Mar 2004 08:04:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6r0O-0007Yh-00
	for avt@ietf.org; Fri, 26 Mar 2004 08:04:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6qzP-0007ST-00
	for avt@ietf.org; Fri, 26 Mar 2004 08:03:12 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6qyi-0007MV-00
	for avt@ietf.org; Fri, 26 Mar 2004 08:02:28 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2QD2RYG007904
	for <avt@ietf.org>; Fri, 26 Mar 2004 14:02:27 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 26 Mar 2004 14:02:27 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HV03H6WS; Fri, 26 Mar 2004 14:02:27 +0100
Message-ID: <406429E2.8000001@ericsson.com>
Date: Fri, 26 Mar 2004 14:02:26 +0100
X-Sybari-Trust: bf2e3d15 272a6e05 0f59bdcd 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
CC: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] WG Last Call: draft-ietf-avt-text-red-02.txt
References: <406302C7.2050707@ericsson.com>
In-Reply-To: <406302C7.2050707@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Mar 2004 13:02:27.0294 (UTC) FILETIME=[96D34FE0:01C41332]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Paul,

When I reviewed for the WG last call I found a few minor issues which 
will need to be corrected in an update after the WG last call. However 
they where so minor that I don't see how they affect the WG last call.

Also my comments does not count to the at least one reviewer rule. It is 
the task of the author to ensure that at least one person do a review.

Comments:

1. First page, left side of the header: It should read "Network Working 
Group" of historic reasons rather than "AVT Working Group".

2. In the "status of this memo" I don't think the intention is for the 
author to remove the "(we)" that are part of the boilerplate text, even 
when you are a single person. It is more important that it is the right 
text, than correctly correspond to if there is a single or more 
authors/contributors.

3. The RFC editor note should be moved to somewhere after the abstract.

Cheers

Magnus


Magnus Westerlund wrote:

> This is to announce a working group last call on the "Registration of 
> the text/red MIME Sub-Type" (draft-ietf-avt-text-red-02.txt).
> http://www.ietf.org/internet-drafts/draft-ietf-avt-text-red-02.txt
> 
> Please send any final comments on this draft to the mailing list by
> Thursday the 8th April 2004.
> At that time, we will consider if it is appropriate to request
> publication of this draft as a proposed standard RFC.
> 
> Note that this draft will not be advanced until we receive at least one
> valid review from someone not directly involved with production of the
> draft (i.e., not an author or a major contributor).
> 
> Regards
> 
> Magnus Westerlund
> 
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> 
> 
> 
> This communication is confidential and intended solely for the 
> addressee(s). Any unauthorized review, use, disclosure or distribution 
> is prohibited. If you believe this message has been sent to you in 
> error, please notify the sender by replying to this transmission and 
> delete the message without disclosing it. Thank you.
> 
> E-mail including attachments is susceptible to data corruption, 
> interruption, unauthorized amendment, tampering and viruses, and we only 
> send and receive e-mails on the basis that we are not liable for any 
> such corruption, interception, amendment, tampering or viruses or any 
> consequences thereof.
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Fri Mar 26 11:44:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00707
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 11:44:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uRI-0007fc-EZ
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 11:44:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QGiCOB029456
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 11:44:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uR7-0007cH-6r; Fri, 26 Mar 2004 11:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uQC-0007XN-GD
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 11:43:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00607
	for <avt@ietf.org>; Fri, 26 Mar 2004 11:43:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6uQB-00024t-00
	for avt@ietf.org; Fri, 26 Mar 2004 11:43:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6uPH-00021h-00
	for avt@ietf.org; Fri, 26 Mar 2004 11:42:07 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6uOP-0001wh-00
	for avt@ietf.org; Fri, 26 Mar 2004 11:41:13 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 26 Mar 2004 08:40:47 -0800
Received: from rkumar-w2k01.cisco.com (sjc-vpn2-785.cisco.com [10.21.115.17])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2QGedex011277;
	Fri, 26 Mar 2004 08:40:40 -0800 (PST)
Message-Id: <4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
X-Sender: rkumar999@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 26 Mar 2004 08:40:38 -0800
To: Colin Perkins <csp@csperkins.org>
From: Rajesh Kumar <rkumar999@comcast.net>
Subject: Re: [AVT] Re: Clearmode definition.
Cc: rkumar@cisco.com, yaakov_s@rad.com, avt@ietf.org
In-Reply-To: <20040326110238.5e8aeba2.csp@csperkins.org>
References: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
 <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
 <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
 <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
 <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
 <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
 <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS 
	autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

At 11:02 AM 3/26/2004 +0000, Colin Perkins wrote:

>Right - you have a pseudo-wire emulation, running multiple streams within
>the pseudo-wire. This would seem to be a typical application for the PWE3
>mechanisms, rather than something AVT should consider.

In some applications, this places a demand for two, not one, signaling 
mechanisms at the multimedia endpoints for RTP media e.g. SIP and PWE3 
control. These are applications where it might set up nx64 sessions and 
other (not necessarily simultaneous) sessions outside the pseudo-wire.

Perhaps, the PWE3 group should MIME this RTP media so that SIP and H.248 
can be used for setting up nx64 sessions. However, if there is no 
wide-spread demand for the SIP or H.248 signaling of the nx64 codec, the 
vendors may define their proprietary MIMEs in the 'vnd' tree.

Rajesh



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



From exim@www1.ietf.org  Fri Mar 26 11:50:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01020
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 11:50:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uWx-0008Gn-0L
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 11:50:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QGo2In031782
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 11:50:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uWu-0008Fk-Ll; Fri, 26 Mar 2004 11:50:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uW2-0008E8-8T
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 11:49:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00971
	for <avt@ietf.org>; Fri, 26 Mar 2004 11:49:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6uW1-0002Uz-00
	for avt@ietf.org; Fri, 26 Mar 2004 11:49:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6uV7-0002Sj-00
	for avt@ietf.org; Fri, 26 Mar 2004 11:48:10 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6uUR-0002Nv-00
	for avt@ietf.org; Fri, 26 Mar 2004 11:47:27 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2QGkZX07115;
	Fri, 26 Mar 2004 11:46:35 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GXT6K4HQ; Fri, 26 Mar 2004 11:46:35 -0500
Received: from nortelnetworks.com (acart1cb.ca.nortel.com [47.129.129.54]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id DBDZJ4NJ; Fri, 26 Mar 2004 11:46:36 -0500
Message-ID: <40645E6A.8010208@nortelnetworks.com>
Date: Fri, 26 Mar 2004 11:46:34 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Moshe Samoha <MosheS@audiocodes.com>
CC: schulzrinne@cs.columbia.edu, scott.petrack@edial.com, avt@ietf.org,
        Oren Peleg <OrenP@audiocodes.com>,
        Yuval Nissan <YuvalN@audiocodes.com>
Subject: Re: [AVT] RE: RFC2833 bis_4
References: <3F7A8186EE94CE4BB13996B62E7370F07E05E9@lodmsg01.corp.audiocodes.com>
In-Reply-To: <3F7A8186EE94CE4BB13996B62E7370F07E05E9@lodmsg01.corp.audiocodes.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by zcars04f.nortelnetworks.com id i2QGkZX07115
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Thanks, I'll check that out.

Moshe Samoha wrote:

> The mistake is at *Table 14* - R2 Backward Register Signals from=20
> =93draft-ietf-avt-rfc2833bis-04=94
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> Moshe.
>=20
> -----Original Message-----
> *From:* Oren Peleg
> *Sent:* Monday, March 22, 2004 12:56 PM
> *To:* Yuval Nissan; Moshe Samoha
> *Subject:* FW: RFC2833 bis_4
> *Importance:* High
>=20
> =20
>=20
> FYI
>=20
> =20
>=20
> -----Original Message-----
> *From:* Oren Peleg
> *Sent:* Monday, March 22, 2004 12:56 PM
> *To:* 'schulzrinne@cs.columbia.edu'; 'scott.petrack@edial.com'
> *Cc:* avt@ietf.org
> *Subject:* FW: RFC2833 bis_4
> *Importance:* High
>=20
> =20
>=20
> Please look below =96 it seems that some kind of technical mistake was=20
> done in the latest draft in regarding to the MF frequency tables.
>=20
> =20
>=20
> Regards,
>=20
> =20
>=20
> Oren P.
>=20
> =20
>=20
> -----Original Message-----
> *From:* Moshe Samoha
> *Sent:* Monday, March 22, 2004 12:27 PM
> *To:* Oren Peleg; Yuval Nissan
> *Subject:* RE: RFC2833 bis_4
> *Importance:* High
>=20
> =20
>=20
> I rechecked the issue.
>=20
> It seems that X-axis and the Y-axis have been replaced at table number =
13.
>=20
> If we replaced them, it is compatible to our old implementation.
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> Moshe.
>=20
> -----Original Message-----
> *From:* Moshe Samoha
> *Sent:* Monday, March 22, 2004 11:49 AM
> *To:* Oren Peleg; Yuval Nissan
> *Subject:* RFC2833 bis_4
> *Importance:* High
>=20
> =20
>=20
> We found out that we are not compatible with the last RFC2833 draft=20
> =93draft-ietf-avt-rfc2833bis-04=94 MFR2 Backward signaling.
>=20
> =20
>=20
> *Code*
>=20
> =09
>=20
> *Frequency *
>=20
> =20
>=20
> =09
>=20
> Old
>=20
> =09
>=20
> New
>=20
> 1
>=20
> =09
>=20
> 1140/1020
>=20
> =09
>=20
> 1020/1140
>=20
> 2
>=20
> =09
>=20
> 1140/900
>=20
> =09
>=20
> 1020/1020
>=20
> 3
>=20
> =09
>=20
> 1020/900
>=20
> =09
>=20
> 1020/900
>=20
> 4
>=20
> =09
>=20
> 1140/780
>=20
> =09
>=20
> 900/1020
>=20
> 5
>=20
> =09
>=20
> 1020/780
>=20
> =09
>=20
> 900/900
>=20
> 6
>=20
> =09
>=20
> 900/780
>=20
> =09
>=20
> 900/780
>=20
> 7
>=20
> =09
>=20
> 1140/660
>=20
> =09
>=20
> 780/1020
>=20
> 8
>=20
> =09
>=20
> 1020/660
>=20
> =09
>=20
> 780/900
>=20
> 9
>=20
> =09
>=20
> 900/660
>=20
> =09
>=20
> 780/780
>=20
> 10
>=20
> =09
>=20
> 780/660
>=20
> =09
>=20
> 780/660
>=20
> 11
>=20
> =09
>=20
> 1140/540
>=20
> =09
>=20
> 660/1020
>=20
> 12
>=20
> =09
>=20
> 1020/540
>=20
> =09
>=20
> 660/900
>=20
> 13
>=20
> =09
>=20
> 900/540
>=20
> =09
>=20
> 660/780
>=20
> 14
>=20
> =09
>=20
> 780/540
>=20
> =09
>=20
> 660/660
>=20
> 15
>=20
> =09
>=20
> 660/540
>=20
> =09
>=20
> 660/540
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> Moshe.
>=20
> =20
>=20

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



From exim@www1.ietf.org  Fri Mar 26 14:59:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11006
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 14:59:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6xTz-0007YM-Hj
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 14:59:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QJxBIS029033
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 14:59:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6xTp-0007Xf-0e; Fri, 26 Mar 2004 14:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6xT5-0007S6-CA
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 14:58:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10980
	for <avt@ietf.org>; Fri, 26 Mar 2004 14:58:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6xT2-0002EJ-00
	for avt@ietf.org; Fri, 26 Mar 2004 14:58:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6xS5-0002BK-00
	for avt@ietf.org; Fri, 26 Mar 2004 14:57:14 -0500
Received: from av5-1-sn1.fre.skanova.net ([81.228.11.111])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6xRW-00026w-00
	for avt@ietf.org; Fri, 26 Mar 2004 14:56:38 -0500
Received: by av5-1-sn1.fre.skanova.net (Postfix, from userid 502)
	id 3367737E69; Fri, 26 Mar 2004 20:56:07 +0100 (CET)
Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net [81.228.11.163])
	by av5-1-sn1.fre.skanova.net (Postfix) with ESMTP
	id 2321437E42; Fri, 26 Mar 2004 20:56:07 +0100 (CET)
Received: from vit (h53n2fls31o265.telia.com [217.208.189.53])
	by smtp3-1-sn1.fre.skanova.net (Postfix) with SMTP
	id ACF3337E42; Fri, 26 Mar 2004 20:56:06 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
        "Paul E. Jones" <paulej@packetizer.com>
Cc: "IETF AVT WG" <avt@ietf.org>
Subject: RE: [AVT] Comments on draft-ietf-avt-rfc2793bis-03.txt
Date: Fri, 26 Mar 2004 20:56:08 +0100
Message-ID: <BHEHLFPKIPMLPFNFAHJKEEAODPAA.gunnar.hellstrom@omnitor.se>
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)
In-Reply-To: <4061B5DB.9020705@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Magnus,
Thanks for the comments on RFC2793bis-03,

Comment 16 reflects another interpretation of RFC2198 than I have done.
-----------------------------------------------------------------------
> 16. Section 6.3:
>    "Below is an example of SDP similar to the above example, but also
>     utilizing RFC 2198 to provide redundancy for the text packets:
>
>         m=text 11000 RTP/AVP 98 100
>         a=rtpmap:98 t140/1000
>         a=rtpmap:100 red/1000
>         a=fmtp:100 98/98 "
>
> I think one should point out in this text that one signals only that one
> will use on layer of text redundancy. IF one would use three levels of
> redundancy then the fmtp line would read:
>     a=fmtp:100 98/98/98/98
>
---------------------------------------------------------------------------
-----
I have not understood that from RFC2198.

This is what RFC2198 says about the FMTP line:
-------------------------------------------------------------------------
To receive a redundant stream, this is all that is required.  However
   to send a redundant stream, the sender needs to know which codecs are
   recommended for the primary and secondary (and tertiary, etc)
   encodings.  This information is specific to the redundancy format,
   and is specified using an additional attribute "fmtp" which conveys
   format-specific information.  A session directory does not parse the
   values specified in an fmtp attribute but merely hands it to the
   media tool unchanged.  For redundancy, we define the format
   parameters to be a slash "/" separated list of RTP payload types.

   Thus a complete example is:

       m=audio 12345 RTP/AVP 121 0 5
       a=rtpmap:121 red/8000/1
       a=fmtp:121 0/5

   This specifies that the default format for senders is redundancy with
   PCM as the primary encoding and DVI as the secondary encoding.
   Encodings cannot be specified in the fmtp attribute unless they are
   also specified as valid encodings on the media ("m=") line.
-----------------------------------------------------------------
I cannot from this description read that there needs to be one figure in
fmtp for each generation of redundant data. I rather expect the fmtp line
to express possible codecs, with the first one being the primary, and then
enumerating the ones used for redundancy taken in any order.

The payload format is specified per block of text in the block header.
Therefore I do not see the need for SDP to specify exactly the planned PT:s
per redundant generation.

Thus
a=fmtp:100 98/98

Would be enough regardless how many generations of PT 98 data we intend to
handle.

OK?

Gunnar
-------------------------------------------
Gunnar Hellstrom
Omnitor AB
Renathvagen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------


> -----Original Message-----
> From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of Magnus
> Westerlund
> Sent: Wednesday, March 24, 2004 5:23 PM
> To: Gunnar Hellstrom; Paul E. Jones
> Cc: IETF AVT WG
> Subject: [AVT] Comments on draft-ietf-avt-rfc2793bis-03.txt
>
>
> Hi,
>
> Here is my comments from a review of this draft. As this draft was
> intended I will be extra hard on the ID nits, see link on:
> http://www.ietf.org/ID.html
>
> 1. The whole draft has 15 extra left columns. This can't be there, there
> is a strict requirement on maximum of 72 columns of text.
>
> 2. The correct page breaks are missing.
>
> 3. The author list contains a blank line.
>
> 4. The first line in the left column of the header says AVT Working
> Group. Of historic reasons it should say "Network Working Group"
>
> 5. The updated boiler plate according to RFC 3667 and RFC 3668 must be
> used.
>
> 6. The RFC editor notes on the first page, are to early. Please move
> them back, at least to after the TOC. But this is also commonly a
> section at the end of the draft.
>
> 7. Section 3. I think this section is mixing to many things into one
> brew. I have previously complained on the structure. I think that a
> simple restructuring of the draft would help immensely. I would propose
> the following:
> In section 3 define the RTP payload format, RTP header fields, and other
> things directly related to the payload.
>
> Create a new section for on usage of RFC 2198 redundancy. This would
> basically be moving section, 3.4, 3.5, 3.8, 3.9 and parts of 4.3 into
> this new section.
>
> 8. Section 3.1: I think this section need to be a bit clearer on what it
> defines. Currently it says:
>
>    "A text conversation RTP packet as specified by the text/t140 payload
>     format consists of an RTP header as defined in RFC 3550 [2] followed
>     immediately by a block of T.140 data, referred to as a "T140block"
>     (see section 3.3).  There are no additional headers specific to this
>     payload format."
>
> I would suggest that this is reformulated to:
>
> The text/t140 conversation RTP payload format consists of one and only
> one block of T.140 data, referred to as a "T140block" (see section 3.3).
> There are no additional headers specific to this payload format. The
> fields in the RTP header is set as defined in section 3.7.
>
> The problem with the old text is that it doesn't clearly define what the
> RTP payload was. Instead it defined an RTP packet, which when combined
> with RFC 2198 never exist in the described form. Because then the RTP
> header has its field defined per RFC 2198, and also the payload is per
> RFC 2198. Also due to text later in the discussion on usage of the
> redundancy there is need for a clear understanding of what the RTP
> payload is.
>
> 9. Same as 8 but for section 3.2.
>
> 10. Section 3.4: "The T140blocks MAY be transmitted redundantly
> according to the payload format defined in RFC 2198 [3]." Please replace
>   "T140blocks" with the "t140 RTP payloads". Reason is that RFC 2198
> sends RTP payloads redundantly.
>
> 11. Section 3.6: "Association of RTP streams is dependent on the
> particular session application and is outside the scope of this
> document." Please remove "session".
>
> 12. Section 4.2: "With both text/t140 and audio/t140, the loss of the
> last packet of a sequence of packets cannot be detected until the next
> text packet is transmitted." Please replace transmitted, with received.
> The receiver needs to get a new sequence number or T140 block counter to
> be able to determine if things has become lost.
>
> 13. Section 4.3:
>    "As an alternative (or in addition) to redundancy, Forward Error
>     Correction mechanisms MAY be used when transmitting text, as per RFC
>     2733 [8] or any other mechanism with the purpose of increasing the
>     reliability of text transmission."
>
> This text is redundant with section 3.5. Please gather things in
> one place.
>
> 14. Section 5.
>    "To control the character transmission rate, the MIME parameter "cps="
>     in the "fmtp" attribute [7] is defined (see section 8 ). It is used
>     in SDP with the following syntax: "
>
> The parameter is named "cps" not "cps=" The equal sign is a result of
> the name value pair that is used in fmtp lines.
>
> 15. Section 5, last paragraph. The network is another reason why a
> receiver may receive higher character rates. For example buffering that
> is more quickly sent than gathered could give this behaviour.
>
> 16. Section 6.3:
>    "Below is an example of SDP similar to the above example, but also
>     utilizing RFC 2198 to provide redundancy for the text packets:
>
>         m=text 11000 RTP/AVP 98 100
>         a=rtpmap:98 t140/1000
>         a=rtpmap:100 red/1000
>         a=fmtp:100 98/98 "
>
> I think one should point out in this text that one signals only that one
> will use on layer of text redundancy. IF one would use three levels of
> redundancy then the fmtp line would read:
>     a=fmtp:100 98/98/98/98
>
> 17. Section 11, The SRTP reference is only informative. A normative
> reference is something that one has a normative dependency of in this
> specification.
>
> 18. Don't forget to update section 13, and 14.
>
> And please go through the ID-Nits list. I have not checked everything on
> this list, but I expect you to do it.
>
> Cheers
>
>
>
> --
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>
>
> This communication is confidential and intended solely for the
> addressee(s). Any unauthorized review, use, disclosure or
> distribution is prohibited. If you believe this message has been
> sent to you in error, please notify the sender by replying to
> this transmission and delete the message without disclosing it.
> Thank you.
>
> E-mail including attachments is susceptible to data corruption,
> interruption, unauthorized amendment, tampering and viruses, and
> we only send and receive e-mails on the basis that we are not
> liable for any such corruption, interception, amendment,
> tampering or viruses or any consequences thereof.
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Fri Mar 26 15:50:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13957
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 15:50:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yHM-0003na-VG
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 15:50:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QKoCqE014566
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 15:50:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yHB-0003m3-Nx; Fri, 26 Mar 2004 15:50:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yGV-0003lF-Rz
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 15:49:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13857
	for <avt@ietf.org>; Fri, 26 Mar 2004 15:49:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yGU-0005kh-00
	for avt@ietf.org; Fri, 26 Mar 2004 15:49:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6yFY-0005hm-00
	for avt@ietf.org; Fri, 26 Mar 2004 15:48:20 -0500
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yF7-0005ei-00
	for avt@ietf.org; Fri, 26 Mar 2004 15:47:53 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id i2QKlrPt014436
	for <avt@ietf.org>; Fri, 26 Mar 2004 13:47:53 -0700 (MST)
Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226])
	by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i2QKhrqg006500;
	Fri, 26 Mar 2004 14:43:54 -0600
Message-ID: <4064970F.1040900@motorola.com>
Date: Fri, 26 Mar 2004 14:48:15 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] AVT WG Minutes from IEFT 59 in Seoul
References: <40642549.2090001@ericsson.com>
In-Reply-To: <40642549.2090001@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

...
>    - draft-ietf-avt-rtp-dsr-codecs-00.txt is the result of merging the
>      three separate DSR drafts. Review is needed, to see if this draft 
>      is ready for WG Last Call.

Hi, all,

I'd welcome your review and comments on this draft.

regards,
-Qiaobing Xie


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



From exim@www1.ietf.org  Fri Mar 26 16:30:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17030
	for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 16:30:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yu8-0005lb-Hz
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 16:30:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QLUGGL022166
	for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 16:30:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ytt-0005jg-BN; Fri, 26 Mar 2004 16:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ytA-0005hD-O6
	for avt@optimus.ietf.org; Fri, 26 Mar 2004 16:29:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16846
	for <avt@ietf.org>; Fri, 26 Mar 2004 16:29:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yt8-00023E-00
	for avt@ietf.org; Fri, 26 Mar 2004 16:29:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6yrv-0001mW-00
	for avt@ietf.org; Fri, 26 Mar 2004 16:28:01 -0500
Received: from rdu74-160-175.nc.rr.com
	([24.74.160.175] helo=paris.arid.us ident=system)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yq6-0001Pm-00
	for avt@ietf.org; Fri, 26 Mar 2004 16:26:06 -0500
Received: from madrid (madrid.arid.us [192.168.1.10])
	by paris.arid.us (8.12.5/8.12.5) with SMTP id i2QLPxw1017787;
	Fri, 26 Mar 2004 16:25:59 -0500
Message-ID: <012801c41378$ee2e9510$0a01a8c0@madrid>
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Cc: "IETF AVT WG" <avt@ietf.org>,
        =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
References: <406302C7.2050707@ericsson.com> <406429E2.8000001@ericsson.com>
Subject: Re: [AVT] WG Last Call: draft-ietf-avt-text-red-02.txt
Date: Fri, 26 Mar 2004 16:25:58 -0500
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 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Magnus,

> Also my comments does not count to the at least one reviewer rule. It is
> the task of the author to ensure that at least one person do a review.

Who should that person be?  Gunnar Hellstrom would likely be happy to review
that document.  However, since he's closely associated with this activity,
perhaps you prefer to have a different person.  Please advise, as I'm not
familiar with this rule.

> 1. First page, left side of the header: It should read "Network Working
> Group" of historic reasons rather than "AVT Working Group".

OK.. no problem.

> 2. In the "status of this memo" I don't think the intention is for the
> author to remove the "(we)" that are part of the boilerplate text, even
> when you are a single person. It is more important that it is the right
> text, than correctly correspond to if there is a single or more
> authors/contributors.

OK.. I've re-inserted the "I (we)" style of phrasing.

> 3. The RFC editor note should be moved to somewhere after the abstract.

OK.. I've moved it into the abstract.  Actually.. there is really no good
place for this :-)

I'll hold this document pending any further comments during the last call
and publish an update when advised.

Paul

> Cheers
>
> Magnus
>
>
> Magnus Westerlund wrote:
>
> > This is to announce a working group last call on the "Registration of
> > the text/red MIME Sub-Type" (draft-ietf-avt-text-red-02.txt).
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-text-red-02.txt
> >
> > Please send any final comments on this draft to the mailing list by
> > Thursday the 8th April 2004.
> > At that time, we will consider if it is appropriate to request
> > publication of this draft as a proposed standard RFC.
> >
> > Note that this draft will not be advanced until we receive at least one
> > valid review from someone not directly involved with production of the
> > draft (i.e., not an author or a major contributor).
> >
> > Regards
> >
> > Magnus Westerlund
> >
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > ----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> >
> >
> >
> > This communication is confidential and intended solely for the
> > addressee(s). Any unauthorized review, use, disclosure or distribution
> > is prohibited. If you believe this message has been sent to you in
> > error, please notify the sender by replying to this transmission and
> > delete the message without disclosing it. Thank you.
> >
> > E-mail including attachments is susceptible to data corruption,
> > interruption, unauthorized amendment, tampering and viruses, and we only
> > send and receive e-mails on the basis that we are not liable for any
> > such corruption, interception, amendment, tampering or viruses or any
> > consequences thereof.
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
> >
>
> -- 
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>
> This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution is
prohibited. If you believe this message has been sent to you in error,
please notify the sender by replying to this transmission and delete the
message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any such
corruption, interception, amendment, tampering or viruses or any
consequences thereof.
>


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



From exim@www1.ietf.org  Sat Mar 27 14:20:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25834
	for <avt-archive@odin.ietf.org>; Sat, 27 Mar 2004 14:20:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7JLw-0007dH-Pv
	for avt-archive@odin.ietf.org; Sat, 27 Mar 2004 14:20:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2RJKK0s029289
	for avt-archive@odin.ietf.org; Sat, 27 Mar 2004 14:20:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7JLe-0007b3-5v; Sat, 27 Mar 2004 14:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7JKy-0007Tf-IN
	for avt@optimus.ietf.org; Sat, 27 Mar 2004 14:19:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25694
	for <avt@ietf.org>; Sat, 27 Mar 2004 14:19:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7JKw-0005uG-00
	for avt@ietf.org; Sat, 27 Mar 2004 14:19:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7JJx-0005ki-00
	for avt@ietf.org; Sat, 27 Mar 2004 14:18:18 -0500
Received: from relay2.eecs.berkeley.edu ([169.229.60.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7JJ8-0005cy-00
	for avt@ietf.org; Sat, 27 Mar 2004 14:17:26 -0500
Received: from relay3.EECS.Berkeley.EDU (localhost [127.0.0.1])
	by relay2.EECS.Berkeley.EDU (8.12.10/8.9.3) with ESMTP id i2RJHPOc004376
	for <avt@ietf.org>; Sat, 27 Mar 2004 11:17:25 -0800 (PST)
Received: from gateway.EECS.Berkeley.EDU (nsmail@gateway.EECS.Berkeley.EDU [169.229.60.73])
	by relay3.EECS.Berkeley.EDU (8.12.10/8.9.3) with ESMTP id i2RJHPPc006409
	for <avt@ietf.org>; Sat, 27 Mar 2004 11:17:25 -0800 (PST)
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU
          [128.32.34.73]) by gateway.EECS.Berkeley.EDU (Netscape Messaging
          Server 4.15) with ESMTP id HV91KZ00.TGR for <avt@ietf.org>; Sat,
          27 Mar 2004 11:17:23 -0800 
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <5F7035B8-8023-11D8-9984-00039372C384@eecs.berkeley.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: avt@ietf.org
From: "John Lazzaro" <lazzaro@eecs.berkeley.edu>
Date: Sat, 27 Mar 2004 11:17:22 -0800
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Update of TCP framing I-D ...
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi everyone,

	Just sent in an update to the TCP framing I-D,
you can download an early copy now from the
Berkeley mirror:

http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-contrans.txt

	See Change Log entry below ...

---

H.  Change Log for <draft-ietf-avt-rtp-framing-contrans-01.txt>

In preparation for the upcoming <draft-ietf-mmusic-sdp-comedia>
revision, all mention of TLS has been removed from -01.txt.  In 
addition,
references have been updated.

---
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
lazzaro [at] cs [dot] berkeley [dot] edu
---


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



From exim@www1.ietf.org  Sun Mar 28 19:27:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13703
	for <avt-archive@odin.ietf.org>; Sun, 28 Mar 2004 19:27:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kcQ-0007P0-Cu
	for avt-archive@odin.ietf.org; Sun, 28 Mar 2004 19:27:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T0RAgU028438
	for avt-archive@odin.ietf.org; Sun, 28 Mar 2004 19:27:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kcG-0007NU-Gp; Sun, 28 Mar 2004 19:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kc9-0007My-JU
	for avt@optimus.ietf.org; Sun, 28 Mar 2004 19:26:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13668
	for <avt@ietf.org>; Sun, 28 Mar 2004 19:26:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7kc8-0001K2-00
	for avt@ietf.org; Sun, 28 Mar 2004 19:26:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7kbB-0001DI-00
	for avt@ietf.org; Sun, 28 Mar 2004 19:25:53 -0500
Received: from news.ti.com ([192.94.94.33] helo=dragon.ti.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7kaH-00010d-00
	for avt@ietf.org; Sun, 28 Mar 2004 19:24:57 -0500
Received: from dlep91.itg.ti.com ([157.170.152.55])
	by dragon.ti.com (8.12.11/8.12.11) with ESMTP id i2T0ORWb006361;
	Sun, 28 Mar 2004 18:24:27 -0600 (CST)
Received: from tnint11.telogy.design.ti.com (localhost [127.0.0.1])
	by dlep91.itg.ti.com (8.12.10/8.12.10) with ESMTP id i2T0OQpi013412;
	Sun, 28 Mar 2004 18:24:27 -0600 (CST)
Received: by tnint11.telogy.design.ti.com with Internet Mail Service (5.5.2653.19)
	id <HYZ83P0A>; Sun, 28 Mar 2004 19:24:14 -0500
Message-ID: <A03FFB626FA02D4A9C68DBA5B228AF1E09586C@gtmentos.telogy.design.ti.com>
From: "Mundra, Satish" <smundra@telogy.com>
To: "'Gunnar Hellstrom'" <gunnar.hellstrom@omnitor.se>,
        avt IETF
	 <avt@ietf.org>
Subject: RE: [avt]  Comments/questions on draft-ietf-avt-rfc2793bis-03.txt
Date: Sun, 28 Mar 2004 19:24:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>


Gunnar/Paul,

Here are some comments/questions on the draft :

1. In section 3.2 : "The T140block counter MUST be initialized to zero the
first time 
that a packet containing...." 

Initializing this counter to zero will make it weaker against encryption
attacks when RTP payload is encrypted. 

2. Section 3.7 states "M-bit: The M-bit has no defined meaning for t140 text
streams and MUST be set to 0."

For audio/t140 this should be set on the first packet of the text-spurt
(start of t140 payload after a period of silence ) as recommended in
RTP/AVT.  Why audio/t140 should be treated any different from other audio
encoding methods ? 

3. Section 3.9 states:  "- Each redundant data block MUST contain the same
data as a T140block previously transmitted as primary data, and be
identified with a timestamp offset
equating to the original timestamp for that T140block." 

This conflicts with Section 3.8  sates "Redundant data older than 16383
divided by the clock frequency MUST NOT be transmitted."  

4a. Section 4.5 states "When using the text/t140 payload format, any
zero-length T140blocks
that are sent as primary data MUST be included as redundant T140blocks on
subsequent packets just as normal text T140blocks would be so that sequence
number inference for the redundant T140blocks will be correct, as explained
in section 3.9. 

It not clear if the MUST is only applicable if one continues to transmit
payload RED.  
I would assume that one could switch to t140 payload for the first packet
after the "silence period". A clarification text regarding switching to t140
payload, if permitted, would be 
helpful.

4b.  Section 4.5 states "When using the audio/t140 payload format,
zero-length T140blocks sent as primary data MUST NOT be included as
redundant T140blocks, as it would simply be a waste of bandwidth to send
them."

With limitation on transmitting the older data (2 seconds) or when only one
level of redundancy is used one would frequently see packets that contain no
redundant data but 
2198 primary encoding block header of with F-bit set to 0.

Recommending a switch to regular t140 payload after "silence period" or
zero-length T140block transmission would save additional bandwidth which
seems to be the motivation.


5. Reading of Section 3.8/3.9/4.5 suggests that "RFC2198 -RTP Payload for
Redundant Audio Data" which is suitable for audio data requires additional
rules/restrictions for text  
data where sequence numbers instead of relative timestamps are of interest.
IMO, a new RTP payload format for redundant text data should be specified
where the redundancy header includes the "RTP sequence number offset"
instead of the timestamp offset. This would simplify the redundancy
mechanism for text where the goal is to infer the sequence number 
correctly and not the timestamp.


6. The last figure in section 6.3 has the F-bit in the last redundancy
header block as "1".
It should be "0".

Also the figures showing T140block counter seem to convey impression that
the t140block counter is not included in "block length" or is part of
redundancy header. Some clarification in the figures would be helpful. 


7. The benefits of introducing T140block counter are not clear.  This
counter is not a character counter which probably could help identifying
exact number of characters lost. 
One can detect loss/duplicate packets using the RTP sequence
numbers/timestamps. During a text-spurt transmission both RTP sequence
numbers and T140block counters would be in sync.
If one could identify the first packet of text-spurt with marker bit then
receiver would not be confused regarding loss, although the detection of
loss of the last packet in a spurt could still be difficult depending on
what follows. You have noted that event with T140block counter the loss of
the last packet of a sequence of packets cannot be detected until the next
text packet is transmitted. Why, it's not desirable to specify appropriate
M-bit behavior instead of an additional 2byte counter in every packet ? 


Regards,

Satish Mundra
Telogy Networks
20450 Century Blvd. 
Germantown, Md. 20874 



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



From exim@www1.ietf.org  Mon Mar 29 02:34:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15827
	for <avt-archive@odin.ietf.org>; Mon, 29 Mar 2004 02:34:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7rHh-0002Ld-8Z
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 02:34:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T7YDQI009026
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 02:34:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7rHW-0002Ka-8U; Mon, 29 Mar 2004 02:34:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7rGi-0002IX-1R
	for avt@optimus.ietf.org; Mon, 29 Mar 2004 02:33:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15712
	for <avt@ietf.org>; Mon, 29 Mar 2004 02:33:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7rGe-0005Ij-00
	for avt@ietf.org; Mon, 29 Mar 2004 02:33:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7rFh-00059X-00
	for avt@ietf.org; Mon, 29 Mar 2004 02:32:10 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7rEq-0004zh-00
	for avt@ietf.org; Mon, 29 Mar 2004 02:31:16 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2T7VGAh017327
	for <avt@ietf.org>; Mon, 29 Mar 2004 09:31:16 +0200
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 29 Mar 2004 09:31:15 +0200
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HV035DDF; Mon, 29 Mar 2004 09:31:24 +0200
Message-ID: <4067D0C3.3070309@ericsson.com>
Date: Mon, 29 Mar 2004 09:31:15 +0200
X-Sybari-Trust: 454b54a4 272a6e05 bf9f9d61 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
CC: "Paul E. Jones" <paulej@packetizer.com>, IETF AVT WG <avt@ietf.org>
References: <BHEHLFPKIPMLPFNFAHJKEEAODPAA.gunnar.hellstrom@omnitor.se>
In-Reply-To: <BHEHLFPKIPMLPFNFAHJKEEAODPAA.gunnar.hellstrom@omnitor.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Mar 2004 07:31:16.0015 (UTC) FILETIME=[D1DC03F0:01C4155F]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] How is SDP a=fmtp used for RFC 2198?
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Gunnar,

See comments inline. However feedback from actual users and the authors 
of RED is kindly requested, to help resolve this problem.


Gunnar Hellstrom wrote:

> Magnus,
> Thanks for the comments on RFC2793bis-03,
> 
> Comment 16 reflects another interpretation of RFC2198 than I have done.
> -----------------------------------------------------------------------
> 
>>16. Section 6.3:
>>   "Below is an example of SDP similar to the above example, but also
>>    utilizing RFC 2198 to provide redundancy for the text packets:
>>
>>        m=text 11000 RTP/AVP 98 100
>>        a=rtpmap:98 t140/1000
>>        a=rtpmap:100 red/1000
>>        a=fmtp:100 98/98 "
>>
>>I think one should point out in this text that one signals only that one
>>will use on layer of text redundancy. IF one would use three levels of
>>redundancy then the fmtp line would read:
>>    a=fmtp:100 98/98/98/98
>>
> 
> ---------------------------------------------------------------------------
> -----
> I have not understood that from RFC2198.
> 
> This is what RFC2198 says about the FMTP line:
> -------------------------------------------------------------------------
> To receive a redundant stream, this is all that is required.  However
>    to send a redundant stream, the sender needs to know which codecs are
>    recommended for the primary and secondary (and tertiary, etc)
>    encodings.  

I am basing this on this part. As it gives clear indication that one 
should indicate what generation of redundancy the codec is specified for.

This information is specific to the redundancy format,
>    and is specified using an additional attribute "fmtp" which conveys
>    format-specific information.  A session directory does not parse the
>    values specified in an fmtp attribute but merely hands it to the
>    media tool unchanged.  For redundancy, we define the format
>    parameters to be a slash "/" separated list of RTP payload types.
> 
>    Thus a complete example is:
> 
>        m=audio 12345 RTP/AVP 121 0 5
>        a=rtpmap:121 red/8000/1
>        a=fmtp:121 0/5
> 
>    This specifies that the default format for senders is redundancy with
>    PCM as the primary encoding and DVI as the secondary encoding.
>    Encodings cannot be specified in the fmtp attribute unless they are
>    also specified as valid encodings on the media ("m=") line.

Also this example clearly indicates that PT=0 (PCM) is used as primary, 
and DVI as secondary encoding. That ranking could not have been done 
unless the list implies an order from primary to higher degrees of 
redundancy.

> -----------------------------------------------------------------
> I cannot from this description read that there needs to be one figure in
> fmtp for each generation of redundant data. I rather expect the fmtp line
> to express possible codecs, with the first one being the primary, and then
> enumerating the ones used for redundancy taken in any order.
> 
> The payload format is specified per block of text in the block header.
> Therefore I do not see the need for SDP to specify exactly the planned PT:s
> per redundant generation.
> 
> Thus
> a=fmtp:100 98/98
> 
> Would be enough regardless how many generations of PT 98 data we intend to
> handle.
> 
> OK?

I also think that it would be simpler to use the list to indicate all 
codecs that MAY appear in the redundancy format. However as in my view 
the text indicates that one should indicate what specific configuration 
of redundancy codecs that should be used. This is also a matter of 
backwards compatibility, for RED in general. Therefore I seek input on 
how this has been interpreted and used so far.

Cheers

Magnus


-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Mon Mar 29 03:47:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18969
	for <avt-archive@odin.ietf.org>; Mon, 29 Mar 2004 03:47:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7sQJ-00036U-24
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 03:47:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T8lB2D011924
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 03:47:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7sQ9-000336-EZ; Mon, 29 Mar 2004 03:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7s5y-0008Gg-Jy
	for avt@optimus.ietf.org; Mon, 29 Mar 2004 03:26:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18058
	for <avt@ietf.org>; Mon, 29 Mar 2004 03:26:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7s5w-00051V-00
	for avt@ietf.org; Mon, 29 Mar 2004 03:26:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7s4y-0004ta-00
	for avt@ietf.org; Mon, 29 Mar 2004 03:25:09 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7s41-0004fk-00
	for avt@ietf.org; Mon, 29 Mar 2004 03:24:09 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63511 helo=mangole.dcs.gla.ac.uk)
	by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.04)
	id 1B7s3L-0002iD-00; Mon, 29 Mar 2004 09:23:29 +0100
Date: Mon, 29 Mar 2004 09:24:18 +0100
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar999@comcast.net>
Cc: rkumar@cisco.com, yaakov_s@rad.com, avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040329092418.651fe50b.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
References: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
	<4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
	<4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
	<27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il>
	<4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
	<4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net>
	<4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
	<4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar999@comcast.net> writes:
> At 11:02 AM 3/26/2004 +0000, Colin Perkins wrote:
> 
> >Right - you have a pseudo-wire emulation, running multiple streams
> >within the pseudo-wire. This would seem to be a typical application for
> >the PWE3 mechanisms, rather than something AVT should consider.
> 
> In some applications, this places a demand for two, not one, signaling 
> mechanisms at the multimedia endpoints for RTP media e.g. SIP and PWE3 
> control. These are applications where it might set up nx64 sessions and 
> other (not necessarily simultaneous) sessions outside the pseudo-wire.
>
> Perhaps, the PWE3 group should MIME this RTP media so that SIP and H.248 
> can be used for setting up nx64 sessions. 

Is that sufficient? You don't need to signal anything about the contents of
the pseudo-wire? Before proposing solutions, what are your requirements?

> However, if there is no 
> wide-spread demand for the SIP or H.248 signaling of the nx64 codec, the 
> vendors may define their proprietary MIMEs in the 'vnd' tree.

Or, perhaps, the vendors should work with PWE3 to define an appropriate
signalling mechanism (be that using SIP or otherwise)? 

-- 
Colin Perkins
http://csperkins.org/

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



From exim@www1.ietf.org  Mon Mar 29 05:15:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23600
	for <avt-archive@odin.ietf.org>; Mon, 29 Mar 2004 05:15:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7tnV-0005Aj-Gi
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 05:15:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TAFDGP019879
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 05:15:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7tnK-00059L-UH; Mon, 29 Mar 2004 05:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7tmY-000584-DN
	for avt@optimus.ietf.org; Mon, 29 Mar 2004 05:14:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23507
	for <avt@ietf.org>; Mon, 29 Mar 2004 05:14:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7tmV-0005J0-00
	for avt@ietf.org; Mon, 29 Mar 2004 05:14:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7tlW-00059q-00
	for avt@ietf.org; Mon, 29 Mar 2004 05:13:11 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7tkW-0004ug-00
	for avt@ietf.org; Mon, 29 Mar 2004 05:12:08 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2TAC8YG026835
	for <avt@ietf.org>; Mon, 29 Mar 2004 12:12:08 +0200 (MEST)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 29 Mar 2004 12:12:07 +0200
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id H7CMMXBN; Mon, 29 Mar 2004 12:10:19 +0200
Message-ID: <4067F605.4000001@ericsson.com>
Date: Mon, 29 Mar 2004 12:10:13 +0200
X-Sybari-Trust: 8720298e 2c4885b5 b4fd76d1 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: qxie1@email.mot.com, bdp003@motorola.com
CC: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Mar 2004 10:12:08.0567 (UTC) FILETIME=[4B3A9070:01C41576]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comments on draft-ietf-avt-rtp-dsr-codecs-00.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

I have reviewed draft-ietf-avt-rtp-dsr-codecs-00.txt and it is in a 
mature state, however I found a few errors and have suggestion for some 
improvements.

1. Status of this memo needs updating in accordance with RFC 3667 and 
RFC 3668. This also implies changes to the copyright, and IPR section. 
Please note that the IPR disclaimer at the end is only added if any IPR 
is known for the draft.

2. Please provide correct page breaks in the next version. It appears 
that it is missing the page break markers.

3. Section 2, second paragraph, last sentence: "... and an RTP 
packetization for ES 201 108 frames is defined in [10] in IETF."
I think that " is defined in RFC 3557 [10] by IETF." is a better wording.

4. Section 2.1, third paragraph. "Then, the quantized
    vectors from two consecutive frames are put into an FP, as described
    in more detail in Section 4.1 below."

I think one should spell out FP as this is the first occurrence in text. 
So my proposal is simply:
"Then, the quantized vectors from two consecutive frames are put into an 
frame pair (FP), as described in more detail in Section 4.1 below."

5. Section 3. I think one could avoid duplication of a lot of text by 
creating a first sub chapter of section three describing common 
behaviour. To such a section I think the following parts belong:
- Sections 3.1.1, 3.2.1, 3.3.1
- Sections 3.1.2, 3.2.2, 3.3.2
- Last paragraph of sections 3.1.3.1, 3.2.3.1, 3.3.3.1
- Sections 3.1.4, 3.2.4, 3.3.4


6. Section 3.2.3.1 and 3.3.3.1: Frame description:
"At the end, each FP MUST be padded with 4 zeros to the MSB 4 bits of 
the last octet in order to make the FP aligned to the 32-bit word 
boundary."

This frame is not 32 bit aligned, I propose that you change it to "octet 
aligned".

7. Section 4. I think it will be clearer if you move the registration 
into 3 different listings. That will avoid any unclarities around what 
the sub-type is. It will also make things clearer that there is three 
MIME types. However it will be a bit wasteful.

8. Section 5.
   "Implementations using the payload defined in this specification are
    subject to the security considerations discussed in the RTP
    specification [8] and the RTP profile [9]. This payload does not
    specify any different security services."

I would propose to change the end of the first sentence to: ... security 
considerations discussed in the RTP specification [8] and any RTP 
profile, e.g. AVP [9].

Update these things I think it is in great shape for a WG last call.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Mon Mar 29 11:17:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10737
	for <avt-archive@odin.ietf.org>; Mon, 29 Mar 2004 11:17:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zRo-0003zc-U2
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 11:17:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TGHCYG015347
	for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 11:17:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zRd-0003yM-VL; Mon, 29 Mar 2004 11:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zRO-0003xP-S9
	for avt@optimus.ietf.org; Mon, 29 Mar 2004 11:16:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10695
	for <avt@ietf.org>; Mon, 29 Mar 2004 11:16:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zRN-0003AV-00
	for avt@ietf.org; Mon, 29 Mar 2004 11:16:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7zQe-00031v-00
	for avt@ietf.org; Mon, 29 Mar 2004 11:16:02 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zQ2-0002rP-00
	for avt@ietf.org; Mon, 29 Mar 2004 11:15:22 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2TGFLqY028378
	for <avt@ietf.org>; Mon, 29 Mar 2004 18:15:21 +0200 (MEST)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 29 Mar 2004 18:15:21 +0200
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id H7CMWKX2; Mon, 29 Mar 2004 18:15:21 +0200
Message-ID: <40684B99.6010603@ericsson.com>
Date: Mon, 29 Mar 2004 18:15:21 +0200
X-Sybari-Trust: edec04bb 2c4885b5 832386e3 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: Adam Li <adamli@icsl.ucla.edu>, IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Mar 2004 16:15:21.0461 (UTC) FILETIME=[08CE4A50:01C415A9]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comments on draft-ietf-avt-ulp-09.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Adam,

I have reviewed draft-ietf-avt-ulp-09.txt, and found a number of thing 
to comment on. I still think there is need to do another revision before 
deciding to do a WG last call. I am not satisfied with the explanation 
of how the FEC stream is bound to the media, especially in regards to 
the SSRC. See more below.

1. You will need to update the status of this memo, copyright, 
disclaimer, and IPR section in accordance with RFC 3667 and RFC 3668.

2. Section 1. first paragraph: "FEC has been one of the
    main methods used to protect against packet loss over packet
    switched networks [1,9]."

Should it say: "FEC is one of the main methods ..." otherwise it sounds 
that FEC is no longer relevant.

3. Section 7.3: I think this section would benefit from being a bit more 
structure: I would propose to use a "field name: explanation ..." 
structure, with separate paragraphs for each section. I would also start 
  with a declaration saying that all RTP header fields are used 
according to RFC 3550.

4. Section 7.3: The marker bit needs a strict definition, even if it 
simply says: Is not used and SHALL be set to 0.

5. Section 7.3: The SSRC field text is strange. In a usage where the FEC 
stream is sent in a separate RTP session then one will need to use the 
same SSRC as in the media packets that one protects.

In general I think the draft is a bit unclear that one for each original 
SSRC media stream will need to have a corresponding FEC stream.

In the case of RED (RFC 2198) one will not have its own SSRC field, it 
will belong to the primary encoding, thus one may only attach FEC 
packets that to a media stream that it protects, as they will need to be 
the same.

6. The usage of RTP sequence number. To my understanding the sequence 
number is only used to detect the loss of FEC packets, it is not used 
for any recovery related procedures. The same is true for the RTP 
timestamp.

7. Section 7.3:
   "The payload type for the FEC packet is determined through dynamic,
    out of band means. According to RFC 3550 [3], RTP participants that
    cannot recognize a payload type must discard it. This provides
    backwards compatibility. The FEC mechanisms can then be used in a
    multicast group with mixed FEC-capable and FEC-incapable receivers.
    In such a case, the FEC stream will have a payload type which is not
    recognized by the FEC-incapable receivers, and will thus be
    disregarded."

Although this section is correct, it doesn't deal with the signalling 
plane. If a receiver gets an SDP that declares that FEC will be used, I 
think it is likely that the receiver will never join the session due to 
that it contains a media that it understand. The receiver must at least 
understand the FEC signalling to be able to determine that it can join 
and ignore the FEC information.


8. Section 7.4: "This header is 12 or 16 octets, depending on whether 
the extension bit is set." It is not depending on the "extension" bit. 
It is depending on the "L" bit.

9. Section 7.4:
   "The SN base field MUST be set to the minimum sequence number of
    those media packets protected by FEC (at all levels for the extended
    mode)."

I think the use of minimum has some problem in regards to wrap around. 
For timestamps we always has the possibilities to use the "earliest" 
designation. However in this case one must probably use a formulation 
like the "... lowest sequence number, taking wrap around into account, 
of those ..."

10. Section 7.5:
"  The setting of mask field when the extended mode FEC is used shall
    follow the following rules:

       a. A media packet SHALL be protected only once at each
          protection level higher than level 0. A media packet MAY be
          protected more than once at level 0 by different packets,
          providing the protection lengths of level 0 of these packets
          are equal.

       b. For a media packet to be protected at level p, it must also
          be protect at level p-1.

       c. If an ULP FEC packet contains protection at level p, it must
          also contain protection at level p-1."

This table and its explanation text has not improved. For example in B. 
I think it is important to point out that it can be by any packet. 
Otherwise it is easy to believe that it must be in this packet.

I think an example like the following at this place in the specification 
is a good one.


RTP seq / FEC packet

1 | 1    2     4
2 | 1    2     4
3 | 2    2     4
4 | 2    2     4
5 | 3    4     4
6 | 3    4     4
7 | 4    4     4
8 | 4    4     4
------------------------
Lvl 0    1     2


Which indicates that the first and third FEC packet does only protect 
level 0. While FEC packet 2 also protects level 0 and 1. And the fourth 
one protects all three levels. This is in accordance with the above rules.

11. Section 8.1, Second bullet:
       o Unsigned network-ordered 16 bit representation of the sum of
         the lengths of the CSRC List, length of the padding, length of
         the extension, and length of the media packet (16 bits)

This text is not as clear as it should be. To my understanding it is 
only clear by reading the recovery operation, that this is the media 
packet length - the fixed RTP header (12 bytes). I would recommend that 
it is formulated as this:

* Unsigned networkd-ordered 16 bit representation of the media packet 
length in bytes minus 12  (for the fixed RTP header), i.e. all of the 
following if present, CSRC list, extension header, RTP payload, and RTP 
padding.

12. Section 8.1 sixth bullet:
       o Padding, if present (variable length)

What padding is meant, I guess that it is the optional RTP padding 
specified by setting the P bit in the RTP header.

13. Section 8.1: Second paragraph:
   "If the lengths of the bit strings are not equal, each bit string
    that is shorter than length of the longest, MUST be padded to that
    length with 0. The pad MUST be added at the end of the bit string."

This section does not specify what padding pattern is used, this is 
important. If not the same pattern is used in protection and recovery 
operation it may swap bits for a longer packet being recovered.

14. Section 8.2.2: "Any value may be used for the padding."

Again a fixed pattern must be used. Use normative language when defining 
it.

15. Section 9.1: Bullet 2.
"For the FEC packet in T, compute the bit string by concatenating the 
first 64 bits of the FEC header with the FEC payload."

I think it is the first 80 bits that shall be copied. Otherwise the 
packet length recovery field will be present in the FEC strings for the 
received packets but not the FEC packet.

16. Section 9.1: Bullet 15: There should be a reference to the section 
that explains how one determines how the FEC stream is bound to the 
media stream. More of this below.

17. Section 9.2.2: I think this section should clarify that the packets 
original length is recovered from protection level 0's packet recovery 
field and will need to be used on higher levels to determine how many 
bytes that should be included in the recovered packet.

18. Section 11. The initial discussion on application of encryption is 
missing one important input parameter: Is FEC done on encrypted or 
unencrypted packets. In certain cases this is possible to do without any 
problems, however the RTP sequence number will need to be in clear. So 
it is most probably only SRTP for which it is interesting. Otherwise the 
FEC must be done prior to encryption.

19. Section 12 and 13 needs to be restructured. I would propose that 
these two is made into 3 sections.

- First a section on the multiplexing issues of FEC. Here one explains 
the two main ones, separate stream, and the special using RED. It 
explains how the original stream is bound to the normal, what 
information is necessary to indicate, and how the SSRC in the recovery 
step is determined.

- as second section we have the MIME parameter registration, listing all 
parameters that is needed.

- Third a mapping to SDP section, which contains rules, an offer-answer 
section, and examples.

This resolves a few loose ends, and will better explain what is 
necessary to declare in the signalling if one does not use SDP. Either 
when we migrates to SDP-NG or if one has H.323 or something else.

20. Section 12.1, the example is using PTs 78 and 79 as dynamic PT. 
please use any number in the range from 96-127, as the current numbers 
has ended up inside the RTCP PT collision space.

21. Section 12.3: The RTSP chapter is not correct. Each media always has 
its individual media RTSP control URL. It is the presence at session 
level that indicates if it aggregated control is available or not. Thus 
one will need to always use the proposed control URL in the fmtp line if 
one uses separate streams. Secondly there should be some rules if one 
needs to use PLAY on a separated FEC stream, or not. One could envision 
that if one sets up the FEC stream one will receive it in relation to 
the sent media when one plays the associated media session. This is only 
a issue for unaggregated control. However there might be reasons that 
one need to put the FEC stream in PLAY mode to receive any FEC. One 
should also not that non-aggreaged control with FEC may be problematic 
as it will not be easy for the server to determine what media stream is 
bound to the FEC stream. Please see the RTP retransmission format for 
such a description on this issue.

22. Section 13.1:

The first two lines with To: and Subject can be removed. they are 
replaced by the IANA sections initial lines requesting registration by IANA.

23. Section 13.1 I think one should specify a required parameter "rate", 
with text declaring that it must (rfc2198 multiplexed) and may be set to 
the same rate (separate sessions) as the associated media. Requiring the 
same rate will require the usage of different PTs if one has multiple 
PTs with different rates for the original media steam.

24. Section 13.1 The address field used is a optional parameter. Also in 
the current draft it has two different incarnations, one is a RTSP url, 
the other a complete address specification. These two will be need to be 
separated.  How to do this in SDP will need to be defined, which is best 
done in a SDP mapping section.

25. Section 13.1 Author/change controller: This should be you adam and 
possibly also include the AVT wg.

26. Section 13.1:
   "RTP and SDP Issues: Usage of this format within RTP and the Session
    Description Protocol (SDP) [6] are fully specified within Section 10
    of RFC xxxx."

What is the purpose of this section?


Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar 30 02:08:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28665
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 02:08:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8DM7-00059F-RV
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 02:08:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U78FT2019777
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 02:08:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8DLu-00052V-Nt; Tue, 30 Mar 2004 02:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7xZz-0003oL-RR
	for avt@optimus.ietf.org; Mon, 29 Mar 2004 09:17:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03693
	for <avt@ietf.org>; Mon, 29 Mar 2004 09:17:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7xZy-0000rA-00
	for avt@ietf.org; Mon, 29 Mar 2004 09:17:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7xZ2-0000k5-00
	for avt@ietf.org; Mon, 29 Mar 2004 09:16:33 -0500
Received: from smtp4.clb.oleane.net ([213.56.31.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7xYR-0000av-00
	for avt@ietf.org; Mon, 29 Mar 2004 09:15:55 -0500
Received: from paviliondeux ([194.206.151.59]) 
	by smtp4.clb.oleane.net with ESMTP id i2TEFO01030954
	for <avt@ietf.org>; Mon, 29 Mar 2004 16:15:24 +0200
Message-Id: <200403291415.i2TEFO01030954@smtp4.clb.oleane.net>
From: "peter lewis" <peter.lewis@upperside.fr>
To: <avt@ietf.org>
Date: Mon, 29 Mar 2004 16:15:26 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003E_01C415A9.0C43E910"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcQVmEhbMbhDAc67Sx2TLNzXb/Bxqw==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_70_80,
	HTML_FONTCOLOR_RED,HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,
	MISSING_OUTLOOK_NAME autolearn=no version=2.60
Subject: [AVT] TVoDSL 2005: call for proposals
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_003E_01C415A9.0C43E910
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

TVoDSL 2005: Broadcasting TV content over ADSL

Home network, middleware, access networks, compression tools: all the TVoDSL
technical issues will be addressed in detail by the major manufacturing,
economic and regulatory players in this promising new market at the TVoDSL
Conference, to take place in Paris on January 25 to 28, 2005. 

The organizers expect more than 600 participants and 40 exhibitors at the
Triple Play Showcase. 

 

A call for proposals is online at:

 

 <http://www.upperside.fr/tvodsl2005/tvodsl2005cfp.htm>
http://www.upperside.fr/tvodsl2005/tvodsl2005cfp.htm

 


------=_NextPart_000_003E_01C415A9.0C43E910
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
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=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><strong><b><font size=3D2 color=3D"#ec7000" =
face=3DArial><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial;color:#EC7000'>TVoDSL 2005:
Broadcasting TV content over ADS</span></font></b></strong><span
class=3Dtitrepapierstyle29><font size=3D2 color=3D"#ec7000" =
face=3DArial><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial;color:#EC7000'>L</span></font=
></span><font
size=3D2 color=3D"#ec7000" face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial;color:#EC7000'><br>
</span></font><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Arial'><br>
Home network, middleware, access networks, compression tools: all the =
TVoDSL
technical issues will be addressed in detail by </span></font><span
class=3Dtextebold><font size=3D2><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>the
major manufacturing, economic and regulatory =
players</span></font></span><font
size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial'>
in this promising new market at the TVoDSL Conference, to take place in =
<st1:place
w:st=3D"on"><st1:City w:st=3D"on">Paris</st1:City></st1:place> on =
January 25 to 28,
2005. </span></font><font size=3D2><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The organizers expect more than 600 =
participants and
40 exhibitors at the Triple Play Showcase. </span></font><font =
size=3D2><span
lang=3DEN-GB style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>A call for proposals is online =
at:</span></font><font
size=3D2><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/tvodsl2005/tvodsl2005cfp.htm"
title=3D"http://www.upperside.fr/tvodsl2005/tvodsl2005cfp.htm"><span =
lang=3DEN-GB>http://www.upperside.fr/tvodsl2005/tvodsl2005cfp.htm</span><=
/a></span></font><font
size=3D2><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_003E_01C415A9.0C43E910--


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



From exim@www1.ietf.org  Tue Mar 30 15:56:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11295
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 15:56:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QHJ-0007ZY-HW
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 15:56:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UKu979029108
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 15:56:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QHB-0007YB-EC; Tue, 30 Mar 2004 15:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QGi-0007Vt-81
	for avt@optimus.ietf.org; Tue, 30 Mar 2004 15:55:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11193
	for <avt@ietf.org>; Tue, 30 Mar 2004 15:55:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8QGg-0005hv-00
	for avt@ietf.org; Tue, 30 Mar 2004 15:55:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8QFp-0005gP-00
	for avt@ietf.org; Tue, 30 Mar 2004 15:54:38 -0500
Received: from av3-1-sn4.m-sp.skanova.net ([81.228.10.114])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8QFC-0005ab-00
	for avt@ietf.org; Tue, 30 Mar 2004 15:53:58 -0500
Received: by av3-1-sn4.m-sp.skanova.net (Postfix, from userid 502)
	id 6135437E82; Tue, 30 Mar 2004 22:53:27 +0200 (CEST)
Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182])
	by av3-1-sn4.m-sp.skanova.net (Postfix) with ESMTP
	id 41B5537E43; Tue, 30 Mar 2004 22:53:27 +0200 (CEST)
Received: from vit (h53n2fls31o265.telia.com [217.208.189.53])
	by smtp2-2-sn4.m-sp.skanova.net (Postfix) with SMTP
	id E3B8337E69; Tue, 30 Mar 2004 22:53:26 +0200 (CEST)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Colin Perkins" <csp@csperkins.org>,
        "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Cc: <paulej@packetizer.com>, <avt@ietf.org>
Subject: RE: [AVT] How is SDP a=fmtp used for RFC 2198?
Date: Tue, 30 Mar 2004 22:53:24 +0200
Message-ID: <BHEHLFPKIPMLPFNFAHJKCEICDPAA.gunnar.hellstrom@omnitor.se>
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)
In-Reply-To: <20040329135920.088a0720.csp@csperkins.org>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

On number of redundant generations for text transmission.
---------------------------------------------------------
There is a need for one original and three redundant copies as the
RECOMMENDED default for text transmission. That will meet the service
requirements of <1% character error rate in conditions when voice is barely
usable ( from F.700 & F.703 ). That can be in a society crisis situation
when the network gets congested, or in next outbreak of worms crawling the
Internet.
Audio can be used for voice, and video for sign language down to around 30%
packet loss. It can be a good goal to maintain usable text transmission at
that packet loss rate.

Try the calculator in http://packetizer.com/iptel/toip/cercalc.html
and find that you need 3 levels of redundancy to get under 1% character
error with 30% packet loss. The character error figure for text coded text
is at the bottom of the page.

It is not expensive. The RECOMMENDATION is to send text packets with 300 ms
intervals, and only when there is something to transmit. The redundancy
levels take little space compared to the packet and RTP header.

3 generations of redundant data may sound excessive, if you have a network
where loss is usually under 1%. But, if there is a risk of 30% in a crisis
situation, you should follow the recommendation.

On SDP for RFC2198
--------------------
If nobody have used RFC2198 for more than one generation of redundancy
before, we are maybe free to document an interpretation of the SDP a=fmtp
parameter in the most reasonable way. I think that is that the
slash-separated list enumerates payload types that may be used in the
session. Then, during media transmission, the PT parameters in the RFC2198
header indicates what coding was selected by the transmitter for that
occasion.

The "secondary", "tertiary" etc payload types, may rather indicate a level
of preference rather than the position among the redundant generations.

In the Introduction of RFC2198, the definition of fixed sets of payload
types communicated out of band is mentioned as a cumbersome approach, while
the freedom to select payload type for secondary information and indicate
it in the same packet is the preferred method used in RFC2198.

I would not expect the SDP parameters needed to use RFC2198 to work against
the promoted idea of the flexible coding of RFC2198.

Therefore, I think, that I can specify a=fmtp: 100 98/98   and mean that PT
98 is used as primary, and PT 98 is used for any number of generations of
secondary coded redundant data. No tertiary choice of coding is specified,
meaning no third choice of coding.

Here is the excerpt of RFC2198 introduction that supports this view:
-------------------------------------------------------------------------
 A modified version of the above solution could be to decide prior to
   the beginning of a conference on a set a 32 encoding combinations
   that will be used for the duration of the conference.  All tools in
   the conference can be initialized with this working set of encoding
   combinations.  Communication of the working set could be made through
   the use of an external, out of band, mechanism.  Setup is complicated
   as great care needs to be taken in starting tools with identical
   parameters.  This scheme is more efficient as only one byte is used
   to identify combinations of encodings.
   It is felt that the complication inherent in distributing the mapping
   of payload types onto combinations of redundant data preclude the use
   of this mechanism.

   A more flexible solution is to have a single payload type which
   signifies a packet with redundancy. That packet then becomes a
   container, encapsulating multiple payloads into a single RTP packet.
   Such a scheme is flexible, since any amount of redundancy may be
   encapsulated within a single packet.  There is, however, a small
   overhead since each encapsulated payload must be preceded by a header
   indicating the type of data enclosed.  This is the preferred
   solution, since it is both flexible, extensible, and has a relatively
   low overhead.  The remainder of this document describes this
   solution.
---------------------------------------------------------------
Clear, isn?t it?

Reagards

Gunnar
-------------------------------------------
Gunnar Hellstrom
Omnitor AB
Renathvagen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------


> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: Monday, March 29, 2004 2:59 PM
> To: Magnus Westerlund
> Cc: gunnar.hellstrom@omnitor.se; paulej@packetizer.com; avt@ietf.org
> Subject: Re: [AVT] How is SDP a=fmtp used for RFC 2198?
>
>
> I agree with Magnus' interpretation of the RED parameters, the complete
> list should be specified. However, our intent when writing RFC 2198 was
> never to include so many levels of redundancy: sending 4 copies of each
> frame seems excessive.
>
> Colin
>
>
>
> --> Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
> > Hi Gunnar,
> >
> > See comments inline. However feedback from actual users and
> the authors
> > of RED is kindly requested, to help resolve this problem.
> >
> >
> > Gunnar Hellstrom wrote:
> >
> > > Magnus,
> > > Thanks for the comments on RFC2793bis-03,
> > >
> > > Comment 16 reflects another interpretation of RFC2198 than I
> have done.
> > >
> -----------------------------------------------------------------------
> > >
> > >>16. Section 6.3:
> > >>   "Below is an example of SDP similar to the above example, but also
> > >>    utilizing RFC 2198 to provide redundancy for the text packets:
> > >>
> > >>        m=text 11000 RTP/AVP 98 100
> > >>        a=rtpmap:98 t140/1000
> > >>        a=rtpmap:100 red/1000
> > >>        a=fmtp:100 98/98 "
> > >>
> > >>I think one should point out in this text that one signals only that
> > >one>will use on layer of text redundancy. IF one would use
> three levels
> > >of>redundancy then the fmtp line would read:
> > >>    a=fmtp:100 98/98/98/98
> > >>
> > >
> > >
> ----------------------------------------------------------------------
> > > ----------
> > > I have not understood that from RFC2198.
> > >
> > > This is what RFC2198 says about the FMTP line:
> > >
> ----------------------------------------------------------------------
> > > --- To receive a redundant stream, this is all that is required.
> > > However
> > >    to send a redundant stream, the sender needs to know which codecs
> > >    are recommended for the primary and secondary (and tertiary, etc)
> > >    encodings.
> >
> > I am basing this on this part. As it gives clear indication that one
> > should indicate what generation of redundancy the codec is
> specified for.
> >
> > This information is specific to the redundancy format,
> > >    and is specified using an additional attribute "fmtp"
> which conveys
> > >    format-specific information.  A session directory does
> not parse the
> > >    values specified in an fmtp attribute but merely hands it to the
> > >    media tool unchanged.  For redundancy, we define the format
> > >    parameters to be a slash "/" separated list of RTP payload types.
> > >
> > >    Thus a complete example is:
> > >
> > >        m=audio 12345 RTP/AVP 121 0 5
> > >        a=rtpmap:121 red/8000/1
> > >        a=fmtp:121 0/5
> > >
> > >    This specifies that the default format for senders is redundancy
> > >    with PCM as the primary encoding and DVI as the secondary
> encoding.
> > >    Encodings cannot be specified in the fmtp attribute
> unless they are
> > >    also specified as valid encodings on the media ("m=") line.
> >
> > Also this example clearly indicates that PT=0 (PCM) is used as
> primary,
> > and DVI as secondary encoding. That ranking could not have been done
> > unless the list implies an order from primary to higher degrees of
> > redundancy.
> >
> > > -----------------------------------------------------------------
> > > I cannot from this description read that there needs to be one figure
> > > in fmtp for each generation of redundant data. I rather
> expect the fmtp
> > > line to express possible codecs, with the first one being
> the primary,
> > > and then enumerating the ones used for redundancy taken in any order.
> > >
> > > The payload format is specified per block of text in the
> block header.
> > > Therefore I do not see the need for SDP to specify exactly
> the planned
> > > PT:s per redundant generation.
> > >
> > > Thus
> > > a=fmtp:100 98/98
> > >
> > > Would be enough regardless how many generations of PT 98
> data we intend
> > > to handle.
> > >
> > > OK?
> >
> > I also think that it would be simpler to use the list to indicate all
> > codecs that MAY appear in the redundancy format. However as in my view
> > the text indicates that one should indicate what specific
> configuration
> > of redundancy codecs that should be used. This is also a matter of
> > backwards compatibility, for RED in general. Therefore I seek input on
> > how this has been interpreted and used so far.
> >
> > Cheers
> >
> > Magnus
> >
> >
> > --
> >
> > Magnus Westerlund
> >
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > ----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> >
> >
> > This communication is confidential and intended solely for the
> > addressee(s). Any unauthorized review, use, disclosure or
> distribution is
> > prohibited. If you believe this message has been sent to you in error,
> > please notify the sender by replying to this transmission and
> delete the
> > message without disclosing it. Thank you.
> >
> > E-mail including attachments is susceptible to data corruption,
> > interruption, unauthorized amendment, tampering and viruses,
> and we only
> > send and receive e-mails on the basis that we are not liable
> for any such
> > corruption, interception, amendment, tampering or viruses or any
> > consequences thereof.
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>
>
> --
> Colin Perkins
> http://csperkins.org/
>



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



From exim@www1.ietf.org  Tue Mar 30 17:57:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22033
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:57:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjc-0006a4-Ui
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAS9nEcm018938
	for avt-archive@odin.ietf.org; Fri, 28 Nov 2003 04:49:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfFO-0004qn-As; Fri, 28 Nov 2003 04:49:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfFC-0004lt-US
	for avt@optimus.ietf.org; Fri, 28 Nov 2003 04:48:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20020;
	Fri, 28 Nov 2003 04:48:45 -0500 (EST)
From: philippe.gentric@philips.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfF9-00060N-00; Fri, 28 Nov 2003 04:48:55 -0500
Received: from [217.32.166.20] (helo=relhubc02-ukbr.tcrelay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfF8-0005yJ-01; Fri, 28 Nov 2003 04:48:55 -0500
Received: from mail pickup service by relhubc02-ukbr.tcrelay.net with Microsoft SMTPSVC;
	 Fri, 28 Nov 2003 09:43:05 +0000
Received: from optimus.ietf.org ([132.151.6.22]) by relhubc02-ukbr.tcrelay.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 26 Nov 2003 16:29:27 +0000
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP2c5-0006gO-RB; Wed, 26 Nov 2003 11:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP2bv-0006fo-Sx
	for dccp@optimus.ietf.org; Wed, 26 Nov 2003 11:33:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16186;
	Wed, 26 Nov 2003 11:33:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP2bu-0000wG-00; Wed, 26 Nov 2003 11:33:50 -0500
Received: from gw-nl5.philips.com ([212.153.235.109] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP2bt-0000wC-00; Wed, 26 Nov 2003 11:33:50 -0500
Received: from smtpscan-nl2.philips.com (smtpscan-nl2.philips.com [130.139.36.22])
	by gw-nl5.philips.com (Postfix) with ESMTP
	id F246D6EE6F; Wed, 26 Nov 2003 17:33:43 +0100 (MET)
Received: from smtpscan-nl2.philips.com (localhost [127.0.0.1])
	by localhost.philips.com (Postfix) with ESMTP
	id 7229119C48; Wed, 26 Nov 2003 17:33:43 +0100 (MET)
Received: from smtprelay-nl2.philips.com (smtprelay-eur2.philips.com [130.139.36.35])
	by smtpscan-nl2.philips.com (Postfix) with ESMTP
	id 9DCA319C56; Wed, 26 Nov 2003 17:33:41 +0100 (MET)
Received: from hbg001soh.diamond.philips.com (e1soh01.diamond.philips.com [130.143.165.45]) 
	by smtprelay-nl2.philips.com (8.9.3p3/8.8.5-1.2.2m-19990317) with ESMTP id RAA08559; Wed, 26 Nov 2003 17:33:40 +0100 (MET)
Subject: Re: [AVT] RE: [dccp] Re: DCCP Media Guide
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: avt@ietf.org, dccp@ietf.org
X-Mailer: Lotus Notes Release 5.0.9a  January 7, 2002
Message-ID: <OF9E0275FF.7E294C3E-ONC1256DEA.00544541-C1256DEA.005AB0CB@diamond.philips.com>
Date: Wed, 26 Nov 2003 17:30:54 +0100
X-MIMETrack: Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.11  |July 24, 2002) at
 26/11/2003 17:35:20
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-BeenThere: dccp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
X-OriginalArrivalTime: 26 Nov 2003 16:30:12.0785 (UTC) FILETIME=[90DA8A10:01C3B43A]
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>


Henning, TFRC experts,


>> It would be interesting to look at the voice response to changing
>> packetization period.

..

>
>We have looked at this systematically, varying the packetization
>threshold. See the papers by Wenyu Jiang and myself at
>http://netbib.info and http://www1.cs.columbia.edu/~wenyu/
>

Does anyone have a clue of how changing the packetization
impacts the behavior of TFRC in presence of TCP traffic ?

For example if an application increases its packet rate
(same media rate, higher transmit rate due to packet headers contribution increasing)
is that added "pressure" against competing TCP traffic ?


regards,


Philippe Gentric
Chief Architect
Philips Software
philippe.gentric@philips.com
http://www.software.philips.com



_______________________________________________
dccp IETF mailing list: dccp@ietf.org
list info:  https://www1.ietf.org/mailman/listinfo/dccp
wg charter: http://www.ietf.org/html.charters/dccp-charter.html

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



From exim@www1.ietf.org  Tue Mar 30 18:06:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24777
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:06:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjX-0006Xa-FI
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAS9nEVH018940
	for avt-archive@odin.ietf.org; Fri, 28 Nov 2003 04:49:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfFM-0004pw-9J; Fri, 28 Nov 2003 04:49:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfFB-0004lk-Q7
	for avt@optimus.ietf.org; Fri, 28 Nov 2003 04:48:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20017;
	Fri, 28 Nov 2003 04:48:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfF8-00060I-00; Fri, 28 Nov 2003 04:48:54 -0500
Received: from [217.32.166.20] (helo=relhubc02-ukbr.tcrelay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfF8-0005yJ-00; Fri, 28 Nov 2003 04:48:54 -0500
Received: from mail pickup service by relhubc02-ukbr.tcrelay.net with Microsoft SMTPSVC;
	 Fri, 28 Nov 2003 09:43:04 +0000
Received: from optimus.ietf.org ([132.151.6.22]) by relhubc02-ukbr.tcrelay.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 26 Nov 2003 14:06:16 +0000
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP0Oe-000425-Hk; Wed, 26 Nov 2003 09:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP0Cb-0003HD-E6
	for dccp@optimus.ietf.org; Wed, 26 Nov 2003 08:59:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06953;
	Wed, 26 Nov 2003 08:59:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP0CZ-0005o9-00; Wed, 26 Nov 2003 08:59:31 -0500
Received: from brazilnut.cc.columbia.edu ([128.59.59.203] ident=cu41754)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP0CZ-0005o5-00; Wed, 26 Nov 2003 08:59:31 -0500
Received: from cs.columbia.edu (path.cs.columbia.edu [128.59.19.143])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.10/8.12.10) with ESMTP id hAQDxN2d015970
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 26 Nov 2003 08:59:23 -0500 (EST)
Message-ID: <3FC4B1BB.7000601@cs.columbia.edu>
Date: Wed, 26 Nov 2003 08:59:23 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: philippe.gentric@philips.com
CC: Stephen Casner <casner@acm.org>, avt@ietf.org, dccp@ietf.org
Subject: Re: [AVT] Re: [dccp] Re: DCCP Media Guide
References: <OF48291A11.1A43A7A1-ONC1256DEA.002CA9EB-C1256DEA.002F4651@diamond.philips.com>
In-Reply-To: <OF48291A11.1A43A7A1-ONC1256DEA.002CA9EB-C1256DEA.002F4651@diamond.philips.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.35
Content-Transfer-Encoding: 7bit
X-BeenThere: dccp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
X-OriginalArrivalTime: 26 Nov 2003 14:06:17.0195 (UTC) FILETIME=[75A413B0:01C3B426]
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


> I fully agree this is the fundamental reason why another protocol than TCP
> is a good idea: media does not need 100% reliability.

The only reason not to get 100% reliability is that relaxing reliability 
constraints reduces delay, as even modest loss rates, if unfortuitously 
placed, can wreak havoc with user experience. For the higher-latency 
streaming application contemplated here, it is unclear that removing 
reliability adds any significant value, particularly given that you end 
up having to add some protection (FEC) to deal with losses, thus 
increasing the overall average bit rate or reducing the quality. 
(Obviously, FEC doesn't deal well with loss spurts, so quality will be 
rather poor if losses are indeed bursty, even with aggressive FEC.) 
Typical FEC overhead for useful error resiliency is usually in excess of 
20%, so the bandwidth penalty is substantial.

Thus, before accepting that DCCP is the right thing for streaming media, 
a bit more human-factors and measurement evidence seems called for.

_______________________________________________
dccp IETF mailing list: dccp@ietf.org
list info:  https://www1.ietf.org/mailman/listinfo/dccp
wg charter: http://www.ietf.org/html.charters/dccp-charter.html

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



From exim@www1.ietf.org  Tue Mar 30 18:41:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04074
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:41:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riw-0006YH-UK
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAI9tuHu023319
	for avt-archive@odin.ietf.org; Tue, 18 Nov 2003 04:55:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM2Zh-0005mn-Hd; Tue, 18 Nov 2003 04:55:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM03W-0004no-Ri
	for avt@optimus.ietf.org; Tue, 18 Nov 2003 02:13:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07559
	for <avt@ietf.org>; Tue, 18 Nov 2003 02:13:34 -0500 (EST)
From: david.liu@st.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM03T-00076u-00
	for avt@ietf.org; Tue, 18 Nov 2003 02:13:43 -0500
Received: from beta.dmz-ap.st.com ([138.198.100.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM03S-00076c-00
	for avt@ietf.org; Tue, 18 Nov 2003 02:13:42 -0500
Received: from zeta.dmz-ap.st.com (ns6.st.com [138.198.234.13])
	by beta.dmz-ap.st.com (STMicroelectronics) with SMTP id 9723CDAC9
	for <avt@ietf.org>; Tue, 18 Nov 2003 07:13:10 +0000 (GMT)
Received: by zeta.dmz-ap.st.com (STMicroelectronics, from userid 60012)
	id 873D248DA; Tue, 18 Nov 2003 07:13:10 +0000 (GMT)
Received: from hkux01.hkg.st.com (localhost [127.0.0.1])
	by zeta.dmz-ap.st.com (STMicroelectronics) with ESMTP id 74E2A185E
	for <avt@ietf.org>; Tue, 18 Nov 2003 07:13:09 +0000 (GMT)
Received: from localhost (root@localhost)
	by hkux01.hkg.st.com (8.9.3 (PHNE_24419)/8.9.3) with ESMTP id PAA29983
	for <avt@ietf.org>; Tue, 18 Nov 2003 15:12:51 +0800 (SST)
X-OpenMail-Hops: 1
Date: Tue, 18 Nov 2003 15:12:50 +0800
Message-Id: <H0000dee02c86716.1069139063.hkux01.hkg.st.com@MHS>
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline; filename="O.TXT"
	;Creation-Date="Tue, 18 Nov 2003 15:04:23 +0800"
	;Modification-Date="Tue, 18 Nov 2003 15:12:46 +0800"
Subject: [AVT] Ask open source information on RTP/RTSP
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

Dear experts,

    Now I want to find a free RTP/RTSP streaming server to test ip set top box 
which does as a RTP/RTSP client.

    I am not very familiar with existed RTP/RTSP open source code. So would you 
like to give me some suggestions.

    If the server can support VOD and control stream bit rate, it is better.

best regards
david.liu

ST Microelectronics Inc.
email: david.liu@st.com


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



From exim@www1.ietf.org  Tue Mar 30 18:43:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04558
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:43:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj5-0006WI-Ki
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1IFMaEu027612
	for avt-archive@odin.ietf.org; Wed, 18 Feb 2004 10:22:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtTWI-0006us-5O; Wed, 18 Feb 2004 10:21:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtTUe-0006SS-1u
	for avt@optimus.ietf.org; Wed, 18 Feb 2004 10:20:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19506
	for <avt@ietf.org>; Wed, 18 Feb 2004 10:20:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtTUb-0000P5-00
	for avt@ietf.org; Wed, 18 Feb 2004 10:20:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtTTr-0000KK-00
	for avt@ietf.org; Wed, 18 Feb 2004 10:19:20 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtTT3-0000FO-00
	for avt@ietf.org; Wed, 18 Feb 2004 10:18:29 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i1IFISqY013619
	for <avt@ietf.org>; Wed, 18 Feb 2004 16:18:28 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 18 Feb 2004 16:18:28 +0100
Received: from ericsson.com (sealwp02-148.sw.ericsson.se [153.88.142.148]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 166BSW63; Wed, 18 Feb 2004 16:18:43 +0100
Message-ID: <403381B3.2050501@ericsson.com>
Date: Wed, 18 Feb 2004 16:16:03 +0100
X-Sybari-Trust: 4086315d c77f3eb6 63d53497 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: "'avt@ietf.org'" <avt@ietf.org>
Content-Type: multipart/mixed;
 boundary="------------010303000807030502010007"
X-OriginalArrivalTime: 18 Feb 2004 15:18:28.0746 (UTC) FILETIME=[76254EA0:01C3F632]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [AVT] Prelimenary agenda
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.
--------------010303000807030502010007
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Here is a preliminary agenda for the AVT WG sessions in Seoul. If you 
have comments please send them as soon as possible to us chairs.

As you can see we have time over in both sessions, so we will accept 
further requests for an agenda slot. However such a request must be sent 
to BOTH chairs before 12.00 AM GMT friday the 20th of February.

In the request include the following information:

A. Presentation Title:

B. Name of presenter:

C. Draft Reference(s):

D. Requested amount of time in minutes:


Cheers


Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


--------------010303000807030502010007
Content-Type: text/plain;
 name="ietf-59-AVT-agenda-prel.txt"
Content-Disposition: inline;
 filename="ietf-59-AVT-agenda-prel.txt"
Content-Transfer-Encoding: 7bit

Audio/Video Transport Working Group

CHAIRS: Colin Perkins     <csp@csperkins.org>
	Magnus Westerlund <magnus.westerlund@ericsson.com>


Tuseday, 2nd March 2004 at 09:00-11:30
=====================================

Introduction, and Status Update				(Chairs)	20
  In publishing process:
	draft-ietf-avt-mpeg4-simple-08.txt		[RFF 3640]
	draft-ietf-avt-rtcp-report-extns-06.txt		[RFC 3611]
	draft-ietf-srtp-09.txt 				[AUTH 48]
	draft-ietf-avt-rtcp-feedback-08.txt		[IESG Evaluation]
	draft-burmeister-avt-rtcp-feedback-sim-05.txt	[IESG Evaluation]
	draft-ietf-avt-rtp-clearmode-04.txt		[IESG Evaluation]
	draft-ietf-avt-ilbc-codec-04 (Experimental)	[IESG Evaluation]
	draft-ietf-avt-rtp-ilbc-04 (Experimental)	[IESG Evaluation]
	draft-ietf-avt-tcrtp-07.txt			[IETF LC]
	draft-ietf-avt-rtp-retransmission-10.txt	[AD Evaluation]
	draft-ietf-avt-uncomp-video-06			[AD Evaluation]
	 
  WG Documents:
	draft-ietf-avt-ulp-09.txt
	draft-ietf-avt-uxp-06.txt
	
	draft-ietf-avt-rfc2833bis-04.txt	
	draft-ietf-avt-rtp-clearmode-03.txt
	draft-ietf-avt-mpeg1and2-mod-00.txt
	draft-ietf-avt-rtp-dsr-codecs-00.txt
	draft-ietf-avt-profile-savpf-00.txt
	draft-ietf-avt-rfc3119bis-02.txt
	draft-ietf-avt-rtp-h264-04.txt
	draft-ietf-avt-rtp-jpeg2000-04.txt
	draft-ietf-avt-text-red-01.txt
	
  Induvidal contributions:	
	draft-sparks-avt-2833-interop-00.txt
	draft-kerr-avt-vorbis-rtp-03.txt
	draft-herlein-speex-rtp-profile-01 
	draft-jones-avt-audio-t38-01.txt
	draft-ramalho-rgl-rtpformat-02.txt
	draft-chen-rtp-bv-01.txt	
	draft-ahmadi-avt-rtp-vmr-wb-00.txt
	draft-ash-avt-ecrtp-over-mpls-protocol-00.txt
	draft-clark-avt-rtpmibv2-00.txt
	draft-finlayson-avt-mpa-robust-interoperability-00.txt
	draft-perkins-avt-rtp-reactive-fec-00.txt
	draft-rajeshkumar-avt-v150-registration-00.txt
	draft-tseng-avt-rtcp-streaming-extens-00.txt


Updates on behalf of author				(Chairs)	 5
	
	draft-ietf-avt-midi-rtp-01.txt
	draft-ietf-avt-midi-guidelines-01.txt
	draft-lazzaro-avt-rtp-framing-contrans-02.txt

RTP payload format for AMR-WB+ audio codec		(Lakaniemi)	15
	draft-sjoberg-avt-rtp-amrwbplus-01.txt

Introduction of ATRAC family payload format.		(Romaine)	15
	draft-hatanaka-avt-rtp-atrac-family-00.txt

3GPP Timed Text						(Rey)		15
	draft-rey-avt-3gpp-timed-text-02.txt

Payload format for text conversation (RFC2793bis )      (Hellstrom)     15
	ietf-draft-avt-rfc2793bis-02 (main document)
        ietf-draft-avt-text-red-00
	draft-ietf-mmusic-sdp-new-16
        draft-sinnreich-sipdev-req-03

H.261 and H.263 payload parameters			(Even)		15
        draft-ietf-avt-rfc2032-bis-00.txt 
        draft-ietf-avt-rfc2429-bis-00.txt 




Wednesay, 3rd March 2004 at 15:30-17:30
=====================================


Chairs Introduction							 5

RTCP Extensions for SSM Sessions with Unicast Feedback  (Ott)		15
	draft-ietf-avt-rtcpssm-06.txt
	
Requirements for ECRTP over MPLS			(Ash)		15
	draft-ash-avt-ecrtp-over-mpls-reqs-01.txt

Verifying the media path using RTP No-Op & Preconditions (Andreasen)    20
	draft-wing-avt-rtp-noop-00.txt
	draft-andreasen-mmusic-connectivityprecondition-00.txt
	
RTP Profile for TCP Friendly Rate Control		(Gharai)        30
        draft-gharai-avt-tfrc-profile-00.txt	




		
		

--------------010303000807030502010007--


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



From exim@www1.ietf.org  Tue Mar 30 18:47:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05569
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:47:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj1-0006a4-AG
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OAt9me013693
	for avt-archive@odin.ietf.org; Fri, 24 Oct 2003 06:55:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACzax-0003Xd-Vm; Fri, 24 Oct 2003 06:55:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACzZw-0003Iq-JY
	for avt@optimus.ietf.org; Fri, 24 Oct 2003 06:54:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25132
	for <avt@ietf.org>; Fri, 24 Oct 2003 06:53:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACzZr-0001TW-00
	for avt@ietf.org; Fri, 24 Oct 2003 06:53:55 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACzZr-0001TT-00
	for avt@ietf.org; Fri, 24 Oct 2003 06:53:55 -0400
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9OArlI2012972;
	Fri, 24 Oct 2003 12:53:47 +0200 (MEST)
Received: from ericsson.com (research-nnng7k.ki.sw.ericsson.se [147.214.34.132]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 43DQA21C; Fri, 24 Oct 2003 12:53:47 +0200
Message-ID: <3F9904B4.7050103@ericsson.com>
Date: Fri, 24 Oct 2003 12:53:40 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rey@panasonic.de
CC: "'IETF AVT WG'" <avt@ietf.org>, "'Dave Singer'" <singer@apple.com>,
        "Jan van der Meer (E-mail)" <jan.vandermeer@philips.com>,
        "Yoshinori Matsui (E-mail)" <matsui.yoshinori@jp.panasonic.com>
References: <004f01c39a14$d4ff9950$05640a0a@panasonic.de>
In-Reply-To: <004f01c39a14$d4ff9950$05640a0a@panasonic.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] Re: Comments on draft-rey-avt-rtp-3gpp-timed-text-01.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi Jos=C3=A9,

See comments and clarifications below. I hope that you will be able to=20
speed up the process for this, if you want to meet the deadlines you=20
have targeted.

Jos=C3=A9 Rey wrote:

>=20
>>8. Section 4. Timestamp definition: In the case of multiple=20
>>samples in a=20
>>packet, I think that the timestamp SHALL be set for the=20
>>earliest, rather=20
>>than first sample. Otherwise the duration rule will have problem. I=20
>>think one should also point out that all samples have unique=20
>>timestamps=20
>>that is why one can use the TS as a identifier of which packet the=20
>>fragments belong to.
>>
>=20
>=20
> This is described in the text as you say above, as no negative SDUR val=
ues are defined.  It seems this needs further clarification...
>=20
Yes, I think so.

>=20
>>10. Section 4. Sequence number handling. I think there are need to=20
>>consider sequence number in the case of FU packets to get the right=20
>>assembly order. In general I think there is a lack of definition or=20
>>explanation of how a receiver determines what is the first and last=20
>>packet of fragment.
>=20
>=20
> Right, this is not specified. I think the best solution here is to add =
(reuse) a new (the fragment) header field carrying some type of fragment =
numbering for those having the same TS. This is much easier. =20
>=20

Yes that will of course work. However it also gives one more insecurity, =

as you will not know when you should have received all fragments. The=20
potential problem as I see it if not all fragments are required to be=20
sent in RTP sequence number order is that the receiver having lost some=20
packets from the start can't determine if the lost packets contained=20
fragments or not. However there might be some other advantage of doing=20
as you propose it.

>=20
>>12. Figure 1, 2, 3, 4. I think there is not clear how a=20
>>receiver will be=20
>>able to distinguish between the cases.=20
>=20
>=20
> This is the same observation as in item 10 above.
>=20
>=20
>>The only one that has an=20
>>explanation at all is the case with FHDR first. How a=20
>>receiver detects=20
>>the presence or not of a SPLDESC I have no idea.=20
>=20
>=20
> The presence of SPLDESC is signalled using SDP. The SPLDESC is always a=
t least one byte long =3D the entry count byte.  A value of zero is allow=
ed for the entry count field.
>=20
> As for the presence of the rest: FHDR is indicated in SDP and for THDR =
in the FHDR itself (T=3D1)
>=20

So you are saying that you will have a different payload type for=20
payloads with SPLDESC compared to the ones without. Then you will have a =

different payload for presence of the FHDR or not. That makes it=20
necessary to have four payload types to allow for all four combinations.

I think you should strongly reconsider the usage of payload type=20
multiplexing for this functionality. Problems I see with payload type=20
multiplexing:

- The eventual exhaustion of the payload format space. If the payload=20
formats starts using multiple payload formats for normal cases the=20
choice of using PT in the RTP retransmission format is probably a bad=20
one, as it doubles the number of used payload formats.
- The need for having MIME parameter declaration for each and everyone=20
of the payload format configurations.

Due to this and the mitigating factor that this payload format is not=20
extremely high packet rate to begin with, the inclusion of 1 byte per=20
header will not cause a massive increase in overhead.

I would propose that you actually spend a byte for indicating the=20
necessary header types, allowing for the use of a single payload format=20
in the normal cases.

>=20
>>When I have this=20
>>complains I would also like to point out that using the=20
>>payload types is=20
>>not a good solution, at least not as the current parameter mapping is=20
>>done. When one has fragments one in fact duplicates all the=20
>>track header=20
>>information and sample descriptions sent in the SDP. As the fmtp line=20
>>can become rather big for this format I don't see this as an=20
>>acceptable=20
>>solution.
>=20
>=20
> Correct. To avoid this, is it not possible to associate the sample desc=
riptions and just write the contents in one line? I think this should be =
possible through some new SDP attribute and defining the behaviour of the=
 receiver. This way the PT-multiplexing still works fine.
>=20

As I point out above I don't think the usage PT multiplexing is the=20
correct choice for this format. I would also like to avoid having to=20
create a copy operation for the fmtp fields in SDP. We don't need more=20
functionality in SDP, we need a better session description format.

>=20
>>13. Section 4.1, page 8:
>>"  The composition of the THDR depends on whether the text sample is
>>    fragmented or not.  In particular:
>>
>>    - SLEN MUST NOT be present if the RTP packet contains a=20
>>text sample
>>    fragment.  If the RTP packet carries one or several non-fragmented
>>    samples SLEN MUST be present for every text sample, as in=20
>>Figure 1."
>>
>>Why should one not have a SLEN field for a fragment?
>=20
>=20
> The motivation for SLEN is for packets containing several whole text sa=
mples, to allow the receiver to jump from one sample to another, as a kin=
d of indexing. In the case the RTP packet only contains one text sample, =
SLEN is theoretically not needed; however we thought making an exception =
here would make it all too confusing.=20
>=20

Yes, I agree with your comments are bad, but you haven't answered why=20
there is a need for having a SLEN exception for the fragmented case.

>=20
>>In my opinion=20
>>knowing the total length of the fragmented sample allows one=20
>>to allocate=20
>>the correct buffer for that sample.
>>
>=20
> I think this is an implementation issue.  In general packet sizes are n=
ot included in RTP and buffering works anyway. I don't see why the sizes =
should be used in this particular case to reserve buffer in advance, spec=
ially given the low bitrates.
>=20

Yes, I would agree that if would not be needed in the normal case, but=20
we are in fact talking about fragmented samples that has no given size=20
limit. They could in fact be as large as 100kbytes. Depending on the=20
unlimited sample size I think it would be good to allow a receiver to=20
determine how big this sample is before trying to assemble it. That it=20
also helps the implementations in some cases to do this efficiently is=20
just a bonus.

>=20
>>14. Section 4.2.2 I am not convinced that the fragmentation=20
>>rules allow=20
>>for all cases to have the sample reconstructed. For example is seems=20
>>that multiple fragments of boxes will not be guaranteed to be=20
>>reconstructed in the correct order unless some other information is=20
>>provided.
>=20
>=20
> I think you mean the same as in 10 and 12 with the reassembly.=20

Yes, at least I think so. There has been a while since I wrote these=20
comments.

>=20
>=20
>>In general I would like to have a discussion of the need for the=20
>>advanced fragmentation formats that is defined. Could not a simple=20
>>fragmentation requiring all parts be sufficient. Are really=20
>>there enough=20
>>advantage of using the fragments when some are missing=20
>>enough. Will it=20
>>also not in some cases result in something that is more confusing the=20
>>not presenting it at all would.
>>
>>If one keeps this advance fragmentation then it is really need for a=20
>>introduction part that talks about why and how this works.
>>
>>15. Section 4.2 There is need for having guidelines on how to=20
>>fragment.=20
>>I think there are some fragmentation points that are advantageous.
>=20
>=20
> We developed the fragmentation headers because 3GPP timed text allows i=
n principle for bigger packets (until 2048 bytes) and didn't want to leav=
e that out. We also didn't assume the use of FEC, for simplicity.
>=20
> We realize that the FHDR increments the complexity of the draft. If fra=
gmentation happens seldom, we agree it is convenient to reduce the comple=
xity of the headers, i.e. to a mere counter of the fragments. Therefore w=
e would agree to simplify them if no one else has an application/use case=
 for that. Does anyone feel the advanced fragmentation headers as they ar=
e in the draft now are needed?
>=20

I don't now about the answer to your question.

>>18. Section 4.3: "   - All SIDX values present in the SPLDESC=20
>>field of=20
>>an RTP packet MUST be present in at least one of the text=20
>>samples in the=20
>>payload." I interpret this rule saying that within a RTP packet which=20
>>carries the Sample descriptions the sample description must=20
>>be included=20
>>in the sample part.=20
>=20
>=20
> This is not what is meant; descriptions are only present once. What we =
meant to be present in both SPLDESC and text samples is the SIDX value to=
 be able to pair them. This has two reasons: 1) in principle, SPLDESC was=
 thought for live streaming and 2) feedback might not always be available=
, so that the sender doesn't know the received descriptions. But it might=
 be used for other things, as you point out. So we can abolish the restri=
ction and make a note saying that the sender shall provide the means for =
the receiver to have all descriptions available for the received text sam=
ples whether there's feedback or not: using retransmissions, include the =
descriptions again or protect them with FEC appropriately.
>=20

I think that sounds more reasonable.

>=20
>=20
>=20
>>However I don't see a reason for this. All sample=20
>>descriptions MUST be cached and can at any time be used.=20
>>Therefore I see=20
>>some advantage of allowing sample description only packets=20
>>for example.=20
>>  They can be given high protection with FEC. They can be=20
>>given highest=20
>>priority for retransmission. They can be sent in advance and=20
>>verified as=20
>>arrived if explicit packet loss vectors are used. So what is=20
>>the reason.
>>
>=20
> I like the idea of using sample-description-only packets. A bit of the =
initial entry count field could be used to indicate there are any (SIDX,S=
PLATTR) pairs following or is just a sample-description-only packet.
>=20

Good, I hope it can be implemented without a lot of complexity.

>=20
>=20
>>20. Section 5.1: Why is not FEC with RFC 2733 mentioned?
>>
>=20
> is an option...can be included in next revision.

I think this is one of the formats that may really need to use FEC for=20
at least any SPDLDESCRs, this is especially for multicast distribution=20
cases, but also for unicast.

>>22. Section 8.1: Fragment variable: The values allow to be given are=20
>>they "one" and "zero" or "1" or "0"?=20
>>
>=20
> "fragment=3D0" and "fragment=3D1" are possible values.

Then please clarify that.

>=20
>=20
>>Also I don't like this=20
>>variable as=20
>>it results in duplication of a rather long "a=3Dfmtp" line.
>=20
>=20
> what do you propose instead?

As I have written previous I would suggest that you drop the whole PT=20
multiplexing for presence or not of FHDR, etc.

>=20
>>25. Section 8.1: spldesc-inband: I think there are interesting cases=20
>>where one would like to initially define some sample=20
>>descriptions which=20
>>is carried out-of-band, e.g. in SDP, and where one later may=20
>>want to add=20
>>more. I think there should be a "both" value for this parameter. Also=20
>>the acceptable value should be clearly defined.
>=20
>=20
> Agree,  how about :
>=20
> "spldesc=3Din"
> "spldesc=3Dout"
> "spldesc=3Dboth"
>=20
> as possible values for in-band, out-of-band and both in- and out-of-ban=
d tx of sample descriptions?

Looks good

>=20
>>28. Section 9, The encoding of the sample descriptions: You=20
>>mention that=20
>>they are compressed why base64 only provides expansion to allow for 8=20
>>bit binary in a set of characters acceptable for text=20
>>protocol. Base 64=20
>>has an expansion factor that 4 8-bit bytes becomes 5 base64 8=20
>>bit chars.
>=20
>=20
> could you reword your question? I am not sure I understand what you mea=
n. Base64 encoding was proposed in the last meeting in Vienna for h264 to=
 reduce overhead in the transport of parameter sets instead of the usual =
base16 encoding which has an expansion factor of two.
>=20

YEs, this is nit picking. If you compare the binary save sample=20
description, that will have a size of X. Then the BASE64 encoded will no =

t be compressed but rather expanded in regards to the binary. OF course=20
it is better than BASE16, but that what not what I was seeing as the=20
base line.


Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


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



From exim@www1.ietf.org  Tue Mar 30 18:48:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05732
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:48:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj1-0006WI-8c
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABGdGpA024824
	for avt-archive@odin.ietf.org; Tue, 11 Nov 2003 11:39:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJbXs-0006NB-4s; Tue, 11 Nov 2003 11:39:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJbXT-0006GC-LL
	for avt@optimus.ietf.org; Tue, 11 Nov 2003 11:38:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08896
	for <avt@ietf.org>; Tue, 11 Nov 2003 11:38:35 -0500 (EST)
From: jan.vandermeer@philips.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJbXS-0005dl-00
	for avt@ietf.org; Tue, 11 Nov 2003 11:38:46 -0500
Received: from gw-nl3.philips.com ([212.153.190.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJbXR-0005di-00
	for avt@ietf.org; Tue, 11 Nov 2003 11:38:45 -0500
Received: from smtpscan-nl3.philips.com (smtpscan-nl3.philips.com [130.139.36.23])
	by gw-nl3.philips.com (Postfix) with ESMTP
	id BAFC42B9D5; Tue, 11 Nov 2003 17:38:38 +0100 (MET)
Received: from smtpscan-nl3.philips.com (localhost [127.0.0.1])
	by localhost.philips.com (Postfix) with ESMTP
	id 28F1519C4A; Tue, 11 Nov 2003 17:38:38 +0100 (MET)
Received: from smtprelay-nl2.philips.com (smtprelay-eur2.philips.com [130.139.36.35])
	by smtpscan-nl3.philips.com (Postfix) with ESMTP
	id 8459119C46; Tue, 11 Nov 2003 17:38:37 +0100 (MET)
Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com [130.139.27.125]) 
	by smtprelay-nl2.philips.com (8.9.3p3/8.8.5-1.2.2m-19990317) with ESMTP id RAA21074; Tue, 11 Nov 2003 17:38:37 +0100 (MET)
To: "Jose Rey" <rey@panasonic.de>
Cc: avt@ietf.org, "Colin Perkins" <csp@csperkins.org>
Subject: Re: AW: [AVT] Slides for Monday AVT session
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF6729004A.B1EBA9DD-ONC1256DDB.005B27D4@philips.com>
Date: Tue, 11 Nov 2003 17:36:36 +0100
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.0.2CF1|June 9, 2003) at
 11/11/2003 17:36:37,
	Serialize complete at 11/11/2003 17:36:37
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 005B6BD6C1256DDB_="
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multipart message in MIME format.
--=_alternative 005B6BD6C1256DDB_=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Jose,

Thanks, I just asked for that in a "crossing" email. Issue resolved,=20
thanks again.

Best regards,

Jan










"Jose Rey" <rey@panasonic.de>
2003-11-11 05:31 PM

=20
        To:     Jan vanderMeer/EHV/CE/PHILIPS@PHILIPS
"Colin Perkins" <csp@csperkins.org>
        cc:     <avt@ietf.org>
        Subject:        AW: [AVT] Slides for Monday AVT session
        Classification:=20



Jan, you can download the ppt version of it under http://www.pel.panasonic.=
de/ietf/docs/ietf58-tt.ppt
=20
cheers,
=20
Jos=E9
=20
=20
-----Urspr=FCngliche Nachricht-----
Von: avt-admin@ietf.org [mailto:avt-admin@ietf.org]Im Auftrag von jan.vande=
rmeer@philips.com
Gesendet: Dienstag, 11. November 2003 17:23
An: Colin Perkins
Cc: avt@ietf.org; avt-admin@ietf.org
Betreff: Re: [AVT] Slides for Monday AVT session


Colin,=20

Thanks for your effort, but unfortunately the timed-text presentation is=20
still corrupted. Because of the problem I installed the latest version of=20
the Acrobat Reader, but that did not help.=20

Best regards,

Jan









Colin Perkins <csp@csperkins.org>=20
Sent by:=20
avt-admin@ietf.org=20
2003-11-11 05:11 PM=20
       =20
        To:        Jan vanderMeer/EHV/CE/PHILIPS@PHILIPS=20
        cc:        avt@ietf.org=20
        Subject:        Re: [AVT] Slides for Monday AVT session=20
        Classification:        =20



On Tuesday, Nov 11, 2003, at 05:13 US/Eastern,=20
jan.vandermeer@philips.com wrote:
> Thanks for making the slides available. I can read all of them, except=20
> the one on Timed Text, which is corrupted when reading it with my=20
> Acrobat Reader 6.0. Acrobat tells it's a font encoding problem. I=20
> would appreciate if you could resolve that.

I updated the zip file - maybe it's better now?

Colin


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




--=_alternative 005B6BD6C1256DDB_=
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">Jose,</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Thanks, I just asked for that in a &=
quot;crossing&quot; email. Issue resolved, thanks again.<br>
<br>
Best regards,<br>
<br>
Jan<br>
</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<td>
<br>
<br>
<br>
<br>
<br><font size=3D1 face=3D"sans-serif"><b>&quot;Jose Rey&quot; &lt;rey@pana=
sonic.de&gt;</b></font>
<p><font size=3D1 face=3D"sans-serif">2003-11-11 05:31 PM</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;Jan vanderMeer/EHV/CE/PHILIPS@PHILIPS<br>
&quot;Colin Perkins&quot; &lt;csp@csperkins.org&gt;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbs=
p; &nbsp; &nbsp; &nbsp;&lt;avt@ietf.org&gt;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject:=
 &nbsp; &nbsp; &nbsp; &nbsp;AW: [AVT] Slides for Monday AVT session</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=3Dblue face=3D"Arial">Jan, you can download the pp=
t version of it under </font><a href=3D"http://www.pel.panasonic.de/ietf/do=
cs/ietf58-tt.ppt"><font size=3D2 color=3Dblue face=3D"Arial"><u>http://www.=
pel.panasonic.de/ietf/docs/ietf58-tt.ppt</u></font></a>
<br><font size=3D3 face=3D"Times New Roman">&nbsp;</font>
<br><font size=3D2 color=3Dblue face=3D"Arial">cheers,</font>
<br><font size=3D3 face=3D"Times New Roman">&nbsp;</font>
<br><font size=3D2 color=3Dblue face=3D"Arial">Jos=E9</font>
<br><font size=3D3 face=3D"Times New Roman">&nbsp;</font>
<br><font size=3D3 face=3D"Times New Roman">&nbsp;</font>
<br><font size=3D2 face=3D"Tahoma">-----Urspr=FCngliche Nachricht-----<b><b=
r>
Von:</b> avt-admin@ietf.org [mailto:avt-admin@ietf.org]<b>Im Auftrag von </=
b>jan.vandermeer@philips.com<b><br>
Gesendet:</b> Dienstag, 11. November 2003 17:23<b><br>
An:</b> Colin Perkins<b><br>
Cc:</b> avt@ietf.org; avt-admin@ietf.org<b><br>
Betreff:</b> Re: [AVT] Slides for Monday AVT session<br>
</font>
<br><font size=3D2 face=3D"sans-serif"><br>
Colin,</font><font size=3D3 face=3D"Times New Roman"> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
Thanks for your effort, but unfortunately the timed-text presentation is st=
ill corrupted. Because of the problem I installed the latest version of the=
 Acrobat Reader, but that did not help.</font><font size=3D3 face=3D"Times =
New Roman"> </font><font size=3D2 face=3D"sans-serif"><br>
<br>
Best regards,<br>
<br>
Jan</font><font size=3D3 face=3D"Times New Roman"><br>
<br>
<br>
</font>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D2%>
<td width=3D40%><font size=3D3 face=3D"Times New Roman"><br>
<br>
<br>
<br>
</font><font size=3D1 face=3D"sans-serif"><b><br>
Colin Perkins &lt;csp@csperkins.org&gt;</b></font><font size=3D3 face=3D"Ti=
mes New Roman"> </font>
<p><font size=3D1 face=3D"sans-serif">Sent by: <br>
avt-admin@ietf.org</font><font size=3D3 face=3D"Times New Roman"> </font>
<p><font size=3D1 face=3D"sans-serif">2003-11-11 05:11 PM</font><font size=
=3D3 face=3D"Times New Roman"> </font>
<td width=3D56%><font size=3D1 face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; <=
/font><font size=3D1 face=3D"sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;To: &nbsp; &nbsp; &nbsp; &nbsp;Jan vanderMeer/E=
HV/CE/PHILIPS@PHILIPS</font><font size=3D3 face=3D"Times New Roman"> </font=
><font size=3D1 face=3D"sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;cc: &nbsp; &nbsp; &nbsp; &nbsp;avt@ietf.org</fo=
nt><font size=3D3 face=3D"Times New Roman"> </font><font size=3D1 face=3D"s=
ans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: [AVT] S=
lides for Monday AVT session</font><font size=3D3 face=3D"Times New Roman">=
 </font>
<p><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Classific=
ation: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=3D3 face=3D"Times New R=
oman"> </font></table>
<p><font size=3D3 face=3D"Times New Roman"><br>
<br>
</font><font size=3D2 face=3D"Courier New"><br>
On Tuesday, Nov 11, 2003, at 05:13 US/Eastern, <br>
jan.vandermeer@philips.com wrote:<br>
&gt; Thanks for making the slides available. I can read all of them, except=
 <br>
&gt; the one on Timed Text, which is corrupted when reading it with my <br>
&gt; Acrobat Reader 6.0. Acrobat tells it's a font encoding problem. I <br>
&gt; would appreciate if you could resolve that.<br>
<br>
I updated the zip file - maybe it's better now?<br>
<br>
Colin<br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
Audio/Video Transport Working Group<br>
avt@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/avt</font><font size=3D3 face=3D"Tim=
es New Roman"><br>
<br>
</font>
<p>
<p>
--=_alternative 005B6BD6C1256DDB_=--

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



From exim@www1.ietf.org  Tue Mar 30 18:53:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07138
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:53:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rix-0006a4-IU
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCTuKw020409
	for avt-archive@odin.ietf.org; Thu, 23 Oct 2003 08:29:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZZ-0004mf-Uo; Thu, 23 Oct 2003 08:28:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZ7-0004SH-8E
	for avt@optimus.ietf.org; Thu, 23 Oct 2003 08:27:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15582
	for <avt@ietf.org>; Thu, 23 Oct 2003 08:27:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZ6-0006S3-00
	for avt@ietf.org; Thu, 23 Oct 2003 08:27:44 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZ5-0006S0-00
	for avt@ietf.org; Thu, 23 Oct 2003 08:27:43 -0400
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9NCRWI2004155;
	Thu, 23 Oct 2003 14:27:37 +0200 (MEST)
Received: from ericsson.com (research-nnng7k.ki.sw.ericsson.se [147.214.34.132]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 43DWQRYX; Thu, 23 Oct 2003 14:28:18 +0200
Message-ID: <3F97C92E.9010202@ericsson.com>
Date: Thu, 23 Oct 2003 14:27:26 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Li <adamli@icsl.ucla.edu>, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] FEC draft
References: <000001c3992d$6760a1b0$6c7ba8c0@divxnetworks.com>
In-Reply-To: <000001c3992d$6760a1b0$6c7ba8c0@divxnetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Adam,

Why not, it should simplify the processing somewhat. However I think 
this should be discussed openly, so I CC the AVT list in this reply. So 
if someone else has any comments about this, please respond.

Cheers

Magnus

Adam Li wrote:

> Hi Magnus,
> 
> I shuffle the fields around a little bit more (since we have them moved
> already). What do you think about the following format along the line
> you proposed? It have a even closer resemblance of the RTP header.
> 
>  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
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |E|L|P|X|  CC   |M| PT recovery |            SN base            |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |                          TS recovery                          |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |        length recovery        |             mask              |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |              mask cont. (present only when L = 1)             |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> Do you think this looks alright? Thanks a lot.
> 
> Adam
> 
> 
> 
>>-----Original Message-----
>>From: avt-admin@ietf.org [mailto:avt-admin@ietf.org] On Behalf Of
>>Magnus Westerlund
>>Sent: Wednesday, October 22, 2003 5:31 AM
>>To: Adam Li
>>Cc: avt@ietf.org
>>Subject: Re: [AVT] FEC draft
>>
>>Hi Adam,
>>
>>[chair hat of]
>>
>>I have actually thought this over and have a counter proposal that I
>>think is rather nice. First I would like to rearrange the header in
>>the
>>following way:
>>
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|      SN base                  |        length recovery        |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|E|L|P|X|  CC   |M| PT recovery |             mask              |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|                          TS recovery                          |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>That way the 16 bits of fields matches the first 16 bits of the RTP
>>header. The sending part can simply XOR the headers of the packet as
>>is
>>and mask out the version bits.
>>
>>Secondly I would actually take the reserved bit and change it into a
>>"Long mask" indicator. When the L bit is set the header would then
>>actually look like this:
>>
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|      SN base                  |        length recovery        |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|E|L|P|X|  CC   |M| PT recovery |             mask              |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|                         mask continued                        |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>|                          TS recovery                          |
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>That way one can allow for a 48 bit mask while still keeping the
>>number
>>of options low and keep the 32 bit alignment.
>>
>>What does you think about it?
>>
>>Cheers
>>
>>Magnus
>>
>>
-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


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



From exim@www1.ietf.org  Tue Mar 30 18:53:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07265
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:53:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riw-0006WI-Me
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i219WKQZ024129
	for avt-archive@odin.ietf.org; Mon, 1 Mar 2004 04:32:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxjmP-0006AZ-QC; Mon, 01 Mar 2004 04:32:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxjmI-00069m-NZ
	for avt@optimus.ietf.org; Mon, 01 Mar 2004 04:31:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04968
	for <avt@ietf.org>; Mon, 1 Mar 2004 04:31:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxjmF-0004Bl-00
	for avt@ietf.org; Mon, 01 Mar 2004 04:31:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxjlE-00044T-00
	for avt@ietf.org; Mon, 01 Mar 2004 04:30:52 -0500
Received: from ns.live.com ([66.80.62.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axjkb-0003y3-00
	for avt@ietf.org; Mon, 01 Mar 2004 04:30:13 -0500
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.12.10/8.12.10) with ESMTP id i219U8NT094842;
	Mon, 1 Mar 2004 01:30:08 -0800 (PST)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.12.10/8.12.9/Submit) id i219U8tK094823;
	Mon, 1 Mar 2004 01:30:08 -0800 (PST)
	(envelope-from rsf)
Message-Id: <6.0.1.1.1.20040229215125.037560a0@localhost>
X-Sender: rsf@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 29 Feb 2004 21:55:58 -0800
To: multicast@lists.uoregon.edu
From: Ross Finlayson <finlayson@live.com>
Cc: avt@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60
Subject: [AVT] Bad RTCP synchronization in IETF MPEG-1 channel 2 session
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

FYI, the RTCP timestamp synchronization in the ongoing IETF MPEG-1 channel 
2 multicast session is broken: The audio and video streams are being 
signalled (by RTCP "SR" packets) as being something like 3900 seconds 
apart!  Not surprisingly, this breaks some media players.

(However, timestamp synchronization in the MPEG-1 channel *1* session seems 
to be OK.)

	Ross Finlayson
	LIVE.COM
	<http://www.live.com/>


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



From exim@www1.ietf.org  Tue Mar 30 18:54:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07523
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:54:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riw-0006a4-K0
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SI1C0g013447
	for avt-archive@odin.ietf.org; Tue, 28 Oct 2003 13:01:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEY9R-0003Tq-0E; Tue, 28 Oct 2003 13:01:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEY8b-0003CF-Ne
	for avt@optimus.ietf.org; Tue, 28 Oct 2003 13:00:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13169
	for <avt@ietf.org>; Tue, 28 Oct 2003 13:00:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEY8Z-00034R-00
	for avt@ietf.org; Tue, 28 Oct 2003 13:00:11 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEY8Y-00034O-00
	for avt@ietf.org; Tue, 28 Oct 2003 13:00:10 -0500
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9SI06I2017724;
	Tue, 28 Oct 2003 19:00:06 +0100 (MET)
Received: from ericsson.com (research-nnng7k.ki.sw.ericsson.se [147.214.34.132]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id VXB8C8Y1; Tue, 28 Oct 2003 19:00:06 +0100
Message-ID: <3F9EAE95.5070401@ericsson.com>
Date: Tue, 28 Oct 2003 18:59:49 +0100
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sassan.ahmadi@nokia.com
CC: IETF AVT WG <avt@ietf.org>, Colin Perkins <csp@csperkins.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comments on draft-ahmadi-avt-rtp-vmr-wb-00.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sassan,

I have a number of comments on the draft you have submitted.

1. First the draft does not follow the ID nits, the lines are too long:
	http://www.ietf.org/ID-nits.html

2. The section on the VMR-WB coded need further improvements in the 
language.

3. You define a the usage of AMR-WB modes within this payload format. I 
don't see the reason for doing this. Having looked at your scenarios I 
would solve this differently.

a. The IP end point to IP end-point. In this case there is no need for 
the interoperability mode. The end-point either supports VMR-WB fully or 
not at all. Therefore there seem to be little reason to switch to a 
constricted compatibility mode.

b. The WMR-WB on circuit switched side over a gateway. In this case the 
IP end-point either handles the full VMR-WB codec and the VMR modes can 
be used. If the other end-point only supports AMR-WB then one can use 
the AMR-WB payload format over the IP transport, using the AMR-WB mode 
set flag to restrict the modes to the single or three supported ones.

c. In the gateway scenario to gateway scenario. In this case either 
VMR-WB or AMR-WB can be used depending on what is used. The gateways can 
in the signalling declare that they support both.

Do you how any other case which motives this interoperability to be sent 
using the VMR format and not AMR-WB?

3. Section 8, figure 2: The stack is presented as RTP/UDP/IP/VMR-WB 
instead of VMR-WB/RTP/UDP/IP

4. Section 9, first paragraph: What is meant with the sentence: "The 
only differences are in the non-interoperable interconnections where NO 
IWF is required."?

5. Section 9.1, paragraph 4, last sentence: "The default input/output
sampling rate is 16 kHz. Note that during a session, the sampling rate
SHALL not be changed.". I can agree that the sampling rate shall not be 
changed for a given payload type. However over RTP the sampling rate 
could be changed through the switching of payload types. Therefore I 
think you should reconsider the SHALL NOT. Please not that in this case 
the NOT would be normative and therefore needs to be upper case.

6. Section 9.3.1: CMR definition: "Therefore, the network MAY
overwrite the mode request depending on the network conditions." This 
sentence is can definitely be misinterpret. Changing the CMR filed 
between RTP ingress point and egress would mean that one performs a 
layer violation that has several problems with it. For example security 
mechanisms, and checksums would drop a packet being changed. I assume 
that you are meaning a circuit switched node, prior to transport over 
RTP can change the CMR field. Please clarify this. Also needs to be 
consider for the type 15 in the CMR table (3).

7. Section 9.3.1, fourth paragraph: "With a given sampling rate (i.e., 
8/16 kHz), the encoder can switch between wide band or narrowband 
operation modes without prior knowledge of the decoder." What do you 
mean with this sentence? You can probably simplest achieve this through 
RTP payload type switching.

8. Section 9.3.2: How does the Q bit relates to the VMR modes?

9. Have you really considered the need for the bandwidth efficient mode?

10. I find the definition of the file format strange. I can certainly 
not have considered the implications of defining multiple magic keys. We 
would only have one, the multi-channel for AMR-WB files if it hadn't 
been so that we added this support to late, so that there where already 
other public specifications that assumed the single channel structure. 
So I would strongly recommend that you define only one magic key. Have 
you also considered the need for this simplistic file format and your 
requirements for a file format?

11. I don't see how you can redefine the AMR-WB format here. If you need 
a file format that can transport also AMR-WB then you will have to put 
this in your own format. I guess that your problem is that any AMR-WB 
file only using the interoperable modes are a valid AMR file, but any 
AMR-WB file is not a interoperable file. Depending on you needs you need 
to think of what the appropriate solution is.

12. There are missing padding bits in the section 10.3 figure.


13. Section 11, the chapter title. What is (Network controlled Mode 
Switching) doing in the title?

14. Section 12.2 Should talk not only about authentication of sources 
but also integrity protection. They are two different functionality, 
however often provided by the same security mechanism.

15. Section 13.1: I don't think you have need for some of the AMR-WB 
parameters. This relates to my concerns about the need for 
interoperability mode.

16. Section 13.1: The sampling frequency parameter could be replaced by 
a required rate parameter instead. the important here is that the actual 
used sampling rate probably needs to be put into the RTP timestamp, 
unless you have desire to make switching very simple and use 16khz for 
both sampling rates.

17. Section 14. The maxptime attribute is not a new attribute, it is 
defined in RFC 3267 and shall be referenced to that specification.

18. I know that the ISOC copyright allows for derived work. However I 
think one should extend the courtesy to acknowledge the massive 
borrowing of text from RFC 3267 that this draft has done.

19. Informative References: Reference 15 can be replace by the TFRC RFC 
reference now.


As a general comment I think that when borrowing this amount of text 
from another specification one should still think on what requirements 
one have and what is needed and what is not. There is still a lot of 
work for you to clear up a lot of small errors.

I welcome more discussion about the need for the interoperability modes.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com



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



From exim@www1.ietf.org  Tue Mar 30 18:57:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08246
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:57:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riv-0006Yx-I6
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NAEJqx016036
	for avt-archive@odin.ietf.org; Thu, 23 Oct 2003 06:14:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcTh-0003vs-CO; Thu, 23 Oct 2003 06:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcSp-0003oM-17
	for avt@optimus.ietf.org; Thu, 23 Oct 2003 06:13:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11520
	for <avt@ietf.org>; Thu, 23 Oct 2003 06:12:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcSl-0004o9-00
	for avt@ietf.org; Thu, 23 Oct 2003 06:13:03 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcSk-0004o6-00
	for avt@ietf.org; Thu, 23 Oct 2003 06:13:02 -0400
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9NAD2Ss029824
	for <avt@ietf.org>; Thu, 23 Oct 2003 12:13:02 +0200 (MEST)
Received: from ericsson.com (research-nnng7k.ki.sw.ericsson.se [147.214.34.132]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 45JSXYS7; Thu, 23 Oct 2003 12:14:02 +0200
Message-ID: <3F97A9A9.7010708@ericsson.com>
Date: Thu, 23 Oct 2003 12:12:57 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: multipart/mixed;
 boundary="------------080106040800080801020402"
Subject: [AVT] [Fwd: I-D ACTION:draft-sjoberg-avt-rtp-amrwbplus-00.txt]
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.
--------------080106040800080801020402
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Folks,

I would just like to inform you about this new RTP payload format for 
the AMR-WB+ codec, which is an extended AMR-WB codec for audio, which is 
   currently under specification within 3GPP. The payload format is 
based on the AMR and AMR-WB payload format with some changes.

Cheers

Magnus

-------- Original Message --------
Subject: I-D ACTION:draft-sjoberg-avt-rtp-amrwbplus-00.txt
Date: Wed, 22 Oct 2003 19:02:50 -0400
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
To: IETF-Announce: ;
CC: pwe3@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Real-Time Transport Protocol (RTP) Payload Format and 			 
Adaptive Multi-Rate Wideband plus (AMR-WB+) Audio Codec
	Author(s)	: J. Sjoberg, et. al.
	Filename	: draft-sjoberg-avt-rtp-amrwbplus-00.txt
	Pages		: 27
	Date		: 2003-10-22
	
This document specifies a real-time transport protocol (RTP) payload
format to be used for Adaptive Multi-Rate Wideband plus (AMR-WB+)
encoded audio signals. The AMR-WB+ codec is an audio extension of the
AMR-WB codec providing additional modes designed to give higher
quality of music and speech than the original modes.  The payload
format is designed according to the principles outlined in the
existing payload formats for AMR and AMR-WB, RFC3267 [9].  A MIME
type registration is included for AMR-WB+.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-sjoberg-avt-rtp-amrwbplus-00.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-sjoberg-avt-rtp-amrwbplus-00.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-sjoberg-avt-rtp-amrwbplus-00.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.




-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

--------------080106040800080801020402
Content-Type: Message/External-body;
 name="draft-sjoberg-avt-rtp-amrwbplus-00.txt"
Content-Disposition: inline;
 filename="draft-sjoberg-avt-rtp-amrwbplus-00.txt"
Content-Transfer-Encoding: 7bit



--------------080106040800080801020402--


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



From exim@www1.ietf.org  Tue Mar 30 18:58:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08399
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:58:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riv-0006Yx-04
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA69pQMN012280
	for avt-archive@odin.ietf.org; Thu, 6 Nov 2003 04:51:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgmH-00034E-K4; Thu, 06 Nov 2003 04:50:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgjW-0002Zz-Ga
	for avt@optimus.ietf.org; Thu, 06 Nov 2003 04:47:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01769
	for <avt@ietf.org>; Thu, 6 Nov 2003 04:46:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgjJ-00061k-00
	for avt@ietf.org; Thu, 06 Nov 2003 04:47:05 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgjI-00061a-00
	for avt@ietf.org; Thu, 06 Nov 2003 04:47:04 -0500
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hA69kuSs007785
	for <avt@ietf.org>; Thu, 6 Nov 2003 10:46:56 +0100 (MET)
Received: from ericsson.com (EF6HC000L5BCS1R.ki.sw.ericsson.se [137.58.144.226]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id V6M207JG; Thu, 6 Nov 2003 10:46:55 +0100
Message-ID: <3FAA187B.5070505@ericsson.com>
Date: Thu, 06 Nov 2003 10:46:35 +0100
X-Sybari-Trust: 4f7cf994 44883c8e fc415c9a 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: multipart/mixed;
 boundary="------------090800080606090906000407"
Subject: [AVT] Updated AVT agenda
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.
--------------090800080606090906000407
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

This is the latest revision of the AVT agenda. It is hopefully the last 
one. We have moved the Uncompressed Video back to monday and now have 
totally filled Monday, and only 10 free minutes on Wednesday.

Cheers

Magnus

--------------090800080606090906000407
Content-Type: text/plain;
 name="agenda.txt"
Content-Disposition: inline;
 filename="agenda.txt"
Content-Transfer-Encoding: base64

QXVkaW8vVmlkZW8gVHJhbnNwb3J0IFdvcmtpbmcgR3JvdXANCg0KQ0hBSVJTOiBDb2xpbiBQ
ZXJraW5zICAgICA8Y3NwQGNzcGVya2lucy5vcmc+DQoJTWFnbnVzIFdlc3Rlcmx1bmQgPG1h
Z251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4NCg0KDQpNb25kYXksIDEwdGggT2N0b2Jl
ciAyMDAzIGF0IDEzOjAwLTE1OjAwDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09DQoNCkludHJvZHVjdGlvbiBhbmQgU3RhdHVzIFVwZGF0ZQkJCQkoQ2hhaXJz
KSAgICAgICAgIDUNCglkcmFmdC1pZXRmLWF2dC1jcnRwLWVuaGFuY2UtMDcudHh0CQk9PiBS
RkMgMzU0NQ0KCWRyYWZ0LWlldGYtYXZ0LXJ0cC1uZXctMTIudHh0CQkJPT4gUkZDIDM1NTAN
CglkcmFmdC1pZXRmLWF2dC1wcm9maWxlLW5ldy0xMy50eHQJCT0+IFJGQyAzNTUxDQoJZHJh
ZnQtaWV0Zi1hdnQtcnRwLW1pbWUtMDYudHh0CQkJPT4gUkZDIDM1NTUNCglkcmFmdC1pZXRm
LWF2dC1ydGNwLWJ3LTA1LnR4dAkJCT0+IFJGQyAzNTU2DQoJZHJhZnQtaWV0Zi1hdnQtZHNy
LTA1LnR4dAkJCT0+IFJGQyAzNTU3DQoJZHJhZnQtaWV0Zi1hdnQtZXZyYy1zbXYtMDMudHh0
CQkJPT4gUkZDIDM1NTgNCglkcmFmdC1pZXRmLWF2dC1ydGNwLXJlcG9ydC1leHRucy0wNi50
eHQJCT0+IFJGQyAzNjExDQoJZHJhZnQtaWV0Zi1hdnQtcnRwLXJldHJhbnNtaXNzaW9uLTA5
LnR4dAlbQUQgRXZhbHVhdGlvbl0NCglkcmFmdC1pZXRmLWF2dC1ydGNwLWZlZWRiYWNrLTA3
LnR4dAkJW0FEIEV2YWx1YXRpb25dDQoJZHJhZnQtYnVybWVpc3Rlci1hdnQtcnRjcC1mZWVk
YmFjay1zaW0tMDIudHh0CVtBRCBFdmFsdWF0aW9uXQ0KCWRyYWZ0LWlldGYtYXZ0LXRjcnRw
LTA3LnR4dAkJCVtBRCBFdmFsdWF0aW9uXQ0KCWRyYWZ0LWlldGYtc3J0cC0wOS50eHQgCQkJ
CVtJRVNHIHJldmlld10NCglkcmFmdC1pZXRmLWF2dC1tcGVnNC1zaW1wbGUtMDgudHh0CQlb
UkZDIEVkaXRvcl0NCglkcmFmdC1pZXRmLWF2dC11eHAtMDYudHh0DQoJZHJhZnQtaWV0Zi1h
dnQtcmZjMjgzM2Jpcy0wMy50eHQJDQoJZHJhZnQtaWV0Zi1hdnQtcnRwLWNsZWFybW9kZS0w
My50eHQNCglkcmFmdC1pZXRmLWF2dC1tcGVnMWFuZDItbW9kLTAwLnR4dA0KCWRyYWZ0LWtl
cnItYXZ0LXZvcmJpcy1ydHAtMDMudHh0DQoJZHJhZnQtaGVybGVpbi1zcGVleC1ydHAtcHJv
ZmlsZS0wMS50eHQgDQoJZHJhZnQtam9uZXMtYXZ0LWF1ZGlvLXQzOC0wMS50eHQNCglkcmFm
dC1yYW1hbGhvLXJnbC1ydHBmb3JtYXQtMDIudHh0DQoJZHJhZnQtY2hlbi1ydHAtYnYtMDAu
dHh0CQ0KCWRyYWZ0LWhhdGFuYWthLWF2dC1ydHAtYXRyYWN4LTAzLnR4dA0KDQpVcGRhdGVz
IG9uIGJlaGFsZiBvZiBhdXRob3IJCQkJKENoYWlycykgICAgICAgIDE1DQoJZHJhZnQtaWV0
Zi1hdnQtdWxwLTA4LnR4dA0KCWRyYWZ0LWlldGYtYXZ0LXJ0cC1qcGVnMjAwMC0wNC50eHQN
CglkcmFmdC1pZXRmLWF2dC1taWRpLXJ0cC0wMC50eHQNCglkcmFmdC1pZXRmLWF2dC1taWRp
LWd1aWRlbGluZXMtMDAudHh0DQoJZHJhZnQtbGF6emFyby1hdnQtcnRwLWZyYW1pbmctY29u
dHJhbnMtMDIudHh0DQoNClJUUCBwYXlsb2FkIGZvcm1hdCBmb3IgQU1SLVdCKyBhdWRpbyBj
b2RlYwkJKExha2FuaWVtaSkgICAgIDE1DQoJZHJhZnQtc2pvYmVyZy1hdnQtcnRwLWFtcndi
cGx1cy0wMC50eHQNCgkNCkhpZ2hsaWdodHMgb2YgVk1SLVdCIFJUUCBQYXlsb2FkIGFuZCBT
dG9yYWdlIEZvcm1hdCAJKEFobWFkaSkgICAgICAgIDE1IA0KCWRyYWZ0LWFobWFkaS1hdnQt
cnRwLXZtci13Yi0wMC50eHQNCg0KUlRQIHBheWxvYWQgZm9ybWF0cyBmb3IgRVRTSSBEU1Ig
ZnJvbnQgZW5kcwkJKFhpZSkgICAgICAgICAgIDE1DQoJZHJhZnQtaWV0Zi1hdnQtZHNyLWVz
MjAyMDUwLTAxLnR4dA0KCWRyYWZ0LXhpZS1hdnQteGRzci1lczIwMjIxMS0wMC50eHQNCglk
cmFmdC14aWUtYXZ0LXhhZHNyLWVzMjAyMjEyLTAwLnR4dA0KDQpJbnRlcm5ldCBMb3cgQml0
IFJhdGUgQ29kZWMgJiBpdHMgUlRQIHBheWxvYWQgZm9ybWF0CShEdXJpYykgICAgICAgICAx
NQ0KCWRyYWZ0LWlldGYtYXZ0LXJ0cC1pbGJjLTAzLnR4dA0KCWRyYWZ0LWlldGYtYXZ0LWls
YmMtY29kZWMtMDMudHh0DQoJDQpSVFAgUGF5bG9hZCBmb3IgVGV4dCBDb252ZXJzYXRpb24J
CQkoSGVsbHN0cm9tKSAgICAgMTUJDQoJZHJhZnQtaGVsbHN0cm9tLWF2dC1yZmMyNzkzYmlz
LTAyLnR4dA0KDQpXYXkgZm9yd2FyZCBmb3IgdGhlIFJUUCBwYXlsb2FkIGZvcm1hdCBmb3Ig
VGltZWQgVGV4dAkoUmV5KSAgICAgICAgICAgMTUNCglkcmFmdC1yZXktYXZ0LTNncHAtdGlt
ZWQtdGV4dC0wMS50eHQNCg0KUlRQIFBheWxvYWQgRm9ybWF0IGZvciBVbmNvbXByZXNzZWQg
VmlkZW8gCQkoR2hhcmFpKSAgICAgICAgMTANCglkcmFmdC1pZXRmLWF2dC11bmNvbXAtdmlk
ZW8tMDQudHh0DQoNCg0KDQpXZWRuZXNkYXksIDEydGggT2N0b2JlciAyMDAzIGF0IDA5OjAw
LTExOjMwDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoN
ClJUUCBwYXlsb2FkIEZvcm1hdCBmb3IgSC4yNjQgVmlkZW8JCQkoV2VzdGVybHVuZCkgICAg
MTUNCglkcmFmdC1pZXRmLWF2dC1ydHAtaDI2NC0wMy50eHQNCg0KUlRDUCBFeHRlbnNpb25z
IGZvciBTU00gd2l0aCBVbmljYXN0IEZlZWRiYWNrCQkoT3R0KSAgICAgICAgICAgMTUNCglk
cmFmdC1pZXRmLWF2dC1ydGNwc3NtLTA1LnR4dA0KDQpFeHRlbmRlZCBTZWN1cmUgUlRQIFBy
b2ZpbGUgZm9yIFJUQ1AtYmFzZWQgRmVlZGJhY2sgCShPdHQpICAgICAgICAgICAxNQ0KCWRy
YWZ0LWlldGYtYXZ0LXByb2ZpbGUtc2F2cGYtMDAudHh0DQoNClJUQ1AgU3RyZWFtaW5nIEV4
dGVuZGVkIFJlcG9ydHMJCQkJKFRzZW5nKSAgICAgICAgIDE1DQoJZHJhZnQtdHNlbmctYXZ0
LXJ0Y3Atc3RyZWFtaW5nLWV4dGVucy0wMC50eHQNCg0KUHJvcG9zZWQgYWRkaXRpb25zIHRv
IFJUUCBNSUIJCQkJKENsYXJrKSAgICAgICAgIDE1DQoJIGRyYWZ0LWNsYXJrLWF2dC1ydHBt
aWJ2Mi0wMC50eHQNCgkgDQpEYXRhZ3JhbSBDb25nZXN0aW9uIENvbnRyb2wgUHJvdG9jb2wg
KERDQ1ApIGFuZCBSVFAJKEtvaGxlcikgICAgICAgIDE1DQoJZHJhZnQtaWV0Zi1kY2NwLXNw
ZWMtMDUudHh0DQoJZHJhZnQtaWV0Zi1kY2NwLWNjaWQyLTA0LnR4dA0KCWRyYWZ0LWlldGYt
ZGNjcC1jY2lkMy0wNC50eHQNCglkcmFmdC1pZXRmLWRjY3AtY2NpZDMtdGhpbi0wMC50eHQJ
IA0KDQpSVFAgSGVhZGVyIENvbXByZXNzaW9uIG92ZXIgTXVsdGktSG9wIFBhdGhzCQkoQXNo
KSAgICAgICAgICAgMTUNCglkcmFmdC1hc2gtZTJlLXZvaXAtaGRyLWNvbXAtcnFtdHMtMDEu
dHh0DQoNClJlcXVpcmVtZW50cyBmb3IgdHJhbnNwb3J0IG9mIHZpZGVvIGNvbnRyb2wgY29t
bWFuZHMgCShCYXNzbykgICAgICAgICAxNQ0KCWRyYWZ0LWJhc3NvLWF2dC12aWRlb2NvbnJl
cS0wMC50eHQNCg0KU0RQIHBhcmFtZXRlcnMgZm9yIHN1cHBvcnRpbmcgSC4yNjMgYW5kIEgu
MjYxIG9wdGlvbnMJKEV2ZW4vSXNtYWlsKSAgIDIwDQoJZHJhZnQtZXZlbi1hdnQtaDI2My1o
MjYxLW9wdGlvbnMtMDAudHh0DQoJZHJhZnQtbmlzbWFpbC1tbXVzaWMtc2RwLXZpZGVvLTAw
LnR4dA0KDQo=
--------------090800080606090906000407--


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



From exim@www1.ietf.org  Tue Mar 30 19:00:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09113
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 19:00:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rir-0006a4-UW
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2496UB1028005
	for avt-archive@odin.ietf.org; Thu, 4 Mar 2004 04:06:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayonr-0007G0-Hh; Thu, 04 Mar 2004 04:06:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayon7-0006xk-17
	for avt@optimus.ietf.org; Thu, 04 Mar 2004 04:05:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01637
	for <avt@ietf.org>; Thu, 4 Mar 2004 04:05:14 -0500 (EST)
From: csp@csperkins.org
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayon4-0000Qt-00
	for avt@ietf.org; Thu, 04 Mar 2004 04:05:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayom7-0000Et-00
	for avt@ietf.org; Thu, 04 Mar 2004 04:04:15 -0500
Received: from ds10.man.olsztyn.pl ([213.184.20.170] helo=eddie)
	by ietf-mx with smtp (Exim 4.12)
	id 1AyolA-0007h4-00
	for avt@ietf.org; Thu, 04 Mar 2004 04:03:16 -0500
Date: Thu, 04 Mar 2004 10:05:43 +0100
To: avt@ietf.org
Message-ID: <gebvyohksngaatqsthx@csperkins.org>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------tfvuvfovrtusrcbuuwam"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Subject: [AVT] ello! =))
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

----------tfvuvfovrtusrcbuuwam
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_BAGLE.GEN-1 in file MoreInfo.zip
The file is deleted.

---------------------------------------------------------

----------tfvuvfovrtusrcbuuwam
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Argh, i don't like  the plaintext :)
 
password  for archive: 30062

----------tfvuvfovrtusrcbuuwam
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

MoreInfo.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------tfvuvfovrtusrcbuuwam--


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



From exim@www1.ietf.org  Tue Mar 30 19:06:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10145
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 19:06:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riz-0006WI-Ns
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:49 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8KFLPvD015143
	for avt-archive@odin.ietf.org; Sat, 20 Sep 2003 11:21:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jXk-0003h7-8E; Sat, 20 Sep 2003 11:21:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0ihx-0006f7-So
	for avt@optimus.ietf.org; Sat, 20 Sep 2003 10:27:33 -0400
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19672
	for <avt@ietf.org>; Fri, 19 Sep 2003 15:35:20 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h8JIpiJ11404;
	Fri, 19 Sep 2003 14:51:45 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZX248DC; Fri, 19 Sep 2003 14:51:44 -0400
Received: from nortelnetworks.com (acart1ec.ca.nortel.com [47.129.129.121]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5M7H6; Fri, 19 Sep 2003 14:51:44 -0400
Message-ID: <3F6B503B.5070307@nortelnetworks.com>
Date: Fri, 19 Sep 2003 14:51:39 -0400
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: Kreuter Ruediger <Ruediger.Kreuter@siemens.com>
CC: michael.whitfield@mindspeed.com,
        Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: AW: [AVT] Working group last call: draft-ietf-avt-rtp-clearmode-02.txt
 - random comments
References: <7C222247E93DB64FA0078E8A4426435C286A93@mchh2g1e.mchh.siemens.de>
In-Reply-To: <7C222247E93DB64FA0078E8A4426435C286A93@mchh2g1e.mchh.siemens.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA19678
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

The 56 kbit/s usage happens in North America because the low-order bits o=
n=20
occasional frames are stolen for signalling.  I would suggest that CLEARM=
ODE ignore=20
the issue.  The gateways can sort out the situation based on signalling p=
assed=20
between them.

Kreuter Ruediger wrote:

> Thanks for your comments
> 1 and 3 is simple (see below),
> but the 2nd one needs some discussion in the working group (see below)
> =20
> Regards,
> Ruediger
>=20
...
>=20
> =09
> 	- Are 56kbps ISDN connections specifically excluded from this draft?  =
It seems to imply that you can use the 64kbps for anything you want as lo=
ng as use use all 64kbps.  Would it be useful to indicate that lower rate=
 data + padding can be passed by mutual agreement, or will that just blow=
 up into a whole mess about how to define mutual agreement.=20
>=20
> 	Ruediger: Well !
>=20
> 	- I would like to here a comment from the US members in the working gr=
oup. Is it necessary to support 56kbps, 48kbps, ... at all ? These bitrat=
es are not supported in RFC 3551 for PCMA/PCMU.
>=20
> 	- Are there other applications that need a 56 kbps (or lower) channel =
?
>=20
> 	- If necessary, is the use of fill bits the appropriate method ?
>=20
> 	- Would we start to conflict here with the N x 64 kbps work in PWE3 ?
>=20
> 	- If support of "64 - (N x 8; where 1 <=3D N <=3D ?) kbps" is necessar=
y and should be supported by the Clearmode draft, then we have at least t=
wo possibilities:
>=20
> 	1) different MIME subtypes for each bitrate (e.g. Clearmode-64, Clearm=
ode-56, etc.), as e.g. with G.726 in RFC3551
>=20
> 	2) introduction of an optional bitrate parameter (in kbps), with "64" =
as default  -> this should be synchronized with the N x 64 kbps work in P=
WE3 =20
>=20
> 	BTW: I am not a member of the PWE3 discussion list. Any answer of PWE3=
 members should be sent to avt@ietf.org too.
>=20
> 	=20
>=20
> =09
> 	- Would it be useful to define where the most and least signficant bit=
s are for each sample, or is that already defined in one of the reference=
s?=20
>=20
> 	Ruediger: this makes sense; I will copy the regarding sentence from RF=
C3551, chapter 4.5.14 (RTP Profile for PCMA/PCMU)
>=20
> 	=20
>=20
> =02b#bu=13=E0=AD=A9=EC=A6=8AZ
> x=06jbz=08m6?=0C0'~ffX)


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



From exim@www1.ietf.org  Tue Mar 30 20:01:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13783
	for <avt-archive@odin.ietf.org>; Tue, 30 Mar 2004 20:01:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8U6O-0000da-Vd
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 20:01:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V118lC002450
	for avt-archive@odin.ietf.org; Tue, 30 Mar 2004 20:01:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8U6H-0000cU-Pu; Tue, 30 Mar 2004 20:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8U5O-0000aE-Bg
	for avt@optimus.ietf.org; Tue, 30 Mar 2004 20:00:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13731
	for <avt@ietf.org>; Tue, 30 Mar 2004 20:00:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8U5M-0003CH-00
	for avt@ietf.org; Tue, 30 Mar 2004 20:00:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8U4Q-00036V-00
	for avt@ietf.org; Tue, 30 Mar 2004 19:59:07 -0500
Received: from rdu74-160-175.nc.rr.com
	([24.74.160.175] helo=berlin.arid.us ident=system)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8U3s-00031I-00
	for avt@ietf.org; Tue, 30 Mar 2004 19:58:32 -0500
Received: from madrid (madrid.arid.us [192.168.1.10])
	by berlin.arid.us (8.12.8/8.12.8) with SMTP id i2V0wPIH028654;
	Tue, 30 Mar 2004 19:58:25 -0500
Message-ID: <014a01c416bb$45f6bcb0$0a01a8c0@madrid>
From: "Paul E. Jones" <paulej@packetizer.com>
To: <avt@ietf.org>
Cc: <tamura@toda.ricoh.co.jp>
Date: Tue, 30 Mar 2004 19:58:23 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0147_01C41691.5B48C060"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_40_50,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [AVT] draft-jones-avt-audio-t38-04.txt
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0147_01C41691.5B48C060
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Folks,

I just wanted to draw your attention to this recently-revised Internet =
Draft.  This revision includes a number of parameters that need to be =
signaled via SDP.  We entered last-call on the previous publication, but =
I requested that we re-visit this document, given that the decision was =
made to make all of the parameters a part of this document.

Please review this document and provide comments to me or Hiroshi.

Best Regards,
Paul

------=_NextPart_000_0147_01C41691.5B48C060
Content-Type: text/html;
	charset="Windows-1252"
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=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Folks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I just wanted to draw your attention to =
this=20
recently-revised Internet Draft.&nbsp; This revision includes a number =
of=20
parameters that need to be signaled via SDP.&nbsp; We entered last-call =
on the=20
previous publication, but I requested that we re-visit this document, =
given that=20
the decision was made to make all of the parameters a part of this=20
document.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Please review this document and provide =
comments to=20
me or Hiroshi.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Paul</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0147_01C41691.5B48C060--


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



From exim@www1.ietf.org  Wed Mar 31 00:24:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28731
	for <avt-archive@odin.ietf.org>; Wed, 31 Mar 2004 00:24:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YD6-0001xe-N3
	for avt-archive@odin.ietf.org; Wed, 31 Mar 2004 00:24:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V5OKSm007535
	for avt-archive@odin.ietf.org; Wed, 31 Mar 2004 00:24:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YCv-0001pU-SP; Wed, 31 Mar 2004 00:24:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8XUP-0007Jv-6A
	for avt@optimus.ietf.org; Tue, 30 Mar 2004 23:38:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26307
	for <avt@ietf.org>; Tue, 30 Mar 2004 23:38:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8XUN-0000Nu-00
	for avt@ietf.org; Tue, 30 Mar 2004 23:38:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8XSK-00004e-00
	for avt@ietf.org; Tue, 30 Mar 2004 23:36:01 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8XRU-0007jA-00
	for avt@ietf.org; Tue, 30 Mar 2004 23:35:09 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2V4Z8YG029399
	for <avt@ietf.org>; Wed, 31 Mar 2004 06:35:08 +0200 (MEST)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 30 Mar 2004 13:03:06 +0200
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id H81SJ42P; Tue, 30 Mar 2004 13:03:08 +0200
Received: from ericsson.com (upcb713.uab.ericsson.se [134.138.239.202]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id H4N83AZJ; Tue, 30 Mar 2004 21:02:50 +1000
Message-ID: <40695409.2010006@ericsson.com>
Date: Tue, 30 Mar 2004 21:03:37 +1000
X-Sybari-Trust: a6ea9dff 272a6e05 0c0b63a9 00000139
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajesh Kumar <rkumar999@comcast.net>
CC: Colin Perkins <csp@csperkins.org>, rkumar@cisco.com, yaakov_s@rad.com,
        avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
References: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com> <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net> <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net> <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il> <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net> <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net> <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com> <4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
In-Reply-To: <4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Mar 2004 11:03:06.0042 (UTC) FILETIME=[9409F9A0:01C41646]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello Rajesh,

H.248 can already signal the use of Nx64k through the use of the multiplex 
descriptor.

Regards, Christian

Rajesh Kumar wrote:

> At 11:02 AM 3/26/2004 +0000, Colin Perkins wrote:
> 
>> Right - you have a pseudo-wire emulation, running multiple streams within
>> the pseudo-wire. This would seem to be a typical application for the PWE3
>> mechanisms, rather than something AVT should consider.
> 
> 
> In some applications, this places a demand for two, not one, signaling 
> mechanisms at the multimedia endpoints for RTP media e.g. SIP and PWE3 
> control. These are applications where it might set up nx64 sessions and 
> other (not necessarily simultaneous) sessions outside the pseudo-wire.
> 
> Perhaps, the PWE3 group should MIME this RTP media so that SIP and H.248 
> can be used for setting up nx64 sessions. However, if there is no 
> wide-spread demand for the SIP or H.248 signaling of the nx64 codec, the 
> vendors may define their proprietary MIMEs in the 'vnd' tree.
> 
> Rajesh
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



