Exchange (lailed@exchange.microsoft.com)
Wed, 4 Aug 1999 21:18:38 -0700
I agree with Keith. There is no formal WAV specification and a plethora of
implementations. To enable interoperability, it is therefore necessary to
provide a document that defines the WAV format for use in the VPIM context.
The WAV definition provided in the internet draft attempts to do just that.
Earlier versions of the VPIM v3 internet draft defined a codec parameter
that specified the codec used for the WAV encapsulated audio. Although it
provided redundant information, it provided a relatively quick way to
determine the codec used without requiring understanding of the data
encapsulation, and without the necessity of parsing the WAV chunks.
Laile
-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu]
Sent: Wednesday, August 04, 1999 6:18 PM
To: Blair Whitney
Cc: 'Keith Moore'; Graham Klyne; VPIM discussion list;
vpim@lists.neystadt.org; ietf-types@iana.org
Subject: Re: [VPIM] draft-ema-vpim-wav-00.txt
> The problem with "what people think of as WAV files" is that there are a
> variety of implementations of WAV file formatting, and the VPIM spec
should
> be as specific as possible.
right. so make the vpim be very specific as to what kind of wav files
are acceptable for the vpim context, and let the audio/wav content-type
correspond more-or-less.to "what people think of as WAV files".
i.e. make vpim-acceptable-content more rigorous than audio/wav.
if you want, define a parameter for audio/wav that indicates the
precise format and codec, define which values of that parameter are
acceptable for vpim, and insist that vpim implementations include that
parameter in mail that they generate. this won't directly help
interoperability, since it's duplicating information already present
in the wav file itself. but it might help call attention to the fact
that only certain formats/codecs of wav are valid for vpim.
think of it as a form of social engineering.
Keith
Copyright (c) 1999. Electronic Messaging Association, Inc. All rights
reserved. A member service of EMA-The Electronic Business Forum 1655
North Fort Myer Drive, Suite 500, Arlington, Virginia 22209-3108 el.
703-524-5550 Fax 703-524-5558 E-Mail: support@ema.org
This archive was generated by hypermail 2.0b3 on Tue Mar 19 2002 - 01:04:14 IDT