Greg (gregv@lucent.com)
Thu, 14 Feb 2002 12:59:36 -0700
I offer my appologies for the delay in responding to these comments.
I offer the following as an an applicability statement. I envision this in
section 1.3, part of the introduction.
"VPIM is intended for the exchange of voice messages between traditional
voice messaging systems and for systems that need to interoperate with such
systems. VPIM is intended connect voice messaging systems into
special-purpose voice messaging networks. VPIM may also be used between
message store servers and VPIM-aware clients such as web servers and TUI
clients. VPIM is not intended or optimized for downloading to, or sending
from commercial email clients.
Internet Voice Messaging is intended to enable commercial email clients to
send and receive voice content through general-purpose message stores in an
interoperable way. IVM may also be a suitable format for downloading voice
messages from a VPIM server to a commercial email client. It may also be a
suitable format for submission of a voice message from a commercial client
into a VPIM system."
IF this is acceptable, I will submit a new version to the ID editors
shortly.
I will submit revised versions of -dur and -32k with a section indicating
changes from the previous version. The -32K version will have corrected
formatting.
Greg V.
-----Original Message-----
From: ned.freed@mrochek.com [ <mailto:ned.freed@mrochek.com>
mailto:ned.freed@mrochek.com]
Sent: Monday, January 28, 2002 8:29 PM
To: vpim@lists.neystadt.org
Cc: paf@cisco.com; ned.freed@mrochek.com
Subject: [VPIM] IESG feedback for VPIMv2 doc set
The IESG is concerned that draft-ietf-vpim-vpimv2r2-04.txt
does not contain an explicit applicability statement. It is
the IESG's understanding that this messaging service profile
is intended to be used between voice messaging systems while
the upcoming IVM work is the profile intended to be used
to communicate with desktop system. If so, this document
needs to avoid confusion by stating what its domain of
applicability is.
Neither draft-ietf-vpim-vpimv2r2-dur-01.txt nor
draft-ietf-vpim-vpimv2r2-32k-02.txt indicate what, if
anything, has changed since the previous version. Simply
adding a statement to the effect that "the only changes
between this document and RFC xxxx are editorial in nature"
would address this.
RFC 2422 says:
+--+--+--+--+--+--+--+--+
|B3|B2|B1|B0|A3|A2|A1|A0|
+--+--+--+--+--+--+--+--+
MSB -> | 7| 6| 5| 4| 3| 2| 1| 0| <- LSB
+--+--+--+--+--+--+--+--+
32K ADPCM / Octet Mapping
draft-ietf-vpim-vpimv2r2-32k-02.txt says:
+--+--+--+--+--+--+--+--+
|B3|B2|B1|B0|A3|A2|A1|A0|
+--+--+--+--+--+--+--+--+
MSB -> | 7| 6| 5| 4| 3| 2| 1| 0| <- LSB
+--+-- --
32K ADPCM / Octet Mapping
This is a minor issue, but there's probably no reason not to fix it to be
+--+--+--+--+--+--+--+--+
|B3|B2|B1|B0|A3|A2|A1|A0|
+--+--+--+--+--+--+--+--+
MSB -> | 7| 6| 5| 4| 3| 2| 1| 0| <- LSB
+--+--+--+--+--+--+--+--+
32K ADPCM / Octet Mapping
This archive was generated by hypermail 2.0b3 on Thu Feb 14 2002 - 22:00:30 IST