Table of Contents
1Scope,PurposeandApplication
1.1Scope
1.2Purpose
1.3Application
2References
2.1Normativereferences
2.2Informativereferences
3Definitions
4Abbreviations
5Overview
5.1Securitytransformations
5.2Securityinformationexchange
5.3Abstractsyntaxfornegotiationofsecurity
parameters
6Model
7Serviceoverview
7.1Associationservices
7.2STASE-ROSEservices
7.3Relationshiptopresentationservices
7.4Servicedefinition
8Interactionbetweenapplicationserviceelements
8.1Associationestablishment
8.2Associationrelease
8.3Associationabort
8.4Datatransfer
9STASE-ROSEprotocol
9.1AbstractsyntaxdefinitionofAPDUs
9.2Abstractsyntaxname
9.3Algorithmsidentifiers
9.4Applicationcontextsnames
9.5STASE-ROSEprocedures
9.6MappingofSTASE-ROSEservicestopresentation
service
10MappingofROSEservicestoSTASE-ROSEservices
11Conformance
12SRPMstatetables
12.1Conventions
12.2ActionstobetakenbySRPM
13Remote-Operations-Protocol-Machinestatetables
AnnexA-SecureCMISE
A.1Applicationcontext
A.2Associationestablishmentrules
A.3Conformance
AnnexB-ASN.1SyntaxdefinedinthisRecommendation
B.1Abstractsyntaxforpublickeyauthenticator
B.2Abstractsyntaxfornegotiationofsecurity
parameters
B.3AbstractsyntaxdefinitionofAPDUs
B.4Abstractsyntaxobjectidentifier
B.5Applicationcontextsnames
AppendixI-Monotonicallyincreasingtimeforsecurity
AppendixII-Negotiationofsecurityalgorithmsexample
AppendixIII-GSS-APIusewithSTASE-ROSE
III.1AssociationEstablishmentphase
III.2Datatransferphase Abstract
Provides specifications to support security transformations, such as encryption, hashing, sealing and signing, focusing on whole Remote Operations Service Element (ROSE) Protocol Data Units (PDUs). Security transformations are used to provide various security services such as authentication, confidentiality, integrity and non-repudiation.
