AD review comments on VPIM IVM documents

[email protected] Thu, 06 Feb 2003 22:29:56 -0800 (PST)
Newsgroups gmane.ietf.vpim
Message-ID <[email protected]>
Review comments on draft-ietf-vpim-ivm-goals-03.txt:

The VPIM acryonym needs to be expanded in the abstract.

References need to be split into normative and informative groups.

The [CODES] reference should be updated to point at RFC 3463.

Review comments on draft-ietf-vpim-ivm-04.txt:

The VPIM acryonym needs to be expanded in the abstract.

Section 4 states, in part:

  Any content type is permitted in a message, but the top level content 
  type on origination of a new, forwarded or reply voice message SHOULD 
  be multipart/mixed. If the recipient is known to be VPIM v2 compliant 
  then multipart/voice-message MAY be used instead (in which case all 
  the provisions of [VPIMV2R2] MUST be implemented in constructing the 
  message).

This places certain constraints on senders but none on receivers. I would like
to see some requirements placed on receivers. A minimum would be a reference to
RFC 2049's requirements for multipart handling.

Section 8 states, in part:

  In the absence of such recipient  knowledge, sending implementations MUST use
  raw G.711 mu-law l  indicated with a MIME content type of "audio/basic" and
  with a  filename parameter that ends ".au" [G711],[MIME2].

Do we really want to require a content-disposition filename parameter ending
in .au? I'd be a lot more comfortable with making this a SHOULD.

Refences need to be split into normative and informative groups.

[CRITICAL] should be updated to refer to RFC 3459.

[DSN] should be updated to refer to RFC 3461. Also, should RFCs 3462-3464 also
be referenced since they are all part of NOTARY that needs to be supported?

[HINT] should be updated to refer to RFC 3458.

This document is missing the IPR boilerplate required in standards track
documents by RFC 2026 section 10.4.

That's it!

				Ned

----------------------------------------------------------
This message was sent to you, since you are subscribed to
[email protected]. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo