[Ietf-calsify] Question about attachment

[Doug Royer]

If a new draft "iCal File Format" were the purpose of CALSIFY
and if such a draft existed, I could agree once I saw
the proposal.

However until such a document is created that also addresses
the other issues with using the ICS data format as a calendar
store, it would just be duplicating the MIME object data that
is easy to parse and understand now.

So I do agree that an iCal-File-Format draft would be useful.
I do not think that adding options to iCal at this point
is on-topic for CALSIFY.

I think we need to leave the file format for the implementation
at this point in time and continue to use MIME as the 2445
and 2446 format which already has those options.


> I agree that the ATTACH property should provide support for 
> parameters to specify information like filename and size the same way
> that RFC 2183 does for the Content-Disposition header:

Doug Royer                     | http://INET-Consulting.com
-------------------------------|-----------------------------

               We Do Standards - You Need Standards

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4532 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20051115/bd4cf7fb/smime.bin