Resource identifiers for a peer-to-peer environment

• US 7,401,152 B2
• Filed: 01/22/2002
• Issued: 07/15/2008
• Est. Priority Date: 01/22/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Pouyoul, Eric, Abdelaziz, Mohamed M., Clary, Michael J., Gong, Li, Traversat, Bernard A., Joy, William N., Hugly, Jean-Christophe, Duigou, Michael J.
• Primary Examiner(s): Nguyen; Dustin
• Application Number:
  US10/055,666
• Publication Number:
  US 20020188657A1
• Time in Patent Office: 2,366 Days
• Field of Search: 709/201, 709/245, 709/250, 709/223, 709/227, 709/228, 709/238, 370/466, 719/330, 707/2
• US Class Current: 709/230
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/222 using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/2546 Arrangements for avoiding unnecessary translation
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 61/50 Address allocation
• CPC Class Codes: H04L 63/0209 Architectural arrangements, e.g. perimeter networks or demilitarized zones
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/105 : Multiple levels of security
• CPC Class Codes: H04L 63/123 : received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/126 : the source of the received data
• CPC Class Codes: H04L 63/164 : at the network layer
• CPC Class Codes: H04L 63/166 : at the transport layer
• CPC Class Codes: H04L 67/104 : Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1044 : Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/1046 : Joining mechanisms
• CPC Class Codes: H04L 67/1048 : Departure or maintenance mechanisms
• CPC Class Codes: H04L 67/1057 : involving pre-assessment of levels of reputation of peers
• CPC Class Codes: H04L 67/1059 : Inter-group management mechanisms, e.g. splitting, merging or interconnection of groups
• CPC Class Codes: H04L 67/1061 : using node-based peer discovery mechanisms static access to replicated servers H04L67/1006; service discovery H04L67/51
• CPC Class Codes: H04L 67/1063 : Discovery through centralising entities
• CPC Class Codes: H04L 67/1068 : Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/107 : with limitation or expansion of the discovery scope
• CPC Class Codes: H04L 67/1093 : Some peer nodes performing special functions
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 : Data redirection of data network streams
• CPC Class Codes: H04L 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: Y10S 707/99939 : Privileged access

Abstract

A system and method for uniquely identifying peers and other resources in a peer-to-peer networking environment. In one embodiment, every peer in the peer-to-peer network may have a unique peer identifier. Other peer-to-peer network resources may also have unique identifiers, including peer groups, services, applications, pipes, endpoints, content and resource advertisements. Identifiers may serve to canonically refer to resources. Identifiers may be embedded in advertisements for resources. In one embodiment, a peer identifier may identify a peer group in which the peer is a member peer. In one embodiment, a peer may have a different peer identifier for each group in which it is a member peer. In one embodiment, an identifier may be bound to a network address of the resource. If the resource changes network addresses, the identifier may be bound to the new network address. Thus, identifiers provide dynamic addressing for resources in the peer-to-peer environment.

Claims

1. A peer computing system, comprising:

a plurality of peer nodes operable to couple to a network;

wherein the plurality of peer nodes are configured to implement a peer-to-peer environment on the network according to a peer-to-peer platform comprising;

a core layer comprising one or more peer-to-peer platform protocols for enabling the plurality of peer nodes to discover each other, communicate with each other, and cooperate with each other to form peer groups and share content in the peer-to-peer environment;

a service layer comprising one or more services each provided by one or more of the plurality of peer nodes in the peer-to-peer environment, wherein at least a subset of the services are operable to be used by the plurality of peer nodes in forming the peer groups and participating in the peer groups, and wherein each of the one or more services are configured to be accessed by the plurality of peer nodes in accordance with at least one of the one or more peer-to-peer platform protocols; and

a unique peer identifier, wherein the peer identifier is configured for use in distinguishing a particular peer node from others of the plurality of peer nodes in the peer-to-peer environment, wherein the peer identifier is independent of a network address of the particular peer node;

wherein each of the plurality of peer nodes is further configured to access another of the plurality of peer nodes on the network using the unique peer identifier of the other peer node, wherein the peer node does not use a network address of the other peer node to access the other peer node.

