Share via

3.1.4.4 Begin Listening

  • Article

When the higher-layer application requests the node to start listening for incoming connections, the P2P Grouping Security Protocol MUST perform the following steps:

  1. Trigger the P2P Graphing Protocol to start listening, as specified in [MS-PPGRH] section 3.1.4.8.

  2. Publish the node information in the PNRP Cloud identified by the Cloud Name opened earlier as specified in section 3.1.4.2, using the following input: (See [MS-PNRP] section 3.2.4.1 for detailed specification of publishing a Peer Name in PRNP.)

    • The elements to form a Peer Name are the following:

      • The local IDC MUST be used as the Peer Identity.

      • The local GMC chain MUST be used as the Certificate Chain.

      • "participant" MUST be specified as the optional classifier.

    • A Service Location Prefix MUST NOT be specified.

    • The Friendly Name string MUST contain the Classifier portion of the Group Peer Name. (See section 3.1.1.)

  3. An Extended Payload MUST NOT be specified.

  4. An Endpoint List MUST be specified using at most 4 of the addresses, randomly selected, on which P2P Graphing is listening.

After the node information is published in PNRP, the node MUST publish its Membership record as specified in section 3.1.7.1 if:

  • It has not already been published.

and

  • The Securities Properties record does not contain the PEER_MEMBER_DATA_OPTIONAL flag.

If any of the preceding steps fails, the listening operation MUST be terminated and the Grouping protocol MUST notify the higher-layer application of the failure.