NEW ISSUE: Case of multiple RM Policies and DAs within an RMD scope

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

Title: Case of multiple RM Policies and DAs within an RMD scope

 

Description: As the 1-1 relationnship between RMD and port (or RMD-WSDL) is no longer required (i010 allows RMS and RMD to span several endpoints) the specification needs be clearer on how RM Policies apply, as an RMD will handle messages and sequences that are subject to different RM policies - meaning protocol parameters as well as DAs.

 

 

Justification: RM policy parameters are so far attached to the endpoint, while they actually concern the RMD behavior, and this may cause an issue if one RMD serves several ports with different policy parameters. Regarding DAs, same 1-n issue: an RMD must be able to handle messages according to different DAs. While the DA to be enforced on a message can be resolved separately from protocol concerns (e.g. based on endpoint info), that would require looking at extra headers if this RMD is deployed as an intermediary. Also that would not work if DAs are to be attached at a finer granularity

than endpoint (e.g. message or operation).

 

 

Target: all

 

Type: design

 

Proposal:

Associate more explicitly policies (and DAs) with sequences, e.g. either in CreateSequence, or CreateSequenceResponse, so that an RMD can apply different policies to different sequences just based on sequence ID.