wsdd-discovery-1.1-spec-wd-05.docx Details

Document Details     TC Member Document View
Title wsdd-discovery-1.1-spec-wd-05.docx
Name * wsdd-discovery-1.1-spec-wd-05.docx (357K)
Description This is a working draft for WS-Discovery 1.1.
Group OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC
Folder Working Drafts
Submitter Vipul Modi
Date Submitted Wednesday, 14 January 2009 07:59pm
Document State Draft (A preliminary unapproved sketch, outline, or version.)
Access This document is visible to OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC and shared with:
  • OASIS Open (General Membership)
  • General Public

Document Revisions
Name # State Submitter Date Action
8
Draft
Vipul Modi
2009-04-12
7
Draft
Vipul Modi
2009-03-17
6
Draft
Vipul Modi
2009-02-12
5
Draft
Vipul Modi
2009-01-14
This doc
4
Draft
Vipul Modi
2008-11-24
3
Draft
Vipul Modi
2008-10-20
2
Draft
Vipul Modi
2008-09-29
1
Draft
Vipul Modi
2008-09-24
0
Draft
Vipul Modi
2008-09-19

Comments  
Subject & Text Submitter Date Action
Initial comment by submitter
This is a working draft 05 for WS-Discovery 1.1 that incorporates the resolution of following issues.

023 - Clarify use of AppSequence and related fields
079 - Too many normative statements in Section 2 Terminology and Notations
081 - Use "urn:uuid" scheme for UUID scope matching rule
086 - Example Hello sent in managed mode does not define "i"
087 - Incorrect reference to RFC 5280
088 - Using whitespaces in the expanded signature can result in different digest values
089 - Namespace of a Type can be altered in a secure discovery message
090 - Compact Signature outline does not include the datatype for Refs attribute
091 - Minor Editorial issues in Section 8.2
096 - Clarify meaning of "device leaving the network"
097 - Clarify meaning of "device joining the network"
098 - Assign an OASIS namespace for Committee Draft 2
099 - typo in URI
100 - typo in introduction
101 - typo in section 2.1
102 - typo in section 3.1
103 - typos in section 3.2
104 - clarify case where a TS doesn't specify a Type
105 - editorial changes in section 3.3
106 - redundant mentions of "one way"
107 - typos in section 3.1 (with DP)
108 - clarify "stable identifier"
118 - Add missing text for adding Algorithmsuite attribute in the expanded signature elements (editorial)
119 - Clarify that the DigestValue element inside the Reference element should be populated with the computed digest value (editorial)
120 - References update
069 - Preventing replay attack using [message id] property is impractical
123 - Remove special "ad-hoc" scope
141 - Editorial - Remove wildcard from the normative outline descriptions
142 - Editorial - Remove wildcard from the normative outline descriptions
124 - xAddrs in ResolveMatches issue
125 - Finding services require a double roundtrip
126 - KeyId complexity in compact signatures
144 - replace the >= 1 symbol with the text
145 - clarify that the security header should not be signed
Vipul Modi
2009-01-14
---