OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: NEW ISSUE: How can RMS communicate the Base Retransmission Interval, Exponential Backoff and Inactivity Timeout values?


Title: NEW ISSUE: How can RMS communicate the Base Retransmission Interval, Exponential Backoff and Inactivity Timeout values?

Title: How can RMS communicate the Base Retransmission Interval, Exponential Backoff and Inactivity Timeout values?

Description:

Currently the WS-RM Policy Assertion specification describes four distinctive assertion parameters in Section 2.1 [1]: Base Retransmission Interval, Exponential Backoff, Inactivity Timeout and Acknowledgement Interval. Further, these parameters are scoped with respect to two distinct roles as summarized below:

RMS:
-- Base Retransmission Interval (BRI)
-- Exponential Backoff (EB)
-- Inactivity Timeout (IT)

RMD:
-- Inactivity Timeout (IT)
-- Acknowledgement Interval (AI)

The specification makes the above distinction and allows both the RMS and the RMD to include their respective parameters. However, it is not clear "where" these parameters would be included and "how" they would be communicated between the RMS and RMD. Specifically, the current RM Assertion element appears to apply only to a WSDL which enables the RMD to communicate it assertions. However, it is not clear how the RMS can express and communicate its RM Assertion parameters.

Justification:

Although the specification defines certain parameters with respect to a role, namely the RMS, it is not clear how they would be expressed and communicated. This makes the specification incomplete and unusable from the perspective of RMS.  For example, it is impossible for an RMS to configure its system once with parameters that suits its own needs and allow these parameters to be negotiated with the RMD.

Target: policy

Type: design

Proposal:

Scope the RM Assertion parameters on a per Sequence basis and utilize the CreateSequence message exchange for communicating RM Assertion parameters between the RMS and the RMD.

Detailed proposal: TBD.

Related Issues:

References:

[1] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14793/wsrmp-1.1-spec-wd-01.pdf


----------------------

Dr. Umit Yalcinalp
Standards Architect
NetWeaver Industry Standards
SAP Labs, LLC
umit.yalcinalp@sap.com
Tel: (650) 320-3095



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]