Share via

3.1.4.4 Resolving a Peer Name

  • Article

In a resolution operation, five inputs are provided by the application or higher layer protocol:

  • A Peer Name;

  • A ServiceLocationPrefix which is a 64-bit integer used to form the top 64 bits of the service location;

  • A ResolveCriteria corresponding to the OpCode values as specified in section 2.2.2.8, which is used by the higher-layer protocol to resolve specific service records for a given authority and classifier as defined by the higher-layer protocol semantics;

  • A flag indicating whether to consider locally-registered PNRP IDs; and

  • An indication in which cloud the resolution is to be done.

If the cloud has not been opened (for example, no state in the Cloud Table exists), the node MUST fail the request. Otherwise, the Resolver MUST validate that the Peer Name conforms to the syntax as specified in section 2.2.4, and fail the request if it does not conform.

If there are no addresses in the Local Endpoint List, the node MUST fail the request.

The Resolver MUST then construct a PNRP ID (as specified in section 3.1.4.4.1) from the Peer Name and ServiceLocationPrefix provided by the application or higher-layer protocol, and from the 64-bit Service Location Suffix (in network byte order) 0x8000000000000000.

The Resolver MUST then attempt to resolve the PNRP ID (as specified in section 3.1.4.4.2) with ResolveReasonCode set to REASON_APP_REQUEST, InitialBestMatchRouteEntry and InitialNextHopRouteEntry set to empty, and PickBestMatchFromLocalIds set to true if the calling code requests locally registered IDs to be considered.