2. The peer computing system as recited in claim 1, wherein each of the plurality of peer nodes is further configured to bind a peer identifier corresponding to the particular peer node to the network address of the particular peer node.

3. The peer computing system as recited in claim 1, wherein, to access the other peer node, the unique peer identifier of the other peer node is configured to be mapped to a network address of the other peer node.

4. The peer computing system as recited in claim 1, wherein, to access the other peer node, the unique peer identifier of the other peer node is configured to be mapped to one of one or more network interfaces of the other peer node.

5. The peer computing system as recited in claim 2, wherein each of the plurality of peer nodes is further configured to:

unbind the peer identifier corresponding to the peer node from the network address;

obtain a new network address; and

bind the peer identifier corresponding to the peer node to the new network address.

6. The peer computing system as recited in claim 1, wherein each peer identifier is further configured for use in determining a particular peer group in which a particular peer node corresponding to the peer identifier is a member peer.

7. The peer computing system as recited in claim 1, wherein each of the plurality of peer nodes is further configured to participate as a member peer in one or more peer groups in the peer-to-peer environment, and wherein each of the plurality of peer nodes is assigned a different unique peer identifier in accordance with the peer-to-peer platform for each of the one or more peer groups in which the peer node is a member peer.

8. The peer computing system as recited in claim 1, wherein each of the plurality of peer nodes is further configured to:

participate as a member peer in a plurality of peer groups in the peer-to-peer environment;

receive a message from another of the plurality of peer nodes, wherein the other peer node is a member peer in a particular one of the plurality of peer groups in which the peer node is a member peer, and wherein the message includes a peer identifier of the other peer; and

determine the particular one of the plurality of peer groups in which the other peer is a member peer from the peer identifier of the other peer.

9. The peer computing system as recited in claim 8, wherein the message specifies a resource hosted by the peer node, wherein the peer node hosts a plurality of instances of the resource, wherein each of the instances of the resource is hosted for a different one of the plurality of peer groups, and wherein the peer node is further configured to access in accordance with the message a particular one of the instances of the resource hosted for the particular one of the plurality of peer groups in which the other peer node is a member peer.

10. The peer computing system as recited in claim 9, wherein the resource is a service, and wherein the instance of the resource is an instance of the service implemented on the peer node.

11. The peer computing system as recited in claim 1, wherein the peer-to-peer platform defines a peer advertisement format for describing and publishing advertisements for peer nodes in the peer-to-peer environment, wherein each of the plurality of peer nodes is further configured to generate a peer advertisement for the particular peer node, wherein the peer advertisement includes a peer identifier for the peer node.

14. The peer computing system as recited in claim 1, wherein each of the one or more peer-to-peer platform protocols defines one or more advertisement formats for describing and publishing advertisements for resources in the peer-to-peer environment, wherein each of the plurality of peer nodes is further configured to:

host a plurality of resources accessible by the plurality of peer nodes in the peer-to-peer environment; and

generate a resource advertisement for each resource corresponding to the particular peer node in accordance with the peer-to-peer platform, wherein at least a subset of the resource advertisements each include a peer identifier of the peer node.

15. The peer computing system as recited in claim 14, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein the pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels.

16. The peer computing system as recited in claim 14, wherein each resource is assigned a unique resource identifier configured for use in distinguishing the particular resource from other resources in the peer-to-peer environment, and wherein each resource advertisement further includes a resource identifier assigned to a particular resource corresponding to the resource advertisement.

17. The peer computing system as recited in claim 1, wherein the one or more peer-to-peer platform protocols includes one or more of:

a peer discovery protocol for discovering resources in the peer-to-peer environment, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels;

a peer membership protocol for use by the peer nodes in applying for membership in the peer groups;

a peer resolver protocol for use in sending search queries from one peer group member to another peer group member;

a peer information protocol for enabling the peer nodes to obtain information about capabilities and status of other peer nodes in the peer-to-peer environment;

a pipe binding protocol for use in finding the physical location of pipe endpoints and binding the pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels; and

an endpoint routing protocol for enabling the peer nodes to request peer routing information to reach the other peer nodes.

