Re: Two new Internet drafts: DIME and WS-Attachments

Prasad Yendluri <[email protected]> Tue, 9 Jul 2002 21:50:38 -0700
Newsgroups gmane.comp.windows.devel.dime
Message-ID <DIME%[email protected]>
Hi,

I am just beginning to get my head into DIME. I have couple of general
questions. I am new to the list (though not perhaps to a few folks on this)
so apologies in advance if this was answered already. I did not find this
in recent archives however.

As some that might to looking to implement DIM,

1. I am curious why these specifications are submitted to IETF?
2. The IP section seems to raise a flag for us. Should people implementing
this spec be concerned about licensing issues?
3. If there was discussion on MIME vs DIME that addresses why MIME does not
cut it (or if there is a write-up somewhere) please provide me a pointer.

Thanks in advance.

Regards, Prasad

On Fri, 28 Jun 2002 11:41:19 -0700, Henrik Frystyk Nielsen
<[email protected]> wrote:

>Two internet drafts have just been submitted to the IETF Internet Draft
>Editors:
>
>1) An updated DIME spec with revisions to the DIME record format so it
>is NOT compatible with the previous version.
>
>2) An WS-Attachments spec (formerly "SOAP in DIME") updated to match the
>new DIME spec and with several clarifications.
>
>Until the drafts become available in the IETF Internet Draft archives
>(may be a backlog because of the upcoming submission deadline), you can
>find a local copy at [1] and [2].
>
>You will note that the DIME author list includes Russell Butek and Simon
>Nash, IBM, and the WS-Attachments spec includes Joel Farrell, IBM.
>
>As always, remember that these specifications are Internet Drafts, work
>in progress, and will change as we move forward. Needless to say they
>replace the previous drafts.
>
>DIME Record Changes
>-------------------
>
>* Addition of a VERSION field at the front allowing us to move to new
>versions as need be. The field has been designed so that it will not
>conflict with existing DIME implementations.
>
>* Addition of an OPTIONS field which contains a set of elements, each
>containing a element type, length, and some data. The element types are
>centrally registered and guidelines for IANA are provided.
>
>* Changed the width of some of the fields so that more are 8/16/32-bit
>aligned
>
>Editorial Changes
>-----------------
>
>* Replaced TNF with TYPE_T (editorial only)
>
>* Updated diagrams to be 32-bit wide (also editorial)
>
>* Added conformance requirement section
>
>* Clarified handling of unknown TYPE_T (formerly TNF) values
>
>* Improved security considerations sections
>
>Think that's it - comments, questions etc are welcome on the mailing
>list!
>
>Henrik Frystyk Nielsen
>mailto:[email protected]
>
>[1]
>http://msdn.microsoft.com/library/en-us/dnglobspec/html/draft-nielsen-di
>me-02.txt
>[2]
>http://msdn.microsoft.com/library/en-us/dnglobspec/html/draft-nielsen-di
>me-soap-01.txt