PIP 5C4 — Distribute Registration Status

RosettaNet choreography in cluster 5, transported on RNIF V02.00 and signed with S/MIME. Operational unit between Manufacturer and Distributor across the high-tech supply chain.

PIP purpose

PIP 5C4 distributes the registration status of a channel deal (deal registration). The manufacturer confirms or rejects a sales opportunity registered by a partner and qualifies the associated protection / discount level.

Message structure

The 5C4 choreography follows the RosettaNet action model:

• Primary action: Registration Status Notification Action
• Signal: Receipt Acknowledgment (RNIF)
• Response action: Receipt Acknowledgment

The action is wrapped in a multipart MIME RNIF V02.00 envelope signed with S/MIME. Here is a condensed view of the envelope:

MIME-Version: 1.0
Content-Type: multipart/related; type="application/xml";
  boundary="RN-BOUNDARY-2026"

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-Preamble.xml

<Preamble xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <standardName>RosettaNet</standardName>
  <standardVersion>V02.00</standardVersion>
</Preamble>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-ServiceHeader.xml

<ServiceHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <GlobalProcessIndicatorCode>5C4</GlobalProcessIndicatorCode>
</ServiceHeader>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: Pip5C4RegistrationStatusNotification.xml

<!-- PIP 5C4 payload above -->

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 5C4 payload for didactic purposes. The structural elements (fromRole, toRole, thisDocumentGenerationDateTime, and the PIP-specific business block) are required in any conformant implementation.

<?xml version="1.0" encoding="UTF-8"?>
<Pip5C4RegistrationStatusNotification xmlns="http://www.rosettanet.org/PIP5C4">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Distributor</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <RegistrationStatus>
      <registrationIdentifier>
        <ProprietaryRegistrationIdentifier>DR-2026-047562</ProprietaryRegistrationIdentifier>
      </registrationIdentifier>
      <registrationDecision>Approved</registrationDecision>
      <protectionLevel>Gold</protectionLevel>
      <validUntil><DateStamp>20260814</DateStamp></validUntil>
    </RegistrationStatus>
</Pip5C4RegistrationStatusNotification>

Transport and acknowledgment

Core of the standard: HTTPS POST to the partner endpoint or via AS2. S/MIME signature and Receipt Acknowledgment are systematic. PIP 5C4 is typically transported asynchronously.

The transport channel is typically AS2 or direct HTTPS (RNIF over HTTP). For a reference of the security layers in use, see the AS2 on ediverse page.

Use case

Cisco confirms to an Italian VAR via PIP 5C4 that deal 47,562 (24 Catalyst 9300 switches at a bank) is approved at Gold deal-protection level, valid for 90 days.

Further reading

• RosettaNet Standards Programme — GS1 US — official PIP catalogue.
• RosettaNet PIP Catalog (web.archive.org) — historical version of the rosettanet.org catalogue before its 2013 retirement.
• RosettaNet — hub on ediverse — overview, PIP / RNIF architecture, and clusters.
• AS2 on ediverse — alternative transport compatible with RNIF.