The first subelement of all payloads is cm-header
. The cm-header
element contains information about the identity of the two parties that exchange the payload.
<!ELEMENT cm-header (cm-sender, cm-receiver?, cm-authentication?)> <!ELEMENT cm-sender EMPTY> <!ATTLIST cm-sender sender-id CDATA #REQUIRED name CDATA #REQUIRED> <!ELEMENT cm-receiver EMPTY> <!ATTLIST cm-receiver receiver-id CDATA #REQUIRED name CDATA #REQUIRED > <!ELEMENT cm-authentication EMPTY> <!ATTLIST cm-authentication login CDATA #REQUIRED password CDATA #REQUIRED >
The cm-sender
element must always appear as the subelement of the cm-header
element. It specifies the identity of the payload sender. The attributes of the cm-sender
elements have the following meanings:
sender-id
sender-id
.name
The cm-receiver
element specifies the identity of the desired receiver of the payload. This element is optional as long as there is an individual network connection between the server and the client. In this case, the sender of the payload and the receiver are uniquely identified. If, however, between the server and the client there is a proxy server which serves several clients or servers, both the server and the client can use the cm-receiver
element to inform the proxy server of the receiver. The attributes of the cm-receiver
elements have the following meanings:
receiver-id
sender-id
attribute of the cm-sender
element. It contains the ID of the NPS server or NPS client which is to receive the payload. The ID is unique within a communication context. For response payloads, this attribute is always a copy of the sender-id
attribute of the cm-sender
element in the corresponding request payload.name
name
attribute of the cm-sender
element in the corresponding request payload.The cm-authentication
element is optional. It can only be used in request payloads. It contains information about the user for whom the request is to be processed. The attributes of the cm-authentication
element have the following meanings:
login
password