[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposed Charter for OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC
To OASIS Members: A draft TC charter has been submitted to establish the OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (http://www.oasis-open.org/committees/process-2008-02-05.php#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 11:45pm ET on 21 July 2008. OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: mailto:email@example.com. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail. A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar. We encourage member comment and ask that you note the name of the proposed TC (WS-DD) in the subject line of your email message. Regards, Mary --------------------------------------------------- Mary P McRae Manager of TC Administration, OASIS email: firstname.lastname@example.org web: www.oasis-open.org phone: 603.232.9090 =========== PROPOSED CHARTER FOR REVIEW AND COMMENT OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) Technical Committee a. Name of the TC OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) Technical Committee b. Statement of Purpose The purpose of the Web Services Discovery and Web Services Devices Profile (WS-DD) Technical Committee (TC) is to define: * A lightweight dynamic discovery protocol to locate web services that composes with other Web service specifications. * A binding of SOAP to UDP (User Datagram Protocol) , including message patterns, addressing requirements, and security considerations. * A profile of Web Services protocols consisting of a minimal set of implementation constraints to enable secure Web service messaging, discovery, description, and eventing on resource-constrained endpoints. The TC will accomplish this purpose through continued refinement of Web Services Discovery (WS-Discovery) specification , SOAP-over-UDP specification , and Devices Profile for Web Services (DPWS) specification  submitted to the TC as referenced in this charter. c. Scope of Work The TC will accept as input: * WS-Discovery . * SOAP-over-UDP . * DPWS . Other contributions will be accepted for consideration without any prejudice or restrictions and evaluated based on technical merit in so far as they conform to this charter. The scope of the TC's work includes further refinement and finalization of the input WS-Discovery specification  to produce a standard version of the specification, including WSDL documents and XML schema renderings, which enables dynamic discovery of web services. This includes: * A mechanism to: o Announce the arrival into a network (Hello message). o Announce departure from a network (Bye message). o Probe a network for matching services (Probe and ProbeMatch messages) where the match criteria for locating services is limited to the type of the service, the binding used by the service, and the administrative scope URIs assigned to the service. o Resolve an endpoint address to a transport address (Resolve and ResolveMatch messages). * Support for the above mechanism in ad hoc networks (based on SOAP-over-UDP) and managed networks (based on SOAP-over-HTTP). * Assignment of IP address and port used for discovery in ad hoc networks. * Multicast suppression using discovery proxy in managed networks. * Support for UDP (based on SOAP-over-UDP) and HTTP (based on SOAP-over-HTTP) transports. * Guidance on use of endpoint addresses. * An optional security model: o Securing multicast messages sent on ad hoc networks over UDP transport using compact signature format (based on WS-Security). * Guidance on security considerations: o Securing messages sent on managed networks over HTTP transport (HTTPS based transport level security and WS-Security based message level security). * A mechanism to order messages based on the order in which messages are transmitted from a service instance. * XML Schema and WSDL to describe the following discovery protocol messages: o One-way Hello and Bye announcement operations. o One-way Probe, ProbeMatch, Resolve, and ResolveMatch operations for use in ad hoc networks. o Request-response operations to handle Probe, ProbeMatch, Resolve, and ResolveMatch messages for discovery proxy interactions in managed networks. * Extensibility of Hello, Bye, Probe, ProbeMatch, Resolve, and ResolveMatch messages. * Extensibility of scope matching algorithms. The scope of the TC's work includes further refinement and finalization of the input SOAP-over-UDP specification  to produce a standard version of the specification that provides a SOAP binding to UDP. This includes: * Details of the UDP packet carrying the payload (SOAP envelope) including its header. * Definition of the following message exchange patterns (MEPs): o Unicast one-way. o Multicast one-way. o Unicast request, unicast response. o Multicast request, unicast response. * Rules for multicast, retransmission, and message encoding. * Guidance on security considerations (based on WS-Security). The scope of the TC's work includes further refinement and finalization of the input DPWS specification  to produce a standard version of the profile specification, including XML schema renderings, which promotes both interoperability between resource-constrained Web service implementations and interoperability with more flexible client implementations using a core set of Web service specifications in the following areas: * Sending messages to and from a Web service (based on SOAP, WS-Addressing) using UDP and HTTP transports. * Dynamically discovering a Web service (based on WS-Discovery). * Describing a Web service (based on WSDL, WS-Policy, WS-MetadataExchange, WS-Transfer, and XML Schema). * Subscribing to and receiving events from a Web service (based on WS-Eventing), including description of event notifications in WSDL. * Use of HTTPS in conjunction with compact signature security mechanism defined in WS-Discovery. * Optional security mechanism (using HTTPS based transport level security and WS-Security). o Support for X.509 certificates. WS-Discovery and SOAP-over-UDP specifications shall remain general, and broadly applicable, to device, enterprise, and other relevant usage scenarios. WS-Discovery, SOAP-over-UDP, and DPWS specifications will uphold the basic principles of other Web services specifications of independence and composition and must be composable with the other specifications in the Web services architecture such as, but not limited to, HTTP 1.1 , SOAP 1.2 , SOAP-over-HTTP binding , WS-Addressing , WSDL 1.1 , WSDL Binding for SOAP 1.2 , WS-Eventing , WS-MetadataExchange , WS-Policy , WS-PolicyAttachment , WS-Security , WS-Transfer , XML Schema  , WS-SecureConversation , and WS-Trust , AES/TLS , SHA1 , TLS , and X.509 v3 . If any specification to be referenced by DPWS, WS-Discovery, or SOAP-over-UDP is outside of a standardization process at the time this TC moves to ratify the profile, or is not far enough along in the standardization process, any normative references to it in the TC output will be expressed in an abstract manner, and the incarnation will be left at that time as an exercise in interoperability. While enabling composition with other specifications is a goal of the TC, it is also a goal to leave the specifics of how that composition is achieved outside the scope of the DPWS, WS-Discovery, and SOAP-over-UDP specifications. This TC may produce the following non-normative supporting documents for WS-Discovery, SOAP-over-UDP and DPWS specifications: * Primer or white paper describing usage scenarios and best practices. * Interoperation test scenarios. Out of Scope The following is a non-exhaustive list provided only for the sake of clarity. If some function, mechanism or feature is not mentioned here, and it is not mentioned as in-scope in the Scope of Work section either, then it will be deemed to be out of scope. The TC will not define a mapping of the functions and elements described in the specifications to any programming language or particular messaging middleware. Except for the elements directly related to the functions in the scope of the specifications, the TC will not prescribe the format of messages that are transferred according to the specifications. Where required, these functions are achieved by composition with other Web services specifications. The TC will not attempt to define functionality duplicating that of a specification normatively referenced in the input specification. This TC will not specify changes to specifications, including but not limited to the referenced specifications, external to the input DPWS, WS-Discovery, and SOAP-over-UDP specifications. This TC will not produce any other specification or document ? normative or non-normative ? other than: * WS-Discovery version 1.1 specification. * SOAP-over-UDP version 1.1 specification. * DPWS version 1.1 specification. * Non-normative supporting documents for WS-Discovery, SOAP-over-UDP and DPWS specifications: o Primer or white paper describing usage scenarios and best practices. o Interoperation test scenarios. For clarity, the out of scope features include, but are not limited to, the following: * Support for SOAP 1.1. * Support for WSDL 2.0. * Mechanisms for provisioning or deployment, or guidance on provisioning or deployment technologies, either by inclusion or reference. * Use or definition of mechanisms or protocols, other than those defined or used in the input specifications, such as: o Additional addressing mechanisms. o Additional discovery protocols. o Additional match criteria while probing the network for matching services. o Paging mechanisms for discovering services during discovery proxy interactions. o Discovery proxy implementation details such as caching and data handling techniques. o Additional device description languages or protocols for obtaining descriptions from implementations. o Additional eventing protocols. o Additional metadata exchange or transfer mechanisms. o Additional security algorithms or mechanisms. o Support for security certificates other than X.509. o Support for additional transport protocols other than UDP and HTTP. * Descriptions for any particular device or service types. * Message formats or mechanisms other than SOAP messages. * Features, mechanisms, extension points, or optimizations beyond those defined in the input specifications    are out of scope, unless included as in scope. Constraining WS-Discovery and SOAP-over-UDP specifications to specific usage scenarios, such as use only with devices, is disallowed. Contributions to this TC which are out of scope for this charter may be accumulated and taken into consideration for potential development of a charter for another technical committee that may be created to address future extensions or modifications to the profile. d. Deliverables This TC has the following set of deliverables: * WS-Discovery version 1.1 specification. * SOAP-over-UDP version 1.1 specification. * DPWS version 1.1 specification. This TC shall produce a Committee Specification version of Devices Profile for Web Services, WS-Discovery, and SOAP-over-UDP specifications by March 2009. Work on these specifications will proceed in parallel. The standard version of these specifications will reflect refinements, corrections or material technological improvements with respect to the input specifications and in accordance with this charter. Ratification of the DPWS, WS-Discovery, and SOAP-over-UDP specifications as OASIS standards, including a brief maintenance period, after the specifications are ratified as a standard, to address any errata, will mark the end of the TC's lifecycle. e. IPR Mode This TC will operate under the "RF (Royalty Free) on RAND Terms" IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy, effective 15 April 2005. f. Anticipated Audience The anticipated audience for this work includes: * Web services platform vendors, service repository providers, application middleware vendors. * System integrators, value-added resellers, and end users implementing Web services-based solutions that require an interoperable, composable distributed device control solution. * End users implementing Web services-based solutions and vendors offering Web services products that require an interoperable, composable, dynamic discovery mechanism and SOAP-over-UDP transport binding. * Device manufacturers (printers, scanners, projectors, medical devices, energy management devices, media devices, and many others). * Device controller manufacturers (computers and computer software, handheld computers, cellular telephones, handheld remote controls, and many other devices) that make use of devices conforming to the DPWS profile. * Specification authors working on WSDLs defining the characteristics of specific device types. * Software architects and programmers, who design, write, test, or integrate applications for Web services and devices whose interactions are based on Web services. g. Language TC business will be conducted in English. References  User Datagram Protocol (UDP) http://www.ietf.org/rfc/rfc768.txt  WS-Discovery http://schemas.xmlsoap.org/ws/2005/04/discovery  SOAP-over-UDP http://schemas.xmlsoap.org/ws/2004/09/soap-over-udp  Devices Profile for Web Services http://schemas.xmlsoap.org/ws/2006/02/devprof  HTTP/1.1 http://www.ietf.org/rfc/rfc2616.txt  SOAP 1.2 (Second Edition), Part 1 http://www.w3.org/TR/2007/REC-soap12-part1-20070427/  SOAP-over-HTTP binding ? SOAP 1.2 (Second Edition), Part 2, Section 7 http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#soapinhttp  WS-Addressing 1.0 ? Core, SOAP Binding and Metadata http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/ http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/ http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904/  WSDL 1.1 http://www.w3.org/TR/2001/NOTE-wsdl-20010315  WSDL Binding for SOAP 1.2 http://www.w3.org/Submission/wsdl11soap12/  WS-Eventing (March 2006 version) http://schemas.xmlsoap.org/ws/2004/08/eventing/  WS-MetadataExchange (August 2006 version) http://schemas.xmlsoap.org/ws/2004/09/mex/  WS-Policy1.5 http://www.w3.org/TR/2007/REC-ws-policy-20070904/  WS-PolicyAttachment 1.5 http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904/  WS-Security Core specification 1.1 http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMes sageSecurity.pdf  WS-Transfer, W3C Member Submission, September 2006 http://schemas.xmlsoap.org/ws/2004/09/transfer/  XML Schema, Part 1 http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/  XML Schema, Part 2 http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/  WS-SecureConversation 1.3 http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512  WS-Trust 1.3 http://docs.oasis-open.org/ws-sx/ws-trust/200512  AES/TLS, June 2002 version P. Chown, "Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)," June 2004, http://www.ietf.org/rfc/rfc3268.txt.  SHA1, April 1995 version "Secure Hash Standard," April 1995, http://www.itl.nist.gov/fipspubs/fip180-1.htm.  TLS version 1.0 T. Dierks, et al, "The TLS Protocol, Version 1.0", January 1999. (See http://www.ietf.org/rfc/rfc2246.txt.  X.509.v3 ITU-T X.509.v3 Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks (ISO/IEC/ITU 9594-8). Non-normative Information The following additional information relates to the launch of the TC, but will not be part of the TC's charter. a. Related Work There is no known standardization work that is currently in progress to apply Web services specifications to resource-constrained devices or to dynamically discover web services. There has been work on devices that communicate over IP based on different protocols, such as UPnP (http://www.upnp.org) and IGRS (http://www.igrs.org/en/index/index.asp). UPnP was submitted to ISO/IEC JTC1 as a Publicly Available Specification and has been approved as an international standard. IGRS was recently approved as a new work item in ISO/IEC JTC1 SC25. However, neither of these protocols is based on Web services specifications and do not incorporate the richness, interoperability, security, scalability, and composability of the full Web services protocol suite. The Mobile Web Initiative of W3C (http://www.w3.org/Mobile/) is focused on web browsing from mobile devices as opposed to controlling mobile devices using Web services or allowing mobile devices to control others using Web services. The OASIS Remote Control XML TC (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=remote-control) is focused on development of a small set of specific operations for remote control of devices which are expressed in XML but without the full richness of the entire Web services protocol suite. Since WS-Discovery, SOAP-over-UDP, and DPWS specifications are based on protocols in the Web services architecture, and must work well with other specifications within that architecture, they must be composable with the other specifications in the Web services architecture such as, but not limited to, HTTP 1.1 , SOAP 1.2 , SOAP-over-HTTP binding , WS-Addressing , WSDL 1.1 , WSDL Binding for SOAP 1.2 , WS-Eventing , WS-MetadataExchange , WS-Policy , WS-PolicyAttachment , WS-Security , WS-Transfer , XML Schema  , WS-SecureConversation , and WS-Trust , AES/TLS , SHA1 , TLS , and X.509 v3 . Where appropriate, the WS-DD TC will foster collaborative relationships and liaisons with other activities including other OASIS Technical Committees and committees of other organizations interested in the work of the TC. Responsibilities for such relationships and liaison will be defined by the TC at that time. b. Date, Time, and Location of First Meeting The first meeting of the WS-DD TC will be a face to face meeting held in Redmond, WA during September 16-18, 2008, from 9 AM PT to 5 PM PT. This meeting will be sponsored by Microsoft. c. On-Going Meeting Plans & Sponsors It is anticipated the WS-DD TC will meet via teleconference every week for 90 minutes at a time determined by the TC members during the TC's first meeting. It is anticipated that the WS-DD TC will meet face to face every quarter at a time and location to be determined by the TC members. Actual pace of face to face and teleconference meetings will be determined by TC members. One of the proposers, as listed below, will sponsor the teleconferences unless other TC members offer to donate their own facilities. If no other TC proposers offer to sponsor teleconference facilities, Microsoft will donate their facilities. d. Proposers of the TC Abbie Barbir, Nortel Networks Limited, email@example.com Lloyd Burch, Novell Inc., firstname.lastname@example.org Steve Carter, Novell Inc., email@example.com Colleen Evans, Microsoft Corporation, firstname.lastname@example.org Donald Ferguson, CA Inc., Donald.Ferguson@ca.com Francois Jammes, Schneider Electric SA, email@example.com Ram Jeyaraman, Microsoft Corporation, firstname.lastname@example.org Devon Kemp, Canon Inc., Devon.Kemp@cda.canon.com Mark Little, Red Hat Inc., email@example.com Jonathan Marsh, WSO2 Inc., firstname.lastname@example.org Jamie Meritt, Progress Software Corporation, email@example.com Toby Nixon, Microsoft Corporation, firstname.lastname@example.org Alain Regnier, Ricoh Company Limited, email@example.com Don Wright, Lexmark International Inc, firstname.lastname@example.org Prasad Yendluri, Software AG, Prasad.Yendluri@softwareag.com e. TC Convener The TC Convener will be Colleen Evans from Microsoft. f. OASIS Member Section affiliation None. g. Technical contributions to the TC The following specifications will be contributed to this TC: * WS-Discovery . * SOAP-over-UDP . * DPWS . h. FAQ This is currently under development. ETA: July 2008. i. Working Title and Acronym for Proposed Specifications Web Services Discovery (WS-Discovery) version 1.1. SOAP-over-UDP version 1.1. Devices Profile for Web Services (DPWS) version 1.1.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]