Search
5 result(s) for AdditionalHeader
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.15 EphemeralKeyTypedata back to the owner of the key. This Structure is used in the additionalHeader with the AdditionalParametersType defined in 7.1 . See OPC 10000-6 for a discussion
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.15 Messagesreduce the attack surface, any Messages can include random data inserted into the AdditionalHeader field of the RequestHeader or ResponseHeader . The key name for this random data is specified ... Table 14 . Table 14 - Padding AdditionalHeader Key Name Name DataType Description Padding ByteString Provides random padding that varies the sizes of Messages . The length is random number of bytes from
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsCreateSession / ActivateSession handshake to do this. For that reason, EphemeralKeys are returned in the AdditionalHeader field of the ResponseHeader of the CreateSession and ActivateSession responses. An overview of the handshake ... list of name-value pairs. An instance of this type is passed in the AdditionalHeader field. Instances of the EphemeralKeyType defined in OPC 10000-4 are passed as values
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappingsmechanisms defined for ECC in 6.8.2 . This includes using the misnamed EccEncryptedSecret and the AdditionalHeader key names defined in Table 70 . The RSA-DH Key Negotiation process is show
-
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject ModelService call. The SpanContextDataType is transported with the AdditionalParametersType in the AdditionalHeader field of the RequestHeader (see OPC 10000-4 ). The Key for the parameter is "SpanContext ... Value is the SpanContextDataType Structure . If a Server receives the optional AdditionalHeader , it uses the provided SpanConextDataType Structure when generating any LogRecords that are generated related to the Service invocation