My unrecorded AI re: i060

[Christopher B Ferris <chrisfer@us.ibm.com>]

Herewith is the dispensation of my unrecorded
AI regarding i060 [1]

I searched through the document for
the term "reliable mess*". Interestingly enough, I found more
this time
than last. Maybe Adobe needs to fix
their find algorithm:-) I also searched (below) for "reliable delivery",
but have made no proposed changes...
that is only for discussion purposes.

For each occurance of the term, I have
listed the line number as per wd-07 [2] and the current text and 
proposed alternate text.

Reliable mess*

line 76-77: The primary goal of this
specification is to create a modular mechanism for reliable message delivery.

The primary goal of this specification
is to create a modular mechanism for reliable delivery of messages.

line 114-116: If an action IRI is used,
and one is not already defined per the rules of the WS-Addressing specification
[WS-Addressing], then the action IRI
MUST consist of the reliable messaging namespace URI
concatenated with a '/', followed by
the message element name.

If an action IRI is used, and one is
not already defined per the rules of the WS-Addressing specification
[WS-Addressing], then the action IRI
MUST consist of the WS-RM  namespace URI
concatenated with a '/', followed by
the message element name.

line 125: Reliable Messaging Model

no change

line 128-130: The WS-ReliableMessaging
specification defines an interoperable protocol that requires a Reliable
Messaging (RM) Source and Reliable Messaging
(RM) Destination to ensure that each message
transmitted by the RM Source is successfully
received by an RM Destination,

No change

line 160: Figure 1 below illustrates
the entities and events in a simple reliable message exchange.

Figure 1 below illustrates the entities
and events in a simple reliable exchange of messages.

line 161-162: The Reliable Messaging
(RM) Source accepts the message and Transmits it one or more times. 

no change

line 167: Figure 1: Reliable Messaging
Model

no change

line 198-199: The RM Source MUST assign
each reliable message a sequence number (defined below) beginning
at 1 and increasing by exactly 1 for
each subsequent reliable message.

The RM Source MUST assign each message
within a Sequence a message number (defined below) beginning
at 1 and increasing by exactly 1 for
each subsequent message.

line 204: Figure 2 illustrates a possible
message exchange between two reliable messaging endpoints A and B.

no change

line 234-236: Additionally, over-aggressive
re-transmissions have been demonstrated to cause
transport or intermediary flooding which
are counterproductive to the intention of providing a reliable
message exchange.

Additionally, over-aggressive re-transmissions
have been demonstrated to cause
transport or intermediary flooding which
are counterproductive to the intention of providing a reliable
exchange of messages.

line 693-694: The purpose of the <wsrm:SequenceFault>
element is to carry the specific details of a fault generated
during the reliable messaging specific
processing of a message belonging to a Sequence.

no change

line 779-780: However, it is recommended
that the security context be established
first.Security contexts are independent
of reliable messaging Sequences.

no change

line 796-803: That is, one aspect of
security is to prevent message replay and the core tenet of
reliable messaging is to replay messages
until they are acknowledged.Consequently, if the security subsystem
processes a message but a failure occurs
before the reliable messaging sub-system records the
message (or the message is considered
"processed"), then it is possible (and likely) that the security
subsystem
will treat subsequent copies as replays
and discard them.At the same time, the reliable messaging
sub-system will likely continue to expect
and even solicit the missing message(s).Care should be taken to
avoid and prevent this rare condition.

no change

line 816: Availability – All reliable
messaging services are subject to a variety of availability attacks.

no change

Reliable delivery

line 78-79: It defines a messaging protocol
to identify, track, and manage the reliable delivery of messages between
a source and a destination.

line 160-161: First, the Application
Source Sends a message for reliable delivery.

line 184: Send: The act of submitting
a message to the RM Source for reliable delivery.

line 447-448: The RM protocol uses a
<wsrm:Sequence> header block to track and manage the reliable delivery
of
messages.

[1] http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i060
[2] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/15789/wsrm-1.1-spec-wd-07.pdf

Cheers,

Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://webpages.charter.net/chrisfer/blog.html
phone: +1 508 377 9295