18. The peer computing system as recited in claim 1, wherein the unique peer identifier of one of the plurality of peer nodes is formatted in accordance with a canonical representation scheme, and wherein the unique peer identifier of a different one of the plurality of peer nodes is formatted in accordance with a different canonical representation scheme.

19. The peer computing system as recited in claim 1, wherein the one of the plurality of peer nodes is a member peer in a peer group, wherein member peers in the peer group are configured to use the canonical representation scheme to format unique peer identifiers within the peer group, wherein the different one of the plurality of peer nodes is a member peer in a different peer group, and wherein member peers in the different peer group are configured to use the different canonical representation scheme to format unique peer identifiers within the different peer group.

12. The peer computing system as recited in claim l, further comprising a plurality of resources accessible by the plurality of peer nodes in the peer-to-peer environment, wherein each resource corresponds to a unique resource identifier configured for use in distinguishing the particular resource from other resources of the plurality of resources in the peer-to-peer environment.

13. The peer computing system as recited in claim 12, wherein the plurality of resources include one or more of peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels.

20. A peer node, comprising:

a network interface for coupling to a network;

a memory comprising program instructions, wherein the program instructions are executable within the peer node to implement, according to a peer-to-peer platform;

a core layer comprising one or more peer-to-peer platform protocols for enabling the peer node to discover other peer nodes, communicate with the other peer nodes, and cooperate with the other peer nodes to form peer groups and share content in a peer-to-peer environment on the network;

a service layer comprising one or more services in the peer-to-peer environment, wherein at least a subset of the services are operable to be used by the peer node and the other peer nodes in forming the peer groups and participating in the peer groups, and wherein each of the one or more services are configured to be accessed in accordance with at least one of the one or more peer-to-peer platform protocols; and

a unique peer identifier in accordance with the peer-to-peer platform, wherein the peer identifier is configured for use in distinguishing the peer node from other peer nodes in the peer-to-peer environment, wherein the peer identifier is independent of a network address for the peer node;

wherein the peer node is configured to access one of the other peer nodes using a unique peer identifier of the one of the other peer nodes, wherein the peer node does not use a network address of the one of the other peer nodes to access the one of the other peer nodes.

21. The peer node as recited in claim 20, wherein the peer node is further configured to bind the peer identifier to the network address of the peer node.

22. The peer node as recited in claim 21, wherein the peer node is further configured to:

unbind the peer identifier from the network address;

obtain a new network address; and

bind the peer identifier to the new network address.

23. The peer node as recited in claim 20, wherein the peer node is further configured to:

participate as a member peer in a plurality of peer groups in the peer-to-peer environment;

receive a message from another peer node, wherein the other peer node is a member peer in a particular one of the plurality of peer groups in which the peer node is a member peer, and wherein the message includes a peer identifier of the other peer; and

determine the particular one of the plurality of peer groups in which the other peer is a member peer from the peer identifier of the other peer.

24. The peer node as recited in claim 20, wherein the peer node is further configured to:

obtain a unique peer identifier of a different peer node on the network; and

access the different peer node on the network using the unique peer identifier of the other peer node;

wherein the peer node is not aware of a network address of the different peer node.

25. The peer node as recited in claim 21, wherein the message specifies a service hosted by the peer node, wherein the peer node hosts a plurality of instances of the service, wherein each of the instances of the service is hosted for a different one of the plurality of peer groups, and wherein the peer node is further configured to provide the message to a particular one of the instances of the service hosted for the particular one of the plurality of peer groups in which the other peer node is a member peer.

26. The peer node as recited in claim 20, wherein the peer-to-peer platform defines a peer advertisement format for describing and publishing advertisements for peer nodes in the peer-to-peer environment, wherein the peer node is further configured to generate a peer advertisement in accordance with the peer advertisement format, wherein the peer advertisement includes a peer identifier for the peer node.

27. The peer node as recited in claim 20, further comprising a plurality of resources accessible by peer nodes in the peer-to-peer environment, wherein the peer node is further configured to assign each of the plurality of peer nodes a unique resource identifier configured for use in distinguishing the particular resource from other resources in the peer-to-peer environment.

28. The peer node as recited in claim 27, wherein the plurality of resources include one or more of content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer node configured to be bound to the pipes to establish the communications channels.

