Forum
Please follow a discussion, or create a new item...
Write post Create new topic Back to overview
AARQ BIT STRING
 | Gyozo Kmethy (04/06/2010 13:53): Dear Prithvi, See Green Book Table 74. For more details please see ISO/IEC 8649 / X.217 9.1.1.15: 9.1.1.15 ACSE Requirements This parameter is used by the requestor to indicate the functional units requested for the association. If not present, only the Kernel functional unit is available for the association. In supporting this negotiation mechanism, the ACSE service-provider removes values for unsupported functional units before issuing the indication primitive to the acceptor. This parameter is used by the acceptor to indicate which of the requested functional units the acceptor selects. The acceptor shall not select a functional unit in the response primitive which was not requested in the indication primitive. The value of the parameter in the response primitive is delivered unchanged in the confirm primitive. This parameter may take one or more of the following symbolic values: – authentication; – application context negotiation. best regards Gyozo |
| Prithvi (04/06/2010 04:26): Dear Gyozo, Plz Clear my query. Regards, Prithvi |
| Prithvi (03/06/2010 04:53): Dear All, what is the significance of BIT STRING in the AARQ Frame (sender-acse-requirements component i.e. encoding the number of unused bits in the last byte of the BIT STRING) while using low / high level security. Where the value of this BIT STRING is used, unable to relate this in AARQ Frame. Regards, Prithvi |