Peer-to-peer name resolution wire protocol and message format data structure for use therein

• US 20050004916A1
• Filed: 06/13/2003
• Published: 01/06/2005
• Est. Priority Date: 06/13/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Miller, John L., Simionescu, Radu, Lieuallen, Brian, Rawas, Henry
• Granted Patent: US 7,533,184 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04J 3/242 the frames being of variable length
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1065 Discovery involving distributed pre-established resource-based relationships among peers, e.g. based on distributed hash tables [DHT] pre-configuration of logical or physical connections H04L67/1053
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

An extensible data structure for messages in a peer to peer name resolution protocol is presented. This message data structure utilizes a number of fields, each containing a message element. Preferably, the first field is the message header that includes protocol information and identifies the type of message. Each message element contains a number of fields. These message element fields include a type field, a length field, and the content or payload of the message element. In one embodiment, at least ten messages are formed for proper operation of a Peer To Peer Name Resolution Protocol (PNRP), including RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages.

Claims

49. A computer-readable medium having stored thereon a RESOLVE message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a resolve controls message element;

a third message field containing a PNRP target identification message element;

a fourth message field containing a validate PNRP identification message element;

a fifth message field containing a certified peer address (CPA) best match message element; and

a sixth message field containing an IPV6 endpoint array message element.

1. A computer-readable medium having stored thereon a data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a first message element stored therein; and

at least a second message field having a second message element stored therein; and

wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

2. The computer-readable medium of claim 1, further comprising a plurality of message fields each having a message element stored therein.

3. The computer-readable medium of claim 1, wherein the first message element stored in the first message field comprises a header message element.

4. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being one of a RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR message.

5. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a RESOLVE message, wherein the second message element stored in the second field comprises a resolve controls message element, the RESOLVE further comprising a third message field containing a PNRP target identification message element, a fourth message field containing a validate PNRP identification message element, a fifth message field containing a certified peer address (CPA) best match message element, and a sixth message field containing an IPV6 endpoint array message element.

6. The computer-readable medium of claim 5, wherein the payload of the resolve controls message element comprises a bit field for context-specific flags, a maximum number of nodes that the RESOLVE message can visit, operation codes to control resolve operation, a precision number of significant bits to match, a reason code that describes a reason for initiating a RESOLVE, a result code that describes a reason for returning a response, and a transaction identification value.

7. The computer-readable medium of claim 5, wherein the payload of the target PNRP identification message element comprises a hash of a peer name of a target peer and a service location derived from an advertised service address.

8. The computer-readable medium of claim 5, wherein the payload of the validate PNRP identification message element comprises a hash of a peer name of a node for which validation and an authority are requested and a service location derived from an advertised service address of the node for which validation and an authority are requested.

9. The computer-readable medium of claim 5, wherein the payload of the CPA best match message element comprises an encoded CPA.

10. The computer-readable medium of claim 5, wherein the payload of the IPV6 endpoint array message element comprises a number of entries in an array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of addresses for each node already visited or to which the RESPONSE message was transmitted.

11. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a RESPONSE message, wherein the second message element stored in the second field comprises a resolve controls message element, and wherein the RESPONSE message further comprises a third message field containing a resolve controls message element, a fourth message field containing a target PNRP ID message element, a fifth message field containing a CPA best match message element, and an IPV6 endpoint array message element.

12. The computer-readable medium of claim 11, wherein the payload of the resolve controls message element comprises a bit field for context-specific flags, a maximum number of nodes that the RESOLVE message can visit, operation codes to control resolve operation, a precision number of significant bits to match, a reason code that describes a reason for initiating a RESOLVE, a result code that describes a reason for returning a response, and a transaction identification value.

13. The computer-readable medium of claim 11, wherein the payload of the target PNRP identification message element comprises a hash of a peer name of a target peer and a service location derived from an advertised service address.

14. The computer-readable medium of claim 11, wherein the payload of the CPA best match message element comprises an encoded CPA.

15. The computer-readable medium of claim 11, wherein the payload of the IPV6 endpoint array message element comprises a number of entries in an array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of addresses for each node already visited or to which the RESPONSE message was transmitted.

16. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a SOLICIT message, wherein the second message element stored in the second field comprises a CPA source message element, and wherein the SOLICIT message further comprises a third message field containing hashed nonce message element.

17. The computer-readable medium of claim 16, wherein the payload of the CPA source message element comprises an encoded source CPA.