29. The peer node as recited in claim 20, wherein each of the one or more peer-to-peer platform protocols defines one or more advertisement formats for describing and publishing advertisements for resources in the peer-to-peer environment, wherein the peer node is further configured to generate a resource advertisement for at least a subset of a plurality of resources on the peer node, wherein the resource advertisements each include the peer identifier for the peer node.

30. The peer node as recited in claim 29, wherein the plurality of resources include one or more of content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer node configured to be bound to the pipes to establish the communications channels.

31. The peer node as recited in claim 20, wherein the one or more peer-to-peer platform protocols includes a peer discovery protocol for discovering resources in the peer-to-peer environment, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on peer nodes that are configured to be bound to the pipes to establish the communications channels.

32. A method for implementing a peer-to-peer environment on a network, the method comprising:

a plurality of peer nodes coupled to a network each implementing a core layer of a peer-to-peer platform, wherein the core layer comprises one or more peer-to-peer platform protocols for enabling the plurality of peer nodes to discover each other, communicate with each other, and cooperate with each other to form peer groups and share content in the peer-to-peer environment;

the plurality of peer nodes each implementing a service layer comprising one or more services each provided by one or more of the plurality of peer nodes in the peer-to-peer environment, wherein each of the one or more services are configured to be accessed by peer nodes in the peer-to-peer environment in accordance with at least a subset of the one or more peer-to-peer platform protocols; and

assigning a unique peer identifier to each of the plurality of peer nodes, wherein each unique peer identifier is configured for use in distinguishing a particular peer node from others of the plurality of peer nodes in the peer-to-peer environment, wherein the peer identifier is independent of a network address of the particular peer node;

one of the plurality of peer nodes accessing another of the plurality of peer nodes on the network using the unique peer identifier of the other peer node, wherein the peer node does not use a network address of the other peer node to access the other peer node.

33. The method as recited in claim 32, further comprising binding the peer identifier of each of the plurality of peer nodes to the network address of the respective peer node.

34. The method as recited in claim 33, wherein, in said accessing the other peer node, the method further comprises mapping the unique peer identifier of the other peer node to a network address of the other peer node.

35. The method as recited in claim 33, wherein, in said accessing the other peer node, the method further comprises mapping the unique peer identifier of the other peer node to one of one or more network interfaces of the other peer node.

36. The method as recited in claim 33, further comprising:

one of the plurality of peer nodes unbinding the peer identifier corresponding to the peer node from the network address of the peer node;

the peer node obtaining a new network address; and

the peer node binding the peer identifier corresponding to the peer node to the new network address.

37. The method as recited in claim 32, further comprising:

at least a subset of the plurality of peer nodes accessing at least a subset of the core services in accordance with at least one of the one or more peer-to-peer platform protocols to form one or more peer groups in the peer-to-peer environment;

wherein each peer identifier is further configured for use in determining a particular one of the one or more peer groups in which a particular peer node corresponding to the peer identifier is a member peer.

38. The method as recited in claim 32, further comprising:

at least a subset of the plurality of peer nodes accessing at least a subset of the core services in accordance with at least one of the one or more peer-to-peer platform protocols to form one or more peer groups in the peer-to-peer environment; and

wherein each of the plurality of peer nodes is assigned a different unique peer identifier in accordance with the peer-to-peer platform for each of the one or more peer groups in which the peer node is a member peer.

39. The method as recited in claim 32, further comprising:

at least a subset of the plurality of peer nodes accessing at least a subset of the core services in accordance with at least one of the one or more peer-to-peer platform protocols to form one or more peer groups in the peer-to-peer environment; and

one of the at least a subset of the plurality of peer nodes receiving a message from another of the at least a subset of the plurality of peer nodes, wherein the other peer node is a member peer in a particular one of the one or more peer groups in which the peer node is a member peer, and wherein the message includes a peer identifier of the other peer; and

determining the particular one of the plurality of peer groups in which the other peer is a member peer from the peer identifier of the other peer.

