Subject: Re: [Dime] Redundancy support AVPs

From: "Tom-PT Taylor" <[email-masked]>
Date: Sat, 09 Dec 2006 05:56:16 -0500

A bit late to the party, but I suggest a small wording change to clarify 
intent.

Tolga Asveren wrote:
> Hi All,
[snip]
> 
> ================================================================
> 8.22
> Session-Info AVP is used by application sessions to store session related
> opaque data in the messages. This AVP carries state information that are
> communicated between Diameter application end-points only. It provides
> applications with a generic method to store opaque data in messages for high
> availability, redundancy or other purposes that may not be defined in the
> Diameter application itself.
> 
>                                             AVP Flag Rules
>                   AVP   Data                     SHLD  MUST  MAY
> Attribute Name    Code  Type         MUST  MAY   NOT   NOT  Encr
> Session-Info       XYZ  Grouped        M    P           V     Y
> Origin-Host        264  DiamIdent      M    P           V     Y
> Session-Data       XYZ  OctetString    M    P           V     Y
> 
> Session-Info AVP
> The Session-Info AVP (AVP code xyz) is of type Grouped and is used by
> Diameter entities serving as application endpoints to send and receive
> session related opaque data. An application originating a request or answer
> message MAY include the Session-Info AVP in the message. The receiver of the
> message that includes a Session-Info AVP inserted by the remote peer MUST
> include the same Session-Info AVP in the subsequent request or answer
> messages. The originating Diameter endpoints MAY update the opaque data carried in
                 ^^^^^^^^^^^
> Session-info AVP. Receiving Diameter endpoints MUST use the last received Session-Info
                     ^^^^^^^^^
> AVP in the subsequent request and answers they generate.
> 
[snip]

_______________________________________________
DiME mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/dime