[MC-PRCR]:
Peer Channel Custom Resolver Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
§ Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions.
§ Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation.
§ No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
§ Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
§ License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map.
§ Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
§ Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
Support. For questions and support, please contact .
Revision Summary
Date / Revision History / Revision Class / Comments /8/10/2007 / 0.1 / Major / Initial Availability
9/28/2007 / 0.2 / Minor / Clarified the meaning of the technical content.
10/23/2007 / 0.3 / Minor / Clarified the meaning of the technical content.
11/30/2007 / 0.3.1 / Editorial / Revised and edited the technical content; updated links.
1/25/2008 / 0.3.2 / Editorial / Changed language and formatting in the technical content.
3/14/2008 / 0.3.3 / Editorial / Changed language and formatting in the technical content.
5/16/2008 / 0.3.4 / Editorial / Changed language and formatting in the technical content.
6/20/2008 / 0.3.5 / Editorial / Changed language and formatting in the technical content.
7/25/2008 / 0.3.6 / Editorial / Changed language and formatting in the technical content.
8/29/2008 / 1.0 / Major / Updated and revised the technical content.
10/24/2008 / 1.0.1 / Editorial / Changed language and formatting in the technical content.
12/5/2008 / 2.0 / Major / Updated and revised the technical content.
1/16/2009 / 2.0.1 / Editorial / Changed language and formatting in the technical content.
2/27/2009 / 2.1 / Minor / Clarified the meaning of the technical content.
4/10/2009 / 2.2 / Minor / Clarified the meaning of the technical content.
5/22/2009 / 2.3 / Minor / Clarified the meaning of the technical content.
7/2/2009 / 2.3.1 / Editorial / Changed language and formatting in the technical content.
8/14/2009 / 2.3.2 / Editorial / Changed language and formatting in the technical content.
9/25/2009 / 2.4 / Minor / Clarified the meaning of the technical content.
11/6/2009 / 2.4.1 / Editorial / Changed language and formatting in the technical content.
12/18/2009 / 2.4.2 / Editorial / Changed language and formatting in the technical content.
1/29/2010 / 2.5 / Minor / Clarified the meaning of the technical content.
3/12/2010 / 2.5.1 / Editorial / Changed language and formatting in the technical content.
4/23/2010 / 2.5.2 / Editorial / Changed language and formatting in the technical content.
6/4/2010 / 3.0 / Major / Updated and revised the technical content.
7/16/2010 / 4.0 / Major / Updated and revised the technical content.
8/27/2010 / 5.0 / Major / Updated and revised the technical content.
10/8/2010 / 6.0 / Major / Updated and revised the technical content.
11/19/2010 / 7.0 / Major / Updated and revised the technical content.
1/7/2011 / 8.0 / Major / Updated and revised the technical content.
2/11/2011 / 8.1 / Minor / Clarified the meaning of the technical content.
3/25/2011 / 8.1 / None / No changes to the meaning, language, or formatting of the technical content.
5/6/2011 / 8.1 / None / No changes to the meaning, language, or formatting of the technical content.
6/17/2011 / 8.2 / Minor / Clarified the meaning of the technical content.
9/23/2011 / 8.2 / None / No changes to the meaning, language, or formatting of the technical content.
12/16/2011 / 9.0 / Major / Updated and revised the technical content.
3/30/2012 / 9.0 / None / No changes to the meaning, language, or formatting of the technical content.
7/12/2012 / 9.0 / None / No changes to the meaning, language, or formatting of the technical content.
10/25/2012 / 10.0 / Major / Updated and revised the technical content.
1/31/2013 / 11.0 / Major / Updated and revised the technical content.
8/8/2013 / 11.0 / None / No changes to the meaning, language, or formatting of the technical content.
11/14/2013 / 11.0 / None / No changes to the meaning, language, or formatting of the technical content.
2/13/2014 / 11.0 / None / No changes to the meaning, language, or formatting of the technical content.
5/15/2014 / 11.0 / None / No changes to the meaning, language, or formatting of the technical content.
6/30/2015 / 12.0 / Major / Significantly changed the technical content.
10/16/2015 / 12.0 / None / No changes to the meaning, language, or formatting of the technical content.
7/14/2016 / 13.0 / Major / Significantly changed the technical content.
3/16/2017 / 14.0 / Major / Significantly changed the technical content.
6/1/2017 / 14.0 / None / No changes to the meaning, language, or formatting of the technical content.
9/15/2017 / 15.0 / Major / Significantly changed the technical content.
Table of Contents
1 Introduction 6
1.1 Glossary 6
1.2 References 6
1.2.1 Normative References 7
1.2.2 Informative References 8
1.3 Overview 8
1.3.1 Identifiers 8
1.3.1.1 Mesh Name 8
1.3.1.2 ClientId 8
1.3.1.3 RegistrationId 8
1.3.2 Connecting to the Resolver Service 8
1.3.3 List of Resolver Service Operations 9
1.3.4 Registration Record Maintenance 9
1.4 Relationship to Other Protocols 9
1.5 Prerequisites/Preconditions 9
1.6 Applicability Statement 10
1.7 Versioning and Capability Negotiation 10
1.8 Vendor-Extensible Fields 10
1.9 Standards Assignments 10
2 Messages 11
2.1 Transport 11
2.2 Message Syntax 11
2.2.1 Namespaces 11
2.2.2 Structures Used 12
2.2.2.1 PeerNodeAddress Structure 12
2.2.2.2 RefreshResult Enumeration 13
2.2.3 Resolver Client Messages 14
2.2.3.1 Register Message 14
2.2.3.2 Resolve Message 15
2.2.3.3 Refresh Message 16
2.2.3.4 Update Message 16
2.2.3.5 Unregister Message 17
2.2.3.6 GetServiceInfo Message 18
2.2.4 Resolver Service Messages 18
2.2.4.1 RegisterResponse Message 18
2.2.4.2 ResolveResponse Message 19
2.2.4.3 RefreshResponse Message 20
2.2.4.4 ServiceSettingsResponseInfo Message 21
3 Protocol Details 22
3.1 Resolver Client Details 22
3.1.1 Abstract Data Model 22
3.1.2 Timers 23
3.1.2.1 Client Refresh Timer 23
3.1.2.2 Message Response Timer 23
3.1.3 Initialization 23
3.1.4 Higher-Layer Triggered Events 23
3.1.4.1 Register 24
3.1.4.2 Update 24
3.1.4.3 Resolve 24
3.1.4.4 Unregister 24
3.1.4.5 Refresh 24
3.1.4.6 GetServiceInfo 24
3.1.5 Message Processing Events and Sequencing Rules 24
3.1.5.1 RegisterResponse Message 24
3.1.5.2 ResolveResponse Message 25
3.1.5.3 RefreshResponse Message 25
3.1.5.4 ServiceSettingsResponseInfo Message 25
3.1.6 Timer Events 25
3.1.6.1 Client Refresh Timer 25
3.1.6.2 Message Response Timer 25
3.1.7 Other Local Events 25
3.1.7.1 Shutting Down the Resolver Service 25
3.2 Resolver Service Details 26
3.2.1 Abstract Data Model 26
3.2.2 Timers 26
3.2.2.1 Maintenance Timer 26
3.2.3 Initialization 26
3.2.4 Higher-Layer Triggered Events 26
3.2.5 Message Processing Events and Sequencing Rules 26
3.2.5.1 Register 26
3.2.5.2 Update 27
3.2.5.3 Resolve 27
3.2.5.4 Unregister 27
3.2.5.5 Refresh 27
3.2.5.6 GetServiceInfo 27
3.2.6 Timer Events 28
3.2.6.1 Maintenance Timer 28
3.2.7 Other Local Events 28
4 Protocol Examples 29
4.1 Peer Discovery 29
5 Security 31
5.1 Security Considerations for Implementers 31
5.2 Index of Security Parameters 31
6 Appendix A: Full WSDL 32
6.1 http://schemas.microsoft.com/net/2006/05/peer/resolver 32
6.2 http://schemas.microsoft.com/net/2006/05/peer 33
6.3 http://schemas.datacontract.org/2004/07/System.ServiceModel.PeerResolvers 35
6.4 http://schemas.microsoft.com/2003/10/Serialization 35
6.5 http://www.w3.org/2005/08/addressing 36
6.6 http://schemas.datacontract.org/2004/07/System.Net 38
6.7 http://schemas.datacontract.org/2004/07/System.Net.Sockets 38
6.8 http://schemas.microsoft.com/2003/10/Serialization/Arrays 42
7 Appendix B: Product Behavior 43
8 Change Tracking 44
9 Index 45
1 Introduction
The Peer Channel Custom Resolver Protocol is used for storage and retrieval of endpoint information of clients that have access to a known service. Clients that use the service can store their own endpoint information at the service and obtain endpoint information about other clients in order to establish direct connections between them.
Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative.
1.1 Glossary
This document uses the following terms:
ClientId: A unique string that the client uses to identify itself to the resolver service, as described in section 1.3.1.2.
endpoint information: An endpoint address, formatted as a Uniform Resource Identifier (URI), along with a set of IP addresses. Describes the set of addresses on which a node is listening.
expiration time: A date-time value, in Coordinated Universal Time (UTC) format, that indicates when an instance of binary data is no longer valid.
globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).
mesh name: A set of nodes that establish connections to each other to form a mesh.
PeerNodeAddress: A structure that contains the URI of a node and a set of IP addresses on which the client is listening ([MC-PRCR] section 2.2.2.1).
registration lifetime: The amount of time during which a registration record is guaranteed to be preserved by the resolver service; always associated with a particular registration record. This time starts upon the successful addition of a registration record to the resolver service. After this time has elapsed, the resolver service can choose to delete the corresponding registration record (section 3).
registration record: A set of endpoint information that is stored at the resolver service.
RegistrationId: A unique identifier in the form of a GUID, as described in section 1.3.1.3.
resolver client: An application endpoint that uses a resolver service to publish or obtain endpoint information.
resolver service: An application implementing this protocol that stores and distributes endpoint information.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
1.2.1 Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information.
[MC-NMF] Microsoft Corporation, ".NET Message Framing Protocol".
[MC-PRCH] Microsoft Corporation, "Peer Channel Protocol".
[MS-DTYP] Microsoft Corporation, "Windows Data Types".
[MS-WSPOL] Microsoft Corporation, "Web Services: Policy Assertions and WSDL Extensions".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc-editor.org/rfc/rfc2119.txt
[SOAP1.1] Box, D., Ehnebuske, D., Kakivaya, G., et al., "Simple Object Access Protocol (SOAP) 1.1", W3C Note, May 2000, http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[SOAP1.2-1/2003] Gudgin, M., Hadley, M., Mendelsohn, N., et al., "SOAP Version 1.2 Part 1: Messaging Framework", W3C Recommendation, June 2003, http://www.w3.org/TR/2003/REC-soap12-part1-20030624
[WSA1.0-Metadata] W3C, "WS-Addressing 1.0 Metadata Namespace", W3C Recommendation, http://www.w3.org/2007/05/addressing/metadata/
[WSA1.0-WSDLBinding] W3C, "WS-Addressing 1.0 WSDL Binding Namespace", W3C Recommendation, http://www.w3.org/2006/05/addressing/wsdl/
[WSAddressing] Box, D., et al., "Web Services Addressing (WS-Addressing)", August 2004, http://www.w3.org/Submission/ws-addressing/
[WSADDR] Gudgin, M., Hadley, M., and Rogers, T., "Web Services Addressing (WS-Addressing) 1.0", W3C Recommendation, May 2006, http://www.w3.org/2005/08/addressing