[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: T2 Non repudiation and MSG, CPP/A, BPSS spec alignment
Resending due to addressing errors. EVERYONE: There is at least one thread running that has incorrect addresses for ebxml-CPPA and ebxml-MSG. Please check your replies and let's try to stamp out the error. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com ************************************************************************************* ---------------------- Forwarded by Martin W Sachs/Watson/IBM on 09/03/2001 09:44 PM --------------------------- Martin W Sachs 09/03/2001 09:12 PM To: David RR Webber - XMLGlobal <Gnosis_@compuserve.com> cc: Arvola Chan <arvola@tibco.com>, ebtwg@lists.ebtwg.org, ebxml-cppa@oasis-open.org, ebxml-msg@oasis-open.org, Duane Nickull <duane@xmlglobal.com>, christopher ferris <chris.ferris@east.sun.com> From: Martin W Sachs/Watson/IBM@IBMUS Subject: Re: T2 Non repudiation and MSG, CPP/A, BPSS spec alignment (Document link: Martin W. Sachs) The CPP information in the registry may or may not be able to resolve the missing information. A CPP may have information covering several different business collaborations. In that case, it would not be clear which information to use. It is the process of CPA composition and negotiation that pins the configuration information down to that agreed to by the two parties for a particular collaboration. In any case, if a partner is attempting to install a CPA template, there may or may not also be a CPP from which to fill the gaps. My point was that adding elements to the header just to cover the case where the CPA is incomplete is not the right approach for the MSG team. The general philosophy should be that if a pair of partners do not want to use a CPA, they are responsible for configuring their systems compatibly by other means. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com ************************************************************************************* David RR Webber - XMLGlobal <Gnosis_@compuserve.com>@compuserve.com> on 09/03/2001 10:29:06 AM To: Martin W Sachs/Watson/IBM@IBMUS cc: Arvola Chan <arvola@tibco.com>, ebtwg@lists.ebtwg.org, ebxml-cppa@oasis-open.org, ebxml-msg@oasis-open.org, Duane Nickull <duane@xmlglobal.com>, christopher ferris <chris.ferris@east.sun.com> Subject: Re: T2 Non repudiation and MSG, CPP/A, BPSS spec alignment Message text written by Martin W Sachs > Chris: When the Messaging Service is used in conjunction with some CPA template, rather than a bilateral CPA, then endpoint information may not be available and has to be explicitly supplied in the message header. I would recommend that the To Party MSH not be obligated to report security errors back to the From Party MSH. The former should have the option of just logging the securty error internally and then silently dropping the message. -Arvola< >>>>>>>>>>>>>>>>> Surely you should reference the partners' CPP in the Registry to access that information - if your system does not have it cached locally already. The CPP does have the pointer to the TRP configuration information. DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC