<?xml version="1.0" encoding="utf-8"?>
<?xml-model href="rfc7991bis.rnc"?>

<!DOCTYPE rfc [
  <!ENTITY nbsp "&#160;">
  <!ENTITY zwsp "&#8203;">
  <!ENTITY nbhy "&#8209;">
  <!ENTITY wj "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     category="std"
     consensus="true"
     docName="draft-liu-iotops-pqc-uasc-01"
     ipr="trust200902"
     sortRefs="true"
     submissionType="IETF"
     symRefs="true"
     tocInclude="true"
     version="3"
     xml:lang="en">

  <front>
    <title abbrev="PQC Protection Profile for OPC UA UASC">Post-Quantum Cryptographic Protection Profile for OPC UA Secure Conversation</title>
    <seriesInfo name="Internet-Draft" value="draft-liu-iotops-pqc-uasc-01"/>

    <author fullname="Penghui Liu" initials="P." role="editor" surname="Liu">
      <organization>Pengcheng Laboratory</organization>
      <address>
        <postal>
          <street>No.2 Xingke 1 Street</street>
          <city>Shenzhen</city>
          <code>518055</code>
          <country>China</country>
        </postal>
        <email>liuph@pcl.ac.cn</email>
      </address>
    </author>
    <author fullname="Rongwei Yang" initials="R." role="editor" surname="Yang">
      <organization>Pengcheng Laboratory</organization>
      <address>
        <postal>
          <street>No.2 Xingke 1 Street</street>
          <city>Shenzhen</city>
          <code>518055</code>
          <country>China</country>
        </postal>
        <email>yangrw@pcl.ac.cn</email>
      </address>
    </author>
    <author fullname="Yu Zhang" initials="Y." role="editor" surname="Zhang">
      <organization>Pengcheng Laboratory</organization>
      <address>
        <postal>
          <street>No.2 Xingke 1 Street</street>
          <city>Shenzhen</city>
          <code>518055</code>
          <country>China</country>
        </postal>
        <email>zhangy08@pcl.ac.cn</email>
      </address>
    </author>
    <author fullname="Xiaoxiong Zhong" initials="X." role="editor" surname="Zhong">
      <organization>Pengcheng Laboratory</organization>
      <address>
        <postal>
          <street>No.2 Xingke 1 Street</street>
          <city>Shenzhen</city>
          <code>518055</code>
          <country>China</country>
        </postal>
        <email>zhongxx@pcl.ac.cn</email>
      </address>
    </author>
    <author fullname="Yanjie  Gong" initials="Y." role="editor" surname="Gong">
      <organization>Schneider Electric</organization>
      <address>
        <postal>
          <street>Building A, No. 6 Wangjing East Road, Chaoyang District</street>
          <city>Beijing</city>
          <code>100102</code>
          <country>China</country>
        </postal>
        <email>garrett.gong@se.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="18"/>
    <area>Security</area>
    <workgroup>iotops</workgroup>
    <keyword>OPC UA</keyword>
    <keyword>Secure Conversation</keyword>
    <keyword>post-quantum cryptography</keyword>
    <keyword>ML-KEM</keyword>
    <keyword>ML-DSA</keyword>

    <abstract>
      <t>This document specifies a post-quantum cryptographic protection profile for the OPC Unified Architecture Secure Conversation protocol (OPC UA UASC) carried over the opc.tcp transport. The profile uses ML-KEM-768 for SecureChannel key establishment, ML-DSA for asymmetric signatures, HKDF-SHA-256 for key derivation, and AES-256-GCM for symmetric message protection. It defines the profile identifiers, nonce encoding, key schedule, authenticated-encryption inputs, certificate and public-key binding requirements, token rollover behavior, and conformance requirements.</t>
      <t>This Internet-Draft is a proposal for Standards Track publication. Permanent OPC UA SecurityPolicy and algorithm identifiers require coordination with the OPC Foundation; the private identifiers documented here remain provisional. This document does not assign official OPC UA identifiers or claim conformance with an OPC Foundation specification.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="introduction">
      <name>Introduction</name>
      <t>OPC Unified Architecture (OPC UA) is used in industrial automation and other operational technology environments. OPC UA Secure Conversation (UASC) provides application authentication, message integrity, confidentiality, and SecureChannel token management for transports such as <tt>opc.tcp</tt>. Existing deployments commonly rely on classical public-key algorithms in the application signature and SecureChannel establishment path. A sufficiently capable quantum computer would threaten those algorithms and would also make recorded traffic vulnerable to retrospective decryption when long-term authentication or key-establishment keys are compromised.</t>
      <t>This document defines a concrete profile that can be implemented by UASC stacks while the OPC UA ecosystem evaluates post-quantum and hybrid migration options. The profile is deliberately narrow: it describes one ML-KEM parameter set, three ML-DSA parameter-set variants, one HKDF construction, and one AEAD construction. The narrow profile makes byte-level interoperability testing possible and exposes the protocol decisions that require review before standardization.</t>
      <t>This document proposes a Standards Track profile for community review. It describes a protocol mapping for OPC UA, but it does not replace OPC UA Part 4 or Part 6 and does not create a new official OPC UA SecurityPolicy. An implementation claiming support for this draft MUST treat the private identifiers as provisional. Identifier coordination and remaining technical review items are recorded in <xref target="identifier-coordination"/> and <xref target="open-issues"/>.</t>
    </section>

    <section anchor="conventions">
      <name>Conventions and Requirements Language</name>
      <t>The key words <bcp14>MUST</bcp14>, <bcp14>MUST NOT</bcp14>, <bcp14>REQUIRED</bcp14>, <bcp14>SHALL</bcp14>, <bcp14>SHALL NOT</bcp14>, <bcp14>SHOULD</bcp14>, <bcp14>SHOULD NOT</bcp14>, <bcp14>RECOMMENDED</bcp14>, <bcp14>NOT RECOMMENDED</bcp14>, <bcp14>MAY</bcp14>, and <bcp14>OPTIONAL</bcp14> in this document are to be interpreted as described in <xref target="RFC2119"/> and <xref target="RFC8174"/> when, and only when, they appear in all capitals.</t>
    </section>

    <section anchor="scope">
      <name>Scope and Relationship to OPC UA</name>
      <t>This document specifies a cryptographic profile for the UASC OpenSecureChannel (OPN), Message (MSG), and CloseSecureChannel (CLO) message paths. It assumes the message framing, sequence headers, SecurityToken fields, endpoint discovery, session services, and application-layer semantics defined by OPC UA Part 4 and Part 6 <xref target="OPCUA-Part4"/><xref target="OPCUA-Part6"/>.</t>
      <t>The profile does not define a new transport, a new OPC UA service, a new user identity token, or a replacement for the OPC UA certificate profile. In particular, an implementation MUST continue to enforce the OPC UA ApplicationUri and certificate validation rules applicable to its deployment. The profile defines additional requirements for binding an ML-DSA verification key to the authenticated application identity.</t>
      <t>Formal allocation of a permanent OPC UA SecurityPolicy URI, inclusion in the OPC UA SecurityPolicy table, and changes to OPC UA conformance requirements are outside the authority of this document and require coordination with the OPC Foundation.</t>
    </section>

    <section anchor="threat-model">
      <name>Threat Model and Design Goals</name>
      <t>The adversary is assumed to control or observe the network between UASC peers, inject, delete, replay, delay, reorder, and modify messages, and record traffic for later cryptanalysis. The adversary can submit malformed public keys, ciphertexts, signatures, certificates, and message headers. The adversary is not assumed to have extracted an endpoint's private ML-KEM or ML-DSA key, compromised the certificate trust anchor, or obtained an implementation's protected signing-service authorization token.</t>
      <t>The profile has the following goals:</t>
      <ul>
        <li>Provide a post-quantum key-establishment path for the SecureChannel symmetric keys.</li>
        <li>Authenticate OPN messages with a post-quantum signature and bind the signature key to the application certificate and configured peer identity.</li>
        <li>Provide confidentiality and integrity for MSG and CLO traffic with an AEAD construction.</li>
        <li>Preserve UASC SecurityToken rollover, chunking, and sequence-number processing.</li>
        <li>Make algorithm identifiers, byte ordering, key labels, and authenticated data explicit enough for independent implementations.</li>
      </ul>
      <t>The profile does not claim protection against endpoint compromise, denial of service, traffic analysis, implementation side channels, weak random-number generators, or a compromised certificate authority. Those risks require deployment and implementation controls in addition to this profile.</t>
    </section>

    <section anchor="profile-identification">
      <name>Profile Identification and Algorithm Suites</name>
      <t>A peer selects this profile using the SecurityPolicy identifier advertised by the OPC UA endpoint. The following provisional identifiers are restricted to explicitly configured development deployments. This document does not register the <tt>urn:open62541-pqc</tt> namespace or assign permanent OPC UA identifiers:</t>
      <table>
        <thead>
          <tr>
            <th>SecurityPolicy identifier</th>
            <th>Signature algorithm</th>
            <th>Key establishment</th>
            <th>Message protection</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td>urn:open62541-pqc:SecurityPolicy#ML-KEM-768-ML-DSA-44-AES-256-GCM</td>
            <td>ML-DSA-44</td><td>ML-KEM-768</td><td>AES-256-GCM</td>
          </tr>
          <tr>
            <td>urn:open62541-pqc:SecurityPolicy#ML-KEM-768-ML-DSA-65-AES-256-GCM</td>
            <td>ML-DSA-65</td><td>ML-KEM-768</td><td>AES-256-GCM</td>
          </tr>
          <tr>
            <td>urn:open62541-pqc:SecurityPolicy#ML-KEM-768-ML-DSA-87-AES-256-GCM</td>
            <td>ML-DSA-87</td><td>ML-KEM-768</td><td>AES-256-GCM</td>
          </tr>
        </tbody>
      </table>
      <t>All three variants use the same key-establishment, key-derivation, nonce, and AEAD rules. Only the ML-DSA parameter set and the resulting signature and public-key lengths differ. An endpoint MUST select exactly one variant for a SecureChannel. A peer MUST reject an endpoint that changes the variant after the SecureChannel has been opened.</t>
      <t>The mandatory-to-implement suite is ML-KEM-768 with ML-DSA-65, HKDF-SHA-256, and AES-256-GCM. Implementations MAY additionally support ML-DSA-44 and ML-DSA-87. Support for a suite does not authorize its use for a peer: endpoint selection and authenticated local policy MUST agree on the suite, the application identity, and the verification key. A mismatch MUST fail without silent fallback.</t>
      <t>The provisional algorithm identifiers for this draft are:</t>
      <ul>
        <li><tt>urn:open62541-pqc:ML-DSA-44</tt>, <tt>urn:open62541-pqc:ML-DSA-65</tt>, or <tt>urn:open62541-pqc:ML-DSA-87</tt> for OPN signatures.</li>
        <li><tt>urn:open62541-pqc:OPN-SignedOnly</tt> for the OPN asymmetric-encryption operation.</li>
        <li><tt>urn:open62541-pqc:AES-256-GCM-Tag</tt> for the symmetric authentication tag operation.</li>
        <li><tt>urn:open62541-pqc:AES-256-GCM</tt> for symmetric encryption and decryption.</li>
      </ul>
      <t>These identifiers have no IANA or OPC Foundation allocation asserted by this draft. Permanent identifiers and their publication authority remain to be agreed as described in <xref target="identifier-coordination"/>. An identifier change MUST NOT silently change the associated algorithm, signature input, key derivation, or wire encoding.</t>
    </section>

    <section anchor="handshake">
      <name>SecureChannel Key Establishment</name>
      <t>The profile maps ML-KEM to the two SecureChannel nonces exchanged in the OPN request and response. The client generates an ML-KEM-768 key pair and sends the public key as the client SecureChannel nonce. The server encapsulates to that public key and sends the resulting ciphertext as the server SecureChannel nonce. The peer MUST verify the exact lengths before invoking the KEM operation.</t>
      <table>
        <thead>
          <tr><th>Value</th><th>Encoding</th><th>Length</th></tr>
        </thead>
        <tbody>
          <tr><td>Client SecureChannel nonce</td><td>ML-KEM-768 public key, opaque octets</td><td>1184 octets</td></tr>
          <tr><td>Server SecureChannel nonce</td><td>ML-KEM-768 ciphertext, opaque octets</td><td>1088 octets</td></tr>
          <tr><td>ML-KEM shared secret</td><td>ML-KEM output, kept internal</td><td>32 octets</td></tr>
        </tbody>
      </table>
      <t>For a client-generated public key <tt>PK</tt>, a server computes <tt>(CT, SS) = Encaps(PK)</tt>. The client computes <tt>SS = Decaps(SK, CT)</tt>. A KEM failure, a length mismatch, or a decapsulation failure MUST abort the SecureChannel without exposing a distinguishable oracle to an unauthenticated peer.</t>
      <t>The client and server nonce values are also the key-establishment transcript inputs. They MUST be used exactly as received, including all leading or trailing zero octets. Implementations MUST NOT parse, normalize, compress, or concatenate them using a text encoding.</t>
      <t>The KEM operation is performed within the OPN exchange already defined by UASC. No additional UASC message type is introduced. A peer that does not understand the profile will not be able to interpret the nonce lengths or profile identifier and MUST fail closed during endpoint or SecureChannel negotiation.</t>
    </section>

    <section anchor="key-schedule">
      <name>Key Schedule</name>
      <t>The profile derives one client-to-server and one server-to-client key and initialization vector from the ML-KEM shared secret. Let <tt>CN</tt> be the client nonce, <tt>SN</tt> be the server nonce, and <tt>SS</tt> be the 32-octet ML-KEM shared secret.</t>
      <t>First compute:</t>
      <t><tt>salt = SHA-256(CN || SN)</tt></t>
      <t>where <tt>||</tt> denotes octet-string concatenation and the client value precedes the server value regardless of which peer performs the computation. Then, for each direction, apply HKDF-SHA-256 <xref target="RFC5869"/> with:</t>
      <ul>
        <li>HKDF-Extract salt: <tt>salt</tt>.</li>
        <li>HKDF-Extract input keying material: <tt>SS</tt>.</li>
        <li>HKDF-Expand info for client-to-server: the ASCII octets of <tt>open62541-private-PQC-UASC-v1/c2s</tt>.</li>
        <li>HKDF-Expand info for server-to-client: the ASCII octets of <tt>open62541-private-PQC-UASC-v1/s2c</tt>.</li>
        <li>HKDF-Expand length: 44 octets.</li>
      </ul>
      <t>For a direction-specific output <tt>OKM</tt>, the first 32 octets are the AES-256-GCM key and the final 12 octets are the base initialization vector:</t>
      <t><tt>key = OKM[0..31]</tt></t>
      <t><tt>base-iv = OKM[32..43]</tt></t>
      <t>The client uses the <tt>c2s</tt> material for locally generated MSG and CLO chunks and the <tt>s2c</tt> material for received chunks. The server uses the inverse mapping. Direction labels are part of the transcript domain separation and MUST be compared as exact ASCII octets.</t>
      <t>The HKDF labels above are exact ASCII protocol constants for this draft, with no trailing zero octet. A revision that changes a label or the key schedule MUST use a distinct profile identifier and specify the resulting compatibility and migration rules.</t>
    </section>

    <section anchor="opn-signatures">
      <name>OPN Signature Processing</name>
      <t>OPN messages use the UASC asymmetric signing input defined by OPC UA Part 6. The profile replaces the classical signature algorithm with the selected ML-DSA parameter set. The signer and verifier MUST use the exact serialized UASC signing input, without adding a profile-specific text prefix or changing the OPC UA byte order.</t>
      <t>Signatures use ML-DSA as specified in FIPS 204 <xref target="FIPS204"/> with an empty context string. HashML-DSA, an implementation-specific prehash, and a nonempty context are not interchangeable with this operation. The public-key and signature lengths for ML-DSA-44, ML-DSA-65, and ML-DSA-87 are respectively 1312 and 2420, 1952 and 3309, and 2592 and 4627 octets.</t>
      <t>This profile defines OPN as signed-only. The asymmetric-encryption operation is therefore a no-op for the OPN payload, while the ML-DSA signature authenticates the OPN signing input. OPN confidentiality is not provided by this profile; confidentiality begins with the symmetric MSG and CLO path after the SecureChannel keys have been derived. Implementations and user interfaces MUST NOT describe this signed-only OPN behavior as full OPN encryption.</t>
      <t>The ML-DSA public key used for verification MUST be bound to the authenticated application identity. At minimum, the verifier MUST check:</t>
      <ul>
        <li>the peer certificate chain and validity period according to the deployment trust policy;</li>
        <li>the OPC UA ApplicationUri and certificate URI SAN binding;</li>
        <li>the configured ML-DSA public-key binding for the peer; and</li>
        <li>the selected ML-DSA parameter set and exact public-key length.</li>
      </ul>
      <t>A successful X.509 path check alone MUST NOT authorize an unrelated ML-DSA public key. Conversely, a matching ML-DSA key pin MUST NOT replace certificate validity, application identity, or authorization checks.</t>
    </section>

    <section anchor="symmetric-protection">
      <name>MSG and CLO Authenticated Encryption</name>
      <t>MSG and CLO chunks use AES-256-GCM <xref target="RFC5116"/> with a 32-octet direction key, a 12-octet nonce, a 16-octet authentication tag, and no padding introduced by this profile. The UASC message and symmetric security headers are left in cleartext as required for routing and token selection. The sequence header and payload are included in the encrypted portion.</t>
      <t>The additional authenticated data (AAD) is the first 16 octets of the chunk: the three-octet MessageType, one-octet ChunkType, four-octet MessageSize, four-octet SecureChannelId, and four-octet SecurityToken identifier, in that order. Each integer uses the UASC little-endian encoding. MessageSize counts the complete chunk, including the headers, ciphertext, and 16-octet tag. The AAD MUST be taken from the exact transmitted or received octets. In particular, SecureChannelId MUST NOT be omitted.</t>
      <t>The plaintext is the eight-octet SequenceHeader (SequenceNumber followed by RequestId, each a little-endian UInt32) followed by the chunk body. No additional counter is serialized. Let <tt>Q</tt> be that SequenceNumber and <tt>S = Q - 1</tt>. The sequence and receiver prediction rules are defined in <xref target="sequence-tokens"/>. Let <tt>IV</tt> be the direction-specific base IV and <tt>T</tt> the SecurityToken identifier from this chunk. The profile constructs the 12-octet GCM nonce as follows:</t>
      <t><tt>N[0..11] = IV</tt></t>
      <t><tt>N[0..3] = N[0..3] XOR LE32(T)</tt></t>
      <t><tt>N[4..7] = N[4..7] XOR LE32(S)</tt></t>
      <t><tt>N[8..11]</tt> remains unchanged.</t>
      <t>Here <tt>LE32</tt> is the four-octet little-endian encoding and XOR is bytewise. The subtraction in <tt>S = Q - 1</tt> is ordinary integer subtraction, not modular arithmetic. For example, an all-zero base IV, token <tt>0x01020304</tt>, and <tt>Q = 2</tt> produce nonce <tt>040302010100000000000000</tt> in hexadecimal. The sender and receiver MUST use this exact nonce calculation for each protected chunk.</t>
      <t>The ciphertext and tag are serialized as the ciphertext followed immediately by the 16-octet GCM tag. A receiver MUST verify the tag before releasing any decrypted octets to the UASC message decoder or application. Authentication failure, an invalid token, an invalid sequence transition, or a nonce reuse condition MUST terminate the affected SecureChannel.</t>
    </section>

    <section anchor="sequence-tokens">
      <name>Sequence Numbers, Replay, and SecurityToken Rollover</name>
      <t>The initial signed OPN in each direction uses SequenceNumber 0. Every subsequent OPN, MSG, or CLO chunk in that direction increments the SequenceNumber by one. The counter is maintained for the SecureChannel, independently of the RequestId, and MUST NOT be reset on token renewal. This profile requires a new SecureChannel before sequence-number wraparound; it does not use a legacy rollover window.</t>
      <t>A receiver initializes its last accepted sequence <tt>L</tt> from the successfully verified initial OPN. Before decrypting an MSG or CLO chunk, it predicts <tt>Q = L + 1</tt> and uses <tt>S = L</tt> to compute the nonce. It then verifies the AEAD tag and checks that the decrypted SequenceNumber equals the predicted <tt>Q</tt>. Only after both checks succeed may it update <tt>L</tt> and release the chunk. A subsequent signed OPN also MUST carry <tt>L + 1</tt> and pass signature verification before advancing <tt>L</tt>. A duplicate, gap, out-of-order chunk, or exhausted sequence space MUST terminate the affected SecureChannel.</t>
      <t>During SecurityToken rollover, a peer MAY receive a message protected under the previous token while the new token is already locally installed, as permitted by UASC. The receiver MUST select the SecurityToken identifier from the chunk's cleartext symmetric security header when selecting the direction key and computing the nonce. It MUST NOT blindly use only the newest locally stored token.</t>
      <t>Each token MUST identify the direction keys and base IVs derived for its corresponding authenticated OPN exchange. Every renewal MUST use a fresh client ML-KEM key pair and fresh server encapsulation. Previous-token keys MAY be retained only for the validity overlap allowed by UASC and MUST be removed when that token expires. An unknown or expired token MUST be rejected before application delivery.</t>
      <t>Token identifiers and sequence numbers are finite fields. An implementation MUST ensure that the same direction key and base IV are never used with a repeated effective nonce. Before exhaustion or wraparound of the sequence space, the implementation MUST establish a new SecureChannel and fresh ML-KEM shared secret. A SecurityToken rollover alone is insufficient if it can reuse the same key, IV, token identifier, and sequence tuple.</t>
      <t>Chunking does not change the AEAD construction. Each chunk is independently authenticated with its own AAD and effective sequence counter. The UASC message reassembly layer MUST deliver a complete message only after every chunk has passed authentication and sequence validation.</t>
    </section>

    <section anchor="certificates">
      <name>Certificates and Key Binding</name>
      <t>Deployments MUST use certificates and trust processing compatible with OPC UA Part 6 and the applicable X.509 profile <xref target="RFC5280"/>. The certificate's ApplicationUri and key usage constraints remain authoritative for OPC UA application identity.</t>
      <t>Implementations MUST support an authenticated, out-of-band binding containing the expected ApplicationUri, peer role, selected ML-DSA parameter set, and exact FIPS 204 public-key octets. The binding MUST be provisioned through an authorized configuration channel, checked together with the X.509 identity, and replaced only through an authorized credential update. A key received in an OPN message or an unverified discovery response MUST NOT create or replace this binding.</t>
      <t>A separately specified certificate-based binding MAY be supported in addition to this baseline. Its extension syntax, validation, and authorization rules must be defined by that specification; this document does not invent an extension identifier. A key mismatch, expired or revoked binding, or failure of the required certificate checks MUST fail authentication.</t>
      <t>If authentication depends on a PKI service response, a failed, unavailable, malformed, expired, revoked, or unauthorized response MUST be treated as a failed authentication decision.</t>
      <t>Private keys, signing-service credentials, and certificate-status tokens MUST be protected as operational secrets. Logging MUST NOT disclose private keys, KEM secret keys, shared secrets, bearer tokens, or complete unredacted certificates when those values are not required for diagnosis.</t>
    </section>

    <section anchor="negotiation">
      <name>Negotiation, Downgrade, and Failure Handling</name>
      <t>A client MUST verify that the selected endpoint advertises the requested provisional SecurityPolicy identifier and the required SignAndEncrypt security mode before opening a SecureChannel. A server MUST reject an OPN request whose profile identifier, nonce length, ML-DSA algorithm, or key length is inconsistent with the configured endpoint.</t>
      <t>An implementation supporting both classical and post-quantum policies MUST apply an explicit local policy for algorithm selection. It MUST NOT silently fall back from this profile to a classical policy after a cryptographic failure, an unsupported nonce length, a signature failure, or a certificate-binding failure. Any fallback, if permitted by deployment policy, MUST require a separate endpoint selection or an explicit authenticated configuration decision.</t>
      <t>Malformed, truncated, overlong, or unexpected nonce fields MUST cause the OPN exchange to fail. KEM, ML-DSA, HKDF, AES-GCM, certificate, and token-processing errors MUST be reported as a generic secure-channel failure to an unauthenticated peer. Detailed diagnostics MAY be logged locally but MUST be access controlled and MUST avoid secret material.</t>
    </section>

    <section anchor="conformance">
      <name>Conformance Requirements</name>
      <t>A conforming implementation:</t>
      <ol>
        <li>MUST implement exact ML-KEM-768 public-key, ciphertext, and shared-secret lengths.</li>
        <li>MUST implement ML-DSA-65, MAY additionally implement ML-DSA-44 and ML-DSA-87, and MUST reject parameter-set mismatches.</li>
        <li>MUST implement the byte-exact nonce, AAD, HKDF, and AES-GCM rules in this document.</li>
        <li>MUST use a cryptographically secure random generator for ML-KEM key generation and other profile nonces.</li>
        <li>MUST perform constant-time or library-provided verification operations where required by the selected cryptographic library.</li>
        <li>MUST reject modified ciphertext, invalid tags, duplicate sequence numbers, invalid tokens, incorrect certificate or ML-DSA key bindings, parameter-set mismatches, and malformed KEM values.</li>
      </ol>
      <t>Implementations MUST use the algorithm and parameter definitions in NIST FIPS 203 and FIPS 204 <xref target="FIPS203"/><xref target="FIPS204"/>. This requirement does not assert that a particular implementation has obtained cryptographic-module validation.</t>
    </section>

    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document makes no request of IANA at this stage. In particular, it does not register a URN namespace or assign an OPC UA SecurityPolicy or algorithm identifier. OPC UA identifier coordination is described in <xref target="identifier-coordination"/>. If an IANA-managed namespace is selected during review, the corresponding registration request must be added to this section before publication.</t>
    </section>

    <section anchor="identifier-coordination">
      <name>OPC UA Identifier Coordination</name>
      <t>Permanent SecurityPolicy and algorithm identifiers, their ownership, and the relationship to OPC UA conformance requirements require agreement with the OPC Foundation. The private identifiers in <xref target="profile-identification"/> specify provisional profile selection; they MUST NOT be advertised as officially allocated identifiers.</t>
      <t>Before publication as a Proposed Standard, this draft needs to document the agreed permanent identifiers or an explicitly accepted identifier scheme, the applicable OPC UA specification changes, and a migration rule from the private identifiers. Peers MUST select the same exact profile identifier. A peer MUST NOT infer compatibility by rewriting or aliasing an unfamiliar identifier.</t>
    </section>

    <section anchor="open-issues">
      <name>Open Issues</name>
      <t>This section records unresolved specification and review work. It does not relax the protocol requirements above. The issues are to be resolved or otherwise explicitly addressed before Proposed Standard publication.</t>
      <ul>
        <li>Complete OPC Foundation coordination for identifiers, the signed-only OPN mapping, and the relationship to OPC UA SecurityPolicy conformance.</li>
        <li>Validate the <tt>S = Q - 1</tt> nonce calculation and receive prediction rule for the initial OPN, first MSG, renewal, previous-token overlap, multi-chunk messages, and counter exhaustion. Publish byte-level vectors for these cases.</li>
        <li>Specify and review the complete OPN request and response signature transcripts, including any request-signature binding required by the selected OPC UA mapping, together with key confirmation, replay resistance, and downgrade handling.</li>
        <li>Review the mandatory suite, AES-GCM key-usage and failed-verification limits, resource bounds, and certificate and ML-DSA identity bindings. Publish canonical vectors covering key establishment, signature inputs, key derivation, AAD, plaintext, ciphertext, and authentication tags for the mandatory suite.</li>
      </ul>
    </section>

    <section anchor="security">
      <name>Security Considerations</name>
      <t>This document defines a post-quantum cryptographic profile, but the security of a deployment depends on the complete UASC implementation and its operational environment. Security review needs to consider the protocol and its deployment using the guidance in <xref target="RFC3552"/>. ML-KEM-768 and ML-DSA are assumed to provide the security properties documented by their standard specifications. This document does not make an independent security claim about those algorithms or about any particular cryptographic library.</t>
      <t>The profile currently uses pure ML-KEM and ML-DSA. It does not combine a classical key-establishment secret with the ML-KEM secret. Deployments that require protection if either a classical or post-quantum assumption fails need a separately specified hybrid construction; they MUST NOT infer hybrid security from this profile.</t>
      <t>OPN is signed-only in this profile. OPN metadata and the OPN payload are therefore not confidential. An observer can learn the existence, timing, and size of the OPN exchange. Deployments requiring OPN confidentiality need a separately reviewed profile that defines and tests an asymmetric encryption or hybrid protection operation.</t>
      <t>AES-GCM security depends on nonce uniqueness under each key. The token and sequence masking rules are intended to prevent nonce reuse across protected chunks, but an implementation bug in sequence handling, token rollover, concurrent send paths, or counter wraparound can invalidate this property. Implementations MUST serialize or otherwise coordinate counter allocation, MUST test rollover and restart behavior, and MUST establish fresh keys before counter exhaustion.</t>
      <t>Certificate trust, ML-DSA key binding, and downgrade protection are part of the authenticated security boundary. Accepting a valid X.509 certificate with an unrelated ML-DSA key, accepting a key solely because it is pinned, or silently selecting a weaker classical policy can defeat the intended authentication or post-quantum property.</t>
      <t>External signing and certificate-status services create availability and authorization dependencies. Deployments using such services SHOULD bound request time and isolate failures to limit denial-of-service exposure. Service authorization tokens MUST be protected, the service endpoint MUST be authenticated and authorized according to local policy, and a failed required authentication check MUST fail closed.</t>
      <t>Industrial control systems have safety and availability requirements that are not addressed by this profile. Operators SHOULD test failure behavior, certificate renewal, key rollover, endpoint recovery, and resource exhaustion in an isolated environment before enabling the profile on a production control network.</t>
    </section>

  </middle>

  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="Scott Bradner" initials="S." surname="Bradner"/>
            <date year="1997" month="March"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="Barry Leiba" initials="B." surname="Leiba"/>
            <date year="2017" month="May"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
        </reference>
        <reference anchor="RFC5116" target="https://www.rfc-editor.org/info/rfc5116">
          <front>
            <title>An Interface and Algorithms for Authenticated Encryption</title>
            <author fullname="David McGrew" initials="D." surname="McGrew"/>
            <author fullname="David Viega" initials="D." surname="Viega"/>
            <date year="2008" month="January"/>
          </front>
          <seriesInfo name="RFC" value="5116"/>
        </reference>
        <reference anchor="RFC5869" target="https://www.rfc-editor.org/info/rfc5869">
          <front>
            <title>HMAC-based Extract-and-Expand Key Derivation Function (HKDF)</title>
            <author fullname="Hugo Krawczyk" initials="H." surname="Krawczyk"/>
            <author fullname="Pasi Eronen" initials="P." surname="Eronen"/>
            <date year="2010" month="May"/>
          </front>
          <seriesInfo name="RFC" value="5869"/>
        </reference>
        <reference anchor="RFC5280" target="https://www.rfc-editor.org/info/rfc5280">
          <front>
            <title>Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</title>
            <author fullname="David Cooper" initials="D." surname="Cooper"/>
            <author fullname="Stephan Santesson" initials="S." surname="Santesson"/>
            <author fullname="Stephen Farrell" initials="S." surname="Farrell"/>
            <author fullname="Sean Boeyen" initials="S." surname="Boeyen"/>
            <author fullname="Russ Housley" initials="R." surname="Housley"/>
            <date year="2008" month="May"/>
          </front>
          <seriesInfo name="RFC" value="5280"/>
        </reference>
        <reference anchor="OPCUA-Part4" target="https://reference.opcfoundation.org/Core/Part4/v105/docs/">
          <front>
            <title>OPC Unified Architecture Specification, Part 4: Services</title>
            <author fullname="OPC Foundation" initials="O." surname="OPC Foundation"/>
            <date year="2023"/>
          </front>
        </reference>
        <reference anchor="OPCUA-Part6" target="https://reference.opcfoundation.org/Core/Part6/v105/docs/">
          <front>
            <title>OPC Unified Architecture Specification, Part 6: Mappings</title>
            <author fullname="OPC Foundation" initials="O." surname="OPC Foundation"/>
            <date year="2023"/>
          </front>
        </reference>
        <reference anchor="FIPS203" target="https://csrc.nist.gov/pubs/fips/203/final">
          <front>
            <title>Module-Lattice-Based Key-Encapsulation Mechanism Standard</title>
            <author fullname="National Institute of Standards and Technology" initials="N." surname="NIST"/>
            <date year="2024" month="August"/>
          </front>
          <seriesInfo name="FIPS" value="203"/>
        </reference>
        <reference anchor="FIPS204" target="https://csrc.nist.gov/pubs/fips/204/final">
          <front>
            <title>Module-Lattice-Based Digital Signature Standard</title>
            <author fullname="National Institute of Standards and Technology" initials="N." surname="NIST"/>
            <date year="2024" month="August"/>
          </front>
          <seriesInfo name="FIPS" value="204"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="RFC3552" target="https://www.rfc-editor.org/info/rfc3552">
          <front>
            <title>Guidelines for Writing RFC Text on Security Considerations</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <author fullname="B. Korver" initials="B." surname="Korver"/>
            <date year="2003" month="July"/>
          </front>
          <seriesInfo name="BCP" value="72"/>
          <seriesInfo name="RFC" value="3552"/>
        </reference>
      </references>
    </references>
  </back>
</rfc>