40. The method as recited in claim 39, wherein the message specifies a service hosted by the peer node, wherein the peer node hosts a plurality of instances of the service, wherein each of the instances of the service is hosted for a different one of the one or more peer groups of which the peer node is a member peer, and wherein the method further comprises the peer node providing the message to a particular one of the instances of the service hosted for the determined particular one of the one or more peer groups in which the other peer node is a member peer.

41. The method as recited in claim 32, wherein the peer-to-peer platform defines a peer advertisement format for describing and publishing advertisements for peer nodes in the peer-to-peer environment, wherein the method further comprises generating a peer advertisement for one of the plurality of peer nodes, wherein the peer advertisement includes a peer identifier for the peer node.

42. The method as recited in claim 32, further comprising at least a subset of the plurality of peer nodes hosting a plurality of resources accessible by the plurality of peer nodes in the peer-to-peer environment, wherein each resource is assigned a unique resource identifier configured for use in distinguishing the particular resource from other resources in the peer-to-peer environment.

43. The method as recited in claim 42, wherein the plurality of resources include one or more of peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels.

44. The method as recited in claim 32, wherein the one or more peer-to-peer platform protocols define one or more advertisement formats for describing and publishing advertisements for resources in the peer-to-peer environment, the method further comprising:

at least a subset of the plurality of peer nodes hosting a plurality of resources accessible by the plurality of peer nodes in the peer-to-peer environment; and

generating a resource advertisement for each of the plurality of resources in accordance with the one or more peer-to-peer platform protocols, wherein at least a subset of the resource advertisements each include one or more peer identifiers each corresponding to one of the plurality of peer nodes associated with the particular resource corresponding to the particular resource advertisement.

45. The method as recited in claim 44, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein the pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels.

46. The method as recited in claim 44, wherein each resource is assigned a unique resource identifier configured for use in distinguishing the particular resource from other resources in the peer-to-peer environment, and wherein each resource advertisement further includes a resource identifier assigned to a particular resource corresponding to the resource advertisement.

47. The method as recited in claim 32, wherein the one or more peer-to-peer platform protocols include one or more of:

a peer discovery protocol for discovering resources in the peer-to-peer environment, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels; and

a peer membership protocol for use by the peer nodes in applying for membership in the peer groups.

48. The method as recited in claim 32, wherein, in said assigning a unique peer identifier to each of the plurality of peer nodes, the method further comprises:

formatting the unique peer identifiers of a subset of the plurality of peer nodes according to a canonical representation scheme; and

formatting the unique peer identifiers of a different subset of the plurality of peer nodes according to a different canonical representation scheme.

49. An article of manufacture comprising software instructions stored in computer storage media executable to implement:

a plurality of peer nodes coupled to a network each implementing a core layer of a peer-to-peer platform, wherein the core layer comprises one or more peer-to-peer platform protocols for enabling the plurality of peer nodes to discover each other, communicate with each other, and cooperate with each other to form peer groups and share content in a peer-to-peer environment;

the plurality of peer nodes each implementing a service layer comprising one or more services each provided by one or more of the plurality of peer nodes in the peer-to-peer environment, wherein each of the one or more services are configured to be accessed by peer nodes in the peer-to-peer environment in accordance with at least a subset of the one or more peer-to-peer platform protocols; and

assigning a unique peer identifier to each of the plurality of peer nodes, wherein each peer identifier is configured for use in distinguishing the respective peer node from others of the plurality of peer nodes in the peer-to-peer environment, wherein the peer identifier of a respective peer node is independent of a network address of the respective peer node;

wherein each of the plurality of peer nodes is configured to access another of the plurality of peer nodes using the unique peer identifier of the other peer node, wherein the peer node does not use a network address of the other peer node to access the other peer node.

50. The article of manufacture as recited in claim 49, wherein the software instructions are further executable to implement binding the peer identifier corresponding to a respective one of the plurality of peer nodes to the network address of the respective peer node.

51. The article of manufacture as recited in claim 50, wherein the software instructions are further executable to implement:

unbinding the peer identifier corresponding to the peer node from the network address;

obtaining a new network address for the peer node; and

binding the peer identifier corresponding to the peer node to the new network address.

52. The article of manufacture as recited in claim 49, wherein the software instructions are further executable to implement:

at least a subset of the plurality of peer nodes accessing at least a subset of the core services in accordance with at least one of the one or more peer-to-peer platform protocols to form one or more peer groups in the peer-to-peer environment;

wherein each peer identifier is further configured for use in determining a particular one of the one or more peer groups in which a particular peer node corresponding to the peer identifier is a member peer.

53. The article of manufacture as recited in claim 49, wherein the software instructions are further executable to implement:

at least a subset of the plurality of peer nodes accessing at least a subset of the core services in accordance with at least one of the one or more peer-to-peer platform protocols to form one or more peer groups in the peer-to-peer environment; and

wherein each of the plurality of peer nodes is assigned a different unique peer identifier in accordance with the peer-to-peer platform for each of the one or more peer groups in which the peer node is a member peer.

54. The article of manufacture as recited in claim 49, wherein the software instructions are further executable to implement:

at least a subset of the plurality of peer nodes accessing at least a subset of the core services in accordance with at least one of the one or more peer-to-peer platform protocols to form one or more peer groups in the peer-to-peer environment; and

;

one of the at least a subset of the plurality of peer nodes receiving a message from another of the at least a subset of the plurality of peer nodes, wherein the other peer node is a member peer in a particular one of the one or more peer groups in which the peer node is a member peer, and wherein the message includes a peer identifier of the other peer; and

determining the particular one of the plurality of peer groups in which the other peer is a member peer from the peer identifier of the other peer.

55. The article of manufacture as recited in claim 54, wherein the message specifies a service hosted by the peer node, wherein the peer node hosts a plurality of instances of the service, wherein each of the instances of the service is hosted for a different one of the one or more peer groups of which the peer node is a member peer, and wherein the software instructions are further executable to implement the peer node providing the message to a particular one of the instances of the service hosted for the determined particular one of the one or more peer groups in which the other peer node is a member peer.

56. The article of manufacture as recited in claim 49, wherein the peer-to-peer platform defines a peer advertisement format for describing and publishing advertisements for peer nodes in the peer-to-peer environment, wherein the software instructions are further executable to implement generating a peer advertisement for one of the plurality of peer nodes, wherein the peer advertisement includes a peer identifier for the peer node.

57. The article of manufacture as recited in claim 49, further comprising at least a subset of the plurality of peer nodes hosting a plurality of resources accessible by the plurality of peer nodes in the peer-to-peer environment, wherein each resource is assigned a unique resource identifier configured for use in distinguishing the particular resource from other resources in the peer-to-peer environment.

58. The article of manufacture as recited in claim 57, wherein the plurality of resources include one or more of peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels.

59. The article of manufacture as recited in claim 49, wherein the one or more peer-to-peer platform protocols define one or more advertisement formats for describing and publishing advertisements for resources in the peer-to-peer environment, wherein the software instructions are further executable to implement:

at least a subset of the plurality of peer nodes hosting a plurality of resources accessible by the plurality of peer nodes in the peer-to-peer environment; and

generating a resource advertisement for each of the plurality of resources in accordance with the one or more peer-to-peer platform protocols, wherein at least a subset of the resource advertisements each include one or more peer identifiers each corresponding to one of the plurality of peer nodes associated with the particular resource corresponding to the particular resource advertisement.

60. The article of manufacture as recited in claim 59, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein the pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels.

61. The article of manufacture as recited in claim 59, wherein each resource is assigned a unique resource identifier configured for use in distinguishing the particular resource from other resources in the peer-to-peer environment, and wherein each resource advertisement further includes a resource identifier assigned to a particular resource corresponding to the resource advertisement.

62. The article of manufacture as recited in claim 49, wherein the one or more peer-to-peer platform protocols include one or more of:

a peer discovery protocol for discovering resources in the peer-to-peer environment, wherein the resources include one or more of peer nodes, peer groups, content, services, applications, pipes, and pipe endpoints, wherein pipes are communications channels between two or more peer nodes in the peer-to-peer environment, and wherein pipe endpoints are network interfaces on the peer nodes that are configured to be bound to the pipes to establish the communications channels; and

a peer membership protocol for use by the peer nodes in applying for membership in the peer groups.