18. The computer-readable medium of claim 16, wherein the payload of the hashed nonce message element comprises an encrypted nonce value.

19. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a ADVERTISE message, wherein the second message element stored in the second field comprises a PNRP header acknowledged message element, and wherein the ADVERTISE message further comprises a third message field containing a PNRP ID array message element, and a fourth message field containing a hashed nonce message element.

20. The computer-readable medium of claim 19, wherein the payload of the PNRP header acknowledged message element comprises a message identification of a message that is being acknowledged.

21. The computer-readable medium of claim 19, wherein the payload of the PNRP ID array message element comprises a number of entries in a PNRP ID array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of PNRP IDs.

22. The computer-readable medium of claim 19, wherein the payload of the hashed nonce message element comprises an encrypted nonce value.

23. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a REQUEST message, wherein the second message element stored in the second field comprises a nonce message element, and wherein the REQUEST message further comprises a third message field containing a PNRP ID array message element.

24. The computer-readable medium of claim 23, wherein the payload of the none message element comprises a decrypted nonce value.

25. The computer-readable medium of claim 23, wherein the payload of the PNRP ID array message element comprises a number of entries in a PNRP ID array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of PNRP IDs.

26. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a FLOOD message, wherein the second message element stored in the second field comprises a flood controls message element, and wherein the FLOOD message further comprises a third message field containing a CPA best match message element, and a fourth message field containing an IPV6 endpoint array message element.

27. The computer-readable medium of claim 26, wherein the payload of the flood controls message element comprises a bit field for context-specific flags, and a reason code that describes the reason for initiation of the FLOOD message.

28. The computer-readable medium of claim 26, wherein the payload of the CPA best match message element comprises an encoded CPA.

29. The computer-readable medium of claim 26, wherein the payload of the IPV6 endpoint array message element comprises a number of entries in an array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of addresses for each node already visited or to which the RESPONSE message was transmitted.

30. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a INQUIRE message, wherein the second message element stored in the second field comprises a flags field message element, and wherein the INQUIRE message further comprises a third message field containing a validate PNRP identification message element.

31. The computer-readable medium of claim 30, wherein the payload of the flags field message element comprises a fit field for context-specific flags.

32. The computer-readable medium of claim 30, wherein the payload of the validate PNRP identification message element comprises a hash of a peer name of a node for which validation and an authority are requested and a service location derived from an advertised service address of the node for which validation and an authority are requested.

33. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a AUTHORITY message, wherein the second message element stored in the second field comprises a PNRP header acknowledged message element, and wherein the AUTHORITY message further comprises a third message field containing a split controls message element, a fourth message field containing flags field message element, a fifth message field containing a validate PNRP ID message element, a sixth message field containing a certificate chain message element, a seventh message field containing an IPV6 referral address message element, an eighth message field containing an IPV6 referral identification message element, and a ninth message field containing a classifier message element.

34. The computer-readable medium of claim 33, wherein the payload of the PNRP header acknowledged message element comprises a message identification of a message that is being acknowledged.

35. The computer-readable medium of claim 33, wherein the payload of the split controls message element comprises information of a size of fragmentation and an offset of the fragmentation.

36. The computer-readable medium of claim 33, wherein the payload of the flags field message element comprises a fit field for context-specific flags.

37. The computer-readable medium of claim 33, wherein the payload of the validate PNRP identification message element comprises a hash of a peer name of a node for which validation and an authority are requested and a service location derived from an advertised service address of the node for which validation and an authority are requested.

38. The computer-readable medium of claim 33, wherein the payload of the certificate chain message element comprises a PKCS7 encoded certificate store.

39. The computer-readable medium of claim 33, wherein the payload of the IPV6 referral address message element comprises a path flag for a node endpoint, an IP protocol number, an IPV6 port, and an IPV6 address as an alternate node'"'"'s address.

40. The computer-readable medium of claim 33, wherein the payload of the IPV6 referral identification message element comprises a hash of a peer name and a service location for a node to which a referral is being made.

41. The computer-readable medium of claim 33, wherein the payload of the classifier message element comprises a Unicode classifier string that was used as a basis for a peer name, encoded as an array of WCHAR elements including a number of entries in an address array, a total length of the array, an identifier for a type or each array entry, a length of each array element, and an array of Unicode characters.

42. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a ACK message, wherein the second message element stored in the second field comprises a PNRP header acknowledged message element.

43. The computer-readable medium of claim 42, wherein the payload of the PNRP header acknowledged message element comprises a message identification of a message that is being acknowledged.

