rfc2524.txt

RFC 的详细文档！

   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]

RFC 2524                          EMSD                     February 1999


   This operation's arguments are:

   DeliveryVerifyArgument ::= SEQUENCE

   {
     -- Identifier of this message. This is the same identifier that
     -- was provided to the originator in the Submission Result.
     -- See comment regarding assignment of message identifiers,
     -- at the definition of EMSDMessageId.
     message-id                                      EMSDMessageId
   };


   Message-id

   This argument contains an EMSD-SA-identifier that distinguishes the
   message from all other messages.  It shall be generated by the EMSD-
   SA, and shall have the same value as the message-submission-
   identifier supplied to the originator of the message when the message
   was submitted.


   Results

   DeliveryVerifyResult ::= SEQUENCE
   {
            status  DeliveryStatus
   };

    DeliveryStatus  ::= ENUMERATED
   {
           no-report-is-sent-out                   (1),
           delivery-report-is-sent-out             (2),
           non-delivery-report-is-sent-out         (3)
    };



   No-report-is-sent-out

   This result indicates that EMSD-SA has received the delivery verify
   and no report is sent out (either because it has not been requested
   or EMSD-SA has problems and can not send it out).


   Delivery-report-is-sent-out

   This result indicates that EMSD-SA has received the delivery verify



Banan                        Informational                     [Page 22]

RFC 2524                          EMSD                     February 1999


   and has sent the delivery report out.


   Non-Delivery-report-is-sent-out

   This result indicates that EMSD-SA has received the delivery verify
   but it has already sent out a non-Delivery report.  This should not
   happen in normal cases but a wrong user profile on EMSD-SA side can
   result in this outcome.

   Errors

   See Section 3.4.3.


3.3  EMSD-SA Invoked Operations

   This section defines the operations invoked by the EMSD-SA:

      a. deliver;

      b. submissionControl;

      c. submissionVerify.

   The deliver operation uses 3-Way handshake service of ESROS. This
   operation always uses the duplication detection functional unit.

   The submissionControl and submissionVerify operations use 2-Way
   handshake service of ESROS without duplication detection.

3.3.1  deliver

   The deliver ES-OPERATIONS enables the EMSD-SA to deliver a message to
   an EMSD-UA.

   deliver ES-OPERATION

       ARGUMENT DeliverArgument
       RESULT NULL
       ERRORS
       {
           deliveryControlViolated,
           securityError,
           resourceError,
           protocolViolation,
           messageError
       } ::= 35;



Banan                        Informational                     [Page 23]

RFC 2524                          EMSD                     February 1999


   The EMSD-UA MUST not refuse performing the deliver ES-OPERATION
   unless the delivery would violate the deliveryControl restrictions
   then in force.


   Arguments

   This operation's arguments are:

   DeliverArgument ::= SEQUENCE
   {
     -- Identifier of this message. This is the same identifier that
     -- was provided to the originator in the Submission Result.
     -- See comment regarding assignment of message identifiers,
     -- at the definition of EMSDMessageId.
     message-id                                      EMSDMessageId,

     -- Time the message was delivered to the recipient by EMSD-SA
     message-delivery-time                           DateTime,

     -- Time EMSD-SA originally took responsibility for processing
     -- of this message. This field shall be omitted if the message-id
     -- contains an EMSDLocalMessageId, because that field contains
     -- the submission time within it.
     message-submission-time [0]  IMPLICIT DateTime OPTIONAL,

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

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

     -- The type of the content
     content-type                                ContentType,

     --
     -- THE CONTENT --
     --

     -- The submitted (and now being delivered) content
     content                           ANY DEFINED BY content-type
   };









Banan                        Informational                     [Page 24]

RFC 2524                          EMSD                     February 1999


   message-id

   This argument contains an EMSD-SA-identifier that distinguishes the
   message from all other messages.  When within the EMSD, it MUST be
   generated by the EMSD-SA, and MUST have the same value as the
   message-submission-identifier supplied to the originator of the
   message when the message was submitted.


   Message-delivery-time

   This argument contains the Time at which delivery occurs and at which
   the EMSD-SA is relinquishing responsibility for the message.  It
   shall be generated by the EMSD-SA.


   Results

   This operation returns an empty result as indication of success.


   Errors

   See Section 3.4.3.


3.3.2  submissionControl

   submissionControl ES-OPERATION
       ARGUMENT SubmissionControlArgument
       RESULT SubmissionControlResult
       ERRORS
       {
           securityError,
           resourceError,
           protocolViolation
       } ::= 4;

   The submissionControl ES-OPERATIONS enables the EMSD-SA to
   temporarily limit the operations that the EMSD-UA may invoke, and the
   messages that the EMSD-UA may submit to the EMSD-SA via the submit
   ES-OPERATIONS.

   The duplicate operation detection is not required for this operation.

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




Banan                        Informational                     [Page 25]

RFC 2524                          EMSD                     February 1999


   The successful completion of the ES-OPERATIONS signifies that the
   specified controls are now in force.  These controls supersede any
   previously in force, and remain in effect until the association is
   released or the EMSD-SA re-invokes the submissionControl ES-
   OPERATIONS.

   The ES-OPERATIONS returns an indication of any ES-OPERATIONS that the
   EMSD-UA would invoke were it not for the prevailing controls.


   Arguments

   This operation's arguments are:

   SubmissionControlArgument ::= 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,

     -- Security features
     security                [3]     IMPLICIT SecurityElement
                                                     OPTIONAL
   };



   Restrict

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

   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.





Banan                        Informational                     [Page 26]

RFC 2524                          EMSD                     February 1999


   Permissible-operations

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

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

      o submit:  The EMSD-UA may/may not invoke the submit ES-
        OPERATIONS; and

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

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


   Permissible-max-content-length

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

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


   Security

   See Section 3.4.1, "SecurityElements".


   Results

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

   };








Banan                        Informational                     [Page 27]

RFC 2524                          EMSD                     February 1999


   Waiting-operations

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

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

      o submit:  The EMSD-UA is/is not holding messages, and would