Subject: RE: [ws-rx] NEW ISSUE - No indication of how to process NACKs in normal case
From: Doug Davis [mailto:firstname.lastname@example.org]
Sent: Wednesday, September 07, 2005 6:37 AM
Subject: Re: [ws-rx] NEW ISSUE - No indication of how to process NACKs in normal case
+1 - although I'd prefer it to be a MUST to be consistent with the text for AckRequested - but since its really up to the RMS to determine when to do it anyway its not a huge thing.
"Winkler, Steve" <email@example.com>
09/06/2005 02:54 PM
To <firstname.lastname@example.org> cc Subject [ws-rx] NEW ISSUE - No indication of how to process NACKs in normal case
Here's a description of the new issue I wanted to raise from the discussion of the related issue i005 .
Title: Processing model of NACKs
Description: Although it is assumed that a NACK will trigger retransmission of a given message from the source to the destination there is no wording in the current version of the spec that describes this feature adequately.
Justification: This will clarify to implementers the spriit of the spec by spelling out in more concrete terms what is currently only implied.
Add the following to the spec directly before the text that is incorporated as a resolution to i005:
Upon the receipt of a Nack, an RM Source SHOULD retransmit the message identified by the Nack as soon as possible.