44. The computer-readable medium of claim 3, wherein the payload of the header message element includes information identifying a message type as being a REPAIR message, wherein the second message element stored in the second field comprises a target PNRP identification message element, and wherein the REPAIR message further comprise a third message field comprising a cache level message element, and a fourth message field comprising an IPV6 endpoint message element.

45. The computer-readable medium of claim 44, wherein the payload of the target PNRP identification message element comprises a hash of a peer name of a target peer and a service location derived from an advertised service address.

46. The computer-readable medium of claim 44, wherein the payload of the cache level message element comprises a cache level number identifying which cache level is to be used when executing a repair.

47. The computer-readable medium of claim 4, wherein the payload of the header message element further includes information identifying a particular message to allow tracking of responses to the particular message.

48. The computer-readable medium of claim 1, wherein the length field contains information identifying a length of the message element, including the length of the field identification field, the length field, and the payload.

50. The computer-readable media of claim 49, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

51. The computer-readable medium of claim 50, wherein the payload of the resolve controls message element comprises a bit field for context-specific flags, a maximum number of nodes that the RESOLVE message can visit, operation codes to control resolve operation, a precision number of significant bits to match, a reason code that describes a reason for initiating a RESOLVE, a result code that describes a reason for returning a response, and a transaction identification value.

52. The computer-readable medium of claim 50, wherein the payload of the target PNRP identification message element comprises a hash of a peer name of a target peer and a service location derived from an advertised service address.

53. The computer-readable medium of claim 50, wherein the payload of the validate PNRP identification message element comprises a hash of a peer name of a node for which validation and an authority are requested and a service location derived from an advertised service address of the node for which validation and an authority are requested.

54. The computer-readable medium of claim 50, wherein the payload of the IPV6 endpoint array message element comprises a number of entries in an array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of addresses for each node already visited or to which the RESPONSE message was transmitted.

53-1. The computer-readable medium of claim 50, wherein the payload of the CPA best match message element comprises an encoded CPA.

55. A computer-readable medium having stored thereon a RESPONSE message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a resolve controls message element;

a third message field containing a resolve controls message element;

a fourth message field containing a target PNRP ID message element;

a fifth message field containing a certified peer address (CPA) best match message element; and

a sixth message field containing an IPV6 endpoint array message element.

56. The computer-readable media of claim 55, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

57. The computer-readable medium of claim 56, wherein the payload of the resolve controls message element comprises a bit field for context-specific flags, a maximum number of nodes that the RESOLVE message can visit, operation codes to control resolve operation, a precision number of significant bits to match, a reason code that describes a reason for initiating a RESOLVE, a result code that describes a reason for returning a response, and a transaction identification value.

58. The computer-readable medium of claim 56, wherein the payload of the target PNRP identification message element comprises a hash of a peer name of a target peer and a service location derived from an advertised service address.

59. The computer-readable medium of claim 56, wherein the payload of the CPA best match message element comprises an encoded CPA.

60. The computer-readable medium of claim 56, wherein the payload of the IPV6 endpoint array message element comprises a number of entries in an array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of addresses for each node already visited or to which the RESPONSE message was transmitted.

61. A computer-readable medium having stored thereon a SOLICIT message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a CPA source message element; and

a third message field containing a hashed nonce message element.

62. The computer-readable media of claim 61, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

63. The computer-readable medium of claim 62, wherein the payload of the CPA source message element comprises an encoded source CPA.

64. The computer-readable medium of claim 62, wherein the payload of the hashed nonce message element comprises an encrypted nonce value.

65. A computer-readable medium having stored thereon a ADVERTISE message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a PNRP header acknowledged message element;

a third message field containing a PNRP ID array message element; and

a fourth message field containing a hashed nonce message element.

66. The computer-readable media of claim 65, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

67. The computer-readable medium of claim 66, wherein the payload of the PNRP header acknowledged message element comprises a message identification of a message that is being acknowledged.

68. The computer-readable medium of claim 66, wherein the payload of the PNRP ID array message element comprises a number of entries in a PNRP ID array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of PNRP IDs.

69. The computer-readable medium of claim 66, wherein the payload of the hashed nonce message element comprises an encrypted nonce value.

70. A computer-readable medium having stored thereon a REQUEST message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a nonce message element; and

a third message field containing a PNRP ID array message element.

71. The computer-readable media of claim 70, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

72. The computer-readable medium of claim 71, wherein the payload of the none message element comprises a decrypted nonce value.

