Re: [AVT] draft-kerr-avt-vorbis-rtp-04

Arthur de Castro Callado <arthur@gprt.ufpe.br> Wed, 19 January 2005 15:25 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21663 for <avt-archive@ietf.org>; Wed, 19 Jan 2005 10:25:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrHxQ-00059Z-DT for avt-archive@ietf.org; Wed, 19 Jan 2005 10:41:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CrHdr-0002GJ-4I; Wed, 19 Jan 2005 10:21:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CrHXp-0008MO-4C for avt@megatron.ietf.org; Wed, 19 Jan 2005 10:14:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20246 for <avt@ietf.org>; Wed, 19 Jan 2005 10:14:50 -0500 (EST)
Received: from [150.161.187.80] (helo=mail.gprt.ufpe.br) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrHnH-0004tP-IX for avt@ietf.org; Wed, 19 Jan 2005 10:30:52 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.gprt.ufpe.br (Postfix) with ESMTP id 79F5929AB2C for <avt@ietf.org>; Wed, 19 Jan 2005 12:14:07 -0300 (BRT)
Received: from mail.gprt.ufpe.br ([127.0.0.1]) by localhost (mail.gprt.ufpe.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21583-08 for <avt@ietf.org>; Wed, 19 Jan 2005 12:14:06 -0300 (BRT)
Received: by mail.gprt.ufpe.br (Postfix, from userid 501) id 0126329AB2A; Wed, 19 Jan 2005 12:14:05 -0300 (BRT)
Received: from localhost (localhost [127.0.0.1]) by mail.gprt.ufpe.br (Postfix) with ESMTP id E853829EB24 for <avt@ietf.org>; Wed, 19 Jan 2005 12:14:05 -0300 (BRT)
Date: Wed, 19 Jan 2005 12:14:05 -0300
From: Arthur de Castro Callado <arthur@gprt.ufpe.br>
To: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] draft-kerr-avt-vorbis-rtp-04
In-Reply-To: <9D277E44D6EF0942B928C6F0DE99BB3164BD0C@lan-ex-01.panasonic.de>
Message-ID: <Pine.LNX.4.60.0501191205520.21640@mail.gprt.ufpe.br>
References: <9D277E44D6EF0942B928C6F0DE99BB3164BD0C@lan-ex-01.panasonic.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: by amavisd-new at gprt.ufpe.br
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Hi,

Can RFC 3385 be considered enough of a reference for CRC32 
implementations, or is it desirable to have (create) another RFC defining 
and naming all versions of CRC32 that MAY or SHOULD NOT be used in future 
IETF standards?

Thanks,
Arthur Callado.

On Tue, 18 Jan 2005, Linus Walleij wrote:

> > I don't know if there is an RFC for CRC32 that you could simply 
> > reference (after checking that it conforms to your implementation of 
> > course).
> 
> Now I know that there is RFC 3385 which carries an example 
> implementation in Verilog, sort of awkward unless you're devising 
> hardware implementations.
> 
> I'd say that SHA-1 is better for any modern software implementation, but 
> it's partly a matter of taste and opinion IMHO.
> 
> 
> Linus Walleij

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