[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: draft issue list 45
Sorry for not getting the issue list updated, here is an
interim copy until after today’s call. I will get an update posted today.
(Note: This does not reflect the editors work on the pending issues from last
week, I’ll catch those and other updates after the call today.) |
Date: 2006/07/06
Revision: 45
core | soap | wsdl | policy | schema | all | total | |
---|---|---|---|---|---|---|---|
unassigned | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
active | 12 | 0 | 0 | 0 | 0 | 0 | 12 |
pending | 15 | 0 | 0 | 0 | 0 | 0 | 15 |
done | 31 | 0 | 0 | 2 | 0 | 0 | 33 |
deferred | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
resolved | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
closed | 57 | 0 | 1 | 6 | 4 | 3 | 72 |
dropped | 14 | 1 | 0 | 3 | 0 | 0 | 18 |
total | 129 | 1 | 1 | 11 | 4 | 3 | 150 |
id | owner | title | target | type | ||
---|---|---|---|---|---|---|
i113 | Jacques Durand | Tightening up the state tables | core | design | * | |
i121 | Gilbert Pilz | security threats and requirements | core | design | * | |
i122 | Gilbert Pilz | security profiles | core | design | * | |
i123 | Gilbert Pilz | security profile agreement | core | design | * | |
i124 | Gilbert Pilz | security composition policy | core | design | * | |
i134 | Update acknowledgements | core | editorial | |||
i139 | Inappropriate Fault destination | core | design | * | ||
i140 | Bob Freund | add sub-headings to fault descriptions | core | editorial | * | |
i143 | Bob Freund | messages have to be received for them to be examined | core | editorial | * | |
i144 | Bob Freund | RMS MessageNumberRollover behavior unclear | core | editorial | * | |
i145 | Bob Freund | Implications of Sequence Expiration not specified | core | editorial | * | |
i147 | Matthew Lovett | Extensibility (or not) of the Protocol Elements | core | editorial | * |
id | owner | title | target | type | ||
---|---|---|---|---|---|---|
i125 | Paul Fremantle | Protocol precondition requires knowledge of policies | core | design | ||
i126 | Chris Ferris | unclear text regarding wsa:Action | core | design | ||
i127 | Doug Davis | Make Accept/AcksTo consistent | core | design | ||
i129 | Doug Davis | Define "discard" | core | design | ||
i130 | Doug Davis | what does ack interval refer to | core | design | ||
i133 | Marc Goodner | Duplicate text in fault section | core | editorial | ||
i135 | Editors | Consistent use of wsrm: in normative text | core | editorial | ||
i136 | Editors | RM SeqID Globally Unique | core | editorial | ||
i137 | Anish Karmarkar | No mechanisms to convey that messages should be polled. | core | design | ||
i138 | Editors | Offer/Accept elements are incomplete | core | editorial | ||
i141 | Bob Freund | Sec 3.3 fault response to TerminateSequenceRequest is not specified. | core | editorial | ||
i142 | Bob Freund | Sec 3.5 Request Acknowledgement text assumesSequence is known | core | editorial | ||
i148 | Matthew Lovett | Reword the Abstract | core | editorial | ||
i149 | Peter Niblett | Define the syntax used to refer to elements and attributes | core | editorial | ||
i150 | Umit Yalcinalp | Define the syntax used to refer to elements and attributes | core | editorial |
id | owner | title | target | type | ||
---|---|---|---|---|---|---|
i007 | Marc Goodner | WSS 1.0/1.1 token support | core | design | ||
i021 | Jacques Durand | An RM Policy applies two-way | policy | design | ||
i042 | Anish Karmarkar | Which version of WS-Addressing spec? | core | design | ||
i061 | Doug Davis | Anonymous AcksTo | core | design | ||
i089 | Doug Davis | suggest the restricted use of anonymous URI | core | design | ||
i090 | Daniel Millwood | Use of offered sequences unclear in current spec | core | design | ||
i091 | Bob Freund-Hitachi | Unexpected UnknownSequenceFault or SequenceTerminatedFault | core | design | ||
i092 | Anish Karmarkar | Where is the SequenceAcknowledgement sent on receipt of AckRequested header? | core | design | ||
i093 | Doug Bunting | 2119 terms apply to implementations, not message (document) instances | core | editorial | ||
i096 | Bob Freund | Complete the state tables | core | design | ||
i097 | Marc Goodner | Extensibility of RM assertion needs to be defined | policy | editorial | ||
i098 | clarify difference between "sequence" and "non-sequence" faults | core | editorial | |||
i099 | Correlating faults to Sequences using SOAP 1.1 | core | design | |||
i100 | Matthew Lovett | Language for faultstring elements | core | editorial | ||
i101 | Paul Fremantle | Recommend RMD Close rather than Terminate | core | design | ||
i103 | Paul Fremantle | Remove the Partial Answer Mode (PAM) | core | design | ||
i104 | Paul Fremantle | Mixing SOAP versions | core | design | ||
i105 | Paul Fremantle | Sequence Acks on all messages after close | core | editorial | ||
i106 | Bob Freund | SequenceAcknowledgement:Final assumption of deliverability | core | design | ||
i107 | Bob Freund | Nacks ack as well as Nack | core | design | ||
i108 | Chris Ferris | misplaced guidance on fault handling | core | editorial | ||
i109 | Chris Ferris | The description of the <Sequence/> element could use some wordsmithing | core | editorial | ||
i110 | Chris Ferris | Chris' Rants (on RM) part 1 | core | editorial | ||
i111 | Paul Fremantle | Sequence state in event of MessageNumberRollover | core | design | ||
i112 | Chris Ferris | dangling reference to RMAssertion acknowledgement timing params | core | design | ||
i114 | Christopher B Ferris | Figure 2 (cd3) is out of date with the changes to the potocol | core | design | ||
i116 | Doug Davis | Add Max Msg Num to Message Number Rollover Fault | core | design | ||
i117 | Anish Karmarkar | Issue 21 resolution text contains language about 'parameters' which don't exist | core | design | ||
i118 | Chris Ferris | misuse of request term | core | editorial | ||
i119 | Doug Davis | When to piggy-back RM headers | core | editorial | ||
i120 | Gilbert Pilz | misplaced paragraph on action IRI's | core | editorial | ||
i131 | Remove sections 1.1 and 1.1.1 | core | editorial | |||
i132 | Change default value of fault uri | core | design |
id | owner | title | target | type |
---|
id | owner | title | target | type |
---|
id | owner | title | target | type | ||
---|---|---|---|---|---|---|
i001 | Lei Jin | Bilateral sequence negotiation | core | design | ||
i002 | Anish Karmarkar | AckTo EPR and seq lifetime | core | design | ||
i003 | Anish Karmarkar | EPRs and sequence scope | core | design | ||
i004 | Marc Goodner | wsa:messageID uniqueness requirments for retransmission | core | design | ||
i005 | Steve Winkler | Source resend of nacks messages when ack already received | core | design | ||
i006 | Tom Rutt | Source based delivery QoS policy assertion | core | design | ||
i008 | Tom Rutt | Policy assertions granularity | policy | design | ||
i009 | Chris Ferris | Declaration of QoS policies | core | design | ||
i010 | Doug Davis | Sequence port spanning | core | design | ||
i011 | Doug Davis | Typo in expires P0S | core | editorial | ||
i012 | Lei Jin | Anonymous acksTo | soap | design | ||
i013 | Doug Davis | Max message number in policy | core | design | ||
i014 | Gilbert Pilz | Document Names | core | editorial | ||
i015 | Gilbert Pilz | Required Artifact Metadata | core | editorial | ||
i016 | Gilbert Pilz | Document Identifiers | core | editorial | ||
i017 | Gilbert Pilz | XML Namespace URIs | schema | editorial | ||
i018 | Doug Bunting | Is an implementation supporting a smaller max message number valid? | core | design | ||
i019 | Jacques Durand | Sequence termination on Fault | core | design | ||
i020 | Tom Rutt | Semantics of "At most once" Delivery assurance | all | design | ||
i022 | Vikas Deolaliker | RM Policy Assertion Model's Base Retransmission Interval Clarification Needed | policy | design | ||
i023 | Marc Goodner | Robust recovery from low-resource conditions | core | design | ||
i024 | Ashok Malhotra | WS-RX policies not manifested on the wire | policy | design | ||
i025 | Chris Ferris | What is the correct form of SeqAck when RMD has received no messages | core | design | ||
i026 | Jacques Durand | better support in handling space-greedy sequences | core | design | ||
i027 | Andreas Bjärlestam | InOrder delivery assurance spanning multiple sequences | core | design | ||
i028 | Jacques Durand | Accurate final acknowledgement of a Sequence with gaps when RMS decides to stop using it | core | design | ||
i029 | Gilbert Pilz | Remove dependency on WS-Security | core | design | ||
i030 | Chris Ferris | What are the obligations on RMD for use (or not) of Offered Sequence? | core | design | ||
i031 | Chris Ferris | Inconsistency between spec and schema (AckRequested) | schema | editorial | ||
i032 | Chris Ferris | Protocol serialization optimization proposal | core | design | ||
i033 | Steve Winkler | Processing model of NACKs | core | design | ||
i034 | Daniel Millwood | If a fault is generated whilst processing a piggy-backed AckRequested or SequenceAcknowledgement header, should this stop processing of the entire message? | core | design | ||
i035 | Umit Yalcinalp | What does 'anon' URI mean when used in AcksTo EPR? | core | design | ||
i036 | Anish Karmarkar | Duplicate detection of wsrm:CreateSequence messages | core | design | ||
i037 | Anish Karmarkar | WS-Addressing Endpoint redefined in WSRM | core | editorial | ||
i038 | Anish Karmarkar | 2396 is obsoleted by 3986 | core | editorial | ||
i039 | Anish Karmarkar | What does 'have a mustUnderstand attribute' mean? | core | editorial | ||
i040 | Anish Karmarkar | Change 'optional' and 'required' in section 3 to RFC 2119 OPTIONAL and REQUIRED | core | editorial | ||
i041 | Anish Karmarkar | Presence of NACK and ACK range in the same message | core | editorial | ||
i043 | Anish Karmarkar | Why is wsa imported in the WSDL? | wsdl | editorial | ||
i044 | Anish Karmarkar | SequenceFault element refers to fault code rather than fault [Subcode] | core | editorial | ||
i045 | Anish Karmarkar | Why is SecureConversation a normative reference? | core | editorial | ||
i046 | Anish Karmarkar | Schema type of wsrm:FaultCode element can be changed from xs:QName to wsrm:FaultCodes | schema | editorial | ||
i047 | Doug Davis | Reorder spec sections | core | editorial | ||
i048 | Doug Davis | CloseSequenceResponse and Acks | core | design | ||
i049 | Tom Rutt | Allignment and refinement of defintions for DA | core | design | ||
i050 | Marc Goodner | spec talks about delivery assurances but does not clearly relate them to the protocol | core | design | ||
i051 | Chris Ferris | Presence of multiple <SequenceAcknowledgement> headers for same Sequence in the same message | core | editorial | ||
i052 | Umit Yalcinalp | Should DA be separate assertion or parameter | policy | design | ||
i053 | Umit Yalcinalp | Which occurances within the specs, if any, of the term "URI" need to be replaced with "IRI"? | core | editorial | ||
i054 | Umit Yalcinalp | Target of RM Assertion parameters are confusing with respect to how they are specified and attached | policy | design | ||
i055 | Marc Goodner | Whose Inactivity Timeout is it anyway? | policy | design | ||
i056 | Chris Feris | How can RMS communicate the Base Retransmission Interval, Exponential Backoff and Inactivity Timeout values? | policy | design | ||
i057 | Umit Yalcinalp | Classification of References (normative vs. non-normative) is needed | core | design | ||
i058 | Tom Rutt | State Transition Table | core | editorial | ||
i059 | Bob Freund | Retransmission behavior | core | design | ||
i060 | Jacques Durand | Definition for "Reliable Message" | core | editorial | ||
i062 | Doug Davis | None AcksTo | core | design | ||
i063 | Doug Davis | SeqAck - None and Final | schema | editorial | ||
i064 | Umit Yalcinalp | Create Sequence Refused Fault is too restrictive | core | design | ||
i065 | Matthew Lovett | Reword "Closing a Sequence" section | core | editorial | ||
i066 | Doug Davis | Remove LastMessage | core | design | ||
i067 | Doug Davis | Replace 'response' | core | editorial | ||
i068 | Doug Davis | Remove 'correlation' text | core | editorial | ||
i069 | Doug Davis | MessageNumber on AckReq | core | design | ||
i070 | Marc Goodner | Receive is defined twice in wsrm-1.1-spec-cd-01 | core | editorial | ||
i071 | Marc Goodner | Editorial nits for wsrm-1.1-spec-cd-01 | core | editorial | ||
i072 | Marc Goodner | Editorial nits for wsrmp-1.1-spec-cd-01 | policy | editorial | ||
i073 | Marc Goodner | Descriptive text of removed parameters also needs to be removed | policy | editorial | ||
i074 | Sanjay Patil | Use of [tcShortName] in artifact locations namespaces, etc | all | editorial | ||
i075 | Umit Yalcinalp | Case of multiple RM Policies and DAs within an RMD scope | core | design | ||
i076 | Matt Lovett | Semantics of offered Sequences | core | design | ||
i077 | Matt Lovett | How does a RM Destination reject an offered Sequence? | core | design | ||
i078 | Bob Freund | Lost TerminateSequence | core | design | ||
i079 | Bob Freund | SequenceClosed fault and SequenceAcknowledgement(Final) | core | editorial | ||
i080 | Anish Karmarkar | Remove ambiguity about the protocol being at least once on the wire | core | editorial | ||
i081 | Jacques Durand | RMS lacks support for InOrder | core | design | ||
i082 | Jacques Durand | Level of "response message" unclear, for SequenceResponse | core | design | ||
i083 | Tom Rutt | Fault Messages for Terminated Sequence | core | editorial | ||
i084 | Matthew Lovett | RMS state table and SequenceClosedFault | core | editorial | ||
i085 | Matthew Lovett | CloseSequence element is inconsistent | core | design | ||
i086 | Paul Fremantle | Alternative approach for MaxMessage | core | design | ||
i087 | Paul Fremantle | Acknowledgement Interval in CreateSequenceResponse | core | design | ||
i088 | Chris Ferris | Versioning policy | all | design | ||
i094 | Doug Davis | New WSRMRequired Fault | core | design | ||
i095 | Anish Karmarkar | CloseSequenceResponse and TerminateSequenceResponse messages are inconsistent wrt presence of wsrm:Identifier | spec | design | ||
i102 | Jacques Durand | consistency in controlling the binding of SequenceAcknowledgement and of seq management responses | core | design | ||
i115 | Gilbert Pilz | "must understand" attribute for extensions to RM components | core | design | ||
i128 | define unspecified IncompleteSequenceBehavior | core | design | |||
i146 | Bob Freund | Editorial Examples in Apx C lack CloseSequence | core | editorial |
i001 | Bilateral sequence negotiation | core - design - closed |
|
||
i002 | AckTo EPR and seq lifetime | core - design - dropped |
|
||
i003 | EPRs and sequence scope | core - design - dropped |
|
||
i004 | wsa:messageID uniqueness requirments for retransmission | core - design - dropped |
|
||
i005 | Source resend of nacks messages when ack already received | core - design - closed |
|
||
i006 | Source based delivery QoS policy assertion | core - design - dropped |
|
||
i007 | WSS 1.0/1.1 token support | core - design - done |
|
||
i008 | Policy assertions granularity | policy - design - dropped |
|
||
i009 | Declaration of QoS policies | core - design - closed |
|
||
i010 | Sequence port spanning | core - design - closed |
|
||
i011 | Typo in expires P0S | core - editorial - closed |
|
||
i012 | Anonymous acksTo | soap - design - dropped |
|
||
i013 | Max message number in policy | core - design - closed |
|
||
i014 | Document Names | core - editorial - closed |
|
||
i015 | Required Artifact Metadata | core - editorial - closed |
|
||
i016 | Document Identifiers | core - editorial - closed |
|
||
i017 | XML Namespace URIs | schema - editorial - closed |
|
||
i018 | Is an implementation supporting a smaller max message number valid? | core - design - closed |
|
||
i019 | Sequence termination on Fault | core - design - closed |
|
||
i020 | Semantics of "At most once" Delivery assurance | all - design - closed |
|
||
i021 | An RM Policy applies two-way | policy - design - done |
|
||
i022 | RM Policy Assertion Model's Base Retransmission Interval Clarification Needed | policy - design - closed |
|
||
i023 | Robust recovery from low-resource conditions | core - design - dropped |
|
||
i024 | WS-RX policies not manifested on the wire | policy - design - closed |
|
||
i025 | What is the correct form of SeqAck when RMD has received no messages | core - design - closed |
|
||
i026 | better support in handling space-greedy sequences | core - design - dropped |
|
||
i027 | InOrder delivery assurance spanning multiple sequences | core - design - closed |
|
||
i028 | Accurate final acknowledgement of a Sequence with gaps when RMS decides to stop using it | core - design - closed |
|
||
i029 | Remove dependency on WS-Security | core - design - closed |
|
||
i030 | What are the obligations on RMD for use (or not) of Offered Sequence? | core - design - closed |
|
||
i031 | Inconsistency between spec and schema (AckRequested) | schema - editorial - closed |
|
||
i032 | Protocol serialization optimization proposal | core - design - dropped |
|
||
i033 | Processing model of NACKs | core - design - closed |
|
||
i034 | If a fault is generated whilst processing a piggy-backed AckRequested or SequenceAcknowledgement header, should this stop processing of the entire message? | core - design - closed |
|
||
i035 | What does 'anon' URI mean when used in AcksTo EPR? | core - design - closed |
|
||
i036 | Duplicate detection of wsrm:CreateSequence messages | core - design - dropped |
|
||
i037 | WS-Addressing Endpoint redefined in WSRM | core - editorial - closed |
|
||
i038 | 2396 is obsoleted by 3986 | core - editorial - closed |
|
||
i039 | What does 'have a mustUnderstand attribute' mean? | core - editorial - closed |
|
||
i040 | Change 'optional' and 'required' in section 3 to RFC 2119 OPTIONAL and REQUIRED | core - editorial - closed |
|
||
i041 | Presence of NACK and ACK range in the same message | core - editorial - closed |
|
||
i042 | Which version of WS-Addressing spec? | core - design - done |
|
||
i043 | Why is wsa imported in the WSDL? | wsdl - editorial - closed |
|
||
i044 | SequenceFault element refers to fault code rather than fault [Subcode] | core - editorial - closed |
|
||
i045 | Why is SecureConversation a normative reference? | core - editorial - closed |
|
||
i046 | Schema type of wsrm:FaultCode element can be changed from xs:QName to wsrm:FaultCodes | schema - editorial - closed |
|
||
i047 | Reorder spec sections | core - editorial - closed |
|
||
i048 | CloseSequenceResponse and Acks | core - design - closed |
|
||
i049 | Allignment and refinement of defintions for DA | core - design - dropped |
|
||
i050 | spec talks about delivery assurances but does not clearly relate them to the protocol | core - design - closed |
|
||
i051 | Presence of multiple <SequenceAcknowledgement> headers for same Sequence in the same message | core - editorial - closed |
|
||
i052 | Should DA be separate assertion or parameter | policy - design - dropped |
|
||
i053 | Which occurances within the specs, if any, of the term "URI" need to be replaced with "IRI"? | core - editorial - closed |
|
||
i054 | Target of RM Assertion parameters are confusing with respect to how they are specified and attached | policy - design - closed |
|
||
i055 | Whose Inactivity Timeout is it anyway? | policy - design - closed |
|
||
i056 | How can RMS communicate the Base Retransmission Interval, Exponential Backoff and Inactivity Timeout values? | policy - design - dropped |
|
||
i057 | Classification of References (normative vs. non-normative) is needed | core - design - closed |
|
||
i058 | State Transition Table | core - editorial - closed |
|
||
i059 | Retransmission behavior | core - design - closed |
|
||
i060 | Definition for "Reliable Message" | core - editorial - closed |
|
||
i061 | Anonymous AcksTo | core - design - done |
|
||
i062 | None AcksTo | core - design - closed |
|
||
i063 | SeqAck - None and Final | schema - editorial - closed |
|
||
i064 | Create Sequence Refused Fault is too restrictive | core - design - closed |
|
||
i065 | Reword "Closing a Sequence" section | core - editorial - closed |
|
||
i066 | Remove LastMessage | core - design - closed |
|
||
i067 | Replace 'response' | core - editorial - closed |
|
||
i068 | Remove 'correlation' text | core - editorial - closed |
|
||
i069 | MessageNumber on AckReq | core - design - closed |
|
||
i070 | Receive is defined twice in wsrm-1.1-spec-cd-01 | core - editorial - closed |
|
||
i071 | Editorial nits for wsrm-1.1-spec-cd-01 | core - editorial - closed |
|
||
i072 | Editorial nits for wsrmp-1.1-spec-cd-01 | policy - editorial - closed |
|
||
i073 | Descriptive text of removed parameters also needs to be removed | policy - editorial - closed |
|
||
i074 | Use of [tcShortName] in artifact locations namespaces, etc | all - editorial - closed |
|
||
i075 | Case of multiple RM Policies and DAs within an RMD scope | core - design - closed |
|
||
i076 | Semantics of offered Sequences | core - design - closed |
|
||
i077 | How does a RM Destination reject an offered Sequence? | core - design - dropped |
|
||
i078 | Lost TerminateSequence | core - design - closed |
|
||
i079 | SequenceClosed fault and SequenceAcknowledgement(Final) | core - editorial - closed |
|
||
i080 | Remove ambiguity about the protocol being at least once on the wire | core - editorial - closed |
|
||
i081 | RMS lacks support for InOrder | core - design - closed |
|
||
i082 | Level of "response message" unclear, for SequenceResponse | core - design - closed |
|
||
i083 | Fault Messages for Terminated Sequence | core - editorial - closed |
|
||
i084 | RMS state table and SequenceClosedFault | core - editorial - closed |
|
||
i085 | CloseSequence element is inconsistent | core - design - closed |
|
||
i086 | Alternative approach for MaxMessage | core - design - closed |
|
||
i087 | Acknowledgement Interval in CreateSequenceResponse | core - design - closed |
|
||
i088 | Versioning policy | all - design - closed |
|
||
i089 | suggest the restricted use of anonymous URI | core - design - done |
|
||
i090 | Use of offered sequences unclear in current spec | core - design - done |
|
||
i091 | Unexpected UnknownSequenceFault or SequenceTerminatedFault | core - design - done |
|
||
i092 | Where is the SequenceAcknowledgement sent on receipt of AckRequested header? | core - design - done |
|
||
i093 | 2119 terms apply to implementations, not message (document) instances | core - editorial - done |
|
||
i094 | New WSRMRequired Fault | core - design - closed |
|
||
i095 | CloseSequenceResponse and TerminateSequenceResponse messages are inconsistent wrt presence of wsrm:Identifier | spec - design - closed |
|
||
i096 | Complete the state tables | core - design - done |
|
||
i097 | Extensibility of RM assertion needs to be defined | policy - editorial - done |
|
||
i098 | clarify difference between "sequence" and "non-sequence" faults | core - editorial - done |
|
||
i099 | Correlating faults to Sequences using SOAP 1.1 | core - design - done |
|
||
i100 | Language for faultstring elements | core - editorial - done |
|
||
i101 | Recommend RMD Close rather than Terminate | core - design - done |
|
||
i102 | consistency in controlling the binding of SequenceAcknowledgement and of seq management responses | core - design - dropped |
|
||
i103 | Remove the Partial Answer Mode (PAM) | core - design - done |
|
||
i104 | Mixing SOAP versions | core - design - done |
|
||
i105 | Sequence Acks on all messages after close | core - editorial - done |
|
||
i106 | SequenceAcknowledgement:Final assumption of deliverability | core - design - done |
|
||
i107 | Nacks ack as well as Nack | core - design - done |
|
||
i108 | misplaced guidance on fault handling | core - editorial - done |
|
||
i109 | The description of the <Sequence/> element could use some wordsmithing | core - editorial - done |
|
||
i110 | Chris' Rants (on RM) part 1 | core - editorial - done |
|
||
i111 | Sequence state in event of MessageNumberRollover | core - design - done |
|
||
i112 | dangling reference to RMAssertion acknowledgement timing params | core - design - done |
|
||
i113 | Tightening up the state tables | core - design - active |
|
||
i114 | Figure 2 (cd3) is out of date with the changes to the potocol | core - design - done |
|
||
i115 | "must understand" attribute for extensions to RM components | core - design - dropped |
|
||
i116 | Add Max Msg Num to Message Number Rollover Fault | core - design - done |
|
||
i117 | Issue 21 resolution text contains language about 'parameters' which don't exist | core - design - done |
|
||
i118 | misuse of request term | core - editorial - done |
|
||
i119 | When to piggy-back RM headers | core - editorial - done |
|
||
i120 | misplaced paragraph on action IRI's | core - editorial - done |
|
||
i121 | security threats and requirements | core - design - active |
|
||
i122 | security profiles | core - design - active |
|
||
i123 | security profile agreement | core - design - active |
|
||
i124 | security composition policy | core - design - active |
|
||
i125 | Protocol precondition requires knowledge of policies | core - design - pending |
|
||
i126 | unclear text regarding wsa:Action | core - design - pending |
|
||
i127 | Make Accept/AcksTo consistent | core - design - pending |
|
||
i128 | define unspecified IncompleteSequenceBehavior | core - design - dropped |
|
||
i129 | Define "discard" | core - design - pending |
|
||
i130 | what does ack interval refer to | core - design - pending |
|
||
i131 | Remove sections 1.1 and 1.1.1 | core - editorial - done |
|
||
i132 | Change default value of fault uri | core - design - done |
|
||
i133 | Duplicate text in fault section | core - editorial - pending |
|
||
i134 | Update acknowledgements | core - editorial - active |
|
||
i135 | Consistent use of wsrm: in normative text | core - editorial - pending |
|
||
i136 | RM SeqID Globally Unique | core - editorial - pending |
|
||
i137 | No mechanisms to convey that messages should be polled. | core - design - pending |
|
||
i138 | Offer/Accept elements are incomplete | core - editorial - pending |
|
||
i139 | Inappropriate Fault destination | core - design - active |
|
||
i140 | add sub-headings to fault descriptions | core - editorial - active |
|
||
i141 | Sec 3.3 fault response to TerminateSequenceRequest is not specified. | core - editorial - pending |
|
||
i142 | Sec 3.5 Request Acknowledgement text assumesSequence is known | core - editorial - pending |
|
||
i143 | messages have to be received for them to be examined | core - editorial - active |
|
||
i144 | RMS MessageNumberRollover behavior unclear | core - editorial - active |
|
||
i145 | Implications of Sequence Expiration not specified | core - editorial - active |
|
||
i146 | Editorial Examples in Apx C lack CloseSequence | core - editorial - dropped |
|
||
i147 | Extensibility (or not) of the Protocol Elements | core - editorial - active |
|
||
i148 | Reword the Abstract | core - editorial - pending |
|
||
i149 | Define the syntax used to refer to elements and attributes | core - editorial - pending |
|
||
i150 | Define the syntax used to refer to elements and attributes | core - editorial - pending |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]