RE: [ebxml-msg] Groups - ebXML Messaging TC weekly call added

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

The details of resending belong to the reliability function, but none of
the existing reliability (RM)specification(s) specify or even
parameterize such a feature which is left to implementation decision.
(the RM specs mostly focus on the major delivery assurances, and on
everything that affect interoperability, and this does not. Even the
parameters for controling resnding were left out, because there was so
many options that couldn't be all covered, while not affecting interop.)

This means some RM implementations may support this , some won't.
Specifying this behavior at MSH level (above the RM function) would
create problems with the elimination of duplicates.
I believe the best way to address this is in a "deployment profile" that
defines details of usage and of deployment of an MSH for a particular
user community, as well as required properties of an implementation.
Deployment profiles handle everything that comes on top of the "base
spec" - best practices, domain-specific extensions, implementation-level
features, etc.
(the IIC produced templates for defining ebMS2 deployt profiles, used by
eAC, HL7, EAN/UCC, RosettaNet...)

Jacques

-----Original Message-----
From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com] 
Sent: Thursday, February 22, 2007 9:14 AM
To: ebxml-msg@lists.oasis-open.org
Subject: FW: [ebxml-msg] Groups - ebXML Messaging TC weekly call added

Team,

      for info from yesterdays call this was the start of the discussion
of a potential 2nd level retry for long outages etc.

Ian

-----Original Message-----
From: Kailar, Rajashekar . (CDC/CCHIS/NCPHI) (CTR) [mailto:rok9@CDC.GOV]

Sent: 21 February 2007 20:10
To: Jones,IC,Ian,XDT63 R
Subject: RE: [ebxml-msg] Groups - ebXML Messaging TC weekly call added

Hi Ian,

I will not be able to make it to the TC meeting today. Here is one point
I wanted to bring up:

Within the CDC PHINMS, we have a feature called "delayed retry". This is
done by a "Message Sender" when a "Message Receiver" is down for an
extended period of time (i.e., after a certain number of retries are
unsuccessful). Basically, the message is kept in a cache and we attempt
it after a long delay (say a few hours or a day). This is useful to
handle network failures. 

I realize that regular retries using the same conversation ID etc are
part of the spec. Is the above kind of delayed retry part of the
"guaranteed delivery" specification? If not, it may be a useful
addition.

Thanks,
Raja

-----Original Message-----
From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com]
Sent: Wednesday, February 21, 2007 7:32 AM
To: ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Groups - ebXML Messaging TC weekly call added


ebXML Messaging TC weekly call has been added by Mr Ian Jones

Date:  Wednesday, 21 February 2007
Time:  02:30pm - 04:00pm PT

Event Description:
ebXML Messaging TC weekly call 

Tel: 1-620-782-2200
Pass code 120905

Agenda:
1. Role
1a.  Approval of previous minutes
2. New Issues
    None posted
3. Non-repudiation issues from JC
4. Webinar - OASIS is trying to arrange a sequnce of web presentations
on ebXML.  The TC has been asked to contribute 5. Review of outstanding
issues 6. A.O.B.


Minutes:


View event details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_i
d=14391

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able
to copy and paste the entire link address into the address field of your
web browser.

Referenced Items
Date            Name                             Type
----            ----                             ----
2007-02-19      MessagingTC021407.htm            Minutes