73. The computer-readable medium of claim 71, wherein the payload of the PNRP ID array message element comprises a number of entries in a PNRP ID array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of PNRP IDs.

74. A computer-readable medium having stored thereon a FLOOD message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a flood controls message element;

a third message field containing a CPA best match message element; and

a fourth message field containing an IPV6 endpoint array message element.

75. The computer-readable media of claim 74, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

76. The computer-readable medium of claim 75, wherein the payload of the flood controls message element comprises a bit field for context-specific flags, and a reason code that describes the reason for initiation of the FLOOD message.

77. The computer-readable medium of claim 75, wherein the payload of the CPA best match message element comprises an encoded CPA.

78. The computer-readable medium of claim 75, wherein the payload of the IPV6 endpoint array message element comprises a number of entries in an array, a total length of the array, an identifier for a type of each array entry, a length of each array element, and an array of addresses for each node already visited or to which the RESPONSE message was transmitted.

79. A computer-readable medium having stored thereon a INQUIRE message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a flags field message element; and

a third message field containing a validate PNRP identification message element.

80. The computer-readable media of claim 79, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

81. The computer-readable medium of claim 80, wherein the payload of the flags field message element comprises a fit field for context-specific flags.

82. The computer-readable medium of claim 80, wherein the payload of the validate PNRP identification message element comprises a hash of a peer name of a node for which validation and an authority are requested and a service location derived from an advertised service address of the node for which validation and an authority are requested.

83. A computer-readable medium having stored thereon a RESOLVE message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field having a PNRP header message element;

a second message field having a PNRP header acknowledged message element;

a third message field containing a split controls message element;

a fourth message field containing a flags field message element;

a fifth message field containing a validate PNRP ID message element;

a sixth message field containing a certificate chain message element;

a seventh message field containing an IPV6 referral address message element;

an eighth message field containing an IPV6 referral identification message element; and

a ninth message field containing a classifier message element.

84. The computer-readable media of claim 83, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

85. The computer-readable medium of claim 84, wherein the payload of the PNRP header acknowledged message element comprises a message identification of a message that is being acknowledged.

86. The computer-readable medium of claim 84, wherein the payload of the split controls message element comprises information of a size of fragmentation and an offset of the fragmentation.

87. The computer-readable medium of claim 84, wherein the payload of the flags field message element comprises a fit field for context-specific flags.

88. The computer-readable medium of claim 84, wherein the payload of the validate PNRP identification message element comprises a hash of a peer name of a node for which validation and an authority are requested and a service location derived from an advertised service address of the node for which validation and an authority are requested.

89. The computer-readable medium of claim 84, wherein the payload of the certificate chain message element comprises a PKCS7 encoded certificate store.

90. The computer-readable medium of claim 84, wherein the payload of the IPV6 referral address message element comprises a path flag for a node endpoint, an IP protocol number, an IPV6 port, and an IPV6 address as an alternate node'"'"'s address.

91. The computer-readable medium of claim 84, wherein the payload of the IPV6 referral identification message element comprises a hash of a peer name and a service location for a node to which a referral is being made.

92. The computer-readable medium of claim 84, wherein the payload of the classifier message element comprises a Unicode classifier string that was used as a basis for a peer name, encoded as an array of WCHAR elements including a number of entries in an address array, a total length of the array, an identifier for a type or each array entry, a length of each array element, and an array of Unicode characters.

93. A computer-readable medium having stored thereon a ACK message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field containing a PNRP header message element; and

a second message field containing a PNRP header acknowledged message element.

94. The computer-readable media of claim 93, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

95. The computer-readable medium of claim 94, wherein the payload of the PNRP header acknowledged message element comprises a message identification of a message that is being acknowledged.

96. A computer-readable medium having stored thereon a REPAIR message data structure for use in a peer to peer name resolution protocol (PNRP), comprising:

a first message field containing a PNRP header message element;

a second message field containing a target PNRP identification message element;

a third message field containing a cache level message element; and

a fourth message field containing an IPV6 endpoint message element.

97. The computer-readable media of claim 96, wherein each message element comprises a message element data structure comprising a field identification field, a length field, and a payload.

98. The computer-readable medium of claim 97, wherein the payload of the target PNRP identification message element comprises a hash of a peer name of a target peer and a service location derived from an advertised service address.

99. The computer-readable medium of claim 97, wherein the payload of the cache level message element comprises a cache level number identifying which cache level is to be used when executing a repair.