Glenn Parsons (gparsons@nortelnetworks.com)
Mon, 20 Aug 2001 09:48:53 -0400
Folks,
Charles suggested a slight rewording to the IVM codec section as below.
He may issues a revised set of slides that reflect what was agreed at the
meeting.
Cheers,
Glenn.
> 6.5 Audio/wav with MS-GSM (Charles Eliot)
>
> - draft-ema-vpim-msgsm-00 (deleted)
> - draft-ema-vpim-wav-00 (deleted)
>
> The drafts have expired (and the WAV has some technical errors). Consensus
> has been reached that IVM will support both MS-GSM/WAV and G.711 (as
> audio/basic) - so we still need the MS-GSM and WAV documents.
>
> No progress on the documents has been made since San Diego, but this will
> change immediately as Charles has taken it over.
>
> The WAV document needs the technical errors corrected - and a thorough
> rewrite! RFC 2361 already defines IANA Registrations for audio/vnd.wave
> codecs. Microsoft has no issues involving intellectual property around
> RIFF and WAV.
>
> One proposal is to simplify the specification to only include what is
> needed to support IVM, rather than making it a generic definition of WAV.
> However this was rejecetd since we also need to generate something that is
> consistent with what is already in general use - which may prevent it from
> being too IVM specific (it needs, at least, to be extensible). It can
> reference existing RFCs and documents.
>
> The consensus was to create a WAV draft as general as possible consistent
> with the primary aim of establishing a defined usage for audio/wav.
> Parameter specifics for encoding MS-GSM payloads inside WAV wrappers will
> be left to the IVM draft.
>
> The MS-GSM draft seem to be technically correct. The current draft
> provides the IANA registration and documents the order/format of GSM
> encoding parameters for MS-GSM. The required definition will be for
> audio/wav not audio/ms-gsm to allow as much as possible of the existing
> deployed base to launch the correct application and to play the voice
> message correctly. Which is why this group also needs to be concerned with
> the broader definition of WAV in MIME.
>
> This draft does not describe implementation of a GSM 6.10 codec (this is
> an external document). Given that, Microsoft do not believe that there are
> any IPR issues associated with this draft.
>
> The consensus then was for the MS-GSM draft to deal narrowly with the bit
> orderings required to get a GSM payload to be recognizable to an MS-GSM
> codec, and will not define a new IANA registration for audio/ms-gsm.
>
> Charles will create the new drafts for review in 3-4 weeks. Once there is
> consensus on those drafts we can update the IVM document and last call it.
>
>
>
This archive was generated by hypermail 2.0b3 on Mon Aug 20 2001 - 16:52:33 IDT