We need to consider Encapsulation again. This has a
number of potential uses:
Encryption
(encrypt the entire document including MIME headers)
Forwarding/Multi-hop (especially with the identified problems with
Signatures)
Third-Party Processing (Intermediate Timestamps...)
Chunking
(sending extremely large files in pieces)
I am sure there will be others.
We used this concept in the UCC Interop test to do
encryption and it worked
quite well. See
document attached.
Regards,
David Fischer
Drummond Group.
-----Original Message-----
From:
ian.c.jones@bt.com [mailto:ian.c.jones@bt.com]
Sent: Wednesday, April 10, 2002 9:52 AM
To: ebxml-msg@lists.oasis-open.org
Subject:
[ebxml-msg] What Next?
Team,
I hope you have
all had a pleasant break over the last couple of
weeks. As the title says what do we do next? It is up to
you, but here are
some ideas to start with.
1 - we MUST capture, answer and resolve any question and
issues during the 3
month public review of version
2.0
2 - The IIC TC would like to produce a
conformance test/suite/documentation
for version
2.0, they will obvious need help from us to do this.
3 - The Business interface layer has never been written - do we need
it?
4 - A primer/introduction to the messaging
service
5 - A document to describe the minimum
implementation. This may be linked
to the IIC
TC point above.
Question: - Do we still have outstanding requirements that
still need to be
addressed? i.e. a definable
business need for them.
Over to all of
you for comments.
Ian Jones
Chair OASIS ebXML
Messaging Services TC
Email: ian.c.jones@bt.com
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>