rfc2524.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.


RFC 2524                          EMSD                     February 1999


   Duplicate operation detection is necessary for this operation.

   The successful completion of the ES-OPERATION signifies that the
   EMSD-SA has accepted responsibility for the message (but not that it
   has delivered it to its intended recipients).

   The disruption of the ES-OPERATION by an error signifies that the
   EMSD-SA cannot assume responsibility for the message.


   Arguments

   This operation's arguments are:

   SubmitArgument ::= SEQUENCE
   {
     -- Security features
     security                [0]    IMPLICIT SecurityElement OPTIONAL,

     -- Segmentation features for efficient transport
     segment-info                            SegmentInfo OPTIONAL,

     -- Content type of the message
     content-type                            ContentType,

     --
     -- THE CONTENT --
     --

     -- The submission content
     content                                 ANY DEFINED BY content-type
   };


   The fields are:


   Security

   See Section 3.4.1, "SecurityElements".


   Segment-info

   See Section 3.4.2, "Message Segmentation and Reassembly".






Banan                        Informational                     [Page 15]

RFC 2524                          EMSD                     February 1999


   Content-type

   This argument identifies the type of the content of the message.  It
   identifies the abstract syntax and the encoding rules used.


   Content

   This argument contains the information the message is intended to
   convey to the recipient(s).  It shall be generated by the originator
   of the message.


   Results

   This operation's results are:

   SubmitResult ::= SEQUENCE

       {
           -- Permanent identifier for this message.
           -- Also contains the message submission time.
           -- See comment regarding assignment of message identifiers,
           -- at the definition of EMSDLocalMessageId.

           message-id                              EMSDLocalMessageId

       };


   The fields are:


   Message-id

   This result contains an EMSD-SA-identifier that uniquely and
   unambiguously identifies the message-submission.  It shall be
   generated by the EMSD-SA.


   Errors

   See Section 3.4.3.








Banan                        Informational                     [Page 16]

RFC 2524                          EMSD                     February 1999


3.2.2  deliveryControl

   The deliveryControl ES-OPERATION enables the EMSD-UA to temporarily
   limit the operations that the EMSD-SA may invoke, and the messages
   that the EMSD-SA may deliver to the EMSD-UA via the Message delivery
   ES-OPERATION.

   deliveryControl ES-OPERATION
       ARGUMENT DeliveryControlArgument
       RESULT DeliveryControlResult
       ERRORS
       {
           securityError,
           resourceError,
           protocolViolation
       } ::= 2;

   The duplicate operation detection is not required for this operation.

   The EMSD-SA shall hold until a later time, rather than abandon, ES-
   OPERATIONS and messages that are presently suspended.

   The successful completion of the ES-OPERATION signifies that the
   specified controls are now in force.

   The ES-OPERATION returns an indication of any ES-OPERATIONS that the
   EMSD-SA would invoke, or any message types that the EMSD-SA would
   deliver, were it not for the prevailing controls.


   Arguments

   This operation's arguments are:

   DeliveryControlArgument ::= SEQUENCE
   {
     -- Request an addition of or removal of a set of restrictions

     restrict                [0]     IMPLICIT Restrict DEFAULT update,

     -- Which operations are to be placed in the restriction set
     permissible-operations  [1]     IMPLICIT Operations OPTIONAL,

     -- What maximum content length should be allowed
     permissible-max-content-length

                                     [2]     IMPLICIT INTEGER
                                      (0..ub-content-length) OPTIONAL,



Banan                        Informational                     [Page 17]

RFC 2524                          EMSD                     February 1999


     -- What is the lowest priority message which may be delivered
     permissible-lowest-priority

                                     [3]     IMPLICIT ENUMERATED
                                              {
                                                non-urgent     (0),
                                                normal         (1),
                                                urgent         (2)
                                              } OPTIONAL,

     -- Security features
     security                        [4]     IMPLICIT SecurityElement
                                             OPTIONAL,

     -- User Feature selection
     user-features                   [5]     IMPLICIT OCTET STRING
                                             OPTIONAL
   };



   Restrict

   This argument indicates whether the controls on ES-OPERATIONS are to
   be updated or removed.  It may be generated by the EMSD-UA.

   This argument may have one of the following values:

      o update:  The other arguments update the prevailing controls;

      o remove:  All temporary controls are to be removed

   In the absence of this argument, the default update shall be assumed.


   Permissible-operations

   This argument indicates the ES-OPERATIONS that the EMSD-SA may invoke
   on the EMSD-UA. It may be generated by the EMSD-UA.

   This argument may have the value allowed or prohibited for each of
   the following:

      o message-delivery:  The EMSD-SA may/may not invoke the deliver
        ES-OPERATIONS; and

      o Other ES-OPERATIONS are not subject to controls, and may be
        invoked at any time.



Banan                        Informational                     [Page 18]

RFC 2524                          EMSD                     February 1999


   In the absence of this argument, the ES-OPERATIONS that the EMSD-SA
   may invoke on the EMSD-UA are unchanged.


   Permissible-max-content-length

   This argument contains the content-length, in octets, of the
   longest-content message that the EMSD-SA shall deliver to the EMSD-UA
   via the deliver ES-OPERATIONS. It may be generated by the EMSD-UA.

   In the absence of this argument, the permissible-maximum-content-
   length of a message that the EMSD-SA may deliver to the EMSD-UA is
   unchanged.


   Permissible-lowest-priority

   This argument contains the priority of the lowest priority message
   that the EMSD-SA shall deliver to the EMSD-UA via the deliver ES-
   OPERATIONS. It may be generated by the EMSD-UA.

   This argument may have one of the following values of the priority
   argument of the submit ES-OPERATIONS: normal, non-urgent or urgent.

   In the absence of this argument, the priority of the lowest priority
   message that the EMSD-SA shall deliver to the EMSD-UA is unchanged.


   Security

   See Section 3.4.1, "SecurityElements".


   User-features

   This argument contains information that allows the EMSD-UA to convey
   to MTS the feature set that the user is capable of supporting.  This
   argument will be defined when the setConfiguration and
   getConfiguration operations are defined.


   Results

   DeliveryControlResult ::= SEQUENCE
   {
     -- Operation types queued at the EMSD-SA due to existing
     -- restrictions.
     waiting-operations      [0]     IMPLICIT Operations DEFAULT { },



Banan                        Informational                     [Page 19]

RFC 2524                          EMSD                     February 1999


     -- Types of messages queued at the EMSD-SA due to
     -- existing restrictions
     waiting-messages        [1]     IMPLICIT WaitingMessages
                                     DEFAULT { },

     -- Content Types of messages queued at the EMSD-SA
     waiting-content-types   SEQUENCE SIZE (0..ub-content-types) OF
                                            ContentType DEFAULT { }

   };

   Restrict ::= ENUMERATED
   {
       update                                      (1),
       remove                                      (2)
   };

   Operations ::= BIT STRING
   {
       submission                                  (0),
       delivery                                    (1)
   };

   WaitingMessages ::= BIT STRING
   {
       long-content                                (0),
       low-priority                                (1)


   };


   Waiting-operations

   This result indicates the ES-OPERATIONS being held by the EMSD-SA,
   and that the EMSD-SA would invoke on the EMSD-UA if it were not for
   the prevailing controls.  It may be generated by the EMSD-SA.

   This result may have the value holding or not-holding for each of the
   following:

      o message-delivery:  The EMSD-SA is/is not holding messages, and
        would invoke the deliver ES-OPERATIONS on the EMSD-UA if it were
        not for the prevailing controls.

   In the absence of this result, it may be assumed that the EMSD-SA is
   not holding any messages for delivery due to the prevailing controls.




Banan                        Informational                     [Page 20]

RFC 2524                          EMSD                     February 1999


   Waiting-messages

   This result indicates the kind of messages the EMSD-SA is holding for
   delivery to the EMSD-UA, and would deliver via the deliver ES-
   OPERATIONS, if it were not for the prevailing controls.  It may be
   generated by the EMSD-SA.

   This result may have one or more of the following values:

      o long-content:  The EMSD-SA has messages held for delivery to the
        EMSD-UA which exceed the permissible maximum-content-length
        control currently in force;

      o low-priority:  The EMSD-SA has messages held for delivery to the
        EMSD-UA of a lower priority than the permissible-lowest-priority
        control currently in force;

   In the absence of this result, it may be assumed that the EMSD-SA is
   not holding any messages for delivery to the EMSD-UA due to the
   permissible-maximum-content-length, permissible-lowest-priority or
   permissible-security context controls currently in force.

   Errors

   See Section 3.4.3.

3.2.3  deliveryVerify

   The deliveryVerify ES-OPERATIONS enables the EMSD-UA to verify
   delivery of a message when it receives FAILURE.indication for deliver
   ES-OPERATIONS.

   deliveryVerify ES-OPERATION

       ARGUMENT DeliveryVerifyArgument
       RESULT DeliveryVerifyResult
       ERRORS
       {
           verifyError,
           resourceError,
           protocolViolation
       } ::= 5;

   The duplicate operation detection is not required for this operation.


   Arguments




Banan                        Informational                     [Page 21]