RE: [Sipping] RE: draft-stein-great-00.txt

"Yaakov Stein" <yaakov_s@rad.com> Sat, 08 October 2005 18:13 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOJCm-0007N6-69; Sat, 08 Oct 2005 14:13:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOJCk-0007Ms-8m for sipping@megatron.ietf.org; Sat, 08 Oct 2005 14:13:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05245 for <sipping@ietf.org>; Sat, 8 Oct 2005 14:13:51 -0400 (EDT)
Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOJM9-0006tF-U8 for sipping@ietf.org; Sat, 08 Oct 2005 14:23:45 -0400
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 j98IAKYR024447 for <sipping@ietf.org>; Sat, 8 Oct 2005 20:10:22 +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 j98IAJLx024441; Sat, 8 Oct 2005 20:10:19 +0200 (IST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] RE: draft-stein-great-00.txt
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Sat, 08 Oct 2005 21:15:18 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A5201860FFE@exrad2.ad.rad.co.il>
Thread-Topic: [Sipping] RE: draft-stein-great-00.txt
Thread-Index: AcXKwMgxOhac20TbQFKnpzySJwalJAAg+FOwAA0bnCAAMKv55g==
From: Yaakov Stein <yaakov_s@rad.com>
To: henry@pulver.com
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: gherlein@herlein.com, Roar Hagen <roar.hagen@globalipsound.com>, wolfgang.beck01@t-online.de, Alan Duric <alan.duric@telio.no>, Sipping <sipping@ietf.org>, simon.morlat@linphone.org, jean-marc.valin@hermes.usherb.ca
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0839811422=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

> The assertion on codecs is quite amazing, 
> if it is meant as a reproach to the IETF.

No reproach intended - quite the opposite!
I am saying that the IETF is precisely the place to do this work.

>>Only the IETF has the motivation to design a codec for:
>>1) no 4kHz (or 8kHz) limitation
>>2) high perceptual quality (not "toll quality")
>>3) not necessarily CBR
>>4) low delay
>>5) resilient to bursty packet loss

>The IETF has published RFCs on the iLBC audio codec, and is doing a lot of
>other work in this area.

>- RFC 3951: Internet Low Bit Rate Codec (iLBC)

>- RFC 3952: Real-time Transport Protocol (RTP) Payload Format for internet
> Low Bit Rate Codec (iLBC) Speech

>- RTP Payload Format for the Speex Codec
> <draft-herlein-speex-rtp-profile-02>

I don't see the connection.
Other than the iLBC codec description
(which is said to have been done in AVT, but in reality
was published as an RFC but there was little technical discussion
on the details of the coedc design in the AVT WG)
the others are pure encapsulation documents.
 
What does that have to do with what we are talking about?

> The I-D <draft-stein-great-00.txt> could indeed use the council given
> earlier on this discussion trail:

>please remove the PSTN nostalgia from the document

>...and I would add; to any similar memos wherever they may be presented.

As I have already written in a previous email,
this is not nostalgia - it is the present state-of-the-art.
And the comparison is routinely discussed in other forums
(e.g. the FGNGN).
 
If you want to close your eyes to user expectations,
go ahead, but then nothing is going to improve.
 
Y(J)S
 
 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP