Subject: RE: [AAA-WG]: New API Draft -- Initial impression (addendum)

From: Cain Brian-BCAIN1 <[email-masked]>
Date: Wed, 18 Apr 2001 10:34:09 -0500

Oops.  I sent that last message prematurely.  Here's an addendum.

>From AVPDescriptor (4.3.3.5):
>-      public boolean isEndToEndEncrypted()
>+      public boolean isEndToEndEncryptable()
>
>-   Return true if this AVP is encrypted end-to-end.
>+   Returns true if this AVP may be encrypted end-to-end.
>

This change is in reference to the "MAY Encr" column in section 4.5 of the base protocol.

The above change would also require the following change to AVP:

>4.3.2.4 Instance Methods
+      public boolean isEndToEndEncrypted()
+
+   Returns true if this AVP is encrypted end-to-end.
+
>      public AVPDescriptor getDescriptor()
>
>   Return the AVP's descriptor.

(and possibly the following change)

>4.3.2.3 Constructor
>
>      public AVP(AVPDescriptor descriptor,
+                 boolean encryptedPayload,
>                 java.lang.Object data)
>
>   Create a new AVP object.
>
>   Parameters are:
>
>      descriptor - An AVPDescriptor object describing the AVP.
>
+      encryptedPayload - True if the data is/will be encrypted (this sets the AVP header's 'P' flag).

For outgoing messages, the API's users will want to know whether or not it's legal for them to encrypt their data, so the descriptor that they get back from the dictionary should have this information.  For incoming messages (and for the API to be able to construct proper outgoing messages), the API's users will want to know whether the data sent was actually encrypted.

-Brian