MIME-type Review Request: draft-ietf-simple-event-list-05.txt

[Larry Masinter]

> http://www.ietf.org/internet-drafts/draft-ietf-simple-event-list-05.txt


# Optional parameters: charset

#      See RFC 3023 [11] for a discussion of the charset parameter on
#      XML-derived MIME types.  Since this MIME type is used exclusively
#      in SIP, the use of UTF-8 encoding is strongly encouraged.

Not using UTF-8 might be a serious 'interoperability' consideration,
then? 

#  Security considerations: Security considerations specific to uses of
#      this this MIME type are discussed in RFC xxxx [[Note to RFC
#      editor: replace xxxx with the RFC number of this document when
#      published]].  RFC 1874 [10] and RFC 3023 [11] discuss security
#      issues common to all uses of XML.

I don't see a discussion of the security considerations specifically
of this MIME type. What are the risks of someone creating a bogus
rlin? None?

#   Published specification: RFC xxxx [[Note to RFC editor: replace xxxx
#      with the RFC number of this document when published]]

It looks like Section 5.1 has the actual schema, and this kind
of MIME body never appears except as the first part of a multipart/related?
Is that intended? Is there ever a case where there are no other
parts?

#   Interoperability considerations: The use of this MIME body is
#      intended to be generally interoperable.  No unique considerations
#      have been identified.

Is this because of the Intended usage: Limited Use?

Larry
-- 
http://larry.masinter.net